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

[Jason Hord (JIRA)]

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

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

With 15.2.2 we currently define AORs in pjsip.conf.  Prior to this we were able to rely solely on the realtime database, but we needed to make this change in order to have qualification work.  The relevant section is here:

{noformat}
[FC-DFW-PROXY]
type=aor
contact=sip:45.32.207.203:5060
qualify_frequency=30
{noformat}

The output of 'pjsip show aor FC-NYC-PROXY' appears to be incorrect.  It shows different values for several settings.  I am assuming that's because it is only pulling the entry from pjsip.conf and using defaults for the values not provided.

The output of 'pjsip show endpoint FC-NYC-PROXY' does appear correct.  The values reflect the settings in the realtime database.

Here is the relevant output from 'pjsip show contacts':

{noformat}
  Contact:  FC-NYC-PROXY/sip:69.55.55.125:5060             58dc908c3c Created       0.000
{noformat}

And here is the output of 'pjsip show scheduled_tasks':

{noformat}
pjsip/options/FC-NYC-PROXY-00000042              30.000      2294 wait   2018-08-06 11:49:55  2018-08-07 06:56:53  2018-08-07 06:57:22 (   20)
{noformat}

Just looking at all of this, I'm guessing that the default max_contacts of 0 with the way we have AORs defined in pjsip.conf could be a problem.  I would still like to know if there is a way to define the AOR in the realtime database and not rely on the pjsip.conf values.

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