Study guide

1.2 Capacity Planning, Sizing & Bandwidth Considerations

Cisco 350-801 CLCOR CCNP/CCIE Collaboration Core v2.0

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Collaboration Architecture, Deployment Models, Sizing & Upgrades

1.1 Collaboration Architecture & Deployment Models 1.2 Capacity Planning, Sizing & Bandwidth Considerations 1.3 High Availability, Redundancy & Disaster Recovery 1.4 Cisco Unified CM Cluster Upgrade Process

2 Chapter 2: Edge Architecture, Security & Network Services

2.1 Collaboration Edge Architecture: CUBE & Expressway 2.2 Security Protocols & PKI: SSO, OAuth, TLS & SRTP 2.3 Network Infrastructure Services: DNS, NTP, DHCP & LDAP

3 Chapter 3: Protocols, Codecs & Endpoint Provisioning

3.1 SIP Signaling Architecture & Call Flows 3.2 Session Description Protocol (SDP) & Early Offer vs. Delayed Offer 3.3 Audio/Video Codecs & DTMF Relay 3.4 Endpoint Deployment, Onboarding & Troubleshooting

4 Chapter 4: CUCM Dial Plan Fundamentals & Digit Analysis

4.1 Partitions and Calling Search Spaces (CSS) 4.2 Route Patterns, Route Groups & Route Lists 4.3 Translation Patterns, Transformation Patterns & Digit Manipulation 4.4 Globalized Call Routing & Local Route Group (LRG)

5 Chapter 5: Advanced Call Control, Call Routing & User Management

5.1 Call Admission Control (CAC), Locations & AAR 5.2 Toll Fraud Prevention & Call Privileges 5.3 CUCM User Management, LDAP Integration & RBAC 5.4 Administrative XML (AXL) API & Dial-Plan Troubleshooting Tools

6 Chapter 6: Cisco Unity Connection & Voicemail Integration

6.1 Cisco Unity Connection Architecture & SIP Integration 6.2 Mailbox Provisioning, User Templates & Class of Service 6.3 Message Waiting Indication (MWI) & Troubleshooting 6.4 Call Handlers & Directory Handlers

7 Chapter 7: IOS XE Voice Gateways, CUBE & Media Resources

7.1 Cisco IOS XE Voice Gateways & Dial Peers 7.2 Voice Translation Rules and Translation Profiles 7.3 Cisco Unified Border Element (CUBE) Configuration & Redundancy 7.4 IOS XE Media Resources & DSP Management

8 Chapter 8: Webex Architecture, Control Hub, Meetings & Messaging

8.1 Webex Suite Overview & Control Hub Architecture 8.2 Cloud Identity Management, SCIM & Directory Connector 8.3 Webex Developer Platform & APIs 8.4 Configuring Webex Cloud Meetings 8.5 Configuring Webex Cloud Messaging

9 Chapter 9: Webex Calling Routing, Permissions & PSTN Connectivity

9.1 Webex Calling Architecture, Locations & Number Management 9.2 Webex Calling Routing, Trunks & Dial Plans 9.3 Webex Calling Call Routing Process & Translation Patterns 9.4 Webex Calling Toll Fraud Prevention, Call Permissions & Operating Modes 9.5 PSTN Connectivity: Cloud-Connected PSTN (CC-PSTN) & Cisco Calling Plans 9.6 Webex Calling Local Gateway (LGW) Architecture & Configuration

10 Chapter 10: Webex Hybrid Services & Cloud Connected UC

10.1 Cloud-Connected UC (CCUC) Architecture & Telemetry 10.2 Webex Hybrid Calendar & Hybrid Directory Services 10.3 Webex Video Mesh & Hybrid Data Security

11 Chapter 11: Media Quality, QoS Engineering & Troubleshooting

11.1 Real-Time Media Characteristics & Impairments 11.2 QoS Classification, Marking & Trust Boundaries 11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE 11.4 Troubleshooting Media Quality & Call Failures

1.2 Capacity Planning, Sizing & Bandwidth Considerations

Key Takeaways Explain This Topic AI

One Erlang represents 3,600 seconds of continuous circuit utilization, calculated as E = (BHCA * H) / 3600, where BHCA represents Busy Hour Call Attempts and H represents average holding time in seconds.

The Erlang B traffic model assumes blocked calls are cleared immediately, serving as the industry standard for sizing PSTN trunks, SIP trunks, and WAN call admission limits under a designated Grade of Service (GoS).

