Core Issue
The phone is unable to contact the Cisco CallManager server for its application.
Resolution
To resolve this issue, perform these steps:
- Make sure port 80 is reachable from the phone's subnet. PIX Firewalls have been known to create this error. Make sure the user has a primary extension selected in the User Information > Device Association screen.
- Refer to these Cisco bug IDs:
- CSCdv13176: Messages button with handset offhook generates host not found. For a workaround, press the message button without lifting the handset off the hook.
- CSCdz47626: IP Phone Services button gives err: host not found after reload. For a workaround, power cycle the phone.
- CSCdx69898: Tomcat Webserver Port Number is stated incorrectly. For a workaround, use the port number 6293 for the IP phone service in Cisco CallManager.
- CSCdz40113: Internet Information Server (IIS) stops responding and needs to be reset. For a workaround, reset the web server (IIS).
- CSCdz56517: CCMUser logon authentication fails when using Active Directory (AD). For a workaround, reset the web server (IIS).
- CSCdx47467: App engine is not starting because Remote Method Invocation (RMI) port 1099 is being used by the Attendant Console. For a workaround, move the application server or attendant console to another machine.
- CSCdx24601: Extensible Markup Language (XML) service GET fails when URL contains authentication. For a workaround, do not use the authentication.
Problem Type
IP phones and other clients (Client registration, faulty IP phone, etc.)
Call control software (CallManager, CallManager Express, ICS7750, SRST, SS7 call agents)
Call Control
CallManager
IP Phones and Clients
IP phone error messages
IP phone faulty operation
Failure Type
Bad operational behavior
Error message
Cannot request a service
When Problem Occurs
When pressing services button
End Where Problem is Heard or Device Type Involved
IP phone
Bug ID Number
CSCdz56517
CSCdx47467
CSCdz40113
IP Phone Errors
Host Not Found
IP Phone Components
Services button
