cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
11574
Views
0
Helpful
0
Comments
TCC_2
Level 10
Level 10

Core Issue

Cisco Emergency Responder (Cisco ER) obtains a list of registered phones from Cisco CallManager and tries to locate all phones. If Cisco ER cannot locate a phone, it places the phone in the default Emergency Response Location (ERL) and puts it in a list of unlocated phones.

These are some explanations that can prevent Cisco ER from locating a phone:

  • If more than one switch port reports the phone as a Cisco Discovery Protocol (Cisco DP) neighbor, then the phone is placed in unlocated phones. This condition is corrected in the next phone tracking when only one switch port reports this phone as its Cisco DP neighbor.

Refer to the Manually Defining a Phone section of  Configuring Cisco Emergency Responder for information on configuring these types of phones if you cannot connect them to a supported device.

  • The phone is connected to a hub, which is connected to a supported switch port, but it does not support Cisco DP. Cisco ER can consistently discover Cisco DP-enabled phones attached to hubs (which are attached to supported switch ports), but cannot always track non-Cisco DP phones attached in this manner. For non-Cisco DP phones, ensure the phones are attached directly to supported switch ports.

  • The switch to which the phone is connected is currently unreachable, for example, it does not respond to Simple Network Management Protocol (SNMP) queries. These could be among the reasons:

    Unreachable switches are not retried until Cisco ER runs the next full switch-port and phone update process, unless you run it against the individual switch as described in the following list.

    • The phone has moved to a switch served by a different Cisco ER group. If this is the case, the Cisco ER group name is shown for the phone in the unlocated phones list. If the phone is not located in the next incremental phone tracking process after it is moved, the phone remains unlocated in any Cisco ER group until a full switch-port and phone update process is run.
    • The phone requires CAM-based tracking, but CAM-based tracking is not enabled on the switch to which the phone is connected. Cisco IP SoftPhone and some other phone models require CAM-based tracking. Refer to the Identifying the LAN Switches section of  Configuring Cisco Emergency Responder for information on enabling CAM-based tracking, and the Network Hardware and Software Requirements section of Planning for Cisco Emergency Responder for a list of phones requiring CAM-based tracking.

Resolution

After fixing the problems that prevent Cisco ER from locating phones, run the switch-port and phone update process on the affected switches, or on all switches:

  • To run the process on a specific switch Select Phone Tracking > LAN Switch Details and select the switch in the left-hand column; then click Locate Switch Ports.
  • To run the process on all switches Select Phone Tracking > Run Switch-Port & Phone Update.

For more details on how to resolve this issue, refer to the Too Many Unlocated Phones section of Troubleshooting Cisco Emergency Responder

For more information about troubleshooting Cisco ER, refer to these documents:

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: