There has always been a problem, getting the bandwidth correct, when using
a policy map, we have to allow about 26kbps per G729 call, within the policy-map, but then when using the frame-relay ip rtp header-compression, it gets compressed to 11.6Kbps, for example we want 5 concurrent calls on a 128kbps link, in the Policy-map that would be 130kbps which is over the 128k, and doesn't allow any bandwidth for the signalling.so we have had to say the bandwidth was more than 128k for things to work.
I see with 122-13T there is now class based RTP& TCP header compression
which overcomes this problem... Has anybody used this yet? If I have one router running an earlier release of IOS with the frame-relay IP rtp Header compression, will that work with a router running the new class based header compression?
any comments most welcome, and a Happy new year to everybody.
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...
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 discusses the bas...