> -----Original Message-----
> From: snacktime [mailto:snacktime@gmail.com]
> Sent: Thursday, May 12, 2005 5:51 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [Asterisk-Users] UNREACHABLE messages
>
>
> I get these on a consistant basis for most of the providers I have
> configured. Some less than others. I even get it from my phone at
> home to my * box at our data center.
>
> What I'm confused about is why it always shows the ping times at right
> around 2000 ms. That just can't be right. It's always right at
2000
> ms. Never less or more by more than 100 or so.
>
>
> May 12 17:42:23 NOTICE[86152]: chan_iax2.c:6916 socket_read: Peer
> 'voicepulse-out' is now TOO LAGGED (2064 ms)!
> May 12 17:42:33 NOTICE[86152]: chan_iax2.c:6910 socket_read: Peer
> 'voicepulse-out' is now REACHABLE! Time: 64
>
>
The 'qualify' mechanism relies on just one udp packet, which can be lost
in transit. Hence the peer appears to become very lagged. Once it becomes
UNREACHABLE another packet is fired off to test if it's come back in range,
that one makes it through and, voila!, the peer becomes reachable again.
You can turn of the qualify mechanism entirely by setting 'qualify=no',
however the default is 2000ms.
See bug #4192 in http://bugs.digium.com for