Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Intercompany Media Engine Release 8.0(3)

  • Viewing Options

  • PDF (525.0 KB)
  • Feedback
Release Notes for Cisco Intercompany Media Engine Release 8.0(3)

Table Of Contents

Release Notes for Cisco Intercompany Media Engine Release 8.0(3)

Contents

Introduction

System Requirements

Server Support

Uninterruptible Power Supply

Upgrading to Cisco Intercompany Media Engine 8.0(3)

Before You Begin

Special Upgrade Information

Write-Cache

Making Configuration Changes During an Upgrade

Ordering the Upgrade Media

Upgrading From an Engineering Special

The Latest Software Upgrades for Cisco Intercompany Media Engine on Cisco.com

Service Updates

Related Documentation

Limitations and Restrictions

Important Notes

Cisco Intercompany Media Engine Limitations and Interactions

CSCtf84703 utils system upgrade initiate listall - CLI Command Issue

CSCti60604 Several syntax and command changes needed in IME ASA setup guide

Configuring NAT for Cisco Intercompany Media Engine Proxy

(Optional) Configuring TLS within the Local Enterprise

Enabling SIP Inspection for the Cisco Intercompany Media Engine Proxy

Validation Parameters

Set the VAP Interface Between the Cisco IME Servers and the Associated Cisco Unified CMs to Encrypted

NTP Server Configuration

Customer Information

CSCti38763 Certificates switched in Configure TLS within the Local Enterprise of IME Installation and Configuration guide

New and Changed Information 8.0(3)

Caveats

Resolved Caveats

UsingBug Toolkit

Open Caveats

Open Caveats for Cisco Intercompany Media Engine Release 8.0(3) As of July 19, 2010

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Intercompany Media Engine Release 8.0(3)


July 26, 2010

This document contains information pertinent to Cisco Intercompany Media Engine (IME) Release 8.0(3).

Contents

This document includes the following information:

Introduction

System Requirements

Upgrading to Cisco Intercompany Media Engine 8.0(3)

Service Updates

Related Documentation

Important Notes

New and Changed Information 8.0(3)

Caveats

Obtaining Documentation and Submitting a Service Request

Introduction

The Cisco Intercompany Media Engine server and software function as a key component of the Cisco Intercompany Media Engine feature that provides a technique for establishing direct IP connectivity between enterprises by combining peer-to-peer technologies with the existing public switched telephone network (PSTN) infrastructure.

System Requirements

The following sections comprise the system requirements for this release of Cisco Intercompany Media Engine.

Server Support

Uninterruptible Power Supply

Server Support

Make sure that you install and configure Cisco Intercompany Media Engine on a Cisco Media Convergence Server (MCS), a Cisco Unified Computing System (UCS) server, or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.

The following servers are compatible with this release:

MCS-7825-H2

MCS-7825-I2

MCS-7825-H3

MCS-7825-I3

MCS-7825-H4

MCS-7825-I4

MCS-7845-H2

MCS-7845-I2

MCS-7845-H3

MCS-7845-I3

Uninterruptible Power Supply

Cisco recommends that you connect each Cisco Intercompany Media Engine server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.


Note You must connect MCS-7825 servers to a UPS to prevent file system corruption during power outages.


Upgrading to Cisco Intercompany Media Engine 8.0(3)

The following sections contain information that is pertinent to upgrading to this release of Cisco Intercompany Media Engine.

Before You Begin

Special Upgrade Information

The Latest Software Upgrades for Cisco Intercompany Media Engine on Cisco.com

Upgrading From an Engineering Special

Before You Begin

1. Before you upgrade the software version of Cisco Intercompany Media Engine verify your current software version.

To do that, from the CLI, execute the show version active command.

2. Read the "Special Upgrade Information" section.

Special Upgrade Information

The following sections include information that you must know before you begin the upgrade process.

Write-Cache

Making Configuration Changes During an Upgrade

Write-Cache

A disabled write-cache on the server causes the upgrade process to run more slowly. Multiple factors, including dead batteries on older servers, can cause the write-cache to get disabled.

If you determine that your write-cache is disabled because of a dead battery, you need to replace the hard disk controller cache battery. Follow your local support procedures to get this battery replaced.

To determine the status of the write-cache, from the CLI, execute the show hardware command.

Making Configuration Changes During an Upgrade

