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

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28961:
------------------------------------------

Anything in the log warning, error, or notice wise? For instance see anything similar to the following: "... task processor queue reached ..."

If the Asterisk system shows everything is fine from a registration perspective (e.g. CLI shows outbound registrations, etc... look okay) then how do you know something is wrong? Is it a case of the upstream provider expiring the registration, Asterisk doesn't send a refresh but still shows everything is "fine"?

If that's the case is no outbound sip registration observed? Like if you got a pcap then a SIP register never goes out to the provider?

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