[asterisk-users] SIP Qualify

[Pavel Jezek]

Hello, is the same qualify behaviour with iax?
i.e. iax qualify also pools peers every 60s and wait "qualify=xx ms" to 
peer respond?
I have set for iax peer:

 Qualify        : every 5000ms when OK, every 10000ms when UNREACHABLE 
(sample smoothing On)

so, I accept 5s delay in response from client, but asterisk logs still 
this messages (look at measured delay cca 2000ms vs. 5000ms, that I can 
accept)
I'm confused :-\
PJ


Aug 15 02:26:32 NOTICE[28564] chan_iax2.c: Peer 'wilder' is now TOO 
LAGGED (2023 ms)!
Aug 15 02:27:04 NOTICE[28564] chan_iax2.c: Peer 'wilder' is now TOO 
LAGGED (2026 ms)!
Aug 15 02:31:18 NOTICE[28564] chan_iax2.c: Peer 'wilder' is now TOO 
LAGGED (2034 ms)!
Aug 15 02:31:40 NOTICE[28564] chan_iax2.c: Peer 'wilder' is now TOO 
LAGGED (2025 ms)!
Aug 15 02:33:52 NOTICE[28564] chan_iax2.c: Peer 'wilder' is now TOO 
LAGGED (2027 ms)!
Aug 15 07:08:53 NOTICE[28564] chan_iax2.c: Peer 'prec' is now TOO LAGGED 
(2051 ms)!
Aug 15 08:28:45 NOTICE[28564] chan_iax2.c: Peer 'prec' is now TOO LAGGED 
(2017 ms)!





Alexander Lopez wrote:
> Qualify does what the name implies "qualifies the connection' It pools
> every 60s but it calculates he time it took for the packet to reach the
> end device. If the endpoint has a latentcy > than the qualify parameter,
> * considers the endpoint unreachable.  This does not however address the
> point you made in another post about RINGING before the INVITE. It is
> still possible to have a phone go dead in the 60sec between qualify
> re-checks.
>
> There are several post in history about qualify and it sending LARGE
> amounts of traffic to endpoints. I think it was John Todd that was the
> OP on the subject IIRC.
>
>
>
> SNIP
>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
>