04-11-2005 12:28 PM - edited 03-13-2019 08:41 AM
One of our customers with their own Callmanager system that we installed has been getting complaints from users saying they get the not enough bandwidth available to make the call. We compared the events to the bandwidth chartsand so far have not seen any traffic related issues. 2 locations have 2 T1's multilinked, one has 3 Multilinked, all 4 locations terminate on a 7206 with a PA-MCT3 card. All multilinks terminate on this router. The bandwidth settings in callmanager are set to the appropriate bandwidth for each location. I have not been able to pull up any docs on how callmanager determines bandwidth useage. All 4 locations the routers are setup as MGCP gateways, but the 7200 is not in the callmanager.
04-11-2005 12:44 PM
Based on my (limited) knowledge of the topic, I believe CallManager tracks the number of active calls to/from a specific location from/to a different location. Then, based on the codec specified in the Region, determines whether there is bandwidth available to complete a call.
It should not rely on "actual" available bandwidth because it has no idea about what other (non-voice) traffic might be using the same network connection. The location settings should specify the maximum amount of bandwidth you would like to use for voice traffic and you should configure traffic-shaping and policing on the WAN routers to ensure that that bandwidth is available as needed.
But that doesn't address your current problem. I recommend that you review what codecs are in use for your WAN calls and how many calls of each codec you plan to use. We use G729 for all WAN calls and see about 25-26k per call. Using that as a general baseline, you should be able to make sure all of your settings are in line.
04-11-2005 04:20 PM
a starting point would be to use the Real Time Monitoring tool (RTMT) with this tool you can monitor the number of calls to a location and the amount of available bandwidth to that location in real time. Perhaps there are more calls attempting to use the WAN links than expected!
04-11-2005 04:40 PM
As the other have stated, this has nothing to do with actual bandwidth usage on the links. This all comes down to how the Locations configuration in CCM was setup. I've included the bandwidth settings that CallManager uses to calculate bandwidth per call, keep in mind that regions will have a factor in this as well. Make sure you check the locations settings of both endpoints if they are in different locations. If you don't see a problem, I would suggest resyncing the locations as they can get out of sync sometimes, like after a WAN failure, etc.
From the CCM Locations help page on a 3.3(3) system:
G.711 call uses 80 kbps
G.723 call uses 24 kbps
G.729 call uses 24 kbps
GSM call uses 29 kbps
Wideband call uses 272 kbps
Cliff
04-12-2005 06:53 AM
Thanks guys, you have provided more help, than hours of searching Cisco docs in regards to this have so far produced. I will keep you informed with what I find.
03-08-2010 02:58 PM
Re-synching bandwidth worked great! thanks for the tip
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide