[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=244414#comment-244414 ] 

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

How to configure endpoints and aors as well as where they are retrieved from hasn't changed.  There likely has been a few new options added to endpoints since v15.2.2 that you would need to update your database schema.  These would be mentioned in the CHANGES and UPGRADE.txt files.  There are Alembic scripts available (See the contrib/ast-db-manage directory in the source tree) to manage the database schema updates.

Qualifying endpoints was rewritten (ASTERISK-26806) and first released in the 15 branch in v15.5.0.

Are you sure you are having these issues in v15.4.0 too?
Are the aors and endpoints loaded?
Does the CLI "pjsip qualify $endpoint" give an error?
What is a typical endpoint and aor configuration?

> 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.4.0, 15.5.0
>         Environment: CentOS 7.5
>            Reporter: Jason Hord
>            Severity: Minor
>              Labels: pjsip
>
> 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)