The administrator must not make any configuration changes to Cisco Intercompany Media Engine during an upgrade. Configuration changes include any changes that you make by using the command line interface (CLI).

If you are upgrading your system, you must complete the upgrade tasks in this section before you perform any configuration tasks.


Caution If you fail to follow these recommendations, unexpected behavior may occur; for example, ports may not initialize as expected.

Upgrade Tasks


Note When the IME server gets upgraded, the services that communicate with IME service on the Cisco Unified Communications Manager stops. This causes the Cisco Unified Communications Manager to temporarily stop learning routes until the upgrade completes, and the IME server gets switched to the new release. During this time, an alert displays on Cisco Unified Communications Manager, indicating that the IME service is down.

To minimize impact on the Cisco Unified Communications Manager, Cisco recommends that you upgrade the IME server during a quiescent period. The upgrade procedure takes 20-30 minutes, so the time that the IME service is unavailable is minimal.


Check System Health

Before beginning the upgrade, check system health by using the CLI command show ime dht peerIDStatus

The health of each peer should be GREEN (meaning no network problems) before you upgrade.

Example

admin:show ime dht peerIDStatus
 
   
Peer ID = 159ee0371f25ca4059f4dec844d33245
    Peer State........................... = JOINED
    DHT Health........................... = GREEN
    DHT Stored Records................... = 3
    DHT Stored Data (Bytes).............. = 18015
    Route Table Size..................... = 8
    Num Client Conn...................... = 7
    Num Server Conn...................... = 1

Upgrade

To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.

Procedure


Step 1 Stop all configuration tasks; that is, do not perform configuration tasks.


Tip For detailed information about the upgrade process, see the Cisco Intercompany Media Engine Installation and Configuration Guide.


Step 2 Perform the upgrade.

Step 3 When the upgrade completes, you can perform configuration tasks as required.


Ordering the Upgrade Media

To upgrade to Cisco IME Release 8.0(2), use the Product Upgrade Tool (PUT) to obtain a media kit and license or to purchase the upgrade from Cisco Sales.

To use the PUT, you must enter your Cisco contract number (Smartnet, SASU or ESW) and request the DVD/DVD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.

For more information about supported Cisco IME upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html

For more information, see the Cisco Intercompany Media Engine Installation and Configuration Guide.

Upgrading From an Engineering Special

If you want to upgrade to this release of Cisco IME and you are currently running an Engineering Special (ES), contact TAC to obtain the fixes that are included in the ES that you currently use.

The Latest Software Upgrades for Cisco Intercompany Media Engine on Cisco.com

You can access the latest software upgrades for this release of Cisco Intercompany Media Engine from http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Service Updates

After you install or upgrade to this release of Cisco Intercompany Media Engine, check to see if Cisco has released critical patches or Service Updates. Service Updates, or SUs, contain fixes that were unavailable at the time of the original release, and often include security fixes, firmware updates, or software fixes that could improve operation.

To check for updates, from www.Cisco.com, select Support > Download Software . Navigate to the "Voice and Unified Communications" section and select IP Telephony > Call Control > Cisco Unified Communications Manager (CallManager) > the appropriate version of Cisco Intercompany Media Engine for your deployment.

For continued notification of updates for your Cisco products, subscribe to the Cisco Notification Service at:

http://www.cisco.com/cisco/support/notifications.html

Related Documentation

You can view documentation that supports this release of Cisco Intercompany Media Engine at http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html

Limitations and Restrictions

A list of compatible software releases represents a major deliverable of Cisco Unified Communications Manager System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.

For a list of software and firmware versions of IP telephony components and contact center components that were tested for interoperability with Cisco Unified Communications Manager 8.0(2) as part of Cisco Unified Communications System Release 8.1 testing, see

http://www.cisco.com/go/unified-techinfo


Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CM, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CM Release 8.0(2). For the most current compatibility combinations and defects that are associated with other Cisco Unified CM products, refer to the documentation that is associated with those products.


Important Notes

The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Intercompany Media Engine Release 8.0(2).

Cisco Intercompany Media Engine Limitations and Interactions

CSCtf84703 utils system upgrade initiate listall - CLI Command Issue

CSCti60604 Several syntax and command changes needed in IME ASA setup guide

Validation Parameters

Set the VAP Interface Between the Cisco IME Servers and the Associated Cisco Unified CMs to Encrypted

