[asterisk-bugs] [JIRA] (ASTERISK-21303) qualifygap SIP general setting appears broken

[Michael L. Young (JIRA)]

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

Michael L. Young commented on ASTERISK-21303:
---------------------------------------------

JoshE, from looking at the source, the "groups" has to do with how many peers at a time get poked.  The setting for that is "qualifypeers".  The default is 1 peer every 10th of a second.  So, you can send a qualify to 10 peers every 100ms or 10 peers every 500ms or keep it at the default of 1 peer every 100ms, as an example.

In sip_poke_all peers, the check "if (num == global_qualify_peers)", is the part that handles this "group" mentioned in sip.conf.

1200ms is only 1.2 seconds.  Have you tried a higher setting?  With your peers being in realtime, hopefully you are not having to do a "sip reload" too often.
                
> qualifygap SIP general setting appears broken
> ---------------------------------------------
>
>                 Key: ASTERISK-21303
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21303
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.2.1
>            Reporter: JoshE
>
> Running Asterisk 11 with around 1600 realtime peers, all of which are qualified behind remote NAT.  
> I am seeing an extremely painful issue with sip reloads generating massive storms of OPTIONS messages, most of which can't be responded to within 2000 ms, so the peer goes missing.  In the case where SRV endpoints are used, this generates a storm of traffic to secondary/tertiary servers, which puts the entire system in a loop.
> My initial solution was to use the qualifygap setting in sip.conf [general].  However, this appears to actually be broken.  When setting this setting to 500 or even 1200, I am still seeing many, many options messages / time period.  I am not sure I have implemented qualifygap correctly, as there is effectively no documentation on it.  I am not sure what the "group" referenced in the comments ("Number of milliseconds between each group of peers being qualified") refers to.  The sip_poke_all_peers seems to not differentiate anything on the basis of any sort of group.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira