For peaked call arrival patterns, Cisco suggests rollover trunk groups in some cases but says that in general enough resources must be allocated to handle the peak traffic.
Checked 2026-09-25
- Vendor
- Cisco
- Product
- Cisco IOS VoIP solutions
- Subsystem
- traffic model selection
- Deployment
- on-premises
- Region
- not restricted
- Release range
- document updated 2001-07-02
- Checked
- 2026-09-25
Sources
- Traffic Analysis — Cisco Systems · tier 2 current vendor documentation · Traffic Model Selection Criteria > Peaked Call Arrival Pattern
Cite this note
APA
WarmTransfer. (2026, September 25). Erlang B and Erlang C for voice and contact center sizing: source note erlang-traffic-engineering-peaked-traffic-rollover. WarmTransfer. https://warmtransfer.net/knowledge/claims/erlang-traffic-engineering-peaked-traffic-rollover
BibTeX
@misc{warmtransfer-claim-erlang-traffic-engineering-peaked-traffic-rollover,
title = {Erlang B and Erlang C for voice and contact center sizing: source note erlang-traffic-engineering-peaked-traffic-rollover},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/erlang-traffic-engineering-peaked-traffic-rollover},
note = {Source note erlang-traffic-engineering-peaked-traffic-rollover, checked 2026-09-25}
}