There is no relateion between actual BW used and BW allocated using Location parameter. In CUCM location parameter, we consider how many number of calls which we can pass using standard values for G711 or G729 calls.
8 kb/s for (G.729) and 64 kbps for G711 calls. So if we says 8kbps calls should go between two location, so location configuratoin will only allow only one call between two location but actualt BW taken by that call between actual physical location would be as per below link
Below is exact BW used by a Cisco VOIP calls. It hs formula related to it.
CUCM takes into consideration some overhead and doesn't calculate based on the payload only. This is the reason for using 80kbps and 24kbps. This amount cannot be modified. You would need to base your calculations for amounts of calls based on this.
Correct, so when calculating the bandwidth you cannot just use you LLQ values from QoS configuration. Consider an example of a site with T1 MPLS connection where 33% of it is assigned to voice in LLQ configuration. Doing the math yileds:
1536 kbps / 3 = 512 kbps, which can support 512/ 32.8 (G729 call with overhead over MPLS) = 15.6 ~ 15 (round down) Calls
You cannot just plug in 512 as the bandwidth in CUCM Location, you need to convert to what CUCM thinks is needed for 15 G729 calls which is 15 * 24 = 360 kbps
Notice the significant discepency, if you were to plug in 512 you sure would cause quality issues.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...