Avaya E129 poorest QoS whith IPO

[lrocha]

Hi again, everyone,

I have successfully registered about 35 SIP E129 phones and everything goes fine until someone make a call... SSA starts triggering QoS Alarms: Every call between SIP E129 endpoint and IPO 500v2 reports about 86.3% packet loss, most of the times...
In the same network, QoS and VLAN Implemented, we have some H.323 endpoints, 1616 & 1608 working just fine, with no QoS problems at all.
Nevertheless there is NO packet loss in calls between SIP endpoints or SIP to H.323 endpoints.
At the beggining we thought a codec change, from G.711 to G.729, could solve the problem, but had no effect.
That made me think there is a problem in RTP port transmit/listen over IPO side, so I have changed RTP traffic port number range from 5000 to 53246, in order to force IPO transmit/listen on 5004 port, which is E129 default local RTP port. That made no changes and SSA Alarms still on fire.

Any ideas?

 

[intrigrant]

I see a lot of QoS errors in SSA, watch a real call live in SSA and see if QoS is really a problem, I don't think so.
And beside SSA, any complaints from the users? They always are my reference, not the diagnostic software which is a guide line.
I suspect the SSA alarms are triggerd right at the start or at the end of a call were the audio path is opened or closed just a bit later as SSA starts to inspect QoS.

 

[lrocha]

Good Point Intrigrant, just a single user had actually complaint about quality issues, but ¿every call between E129's and IPO gets it's own personal Alarm? that most not be ok... Also, h.323 devices do not show anything...
I will trace some live calls with SYSMON and also will configure the user's PC port to mirror all traffic, and see than happens.

 

[holdmusic34]

You can change the system status threshholds.
Manager> System>System Events> Configuration

Or the better way> System status> Log off

In trouble to be troubled, is to have your trouble doubled.

 

[qtelcom]

SSA QoS alarms are a joke. I get them on every call here in our office for our IP phones with ridiculous stats, and we have zero quality issues on calls.

I think intrigrant is right on this point

"I suspect the SSA alarms are triggerd right at the start or at the end of a call were the audio path is opened or closed just a bit later as SSA starts to inspect QoS"