VoIP packets carry 40 bytes of IP/UDP/RTP headers (20-byte IP + 8-byte UDP + 12-byte RTP); untagged Ethernet adds 18 bytes (14-byte header plus 4-byte FCS), and an 802.1Q tag adds 4 more.

At standard 20 ms packetization, G.711 consumes 80.0 kbps at Layer 3 and 87.2 kbps on Ethernet L2, whereas G.729 consumes 24.0 kbps at Layer 3 and 31.2 kbps on Ethernet L2, delivering a 64.2% bandwidth reduction.

High Efficiency Video Coding (H.265 / HEVC) delivers a 40% to 50% bandwidth reduction over H.264 AVC at identical resolutions by employing Coding Tree Units (CTUs) up to 64x64 pixels and 35 intra-prediction modes (33 angular plus planar and DC).

Last updated: October 2026

1.2 Capacity Planning, Sizing & Bandwidth Considerations

Designing enterprise voice and video networks requires rigorous mathematical modeling of telecommunications traffic and granular analysis of packet-level encapsulation overhead. Collaboration engineers must accurately forecast concurrent session volume, determine PSTN and SIP trunk requirements, and allocate adequate Quality of Service (QoS) bandwidth across wide area network links.

1. Telephony Traffic Engineering: Erlang Models & BHCA

Telecommunications capacity planning quantifies user calling behavior during the most heavily utilized period of the business day: the Busy Hour .

Core Traffic Metrics

Busy Hour Call Attempts (BHCA) : The total number of call setup attempts (both answered and unanswered) initiated during the peak 60-minute traffic window.

Holding Time ( H H H ) : The average call duration in seconds, measuring the period a trunk or audio channel remains engaged.

Erlang ( E E E ) : The dimensionless international standard unit of telecommunications traffic intensity. One Erlang represents continuous utilization of one voice channel for one hour (3,600 call-seconds).

Centum Call Seconds (CCS) : Unit representing 100 call-seconds of traffic. Since one hour contains 3,600 seconds:

1 Erlang = 36 CCS 1 \text{ Erlang} = 36 \text{ CCS} 1 Erlang = 36 CCS

Traffic intensity in Erlangs is calculated using the formula:

E = BHCA × H 3600 E = \frac{\text{BHCA} \times H}{3600} E = 3600 BHCA × H ​

Example Calculation : If an office generates 1,200 BHCA with an average holding time of 180 seconds:

E = 1200 × 180 3600 = 216000 3600 = 60 Erlangs E = \frac{1200 \times 180}{3600} = \frac{216000}{3600} = 60 \text{ Erlangs} E = 3600 1200 × 180 ​ = 3600 216000 ​ = 60 Erlangs

Erlang B vs. Erlang C Traffic Models

Selecting the correct Erlang distribution model depends on how the underlying telecommunications system handles blocked traffic during peak hours:

Traffic Model Underlying Assumption Primary Collaboration Application Output Variable Calculated

Erlang B Blocked Calls Cleared (Lost) : Callers who encounter a busy signal hang up immediately and do not queue. Sizing PSTN T1/E1 trunks, SIP gateway trunks, and WAN call concurrency limits. Trunks required to achieve target Grade of Service (e.g., P.01 = 1% block).

Extended Erlang B Blocked Calls Retry : A fixed percentage of blocked callers immediately redial after receiving a busy signal. High-traffic PSTN ingress trunks with persistent retry behaviors. Adjusted trunk count compensating for caller retry multiplication.

Erlang C Blocked Calls Delayed (Queued) : Blocked callers do not receive a busy tone; they wait in an infinite or finite FIFO queue. Sizing Cisco Unified Contact Center Enterprise (UCCE/PCCE) agent pools and IVR ports. Number of agents required to meet target Average Speed of Answer (ASA).

Grade of Service (GoS)

Grade of Service expresses the probability ( P P P ) that a call attempt will be blocked due to insufficient trunk capacity during the busy hour. Common enterprise engineering thresholds include:

P.01 (1% blocking) : Standard commercial enterprise trunking design. Out of 100 call attempts, no more than 1 will encounter a busy tone.

P.001 (0.1% blocking) : Mission-critical or emergency response trunking design.

2. Voice Packet Overhead & Bandwidth Calculation

A Voice over IP (VoIP) stream consists of digitized voice samples packed into RTP packets, encapsulated across UDP, IP, and the underlying data link layer.

