Call Quality of Service - Jitter

[Suporte JustGroup]

Hi Guys. Can you help me please?

I searched in the forum but I did not find something specifically for this problem.

7/13/2016 8:27:35 AM 14975 Extension 4021 172.16.1.160 172.16.1.10 49.4ms
7/13/2016 8:30:46 AM 14942 Extension 4013 172.16.1.213 172.16.1.10 966.1ms
7/13/2016 8:50:12 AM 15153 Extension 4001 172.16.1.83 172.16.1.10 1,251.5ms
7/13/2016 8:56:00 AM 15130 Extension 4004 172.16.1.96 172.16.1.10 1,172.6ms
7/13/2016 9:02:17 AM 15222 Extension 4012 172.16.1.157 172.16.1.10 542ms
7/13/2016 9:25:02 AM 15524 Extension 4002 172.16.1.154 172.16.1.10 1,174ms

I understand the association of Jitters, but I do not understand how they are occurring in my IP Office 9.0.11.0 B 1003.

Some users are complaining of losses momentary voice, only in outbound calls.

LINK E1 / R2 BRAZIL, as it is not SIP, I do not understand why I have JITTER.

The network consists in (IP Office) + (1 ERS 3500 + 22 1608 phones) + (3 Cisco 2960 48 ports with 9620 Phones), but this problem only occur in 1608 Phones.

Only VOICE through the Switch, no VLAN configured.

Thank you guys!

 

[critchey]

Only VOICE through the Switch, no VLAN configured.

Just to be clear you have no devices other then phones connected to this network?

The fact that you have all the 1608s plugged into the ERS, and they all have issues and the rest of the phones are on Cisco switches with no problems, leads me to believe there is an issue with the ERS.

 

[janni78]

1608 are IP Phones so you can still have jitter in a bad network.

"Trying is the first step to failure..." - Homer

 

[Suporte JustGroup]

Yes, no other devices. Only IP Office and Phones and a Server with voicemail pro.

When you said issue in ERS means configuration or hardware?

Janni i know that

The strange is why on Avaya Switch is happening this.

 

[critchey]

Could be configuration or hardware honestly. If possible try the 1608 on something else and see if it still gets jitter. If moving the phone off the ERS helps the jitter then you need to figure out if its the configuration or bad hardware. I always assume bad configuration at first, and after triple checking the configuration then I start to suspect the hardware itself. But hey, that is just me.

 

[Suporte JustGroup]

Okay i gonna do the Double check in everything.

Thank you very much!

 

[IPGuru]

Are your users reporting issues?

the IPO reporting on jitters is misleading at the best of times.

if you are not getting users complaining of poor speech quality then there is nothing to worry about.
if they are then there is something causing interference of your voice Vlan.


The mots important thing to remember is
DON'T GO LOOKING FOR PROBLEMS, PROBLEMS WILL FIND YOU SOON ENOUGH IF THEY EXIST



Do things on the cheap & it will cost you dear

 

[Suporte JustGroup]

Are your users reporting issues?

the IPO reporting on jitters is misleading at the best of times.

if you are not getting users complaining of poor speech quality then there is nothing to worry about.
if they are then there is something causing interference of your voice Vlan.


The mots important thing to remember is
DON'T GO LOOKING FOR PROBLEMS, PROBLEMS WILL FIND YOU SOON ENOUGH IF THEY EXIST

Thank you thank you.

This is true, i too worried with 1 or another user complaining, but the jitters always was there and never was a problem.

I gonna wait a little more to get the best conclusion.

thank you again.

 

[mattKnight]

Jitter of 1 thousand and 2 hundred and some tens of milliseconds...

That's over 1 and a quarter seconds.

1. That is a long time in network terms... about 3 times round the world

2 if you had that amount of jitter, you would have complaints from users. If I were a user experiencing 1.25 seconds of jitter, Id be camped on your doorstep demanding action


I think you have a monitoring anomaly

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[derfloh]

I sometimes see 95% packet loss without any issues ;-)

 

[critchey]

I have seen 33000ms jitter before lol

 

[Suporte JustGroup]

Yah, this is the last SSA data.

