Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Bandwidth Management

Publisher

Cisco

URL

https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/14/collbcvd/bwmgmt.html

Published

2021-05-21

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco website terms (not verified); no-redistribution; short excerpts and locators only

Source notes citing this source

• When call admission control denies an inter-location call, Unified CM can automatically reroute it to the destination over the PSTN using Automated Alternate Routing (AAR). in context
• AAR is invoked only when Enhanced Locations CAC denies a call for lack of bandwidth along the effective path. in context
• Mapping the topology between clusters requires each cluster to have at least one location in common with another cluster. in context
• The Collaboration 14 preferred architecture lists the devices that must be configured in a location: endpoints, conference bridges, gateways, SIP trunks, music on hold servers, and annunciators (via device pool). in context
• For audio, Enhanced Locations CAC deducts 80 kbps per G.711 or G.722 call: the 64 kbps codec bit rate plus 16 kbps of IP/UDP headers. in context
• For a G.729 call, Enhanced Locations CAC deducts 24 kbps: the 8 kbps payload plus 16 kbps of IP/UDP overhead. in context
• Hub_None is a default location that typically serves as a hub linking two or more locations, and it comes with unlimited intra-location bandwidth allocations. in context
• Cisco's Collaboration 14 preferred architecture recommends leaving intra-location bandwidth at its Unlimited default because there is little or no reason to limit bandwidth within a LAN. in context
• The LBM supplies configured and dynamic data to serviceability and updates the Location Real-Time Monitoring Tool (RTMT) counters. in context
• The Collaboration 14 preferred architecture does not use the immersive video bandwidth allocation. in context
• If a video call fails CAC, video endpoints or SIP trunks with Retry Video Call as Audio enabled retry the call as audio-only; the option is set on the endpoint or SIP trunk configuration page. in context
• The Shadow location cannot have links to other locations, so no bandwidth can be reserved between it and any other location. in context
• The Shadow location lets a SIP trunk pass ELCAC information, such as the location name, so that Enhanced Locations CAC can work between clusters. in context
• A location with the same name in two or more clusters is treated as the same, shared location across those clusters. in context
• The Collaboration 14 preferred architecture recommends standardizing on one audio codec across the organization, LAN and WAN, to keep the region matrix simple. in context
• Cisco describes Enhanced Locations CAC as a model-based, static mechanism that does not take network failures or routing-protocol reroutes into account. in context
• For video calls Unified CM counts only the video payload, without IP/UDP overhead, while the audio stream is counted with IP/UDP overhead; a 384 kbps video call with G.711 audio therefore deducts 320 kbps of video plus 80 kbps of audio. in context
• Because ELCAC is static, after a WAN failure or reroute onto a smaller backup path it can keep admitting calls up to the configured link bandwidth, oversubscribing the path actually in use. inferred in context
• The Cisco Collaboration 14 PA treats the Internet as an unmanaged, non-QoS-enabled network. It relies on media resilience and rate adaptation there rather than on DSCP. in context
• The Cisco Collaboration 14 PA treats PCs, Macs and mobile devices running Jabber as untrusted. It classifies their media and signaling by port ranges and re-marks with network access lists, while servers, gateways and video endpoints are trusted. in context
• In the Cisco Collaboration 14 PA, audio is marked EF, prioritized video AF41, opportunistic video (Jabber, MRA) AF42, and call signaling CS3. in context
• Cisco warns that port-based classification of client media is not a fully secure method, because other applications can use the same ports and gain unintended priority. in context
• The Cisco Collaboration 14 PA places EF audio in a priority queue with a strict policer, sized for voice-only calls plus the audio portion of video calls. Video goes to CBWFQ with WRED, where AF42 is dropped before AF41. in context
• Cisco's Collaboration 14 Preferred Architecture recommends enforcing the QoS trust boundary at the network edge, at LAN access ingress, the WAN edge, or both. in context

Cite this source record

APA

WarmTransfer. (2021, May 21). Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Bandwidth Management. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-pa-collab14-bandwidth-management

BibTeX

@misc{warmtransfer-cisco-pa-collab14-bandwidth-management,
  title  = {Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Bandwidth Management},
  author = {{WarmTransfer}},
  year   = {2021},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-pa-collab14-bandwidth-management},
  note   = {Cisco, accessed 2026-09-24}
}