<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>It all depends on where the problem is being introduced. If the speech quality impairment is associated with the endpoint itself or any part of their headset gear, cabling etc. then monitoring on the IP packet network will not analyze this. With a monitoring system, you might be able to capture the RTP and listen to it. With an expert ear, that might ascertain the source of the problem<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>In order to measure truly end-to-end from the analog interface of the headset [or even from an acoustic interface if necessary], normal practice is to transmit an audio speech file into the analog interface of the endpoint and do an Intrusive speech quality management. The standard is PESQ or more latterly POLQA.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>POLQA Is an ITU-T standard, has the benefit of over 20 years collective research and development from over 6 research labs, combined with testing against a database of over 850,000 subjective assessments. When measured accurately, it has 97% correlation with human subjective experience i.e. MOS [ITU-T recommendation P.800] and 1 or 2 such test solutions will also give you analysis that assists you determine the root cause of the impairment<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-family:Calibri;color:black'>From: </span></b><span style='font-family:Calibri;color:black'>VoiceOps <voiceops-bounces@voiceops.org> on behalf of "Glenn Geller (VDOPh)" <ggeller@vdo-ph.com><br><b>Date: </b>Tuesday, May 23, 2017 at 1:52 PM<br><b>To: </b>Mark Wiater <mark.wiater@greybeam.com><br><b>Cc: </b>"Voiceops.org" <voiceops@voiceops.org><br><b>Subject: </b>Re: [VoiceOps] VoIP Testing<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>+100 for voipmonitor <o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'>Thanks, Glenn (Mobile)<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>On May 23, 2017 12:49 PM, "Mark Wiater" <<a href="mailto:mark.wiater@greybeam.com">mark.wiater@greybeam.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal style='margin-left:.5in'> From time to time we have some remote clients who are facing voice quality issues on their endpoints and I have no real good way of troubleshooting or pin pointing the problem.<o:p></o:p></p></blockquote></div><p class=MsoNormal style='margin-left:.5in'>While it's not completely free, I couldn't live without voipmonitor for this very use. I install a sensor in the client network on a mirror port or on the phone system and get to see exactly what they see, from a voip perspective.<br><br>The collection software is open source but the gui is invaluable.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><br><br><br><br>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div></div></div><p class=MsoNormal style='margin-left:.5in'>_______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops <o:p></o:p></p></div></body></html>