03-19-2010 10:48 PM - edited 03-21-2019 09:25 AM
Hi!
I am using freeswitch to connect to my SPA3102 which is registered using TLS. Quite often I see the following, which results in FreeSwitch ending the call with NORMAL_TEMPORARY_FAILURE.
The syslog from the SPA3102 looks like this:
Mar 19 19:58:15 xxx.xxx.xxx.xxx CC:pc(1)=130 not in codec list
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0:0]AUD ALLOC CALL (port=30322)
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0:0]RTP Rx Up
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0]->124.xxx.xxx.xxx:442(519)
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0]->124.xxx.xxx.xxx:442(519)
Mar 19 19:58:15 xxx.xxx.xxx.xxx SIP/2.0 180 Ringing To: <sip:2001@xxx.xxx.xxx.xxx:5070;transport=tls>;tag=80a48d552a9b8589i0 From: "anonymous" <sip:anonymous@124.xxx.xxx.xxx>;tag=BFgcyp329X51S Call-ID: 650ac1cf-add8-122d-71b8-00e04c0312e9 CSeq: 128376211 INVITE Via: SIP/2.0/TLS 124.xxx.xxx.xxx:442;branch=z9hG4bK2U30XeKBjamap;rport=442 Contact: 2001 <sip:2001@xxx.xxx.xxx.xxx:5070;transport=tls> Server: Linksys/SPA3102-5.1.10(GW) Remote-Party-ID: 2001 <sip:2001@mydns.dyndns.org:442>;screen=yes;party=called Content-Length: 0
Mar 19 19:58:15 xxx.xxx.xxx.xxx
Mar 19 19:58:15 xxx.xxx.xxx.xxx
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0]SIP/TCP ServerDisconnected:-257
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0]SIP/TCP ServerDisconnected:-257
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0]FM Alert Stop RxTx (c=0024e6b0;a=0)
Mar 19 19:58:15 xxx.xxx.xxx.xxx [0:0]AUD Rel Call
Mar 19 19:58:15 xxx.xxx.xxx.xxx CC:Failed w/ Ringing
Mar 19 19:58:15 xxx.xxx.xxx.xxx DLG Terminated 2a8d10
Mar 19 19:58:15 xxx.xxx.xxx.xxx Sess Terminated
Can someone explain why this might be failing? Thanks!
03-22-2010 08:26 AM
Dear Sir;
Do you have network traces, e.g. ethereal or wireshark??
Regards
Alberto
03-22-2010 02:41 PM
I use TLS, so are pcap traces required? They won't show much.
I can give you the complete syslog from the spa3102. Is that enough?
03-24-2010 02:58 AM
Dear Sir;
Please send the syslog traces. Wont be able to see RTP but it may be sufficient.
Regards
Alberto
03-24-2010 03:46 PM
03-30-2010 01:34 AM
Hi Alberto,
Did the logs help at all?
03-30-2010 08:02 AM
Dear Sir;
I've escalated this, as this has to do with TCP/IP interop. Why are you using DDNS all the way to the device? This is not a normal practice, you either use STUN or fixed mapping (or SBC function at the server).
Stay tuned.
Alberto
03-30-2010 03:36 PM
Hi Alberto,
Thanks for replying. I'm not using DDNS all the way to the device for SIP handling - these should have been removed from the syslog.
Looking forward to engineerings response.
Thanks
04-15-2010 04:19 AM
Hi Alberto,
Has there been any response from Engineering?
Thanks!
04-23-2010 03:37 AM
Hi Alberto,
Has there been any response from Engineering?
Thanks!
05-18-2010 12:06 AM
Hi Again,
Please, has there been any updates on this failure?
Thanks
06-05-2010 01:41 AM
Hi Alberto,
I haven't heard anything for months regarding his fault. You stated in March that 'I've escalated this, as this has to do with TCP/IP interop.'
Please can you give me some indication of the status of the investigation.
06-08-2010 03:46 AM
Dear Sir;
I'm sorry for the delay, the email was sitting on my inbox (my mistake).
One question is that on the trace we see a "130 not in codec list" between the trying and ringing messages. Can you please check this is not causing an issue on your system?
Regards
Alberto
06-22-2010 06:01 AM
Hi Albert,
I still see this problem after shutting down all codecs not being used, and I do not see the "130 not in codec list" anymore. The fault is still there - see below from the syslog
Jun 22 19:27:35 92.xxx.xxx.xxx SIP/2.0 180 Ringing To: <2001>;tag=9766c2dbbb305122i0 From: "1000" <>>2001>1000@124.xx.xx.xx>;tag=gv0X0eX3jKrme Call-ID: 3bc7e780-f883-122d-c6a6-00e04c0312e9 CSeq: 132481091 INVITE Via: SIP/2.0/TLS 124.xx.xx.xx:442;branch=z9hG4bK8K08jFN2FH2Ur;rport=442 Contact: 2001 <2001> Server: Linksys/SPA3102-5.1.10(GW) Remote-Party-ID: 2001 <>>2001>2001@mydns.dyndns.org:442>;screen=yes;party=called Content-Length: 0
Jun 22 19:27:35 92.xxx.xxx.xxx
Jun 22 19:27:35 92.xxx.xxx.xxx
Jun 22 19:27:36 92.xxx.xxx.xxx [0]SIP/TCP ServerDisconnected:-257
Jun 22 19:27:36 92.xxx.xxx.xxx [0]SIP/TCP ServerDisconnected:-257
Jun 22 19:27:36 92.xxx.xxx.xxx [0]FM Alert Stop RxTx (c=0024e6b0;a=0)
Jun 22 19:27:36 92.xxx.xxx.xxx [0:0]AUD Rel Call
Jun 22 19:27:36 92.xxx.xxx.xxx CC:Failed w/ Ringing
Jun 22 19:27:36 92.xxx.xxx.xxx DLG Terminated 2a8d10
Jun 22 19:27:36 92.xxx.xxx.xxx Sess Terminated
Jun 22 19:27:36 92.xxx.xxx.xxx RSE_DEBUG: getting alternate from domain:mydns.dyndns.org
Jun 22 19:27:36 92.xxx.xxx.xxx [0]SIP/TCP NewLocalPort:5064
Jun 22 19:27:36 92.xxx.xxx.xxx [0]SIP/TCP NewLocalPort:5064
Jun 22 19:27:36 92.xxx.xxx.xxx [0:0]SIP/TCP:Connecting(25)
Jun 22 19:27:36 92.xxx.xxx.xxx [0:0]SIP/TCP:Connecting(25)
Jun 22 19:27:36 92.xxx.xxx.xxx [0:0]SIP/TCP:Connect=-1
Jun 22 19:27:36 92.xxx.xxx.xxx [0:0]SIP/TCP:Connect=-1
Jun 22 19:27:36 92.xxx.xxx.xxx RSE_DEBUG: getting alternate from domain:mydns.dyndns.org
Jun 22 19:27:36 92.xxx.xxx.xxx [0]SIP/TCP Backoff 500 ms
Jun 22 19:27:36 92.xxx.xxx.xxx [0]SIP/TCP Backoff 500 ms
Jun 22 19:27:37 92.xxx.xxx.xxx [0]SIP/TCP NewLocalPort:5065
Jun 22 19:27:37 92.xxx.xxx.xxx [0]SIP/TCP NewLocalPort:5065
Jun 22 19:27:37 92.xxx.xxx.xxx [0:0]SIP/TCP:Connecting(26)
Jun 22 19:27:37 92.xxx.xxx.xxx [0:0]SIP/TCP:Connecting(26)
Jun 22 19:27:37 92.xxx.xxx.xxx [0:0]SIP/TCP:Connect=0
Jun 22 19:27:37 92.xxx.xxx.xxx [0:0]SIP/TCP:Connect=0
Jun 22 19:27:37 92.xxx.xxx.xxx [0:0]SIP/TLS:Connecting(26)...
Jun 22 19:27:37 92.xxx.xxx.xxx [0:0]SIP/TLS:Connecting(26)...
Jun 22 19:27:38 92.xxx.xxx.xxx [0:0]SIP/TLS:Connect=0
Jun 22 19:27:38 92.xxx.xxx.xxx [0:0]SIP/TLS:Connect=0
Jun 22 19:27:38 92.xxx.xxx.xxx [0:0]SIP/TLS:Connect OK
Jun 22 19:27:38 92.xxx.xxx.xxx [0:0]SIP/TLS:Connect OK
Jun 22 19:27:38 92.xxx.xxx.xxx [0]->124.xx.xx.xx:442(787)
Jun 22 19:27:38 92.xxx.xxx.xxx [0]->124.xx.xx.xx:442(787)
Jun 22 19:27:38 92.xxx.xxx.xxx REGISTER sip:
06-23-2010 04:03 AM
Dear Mark;
Thanks for sending the traces. I'll check with engineering and let you know
Alberto
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide