<html xmlns:v="urn:schemas-microsoft-com:vml" 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 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;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Feeling the need to jump in here... Telchemy’s VQmon technology does integrate acoustic effects into its quality prediction…. When integrated into audio and video endpoints – like Polycom, Cisco, Yealink and Avaya have done (and whose technology I believe a number of list subscribers leverage on a daily basis) - VQMon incorporates analog metrics including signal, noise, and echo levels, which are not available using mid-stream analysis alone. <o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></a></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Which then obviously relieves you from the need to listen to every / all calls. It really is the better mousetrap.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Here’s a writeup we did a long while back on this: </span></span><a href="http://www.lovemytool.com/blog/2008/02/telchemy-1.html"><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>http://www.lovemytool.com/blog/2008/02/telchemy-1.html</span></span><span style='mso-bookmark:_MailEndCompose'></span></a><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Happy to answer more questions – if there are any.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>-anthony<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><span style='mso-bookmark:_MailEndCompose'>Anthony Caiozzo<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><span style='mso-bookmark:_MailEndCompose'>Telchemy - </span><a href="http://www.telchemy.com"><span style='mso-bookmark:_MailEndCompose'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>www.telchemy.com</span></span><span style='mso-bookmark:_MailEndCompose'></span></a><span style='mso-bookmark:_MailEndCompose'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><span style='mso-bookmark:_MailEndCompose'>m: 617-312-5189 f: 678-387-3008<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><span style='mso-bookmark:_MailEndCompose'>e: </span><a href="mailto:anthony.caiozzo@telchemy.com"><span style='mso-bookmark:_MailEndCompose'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>anthony.caiozzo@telchemy.com</span></span><span style='mso-bookmark:_MailEndCompose'></span></a><span style='mso-bookmark:_MailEndCompose'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><span style='mso-bookmark:_MailEndCompose'>support: 1-866-TELCHEMY or </span><a href="http://www.telchemy.com/custportal"><span style='mso-bookmark:_MailEndCompose'>www.telchemy.com/custportal</span><span style='mso-bookmark:_MailEndCompose'></span></a><span style='mso-bookmark:_MailEndCompose'> to open a ticket<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:-.25in'><span style='mso-bookmark:_MailEndCompose'>Skype: acaiozzo<o:p></o:p></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><span style='mso-bookmark:_MailEndCompose'></span><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> VoiceOps [mailto:voiceops-bounces@voiceops.org] <b>On Behalf Of </b>Richard Jobson<br><b>Sent:</b> Tuesday, May 23, 2017 10:58 PM<br><b>To:</b> Mark Wiater <mark.wiater@greybeam.com>; Voiceops.org <voiceops@voiceops.org><br><b>Subject:</b> Re: [VoiceOps] VoIP Testing<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>So assuming it’s not packet loss or jitter, it’s a problem associated with the endpoint? No tool monitoring packets is going to <i><u>alert</u></i> you to this problem because it only appears in the audio . you could take the time to listen to every suspect call. Or you could take your customers’ time and ask him to specify which calls are problematic and listen only to those<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>What does audio sound like if a softphone is squeezed on CPU resources? Or maybe it’s echo or maybe it’s static or maybe it’s problems associated with Wi-Fi or maybe it’s cabling or connectors? If You can ascertain the root cause simply by listing to the audio, then that’s fine.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>It depends on the objectives. If all you need to do is to be able to point to suspect equipment and tell the customer to replace it and move on, then above is fine. If you need to isolate this specific systematic problem in a population of endpoints, demonstrate it to external vendor or partner or provide best practices for call center Endpoints and setup, then perhaps more investment in troubleshooting to root cause might be justified.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>“Horses for courses “ </span><span style='font-size:11.0pt;font-family:"Segoe UI Emoji",sans-serif'>☺</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><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",sans-serif;color:black'>From: </span></b><span style='font-family:"Calibri",sans-serif;color:black'>VoiceOps <<a href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a>> on behalf of Mark Wiater <<a href="mailto:mark.wiater@greybeam.com">mark.wiater@greybeam.com</a>><br><b>Date: </b>Tuesday, May 23, 2017 at 2:37 PM<br><b>To: </b>"Voiceops.org" <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>><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><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>On 5/23/2017 4:18 PM, Richard Jobson wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>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</span><o:p></o:p></p></blockquote><p class=MsoNormal style='margin-left:.5in'><br>Of course you're right. But heck, if the problem doesn't manifest at the monitoring system in the clients local network, then you kinda know where the problem is, right? :-)<br><br>I don't argue your points about POLQA and such, but voipmonitor makes it pretty easy for me to identify root causes of client complaints kinda quickly. <br><br><br>_______________________________________________ VoiceOps mailing list <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a> <a href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a> <o:p></o:p></p></div></body></html>