Note To configure security for Service Monitor using Cisco Secure ACS, see Installation Guide for Cisco Unified Service Monitor 8.5. Otherwise, configure security for Service Monitor using Common Services; for more information, see Common Services online help.

The Common Services online help is only available through the Common Services pages, which are located in the Administration tab.

To access the Common Services Online Help, you can use the following procedure:

1. Select Administration > Server Administration (Common Services) > Security. The Setting up Security page appears.

2. Click Help. The online help opens.

Table A-1 lists configuration tasks that you must complete before Service Monitor can start to monitor MOS and send traps.

Table A-1 Initial Configuration Task Checklist
Tasks		Description and Reference
Configuring Service Monitor and Cisco Unified Communications Manager (when Present in your Network)
		Configure Cisco Unified Communications Manager (Unified Communications Manager) as described in Unified Communications Manager Configuration, page B-1.
		Add credentials for Unified Communications Managers to Service Monitor; see Understanding and Setting Data Source Credentials, page 3-2.
Configuring Service Monitor and Sensors (when Present in your Network)
	Configuring NAMs
		Configure NAMs. See NAM Configuration, page C-1.
		Add credentials for NAMs to Service Monitor.
	Configuring Cisco 1040s
		Add at least one TFTP server. See Configuring TFTP Servers for Cisco 1040 Configuration and Image Files, page 4-1.
		Set up the sensor default configuration file. See Setting Up the Cisco 1040 Sensor Default Configuration, page 4-3.
		Copy the binary image file to the root location on the TFTP server. See Copying the Binary Image File to the TFTP Server, page 4-3.
Configuring Trap Receivers
		Service Monitor can send generated SNMP traps to up to four trap receivers. See Configuring Trap Receivers, page 3-1.

For Service Monitor to supply categorized call data to Service Statistics Manager (if present in your network), you must configure call classification; see Call Classification Configuration Checklist.

To launch Operations Manager—for the purpose of obtaining more information about endpoints that appear in Service Monitor reports—you must first enter the Operations Manager server IP address in Service Monitor. For more information, see Configuring and Viewing Other Settings, page 3-34.

Call Classification Configuration Checklist

Call classification configuration enables Service Monitor to categorize call data and accomplish the following:

•Provide categorized call data to Service Statistics Manager to support reports by call category.

Note If Service Statistics Manager is present in your network, you must configure call classification in Service Monitor.

•Apply user-defined call categories in the CDR Call Report.

Note Only system-defined call categories are used unless you configure call classification. System-defined call categories are listed in Table 3-3 on page 3-19.

To configure call classification, perform the following tasks:

•Configure at least one dial plan. See Configuring User-Defined Dial Plans, page 3-22.

•Assign a dial plan to each cluster. See Assigning a User-Defined Dial Plan to a Cluster, page 3-30.

•Configure gateway codes. See Configuring Gateway Codes, page 3-30.

Server and Client Configuration Checklist

Perform the following tasks:

•On the Service Monitor server, exclude the NMSROOT\databases directory from virus scanning. Problems can arise if database files are locked because of virus scanning.

Note NMSROOT is the directory where Service Monitor is installed on your system. If you selected the default directory during installation, it is C:\Program Files\CSCOpx.

•On Service Monitor clients, you must disable any software that you use to prevent popup windows from displaying. Service Monitor must be able to open multiple windows to display information.

When You Can Expect to See Results

After you complete the tasks in Table A-1, Service Monitor starts to receive, analyze, and present data as follows:

•Sensor records contain data for a 60-second period. Sensors, therefore, report MOS that is calculated while a call is in progress.Therefore, Service Monitor can start to generate traps while the call ensues. Similarly, sensor data can be displayed in Service Monitor reports while the call is in progress.

•Call data records (CDRs) are only written by Unified Communications Manager after a call has completed. Although Service Monitor might obtain data from Unified Communications Manager every 60 seconds, Service Monitor cannot generate traps until the call is over. Similarly, CVTQ data cannot be displayed in Service Monitor reports until a call has completed.

Optional Configuration Checklist

These tasks enable you to:

•Update and override the default global thresholds—one per codec—that Service Monitor uses to trigger trap generation.

•Generate most-impacted endpoint reports automatically on a nightly and weekly basis.

Table A-2 Optional Configuration Tasks
Tasks	Description and Reference
Updating and Overriding Global Thresholds
	Update global threshold values. See Configuring Global Thresholds, page 5-3.
	Override global threshold values, providing values for selected sensors. See Configuring Sensor Threshold Groups, page 5-9.
	Override global threshold values, providing values for selected clusters. See Configuring CVTQ Threshold Groups, page 5-4.
Exporting Most-Impacted Endpoint Reports
	See Configuring Settings for Most-Impacted Endpoints Reports, page 3-16.
Updating Report-Related Settings and System Schedules
	Update the number of minutes that diagnostic reports search for data and the number of records to export to a CSV file. See Configuring Diagnostic Report Search and CSV Export Limit Settings, page 3-35.
	Update system schedules. See Configuring Low-Volume Schedule and Database Purging, page 6-2.