Белая книга для Cisco Cisco Prime Unified Service Monitor 8.7
White Paper
© 2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 23 of 26
Q.
A.
Q.
A.
A.
Q.
A.
A.
Q.
A.
A.
A few rows in the sensor diagnostic reports do not show directory numbers What could
be the issue?
Make sure that the call is over. CDRs and CMRs are generated at the end of the call only,
whereas sensors send data even while the call is in progress.
Make sure that the call is over. CDRs and CMRs are generated at the end of the call only,
whereas sensors send data even while the call is in progress.
●
Make sure that the corresponding call in the Cisco Voice Transmission Quality diagnostic
report shows directory number for both the caller and callee. Some gateway ports do not
have directory numbers Sensor rows for those calls will not have directory number
information.
report shows directory number for both the caller and callee. Some gateway ports do not
have directory numbers Sensor rows for those calls will not have directory number
information.
Why is the directory number missing in sensor reports?
Please check the following:
Please check the following:
●
The Cisco 1040 Sensors monitor RTP traffic; they do not report directory numbers.
●
Directory numbers can be seen in the diagnostic sensor reports only if the call whose
streams are being reported by sensors to Service Monitor is also reported by call manager
to Service Monitor meaning that the call manager server must be added to the Service
Monitor server.
streams are being reported by sensors to Service Monitor is also reported by call manager
to Service Monitor meaning that the call manager server must be added to the Service
Monitor server.
●
Service Monitor and call managers have to be time synched in order to display the directory
numbers.
numbers.
General sensor troubleshooting tips:
Please check the following:
Please check the following:
●
If the sensor is not receiving the IP address, check the DHCP configuration on the DHCP
server.
server.
●
Start with http://<ip-addr>/Communication and see what the sensor communication debug
page says. If there are any startup issues on the sensor (such as the TFTP server not being
reachable or inability to download the image file), this page should tell you.
page says. If there are any startup issues on the sensor (such as the TFTP server not being
reachable or inability to download the image file), this page should tell you.
●
If you are suspecting a sensor/Service Monitor issue, then use the sniffer to check the
communication from the sensor to the rest of the world. You should use the sniffer on the
management port of the sensor to begin with.
communication from the sensor to the rest of the world. You should use the sniffer on the
management port of the sensor to begin with.
●
If Cisco Unified Communication Manager 5.x is used for TFTP server, please restart the
TFTP service after the configuration files and image files are manually copied over for
changes to take effect.
TFTP service after the configuration files and image files are manually copied over for
changes to take effect.
●
The spanning port doesn’t play a role in booting the sensor. But do make sure SPAN is
configured on the switch port instead of the routed port.
configured on the switch port instead of the routed port.
●
Service Monitor installs the TFTP server by default; If the customer installs another TFTP
server, make sure the TFTP service in Common Service (CS) is shut down to avoid any
potential issue.
server, make sure the TFTP service in Common Service (CS) is shut down to avoid any
potential issue.
●
Do not edit configuration files using Wordpad (where the TFTP server is not editable), as it
introduces a carriage return.
introduces a carriage return.
What type of credentials do we configure?
Please check the following:
Please check the following:
●
For call manager 5.x and above: HTTP/HTTPS credentials
These are the same as those used by the browser for accessing the call manager Web-based
administration page. The IP address provided should be the publisher’s IP address.
administration page. The IP address provided should be the publisher’s IP address.