Close monitoring of networking everywhere can get pretty time intensive. ;-) Does asterisk (for example) log anomalous events anywhere that you could extract and eyeball? I'd also be surprised if the endpoints (hardware phones) don't have the capability to emit SNMP traps or something.
For wide-angle network monitoring (aka "is my provider dropping all traffic or is latency periodically spiking" - Smokeping is pretty handy. collectd's network plugin has detailed logging of a whole bunch of TCP parameters - that can be useful as well. OpenNMS / cacti / phpweathermap are good if you have a bunch of core switches to watch over, and need detailed data on every single port.... there are a lot of choices available here. --e On Fri, May 8, 2015 at 7:24 AM, Matt Simmons <msimm...@lopsa.org> wrote: > Is this something you could use netflow/sFlow to monitor? > > Also, this looks like an interesting slide deck from someone who has also > thought about this problem: > > http://luca.ntop.org/OpenSourceVoipMonitoring.pdf > > --Matt > > > On Fri, May 8, 2015 at 8:10 AM, Evan Pettrey <jepett...@gmail.com> wrote: >> >> Greetings folks, >> >> I'm currently in the process of trying to put in place better proactive >> monitoring of our VoIP environment and I'm hoping to tap into the wisdom of >> some of you that have more experience with this than myself. >> >> The challenge that we're running into is that there are simply so many >> different things to monitor and it's not something that is on/off or that >> relies solely on hardware utilization to fire off alerts. Currently we >> typically don't know there is a problem until users report that audio on >> their calls is dropping in and out. >> >> Essentially we need to be able to monitor SIP and RTP traffic flow >> end-to-end to be alerted when there is jitter or anything else that could >> affect call quality. This should include (but may not be limited to): >> >> Internal Network - Juniper hardware (I've come across some really good >> VoIP monitoring tools like the one available from Solarwinds but they >> require Cisco hardware) >> >> VoIP Servers - Running Asterisk 1.8 >> >> SIP Trunks - We have limited ability to monitor traffic once it hits our >> SIP trunks so this poses a challenge but it needs to be monitored >> nonetheless >> >> We've set things up like Homer and while that is a great tool for >> retroactively troubleshooting issues reported it does not do much to alert >> us to problems proactively. >> >> >> Any guidance here would be greatly appreciated. Thanks in advance! >> >> >> Best, >> Evan >> >> >> _______________________________________________ >> Discuss mailing list >> Discuss@lists.lopsa.org >> https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss >> This list provided by the League of Professional System Administrators >> http://lopsa.org/ >> > > > _______________________________________________ > Discuss mailing list > Discuss@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
