We are facing Voice Degradation wil using FXO cards in 2610 Routers.
The link is through Frame-Relay Voice PVC (32K CIR) over 256K Access Pipe. The same serial interface carries another PVC for Data (96K CIR).
The Voice PVC doesn't carry any other traffic except voice. We have "not" implemented Frame-Relay Traffic-Shapping.
The Voice quality is really bad in ONE Direction (i.e from location1 to location2). However Voice from location 2 - location 1 is without any problems. And at the same time i do see some FECN (at location 2) and BECN (at location 1) indicating congestion.
1. Has any one experienced Bad Voice quality in only one direction ?
2. Would it help to implement Traffic-Shapping ?
3. What percentage of FECN and BECN is normal ?
4. Is 32K BW enough for 4 FXO ports (4 Voice calls) simulteneously ?
Re: Voice Degradation using FXO Cards in Cisco 2610
To be honest im not surprised you are seeing voice quality problems. And one way is also very common because it depends on bottlenecks. Answers to your questions are :
1. Yes.. it is common.
2. It would help greatly, you should configure it not to burst (mincir = cir = 32 and be = 0).
4. depending on what codec, VAD, crTP you use. Typicall 32K will not be enough for 4 calls, even with g729 and VAD on. If you turn on cRTP, then you can shave it down to 12K, but thats still 36K per call.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...