@cramermp wrote:
Hi all.
I made this post/log monitor a while ago to monitor my asterisk logs via email:
Since then, the rest of my team is wondering if we're chasing ghosts. We get disconnected peers every day, but people aren't complaining about poor audio quality or dropped calls or anything, and running some UDP tests over the network we get perfect results. The peers that get disconnected seem random... there's no common hardware involved except "all the switches." And nobody complains about it, sometimes its in the middle of the night.
So if I'm seeing these errors, how worried should I be? Should I be pushing my network guys to figure out whats going wrong, or does this sort of thing just happen to everyone?
[2016-09-23 10:02:47] NOTICE[2258] chan_sip.c: Peer '138' is now UNREACHABLE! Last qualify: 85 [2016-09-23 10:02:47] NOTICE[2258] chan_sip.c: Peer '121' is now UNREACHABLE! Last qualify: 35 [2016-09-23 10:02:47] NOTICE[2258] chan_sip.c: Peer '126' is now UNREACHABLE! Last qualify: 83 [2016-09-23 10:02:47] NOTICE[2258] chan_sip.c: Peer '130' is now UNREACHABLE! Last qualify: 80 [2016-09-23 10:02:47] NOTICE[2258] chan_sip.c: Peer '117' is now UNREACHABLE! Last qualify: 80 [2016-09-23 10:02:57] NOTICE[2258] chan_sip.c: Peer '121' is now Reachable. (12ms / 2000ms) [2016-09-23 10:02:57] NOTICE[2258] chan_sip.c: Peer '117' is now Reachable. (74ms / 2000ms) [2016-09-23 10:02:57] NOTICE[2258] chan_sip.c: Peer '126' is now Reachable. (75ms / 2000ms) [2016-09-23 10:02:57] NOTICE[2258] chan_sip.c: Peer '138' is now Reachable. (82ms / 2000ms) [2016-09-23 10:02:57] NOTICE[2258] chan_sip.c: Peer '130' is now Reachable. (96ms / 2000ms) [2016-09-27 09:42:25] NOTICE[2258] chan_sip.c: Peer '119' is now Lagged. (3183ms / 2000ms) [2016-09-27 09:42:36] NOTICE[2258] chan_sip.c: Peer '119' is now Reachable. (90ms / 2000ms)[
Posts: 1
Participants: 1