Andrew,<div><br></div><div>I'd put Wireshark on a PC behind one or more of the phones reporting the problem. It can give you some pretty good RTP statistics regarding delay and jitter. You can see how many RTP packets arrived in more or less than the 20 msec expected gap between packets, and how many might have been missed altogether.</div>
<div><br></div><div>A good stream will show packets coming in at even 20 msec intervals with consecutive sequence numbers.</div><div><br></div><div>Right click on the RTP packet in Wireshark and go to something like "Stream Analysis" or highlight the packet and in the top menu go to "Statistics -> RTP -> Stream Analysis".</div>
<div><br></div><div>Look for out of order sequence numbers, gaps bigger or smaller than 20 msecs, or big gaps in sequence numbers. If you can spot a particular direction of the stream that looks goofed up you can identify all of the ingress and egress interfaces between the two endpoints in the call and look closer.</div>
<div><br></div><div>PhoneA -- Switch 1 -- Switch 2 -- Router 1 --- Router 2 -- Switch 3 - Switch 4 -- Phone B</div><div><br></div><div>Start with captures at Phone A and Phone B. If you spot problems, bisect the link and capture between Router 1 and Router 2 to see which half is introducing problems. Repeat.</div>
<div><br></div><div>If on the other hand you don't see any problem in the packet capture, then maybe the phones are calculating something wrong.</div><div><br></div><div>For the Null CMR values, make sure you reset the phones. See if they start populating CMR data after that.</div>
<div><br><br><div class="gmail_quote">On Wed, Jul 8, 2009 at 11:57 AM, Andrew <span dir="ltr"><<a href="mailto:voiptech@gmx.de">voiptech@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Dear All,<br>
I am currently troubleshooting issues with very low MOS values being displayed on the IP Phone statistics. While the customer isn’t noticing any issues with voice quality, I’ve been asked nevertheless to attempt to resolve the issue.<br>
There are around 20 IP Phones (7940/7961) in use on the site, and at any given time 2 -6 of them can be displaying low values, usually the same culprits every time. The phones are using the G711 codec and the switches are connected (with 1 exception) via gigabit links.<br>
The interface counters on the phones and the switches between the phones, gateway and call manager (retracing the entire path) don’t have any more than a normal volume of errors (>1%). QOS is configured on all interfaces.<br>
We made test calls both internally and externally with 5 separate phones attached to each of the switches, and every time the MOS results were between 4.48 and 4.5.<br>
Values for the phones with issues look like:<br>
<br>
MOS LQK 2.0000 Avg MOS LQK 2.2219 Min MOS LQK 2.0000 Max MOS LQK 4.1779<br>
MOS LQK Version0.95<br>
Cumulative Conceal Ratio 0.5963 Interval Conceal Ratio 0.0860 Max Conceal Ratio 1.0000<br>
Conceal Secs 140 Severely Conceal Secs 133<br>
Latency 0 Max. Jitter 19<br>
<br>
However at some point the values are going back to the same low values. We enabled CMRs for the calls to determine if specific calls were showing the poor values, however for all of the calls being logged the media info is still carrying only the values “null”.<br>
<br>
Does anyone have any advice on how we could try an resolve this issue, or if not the MOS issue than the null values for the CMR records?<br>
<br>
Thanks for any help anyone can offer,<br>
<br>
Andrew Cook<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br></div>