[asterisk-bugs] [JIRA] (ASTERISK-28003) Qualifying non-authenticated endpoints on startup

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-28003:
--------------------------------------------

To answer your question, no that is not correct behavior as all those records were asked for when Asterisk started.

When asterisk starts, right after res_pjsip.so registers endpoint, contact, and aor option parameters with the sorcery configuration framework res_pjsip attempts to load all endpoints from the database.  When res_pjsip sets up the qualify options ping sub-module it will also attempt to get all aors and endpoints.  When chan_pjsip.so loads after res_pjsip.so it also reloads all endpoints to update their device state from invalid.  Something seems to not be ready to handle the database requests until later.

You get the 'pjsip show qualify aor FC-NYC-PROXY' error because the AORs didn't get loaded when the qualify options sub-module couldn't load the aor records.

> Qualifying non-authenticated endpoints on startup
> -------------------------------------------------
>
>                 Key: ASTERISK-28003
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28003
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 15.5.0
>         Environment: CentOS 7.5
>            Reporter: Jason Hord
>            Assignee: Jason Hord
>            Severity: Minor
>              Labels: fax, patch, pjsip
>         Attachments: debug-28003-pjsip-aor.txt, debug-28003-pjsip-endpoint.txt, debug-28003-realtime-only.txt, jira_asterisk_28003_debug_v15.5.0.patch
>
>
> It would appear as though something has changed after Asterisk version 15.2.2 related to manual/persistent endpoints being qualified on startup.
> At the company I work for, we currently run 15.2.2 with AORs defined in pjsip.conf.  When Asterisk starts up it will create endpoints and contacts for these based on settings from our realtime database and qualify them on regular intervals.  We use this to keep ensure our outbound SIP proxies are always in a known state.
> While testing upgrades to 15.4 and 15.5 I have found this to no longer be the case.  The same configuration we are using for 15.2.2 will create the endpoints but they are never qualified and the contacts always just show 'Created'.  Manually qualifying these endpoints using 'pjsip qualify $endpoint' doesn't even appear to send SIP traffic.
> Is this expected behavior with 15.4+?  What is the correct way to configure static endpoints/contacts in the realtime database such that they will be qualified on startup?  Since we have a large, distributed infrastructure we would like to avoid using pjsip.conf completely.



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