 Feedback
|
Table Of Contents
Release Notes for Cisco Intercompany Media Engine Release 8.0(3)
Upgrading to Cisco Intercompany Media Engine 8.0(3)
Making Configuration Changes During an Upgrade
Upgrading From an Engineering Special
The Latest Software Upgrades for Cisco Intercompany Media Engine on Cisco.com
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
New and Changed Information 8.0(3)
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:
•
Upgrading to Cisco Intercompany Media Engine 8.0(3)
•
•
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
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:
•
•
•
•
•
•
•
•
•
•
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
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
1.
To do that, from the CLI, execute the show version active command.
2.
Special Upgrade Information
The following sections include information that you must know before you begin the upgrade process.
•
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
Upgrade Tasks
Note
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 peerIDStatusPeer ID = 159ee0371f25ca4059f4dec844d33245Peer State........................... = JOINEDDHT Health........................... = GREENDHT Stored Records................... = 3DHT Stored Data (Bytes).............. = 18015Route Table Size..................... = 8Num Client Conn...................... = 7Num Server Conn...................... = 1Upgrade
To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.
Procedure
Step 1
Tip
Step 2
Step 3
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/public/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
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
This section describes the limitations for the Cisco Intercompany Media Engine (Cisco IME) and the interactions with other features.
Limitations
•
•
•
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
Example: hostname(config)# object network ucm_real_1Step 2
Example: hostname(config-network-object)# host 192.168.10.30Step 3
Example: hostname(config-network-object)# description "Cisco UCM #1 Real IP Address"Step 4
Example: object ucm_real_2 will contain host 192.160.10.31Step 5
Example: hostname(config) # object network ucm_map_1Step 6
Example: hostname(config-network-object) # host 209.165.200.227Step 7
Example: hostname(config-network-object)# description "Cisco UCM Translated IP Address"Step 8
Example: object ucm_map_2 will contain host 209.165.200.228Step 9
Example:hostname(config)# object network ucm_real_1hostname(config-network-object)# nat (inside,outside) static ucm_map_1hostname(config-network-object)# exithostname(config)# object network ucm_real_2hostname(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
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
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:
•
•
•
•
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 peerIDStatusCertSize: 10 PeersPeer ID = 9bb51c8746d78f92d169ec44081154f3Peer State........................... = JOINEDDHT Health........................... = GREENDHT Stored Records................... = 4DHT Stored Data (Bytes).............. = 24594Route Table Size..................... = 3Num Client Conn...................... = 2Num Server Conn...................... = 1Message 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 2010Message = 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:
•
Note
The following example displays the VCRs on the Cisco Intercompany Media Engine with the calling number +19876543210:
admin:show ime voicerecord details callingDN +19876543210Orig: called = +12324324366 calling = +19876543210 VService = d304000029090000Orig: called = +12324324356 calling = +19876543210 VService = d304000029090000Orig: called = +12324324376 calling = +19876543210 VService = d304000029090000Term: called = +12324324256 calling = +19876543210 VService = d204000057040000Term: called = +12324324266 calling = +19876543210 VService = d204000057040000•
•
•
admin:add ime vapserver bldrcucm2 5622In this release, you enter the following command:
admin:add ime vapserverctrl-c: To quit the input.Vapserver name:: bldrcucm2Port number (must be unique on this server): [5620]:: 5622Enter the authenticationmode(encrypted|authenticated) [encrypted]::Record added successfully
Note
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
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:
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•
•
•
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1
Step 2
Step 3
Tip
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
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.
•
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
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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)