NTP Server Configuration

Customer Information

CSCti38763 Certificates switched in Configure TLS within the Local Enterprise of IME Installation and Configuration guide

Cisco Intercompany Media Engine Limitations and Interactions

This section describes the limitations for the Cisco Intercompany Media Engine (Cisco IME) and the interactions with other features.

Limitations

Cisco IME learned routes do not get generated when a user makes a Mobile Voice Access call from a remote destination to another enterprise.

When endpoints with Cisco IME-enrolled DIDs are remotely located with VPN connectivity into the enterprise, latency and jitter characteristics for calls with these endpoints will be amplified and could result in the Cisco IME-enabled ASAs triggering more frequent fallbacks to the PSTN. If fallbacks occur too frequently for a specific endpoint, it might be necessary either to configure these devices with a device pool that has a fallback profile with no fallback enabled, to lower the fallback sensitivity levels, or to remove the enrolled DID from Cisco IME.

When a Cisco IME call gets placed and a loss of Internet connectivity between enterprises occurs, the originating Cisco Unified Communications Manager initiates a call over the PSTN. The initial Invite from the originating Cisco Unified Communications Manager causes the called phone in the terminating enterprise to ring. When the PSTN call reaches the phone in the terminating cluster, a second call occurs on the called phone. If the first call still exists on the phone, the user called party sees two calls on the phone—the actual call and a ghost call.

Interactions (Number-to-Remote-Destination Mapping)

If the Remote Destination exists as a learned pattern in the Cisco IME network, calls that are targeted for Remote Destination get rerouted over Cisco IME.

CSCtf84703 utils system upgrade initiate listall - CLI Command Issue

Symptom

Executed the utils system upgrade initiate listall CLI command, but no filtered items display.

Conditions

Upgrading Cisco IME by using the CLI.

Workaround

Examine the upgrade log for filter log messages which indicate filtered items and the reason for them being filtered out of the valid upgrade item list.

CSCti60604 Several syntax and command changes needed in IME ASA setup guide

The following procedures have been corrected for Caveat CSCti60604:

Configuring NAT for Cisco Intercompany Media Engine Proxy

To configure auto NAT rules for the Cisco UCM server, complete the following steps:


Step 1 Run the following command to set up a network object for the real address of Cisco UCM that you want to translate: hostname(config)# object network name

Example: hostname(config)# object network ucm_real_1
 
   

Step 2 Run the following command to specify the real IP address of the Cisco UCM host for the network object: hostname(config-network-object)# host ip_address

Example: hostname(config-network-object)# host 192.168.10.30
 
   

Step 3 (Optional) Run the following command to provide a description of the network object: hostname(config-network-object)# description string

Example: hostname(config-network-object)# description "Cisco UCM #1 Real IP Address"
 
   

Step 4 Repeat steps 1 through 3 for any other Cisco UCM nodes that you want to translate. hostname(config-network-object)# host ip_address

Example: object ucm_real_2 will contain host 192.160.10.31
 
   

Step 5 Run the following command to set up a network object for the outside (translated) addresses of Cisco UCMs: hostname(config)# object network name

Example: hostname(config) # object network ucm_map_1
 
   

Step 6 Run the following command to specify the translated IP address of the Cisco UCM host for the network object: hostname(config-network-object)# host ip_address

Example: hostname(config-network-object) # host 209.165.200.227
 
   

Step 7 (Optional) Run the following command to provide a description of the network object:hostname(config-network-object)# description string

Example: hostname(config-network-object)# description "Cisco UCM Translated IP Address"
 
   

Step 8 Repeat steps 5 through 7 for any other Cisco UCM nodes that you want to translate.

Example: object ucm_map_2 will contain host 209.165.200.228
 
   

Step 9 Run the following command to specify the address translation on the network objects created in this example:

Example:
hostname(config)# object network ucm_real_1
hostname(config-network-object)# nat (inside,outside) static ucm_map_1
hostname(config-network-object)# exit
hostname(config)# object network ucm_real_2
hostname(config-network-object)# nat (inside,outside) static ucm_map_2
 
   

(Optional) Configuring TLS within the Local Enterprise

The trustpoint needs to be enrolled before an identity certificate can be exported. The following step was added after step 2 of the procedure(Optional) Configuring TLS within the Local Enterprise:

