g.711 vs g.729 over MPLS and SSA Call Quality Alerts 2

[waldrondigital]

I don't get it. When I switch out out IPO (5.0(26)) SCN codec to g.711 over our MPLS QoS controlled Paetec circuit I get SSA alerts about packet loss. When I switch this to g.729 this never happens... ever. The calls sound fine with the fatty g.711 codec, nobody complains, so my question is:

Can the SSA alerts be trusted in this regard? Strange that one codec never reports trouble and the other does.

 

[amriddle01]

SSA QoS alarms are bullsh1t and can't be trusted, the system makes them up, if call quality is not effected ignore them....I do

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[waldrondigital]

This is why you are a genius Andy! Cheers mate.

 

[qtelcom]

ditto on the SSA QoS alarms being Bullsh1t and can't be trusted. Why avaya even includes this unreliable POS in SSA, it's ridiculous. If it's going to generate a bunch of crap alarms, why even have it in there AVAYA?!?

 

[waldrondigital]

Funny you mention the BS factor of SSA. I had a client on 5.0 (18) with tons of QoS/park issues that were real (remote IP phones). After the upgrade to 5.0 (23) the QoS issues went away, totally. They contacted an Avaya certified rep to get that gem of information as I was adamant about this being an oversubscribed circuit issue. Never thought I'd feel so fucking dumb... but I do.

I'm no Avaya expert by any means, but some of the experts I've met even I've surpassed in my knowledge of the system... Ugh

But the real experts are at tek-tips. That's the truth.

Thanks for the help and for dealing with my stupidity.

 

[waldrondigital]

I also mention that SSA still reports quality issues at the client in the previous post, but they say everything is working great now. Ugh x 2

 

[amriddle01]

Don't feel stupid, why wouldn't you believe the alarms, isn't that why avaya put them there... to help troubleshoot the system?

In your case the bullsh1t alarms happened to coincide with real issues and so you thought that's what they were reflecting. Truth is the presence or lack of thoses alarms (and many others) in SSA does not mean anything is good or bad. Only time pulling your hair out tells you which alarms can be trusted or not, or you can ask here

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[Westi]

it is worse when the customers IT guy sees the alarms and tells you that you have issues with your system or the phones because his network is perfect. Ualp
I have one of these knowitall IT guys that constantly sends me screenshots of the SSA and asks for troubleshooting on it but he has no quality issues. I told him that if there is an issue that his network is causing them but of course he has the ear of the boss in that company as he is there for a 100 years or so.

Joe W.

16103

 

[waldrondigital]

I AM the IT guy (my primary expertise) so I manage both their network AND Avaya system (they are friends and client). At war with myself I suppose!

 

[qtelcom]

Well Westi (and anyone else), in case you get a hyper-IT guy you can always turn off the generated QoS monitoring that populate those alarms in SSA. It's a setting in Manager, LAN1, VoIP, and uncheck "Enable RTCP Monitor On Port 5005". Poof! No more distracting QoS false alarms...

I've always left it on, figuring it would be fixed and considered reliable in the "next" patch or release. I'm pretty much done waiting for that one though.

 

[hairlessupportmonkey]

rule - if the customer or user aint complaining, dont make your self any more work than you have to ;-)

ACSS - SME
General Geek

 

[tlpeter]

Although i have seen site without any QOS issues in SSA and others with a crappy network did have QOS issues.

Mostly i see those errors when the 16XX are used.


BAZINGA!

I'm not insane, my mother had me tested!