All topic guides
Layer 2 SwitchingAmalgamated guide

Voice VLAN & IP Telephony

Voice VLAN, Cisco IP phones, CUCME basics, and QoS priority for voice.

How the sources were combined

jdepew88 Cisco IP Phones and CUCME is the primary source. Panagiss VLAN.md voice VLAN section adds switchport voice vlan syntax — merged for CCNA voice/security/QoS crossover.

Overview

IP phones need isolated voice VLANs, QoS trust, and DHCP Option 150 for TFTP configuration. This guide covers switchport voice VLAN, CUCME basics, and how voice ties into the QoS pipeline.

Why voice gets its own VLAN

IP phones and PCs can share one cable, but they should not share one broadcast domain for call traffic. A dedicated voice VLAN provides:

GoalMechanism
SecurityPC on data VLAN cannot easily capture phone RTP streams on a separate voice subnet
QoSVoice frames marked and queued with higher priority than best-effort data
OperationsDHCP, TFTP, and CUCM registration scoped to voice infrastructure
Info

jdepew88 notes emphasize that separating host and phone subnets prevents the PC from "listening in" on call packets. Panagiss adds the switch configuration: switchport access vlan for data + switchport voice vlan for voice.

Physical connection models

  1. Phone → switch (PC unplugged) — phone alone on access port
  2. Phone → switch, PC → phone (pass-through) — most common desk layout
  3. Phone powered by wall adapter, PoE injector, or 802.3af/at PoE from the switch

The switch port is still one access port with two logical VLAN memberships: data (untagged from PC) and voice (tagged/CDP-negotiated for phone).

Voice VLAN switch configuration

Access port with voice VLAN

interface FastEthernet0/10 description IP Phone + PC switchport mode access switchport access vlan 10 switchport voice vlan 20 mls qos trust cos

  • VLAN 10 — data subnet for the PC (switchport access vlan)
  • VLAN 20 — voice subnet for the phone (switchport voice vlan)
  • Phone discovers voice VLAN via CDP (Cisco) or LLDP-MED (multi-vendor)
Tip

Enable QoS trust on phone ports so CoS/DSCP markings from the phone are honored — voice stays prioritized through the campus.

Cisco IP phone boot process

Understanding phone startup helps you troubleshoot "phone gets IP but won't register" scenarios:

  1. Power on — wall power, injector, or PoE/POE+ from switch PSE
  2. Load stored image and last-known config from flash
  3. Learn VLAN — switch advertises voice VLAN via CDP/LLDP-MED
  4. DHCP — phone requests address on voice VLAN; Option 150 points to TFTP server
  5. Download config/firmware from TFTP
  6. Register with call manager — CUCM (enterprise) or CUCME (router-embedded) via SCCP or SIP
  7. Softkey template download (SCCP environments)
Warning

Missing DHCP Option 150 (TFTP server IP) is a common lab exam trap — phone has an IP but cannot download config or register.

Power over Ethernet (PoE)

Phones are powered devices (PD); switches are power sourcing equipment (PSE).

StandardPowerNotes
Cisco pre-standard~6.3 WProprietary early implementation
802.3af (PoE)15.4 W (Class 3)Multi-vendor interoperability
802.3at (PoE+)30 WHigh-end phones, APs, cameras
POE Classes

802.3af PoE classes — switch negotiates power budget with the powered device.

From study charts · jdepew88 CCNA notes

Discovery: PSE sends low voltage and expects 25 kΩ signature resistance. Cisco historically used Fast Link Pulse (FLP) to detect PoE-capable phones vs PCs.

Mid-span power injectors add PoE when the switch lacks PoE — useful in retrofit deployments.

CUCME vs CUCM (CCNA scope)

PlatformRole
CUCM (Call Manager)Enterprise centralized call control; phones register to cluster
CUCME (Express)IOS-based call control on a router — common in CCNA labs

Phones need reachability to the TFTP server and the call agent IP. Routing between voice VLAN and server subnets must work; inter-VLAN routing and ACLs must permit SCCP/SIP and RTP media ports.

QoS for voice

Voice is delay-sensitive and loss-intolerant. Campus QoS pipeline:

  1. Classify — identify voice/signaling traffic
  2. Mark — set CoS (Layer 2) or DSCP (Layer 3) — voice often EF (DSCP 46) / CoS 5
  3. Queue — prioritize voice in hardware queues
  4. Police/shape — protect voice from data bursts
QOS Reccomendations Chart

QoS recommendations — voice traffic gets strict priority queuing.

From study charts · jdepew88 CCNA notes

On the access port:

  • Phone marks voice frames with higher CoS
  • mls qos trust cos (or trust dscp) tells the switch to accept those markings
  • Queuing policies on uplinks preserve priority end-to-end
Info

Full QoS policy design spans access, distribution, and WAN — see the QoS topic for marking and queuing depth. Voice VLAN is the access-layer hook that starts the pipeline.

Port security with phone + PC

A single access port with phone and PC typically needs two MAC addresses:

Port security for phone + PC

interface FastEthernet0/10 switchport mode access switchport access vlan 10 switchport voice vlan 20 switchport port-security maximum 2 switchport port-security mac-address sticky

Without maximum 2, port security shuts down when the second MAC (PC) appears.

DHCP and voice VLAN

Voice VLAN is a separate broadcast domain — it needs its own DHCP scope on the voice subnet:

  • Voice gateway (router/SVI) on voice VLAN
  • DHCP scope for phones with Option 150 = TFTP server IP
  • DNS/NTP as required by CUCM/CUCME design

Cross-reference Switch Security if DHCP snooping protects the voice VLAN from rogue servers.

Verification commands

Voice VLAN troubleshooting

show interfaces FastEthernet0/10 switchport show vlan brief show power inline show cdp neighbors detail show mls qos interface FastEthernet0/10

Design workflow

  1. Create data and voice VLANs with separate subnets
  2. Configure access ports: switchport access vlan + switchport voice vlan
  3. Allow both VLANs on trunks to distribution/core
  4. Enable QoS trust on phone ports; mark/queue on uplinks
  5. DHCP scope on voice VLAN with Option 150
  6. Set port security maximum 2 where PC passes through phone
  7. Test: phone registers, dial tone, PC still reaches data network

Exam checklist

TrapDetail
Forgot switchport voice vlanPhone stays on data VLAN — wrong subnet/QoS
No DHCP Option 150Phone gets IP but no TFTP/config
Port security max 1Phone+PC triggers violation shutdown
QoS trust disabledPhone CoS markings ignored — voice competes with data
Voice VLAN not in trunk allowed listPhone works locally but not across switches
Confusing access vs voice VLANAccess VLAN = data; voice VLAN = overlay for phone traffic

Related lessons on this site

Continue in this domain

Layer 2 Switching · guide 4 of 4

Sources & further reading

jdepew88 CCNA Notes (markdown)

psaumur CCNA Course Notes

Additional references

This page is an amalgamated study guide synthesized from the markdown sources above, cross-checked against Cisco's official CCNA exam topics. Verify scope before your exam date.