Cisco notes that VRU queuing and VRU self-service scenarios each need a different number of VRU ports because each has a different average handle time and possibly a different call load.
Checked 2026-09-25
- Vendor
- Cisco
- Product
- Unified Contact Center Enterprise
- Subsystem
- trunk and port sizing
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 15.0(1)
- Checked
- 2026-09-25
Sources
- Solution Design Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1) - Sizing and Operating Conditions for Reference Designs — Cisco Systems · tier 2 current vendor documentation · VRU Port Sizing for Queuing
Cite this note
APA
WarmTransfer. (2026, September 25). Erlang B and Erlang C for voice and contact center sizing: source note erlang-traffic-engineering-vru-ports-per-scenario. WarmTransfer. https://warmtransfer.net/knowledge/claims/erlang-traffic-engineering-vru-ports-per-scenario
BibTeX
@misc{warmtransfer-claim-erlang-traffic-engineering-vru-ports-per-scenario,
title = {Erlang B and Erlang C for voice and contact center sizing: source note erlang-traffic-engineering-vru-ports-per-scenario},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/erlang-traffic-engineering-vru-ports-per-scenario},
note = {Source note erlang-traffic-engineering-vru-ports-per-scenario, checked 2026-09-25}
}