[asterisk-bugs] [JIRA] (ASTERISK-28961) res_pjsip_outbound_registration: Re-registration is incorrectly timed

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28961:
--------------------------------------

    Summary: res_pjsip_outbound_registration: Re-registration is incorrectly timed  (was: asterisk stops sending outbound registrations.)

> res_pjsip_outbound_registration: Re-registration is incorrectly timed
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-28961
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28961
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_outbound_registration
>    Affects Versions: 16.10.0, 16.11.1
>         Environment: 18.04 ubuntu, asterisk 16.10, docker, pjsip
>            Reporter: Robert Sutton
>            Assignee: Unassigned
>
> 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)