Cisco Collaboration Concepts You Must Master (CCNA / CCNP)
Home › IP Collaboration › Cisco Collaboration CCNA/CCNP
☰ Table of Contents
- VoIP Fundamentals — How Voice Works Over IP
- Signaling Protocols — SIP, H.323 & SCCP
- Media Protocols — RTP, RTCP & SRTP
- Voice Codecs — G.711, G.729 & Codec Selection
- Cisco CUCM — Call Manager Architecture
- Dial Plans — Route Patterns, Route Groups & Translation
- QoS for Voice & Video
- Cisco CUBE — Border Element & SIP Trunking
- PSTN Integration — Gateways & PRI/BRI
- Cisco Unity Connection — Voicemail & AA
- Cisco Webex & Cloud Collaboration
- Exam Tips & Quick-Reference Table
Voice and video have moved from dedicated, circuit-switched networks to packet-based IP infrastructure — and with that shift, the network engineer's responsibility has expanded dramatically. Today's enterprise networks must deliver voice quality that rivals the traditional phone system, video conferences that feel seamless, and voicemail, auto-attendants, and presence indicators — all running on the same IP fabric as business-critical data. Getting any of it wrong — a misconfigured codec, a dial plan with the wrong translation rule, a QoS policy that doesn't mark voice traffic correctly — and the phones go dead or calls sound like robots talking underwater.
Cisco collaboration is one of the most nuanced and protocol-rich domains across both the CCNA (200-301) and CCNP CLCOR (350-801) exams. This guide covers every concept you need — from the physics of voice digitization to the architecture of CUCM clusters, from SIP message flows to CUBE SIP trunking, from DSCP marking to Webex cloud deployment — with real Cisco CLI commands and architecture context throughout.
1. VoIP Fundamentals — How Voice Works Over IP
Voice over IP (VoIP) converts analog audio into digital packets that travel across an IP network — replacing traditional circuit-switched telephony (PSTN) where a dedicated physical path was reserved for each call. Understanding this digitization pipeline is the foundation of everything in the collaboration domain.
Voice Quality Metrics — The Three Enemies
⏱
DELAY (Latency)
One-way delay between source and destination. Causes annoying echoes and talk-over.
Target: <150ms
Maximum: 400ms
JITTER
Variation in packet arrival times. Causes choppy, robotic voice quality.
Target: <30ms
Fixed by jitter buffer
PACKET LOSS
Missing packets cause audible gaps, clipping, and dropped syllables. Cannot be retransmitted (UDP).
Target: <1%
Maximum: 5%
MOS — Mean Opinion Score: The industry standard for measuring perceived voice quality on a scale of 1 (unacceptable) to 5 (perfect). G.711 delivers MOS ≈ 4.1; G.729 ≈ 3.92. A MOS below 3.5 is generally considered unacceptable for business use. Always use QoS to protect voice traffic from degrading below this threshold.
2. Signaling Protocols — SIP, H.323 & SCCP
Signaling protocols handle call setup, teardown, and feature negotiation — they are the "phone ringing" layer of VoIP. They do not carry the actual voice audio (that is handled by RTP). Think of signaling as the conversation that arranges a meeting, while RTP is the meeting itself.
SIP — Session Initiation Protocol (RFC 3261)
SIP is the dominant open-standard signaling protocol for modern VoIP and unified communications. It is text-based (like HTTP), uses a request/response model, and operates over UDP (port 5060) or TLS (port 5061 for encrypted SIP — SIPS).
SIP vs H.323 vs SCCP — Protocol Comparison
| Feature | SIP | H.323 | SCCP (Skinny) |
|---|---|---|---|
| Standard | IETF (RFC 3261) | ITU-T | Cisco Proprietary |
| Format | Text-based (like HTTP) | Binary (complex) | Binary (lightweight) |
| Transport | UDP 5060 / TLS 5061 | TCP 1720 | TCP 2000 |
| Peer Model | Peer-to-peer | Peer-to-peer + Gatekeeper | Client-server only (CUCM) |
| Complexity | Simple — easy to debug | High — complex stack | Simple — thin client |
| Best Use | Enterprise, SIP trunking, cloud | Legacy video conferencing | Cisco IP phones with CUCM |
3. Media Protocols — RTP, RTCP & SRTP
Once signaling has set up a call, the actual voice audio travels using a completely separate protocol stack. RTP (Real-time Transport Protocol, RFC 3550) carries the encoded voice samples in UDP datagrams — using even-numbered UDP ports (dynamically negotiated via SDP, typically in the range 16384–32767 on Cisco platforms).
RTP
Carries encoded voice/video payload. Contains sequence numbers (detect loss/reorder) and timestamps (drive jitter buffer). Uses even UDP ports.
UDP port 16384–32767
RTCP
Control companion to RTP. Reports statistics: packet loss, jitter, round-trip time. Enables real-time monitoring of call quality without packet capture.
RTP port + 1 (odd)
SRTP
Secure RTP — encrypts voice payload using AES-128. Requires key exchange via SDES (in SDP) or DTLS-SRTP. Mandatory for compliance-regulated industries.
AES-128 / HMAC-SHA1
RTP Header Structure
! RTP Header Fields (12 bytes minimum): Version (2b) | Padding | Extension | CSRC Count | Marker | Payload Type (7b) Sequence Number (16b) — detect loss, enable reordering Timestamp (32b) — drive jitter buffer playout SSRC (32b) — unique stream identifier ! Common RTP Payload Types: PT 0 = G.711 μ-law (PCMU) — North America PT 8 = G.711 A-law (PCMA) — Europe/International PT 18 = G.729 — compressed voice PT 34 = H.263 — video PT 96+ = Dynamic — negotiated via SDP
4. Voice Codecs — G.711, G.729 & Codec Selection
A codec (coder-decoder) defines the algorithm used to compress and decompress voice audio. Codec selection is one of the most important decisions in a VoIP deployment — it directly determines call quality, bandwidth consumption, and transcoding requirements when calls cross network boundaries.
| Codec | Bitrate | MOS | BW w/ Overhead | Best Use Case |
|---|---|---|---|---|
| G.711 μ-law | 64 kbps | 4.1 | ~87 kbps | LAN, high-quality calls, North America/Japan |
| G.711 A-law | 64 kbps | 4.1 | ~87 kbps | LAN, high-quality calls, Europe/International |
| G.729 | 8 kbps | 3.92 | ~24 kbps | WAN links, low bandwidth connections |
| G.722 | 64 kbps | 4.5 | ~87 kbps | HD voice — wideband audio (7kHz) on Cisco IP phones |
| Opus | 6–510 kbps | 4.5+ | Variable | WebRTC, Webex, modern cloud UC platforms |
⚠ Transcoding: When two endpoints negotiate different codecs (e.g., G.711 LAN phone calls a G.729 WAN endpoint), a transcoder (hardware DSP or software) must convert between them in real time. Transcoding adds latency and consumes DSP resources. Always design your dial plan to avoid unnecessary transcoding — use a consistent codec within each network region.
5. Cisco CUCM — Call Manager Architecture
Cisco Unified Communications Manager (CUCM) is the enterprise-grade IP-PBX at the core of Cisco collaboration deployments. CUCM handles call processing, device registration, dial plan enforcement, conferencing, call coverage, and integration with voicemail (Unity Connection), presence (IM&P), and video infrastructure.
CUCM Cluster Architecture
Key CUCM Objects You Must Know
6. Dial Plans — Route Patterns, Route Groups & Translation
The dial plan is the logic that determines how a dialed digit string is interpreted and routed to its destination. A well-designed dial plan is invisible to users — calls just work. A poorly designed one generates complaints, misdials, and expensive PSTN calls that should have been internal.
CUCM Dial Plan Hierarchy
Translation Patterns & Digit Manipulation
Translation patterns transform dialed digits before matching them against route patterns or sending them out a gateway. Digit manipulation happens via Called Party Transformations and Calling Party Transformations on gateways and trunks.
! CUCM Route Pattern wildcards: X = any single digit (0-9) ! = one or more digits (greedy) [0-9] = range of digits [^5] = any digit except 5 . = zero or more digits (wildcard) @ = all PSTN patterns (North America) ! Common route patterns: 1XXX → 4-digit internal extension (1000-1999) 9.1[2-9]XX[2-9]XXXXXX → 10-digit PSTN (preceded by 9) 9.011! → International calls 9.1900! → Block 900 numbers ! CUBE digit manipulation (IOS): ! Strip leading 9 before sending to PSTN dial-peer voice 10 voip destination-pattern 9T session target ipv4:10.0.0.1 num-exp 9 none ! remove leading 9 ! OR use translation rules: voice translation-rule 1 rule 1 /^9\(.*\)/ /\1/ ! strip leading 9 voice translation-profile STRIP-9 translate called 1 dial-peer voice 10 voip translation-profile outgoing STRIP-9
7. QoS for Voice & Video
QoS (Quality of Service) is not optional for voice — it is mandatory. Voice traffic is latency-sensitive and loss-intolerant, but individual voice streams are relatively low bandwidth. Without QoS, a single large file transfer can destroy call quality by filling router queues and dropping voice packets. QoS gives voice a first-class seat in the queue, regardless of other traffic.
DSCP Marking Standards for Collaboration
| Traffic Type | DSCP Value | DSCP Name | PHB | Queue Class |
|---|---|---|---|---|
| Voice (RTP) | 46 (101110) | EF | Expedited Forwarding | Priority Queue (LLQ) |
| Video (Interactive) | 34 (100010) | AF41 | Assured Forwarding | Bandwidth Queue |
| Call Signaling (SIP) | 24 (011000) | CS3 | Class Selector | Signaling Queue |
| Network Control (SCCP) | 48 (110000) | CS6 | Class Selector | Network Control |
| Best Effort Data | 0 | BE / DF | Default | Default Queue |
! ── MQC QoS for Voice on WAN Interface ── ! Step 1: Classify voice and signaling traffic class-map match-any VOICE-RTP match dscp ef ! Already marked EF by phones class-map match-any CALL-SIGNALING match dscp cs3 class-map match-any VIDEO match dscp af41 ! Step 2: Policy — LLQ (priority) for voice, bandwidth for video policy-map WAN-EGRESS-QOS class VOICE-RTP priority percent 30 ! LLQ — strict priority, max 30% BW class CALL-SIGNALING bandwidth percent 5 class VIDEO bandwidth percent 25 class class-default fair-queue bandwidth percent 40 ! Step 3: Apply to WAN interface (outbound) interface Serial0/0 service-policy output WAN-EGRESS-QOS ! Mark voice at the access layer (if phones don't self-mark) interface GigabitEthernet0/1 mls qos trust dscp ! Trust phone's DSCP markings ! OR use auto QoS for IP phones: auto qos voip cisco-phone
8. Cisco CUBE — Border Element & SIP Trunking
Cisco CUBE (Cisco Unified Border Element) is a back-to-back user agent (B2BUA) that sits at the boundary between an enterprise network and a SIP service provider. It terminates SIP sessions from the ITSP (Internet Telephony Service Provider) and re-originates them toward the internal CUCM — providing security, interoperability, and protocol normalization at the SIP trunk boundary.
Why CUBE is Critical
- Security boundary — ITSP never sees internal IP topology
- SIP normalization — fixes header incompatibilities between CUCM and ITSP
- Codec transcoding — converts between G.711 and G.729 at the border
- DTMF interworking — converts between RFC 2833, SIP INFO, in-band
- CAC — limits concurrent calls on the SIP trunk
CUBE Traffic Flow
ITSP SIP Trunk
↓ (public SIP — UDP/TLS 5060/5061)
CUBE (B2BUA)
↓ (internal SIP trunk)
CUCM Subscriber
↓
IP Phone / Endpoint
! ── CUBE Basic SIP Trunk Configuration ── ip routing voice service voip ip address trusted list ipv4 203.0.113.0 255.255.255.0 ! Trust ITSP IP range allow-connections sip to sip ! Enable B2BUA mode sip bind control source-interface GigabitEthernet0/0 bind media source-interface GigabitEthernet0/0 ! Dial peer TOWARD ITSP (inbound from ITSP) dial-peer voice 100 voip description ITSP-INBOUND session protocol sipv2 session transport udp incoming called-number . ! Match all inbound voice-class codec 1 dtmf-relay rtp-nte ! Dial peer TOWARD CUCM (forward call in) dial-peer voice 200 voip description CUCM-INBOUND destination-pattern .T session protocol sipv2 session target ipv4:10.10.10.10 ! CUCM subscriber IP voice-class codec 1 dtmf-relay rtp-nte ! Outbound to ITSP (from CUCM) dial-peer voice 300 voip description CUCM-TO-ITSP destination-pattern 9T session protocol sipv2 session target ipv4:203.0.113.1 ! ITSP SIP proxy voice-class codec 1 dtmf-relay rtp-nte ! Verification show call active voice show sip-ua calls show voice call summary
9. PSTN Integration — Gateways & PRI/BRI
Before SIP trunking became universal, enterprises connected to the PSTN through TDM (Time Division Multiplexing) gateways using ISDN PRI or BRI circuits. Many enterprises still use TDM gateways as primary or backup PSTN access — and they are heavily tested on CCNA and CCNP exams.
PRI — Primary Rate Interface
T1-PRI (North America): 23 Bearer (B) channels + 1 Data (D) signaling channel = 24 channels. Max 23 simultaneous calls.
E1-PRI (Europe): 30 B channels + 2 D channels = 32 channels. Max 30 simultaneous calls.
T1 = 1.544 Mbps | E1 = 2.048 Mbps
BRI — Basic Rate Interface
2 B channels (64 kbps each) + 1 D channel (16 kbps) = 2B+D. Maximum 2 simultaneous calls. Used for small offices and SOHO — rarely deployed for new installations but still appears on exams and in existing installations.
Total BW = 144 kbps (2×64 + 16)
! ── T1-PRI Gateway Configuration (IOS) ── controller T1 0/0/0 framing esf ! Extended Superframe linecode b8zs ! B8ZS line coding for T1 pri-group timeslots 1-24 ! ISDN interface auto-created as Serial0/0/0:23 (D-channel) interface Serial0/0/0:23 isdn switch-type primary-ni ! National ISDN (most common in US) isdn incoming-voice voice ! Dial peer for inbound PSTN calls dial-peer voice 1 pots description PSTN-INBOUND incoming called-number . ! Match all inbound direct-inward-dial ! Pass DID digits to CUCM port 0/0/0:23 ! Dial peer for outbound PSTN calls dial-peer voice 2 pots description PSTN-OUTBOUND destination-pattern 9T ! 9 + any number forward-digits all ! Send all digits after 9 port 0/0/0:23 ! Verification show controllers T1 0/0/0 show isdn status show voice port 0/0/0:23
10. Cisco Unity Connection — Voicemail & Auto Attendant
Cisco Unity Connection (CUC) is Cisco's unified messaging platform — providing voicemail, automated attendant (AA), interactive voice response (IVR), and speech-to-text transcription. It integrates tightly with CUCM via SIP trunk and SCCP, presenting voicemail as just another call forwarded when a phone is busy or unanswered.
CUC's Call Handler objects provide the auto attendant logic — playing greetings, routing keypad inputs (1 for sales, 2 for support), and transferring to extensions or operators. Interview Handlers record multi-question responses for call-backs or surveys. Directory Handlers allow callers to spell a name and be connected automatically.
11. Cisco Webex & Cloud Collaboration
Cisco Webex is Cisco's cloud-native unified communications and collaboration platform — providing meetings, messaging, calling, contact center, and devices in a single integrated cloud service. For enterprises, Webex represents the evolution from on-premises CUCM deployments toward cloud-hosted or hybrid collaboration architectures.
☁ Webex Calling (Cloud UCaaS)
Replaces on-premises CUCM entirely. Phones register to Cisco's cloud infrastructure. PSTN connectivity via Cisco-provided trunks (CCP) or customer-provided SIP trunks (CCPP). Managed entirely via Webex Control Hub — no on-premises call processing hardware.
⚙ Webex for On-Premises (Hybrid)
Cisco Expressway (previously VCS) enables hybrid scenarios — on-premises CUCM phones register and participate in Webex meetings. Expressway-C (inside DMZ) + Expressway-E (internet-facing) create a secure traversal path for remote endpoints without VPN.
Expressway — Mobile Remote Access (MRA)
MRA allows Cisco IP phones and Jabber clients to register to on-premises CUCM from outside the corporate network — without VPN. Expressway provides a secure traversal zone. Critical for modern remote work deployments.
Webex Meetings Architecture
Webex uses a media relay architecture — audio/video flows through Webex Media Nodes (distributed globally). TURN servers handle firewall traversal. Webex supports up to 100,000 participants in a webcast and provides end-to-end encryption for meetings.
12. Exam Tips & Quick-Reference Table
| Topic | Key Fact / Number | Common Exam Trap |
|---|---|---|
| G.711 Bandwidth | 64 kbps codec + ~23 kbps overhead = ~87 kbps per call | Always calculate with headers — 64 kbps alone is never the right answer |
| G.729 Bandwidth | 8 kbps codec + ~16 kbps overhead = ~24 kbps per call | G.729a is a lower-complexity variant — same quality, less CPU |
| SIP Default Ports | UDP/TCP 5060 (SIP) | TLS 5061 (SIPS) | SIP uses port 5060 — not 5004 (that is SRTP) or 5080 |
| RTP Port Range | 16384–32767 (Cisco default) — always even ports | RTCP uses RTP port +1 (odd port). RTP and RTCP are never the same port. |
| Voice DSCP | RTP = EF (46) | Signaling = CS3 (24) | Video = AF41 (34) | Voice uses EF not CS5 — CS5 is for call signaling in some legacy configs |
| Delay Targets | One-way <150ms (recommended) | <400ms (maximum) | These are one-way — not round-trip. RTT for voice is <300ms recommended |
| T1-PRI Channels | 23B + 1D = 23 simultaneous calls max | E1-PRI = 30B + 2D = 30 calls. T1 total channels = 24, E1 = 32 |
| CUCM Route Pattern | ! = one or more digits | X = exactly one digit |
9.! uses the inter-digit timer — T suffix forces immediate timer |
| CUBE Function | B2BUA — terminates and re-originates SIP sessions | CUBE is NOT a proxy — it is a back-to-back user agent (creates two separate call legs) |
| SRST Purpose | Branch phones register to local router when WAN/CUCM fails | SRST phones get reduced features — no voicemail, no CUCM features during fallback |
Master Checklist — Before Your CCNA/CCNP Exam
☑ Explain PCM digitization: sampling (8000/s), quantization (8-bit), encoding
☑ Define delay, jitter, and packet loss targets for voice
☑ Trace a complete SIP INVITE call flow from UAC to UAS
☑ Differentiate SIP, H.323, and SCCP use cases and ports
☑ Calculate G.711 and G.729 bandwidth including headers
☑ Explain CUCM Publisher vs Subscriber roles
☑ Configure a CUCM dial plan: Route Pattern → Route List → Route Group
☑ Apply QoS MQC policy with LLQ for voice (DSCP EF) on WAN
☑ Configure a CUBE SIP trunk with dial peers toward ITSP and CUCM
☑ Configure a T1-PRI gateway with POTS dial peers
☑ Explain Unity Connection call flow: forward → pilot → mailbox
☑ Describe SRST fallback and Expressway MRA for remote endpoints
Tags
