Detailed SIP Registration Debugging


#1

Three weeks ago I set up a UCM6202 using the European/German SIP provider Axxeso. Registration of the two SIP trunk was straight forward and worked right away. However, now all of a sudden registration stopped working with a 408 Error:

Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.475] VERB [08297] res_pjsip_logger.c:118: <--- Transmitting SIP request (587 bytes) to UDP:83.125.37.14:5060 ---> REGISTER sip:TXL42.AXXESO.COM SIP/2.0^M Via: SIP/2.0/UDP 68.7.84.58:5060;rport;branch=z9hG4bKPj0d6aca1f-fd0f-4912-9924-9c1ddc380c8e^M From: <sip:02232005201@TXL42.AXXESO.COM>;tag=19a2f9a5-8d26-421c-ad61-05f648762730^M To: <sip:02232005201@TXL42.AXXESO.COM>^M Call-ID: ae78256d-63ef-4eeb-9e30-cad4f322a30c^M CSeq: 52538 REGISTER^M Contact: <sip:02232005201@68.7.84.58:5060>^M Expires: 120^M Allow: OPTIONS, INFO, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REFER, MESSAGE, REGISTER^M Max-Forwards: 70^M User-Agent: Grandstream UCM6202V1.5A 1.0.18.12^M Content-Length:  0^M ^M
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[08297] res_pjsip_log_forwarder.c:97: <PJSIP>	 tsx0xd71dd4 Timeout timer event
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[08297] res_pjsip_log_forwarder.c:97: <PJSIP>	 tsx0xd71dd4 .State changed from Calling to Terminated, event=TIMER
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[08297] res_pjsip_outbound_registration.c:1000: Received REGISTER response 408(Request Timeout) from server 'sip:TXL42.AXXESO.COM' for client 'sip:02232005202@TXL42.AXXESO.COM
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[08297] res_pjsip_log_forwarder.c:97: <PJSIP>	 tsx0xd71dd4 Timeout timer event
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[08297] res_pjsip_log_forwarder.c:97: <PJSIP>	 tsx0xd71dd4 .State changed from Terminated to Destroyed, event=TIMER
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[10892] res_pjsip_outbound_registration.c:858: Processing REGISTER response 408 from server 'sip:TXL42.AXXESO.COM' for client 'sip:02232005202@TXL42.AXXESO.COM'
Dec 21 20:12:01 UCM6202 user.debug asterisk:  [20181221 20:12:01.944] DEBUG[10892] res_pjsip_outbound_registration.c:673: Scheduling outbound registration to server 'sip:TXL42.AXXESO.COM' from client 'sip:02232005202@TXL42.AXXESO.COM' in 20 seconds

It is not a networking issue. The UCM can ping the SIP server. A SIP soft client and a Grandstream phone on the same network can successfully register with the SIP server. The UCM can also register successfully with a SIP trunk from another provider.

I am at a loss what the issue could be. The syslogs do not tell that much. Is there a way to get a more detailed log?

Thank you.


#2

Use the network capture function in maintenance. a 408 is a timeout. Let the capture run for a few minutes.


#3

Thank you. There is indeed no response from the SIP server to the registration request. That is odd because the SIP server responds to registration requests from Grandstream phones and softphones on the same network. Since the network is behind a NAT the IP address the registration requests are coming from is always the same.

I have the suspicion that the SIP provider blocks the registration requests from the UCM. Is there a way to change the user agent used by the SIP requests?


#4

Can you send me the trace? It seems unlikely that the UA would be the cause, but I suppose it possible.