Lync Call on MPLS network the voice quality is bad

Any advice for below ping result.?

Reply from 192.168.1.100: bytes=32 time=89ms TTL=59
Reply from 192.168.1.100: bytes=32 time=77ms TTL=59
Reply from 192.168.1.100: bytes=32 time=87ms TTL=59
Reply from 192.168.1.100: bytes=32 time=119ms TTL=59
Reply from 192.168.1.100: bytes=32 time=86ms TTL=59
Reply from 192.168.1.100: bytes=32 time=96ms TTL=59
Reply from 192.168.1.100: bytes=32 time=85ms TTL=59
Request timed out.
Reply from 192.168.1.100: bytes=32 time=94ms TTL=59
Reply from 192.168.1.100: bytes=32 time=82ms TTL=59
Reply from 192.168.1.100: bytes=32 time=94ms TTL=59
Request timed out.
Reply from 192.168.1.100: bytes=32 time=107ms TTL=59
Reply from 192.168.1.100: bytes=32 time=77ms TTL=59
Reply from 192.168.1.100: bytes=32 time=81ms TTL=59
Reply from 192.168.1.100: bytes=32 time=100ms TTL=59
Reply from 192.168.1.100: bytes=32 time=88ms TTL=59
Reply from 192.168.1.100: bytes=32 time=88ms TTL=59
Reply from 192.168.1.100: bytes=32 time=76ms TTL=59
Reply from 192.168.1.100: bytes=32 time=94ms TTL=59
Reply from 192.168.1.100: bytes=32 time=94ms TTL=59
Reply from 192.168.1.100: bytes=32 time=90ms TTL=59
Reply from 192.168.1.100: bytes=32 time=71ms TTL=59
Reply from 192.168.1.100: bytes=32 time=64ms TTL=59
Reply from 192.168.1.100: bytes=32 time=66ms TTL=59
Reply from 192.168.1.100: bytes=32 time=68ms TTL=59
Reply from 192.168.1.100: bytes=32 time=120ms TTL=59
Reply from 192.168.1.100: bytes=32 time=49ms TTL=59
Reply from 192.168.1.100: bytes=32 time=34ms TTL=59
Reply from 192.168.1.100: bytes=32 time=80ms TTL=59
Reply from 192.168.1.100: bytes=32 time=41ms TTL=59
Reply from 192.168.1.100: bytes=32 time=31ms TTL=59
Reply from 192.168.1.100: bytes=32 time=27ms TTL=59
Reply from 192.168.1.100: bytes=32 time=43ms TTL=59
Reply from 192.168.1.100: bytes=32 time=74ms TTL=59
Reply from 192.168.1.100: bytes=32 time=36ms TTL=59
Reply from 192.168.1.100: bytes=32 time=32ms TTL=59
Reply from 192.168.1.100: bytes=32 time=28ms TTL=59
Reply from 192.168.1.100: bytes=32 time=39ms TTL=59
Reply from 192.168.1.100: bytes=32 time=38ms TTL=59
Reply from 192.168.1.100: bytes=32 time=25ms TTL=59
Reply from 192.168.1.100: bytes=32 time=26ms TTL=59
Reply from 192.168.1.100: bytes=32 time=31ms TTL=59
Reply from 192.168.1.100: bytes=32 time=27ms TTL=59
Reply from 192.168.1.100: bytes=32 time=31ms TTL=59
Reply from 192.168.1.100: bytes=32 time=26ms TTL=59
Reply from 192.168.1.100: bytes=32 time=30ms TTL=59
Reply from 192.168.1.100: bytes=32 time=26ms TTL=59
Reply from 192.168.1.100: bytes=32 time=41ms TTL=59
Reply from 192.168.1.100: bytes=32 time=39ms TTL=59
Reply from 192.168.1.100: bytes=32 time=29ms TTL=59
Reply from 192.168.1.100: bytes=32 time=29ms TTL=59
Reply from 192.168.1.100: bytes=32 time=29ms TTL=59
Reply from 192.168.1.100: bytes=32 time=57ms TTL=59
Reply from 192.168.1.100: bytes=32 time=51ms TTL=59
Reply from 192.168.1.100: bytes=32 time=76ms TTL=59
Reply from 192.168.1.100: bytes=32 time=99ms TTL=59
Reply from 192.168.1.100: bytes=32 time=52ms TTL=59
Reply from 192.168.1.100: bytes=32 time=73ms TTL=59
Reply from 192.168.1.100: bytes=32 time=94ms TTL=59
Reply from 192.168.1.100: bytes=32 time=95ms TTL=59
Reply from 192.168.1.100: bytes=32 time=46ms TTL=59
Reply from 192.168.1.100: bytes=32 time=49ms TTL=59
Reply from 192.168.1.100: bytes=32 time=43ms TTL=59
Reply from 192.168.1.100: bytes=32 time=63ms TTL=59
Reply from 192.168.1.100: bytes=32 time=27ms TTL=59
Reply from 192.168.1.100: bytes=32 time=26ms TTL=59
Reply from 192.168.1.100: bytes=32 time=37ms TTL=59
Reply from 192.168.1.100: bytes=32 time=47ms TTL=59
Reply from 192.168.1.100: bytes=32 time=28ms TTL=59
Reply from 192.168.1.100: bytes=32 time=34ms TTL=59
Reply from 192.168.1.100: bytes=32 time=28ms TTL=59
Reply from 192.168.1.100: bytes=32 time=37ms TTL=59
Reply from 192.168.1.100: bytes=32 time=31ms TTL=59
Reply from 192.168.1.100: bytes=32 time=34ms TTL=59
Reply from 192.168.1.100: bytes=32 time=33ms TTL=59
Reply from 192.168.1.100: bytes=32 time=26ms TTL=59
Reply from 192.168.1.100: bytes=32 time=31ms TTL=59
Reply from 192.168.1.100: bytes=32 time=25ms TTL=59
Reply from 192.168.1.100: bytes=32 time=27ms TTL=59

Latency is not good, some time have time out.

How to improve the voice quality? QOS , Tell MPLS vendor to do QOS?

How to test the UDP Port? Lync Monitor report doesn't have QOE report when the call is come from MPLS network. The MPLS firewall blocked?

Thanks.

August 21st, 2015 1:31pm

Yeah, your latency is inconsistent, 100ms isn't the worst if it's stable, but if one packet arrives in 25ms and the other in 100ms, you can get packets out of order and jitter.  Regardless, if voice traffic is being carried over this line, you'll need QoS implemented otherwise you'll never be able to guarantee any sort of quality.

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 5:53pm

How to improve the voice quality? QOS , Tell MPLS vendor to do QOS? Lync Monitor report doesn't have QOE report when the call is come from MPLS network. 

Look at the mediation leg of the Lync monitoring report for the calls.

=================================================

How to test the UDP Port?

http://www.microsoft.com/en-us/download/details.aspx?id=24009

====================================================

August 30th, 2015 3:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics