grandstream GXW4104 (GXW410x) errors
I have the GXW4104 up and working - but I'm getting a error level log listed as: Sep 19 15:16:03 gxw4104 GS_LOG: [00:0B:82:48:E3:94][712][9660000322A][1.4.1.4] 1376 cm_rtp.c discard it, RTP Ver no match ! Sess: 0 Any clue as to what it might mean? Didn't see anything in the freeswitch logs at error level. At boot time the GXW4104 spits out a different error Sep 19 15:18:40 gxw4104 GS_LOG: [00:0B:82:48:E3:94][707][9660000322A][1.4.1.4] TIMER: Invalid timer period: 0, TimerID: 6 sip_transport.c:539 Sep 19 15:18:40 gxw4104 GS_LOG: [00:0B:82:48:E3:94][707][9660000322A][1.4.1.4] TIMER: Invalid timer period: 0, TimerID: 2 sip_transport.c:539 I'm actually writing up a how-to-config for FS on these. The SIP settings can be seen at http://xtronics.com/uploads/gxw4104_accounts.sip_settings.png -------------------------------------------------------------------------------- Karl Schmidt EMail Karl@xtronics.com Transtronics, Inc. WEB http://secure.transtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Full government control of all activities of the individual is virtually the goal of both national parties. --Ludwig von Mises --------------------------------------------------------------------------------
Curious, I can't find a single reference to that anywhere on Google. Perhaps try messing around with some of the RTP/SDP settings and see if you can make the error change/disappear. You could also try throwing the phone onto a clean standalone freeswitch instance and see if the problem still happens, or put it onto another platform, compare the SDP and go from there. Or throw a proxy in between it and modify the SDP on the fly to see if you can change the result. Keep us posted on how you get on, it would be good to document this if possible. Hope this helps Cal On Thu, Sep 19, 2013 at 9:36 PM, Karl Schmidt <karl@xtronics.com> wrote:
I have the GXW4104 up and working - but I'm getting a error level log listed as:
Sep 19 15:16:03 gxw4104 GS_LOG: [00:0B:82:48:E3:94][712][9660000322A][1.4.1.4] 1376 cm_rtp.c discard it, RTP Ver no match ! Sess: 0
Any clue as to what it might mean?
Didn't see anything in the freeswitch logs at error level.
At boot time the GXW4104 spits out a different error
Sep 19 15:18:40 gxw4104 GS_LOG: [00:0B:82:48:E3:94][707][9660000322A][1.4.1.4] TIMER: Invalid timer period: 0, TimerID: 6 sip_transport.c:539 Sep 19 15:18:40 gxw4104 GS_LOG: [00:0B:82:48:E3:94][707][9660000322A][1.4.1.4] TIMER: Invalid timer period: 0, TimerID: 2 sip_transport.c:539
I'm actually writing up a how-to-config for FS on these.
The SIP settings can be seen at http://xtronics.com/uploads/gxw4104_accounts.sip_settings.png
-------------------------------------------------------------------------------- Karl Schmidt EMail Karl@xtronics.com Transtronics, Inc. WEB http://secure.transtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434
Full government control of all activities of the individual is virtually the goal of both national parties. --Ludwig von Mises
--------------------------------------------------------------------------------
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On 09/25/2013 11:03 AM, Cal Leeming [Simplicity Media Ltd] wrote:
Curious, I can't find a single reference to that anywhere on Google.
Perhaps try messing around with some of the RTP/SDP settings and see if you can make the error change/disappear.
You could also try throwing the phone onto a clean standalone freeswitch instance and see if the problem still happens, or put it onto another platform, compare the SDP and go from there. Or throw a proxy in between it and modify the SDP on the fly to see if you can change the result.
Keep us posted on how you get on, it would be good to document this if possible.
Hope this helps
It is working as is - I'm thinking it could be log noise? - testing for a RTP version? I did find that backing up the config via the web interface and restoring via TFTP does not work quite right. I resorted to doing screen grabs of the config as I don't trust the workings of the provisioning software other than doing firmware upgrades. My observations about grandstream - I have both a FXS and FXO box: The hardware seems to work just fine, but the configuration software as the Chinese curse says, is 'interesting'. Up-to-date versions do appear to work - but need polishing. But compared to fighting with digium hardware it is a breeze. Provisioning requires downloading via the web interface your settings - then you have to 'compile' the settings to create an upload file. (Which is insane). I would just skip the provisioning - just use the web interface to configure. The syslog is quite useful for debugging. I now have these grandstreams working and a couple of polycom IP 560's working. My take with the Polycoms again is to skip the provisioning and use the web interface to backup and restore unless you have more than 20 some phones. -------------------------------------------------------------------------------- Karl Schmidt EMail Karl@xtronics.com Transtronics, Inc. WEB http://secure.transtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Even if you are on the right track, you'll get run over if you just sit there - Will Rogers --------------------------------------------------------------------------------
participants (2)
-
Cal Leeming [Simplicity Media Ltd]
-
Karl Schmidt