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 <[email protected]> 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 <[email protected]> on behalf of Lorenzo > Mangani <[email protected]> > Date: Tuesday, December 1, 2015 at 9:56 AM > To: Colton Conor <[email protected]> > Cc: "[email protected]" <[email protected]> > 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-ucs/5-0-1/administrator-guide/set-phone-audio-features > > 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 > [email protected] https://puck.nether.net/mailman/listinfo/voiceops > > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
