Cisco Emergency Responder 8.6 Troubleshooting Guide
Troubleshooting Cisco Emergency Responder System Problems
Downloads: This chapterpdf (PDF - 336.0KB) The complete bookPDF (PDF - 1.24MB) | Feedback

Troubleshooting Cisco Emergency Responder System Problems

Table Of Contents

Troubleshooting Cisco Emergency Responder System Problems

Emergency Responder Intra-Cluster Call Routing Fails

Emergency Responder Exits After Starting

Emergency Responder Groups In Cluster Screen Does Not Load


Troubleshooting Cisco Emergency Responder System Problems


This chapter covers topics that help you troubleshoot issues you might encounter with general operation of the Cisco Emergency Responder (Emergency Responder) system and the configuration screens that involve the Emergency Responder server, group, and cluster:

Emergency Responder Intra-Cluster Call Routing Fails

Emergency Responder Exits After Starting

Emergency Responder Exits After Starting

Emergency Responder Groups In Cluster Screen Does Not Load

Emergency Responder Intra-Cluster Call Routing Fails

You might encounter the following issue when routing calls between clusters.

Symptom    Emergency Responder intra-cluster call routing fails or Emergency Responder does not discover phones correctly.

Recommended Action    Ensure that all the Emergency Responder servers in an Emergency Responder cluster can be found by their host name, and ensure that all are reachable on the network by all the other Emergency Responder servers.

Recommended Action    Ensure that all the Emergency Responder servers can reach the Emergency Responder cluster DB host and that the cluster DB password is the same across all servers in the cluster.

Emergency Responder Exits After Starting

You might encounter the following issue when starting Emergency Responder.

Symptom    Emergency Responder exits after starting.

Possible Cause    You have configured Emergency Responder to use a TCP port that is already in use.

Recommended Action    Check the Windows Event Viewer for the message "CER could not open socket at port peer-tcp-port, Exiting." If you see this message, change the Emergency Responder group configuration to use a different TCP port. See the Configuring a Cisco Emergency Responder Server Group section in the Cisco Emergency Responder 8.6 Administration Guide for instructions.

Emergency Responder Groups In Cluster Screen Does Not Load

You might encounter the following issue when working with Emergency Responder groups in a cluster.

Symptom    The Emergency Responder Groups in Cluster screen does not load, and exhibits the error "Cannot connect to cluster DB host."

Recommended Action    Ensure that the cluster DB host can be found by host name.

Ensure that the specified cluster db host password is the same across all Emergency Responder server groups in the cluster.

For more information, see the 8.6 Cisco Emergency Responder Cluster and Cluster DB Host section in the Cisco Emergency Responder 8.6 Administration Guide.

Related Topics

Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster, page 8-1

Starting And Stopping A Cisco Emergency Responder Server, page 10-1

Viewing Event Messages, page 14-1

Managing Performance, page 15-1

Backing Up And Recovering Data, page 17-1