7/13/2016 3:16:09 PM 19916 Extension 4021 172.16.1.160 172.16.1.10 324ms
7/13/2016 3:32:38 PM 20113 Extension 4023 172.16.1.158 172.16.1.10 1,172.6ms
7/13/2016 3:36:15 PM 20224 Extension 4014 172.16.1.159 172.16.1.10 1,080.9ms
7/13/2016 3:43:52 PM 20247 Extension 4012 172.16.1.157 172.16.1.10 284.5ms
7/13/2016 3:47:56 PM 20370 Extension 4018 172.16.1.97 172.16.1.10 1,172.4ms
7/13/2016 3:48:40 PM 20363 Extension 4014 172.16.1.159 172.16.1.10 2,344.9ms
7/13/2016 3:50:04 PM 20433 Extension 4010 172.16.1.53 172.16.1.10 614.6ms
7/13/2016 3:53:26 PM 20475 Extension 4021 172.16.1.160 172.16.1.10 1,173.1ms
7/13/2016 3:53:34 PM 20503 Extension 4019 172.16.1.151 172.16.1.10 1,250.9ms
7/13/2016 4:05:25 PM 20513 Extension 4012 172.16.1.157 172.16.1.10 2,987.1ms
7/13/2016 4:15:27 PM 20731 Line 13 172.16.1.10 172.16.1.77 14%
7/13/2016 4:17:04 PM 20760 Extension 8643 172.16.1.139 172.16.1.48 14.8%
7/13/2016 4:21:55 PM 20629 Extension 4012 172.16.1.157 172.16.1.10 700.6ms
7/13/2016 4:24:21 PM 20863 Line 14 172.16.1.10 172.16.1.136 26ms
7/13/2016 4:54:54 PM 21232 Extension 4010 172.16.1.53 172.16.1.10 1,251.4ms
7/13/2016 4:55:45 PM 21265 Extension 4007 172.16.1.30 172.16.1.10 300.1ms
7/13/2016 4:56:08 PM 21166 Extension 4027 172.16.1.94 172.16.1.10 181.2ms
7/13/2016 4:57:59 PM 21234 Extension 4009 172.16.1.31 172.16.1.10 3,751ms
7/13/2016 5:34:42 PM 21518 Extension 4009 172.16.1.31 172.16.1.10 1,172.8ms
7/13/2016 5:58:20 PM 21714 Extension 4015 172.16.1.153 172.16.1.10 2,345.4ms

But without any user complaining.

 

[janni78]

System Status is not a reliable QoS Monitor, you can check a call in realtime but it tends to give high packet loss or jitter when a call is completed.

"Trying is the first step to failure..." - Homer

 

[Alfalis]

In my experience the QoS in SSA is BS...
Seems to me that as soon as only one single packet is dropped during a call SSA is generating an alarm^^

As IPGuru said:
If you are not getting users complaining of poor speech quality then there is nothing to worry about.

 

[amriddle01]

I always turn the QoS monitoring off, it's no use and just generates false alarms all the time making people think there's issues when there isn't.

Ditch it

 

[Suporte JustGroup]

Hummm, how i turn this QoS Alarm off?

 

[janni78]

Uncheck "Enable RTCP Monitoring on Port 5005" in System -> LANx -> VoIP.
You can also point it to a 3rd party monitoring server.

You also have these settings in 46xxsettings.txt, but don't know if they apply for IP Office.

#################### RTCP MONITORING #####################
##
## The RTCP monitor
## One RTCP monitor (VMM server) IP address in
## dotted-decimal format or DNS name format (0 to 15
## characters). Note that for H.323 telephones only this
## parameter may be changed via signaling from Avaya
## Communication Manager. For 96xx SIP models in Avaya
## environments, this parameter is set via the PPM server.
## This parameter is not supported on 16CC model phones.
## Note : This setting is applicable for 1603 SIP phones also.
## Note : This setting is supported by H1xx SIP R1.0 as well.
## SET RTCPMON 192.168.0.10
##
## RTCPMONPORT sets the port used to send RTCP information
## to the IP address specified in the RTCPMON parameter.
## RTCPMONPORT is only supported on 46xx SIP telephones and
## 96xx telephones in non-Avaya environments. For 96xx SIP
## models in Avaya environments, this parameter is set via
## the PPM server. The default value is 5005.
## Note : This setting is applicable for 1603 SIP phones also.
## Note : This setting is supported by H1xx SIP R1.0 as well.
## SET RTCPMONPORT 5005
##
## RTCP Monitor Report Period
## Specifies the interval for sending out RTCP monitoring
## reports (5-30 seconds). Default is 5 seconds. This
## parameter applies only to 96xx SIP telephones.
## Note : This setting is applicable for 1603 SIP phones also.
## SET RTCPMONPERIOD 5
##

"Trying is the first step to failure..." - Homer