Configuring CallMgr bandwidth in a location w/ RTP compression
I have a number of sites which are connected via Frame, using G.729, and RTP header compression.
According to Cisco docs, each G729 stream uses approx 26bkps with two streams being used per call for a total of 52kbps.
With header compression, each stream should drop to approx 15kbps so the total call bandwidth should be approx 30kbps per call.
When I set the location bandwidth setting, should I be accounting for the compression since CallMgr doesn't know anything about the compression and the savings?
For example on a 256k pipe:
I can get 4 uncompressed header calls through
Using compression, I can do 8 calls
So, when I enter the location bandwidth settings, would I want to enter 256 for it or 512k?
My reasoning is that I would want to do 512k so that I can get the full amount of calls (eight total with header compression).... where if I did 256, then I could only do 4 calls since CallMgr is assuming that I am using uncompressed headers.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4