How to Assign Extensions to Cisco Phones in Packet Tracer

Cisco Packet Tracer is one of the most widely used network simulation tools for learning voice over IP (VoIP) and telephony concepts. Assigning extensions to Cisco IP phones within Packet Tracer involves configuring a Cisco CallManager Express (CME) router to register phones and dial plans. Understanding the full process — and where configuration choices diverge — helps you build a working lab or troubleshoot an existing one.

What "Assigning an Extension" Actually Means

In a real or simulated Cisco telephony environment, an extension is a short internal number assigned to a specific IP phone. When someone dials that number from another phone on the same system, the call routes directly to that device.

In Packet Tracer, phones don't self-configure. The CME router acts as the call processing engine. It tells each phone what number it owns, what codec to use, and how to reach other phones. The phone itself is a relatively passive endpoint — it registers with the router using the SCCP (Skinny Client Control Protocol) and receives its configuration from there.

The Core Configuration Flow

Assigning extensions in Packet Tracer follows a consistent sequence regardless of how many phones you're working with.

Step 1: Set Up the Network Topology

Before any telephony configuration, your physical (or simulated) topology needs to be correct:

• Connect Cisco IP phones (typically the 7960 model in Packet Tracer) to a switch
• Connect the switch to a router that will run CME
• Ensure the router interface connecting to the phone network is up/up

Step 2: Configure DHCP on the Router

IP phones need an IP address to register. Configure a DHCP pool on the router with the option 150 setting, which points phones to the TFTP server address (the router itself in most lab setups):

ip dhcp pool VOICE network 192.168.1.0 255.255.255.0 default-router 192.168.1.1 option 150 ip 192.168.1.1 

Option 150 is the critical piece — without it, phones won't know where to download their configuration, and they won't register.

Step 3: Enable Telephony Service (CME)

On the router, enter telephony-service configuration mode:

telephony-service max-ephones 5 max-dn 10 ip source-address 192.168.1.1 port 2000 auto assign 1 to 5 

• max-ephones sets the maximum number of physical phones the system will support
• max-dn sets the maximum number of directory numbers (extensions)
• ip source-address tells the CME where to listen for phone registrations
• auto assign automatically maps directory numbers to phones as they register 🔧

Step 4: Create Directory Numbers (Extensions)

Each extension is defined using the ephone-dn command:

ephone-dn 1 number 1001 ephone-dn 2 number 1002 ephone-dn 3 number 1003 

The number following ephone-dn is the internal identifier for that directory number slot. The value after number is the actual dialable extension — what a user dials to reach that phone.

Step 5: Assign Directory Numbers to Physical Phones

Each physical phone is represented by an ephone entry, typically matched by its MAC address in real deployments. In Packet Tracer, auto-assignment often handles this, but manual assignment looks like:

ephone 1 mac-address xxxx.xxxx.xxxx type 7960 button 1:1 

The button 1:1 line maps button 1 on the physical phone to ephone-dn 1 (which holds extension 1001). This is where the physical device and the logical extension connect.

Variables That Affect How This Works 📋

Not every Packet Tracer lab produces the same result with identical commands. Several factors shape what works and what doesn't:

Common Registration Problems and What They Mean

If a phone shows "Configuring IP" indefinitely, the DHCP pool is likely misconfigured or the option 150 address is wrong. If it shows "Registering" but never completes, the ip source-address in telephony-service is likely pointing to the wrong interface or port.

If phones register but can't call each other, the ephone-dn numbers may not be assigned, or the button mapping under each ephone may be missing.

Using show ephone registered and show telephony-service in Packet Tracer's CLI gives you a fast view of what the router actually sees — which phones are registered, which directory numbers are active, and whether the configuration matches your intent.

How Complexity Scales With Lab Size 🖥️

A two-phone lab is straightforward — two ephone-dns, two ephones, one switch, one router. But as labs grow to simulate full office environments, the configuration surface expands:

• Multiple VLANs require inter-VLAN routing and switch port configuration
• Dial peers become relevant when simulating calls between different CME routers
• Codec settings (G.711 vs G.729) affect simulated call quality behavior
• Hunt groups and shared lines require dual-line ephone-dn configurations

The same core extension assignment logic applies at every scale — but the dependencies multiply. A misconfigured trunk between two routers won't prevent local extensions from working, but it will break any cross-site dialing.

Whether your lab involves two phones testing basic connectivity or a multi-site topology simulating a branch office setup, the configuration decisions that matter most depend on what you're actually trying to simulate — and how closely your Packet Tracer version supports the CME feature set you need.