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