Hi All,
I'm wondering if anyone can share any info on why I frequently get peer
timeouts like below, and receive 489 messages from another A*k server on
the same LAN.
For the peers, we've one L2 switch. ICMP is <1ms. The CPU of the main
A*k server is usually < 2%. So I can't see why we'd get such large
delays. The phones are all Cisco 7940s (SIP 2xx)
The 489 originate from another A*k server that my boss wants to run.
Our A*k is 1.2.18, and his is 1.4.x
I'm not sure if either of these messages will actually cause issues, how
I can debug them further?
Any ideas?
Adrian
Jun 19 09:24:45 NOTICE[6632]: chan_sip.c:10029 handle_response_peerpoke:
Peer '227' is now TOO LAGGED! (204ms / 200ms)
Jun 19 09:24:55 NOTICE[6632]: chan_sip.c:10023 handle_response_peerpoke:
Peer '227' is now REACHABLE! (148ms / 200ms)
Jun 19 09:24:59 NOTICE[6632]: chan_sip.c:11777 sip_poke_noanswer: Peer
'464' is now UNREACHABLE! Last qualify: 101
Jun 19 09:24:59 NOTICE[6632]: chan_sip.c:10029 handle_response_peerpoke:
Peer '254' is now TOO LAGGED! (214ms / 200ms)
-- Got SIP response 489 "Bad event" back from 192.168.3.10
Jun 19 09:25:09 NOTICE[6632]: chan_sip.c:10023 handle_response_peerpoke:
Peer '254' is now REACHABLE! (198ms / 200ms)
Jun 19 09:25:29 NOTICE[6632]: chan_sip.c:11777 sip_poke_noanswer: Peer
'438' is now UNREACHABLE! Last qualify: 128
-- Registered SIP '442' at 192.168.50.16 port 32768 expires 3600
-- Saved useragent "Nokia RM-92 V 4.0632.0.38" for peer 442
-- Registered SIP '464' at 192.168.50.2 port 47242 expires 3600
Jun 19 09:25:36 NOTICE[6632]: chan_sip.c:10023 handle_response_peerpoke:
Peer '464' is now REACHABLE! (73ms / 2000ms)
