sys alarm #32 P6002 INSUF BAND

[tech1302]

hi all

we are having this alarm on one of our sites. flag is off. there are 3 more remote sites connected to this site VIA VPN.
i have changed the codec to 729 (speech). system is 5200 CS version 3.2.
what is the best codec for DTMF ?
no issue on broadband on this particular site 15Mb down 888Kb up.

what could be the reason for this ?

please help.

thanks guys

 

[tech1302]

hi all


does anyone know the solution for my issue please...



Thanks

 

[tech1302]

what should be the best DTMF encoding settings and speech encoding settings for a system which has a got a broadband speed of 1.5Mb down and 478Kb up please

thanks

 

[NTEDave]

Do any users complain of poor quality speech when using the link for voice?

Is the link also used for data connectivity?

I've found the 5000 to have a bit of a hair trigger for firing Low Bandwidth alarms, in fact a lot of my customers turn the alarm off!

 

[tech1302]

thanks for the reply

yes this happens for internal calls and for overflowing calls from one site to another site through the VPN.
no they are not using the line for data but the local network is connected to the voice router for call manager software purposes.

i have turned off the flag but the message is still appearing on the phones and the call quality is petty bad.

 

[theohiopatriot]

The proper vocoder for internal calls should be G 7.11 but calls that traverse an Wan link should use G 7.29.

 

[619Tech]

Hi tech1302 - Keep in mind that the "Low Bandwitdth" Alarm can be deceptive in 5000 & Axxess. Any network latency and/or connectivity issue, regardless of duration will trigger it. Available bandwidth might not be your issue. DTMF should stay at G.711; I only use G.729 for voice if I have to, and usually use G.711 to avoid quality complaints. That being said, it sounds like you are connecting via VPN instead of open internet to a NAT, so how about setting up some QOS on the connections? If you have the ability to implement Expedited Forwarding (Cisco 46) on your routers, you can implement TOS 184 on your 5000 and endpoints to prioritize your voice traffic.