Protocol Encapsulation Breakdown +-----------------------------------------------------------------------------------------+

  • | ETHERNET VoIP PACKET |
  • +-----------------------+-------------------+------------------+---------------+----------+
  • | Layer 2 Frame Header | IPv4 Header | UDP Header | RTP Header | Audio |
  • | Dest MAC + Src MAC + | 20 Bytes | 8 Bytes | 12 Bytes | Payload |
  • | Type + 4-byte FCS | (40 B for IPv6) | | | (e.g., |
  • | = 18 Bytes | | | | 160 B) |
  • +-----------------------+-------------------+------------------+---------------+----------+
  • | |<------------------ 40-BYTE L3/L4/RTP --------------->| |
  • |<--------------------------- TOTAL PACKET SIZE: 218 BYTES ------------------------------>|

Layer 2 Ethernet Overhead : Ethernet II framing adds a 14-byte header (6-byte destination MAC + 6-byte source MAC + 2-byte EtherType) and a 4-byte Frame Check Sequence (FCS) trailer, totaling 18 bytes of data-link overhead. Where an 802.1Q VLAN tag is present (for example, on a trunk link), it adds 4 more bytes for 22 bytes ; G.711 at 20 ms then needs 88.8 kbps instead of 87.2 kbps.

Layer 3 IPv4 Header : Standard IPv4 header without options consumes 20 bytes (IPv6 consumes 40 bytes).

Layer 4 UDP Header : User Datagram Protocol consumes 8 bytes .

Real-time Transport Protocol (RTP) Header : Standard RTP header consumes 12 bytes .

Total combined IP/UDP/RTP header overhead at Layer 3 and Layer 4:

Header Overhead = 20 (IP) + 8 (UDP) + 12 (RTP) = 40 bytes \text{Header Overhead} = 20 \text{ (IP)} + 8 \text{ (UDP)} + 12 \text{ (RTP)} = 40 \text{ bytes} Header Overhead = 20 (IP) + 8 (UDP) + 12 (RTP) = 40 bytes

Packetization Interval and Packet Rate

VoIP endpoints sample analog signals and package them at fixed transmission intervals (packetization intervals), most commonly 20 ms (50 packets per second), 10 ms (100 packets per second), or 30 ms (33.33 packets per second):

Packets Per Second (pps) = 1 Packetization Interval (seconds) \text{Packets Per Second (pps)} = \frac{1}{\text{Packetization Interval (seconds)}} Packets Per Second (pps) = Packetization Interval (seconds) 1 ​

Voice Payload (bytes) = Codec Bitrate (bps) × Packetization Interval (s) 8 bits/byte \text{Voice Payload (bytes)} = \frac{\text{Codec Bitrate (bps)} \times \text{Packetization Interval (s)}}{8 \text{ bits/byte}} Voice Payload (bytes) = 8 bits/byte Codec Bitrate (bps) × Packetization Interval (s) ​

Example (G.711 at 20 ms) :

Voice Payload = 64000 × 0.020 8 = 160 bytes \text{Voice Payload} = \frac{64000 \times 0.020}{8} = 160 \text{ bytes} Voice Payload = 8 64000 × 0.020 ​ = 160 bytes

Example (G.729 at 20 ms) :

Voice Payload = 8000 × 0.020 8 = 20 bytes \text{Voice Payload} = \frac{8000 \times 0.020}{8} = 20 \text{ bytes} Voice Payload = 8 8000 × 0.020 ​ = 20 bytes

Calculating Bitrates

Layer 3 Packet Size : Payload Bytes + 40 bytes \text{Payload Bytes} + 40 \text{ bytes} Payload Bytes + 40 bytes

Layer 3 Bandwidth (bps) : L3 Packet Size (bytes) × 8 bits/byte × pps \text{L3 Packet Size (bytes)} \times 8 \text{ bits/byte} \times \text{pps} L3 Packet Size (bytes) × 8 bits/byte × pps

Layer 2 Frame Size : L3 Packet Size + 18 bytes \text{L3 Packet Size} + 18 \text{ bytes} L3 Packet Size + 18 bytes (untagged Ethernet; add 4 bytes for 802.1Q)

Layer 2 Bandwidth (bps) : L2 Frame Size (bytes) × 8 bits/byte × pps \text{L2 Frame Size (bytes)} \times 8 \text{ bits/byte} \times \text{pps} L2 Frame Size (bytes) × 8 bits/byte × pps

3. Audio Codec Bandwidth Comparison

The following table details packet dimensions and bandwidth requirements for prominent enterprise codecs across standard Ethernet infrastructure:

