[Asterisk-Users] Qualify time +2000ms?

Jonathan k. Creasy jonathan at bluegrass.net
Mon Aug 22 07:06:02 MST 2005


I have some netweb 302 phones which we used when we first started
evaluating Asterisk. These phones would do this all the time. It seemed
to have nothing to do with the network ping time. I never really did
check in to what was going on because it only happened with those phones
and we don't use those anymore. 

They were attached to the asterisk server via a 100mb LAN and 1ms was
the highest latency "ping" would ever show. 

-Jonathan

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of MF Hulber
Sent: Monday, August 22, 2005 9:47 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [Asterisk-Users] Qualify time +2000ms?

Although I'm convinced that Broadvoice doesn't have the most stable of 
ping times, it seems like I get ping results that are approximately the 
ping time +2000ms at times.  Has anyone experienced this problem with 
qualify on a SIP connection before?

So here, was the ping 20ms or 2020ms as reported?

Aug 22 06:39:49 NOTICE[6964]: chan_sip.c:8481 handle_response_peerpoke: 
Peer 'broadvoice-in' is now TOO LAGGED! (2020ms / 2000ms)
Aug 22 06:39:59 NOTICE[6964]: chan_sip.c:8475 handle_response_peerpoke: 
Peer 'broadvoice-in' is now REACHABLE! (20ms / 2000ms)

Aug 22 09:38:34 NOTICE[6964]: chan_sip.c:8481 handle_response_peerpoke: 
Peer 'broadvoice-in' is now TOO LAGGED! (2025ms / 2000ms)
Aug 22 09:38:44 NOTICE[6964]: chan_sip.c:8475 handle_response_peerpoke: 
Peer 'broadvoice-in' is now REACHABLE! (19ms / 2000ms)
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users



More information about the asterisk-users mailing list