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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28961:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> 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)