A P P E N D I X B

Case Study: Troubleshooting

Cisco Unified IP Phone Calls

This appendix contains two case studies:

Troubleshooting Intracluster Cisco Unified IP Phone Calls

Troubleshooting Intercluster Cisco Unified IP Phone Calls

Troubleshooting Intracluster Cisco Unified IP Phone Calls

The case study in this section discusses in detail the call flow between two Cisco Unified IP Phones within a cluster, called an intracluster call. This case study also focuses on Cisco Unified CallManager and Cisco Unified IP Phone initialization, registration, and keepalive processes. A detailed explanation of an intracluster call flow follows the discussion. The explanation of the processes are explained using the trace utilities and tools discussed in Chapter 2, “Troubleshooting Tools.”

This section contains the following topics:

Sample Topology

Cisco Unified IP Phone Initialization Process

Cisco Unified CallManager Initialization Process

Self-Starting Processes

Cisco Unified CallManager Registration Process

Cisco Unified CallManager KeepAlive Process

Cisco Unified CallManager Intracluster Call Flow Traces

Sample Topology

Given that you have two clusters named Cluster 1 and Cluster 2, the two Cisco Unified CallManagers in Cluster 1 are called Unified CM3 and Unified CM4, while the two Cisco Unified CallManagers in Cluster 2 are called Unified CM1 and Unified CM2.

The traces collected for this case study come from Unified CM1, which is located in Cluster 2, as shown in Figure B-1. The basis for the call flow are the two Cisco Unified IP Phones in Cluster 2. The IP addresses of these two Cisco IP Phones are 172.16.70.230 (directory number 1000) and 172.16.70.231 (directory number 1001), respectively.

Troubleshooting Guide for Cisco Unified CallManager Release 5.0(2)

 

OL-9420-01

B-1

 

Page 1
Image 1
Cisco Systems OL-9420-01 appendix Case Study Troubleshooting Cisco Unified IP Phone Calls, Sample Topology