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 HOMER DEV TEAM QXIP - Network Engineering http://qxip.net
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
HOMER DEV TEAM QXIP - Network Engineering http://qxip.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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
HOMER DEV TEAM QXIP - Network Engineering http://qxip.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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> 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> 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
HOMER DEV TEAM QXIP - Network Engineering http://qxip.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Colton ? it?s all explained here in extreme detail - http://community.polycom.com/t5/Polycom-Technology-Partners/Telchemy-SQmedia... Your application is one that we are quite intimate with. Let me know if you have any questions after reading through the material- -anthony 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: 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 <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 HOMER DEV TEAM QXIP - Network Engineering http://qxip.net _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
Colton, The configuration steps are quite simple and outlined here: http://documents.polycom.com/documents/voice/unified-communications-software... You basically only have to enable the feature and specify the collector for the PUBLISH or NOTIFY RFC 6035 messages the phone will start sending, each containing all the QoS metrics the device can generate (this changes across firmwares/versions) including the MOS score where available in final reports, painting an accurate picture of the user experience and/or broadband quality without additional probing or remote estimations. Our platforms OSS HOMER & PCAPture both support acting as RTCP-XR VQ Publish report collector and parser with full correlation to the originating SIP sessions and extracting the values for global statistics. Kind Regards, Lorenzo Mangani QXIP BV - Capture Engineering Amsterdam, The Netherlands
Hello Colton, At the risk of overwhelming you with good advice, ;) ;) Here is a screenshot of the relevant page from the Polycom manual ? if this email system preserves attachments As you would expect, Palladion/COM has for many years been able to act as the VQ Collector and correlates those streams with the other RTP stream/legs captured natively by the COM probe or by RTCP Many Thanks & Best Regards, Richard From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Lorenzo Mangani <lorenzo.mangani at gmail.com> Date: Tuesday, December 1, 2015 at 9:56 AM To: Colton Conor <colton.conor at gmail.com> Cc: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: Re: [VoiceOps] Homer vs VoIPMonitor Colton, The configuration steps are quite simple and outlined here: http://documents.polycom.com/documents/voice/unified-communications-software... You basically only have to enable the feature and specify the collector for the PUBLISH or NOTIFY RFC 6035 messages the phone will start sending, each containing all the QoS metrics the device can generate (this changes across firmwares/versions) including the MOS score where available in final reports, painting an accurate picture of the user experience and/or broadband quality without additional probing or remote estimations. Our platforms OSS HOMER & PCAPture both support acting as RTCP-XR VQ Publish report collector and parser with full correlation to the originating SIP sessions and extracting the values for global statistics. Kind Regards, Lorenzo Mangani QXIP BV - Capture Engineering Amsterdam, The Netherlands _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Let's just hope other commercially motivated folks on the list refrain from sending a 300KB attachment as an excuse to slip in their product name... please :) =Marco On Tue, Dec 1, 2015 at 5:41 PM, Richard Jobson <richard at teraquant.com> wrote:
Hello Colton,
At the risk of overwhelming you with good advice, ;) ;) Here is a screenshot of the relevant page from the Polycom manual ? if this email system preserves attachments
As you would expect, Palladion/COM has for many years been able to act as the VQ Collector and correlates those streams with the other RTP stream/legs captured natively by the COM probe or by RTCP
Many Thanks & Best Regards,
Richard
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Lorenzo Mangani <lorenzo.mangani at gmail.com> Date: Tuesday, December 1, 2015 at 9:56 AM To: Colton Conor <colton.conor at gmail.com> Cc: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: Re: [VoiceOps] Homer vs VoIPMonitor
Colton,
The configuration steps are quite simple and outlined here:
http://documents.polycom.com/documents/voice/unified-communications-software...
You basically only have to enable the feature and specify the collector for the PUBLISH or NOTIFY RFC 6035 messages the phone will start sending, each containing all the QoS metrics the device can generate (this changes across firmwares/versions) including the MOS score where available in final reports, painting an accurate picture of the user experience and/or broadband quality without additional probing or remote estimations. Our platforms OSS HOMER & PCAPture both support acting as RTCP-XR VQ Publish report collector and parser with full correlation to the originating SIP sessions and extracting the values for global statistics.
Kind Regards,
Lorenzo Mangani QXIP BV - Capture Engineering Amsterdam, The Netherlands
_______________________________________________ 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
participants (5)
-
admin＠marcoteixeira.com -
anthony.caiozzo＠telchemy.com -
colton.conor＠gmail.com -
lorenzo.mangani＠gmail.com -
richard＠teraquant.com