Yup! Remote probes solved a couple challenges: Not only enabling geographically diverse networks, but also removing the need for port mirroring/SPAN within a datacenter. Regards, Calvin Ellison Voice Services Engineer calvin.ellison at voxox.com +1 (213) 285-0555 ----------------------------------------------- voxox.com 9276 Scranton Rd, Suite 200 San Diego, CA 92121 On Fri, Nov 20, 2015 at 1:00 PM, Brian Murray <bmurray at transbeam.com> wrote:
Is anyone clustering VoIPMonitor? Geographically diverse networks with probes reporting up to a single front end?
--------------------------- Brian J Murray
-----Original Message----- From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Calvin Ellison Sent: Friday, November 20, 2015 1:33 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Homer vs VoIPMonitor
Jumping on the VoIPmonitor bandwagon here; they've been more responsive than the average vendor to new feature requests. A memorable interaction went something like this:
Voxox: "We'd like voipmon to do X." (e.g. process RTCP-XR and SIP PUBLISH reports from Polycom, or analyze a proprietary codec)
VoIPMon: "We've had that on our roadmap for a while. Now that a customer (you) has requested X it will be moved to the top of our todo list. We're having a meeting today about upcoming priorities, and will follow up with you tomorrow with a timeline for the feature"
Hard to beat that.
Regards,
Calvin Ellison Voice Services Engineer calvin.ellison at voxox.com +1 (213) 285-0555
----------------------------------------------- voxox.com 9276 Scranton Rd, Suite 200 San Diego, CA 92121
On Fri, Nov 20, 2015 at 8:02 AM, Kidd Filby <kiddfilby at gmail.com> wrote:
I have had experience with Empirix, Palladian and VoIPMonitor. Both Empirix and Palladian are EXPENSIVE and very hard to Engineer correctly to capture all the messaging. An under-engineered system will be VERY annoying and a HUGE waste of money. VoIPMonitor has been extremely valuable, very easy to use, simple to integrate, cost effective and plain old accurate. For the options available today, I wouldn't go with anything other than VoIPMonitor.
Kidd
On Fri, Nov 20, 2015 at 6:46 AM, Daniel-Constantin Mierla <miconda at gmail.com> wrote:
On 20/11/15 14:22, Colton Conor wrote:
I believe you are correct that Homer only does SIP, where VoIPMonitor does both. The latest version of homer capture agent can track rtcp:
https://github.com/sipcapture/captagent
Cheers, Daniel
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Kidd Filby 661.557.5640 (C) http://www.linkedin.com/in/kiddfilby
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops