[asterisk-bugs] [JIRA] (ASTERISK-28961) asterisk stops sending outbound registrations.

[Robert Sutton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251420#comment-251420 ] 

Robert Sutton commented on ASTERISK-28961:
------------------------------------------

OK, So I found an occurrence where asterisk ignored the returned expiry.

This resulted in the trunk going off line for an hour.

It is interesting that the contact appeared twice in the response from the sip provider (this is unusual), but I do wonder if asterisk may have logged it incorrectly.

{noformat}
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c  sip_outbound_registration_response_cb  Received REGISTER response 401(Unauthorized)
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c  handle_registration_response  Processing REGISTER response 401 from server 'sip:trunk.com' for client 'sip:customer at trunk.com'
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c   handle_registration_response  Sending authenticated REGISTER to server 'sip:trunk.com' from client 'sip:customer at trunk.com'
Jul 14 17:44:42 : <--- Transmitting SIP request (935 bytes) to UDP:1.2.3.5:5060 --->
Jul 14 17:44:42 : REGISTER sip:trunk.com SIP/2.0 
Jul 14 17:44:42 : Via: SIP/2.0/UDP 1.2.3.4:5060;rport;branch=z9hG4bKPj718c833e-7e36-4509-ac44-879e8e9f155b 
Jul 14 17:44:42 : From: <sip:customer at trunk.com>;tag=c82c4b96-f29a-4b36-85e2-a50c8a4f4849 
Jul 14 17:44:42 : To: <sip:customer at trunk.com> 
Jul 14 17:44:42 : Call-ID: 4fae2819-4bb1-4205-b412-f44457b54474 
Jul 14 17:44:42 : CSeq: 40622 REGISTER 
Jul 14 17:44:42 : Contact: <sip:customer at 1.2.3.4:5060;line=oxaimwu> 
Jul 14 17:44:42 : Expires: 3600 
Jul 14 17:44:42 : Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER 
Jul 14 17:44:42 : Max-Forwards: 70 
Jul 14 17:44:42 : User-Agent: Asterisk PBX 16.11.1 
Jul 14 17:44:42 : Authorization: Digest username="customer", realm="trunk.com", nonce="a6bc471d-be32-44bb-832a-e48df33a7570", uri="sip:trunk.com", response="a6275e95bfcd66150dcd647b403c5336", algorithm=MD5, cnonce="65c4872c317849a8bc11f6a33f4fde5e", qop=auth, nc=00000001 
Jul 14 17:44:42 : Content-Length:  0 
Jul 14 17:44:42 :  
Jul 14 17:44:42 :
Jul 14 17:44:42 : <--- Received SIP response (745 bytes) from UDP:1.2.3.5:5060 --->
Jul 14 17:44:42 : SIP/2.0 200 OK 
Jul 14 17:44:42 : Via: SIP/2.0/UDP 1.2.3.4:5060;received=1.2.3.4;rport=5060;branch=z9hG4bKPj718c833e-7e36-4509-ac44-879e8e9f155b 
Jul 14 17:44:42 : From: <sip:customer at trunk.com>;tag=c82c4b96-f29a-4b36-85e2-a50c8a4f4849 
Jul 14 17:44:42 : To: <sip:customer at trunk.com>;tag=yQSjSU5jj0v0c 
Jul 14 17:44:42 : Call-ID: 4fae2819-4bb1-4205-b412-f44457b54474 
Jul 14 17:44:42 : CSeq: 40622 REGISTER 
Jul 14 17:44:42 : Contact: <sip:customer at 1.2.3.4:5060;line=oxaimwu>;expires=120 
Jul 14 17:44:42 : Contact: <sip:customer at 1.2.3.4:5060;line=oxaimwu>;expires=120 
Jul 14 17:44:42 : Date: Tue, 14 Jul 2020 07:44:42 GMT 
Jul 14 17:44:42 : User-Agent: ColouredLines-sipswitch 
Jul 14 17:44:42 : Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY 
Jul 14 17:44:42 : Supported: timer, path, replaces 
Jul 14 17:44:42 : Content-Length: 0 
Jul 14 17:44:42 :  
Jul 14 17:44:42 :
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c  sip_outbound_registration_response_cb  Received REGISTER response 200(OK)
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c  handle_registration_response  Processing REGISTER response 200 from server 'sip:trunk.com' for client 'sip:customer at trunk.com'
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c  handle_registration_response  Outbound registration to 'sip:trunk.com' with client 'sip:customer at trunk.com' successful
Jul 14 17:44:42 :    res_pjsip_outbound_registration.c  schedule_registration  Scheduling outbound registration to server 'sip:trunk.com' from client 'sip:customer at trunk.com' in 3590 seconds
Jul 14 17:44:52 :    res_pjsip/pjsip_resolver.c    sip_resolve  [0x7f297c040d38] Starting initial resolution using parallel queries for target 'trunk.com'
Jul 14 17:44:52 :    res_pjsip/pjsip_resolver.c    sip_resolve_callback  [0x7f297c040d38] All parallel queries completed
Jul 14 17:44:52 :    res_pjsip/pjsip_resolver.c    sip_resolve_callback  [0x7f297c040d38] Resolution completed - 1 viable targets
J
{noformat}

> asterisk stops sending outbound registrations.
> ----------------------------------------------
>
>                 Key: ASTERISK-28961
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28961
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.10.0
>         Environment: 18.04 ubuntu, asterisk 16.10, docker, pjsip
>            Reporter: Robert Sutton
>
> Systems periodically get into a state where they stop registering the trunks to the sip provider.
> Our up stream provider tells us that when this happens it lasts for about an hour and then starts working again (happened at 3am, by the time we investigated it had resolved itself).
> We've also observed (historically from logs) that when it happens asterisk still thinks that it is registered. ie show registrations, show endpoints, show contacts.
> This is not much to go on, but we are having trouble catching a system in the act.
> if the required logging doesn't generate to much load, we cloud leave it turned on.
> What logging levels would be required to be useful here?



--
This message was sent by Atlassian JIRA
(v6.2#6252)