Why Won't My IP Phones Register in Cisco Packet Tracer? (VoIP Troubleshooting)

You configured Call Manager Express, created the directory numbers, and the IP phone still won't come up — blank screen, stuck on "Configuring IP," or registered but no dial tone. VoIP failures in Cisco Packet Tracer almost always trace to one of four layers, and they fail in a specific order: power → IP → registration → calls. Work them in that order and the problem usually falls out in a minute.

Bottom line: a dead phone is a PoE/power problem; a phone stuck on "Configuring IP" is a DHCP option 150 problem; a phone with a number but no calls is a CME or dial-peer problem. Check them in that sequence. If you'd rather not hunt, NetPilot imports a broken VoIP .pkt, finds the exact layer that's off, fixes it, and explains what was wrong — in about two minutes.

The phone screen is blank — no power

If the phone shows nothing at all, it isn't getting power. IP phones in Packet Tracer are powered over Ethernet:

Connect the phone to a PoE-capable switch. In Packet Tracer the 3560 supplies PoE; the common 2960 does not, so a phone on a 2960 port stays dark.
On a non-PoE switch, add a power adapter to the phone (its Physical tab) instead.
Give it a few seconds after cabling; the phone boots, then starts looking for an address.

Stuck on "Configuring IP" — DHCP / option 150

If the screen shows "Configuring IP" forever, the phone either isn't getting an address or isn't being told where the call server is:

Confirm DHCP is reachable and the pool covers the voice subnet. The phone needs a valid address first.
Confirm option 150 is in the DHCP pool, pointing at the CME router's voice interface:

ip dhcp pool VOICE
 network 192.168.10.0 255.255.255.0
 default-router 192.168.10.1
 option 150 ip 192.168.10.1

Option 150 is the number-one cause of "the phone has an IP but never registers." Without it the phone has no idea where Call Manager is, so it can't download its configuration or get an extension. If the phone reaches an IP and stalls, this is almost always why.

Has an IP but no number — CME registration

If the phone gets an address but never shows an extension, registration to Call Manager Express is failing:

Check ip source-address under telephony-service — it must be the router's voice interface address, on port 2000. If it points at the wrong interface, phones can't register.
Check max-ephones / max-dn — if they're lower than the number of phones/lines, CME silently refuses the extras. Raise them.
Confirm auto assign (or a manual ephone/button binding) so directory numbers actually attach to phones.

Verify what CME sees:

show ephone
show telephony-service

show ephone lists registered phones and their status — if a phone isn't there, it never registered, and you're back to power or option 150.

Registers fine, but calls between sites fail — dial-peers

If two phones on the same router call fine but a call to the other site fails, the problem is dial-peer routing, not registration:

Each router needs a VoIP dial-peer for the remote numbers, with a destination-pattern that matches them and a session target ipv4: pointing at the other router.
Confirm IP connectivity between the routers (ping the remote voice interface) — dial-peers can't route a call over a path that isn't there.
Check the destination-pattern actually matches the dialed digits — 2... matches a four-digit number starting with 2; a mismatch means the call never leaves the router.

Let the AI find the layer for you

VoIP failures are tedious because the phone gives you almost no feedback — a blank screen and "Configuring IP" cover four different root causes. Upload the broken file to NetPilot:

"Here's my Packet Tracer VoIP lab — the phones won't register. Find what's wrong and fix it."

It reads the .pkt, identifies which layer is broken (PoE, option 150, CME registration, or dial-peers), corrects it, explains in plain English what was wrong and why, and hands you a working .pkt back. You learn the failure mode instead of guessing — and next time you'll spot it yourself. No download, no NetAcad account, all in your browser.

FAQ

My IP phone screen is completely blank in Packet Tracer — what's wrong?

A blank screen means no power. IP phones draw power over Ethernet, so connect the phone to a PoE-capable switch (in Packet Tracer the 3560 supplies PoE; the 2960 does not) or add a power adapter on the phone's Physical tab. A phone on a non-PoE port with no adapter never boots, which is the most common reason it appears completely dead.

Why is my Packet Tracer phone stuck on "Configuring IP"?

The phone either can't get a DHCP address or isn't being told where the call server is. Verify the DHCP pool covers the voice subnet, then confirm it includes option 150 ip <CME-address> — without option 150 the phone gets an IP but can't locate Call Manager Express, so it stalls before registering.

How do I check whether an IP phone registered to CME in Packet Tracer?

Run show ephone on the CME router — it lists each registered phone and its status. show telephony-service shows your ip source-address, max-ephones, and max-dn settings. If a phone isn't in the show ephone output, it never registered, so go back and check power and DHCP option 150 first.

My phones call each other but calls to the other site fail — why?

That's a dial-peer problem, not registration. Each router needs a VoIP dial-peer whose destination-pattern matches the remote extensions and whose session target ipv4: points at the other router, and the two routers must have IP connectivity. If same-site calls work but inter-site calls don't, check the dial-peer pattern and ping the remote voice interface.

Stuck on a phone that won't register? Upload your lab to NetPilot — it finds the broken layer, fixes it, and explains what was wrong, so you get a working .pkt and learn the failure mode.

Try NetPilot Free