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

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

Joshua and Richard,

Thanks for the updates.  We have been anxious to test the new OPTIONS code because one of our servers has over 3,500 contacts registered and we have been fighting edge-case performance issues.  We don't run 24,000 endpoints on any single server and 3,500-4,000 is probably all we need.  We start seeing call quality drop off after that due to CPU contention.

Is there a document that explicitly describes the startup process for Asterisk with respect to this new patch?  I have looked over the changelog and got a sense for what changed but I'm still having trouble getting the configuration I would like.  Perhaps you could point me to a couple of source files to look over?

I'm thinking what I might try to do is add functionality to only start qualifying static endpoints.  I'm guessing these would either be endpoints with a contact specified on the AOR or perhaps just flagged in the config.  From our perspective this should allows us to quickly load the 40-50 endpoints we need at service startup and then let normal Asterisk processing proceed for dynamic endpoints as they re-register.  I'm not sure how well this would play with astdb so any opinion would be welcome.


> 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-patched-aor.txt, debug-28003-pjsip-aor.txt, debug-28003-pjsip-endpoint.txt, debug-28003-realtime-only.txt, extconfig.conf, jira_asterisk_28003_debug_v15.5.0.patch, modules.conf, sorcery.conf
>
>
> 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)