Table Of Contents
Release Notes for Cisco Unified
Service Monitor 2.3
Revised: May 21, 2010, OL-20787-01
Cisco Unified Service Monitor is a product from the Cisco Unified Communications Management Suite. These release notes provide:
The following changes and enhancements are included in Service Monitor 2.3:
•Add support for:
–Cisco Unified Communications Manager (Unified Communications Manager) 8.0
–New Cisco Unified IP phone models—8961, 9951, and 9971 (SIP protocol only)
–Cisco NAM 4.2 software
•New report—CDR Call Data Report.
•Call classification configuration—Configure dial plans (and call categories) to:
–Support the CDR Call Data Report
–Provide categorized call data to Service Statistics Manager 1.3
Note If you have Service Statistics Manager installed in your network, see Saving Service Statistics Manager Information to Reuse in Service Monitor 2.3.
See the following topics:
Locating the Call Migration Tool on the Product CD
To save report data, you must run the call migration tool before you upgrade. You can find the call migration tool in the \install\CallMigrationTool directory:
•In the Service Monitor product zip file (CUSM2_3.zip) that you can download from Cisco.com.
•On the product CD in the \install\CallDataMigrationTool directory. (In most cases, Service Monitor is provided through electronic delivery and you will not receive a product CD.)
Extract the contents of the QOVR_CMT.zip file and see the readme file for detailed instructions. Also, see the section "(Optional) Planning for Data Migration and Migrating Call Data Before the Upgrade" in Installation Guide for Cisco Unified Service Monitor.
Note Running the call migration tool is optional. The tool migrates call data to the Service Monitor 2.3 database. Other Service Monitor 2.2 data migrates automatically during the upgrade.
Saving Service Statistics Manager Information to Reuse in Service Monitor 2.3
This information is important when you have Service Statistics Manager installed in your network and you are upgrading to Service Monitor 2.3. Call classification and dial plan configuration is removed from Service Statistics Manager and added to Service Monitor 2.3.
Caution When you upgrade from Service Statistics Manager 1.2, the dial plan and call classification configuration data is lost.
You cannot automatically migrate dial plan and call classification configuration data from Service Statistics Manager 1.2 to Service Monitor 2.3 due to these differences:
•Dial plans are assigned on a per cluster basis in Service Monitor while a single dial plan is applied to clusters in Service Statistics Manager.
•Toll-free numbers and service numbers are configured in each dial plan in Service Monitor.
•Many call categories used in Service Monitor are different from those used previously in Service Statistics Manager; see Service Statistics Manager Call Categories that Remain Available in Service Monitor.
You must shut down Service Statistics Manager 1.2 before you upgrade Service Monitor from 2.2 to 2.3. Before you upgrade, consider taking screenshots or otherwise making a record of the dial plan entries, gateway codes, toll-free numbers, and service numbers in Service Statistics Manager 1.2 that you would like to reconfigure in Service Monitor 2.3. Table 1 provides more information.
Table 1 Preparing to Manually Move Data from Service Statistics Manager 1.2 to Service Monitor 2.3
Dial Plan Data Location in Service Statistics Manager Location in Service Monitor
To view the gateway codes, service numbers, and toll-free numbers that are configured, go to the Dial Plan Configuration page:
1. From the Administration tab, scroll to Advanced.
2. Click Edit in the Dial Plan, Gateway Codes, Toll-Free Numbers, Service Numbers row. The Dial Plan Configuration page appears. Drill down to the necessary data.
To configure gateway codes, select Configuration > Call Classification > Gateway Codes.
Note Before you configure gateway codes, Service Monitor must finish collecting configuration data from the Unified Communications Managers for which credentials are stored in Service Monitor. Check the status of configuration data collection from the Data Source Credentials page.
To configure a service number, configure a dial pattern in the Service category.
Select Configuration > Call Classification > Dial Plan Configuration.
To configure toll-free numbers, configure a dial plan.
One dial plan in Service Statistics Manager is applied to all clusters. Knowing the dial plan entries that are configured and the priority of each is useful for configuring dial plans in Service Monitor.
Note For information about call categories, see Service Statistics Manager Call Categories that Remain Available in Service Monitor.
You can configure multiple dial plans.
•Select Configuration > Call Classification > Dial Plan Configuration.
For a dial plan to be in effect, you must assign it to a cluster.
•Select Configuration > Call Classification > Dial Plan Assignment.
Service Statistics Manager Call Categories that Remain Available in Service Monitor
Of the call categories that are defined in Service Statistics Manager 1.2, the following are also available in Service Monitor 2.3:
•Internal—A system-defined call category. (Service Monitor assigns calls to all applicable system-defined call categories. For more information, see the Service Monitor online help or user guide.)
•User-defined call categories that you can use in configuring dial patterns:
Note The Voicemail user-defined call category in Service Monitor replaces the Voice Mail call category used in Service Statistics Manager.
When a dial plan is applicable, Service Monitor assigns the call to the highest priority dial pattern call category in addition to assigning the call to all applicable system-defined call categories.
For more information, see online help for Service Monitor or see User Guide for Cisco Unified Service Monitor.
Note The originally published printed and electronic documentation is included with your product. Any changes after original publication are reflected on Cisco.com, where you will find the most up-to-date documentation.
Table 2 describes the product documentation that is available.
Note The originally published printed and electronic documentation was included with your product. Any changes after original publication are reflected on Cisco.com, where you will find the most up-to-date documentation.
Table 3 describes the additional documentation that is available.
Compatible Phones, Gateways, and Software Versions
For supported phones, software versions, and, where applicable, configuration notes and hardware models, see Cisco Unified Service Monitor 2.3 Compatibility Matrix. It includes information for the following:
•Cisco Unified Communications Management Suite products
•Cisco Unified Communications Manager
•Cisco 1040 Sensor binary image
•Cisco Unified IP Phones
•Cisco Network Analysis Module software (and hardware)
Required Unified Communications Manager Patches and Workarounds
Problems with CVTQ data can occur due to known problems with certain versions of Unified Communications Manager. Table 3 documents these problems.
Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)
Table 3 describes problems known to exist in this release.
Table 5 Known Problems in Service Monitor 2.3
Bug ID Summary Explanation
IMPORTANT TLS/SSL SECURITY UPDATE
An industry-wide vulnerability exists in the Transport Layer Security (TLS) protocol that could impact any Cisco product that uses any version of TLS and SSL. The vulnerability exists in how the protocol handles session renegotiation and exposes users to a potential man-in-the-middle attack.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20091109-tls.shtml.
Common Services has released OpenSSL security patch for TLS/SSL renegotiation vulnerability (CSCtd01597) on Cisco.com. The patch can be downloaded from the following URL: http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=276698858.
Report filter page shows different current date from calendar widget
Report filter pages—such as CVTQ Report Filter, CDR Call Report Filter, Sensor Report Filter—display the current date based on Service Monitor server time. However, on the calendar widget that you can access from the filter pages, the current highlighted date is based on the client time.
When the Service Monitor client is in a different time zone from the server, at some points the date on a report filter page can be a day off from the date on the calendar widget.
You can enter dates manually instead of using the calendar widget.
CVTQ report misses first record when a phone is seen for first time
A CVTQ report should show two rows for each call, but Service Monitor drops CMRs the first time a device is seen. As a result, only one row each for each call is included in the CVTQ report.
Data exported from sensor report differs from what is displayed
This problem occurs when you view a trap on the Operations Manager Service Quality Alerts display, launch a Service Monitor sensor report for the trap, and export a range of rows from the sensor report. The resultant CSV file contains data that does not match what is displayed in the sensor report.
To obtain an export file with the correct data:
1. In Service Monitor, select Reports > Diagnostics > Sensor.
2. Enter the endpoints and time range that are shown in the existing report.
3. Generate the report and export the data.
Most-Impacted Sensor report incorrect when multiline phone
When calls are made from a single-line phone to directory numbers on a multiline phone, the Most-Impacted Sensor report includes only one of the directory numbers on the multiline phone.
Phone 1—Single-line phone (directory number: 48003)
Phone 2 —Multiline phone (directory numbers: 48006 and 48007)
From Phone 1 (48003), make two calls: to 48006 and to 48007.
In Most-Impacted Sensor report, only 48007 is displayed as an endpoint.
There is no workaround.
Apache error on local machine
When you log in to the Windows system where Service Monitor is installed, you might see a few dialog boxes that show Apache errors. This happens on initial reboot of the system.
The errors are harmless and you can close the dialog boxes.
Monitored phone count can lag device discovery
There might be a lag of up to one minute between the time that Service Monitor discovers devices and the time when the monitored phone count is updated.
There is no workaround for this problem.
The following problems exist in the documentation that is released in the downloadable product zip file and on the product CD. The problems are corrected on Cisco.com.
Installation Guide—(Optional) Planning for Data Migration and Migrating Call Data Before the Upgrade Migrating
The topic is rewritten to correct the location of the Call Migration Tool on Cisco.com as follows.
Migrating call data is optional. However, to keep the data, you must migrate it before you start the upgrade to Service Monitor 2.3. You can find the call migration tool in the zip file that contains the Service Monitor product on Cisco.com.
Note The README_QOVR_CMT.TXT. file that is included with the Call Migration Tool provides estimates of the time that data migration takes and the disk space it uses. It also explains the effect that running the tool has on Operations Manager and Service Statistics Manager, if they are installed in your network.
Step 1 Download the zip file (CUSM2_3.zip) that contains the Service Monitor product from Cisco.com. You can navigate there as follows:
b. If you have not already logged in to Cisco.com, log in.
c. Click the Download Software link.
d. Follow the online instructions to select Cisco Unified Service Monitor 2.3 and download the zip file.
Step 2 Extract the QOVR_CMT.zip file from the \install\CallMigrationTool folder in the CUSM2_3.zip file.
Step 3 Extract the README_QOVR_CMT.TXT file from the QOVR_CMT.zip file and use the information in it to plan for and execute the migration.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
SUPPLEMENTAL LICENSE AGREEMENT
SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCO UNIFIED SERVICE MONITOR.
IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the End User License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the End User License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.
By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download or otherwise use the Software. When used below, the term "server" refers to central processor unit.
1. ADDITIONAL LICENSE RESTRICTIONS.
•Installation and Use. The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Customer may install and use the following Software components:
–CiscoWorks Common Services: Contains shared resources used by other components in this bundle. In many cases, all components in this bundle can be installed on a single server.
–Cisco Unified Service Monitor: May be installed on one (1) server in Customer's network management environment.
•Number of IP Phones. For each Software license granted, Customer may install and run the Software on a single server to manage the number of IP phones specified in the license file provided with the Software, or as specified in the Software License Claim Certificate. Customers whose requirements exceed the IP phone limit must purchase upgrade licenses or additional copies of the Software. The IP phone limit is enforced by license registration.
•Reproduction and Distribution. Customer may not reproduce nor distribute the Software.
2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.
Please refer to the Cisco Systems, Inc. End User License Agreement.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.