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

Jason Hord edited comment on ASTERISK-28003 at 8/10/18 4:12 PM:
----------------------------------------------------------------

Thank-you for the response, Richard.  I was able to play around with a few settings and am seeing some different behavior now.  If I remove {{allow_unqualified_fetch}} or set it to 'yes', all of the AORs and endpoints are loaded as expected.  The contacts also qualify properly and everything appears to be working as expected.

However, I'm also seeing a tremendous amount of load on the system.  The asterisk process will use 95%+ CPU continuously and never seems to drop.  I was able to attempt a test call and audio was completely choppy and lagged.

Our realtime database has over 24,000 endpoints in total and it looks like it may be loading all of these on startup.  The vast majority of these are dynamic endpoints that only need to be present when a device registers.  We need to load around 50 static endpoints, though.  I'm still a little unclear on all the options that can be set in sorcery.conf.  Is there a magical combination that will only load our static endpoints but not dynamic ones until registration?


was (Author: jhord):
Thank-you for the response, Richard.  I was able to play around with a few settings and am seeing some different behavior now.  If I remove {noformat}allow_unqualified_fetch{noformat} or set it to 'yes', all of the AORs and endpoints are loaded as expected.  The contacts also qualify properly and everything appears to be working as expected.

However, I'm also seeing a tremendous amount of load on the system.  The asterisk process will use 95%+ CPU continuously and never seems to drop.  I was able to attempt a test call and audio was completely choppy and lagged.

Our realtime database has over 24,000 endpoints in total and it looks like it may be loading all of these on startup.  The vast majority of these are dynamic endpoints that only need to be present when a device registers.  We need to load around 50 static endpoints, though.  I'm still a little unclear on all the options that can be set in sorcery.conf.  Is there a magical combination that will only load our static endpoints but not dynamic ones until registration?

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