Asterisk Users, I am running Asterisk 1.2.13 on Debian Etch with McLeodUSA's T1 service. I have two Netgear switches on my T1 router, one for VOIP and another for data. I use a gigabit switch for all VOIP and a regular 10/100Mbps switch for all data. This morning I saw this message a few times on the Asterisk command line. The lagged cause garbled phone calls. Is my network to slow? Or is there something else going on? Aug 9 09:40:21 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer 'netlogic' is now TOO LAGGED! (1050ms / 1000ms) Aug 9 09:40:55 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer 'netlogic' is now REACHABLE! (17ms / 1000ms) Aug 9 09:41:56 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer 'netlogic' is now TOO LAGGED! (1017ms / 1000ms) Aug 9 09:42:17 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer 'netlogic' is now REACHABLE! (17ms / 1000ms) Aug 9 09:48:18 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer 'netlogic' is now TOO LAGGED! (1017ms / 1000ms) Aug 9 09:48:28 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer 'netlogic' is now REACHABLE! (17ms / 1000ms) Aug 9 09:50:29 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer 'netlogic' is now TOO LAGGED! (1017ms / 1000ms) Aug 9 09:50:39 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer 'netlogic' is now REACHABLE! (17ms / 1000ms) Aug 9 09:56:41 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer 'netlogic' is now TOO LAGGED! (1018ms / 1000ms) Aug 9 09:56:51 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer 'netlogic' is now REACHABLE! (17ms / 1000ms) Aug 9 10:01:52 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer 'netlogic' is now TOO LAGGED! (1017ms / 1000ms) Aug 9 10:02:02 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer 'netlogic' is now REACHABLE! (17ms / 1000ms) Best Regards, John _________________________________________________________________ A new home for Mom, no cleanup required. All starts here. http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
On Thu, 9 Aug 2007, John Meksavan wrote:> Is my network to slow? Or is there something else going on?It sounds like there may have been a temporary period of high utilisation that created this distortion. However, in general, the Asterisk 'qualify' mechanism (which consists of a SIP OPTIONS ping, nothing more) is not a terribly reliable metric of network throughput or performance, especially when constrained to extremely low latency. Nor does Asterisk always accurately determine that a peer is "UNREACHABLE" only when it is, in fact, UNREACHABLE. I encourage you to set the qualify= value for each peer in sip.conf very high, or otherwise omit the setting entirely. -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : +1-678-954-0670 Direct : +1-678-954-0671
I have the same debian and asterisk version combo running in more than one location. Some are T1 and some are in data centers. There have been times when I got such messages and some simple ping/traceroute testing showed obvious problems at my end or the provider end. Problems at the provider end were confirmed by testing from multiple locations. John Meksavan wrote:>Asterisk Users, > > I am running Asterisk 1.2.13 on Debian Etch with McLeodUSA's T1 service. >I have two Netgear switches on my T1 router, one for VOIP and another for >data. > > I use a gigabit switch for all VOIP and a regular 10/100Mbps switch for >all data. This morning I saw this message a few times on the Asterisk >command line. The lagged cause garbled phone calls. > > Is my network to slow? Or is there something else going on? > >Aug 9 09:40:21 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer >'netlogic' is now TOO LAGGED! (1050ms / 1000ms) >Aug 9 09:40:55 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer >'netlogic' is now REACHABLE! (17ms / 1000ms) >Aug 9 09:41:56 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer >'netlogic' is now TOO LAGGED! (1017ms / 1000ms) >Aug 9 09:42:17 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer >'netlogic' is now REACHABLE! (17ms / 1000ms) >Aug 9 09:48:18 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer >'netlogic' is now TOO LAGGED! (1017ms / 1000ms) >Aug 9 09:48:28 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer >'netlogic' is now REACHABLE! (17ms / 1000ms) >Aug 9 09:50:29 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer >'netlogic' is now TOO LAGGED! (1017ms / 1000ms) >Aug 9 09:50:39 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer >'netlogic' is now REACHABLE! (17ms / 1000ms) >Aug 9 09:56:41 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer >'netlogic' is now TOO LAGGED! (1018ms / 1000ms) >Aug 9 09:56:51 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer >'netlogic' is now REACHABLE! (17ms / 1000ms) >Aug 9 10:01:52 NOTICE[6395]: chan_sip.c:9929 handle_response_peerpoke: Peer >'netlogic' is now TOO LAGGED! (1017ms / 1000ms) >Aug 9 10:02:02 NOTICE[6395]: chan_sip.c:9923 handle_response_peerpoke: Peer >'netlogic' is now REACHABLE! (17ms / 1000ms) > > > >Best Regards, >John > >_________________________________________________________________ >A new home for Mom, no cleanup required. All starts here. >http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us > > >_______________________________________________ >--Bandwidth and Colocation Provided by http://www.api-digital.com-- > >asterisk-users mailing list >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >