[VoiceOps] Homer vs VoIPMonitor

Anthony Caiozzo anthony.caiozzo at telchemy.com
Tue Dec 1 11:52:46 EST 2015

Colton – it’s all explained here in extreme detail - http://community.polycom.com/t5/Polycom-Technology-Partners/Telchemy-SQmediator-Next-Generation-Performance-Management/ba-p/27628


Your application is one that we are quite intimate with.


Let me know if you have any questions after reading through the material-




Anthony Caiozzo

Telchemy -  <http://www.telchemy.com> www.telchemy.com 

m: 617-312-5189 f: 678-387-3008

e:  <mailto:anthony.caiozzo at telchemy.com> anthony.caiozzo at telchemy.com

support: 1-866-TELCHEMY or  <http://www.telchemy.com/custportal> www.telchemy.com/custportal to open a ticket

Skype: acaiozzo


From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton Conor
Sent: Tuesday, December 1, 2015 11:31 AM
To: Lorenzo Mangani <lorenzo.mangani at gmail.com>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] Homer vs VoIPMonitor


How specifically does this work with Poylcom VVX phones that have the VQMon license? I know the VVX 500 and VXX 600 come with the license by default, but the lower part of the line you have to purchase the VQMON license which we have that is like an additional $2 per phone one time cost. 


I guess I am confused

1. Not sure how to enabled VQMon

2. What VQMon actually reports upstream once enabled

3. If what is reported upstream is even useful. I assume it would be since most of our customers are bring your own broadband type customers, so we don't have a managed CPE onsite to give QOS stats to know what they are actually hearing.




On Tue, Dec 1, 2015 at 2:01 AM, Lorenzo Mangani <lorenzo.mangani at gmail.com <mailto:lorenzo.mangani at gmail.com> > wrote:

Hi Colton,


That was indeed a typo - my apologies. Both platforms support RTCP-XR and VQ PUBLISH reports. In Homer, they can be handled and forwarded by a capture agent then parsed in Kamailio [ if(method == "PUBLISH" && hash_body("application/vq-rtcpxr")) ... ] while PCAPTURE can handle them at the core directly.

Kind Regards,


Lorenzo Mangani

QXIP BV - Capture Engineering

Amsterdam, The Netherlands



On Tue, Dec 1, 2015 at 5:04 AM, Colton Conor <colton.conor at gmail.com <mailto:colton.conor at gmail.com> > wrote:



What about RTCP-XR with Homer? Or is RTCP-XR a paid for feature only working with PCAPture? Above you mentioned RTCP-XT, but I assume you mean to type RTCP-XR as I have not heard of RTCP-XT. 


On Fri, Nov 27, 2015 at 1:36 PM, Lorenzo Mangani <lorenzo.mangani at gmail.com <mailto:lorenzo.mangani at gmail.com> > wrote:

Interesting thread! 


I'm one of the authors of Homer and PCAPture, just dropping in to extend the subject with more details for those interested and by invite of some of our users on the list.


First of all Homer is free and fully open-source, while VoipMonitor is a paid application and should be best compared with our commercial product PCAPture (http://pcapture.com) which provides advanced features and support for multiple signaling protocols with programmable correlation, passive RTP Analysis agents with pseudo-MOS, RTCP-XT and RTP-Stats collection, Injection of arbitrary rows (read syslog or CDRs, QoS) with a correlation IDs, Geo-Location, Fraud Detection with LCR/ENUM backend, Lawful Interception and much more in terms of scalability and geo-redundancy - All while retaining full compatibility with agents using the encapsulation protocol HEP/EEP which is natively supported in Kamailio, OpenSIPS, Asterisk, Freeswitch as well as tools such as sipgrep, sngrep and nprobe making our solution quite transparent to integrate with or without port spanning/mirroring when needed (read cloud) and able to fetch key internal data from the platforms it taps natively. 


This being said - Homer delivers plenty of value and simply addresses media monitoring differently without storing and analyzing pcap files, instead relying on external light-weight analyzers sending customizable QoS reports at a fraction of the bandwidth, storage and capex cost, with full recording being an on-demand feature instead of a default. Also our user interfaces and user experiences are radically different in approach and I'm sure each satisfies a different audience, without prejudice. I suggest to give both a try before making a decision ;)


I hope this (inevitably biased) extension helps anyone evaluating their options more clearly, our team is always available to answer any questions!


Kind Regards,

Lorenzo Mangani



QXIP - Network Engineering




VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20151201/21b59e3e/attachment.html>

More information about the VoiceOps mailing list