Codec Algorithmic Bitrate Packetization Interval Payload Size Packets Per Second Layer 3 Bandwidth Ethernet L2 Bandwidth (untagged, 18 bytes)

  • G.711 ( μ \mu μ -law / A-law) 64.0 kbps 20 ms 160 bytes 50 pps 80.0 kbps 87.2 kbps
  • G.711 ( μ \mu μ -law / A-law) 64.0 kbps 10 ms 80 bytes 100 pps 96.0 kbps 110.4 kbps
  • G.711 ( μ \mu μ -law / A-law) 64.0 kbps 30 ms 240 bytes 33.33 pps 74.7 kbps 79.5 kbps
  • G.729 / G.729a 8.0 kbps 20 ms 20 bytes 50 pps 24.0 kbps 31.2 kbps
  • G.722 (Wideband) 64.0 kbps 20 ms 160 bytes 50 pps 80.0 kbps 87.2 kbps
  • Opus (Speech Mode) ~20.0 kbps (adaptive) 20 ms 50 bytes 50 pps 36.0 kbps 43.2 kbps
  • iLBC (Mode 20) 15.2 kbps 20 ms 38 bytes 50 pps 31.2 kbps 38.4 kbps
  • iLBC (Mode 30) 13.33 kbps 30 ms 50 bytes 33.33 pps 24.0 kbps 28.8 kbps

Header Compression Note : Compressed RTP (cRTP, RFC 2508) compresses the 40-byte IP/UDP/RTP header down to 2 or 4 bytes over point-to-point serial WAN links (such as T1/E1 PPP/HDLC). However, cRTP is CPU-intensive and is not supported across standard Ethernet, MPLS, or IPsec encapsulated tunnels.

4. Video Bandwidth Requirements: H.264 AVC vs. H.265 HEVC

Video endpoints generate variable bitrate (VBR) or constrained bitrate (CBR) RTP streams that consume significantly greater bandwidth than voice streams.

Video Resolution and Bandwidth Matrix

Video Format Resolution (Pixels) Frame Rate H.264 AVC Target Bandwidth H.265 HEVC Target Bandwidth Typical Use Case

720p HD 1280 × 720 1280 \times 720 1280 × 720 30 fps 1.0 Mbps to 1.5 Mbps 600 kbps to 900 kbps Cisco Webex Desk Series, standard desktop video

1080p Full HD 1920 × 1080 1920 \times 1080 1920 × 1080 30 fps 2.5 Mbps to 4.0 Mbps 1.5 Mbps to 2.2 Mbps Cisco Room Kit, Board Series, conference rooms

1080p60 High Motion 1920 × 1080 1920 \times 1080 1920 × 1080 60 fps 4.0 Mbps to 6.0 Mbps 2.5 Mbps to 3.5 Mbps Immersive Telepresence, high-motion data sharing

4K Ultra HD 3840 × 2160 3840 \times 2160 3840 × 2160 30 fps 12.0 Mbps to 18.0 Mbps 6.0 Mbps to 10.0 Mbps Ultra-high-definition presentation and main video

Architectural Efficiency: H.264 vs. H.265

High Efficiency Video Coding (H.265 / HEVC) delivers approximately 40% to 50% bandwidth savings over H.264 Advanced Video Coding (AVC) at equivalent subjective visual quality:

Block Partitioning : H.264 relies on rigid 16 × 16 16 \times 16 16 × 16 pixel macroblocks. H.265 replaces macroblocks with flexible Coding Tree Units (CTUs) ranging up to 64 × 64 64 \times 64 64 × 64 pixels, allowing efficient compression of expansive background regions.

Intra-Prediction Precision : H.264 uses up to 9 intra-prediction modes (for 4x4 luma blocks); H.265 defines 35 (33 angular plus planar and DC), which predicts detail more accurately and leaves less residual to encode.

Network Impact : Upgrading video endpoints to H.265 enables enterprises to route 1080p30 video over WAN links provisioned for 1.8 Mbps rather than 3.5 Mbps.

  • 5. Step-by-Step Worked Bandwidth Calculation
  • Problem Statement

An enterprise branch office connects to corporate headquarters across an MPLS WAN. The branch requires concurrent capacity for 100 active voice calls .

Calculate the required Layer 2 Ethernet WAN bandwidth for 100 concurrent G.711 calls at 20 ms packetization.

Calculate the required Layer 2 Ethernet WAN bandwidth for 100 concurrent G.729 calls at 20 ms packetization.

Factor in a 5% signaling buffer (SIP and RTCP) and a 20% QoS Low Latency Queuing (LLQ) headroom reserve to determine the final provisioned Priority Queue size.

  • Step-by-Step Solution
  • Part A: Sizing for 100 G.711 Calls (20 ms)

