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

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-21303:
-----------------------------------------

{quote}
;qualifyfreq=60                 ; Qualification: How often to check for the host to be up in seconds
                                ; and reported in milliseconds with sip show settings.
                                ; Set to low value if you use low timeout for NAT of UDP sessions
                                ; Default: 60
;qualifygap=100                 ; Number of milliseconds between each group of peers being qualified
                                ; Default: 100
;qualifypeers=1                 ; Number of peers in a group to be qualified at the same time
                                ; Default: 1
{quote}

The documentation in the sample seems pretty clear. JoshE - you can provide a documentation patch if there is a way to provide additional clarity.

Other than that, does it appear to be behaving as expected per the documentation and Michael's comments?
                
> 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
>          Components: Channels/chan_sip/General
>    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