Enroll the trustpoint before exporting the identity certificate. (config mode) crypto ca enroll <trustpoint>

The trustpoint in this case is local-asa.

Enabling SIP Inspection for the Cisco Intercompany Media Engine Proxy

In Step 9 and 12 of the procedure Enabling SIP Inspection for the Cisco Intercompany Media Engine Proxy, the "inspect" syntax is incorrect. The correct syntax is:

inspect sip [sip_map] uc-ime <uc_ime_map> tls-proxy <proxy_name>

Validation Parameters

The Cisco IME server relies on validation parameters to establish the security (number of calls required to learn a route) for call validation. By default, the system uses "medium security" values, and these values are designed to provide a sufficient level of security for most Cisco IME deployments. These "medium security" values will require multiple calls to numbers enrolled at a remote Cisco IME server before any routes can be learned to Cisco Unified Communications Manager servers attached to that Cisco IME server. It may take 2 hours or more before a route is learned even if there is a sufficient call volume to numbers enrolled at a remote Cisco IME server. During system installation and configuration, you may wish to see a validation happen quickly. This can be done by lowering the validation parameter settings. It is very important to note: if you set these parameters low for testing, be sure to set them back to their default settings as soon as installation/testing is complete. This will insure good security for normal system operation.

To set the values to minimum security levels, use the ime validator minsecurity CLI command. To reset the values to default security levels, use the ime validator defaultsecurity CLI command.

Set the VAP Interface Between the Cisco IME Servers and the Associated Cisco Unified CMs to Encrypted

Cisco recommends that you set the VAP interface between the Cisco IME servers and the associated Cisco Unified Communications Manager servers to encrypted.

Check to see if the authentication mode for all vapservers is already set to "Encrypted" by executing the show ime vapserver all command from the Cisco IME server CLI.

If they are not set to encrypted, refer to the Cisco Intercompany Media Engine Installation and Configuration Guide for instructions.


Note To set encryption, you will have to change the configuration setting on the Cisco Unified Communications Manager, set the vapserver authentication mode on the Cisco IME server, and install certificates.


When adding a new vapserver using the add ime vapserver CLI command, you get prompted for the parameters, including the encryption mode.

NTP Server Configuration

The Cisco IME server requires a properly functioning NTP server configuration.

To verify NTP operation, execute the utils ntp status CLI command and insure that the Cisco IME server is connected to the appropriate NTP server and that the UTC and local times are correct.

Customer Information

The Cisco IME server stores contact information for your location which allows Cisco IME administration to contact you if the server is not configured properly (if, for example, it rejects connections from other servers).

To display the customer information settings, execute the show ime customerinfo command.

To change or add to the customer information settings, exectue the set ime customerinfo command. You will be prompted for contact information.

CSCti38763 Certificates switched in Configure TLS within the Local Enterprise of IME Installation and Configuration guide

The following changes are made to the procedure Configure TLS within the Local Enterprise of the Intercompany Media Engine Installation and Configuration Guide:

Step 7 Commands:

hostname(config)# tls-proxy proxy_name

hostname(config-tlsp)# server trust-point trustpoint_name

hostname(config-tlsp)# client trust-point proxy_trustpoint

hostname(config-tlsp)# client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1

Example:

hostname(config)# tls-proxy local_to_remote-ent

hostname(config-tlsp)# server trust-point local-asa

hostname(config-tlsp)# client trust-point local-ent

hostname(config-tlsp)# client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1

Step 7 Purpose:

Updates the TLS proxy for outbound connections.

Where proxy_name is the name you entered in Step 1 of the task Creating the TLS Proxy.

Where trustpoint_name for the server trust-point command is the name you entered in Step 1 of this procedure.

Where proxy_trustpoint for the client trust-point command is the name you entered in Step 2 of the task Creating Trustpoints and Generating Certificates.

Note In this step, you are creating different trustpoints for the client and the server.

Step 9 Commands:

hostname(config)# tls-proxy proxy_name

hostname(config-tlsp)# server trust-point proxy_trustpoint

hostname(config-tlsp)# client trust-point trustpoint_name

hostname(config-tlsp)# client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1

Example:

hostname(config)# tls-proxy remote_to_local-ent

hostname(config-tlsp)# server trust-point local-ent

hostname(config-tlsp)# client trust-point local-asa

hostname(config-tlsp)# client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1