Determine Payload : G.711 produces 64,000 bps. Over 20 ms, payload is: 64000 × 0.020 8 = 160 bytes \frac{64000 \times 0.020}{8} = 160 \text{ bytes} 8 64000 × 0.020 ​ = 160 bytes

Calculate L3 Packet Size : Add 40 bytes for IP/UDP/RTP headers: 160 + 40 = 200 bytes 160 + 40 = 200 \text{ bytes} 160 + 40 = 200 bytes

Calculate L2 Frame Size : Add 18 bytes of untagged Ethernet overhead: 200 + 18 = 218 bytes 200 + 18 = 218 \text{ bytes} 200 + 18 = 218 bytes

Calculate Single Call L2 Bitrate : At 50 packets per second: 218 bytes × 8 bits/byte × 50 pps = 87 , 200 bps = 87.2 kbps 218 \text{ bytes} \times 8 \text{ bits/byte} \times 50 \text{ pps} = 87,200 \text{ bps} = 87.2 \text{ kbps} 218 bytes × 8 bits/byte × 50 pps = 87 , 200 bps = 87.2 kbps

Aggregate Media Bandwidth (100 Calls) : 100 × 87.2 kbps = 8 , 720 kbps = 8.72 Mbps 100 \times 87.2 \text{ kbps} = 8,720 \text{ kbps} = 8.72 \text{ Mbps} 100 × 87.2 kbps = 8 , 720 kbps = 8.72 Mbps

Add 5% Signaling (SIP/RTCP) : 8.72 Mbps × 1.05 = 9.156 Mbps 8.72 \text{ Mbps} \times 1.05 = 9.156 \text{ Mbps} 8.72 Mbps × 1.05 = 9.156 Mbps

Apply 20% QoS Headroom Safety Margin : 9.156 Mbps × 1.20 = 10.987 Mbps ≈ 11.0 Mbps 9.156 \text{ Mbps} \times 1.20 = 10.987 \text{ Mbps} \approx 11.0 \text{ Mbps} 9.156 Mbps × 1.20 = 10.987 Mbps ≈ 11.0 Mbps

Part B: Sizing for 100 G.729 Calls (20 ms)

Determine Payload : G.729 produces 8,000 bps. Over 20 ms, payload is: 8000 × 0.020 8 = 20 bytes \frac{8000 \times 0.020}{8} = 20 \text{ bytes} 8 8000 × 0.020 ​ = 20 bytes

Calculate L3 Packet Size : Add 40 bytes for IP/UDP/RTP headers: 20 + 40 = 60 bytes 20 + 40 = 60 \text{ bytes} 20 + 40 = 60 bytes

Calculate L2 Frame Size : Add 18 bytes of untagged Ethernet overhead: 60 + 18 = 78 bytes 60 + 18 = 78 \text{ bytes} 60 + 18 = 78 bytes

Calculate Single Call L2 Bitrate : At 50 packets per second: 78 bytes × 8 bits/byte × 50 pps = 31 , 200 bps = 31.2 kbps 78 \text{ bytes} \times 8 \text{ bits/byte} \times 50 \text{ pps} = 31,200 \text{ bps} = 31.2 \text{ kbps} 78 bytes × 8 bits/byte × 50 pps = 31 , 200 bps = 31.2 kbps

Aggregate Media Bandwidth (100 Calls) : 100 × 31.2 kbps = 3 , 120 kbps = 3.12 Mbps 100 \times 31.2 \text{ kbps} = 3,120 \text{ kbps} = 3.12 \text{ Mbps} 100 × 31.2 kbps = 3 , 120 kbps = 3.12 Mbps

Add 5% Signaling (SIP/RTCP) : 3.12 Mbps × 1.05 = 3.276 Mbps 3.12 \text{ Mbps} \times 1.05 = 3.276 \text{ Mbps} 3.12 Mbps × 1.05 = 3.276 Mbps

Apply 20% QoS Headroom Safety Margin : 3.276 Mbps × 1.20 = 3.931 Mbps ≈ 3.93 Mbps 3.276 \text{ Mbps} \times 1.20 = 3.931 \text{ Mbps} \approx 3.93 \text{ Mbps} 3.276 Mbps × 1.20 = 3.931 Mbps ≈ 3.93 Mbps

Summary of Results

Transitioning 100 concurrent calls from G.711 to G.729 reduces the required priority queue allocation from 11.0 Mbps down to 3.93 Mbps , generating an immediate WAN bandwidth conservation of 64.2% .

Loading diagram... VoIP Protocol Encapsulation and Bandwidth Amplification