[VoiceOps] Homer vs VoIPMonitor

Lorenzo Mangani lorenzo.mangani at gmail.com
Tue Dec 1 03:01:35 EST 2015

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> wrote:

> Lorenzo,
> 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> 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
>> http://qxip.net
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20151201/5326d840/attachment.html>

More information about the VoiceOps mailing list