Cisco Extension Mobility issue – “no service configured”

If you support a company that uses Cisco Extension mobility then you will at some point come across a If you support a Cisco Unified Communications environment that uses Extension Mobility (EM), you will eventually run into a phone that displays:

“No Services Configured”

This usually appears when a user presses the Services button to log in to Extension Mobility—and it almost always causes confusion, especially when:

• Extension Mobility works fine on every other phone
• The phone is registered in CUCM
• The service is correctly configured at an organisational level
• Nothing “recently changed” (at least according to the change log)

In theory, this error should be simple—just subscribe the phone to the Extension Mobility service.
In reality, that’s only the first layer of troubleshooting.

This article assumes:

• Extension Mobility is already configured correctly
• Other phones work as expected
• The problem is isolated to one or a small number of phones

From real-world experience, when you see this error on a single device, the issue is almost always trust, cache, or firmware-related, not configuration.

Quick Sanity Checks (Before You Go Deeper)

Before jumping into advanced troubleshooting, confirm the basics:

• ✔ Extension Mobility service is running under Cisco Unified Serviceability
• ✔ Phone is registered successfully with CUCM
• ✔ Phone is enabled for Extension Mobility
• ✔ Device profile exists and works on other phones
• ✔ Extension Mobility service is subscribed on the phone or device profile

If all of the above are true and the phone still shows “No Services Configured”, keep reading.

Understanding Why This Error Occurs

From years of supporting Cisco voice environments, this issue usually comes down to one of the following:

1. Outdated or corrupted trust (ITL) files
2. CUCM node changes that weren’t fully accepted by the phone
3. Firmware inconsistencies
4. Cached service data on the handset
5. Failed secure service negotiation

What’s important to understand is that Cisco IP phones are very stateful devices.
They don’t just pull config once—they cache trust relationships, services, and certificates.

When that trust breaks, services silently fail.

Solution 1: Delete the Phone’s ITL (Trust) File

This is by far the most common and least disruptive fix.

When This Fix Works Best

If the affected phone also shows symptoms like:

• Corporate directory missing
• Missed/placed calls not appearing
• Ringtones missing
• Services button not responding
• EM login screen failing

…then you’re almost certainly dealing with a trust list issue.

What Is the ITL File and Why It Breaks Things

The ITL (Initial Trust List) file contains:

• CUCM node certificates
• Trust relationships between phone and cluster
• Secure service validation data

If:

• A CUCM node was replaced
• A hostname changed
• Certificates were regenerated
• A phone was moved between clusters
• A phone sat powered off during an upgrade

…the ITL file can contain outdated CUCM entries, causing services to fail—even though registration still works.

How to Delete the ITL File on a Cisco IP Phone

On the affected phone:

1. Press the Settings button
2. Navigate to Security Configuration
3. Select Trust List
4. Review the ITL entries
   • You’ll often see references to old CUCM node names
5. Erase the ITL file using the keypad sequence:

**#
More → Erase

⚠️ The exact menu wording can vary slightly by phone model.

The ITL showed entries with an old CUCM node name.

What Happens Next

• The phone reboots
• It pulls a fresh ITL file from CUCM
• Trust is re-established
• Services repopulate

In most cases, the Services button immediately works again, and Extension Mobility login appears as expected.

Solution 2: Factory Reset the Cisco IP Phone

If deleting the ITL file doesn’t resolve the issue, the next step is a full factory reset.

This sounds extreme, but in practice it’s very safe—and often faster than chasing obscure cache issues.

When a Factory Reset Is Required

I usually go straight to this step if:

• The phone has been redeployed multiple times
• Firmware was upgraded recently
• The phone was previously used in another cluster
• The handset behaves inconsistently
• ITL deletion didn’t help

A factory reset forces the phone to:

• Erase firmware
• Clear all cached config
• Re-download everything from CUCM

How to Factory Reset a Cisco IP Phone (Most Models)

1. Unplug the power cable (or network cable if PoE)
2. Plug it back in
3. While the phone is booting, before the Speaker button flashes, press and hold #
4. Continue holding # until all line buttons flash orange in sequence
5. Release #
6. Enter the following sequence:

123456789*0#

What to Expect During Reset

• Line buttons flash orange, then green
• Firmware is erased
• Phone reboots multiple times
• Process can take several minutes

Once complete:

• The phone re-registers with CUCM
• Pulls the correct device configuration
• Services repopulate
• Extension Mobility becomes available again

Additional Real-World Tips from the Field

Tip 1: Check Secure Service Mode

If your cluster uses mixed or secure mode, Extension Mobility relies heavily on certificate trust.
Any mismatch can break services while calls continue to work.

Tip 2: Compare a Working Phone

Compare the following between a working and non-working phone:

• Firmware version
• Device pool
• Phone load
• Trust list entries

Differences here often reveal the root cause quickly.

Tip 3: Avoid Reusing Phones Without Resetting

Phones that move between:

• Sites
• Clusters
• Device pools

…should always be factory reset. Skipping this step causes long-term service issues.

Preventing This Issue in the Future

To reduce recurring Extension Mobility problems:

• Standardise phone firmware versions
• Reset phones before redeployment
• Document CUCM certificate changes
• Avoid unnecessary hostname changes
• Periodically audit ITL trust consistency

In large environments, most EM issues are lifecycle problems, not configuration mistakes.

Final Thoughts: Why This Error Is Misleading

The message “No Services Configured” implies:

• A missing subscription
• A configuration error
• An admin oversight

In reality, it usually means:

• The phone no longer trusts CUCM

Once you understand that, troubleshooting becomes faster and far less frustrating.

If you support Cisco UC long enough, this becomes one of those fixes you perform instinctively—and now you have a documented, repeatable approach.mware of the IP Phone will be erased. Once complete, the extension mobility feature will then be available.

Daniel Lutton

From my early days on the helpdesk through roles as a service desk manager, systems administrator, and network engineer, I’ve spent more than 25 years in the IT world. As I transition into cyber security, my goal is to make tech a little less confusing by sharing what I’ve learned and helping others wherever I can.