-
Cisco Unified Communications Manager Managed Services Guide, Release 7.1
-
Preface
-
Overview
-
New and Changed Information
-
Managing and Monitoring the Health of Cisco Unified Communications Manager Systems
-
Simple Network Management Protocol
-
Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
-
Cisco Unified Serviceability Alarms and CiscoLog Messages
-
Cisco Management Information Base
-
Industry-Standard Management Information Base
-
Vendor-Specific Management Information Base
-
Index
-
Feedback
Table Of Contents
Cisco Unified Communications Manager Release 7.1
Unconfigured Device Registration Attempts Restricted
Always Use Prime Line and Voice Message
New Cisco Unified Serviceability Alarm Definition Catalogs
New Cisco Unified Serviceability Alarms
Cisco Unified Cisco Unified Real-Time Monitoring Tool
Centralized Audit Logging and Security for Linux
Cisco Unified Communications Manager CDR Analysis and Reporting
CAR Administrator Privileges Restored After Upgrade
Cisco Unified Communications Manager Call Detail Records
New Call Termination Cause Codes
SIP Calls with URL in callingPartyNumber Field
GlobalCallId Survives Over Cisco Unified Communications Manager Restarts
Cisco Unified Communications Manager Release 7.0(x)
Cisco Unified Communications Manager Release 7.0(2)
Cisco Unified Communications Manager Release 7.0(1)
Cisco Unified Real-Time Monitoring Tool
Cisco Unified Communications Manager CDR Analysis and Reporting
Cisco Unified Communications Manager Call Detail Records
Cisco Unified Communications Manager Release 6.1(x)
Cisco Unified Communications Manager Release 6.1(3)
Cisco Unified Cisco Unified Real-Time Monitoring Tool
Cisco Unified Communications Manager CDR Analysis and Reporting
Cisco Unified Communications Manager Call Detail Records
Cisco Unified Communications Manager Release 6.1(2)
Cisco Unified Communications Real-Time Monitoring Tool
Cisco Unified Communications Manager Release 6.1(1a)
CDR Analysis and Reporting Tool/Call Detail Record (CAR/CDR)
Cisco Unified Communciations Manager Release 6.1(1b)
Cisco Unified Communications Manager Release 6.0(1x)
Cisco Unified Communications Manager Release 6.0(1)
No Such Name Error in SNMP Response
Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
Secure Conferencing and CRD Data
Cisco Unified Communications Real-Time Monitoring Tool
Cisco Unified Communications Manager CDR Analysis and Reporting
Cisco Unified Communications Manager Release 6.0(1a)
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
Cisco Unified Communications Manager Release 6.0(1b)
New and Changed Information
This chapter describes new and changed information in Cisco Unified Communications Manager (Cisco Unified CM) from release to release beginning with Release 6.x. It contains the following sections:
•
Cisco Unified Communications Manager Release 7.1
•
•
•
For complete release note information, refer to this index for your Cisco Unified CM release:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html.
Cisco Unified Communications Manager Release 7.1
This section describes the new and changed information in Cisco Unified Communications Manager Release 7.1. It contains the following subsections:
•
•
•
Cisco Unified Serviceability
This section contains the following subsections:
•
•
•
•
IPv6 and Address Space
IPv6 is the latest version of IP that uses packets to exchange data, voice, and video traffic over digital networks and that increases the number of network address bits from 32 bits in IPv4 to 128 bits. IPv6 support in the Cisco Unified Communications Manager network enables the network to transparently perform tasks in a dual-stack environment and provides additional IP address space and autoconfiguration capabilities to devices that are connected to the network.
Before you configure IPv6, review the "Internet Protocol Version 6 (IPv6)" chapter in the Cisco Unified Communications Manager Features and Services Guide carefully. Specifically review how to configure IPv6 the Cisco Unified Communications Manager server and phones in dual-stack mode and how Cisco Unified Communications Manager uses MTPs to translate IPv4 to IPv6 or vice versa.
SNMP supports IPv4, and the CISCO-CCM-MIB includes columns and storage for IPv6 addresses and preferences. IPv6 impacts the Cisco CallManager, CTIManager, and Certificate Authority Proxy Function services in Cisco Unified Serviceability. See "CISCO-CCM-MIB" section and the Cisco Unified Serviceability Administration Guide for more information.
Service Manager Enhancements
This release includes two new service states: Starting and Stopping. When the service state is stopping, a service cannot start. When a service state is starting, a service cannot stop. These states display in the Service Activation window in Cisco Unified Serviceability and in the command line interface (CLI).
This release also includes the following performance enhancements:
•
•
•
•
•
•
•
•
•
•
•
•
•
Table 1 describes new Service Manager return codes.
Cisco Audit Event Service
The Cisco Audit Event Service, which was added to the Control Center Network GUI in Cisco Unified Serviceability, starts or stops the Audit Log service. Only a user with an audit role has permission to change the Audit Log settings.
By default, CCMAdministrator takes the audit role after fresh installs and upgrades. This role can assign the "standard audit users" group to any new user that the administrator specifically creates for audit purposes. The CCMAdministrator role can then get removed from the audit user group.
The "standard audit log configuration" role provides the ability to delete audit logs, read/update access to Cisco Unified Real-Time Monitoring Tool, Trace Collection Tool, RTMT Alert Configuration, the Control Center - Network Services window, RTMT Profile Saving, the Audit Configuration window, and a new resource called Audit Traces.
New Audit Log CLI Commands
The following new audit log CLI commands are added. For more information about command syntax and parameters, see the Command Line Interface Reference Guide for Cisco Unified Solutions.
•
•
•
•
–
–
Logical Partitioning
The following serviceability consideration exists for the logical partitioning feature:
•
–
–
–
–
–
–
–
–
–
–
See the "Performance Monitoring in RTMT" section for details. For CAR/CDR and to support logical partitioning, call termination cause codes are added.
For details on CDR codes and codecs, refer to the "Cisco Call Detail Records Codes" chapter of the Cisco Unified Communications Manager Call Detail Records Administration Guide. The "CDR Examples" chapter provides examples of CDRs that are added to support the logical partitioning feature.
For more information on this feature, refer to the Cisco Unified Communications Manager Administration Guide.
Standard Audit Log
The Standard Audit Log can be configured in Cisco Unified Serviceability to read or update the Resource Access Information. The following resources are configurable:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Table Out of Sync Detection
When the Table Out Of Sync parameter is turned on, the Database Replication Status summary gets collected every day during the maintenance window. The system compares the output of three consecutive days to determine whether the tables have been out of sync for all three days. If so, it triggers an alert. Enable the Alert in Cisco Unified Serviceability. To configure the Alert in RTMT, refer to the Setting Alert Properties in the Cisco Unified Real-time Monitoring Tool Guide. Cisco recommends that you call TAC if this alert gets generated.
Unconfigured Device Registration Attempts Restricted
Prior to Cisco Unified Communications Manager 6.1(3) and 7.1 (not 7.0(1)), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have auto-registration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager.
In Cisco Unified Communications Manager 6.1(3) or 7.1, if auto-registration is disabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone does not attempt to register with Cisco Unified Communications Manager. The phone continues to display the Configuring IP message until auto-registration gets enabled or until the phone gets added to the Cisco Unified Communications Manager database.
The Cisco RTMT and Cisco Unified Reporting display information on registered and unregistered devices. For more information, refer to the Cisco Unified Real-Time Monitoring Tool Administration Guide and the Cisco Unified Reporting Administration Guide.
Always Use Prime Line and Voice Message
The Always Use Prime Line feature relies on a Cisco CallManager service. After the feature is enabled, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the device configured value; for example, alwaysPrimeLine=1, which indicates that the device uses On for the configuration.
The Always Use Prime Line for Voice Message feature relies on a Cisco CallManager service. After the feature is enabled, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the device configured value; for example, alwaysUsePrimeLineForVM=2, which indicates that the device uses the default.
In previous releases of Cisco Unified Communications Manager, except Release 6.1(3), you configured the Always Use Prime Line and Always Use Prime Line for Voice Message service parameters that applied to the entire cluster. In Cisco Unified Communications Manager 6.1(3) and 7.1, you can configure both services for specific devices and device profiles.
New Cisco Unified Serviceability Alarm Definition Catalogs
The following catalogs have been added to Cisco Unified Serviceability:
•
•
New Cisco Unified Serviceability Alarms
•
•
•
•
•
Cisco Unified Cisco Unified Real-Time Monitoring Tool
This section contains these subsections:
•
IPv6 Addressing and RTMT
In RTMT, you can monitor CTI applications, CTI devices, and CTI lines that use IPv6 addresses. When you search for the application, device, or line, enter the IPv6 address, and check the AppIpv6Addr check box in the attribute window or in the case of phones and SIP Trunks, check the Ipv6Address check box in the attributes window. Log files display IPv4 and IPv6 addresses depending on the configuration in your network.
Table 2-2 lists and describes the PerfMon counters that provide IPv6 statistics for your system.
Centralized Audit Logging and Security for Linux
Centralized audit logging reports any configuration change to the Cisco Unified Communications Manager system and creates log files. In addition to centralized audit logging, there are security features. The events occur in Cisco Unified Serviceability and the following events are logged:
•
•
•
•
•
Cisco Unified RTMT logs the following events with an audit event alarm:
•
•
•
•
•
•
•
•
•
•
All audit logs get collected, viewed, and deleted from Trace and Log Central in the Cisco Unified RTMT. and the Log Partition Monitor (LPM) manages the purging of these audit logs as needed.
By default, the LPM purges the audit logs, but the user can change this setting from the Audit User Configuration window in Cisco Unified Serviceability. The LPM sends an alert whenever the common partition disk usage exceeds the threshold; however, the alert does not have the information about whether the disk is full because of audit logs or trace files.
Quality Report Tool Reports
A change occurred in the Call State information that is collected from Cisco Unified Communications Manager/CTIManager and displayed in the Quality Report Tool (QRT) reports. Previously, the information included Connected, Connected Conference, Connected Transfer, and On Hook call state information. Now, the report only includes Connected and On Hook call state information.
System History Log
The system history log provides a central location for getting a quick overview of the initial system install, system upgrades, Cisco option installations, DRS backups and DRS restores, switch version, and reboot history.
The system history log exists as a simple ASCII file, system-history.log, and the data does not get maintained in the database. Because it does not get excessively large, the system history file does not get rotated. It logs the following information:
•
•
•
•
•
•
•
•
Each system history log entry contains the <timestamp> <userid> <action> <description> <start/result> fields. The fields can contain the following values:
•
•
•
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
•
–
–
–
The following example shows a system history log:
admin:file dump install system-history.log=======================================Product Name - Cisco Unified Communications ManagerProduct Version - 6.1.2.9901-117Kernel Image - 2.4.21-47.EL.cs.3BOOT=======================================07/25/2008 14:20:06 | root: Install 6.1.2.9901-117 Start07/25/2008 15:05:37 | root: Install 6.1.2.9901-117 Success07/25/2008 15:05:38 | root: Boot 6.1.2.9901-117 Start07/30/2008 10:08:56 | root: Upgrade 6.1.2.9901-126 Start07/30/2008 10:46:31 | root: Upgrade 6.1.2.9901-126 Success07/30/2008 10:46:43 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Start07/30/2008 10:48:39 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Success07/30/2008 10:48:39 | root: Restart 6.1.2.9901-126 Start07/30/2008 10:51:27 | root: Boot 6.1.2.9901-126 Start08/01/2008 16:29:31 | root: Restart 6.1.2.9901-126 Start08/01/2008 16:32:31 | root: Boot 6.1.2.9901-126 StartYou can access the system history log by using the following CLI file commands:
•
•
Cisco Unified Communications Manager CDR Analysis and Reporting
This section contains these subsections:
•
Customized Logon Message
You can upload a text file that contains a customized logon message that displays on the initial Cisco Unified Communications Manager CDR Analysis and Reporting window.
Upgrade of CAR Data
When you upgrade to a later version of Cisco Unified Communications Manager, your CDR data may not be upgraded. The Cisco Unified Communications Manager installation program limits the time period for the migration of the CAR records from the CSV files in the Data Migration Assistant (DMA) TAR file to the CAR database on the upgraded system. The migration time period is 60 minutes.
To allow the migration of the highest number of CSV files in the allotted time period, CAR record migration uses the following process:
•
–
–
•
–
–
If the 60-minute migration time limit occurs at any point in the migration process, CAR data migration stops and the tbl_system_preferences of the CAR database get updated to reflect the data present in the upgraded system database.
Backup of CAR Data
The CAR and CDR Disaster Recovery Service (DRS) includes the backup of the CAR database, pregenerated reports, and the CDR preserved flat files. The CAR Web Service and CAR Scheduler automatically stop before the backup and restore process begins and automatically restarts after the backup and restore process completes.
Table 2-3 lists Cisco Unified CM features and components UCM that the DRS can back up and restore. For each feature that you choose, the system backs up all its components automatically.
FTP/SFTP Billing Servers
Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to the following URL:
http://www.cisco.com/pcgi-bin/ctdp/Search.pl
For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to the following URL:
http://www.globalscape.com/gsftps/cisco.aspx
Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
•
•
•
Note
Cisco has tested and supports the following versions of FTP or SFTP for CAR billing servers:
•
–
–
•
–
–
CAR Administrator Privileges Restored After Upgrade
When you use DMA to upgrade Cisco Unified Communications Manager, CAR users no longer have CAR administrator privileges after the upgrade and become standard end users. You must reset the CAR administrator privileges after the upgrade. Refer to the "Configuring CAR Administrators, Managers, and Users" chapter in the CDR Analysis and Reporting Administration Guide for more information on how to configure CAR administrators.
Cisco Unified Communications Manager Call Detail Records
This section contains these subsections:
•
•
•
IPv6 and New CDR Fields
Cisco Unified Communications Manager supports IPv6 in this release. Table 2-4 describes two new CDR fields.
Video Channels and CDRs
There are new CDR fields that support a second video channel for both the origination and destination devices. Table 2-5 describes the new fields.
Table 2-5 New CDR Field Descriptions for Video Channels
origVideoCap_Codec_Channel2
0,
100 = H.261,
101 = H.263,
102 = Vieo,
103 = H.264
Identifies the codec type that the originator uses to transmit video (H.261, H.263, Vieo, H.264) for the second video channel.
origVideoCap_Bandwidth_Channel2
0, Positive integer
Identifies the bandwidth that is measured in units of kbs for the second video channel.
origVideoCap_Resolution_Channel2
0,
1 = SQCIF,
2 = QCIF,
3 = CIF,
4 = CIF4,
5 = CIF16
Identifies the video resolution for the second video channel.
origVideoTransportAddress_IP_Channel2
0, Integer
Identifies the v4 IP address of the device that originates the call for the second video channel.
origVideoTransportAddress_Port_Channel2
0, Positive integer
Identifies the video RTP port that is associated with the origH239VideoTransportAddress_IP field for the second video channel.
origVideoChannel_Role_Channel2
0 = Presentation role,
1 = Live role,
Positive integer
Identifies the H.239 video channel role of the device that originates.
destVideoCap_Codec_Channel2
0,
100 = H.261
101 = H.263
102 = Vieo
103 = H.265
Identifies the codec type that the terminating party uses to transmit video for the second video channel (H.261, H.263, Vieo, H.264).
destVideoCap_Bandwidth_Channel2
0, Positive integer
Identifies the bandwidth that is measured in units of kbs for the second video channel.
destVideoCap_Resolution_Channel2
0,
1 = SQCIF,
2 = QCIF,
3 = CIF,
4 = CIF4,
5 = CIF16
Identifies the video resolution for the second video channel.
destVideoTransportAddress_IP_Channel2
0, Integer
Identifies the IPv4 address of the device that receives the call.
destVideoTransportAddress_Port_Channel2
0, Positive integer
Identifies the video RTP port that is associated with the destH239VideoTransportAddress_IP field.
destVideoChannel_Role_Channel2
0 = Presentation role,
1 = Live role,
Positive integer
Identifies the H.239 video channel role of the device that receives the call.
1 The default is zero (0). If media does not get established, this field displays 0 and if H.239 is not supported, this field displays 0.
New Call Termination Cause Codes
Table 2-6 lists and describes new Cisco call termination cause codes that support logical partitioning.
SIP Calls with URL in callingPartyNumber Field
A new CDR example exists for an incoming call received through a SIP trunk by the Cisco Unified Communications Manager. The call contains a SIP URL for the callingPartyNumber CDR field.
GlobalCallId Survives Over Cisco Unified Communications Manager Restarts
In Release 4.x and earlier releases, the GlobalCallId field was time-based, so the field got reused under conditions of heavy traffic. Because of this behavior, problems occurred with customer billing applications and the ability of CAR to correlate CMRs with CDRs and to correlate conference call CDRs.
For Cisco Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Cisco Unified Communications Manager restarts because it retains a unique value for a certain number of days. The last used globalCallId_callId value gets written to disk periodically (for every x number of calls). The value gets retrieved after a Cisco Unified Communications Manager restart, and the new globalCallId_callId value begins with this number plus x.
Cisco Unified Reporting
For a complete description of reports that are available on your system and the data that gets captured in a report, access Report Descriptions. Table 2-7 describes the new standard reports.
Documentation Updates
In the Cisco Unified Communications Manager CDR Analysis and Reporting Administration Guide, the configuration for the Department Bills Users Reports, the following note was added to Step 6 of the Configuring Department Bills Reports procedure:
Note
New Fields in CISCO-CCM-MIB
In the CISCO-CCM-MIB, the CTI InetAddress ccmCTIDeviceInetAddressType and ccmCTIDeviceInetAddress fields are deprecated.
There are two new IPv4/IPv6 fields added to the ccmCTIDeviceTable to improve the SNMP query performance when there are a huge number of entries in the table. The new fields are ccmCTIDeviceInetAddressIPv4 and ccmCTIDeviceInetAddressIPv6 .The definitions are as follows:
ccmCTIDeviceInetAddressIPv4 OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS read-only
STATUS current
DESCRIPTION—This object identifies the last known primary IPv4 address of the CTI device. This object contains value zero if IPV4 address is not available.
::= { ccmCTIDeviceEntry 14 }
ccmCTIDeviceInetAddressIPv6 OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-only
STATUS current
DESCRIPTION—This object identifies the last known primary IPv6 address of the CTI device. This object contains value zero if IPV6 address is not available.
::= { ccmCTIDeviceEntry 15 }
With these changes, the ccmCTIDeviceEntry looks like the following:
CcmCTIDeviceEntry ::= SEQUENCE {
ccmCTIDeviceIndex CcmIndex,
ccmCTIDeviceName SnmpAdminString,
ccmCTIDeviceType INTEGER ,
ccmCTIDeviceDescription SnmpAdminString,
ccmCTIDeviceStatus CcmDeviceStatus,
ccmCTIDevicePoolIndex CcmIndexOrZero,
ccmCTIDeviceInetAddressType InetAddressType,
ccmCTIDeviceInetAddress InetAddress,
ccmCTIDeviceAppInfo SnmpAdminString,
ccmCTIDeviceStatusReason CcmDevFailCauseCode,
ccmCTIDeviceTimeLastStatusUpdt DateAndTime,
ccmCTIDeviceTimeLastRegistered DateAndTime,
ccmCTIDeviceProductTypeIndex CcmIndexOrZero,
ccmCTIDeviceInetAddressIPv4 InetAddressIPv4,
ccmCTIDeviceInetAddressIPv6 InetAddressIPv6
}
Cisco Unified Communications Manager Release 7.0(x)
This section contains the following subsections:
•
•
Cisco Unified Communications Manager Release 7.0(2)
This section describes the new and changed information in Cisco Unified Communications Manager Release 7.0(2). It contains the following subsections:
Resolved Caveats
CAR
•
•
•
CCM Serviceability
•
CDR Management
•
Call Control
•
RTMT
•
•
SDL
•
•
Syslog
•
Unknown
•
•
•
•
•
•
•
Important Notes
Serviceability Session Timeout Not Graceful
When a session has been idle for more than 30 minutes, the Cisco Unified Serviceability user interface allows you to make changes before it indicates that the session timed out and redirects you to the login window. After you log in again, you may have to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows.
Workaround—If you know that the session has been idle for more than 30 minutes, log out by using the Logout button before making any changes in the user interface.
RTMT Perfmon Counters and Cisco Unified Communications Manager Upgrade
If you are running the RTMT client and monitoring performance counters during a Cisco Unified Communications Manager upgrade, the performance counters will not update during and after the upgrade. To continue monitoring performance counters accurately after the upgrade completes, you must either reload the RTMT profile or restart the RTMT client.
Installation of RTMT on Microsoft Vista Platform
When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control pop-up window to indicate that an unidentified program wants access to your computer. This occurs because of a limitation in the InstallAnywhere software. This one-time pop-up displays only when you are installing RTMT. Choose Allow to continue.
Serviceability Administrator Created during Installation
Removing the Administrator that is created during installation or upgrade can cause communication with remote nodes via Serviceability Administration to fail.
Best Practices for Assigning Roles to Serviceability Administrators
When starting and stopping services, Cisco recommends that you configure application users, rather than end users, to access remote nodes to perform tasks. Starting and stopping services requires that the Standard SERVICEABILITY Administration and Standard RealtimeAndTraceCollection roles be assigned.
CSCsq22385 Database Replication Failure Alert
The primary AMC server, which by default is the publisher node, raises the DBReplicationFailure alert after you add a new subscriber node to an existing cluster. After the install completes, the following alert displays.
May 7 16:02:09 lg-pub-1 local7 2 : 116: May 07 20:02:09.491 UTC : %CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:DBReplicationFailure Detail: DBReplicationFailure occurred. CallManager database replication errors, Reason code: Replication setup failed. The alert is generated on Wed May 07 16:02:09 EDT 2008 on node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxxYou can observe this alert by using RTMT Alert Central or Summary view. You can also find the alerts in the EventViewer - Application Logs (CiscoSyslog) by using RTMT syslog viewer or by using the file view activelog syslog/CiscoSyslog CLI.
The following list gives more symptoms of DBReplicationFailure that you may experience:
•
dbl_repl_cdr_define_lg_sub_8_ccm6_1_2_1000_13-2008_05_07_12_00_20.logsucmd_err [su -c 'ulimit -c 0;cdr err --zap' - informix ]Executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 --ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' - informix]We got exception in Cdr defineException from cdr define e.value[100] e.msg [Error executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 --ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' - informix] returned [25600]]•
11:47:51 CDR GC: GC could not verify the local server identity in CDR catalog with that in sqlhost file during CDR recovery.•
By default, the publisher node DB replicator service continuously attempts to define the new server and generates a new log every 5 minutes. Use the following workaround for a single node.
Step 1
May 7 16:02:09 lg-pub-1 local7 2 : 116: May 07 20:02:09.491 UTC : %CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:DBReplicationFailure Detail: DBReplicationFailure occured. CallManager database replication errors, Reason code: Replication setup failed. The alert is generated on Wed May 07 16:02:09 EDT 2008 on node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxxStep 2
Step 3
Note
Step 4
Step 5
At the end of the command output, the following message displays:
admin:utils dbreplication reset nw104a-195Repairing of replication is in progress.Background repair of replication will continue after that for 30 minutes.command failed -- Enterprise Replication not active (62)This output does not indicate a failure in the reset command. It serves as an informational message that gets generated when you drop the admindb on the subscriber. The reset completes successfully but the operation can take 30 minutes or more to finish.
If you revert the servers in a cluster to run a prior release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the prior release, enter the utils dbreplication reset all command on the publisher server.
When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message that reminds you about the requirement to reset database replication if you are reverting to an older product release. The caveats CSCsl57629 and CSCsl57655 also document this behavior.
For information about the utils dbreplication clusterreset, utils dbreplication dropadmindb, and utils dbreplication forcedatasyncsub commands, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 7.0(1) document at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html.
Serviceability Inaccessible
If you cannot access Cisco Unified Serviceability from Cisco Unified OS Administration, "Loading, please wait" message displays indefinitely. Log out from Cisco Unified OS Administration, select Cisco Unified Serviceability from the navigation menu, and log into Cisco Unified Serviceability.
Cisco Unified Communications Manager Release 7.0(1)
This section describes the new and changed information in Cisco Unified Communications Manager Release 7.0(1). It contains the following subsections:
•
•
Cisco Unified Serviceability
This section contains the following subsections:
•
•
•
Browser Requirements
The following browser requirements apply to Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, Bulk Administration Tool, Cisco Unified Communications Operating System, Disaster Recovery System, and Cisco Unified Reporting:
•
•
New Enterprise Parameters for Cisco Syslog Agent
Cisco Syslog Agent forwards all alarms that meet or exceed the configured threshold to a remote syslog server with two settings: remote syslog server name and syslog severity. The alarms include system (OS/hardware platform), application (services), and security alarms. If the server name is not specified, Cisco Unified Serviceability does not send any syslog messages.
The following tips should be considered:
•
•
•
•
Configuring the Application Billing Servers
There are two new billing application server configuration parameters:
•
•
Vendor-Supported MIB OIDs
See Chapter 9 "Vendor-Specific Management Information Base" to find the Object IDs (OIDs) for vendor-supported MIBS.
Cluster Service Activation Node Recommendations
The "Configuring Services" chapter in the Cisco Unified Serviceability Administration Guide describes the recommendations for cluster service activation for specific nodes in a cluster.
Alarm Additions and Changes
•
Table 2-8 lists the differences in the TFTP alarm names from Cisco Unified CM Release 6.1(2) to Release 7.0(1).
•
–
–
•
•
•
–
–
–
•
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
IPV6Address
IPAddrAttributes
IPV6AddrAttributes
Additional Reason codes
–
IPV6Address
IPAddrAttributes
IPV6AddrAttributes
ActiveLoadId
Additional Perfmon types and Device types
–
IPV6Address
IPAddrAttributes
IPV6AddrAttributes
Additional Device types
–
IPV6Address
–
IPV6Address
Removed Alarms
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Existing/Inapplicable Alarms
The following alarms exist but no longer apply to Cisco Unified CM Release 6.1 or Release 7.0(1):
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Real-Time Monitoring Tool
This section contains these subsections:
•
•
Perfmon Counters Added
Four new perfmon counters are added and are described in the following paragraphs:
•
•
•
•
Preconfigured Perfmons Added
Table 2-9 describes new preconfigured perfmons.
CTIManager Improved Throughput
The following new alarms, counters, and alerts support the spare partition:
•
–
–
•
–
•
–
–
Simultaneous Alert Configuration
All pre-canned alerts initially get assigned a default alert action. The default alert action configures the alerts for syslog and alert logging. When you add e-mail destinations to the default alert action, all precanned alerts get sent to those recipients. Updating the default alert action impacts all alerts that you configured. You cannot remove the default alert action.
Refer to the Cisco Unified Real-Time Monitoring Tool Administration Guide for the configuration procedure that adds the default alert action for all precanned alerts simultaneously.
Cisco Unified Communications Manager CDR Analysis and Reporting
This section contains the following subsections:
•
•
•
•
•
•
•
Backup of CAR Database
The CAR and CDR Disaster Recovery Service (DRS) now integrates into the Disaster Recovery System (DRS). The DRS includes the backup of the CAR database, pregenerated reports, and the CDR preserved flat files.
New CDR Service Parameters
The following new service parameters can affect CDR/CMR records:
•
•
•
Supported Versions of FTP/SFTP for Billing Servers
The CDR Repository Manager sends CDR files to preconfigured destinations (up to three billing servers) that are using FTP/SFTP. Ensure that your billing server uses one of the following Cisco tested and supported versions of FTP or SFTP:
•
–
–
•
–
–
Configuring Individual and Department Bills Reports
Before you can configure the Individual or Department Bills reports, you must ensure that a device with an assigned Owner User ID exists, in the case of the Individual Bills reports, in Cisco Unified Communications Manager Administration for each user that is included in the report. In the case of the the Department Bills report, you must ensure that a device with an assigned Owner User ID and Manager User ID exists in Cisco Unified Communications Manager Administration for each user that is included in the report.
For both individual bills and department bills, if the Extension Mobility feature is enabled on the device and the user logs into the phone and places a call, the User ID that gets recorded in the CDRs represents the logged in User ID. If Cisco Extension Mobility is not enabled on the device, the User ID that gets recorded in the CDRs specifies the Owner User ID that is configured for the device.
In the situation in which the User ID or the Owner User ID are not configured (that is, Cisco Extension Mobility is not enabled, and the Owner User ID is not configured), the User ID field in the CDRs gets recorded as blank. CAR uses the default User ID of "_unspecified user" when it loads the CDRs, and the CDRs do not display in the Individual Bills User reports because no user by the name of "_unspecifieduser" exists in the Cisco Unified Communications Manager database.
If you look for the reports for a particular end user in the directory, the User ID for the particular end user must be configured as the Owner User ID for the device or the particular end user must have logged in to the device with the Cisco Extension Mobility feature enabled.
Configuring CDR Error Reports
To determine why the error records failed the CDR Load, you must review the information in the tbl_error_id_map table. Refer to the CDR Analysis and Reporting Administration Guide.
Configuring the CDR Load Schedule
The default batch size specifies 600 CDR or CMR. The default sleep time between each CDR batch equals 2500 ms and 3000 ms for each CMR batch. However, you can configure the batch size from the tbl_system_preferences table "Loader Batch" column to have any value between 50 and 2000.
Manual Purging or Reloading the CAR Database
Manual purging of the CDRs stops if the CAR Web Service is stopped during the manual purge process. Manual purging cannot begin again until the CAR Web Service restarts. Then, you must begin the manual purge process again. The CDR Loader cannot begin again until either the CAR Web Service or the CAR Scheduler gets restarted. Refer to the CDR Analysis and Reporting Administration Guide.
Task Monitor and Database Maintenance
Cisco Unified Communications Manager introduced the Task Monitor and Database Maintenance features. The Task Monitor begins about 1 minute after the Scheduler starts, and 1 minute after the Scheduler repopulates the schedules every day at midnight (00.00). The Task Monitor periodically (every 5 minutes) monitors the status of all jobs for the day from the tbl_event_log with the exception of the following jobs: PopulateSchedules, TaskMonitor, DatabaseMaintenance, and DailyCdrLoad.
When a task does not start on schedule because an earlier task is still running, you may see something like the following trace message:
2008-02-14 08:00:04, 602 WARN [main] services. Scheduler - runTasks(): Job [DailyCdrLoad] thread is busy, hence it will be removed from today's schedule and not be started!"The Scheduler has a grace period for 10 seconds to check whether the task thread is complete. The Scheduler sleeps up to 2 minutes total. If the task thread does not complete after the 2 minutes of wait time, the next task gets removed from the current schedule and does not run until its next scheduled time.
A new field, Scheduled, exists in the Event Log report status that includes tasks that have been scheduled but have not yet started. When the Scheduler restarts, all unfinished jobs with a status of Scheduled get deleted. Current jobs with the status of In Progress or Scheduled get changed to Unsuccessful.
Enabling or Customizing Reports for Automatic GenerationFor all new installations of Cisco Unified Communications Manager, you must first enable the e-mail alerts and reports for automatic generation. The default status for all reports and alerts is "Disabled." For all Cisco Unified Communications Manager upgrades from Release 5.x to a later release of Cisco Unified Communications Manager, the tbl_pregenmail_option table data migrates only if the CAR Scheduler service is active.
Cisco Unified Communications Manager Call Detail Records
This section contains the following subsections:
•
•
•
Partition/Extension Numbers in CDRs
The following new partition/extension numbers fields exist in a CDR record:
•
•
Calling Party Normalization and Support for Dialing "+" in CDRs
Cisco Unified Communications Manager supports Calling Party Normalization and dialing "+". The callingPartyNumber, originalCalledPartyNumber, finalCalledPartyNumber, lastRedirectDN, and the fields, outpulsedCallingPartyNumber and outpulsedCalledPartyNumber can now contain a "+" in the CDR. The device reports the calling party number that it outpulses to call control only if calling party normalization/localization takes place.
Call Park CDR Examples of New Service Parameters
The useGcidOfParkedCallEnabled service parameter includes the default value of False that provides, when a call is retrieved from park, Cisco Unified Communications Manager creates a new globalCallId. The value of True provides that, when the call is retrieved from park, Cisco Unified Communications Manager retains the original globalCallId. The following CDRs are examples of these scenarios.
Example 1
50003 calls 50002; 50002 presses the Park softkey. 50001 picks up the parked call by dialing the park code (44444).
Example 2
50003 calls 50002; 50002 presses the Park softkey. 50001 picks up the parked call by dialing the park code (44444).
Cisco Unified Reporting
In Cisco Unified Reporting, trace settings for the publisher server and cluster servers that do not match the publisher trace settings display in the Cisco Unified CM Cluster Overview report under Cisco Unified CM Trace Information.
For Cisco Unified CMBE, trace settings for the server display in the Cisco Unified CM Cluster Overview report under Cisco Unified CM Trace Information.
For a complete description of reports that are available on your system and the data that gets captured in a report, access the Report Descriptions report, as described in the Cisco Unified Reporting Administration Guide.
Cisco Unified Communications Manager Release 6.1(x)
This section describes the new and changed information in Cisco Unified Communications Manager Release 6.x . It contains the following subsections:
•
•
•
•
Cisco Unified Communications Manager Release 6.1(3)
This section contains the following subsections:
•
•
•
•
Cisco Unified Cisco Unified Real-Time Monitoring Tool
A change occurred in the Call State information that is collected from Cisco Unified Communications Manager/CTIManager and displayed in the Quality Report Tool (QRT) reports. Previously, the information included Connected, Connected Conference, Connected Transfer, and On Hook call state information. Now, the report only includes Connected and On Hook call state information.
Cisco Unified Communications Manager CDR Analysis and Reporting
This section contains these subsections:
•
•
•
•
•
•
Unavailable Reports to CAR Administrator
A CAR administrator can no longer generate CAR reports when a manual purge of the CAR database is in process or CDR records are reloading. The following message displays when you try to run reports during these processes:
10023: Manual Purge/Reload is in process. Please run the reports once the Manual Purge/Reload is over.Both the Purge button and the Reload All Call Detail Records button get disabled, and the following message displays on the Manual Purge window, when either a manual purge or CDR reload occurs:
Manual Purge/Reload is still running. User will not be allowed to run another instance of Manual Purge/Reload. So, both Purge and Reload All Call Detail Records buttons are disabled.Before this enhancement, a CAR administrator could request CAR reports during the purge, but message 10012 displayed.
CDR Search by User Extension Supports "+" and URLs for SIP Calls
When you use the CDR Search by User Extension feature, you may use the "+" in any position of the user extension number; however, the "+" cannot be used in any dial plan configurations. When the user extension number is a SIP call with a URL, the system allows no space in the URL.
Change in Supported FTP/SFTP Versions for CAR Billing Servers
Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to the following URL:
http://www.cisco.com/pcgi-bin/ctdp/Search.pl
For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to the following URL:
http://www.globalscape.com/gsftps/cisco.aspx
Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
•
•
•
Note
Cisco has tested and will support the following versions of FTP or SFTP for CAR billing servers:
•
•
Effects on CAR Data and Upgrade Cisco Unified Communications Manager
If you do not need to carry over your CAR data to Cisco Unified Communications Manager 6.1(3), Cisco recommends that you purge the CAR data before you run the Data Migration Assistant (DMA). Purging the CDR data speeds up the migration process and decreases the size of the DMA TAR file. Ensure that you purge any CAR records that are older than 180 days. See Upgrade of CAR Data for more information.
Ensure CAR Administrator Privileges Are Restored After Upgrade
When you use DMA to upgrade Cisco Unified Communications Manager, CAR users no longer have CAR administrator privileges after the upgrade and become standard end users. You must reset the CAR administrator privileges after the upgrade. Refer to the "Configuring CAR Administrators, Managers, and Users" section in the CDR Analysis and Reporting Administration Guide for more information on how to configure CAR administrators.
Configuring CDR Error Reports
To determine why the error records fail the CDR load, you must review the information in the tbl_error_id_map table.
Table 2-12 lists the CDR error codes and the definition of the error.
Table 2-12 CDR Error Codes
CDRs
31101
CDR globalCallID_callManagerId <= 0
31102
CDR globalCallID_callId <= 0
31103
CDR origLegCallIdentifier <= 0
31105
CDR dateTimeOrigination <= 0
31108
CDR destLegIdentifier <= 0
31110
CDR dateTimeConnect <= 0
31111
CDR dateTimeDisconnect <= 0
31119
CDR originalCalledPartyNumber is empty
31120
CDR finalCalledPartyNumber is empty
31122
CDR duration < 0
31137
CDR LDAP error while retrieving UserID or ManagerID
31139
CDR callingPartyNumber is empty
31147
CDR origDeviceName is empty
31148
CDR destDeviceName is empty
31151
CDR origCallTerminationOnBehalfOf < 0
31152
CDR destCallTerminationOnBehalfOf < 0
31153
CDR lastRedirectRedirectOnBehalfOf < 0
31155
CDR destConversationId < 0
31156
CDR globalCallId_ClusterID is empty1
Orig CMR
31123
Orig CMR globalCallID_callManagerId <= 0
31124
Orig CMR globalCallID_callId <= 0
31125
Orig CMR numberPacketsSent < 0
31126
Orig CMR numberPacketsReceived < 0
31127
Orig CMR jitter < 0
31129
Orig CMR callIdentifier <= 0
31149
Orig CMR deviceName is empty
31157
Orig CMR globalCallId_ClusterID is empty1
Dest CMR
31140
Dest CMR globalCallID_callManagerId <= 0
31141
Dest CMR globalCallID_callId <= 0
31142
Dest CMR numberPacketsSent < 0
31143
Dest CMR numberPacketsReceived < 0
31144
Dest CMR jitter < 0
31145
Dest CMR callIdentifier <= 0
31150
Dest CMR deviceName is empty
31158
Dest CMR globalCallId_ClusterID is empty1
1 Applies to Cisco Unified CM only and not to Cisco Unified CMBE.
New Error Message for Data in Invalid or Remainder Partitions
A message gets logged in the CAR Scheduler traces if data is present in invalid and remainder partitions of the tbl_billing_data and tbl_billing_error files.
The LWM/HWM/2M e-mail alerts that get sent to the CAR administrator when CAR detects records in either the part_invalid or part_remainder partitions will contain the following information:
Data is present in invalid/remainder partition also, which cannot be removed by Automatic-Purge. Please delete these record(s) manually from Manual-Purge.Cisco Unified Communications Manager Call Detail Records
For Cisco Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Cisco Unified Communications Manager restarts. In Release 4.x and earlier releases, even though the GlobalCallId field is time-based, the field gets reused under conditions of heavy traffic.
Because of this behavior, problems can occur with customer billing applications and the ability of CAR to correlate CMRs with CDRs and to correlate conference call CDRs. For Release 5.x and later releases, GlobalCallId redesign ensures the field retains a unique value, at least for a certain number of days.
Now, the last used globalCallId_callId value gets written to disk periodically (for every x number of calls). The value gets retrieved after a Cisco Unified Communications Manager restart, and the new globalCallId_callId value begins with this number plus x.
Cisco Unified Communications Manager Release 6.1(2)
This section contains the following subsections:
•
Cisco Unified Serviceability
The following list shows preconfigured alerts that are now available in Cisco Unified Serviceability:
•
•
•
•
•
Cisco Unified Communications Real-Time Monitoring Tool
Database Summary Includes Database Replication Information
RTMT displays information on predefined Cisco Unified Communications Manager objects in the monitoring pane when you select Communications Manager in the quick launch channel. It monitors the predefined objects on all nodes in the cluster. The Service category includes the Database Summary that now provides the number of replicates that have been created and the status of the replication in addition to the other types of connection information that was previously provided.
For more information, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
RTMT Critical Services
Cisco Unified Communications Manager Real-Time Monitoring Tool (RTMT) provides new states for the critical services that display in RTMT. The Critical Services monitoring category (choose Monitor > Server > Critical Services or click the Server button and Critical Services icon) provides the name of the critical service, the status (whether the service is starting, up, stopping, down, stopped by the administrator, not activated, or in an unknown state), and the elapsed time during which the services have existed in a particular state for the Cisco Unified Communications Manager server. For a specific description of each state, review the following information:
•
•
•
•
Tip
•
•
•
Adding RTMT Performance Counters in Bulk
On the RTMT Perfmon Monitoring pane, in table format only (not in chart format), you can now select multiple counters and multiple instances of counters, and add them all with a single click. Prior to this enhancement, you could add them only one at a time.
For more information, see the Cisco Unified Communications Manager Real-Time Monitoring Administration Tool Guide.
RTMT Trace and Log Central Disk IO and CPU Throttling
RTMT now supports the throttling of critical Trace and Log Central operations and jobs, whether they are running on demand, scheduled, or automatic. The effect of the throttling slows the operations when IO utilization is in high demand for call processing, so that call processing can take precedence.
For more information, see the Cisco Unified Communications Manager Real-Time Monitoring Administration Tool Guide.
Cisco Unified Communications Manager Release 6.1(1a)
This contains the following subsections:
•
•
CDR Analysis and Reporting Tool/Call Detail Record (CAR/CDR)
The following sections detail changes in CAR/CDR in release 6.1(1a) of Cisco Unified Communications Manager.
•
•
•
•
•
•
•
CAR System Scheduler Default Status
The CAR System Scheduler default status now specifies that CAR processes CDRs continuously 24 hours per day and 7 days per week. However, you can set the loading time, interval, and duration as needed. In addition, the default setting loads only CDR records. Call Management Records (CMR) records do not get loaded.
An option allows you to uncheck the "Load CDR Only" check box in the CAR System Scheduler window to allow CMR records to load.
Automatically Generated Reports
You can schedule CAR reports to generate automatically at a regular time. Each report that can be scheduled has its own report generation interval. In previous releases of Cisco Unified Communications Manager, the automatically generated reports default status specified Enabled. Beginning with Cisco Unified Communications Manager Release 6.1(1a), the default status specifies Disabled for the automatically generated reports. You must enable each automatically generated report after CAR is activated on your system.
Tbl_pregenmail_option Table Data
For all Cisco Unified Communications Manager upgrades from Release 5.x to a later release of Cisco Unified Communications Manager, the tbl_pregenmail_option table data migrates only if the CAR Scheduler service is active.
Calculation of the Utilization of H.323 Gateways
For calculation of the utilization of H.323 gateways, the system uses the port numbers from the CAR Gateway Configuration window. To find this window, choose System > System Parameters > Gateway Configuration. You cannot take port details for H.323 gateways from the Cisco Unified Communications Manager database because the H.323 port number always equals zero in the database. The user must update H.323 gateway ports information in the CAR Gateway Configuration window.
Be aware that the only port detail information that is taken from the CAR Gateway Configuration window is for those gateways that do not have port details that are available or that show zero in the Cisco Unified Communications Manager database.
CDR Search Reports Display Time in Two Ways
The CDR Search by User Extension, CDR Search by Gateway, CDR Search by Call Precedence Levels, and CDR Search for Malicious Calls reports now display current time in both Coordinated Universal Time (UTC) and local time and use the following rules:
•
•
•
•
CAR Scheduler Now a Network Service
Installed automatically, network services include services that the Cisco Unified Communications Manager Business edition system requires to function. Because these services are required for basic functionality, you cannot activate them in the Service Activation window. Cisco CAR Scheduler now represents a network service. In the previous release of Cisco Unified Communications Manager Business Edition the Cisco CAR Scheduler represented a feature service.
Cisco Unified Communciations Manager Release 6.1(1b)
This section contains the following noncomprehensive list of caveats that were resolved in this release of Cisco Unified CM:
•
•
•
•
•
•
•
Cisco Unified Communications Manager Release 6.0(1x)
This section describes the new and changed information in Cisco Unified Communications Manager Release 6.0(1x). It contains the following subsections:
•
•
•
Cisco Unified Communications Manager Release 6.0(1)
This section describes the new and changed information in Cisco Unified Communications Manager Release 6.0(1). It contains the following subsections:
•
•
•
•
•
No Such Name Error in SNMP Response
If the getbulk/getnext/getmany request contains multiple OID variables in its request PDU and the subsequent tables appear empty in the CISCO-CCM MIB, the responses may include NO_SUCH_NAME, for SNMP v1 version or GENERIC_ERROR, for SNMP v2c or v3 version because the time that it takes to process the SNMP requests exceeds the MasterAgent timeout duration (currently set at 25 seconds).
Perform the following workaround:
•
•
•
•
•
•
Note
Maximum Trace Settings
The maximum recommended Cisco Unified Communications Manager trace settings specifies 2,500 files of 2 MB each, for SDI and SDL traces, for a combined total of 5000 files. You can increase SDI traces to 5,000 files if SDL traces are disabled, but not vice versa. All other components should stay within 126 MB bucket (for example, 63 files of 2 MB). If you increase logs past the recommended limit, system performance gets reduced due to IOWAIT. After the system experiences IOWAIT related performance degradation, the only solution requires you to lower traces and use RTMT to remove all CCM/CTI SDI/SDL traces. For that reason, you should limit tracing to 5 GB for CCM and 5 GB for CTI.
Terminal Server Causes RTMT to Display Repeating Syslog and Alert Messages
When a terminal server is connected to the serial port of a Cisco Unified Communications Manager server, the system generates a repeating alert message and corresponding syslog message similar to the following examples:
•
•
This includes a router that is being used as a terminal server.
Cisco recommended that you configure no exec on the lines that are connected to the console of the other devices.
Secure Conferencing and CRD Data
The Secure Conferencing feature provides authentication and encryption to secure a conference. CDR data provides the security status of each call leg from the phone endpoint to the conference bridge as well as the security status of the conference itself. The two values use two different fields inside the CDR database. CDR data provides termination cause code 58 (Bearer capability not presently available) when a Meet-Me conference rejects a join attempt that does not meet the minimum security level requirement. There are no new performance objects, counters, or alarms.
Cisco Unified Serviceability
Cisco Unified Serviceability allows you to perform such tasks as configuring trace parameters, configuring alarms, and activating, starting, and stopping services for Cisco Unified Communications Manager.
The Cisco Unified Serviceability GUI contains the following additions and changes:
•
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
The Cisco Unified Serviceability Administration Guide describes all the other catalogs, which existed in previous releases.
Cisco Unified Communications Real-Time Monitoring Tool
The Cisco Unified Communications Manager Cisco Unified Real-Time Monitoring Tool contains the following changes:
•
•
•
•
–
–
–
–
•
–
–
–
–
–
–
–
–
–
Cisco Unified Communications Manager CDR Analysis and Reporting
The Cisco Unified Communications Manager CDR Analysis and Reporting (CAR) application The following changes apply to CAR:
•
•
–
–
•
•
•
•
•
•
•
•
This change applies mainly to H.323 gateways and to any other gateways that have no port information available in the Cisco Unified Communications Manager database. The Cisco Unified Communications Manager database includes port information for most of the other types of gateways.
•
Call Detail Record Definitions
This section describes the changes to the CDRs and CMRs with this release.
•
•
The requestor party (party that requested the removal of a participant) appears in the CDR comment field to track the drop requestor because the requestor can be a participant other than the controller. The following tags apply for the originator information: ConfRequestorDn and ConfRequestorDeviceName. The tags for the drop requestor information include DropConfRequestorDn and DropConfRequestorDeviceName.
•
–
–
–
–
•
Two new redirect reasons exist:
–
–
Two new OnBehalfOf values exist:
–
–
The destconversationID field of the Monitoring call CDR will match the agent call leg identifier in the CDR of the call that is monitored. This will link the monitored call CDR and the monitoring call CDR together.
The origconversationID field of the two Recording call CDRs will match the agent call leg identifier in the recorded call CDR. This conversation ID will link the recorded call CDR and the CDRs that the recording calls generate.
•
•
The release adds the following new bandwidth fields to the CDR:
–
–
•
One new OnBehalfOf value exists:
–
Four new Redirect Reason values exist:
–
–
–
–
•
•
•
–
–
•
The release adds value of 2 = CMR record to the cdrRecordType CMR field.
Cisco Unified Communications Manager Release 6.0(1a)
This section describes the new and changed information in Cisco Unified Communications Manager Release 6.0(1a). It contains the following subsections:
•
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
Sporadic reboots of the 7825H2 servers get triggered during long system hangs. ASR functionality autorecovers the servers after 10 minutes of kernel unresponsiveness. Event timing ranges from once every 3 months to once every 3 days. To work around the issue, see http://www.cisco.com/warp/public/770/fn62850.shtml.
Cisco Unified Communications Manager Release 6.0(1b)
This section describes the new and changed information in Cisco Unified Communications Manager Release 6.0(1b). It contains the following subsections:
Resolved Caveats
The following list gives the caveats that are useful for Cisco Unified Serviceability, Cisco Unified RTMT, and Cisco Unified CAR and that were resolved in this release of Cisco Unified CM:
•
•
•
•
•
•
•
•
•
