Cisco Cisco Prime Unified Operations Manager 8.7 Libro bianco

All contents are Copyright © 1992–2006 Cisco Systems, Inc.   All rights reserved. 

Page 55 of 112 

Description 

TAG 

Example 

4: …… 
<Refer to appendix 
A for the complete 
list> 

Calculated MOS score for call 

E 

35 (for 3.5) (44 is a 
perfect call) 

2 

Primary cause of call degradation 

F 

J: Jitter 
P: Packet Loss 

1 

Actual packet loss 

G 

9999 (Decimal) 

4 

Actual jitter 

H 

9999 (Decimal) 

4 

Total 

 ― 

 ― 

37 

 
•  Check the trapgen.log file in C:\Program Files\CSCOpx\log\qovr. Make sure events 

are current and being updated. 

•  Enable Call Metrics and check the .csv file in C:\Program 

Files\CSCOpx\data\CallMetrics and ensure that the files are being created every 60 
seconds. 

•  Check the http pages on the Cisco 1040 sensor: http://<1040 ip address> and 

http://<1040 IP address>/Communication for device details. 

•  Ensure that you do not have a port conflict on port 162, the SNMP trap port.  

Software such as MGSoft will conflict with the Operations Manager QoV trap 
reception on port 162. Also, disable Windows "SNMP Trap Service" under 
Administrative Tools > Services and then restart the SNMP Daemon Manager. 

 

 

Cisco 1040 ID  

A letter and a 3-digit number; for example, A100  

Time stamp  

Date and time  

Flag indicating actual or sampled 
data  

0: Actual  

1: Sampled  

Source device IP address  

IPv4 address; for example, 172.020.119.043