Step 9 Purpose:

Updates the TLS proxy for inbound connections.

Where proxy_name is the name you entered in Step 5 of the task Creating the TLS Proxy.

Where proxy_trustpoint for the server trust-point command is the name you entered in Step 2 of the task Creating Trustpoints and Generating Certificates.

Where trustpoint_name for the client trust-point command is the name you entered in Step 1 of this procedure.

New and Changed Information 8.0(3)

This section contains information on the following topics:

Description

Peer ID Changes

Message of the Day Changes

CLI Changes

Description

Enhancements to the Cisco Intercompany Media Engine (Cisco IME) server software in this release facilitate troubleshooting and allow for directed communications to individual servers on the network. The enhancements include the following:

Only one peer ID in the license (and GoDaddy certificate) joins the IME Distributed Cache ring, compared to 5 to 10 peer IDs per server in the 8.0(2) release. By limiting the number of peer IDs needed to join the ring, Cisco has reduced memory usage and number of required TLS connections as well as facilitated troubleshooting for the Cisco IME server. For more information, see the "Peer ID Changes" section.

New parameters for the show ime voicerecord details command allow you to filter VCR results on called number, calling number, originating calls, and terminating calls. For more information, see the "CLI Changes" section.

New command line interface (CLI) commands allow you to easily set validation parameters to minimal values to enable testing on a newly installed system and then to resest validation parameters to default values. For more information, see the "CLI Changes" section.

Bootstrap administrators can send a directed message of the day to a single server in addition to a message of the day to all servers. Administrators view these messages using the show ime motd command. For more information, see the "Message of the Day Changes" section.

Peer ID Changes

For each Cisco IME server, the license (and certificate from GoDaddy) contains either 5 or 10 peer IDs, depending on server type. In the 8.0(2) release, each peer ID joined the IME Distributed Cache ring. You could check the status of each peer ID by using commands such as show ime dht peerIDStatus.

In the 8.0(3) release, each license and certificate contains the same number of peer IDs, depending on the server type, but only one peer ID joins the ring. This facilitates debugging and reduces TLS connection and memory requirements. The following example shows the output of the show ime dht peerIDStatus command:

admin:show ime dht peerIDStatus
CertSize: 10 Peers
 
   
Peer ID = 9bb51c8746d78f92d169ec44081154f3
    Peer State........................... = JOINED
    DHT Health........................... = GREEN
    DHT Stored Records................... = 4
    DHT Stored Data (Bytes).............. = 24594
    Route Table Size..................... = 3
    Num Client Conn...................... = 2
    Num Server Conn...................... = 1
 
   

Message of the Day Changes

In the 8.0(2) release, administrators can use the show ime motd command to view messages sent by the bootstrap server administrator. All servers receive the same message/alert. In this release, bootstrap administrators can send a directed message of the day to a single server.

When you use the show ime motd command, both the message of the day and the directed message of the day (if any) display. The following example shows the output of the show ime motd command when a directed message of the day exists:

admin:show ime motd
===============================================================
System Message of the Day (msg sent to all IME servers)
===============================================================
Message Id = Wed May  5 14:25:04 2010Message = Expect failed validations, having trouble 
on the DHT ring, hope to get this problem corrected by midnight.Repeat = 60 minutes 
Severity = notice
================================================================
Directed Message of the Day (msg sent to this IME server) 
===============================================================
Time Sent = Wed May  5 14:56:20 2010
Message = Your configuration looks good now. Thanks for updating your firewall.
Severity = notice
=============================================================== 

CLI Changes

The following CLI commands have been added or changed on the Cisco Intercompany Media Engine server:

show ime voicerecord details [calledDN | callingDN | orig | term | all]—In release 8.0(2), the show ime voicerecord details command displays all voice call records (VCRs) that the Cisco Unified Communications Manager creates and sends to the Cisco Intercompany Media Engine server after a user completes a PSTN call. This command enables administrators to ensure that VCRs are getting created and that the numbers are in +E.164 format. In this release, new parameters for this command allow you to filter VCR results on called number, calling number, originating calls, and terminating calls.


Note You must enter numbers in +E.164 format.


The following example displays the VCRs on the Cisco Intercompany Media Engine with the calling number +19876543210:

