[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=251427#comment-251427 ] 

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

To summarize the problem; the sip provider requires registration re-registration every 120 seconds and asterisk on the other 700+ occasions this day does the right thing, but on this one occasion asterisk ignores that and decides that the next registration is not required for an hour. This results in the trunk being unregistered for 58 minutes. Our up stream provider has confirmed this, and also the absence of incoming calls also confirms this.

As asterisk asterisk has successfully registered and thinks it doesn't need to register again for an hour, so it thinks that it is registered for the next hour despite that not being the case.

In the full logs it can be seen that there is a registration from asterisk every 2 minutes of the day, except after this event where there are no registrations for this trunk for an hour after which things go back to normal.

An Unauthorized is just part of the normal process of registering. As I understand it sip auth requires attempting registering without a password and the parts of the failed response are used to hash the password when submitting the proper auth.

here are the important parts

the sip provider responds with expires=120, so after this successful registration we will become unregistered if we don't register again.
{noformat}Jul 14 17:44:42 : Contact: <sip:customer at 1.2.3.4:5060;line=oxaimwu>;expires=120{noformat}

then asterisk decides to schedule the next registration for 1 hours time (3590 seconds)
{noformat}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{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, 16.11.1
>         Environment: 18.04 ubuntu, asterisk 16.10, docker, pjsip
>            Reporter: Robert Sutton
>            Assignee: 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)