1,2,3 all seem fine, as the call originates and terminates in the same location 'B14'. Locations tracks only the bandwidth used between a location and any other location (e.g. hub_none).
4,5 - here, as G729 is streamed from hub_none to B14, 24Kbps is assigned as used. CCM doesn't know the exact bandwidth used by a call (which varies depending on the L2 transmission media and other things) so it assumes G729=24Kbps, and G711=80Kbps.
6 - 96 - 24 = 72, which is correct.
7 - I presume the Operator is attempting to transfer to Hub_none or another non-B14 location? It would appear that whatever the Operator is trying to transfer to must be configured for G711 only and be in a location other than B14. As CCM requires 80Kbps for this call, it is rejected.
If you increase the locations bandwidth from 96 to 104, it will allow the transfer.
When you set up locations, you generally don't configure the exact REAL bandwidth you have available - you work out how many G729 or G711 calls you can fit into your real bandwidth, taking into account overhead and so on. You then calculate the figure that will enforce the correct limit on CCM.
E.g. you know you can pass 3 G729 calls accross the WAN, so you assign 72K to the location, even though in reality the calls may take 90K.
It's best to not mix G711 and G729 on the same link, as it makes the maths difficult.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
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. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...