admin:show ime voicerecord details callingDN +19876543210
  Orig:  called = +12324324366    calling = +19876543210   VService = d304000029090000
  Orig:  called = +12324324356    calling = +19876543210   VService = d304000029090000
  Orig:  called = +12324324376    calling = +19876543210   VService = d304000029090000
  Term:  called = +12324324256    calling = +19876543210   VService = d204000057040000
  Term:  called = +12324324266    calling = +19876543210   VService = d204000057040000
 
   

set ime validator local minsecurity—This command allows administrators to set security parameters to a minimal security level so that Cisco Unified Communications Manager learns routes after validation of one PSTN call. By default, validation settings require 3 to 4 PSTN calls to the same directory number before Cisco Unified Communications Manager learns a Cisco IME route. You may want to use this command to lower security on a newly installed system to test Cisco IME functionality. Cisco recommends that you use default security settings during normal operation. After using this command, you may need to wait 5 minutes before it takes effect. To set security parameters back to the default settings, enter set ime validator local defaultsecurity.

set ime validator local defaultsecurity—This command allows administrators to set security parameters back to their default levels, so that Cisco Unified Communications Manager learns routes after validation of 3 to 4 PSTN calls. Cisco recommends that you use default security settings during normal operation.

add ime vapserver—In this release, the add ime vapserver command prompts you for parameters rather than requiring you to enter the name and port together. For example, in release 8.0(2), you would enter the following command:

admin:add ime vapserver bldrcucm2 5622
 
   

In this release, you enter the following command:

 
   
admin:add ime vapserver 
 
   
ctrl-c: To quit the input.
 
   
Vapserver name:: bldrcucm2
Port number (must be unique on this server): [5620]:: 5622
Enter the authenticationmode(encrypted|authenticated)  [encrypted]:: 
Record added successfully

Note Be sure the authentication mode entered here matches the value that you entered on the Cisco Unified Communications Manager server for this connection.


Caveats

The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity levels 1, 2, and 3.

Caveats describe unexpected behavior on a Cisco Intercompany Media Engine server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.

Resolved Caveats

You can find the latest resolved caveat information for Cisco Intercompany Media Engine Release 8.0 by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.


Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit.


UsingBug Toolkit

The system grades known problems (bugs) according to severity level. These release notes contain descriptions of the following bug levels:

All severity level 1 or 2 bugs.

Significant severity level 3 bugs.

You can search for problems by using the Cisco Software Bug Toolkit.

To access Bug Toolkit, you need the following items:

Internet connection

Web browser

Cisco.com user ID and password

To use the Software Bug Toolkit, follow these steps:

Procedure


Step 1 Access the Bug Toolkit, http://tools.cisco.com/Support/BugToolKit.

Step 2 Log in with your Cisco.com user ID and password.

Step 3 If you are looking for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field, and click Go.



Tip Click Help on the Bug Toolkit page for information about how to search for bugs, create saved searches, create bug groups, and so on.


Open Caveats

Open Caveats for Cisco Intercompany Media Engine Release 8.0(3) As of July 19, 2010 describe possible unexpected behaviors in Cisco Intercompany Media Engine Release 8.0(2), which are sorted by component.


Tip For more information about an individual defect, click the associated Identifier in the "Open Caveats for Cisco Intercompany Media Engine Release 8.0(3) As of July 19, 2010" section to access the online record for that defect, including workarounds.


Understanding the Fixed-in Version Field in the Online Defect Record

When you open the online record for a defect, you will see data in the "First Fixed-in Version" field. The information that displays in this field identifies the list of Cisco Intercompany Media Engine interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Intercompany Media Engine releases.

Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Intercompany Media Engine maintenance releases may not be as clearly identified.

The following example shows how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Intercompany Media Engine release that includes that interim version. You can use this examples as guidance to better understand the presentation of information in these fields.

8.0(2.20000-x) = Cisco Intercompany Media Engine Release 8.0(2)

Because defect status continually changes, be aware that the "Open Caveats for Cisco Intercompany Media Engine Release 8.0(3) As of July 19, 2010" section reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "UsingBug Toolkit" section.


Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


Open Caveats for Cisco Intercompany Media Engine Release 8.0(3) As of July 19, 2010

As of July 26, 2010, no open caveats exist for this release of Cisco Intercompany Media Engine.

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

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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 by using a reader application. Be aware that the RSS feeds are a free service, and Cisco currently supports RSS version 2.0.