Cisco Cisco Unified Operations Manager 8.0 White Paper
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 39 of 70
Creating Synthetic IP Phones in Cisco Unified Communications Manager
To define simulated phones in Cisco Unified Communications Manager for the synthetic tests, do the following:
Step 1. Launch and log in to the Cisco Unified Communications Manager Administration page.
Step 2. From the Cisco Unified Communications Manager Administration tool, select from the menu Device >
Add a New Device.
Step 3. Change the device type from the drop-down menu to Phone and click Next.
The phone type for the simulated phone must be Cisco 7960.
Step 4. Select this model as the phone type and click Next.
Step 5. In the Phone Configuration window, enter a MAC address between 00059a3b7700 and 00059a3b8aff.
The tool automatically fills in the Description field. Other required fields are Device Pool and Button
Template. Keep the default values for these fields.
Step 6. Click Insert.
Schedule an IP Phone Discovery; it must complete before the new synthetic IP phone can be used in the synthetic
test.
Node-to-Node Tests
Node-to-node tests are typically used to measure jitter, packet loss, and delay on synthetic test traffic generated
by the Cisco IOS IP SLA on any Cisco IOS device across a WAN.
Preparing Devices for Node-to-Node Tests
The IP SLA is enabled manually in Cisco IOS Software. You may need to configure, depending on the Cisco IOS
device, the RTR Responder, or the IP SLA Responder command-line interface (CLI). The codec type for the jitter
test is supported only on certain versions of Cisco IOS Software (specifically, 12.3(4)T and later). Therefore, it is
possible that the codec type selection might be grayed out based on the source device you choose.
Node-to-Node Test Events
The events are raised on the source device. A threshold event is generated when the threshold violation occurs for
three consecutive polling cycles. The event is cleared if the value falls below the threshold in the following polling
cycle.
The following node-to-node events can be generated:
●
NodeToNodeTestFailed
●
RoundTripResponseTime_ThresholdExceeded
●
RingBackResponseTime_ThresholdExceeded
●
RegistrationResponseTime_ThresholdExceeded
●
AverageLatency_ThresholdExceeded
●
PacketLossSD_ThresholdExceeded
●
PacketLossDS_ThresholdExceeded