<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thank you for all the suggestions will definitely check out Homer & Voip Monitor.</p>
<p>I really just need to be sure there are no issues on my end (server side) so that I can confidently tell the client its their home network and why. </p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 5/23/2017 10:58 PM, Richard Jobson wrote:<br>
</div>
<blockquote type="cite" cite="mid:564118AE-5796-46AF-A941-7DD62442247C@teraquant.com">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:"Apple Color Emoji";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">“Horses for courses “
</span><span style="font-size:11.0pt;font-family:"Apple Color
Emoji"">☺</span><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"><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 <a class="moz-txt-link-rfc2396E" href="mailto:voiceops-bounces@voiceops.org">
<voiceops-bounces@voiceops.org></a> on behalf of Mark Wiater <a class="moz-txt-link-rfc2396E" 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 class="moz-txt-link-rfc2396E" 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">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 class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">
VoiceOps@voiceops.org</a> <a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">
https://puck.nether.net/mailman/listinfo/voiceops</a> <o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</body>
</html>