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

Jason Hord (JIRA) noreply at issues.asterisk.org
Thu Aug 9 16:21:54 CDT 2018


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

Jason Hord commented on ASTERISK-28003:
---------------------------------------

I just wanted to update the ticket with some new information.  I have found a process to produce the behavior I'd like, but I'm a little confused on why it works the way it does.

I have completely emptied pjsip.conf in order to rely on our ODBC realtime only.  I have also modified sorcery.conf to only use memory_cache and realtime sources.

When Asterisk starts, I still have no AORs or endpoints loaded.  However, if I run 'pjsip reload qualify endpoint FC-NYC-PROXY', the AOR is created, the endpoint is created, the contact is created, and it qualifies successfully.

What is odd to me is that prior to that, if I run 'pjsip show qualify endpoint FC-NYC-PROXY', I get no output.  Running 'pjsip show qualify aor FC-NYC-PROXY' gives the following error:

{noformat}
$ asterisk -rx 'pjsip show qualify aor FC-NYC-PROXY'
Unable to retrieve aor 'FC-NYC-PROXY' qualify options
Command 'pjsip show qualify aor FC-NYC-PROXY' failed.
{noformat}

After performing the reload operation, however, I get normal output for both commands.  It would appear as though the AOR and/or endpoint aren't loaded from any source until referenced in some way.  Is that correct behavior or would this indicate a configuration problem in our realtime database?

> 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: Unassigned
>            Severity: Minor
>              Labels: fax, pjsip
>         Attachments: debug-28003-pjsip-aor.txt, debug-28003-pjsip-endpoint.txt, debug-28003-realtime-only.txt
>
>
> 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)



More information about the asterisk-bugs mailing list