Table Of Contents
Performing Your System Upgrade
Deployment Models
Single-Site Model
Multisite Centralized Model
Multisite Distributed Model
Clustering over the WAN (CoW) Model
Upgrading Components
Upgrading Contact Center Test Beds
Single-Stage Upgrade
Multistage System Upgrade
Verifying Multistage System Upgrades
Exit Criteria for Multistage System Upgrade Stages
Switches and Routers Upgrade Exit Criteria
Security Components Upgrade Exit Criteria
Gatekeepers and Voice and Data Gateways Upgrade Exit Criteria
Cisco IOS Gatekeeper and Cisco Unified Border Element Upgrade Exit Criteria
Cisco Aironet Access Point Upgrade Exit Criteria
Cisco IOS-based Transcoders and Conference Bridges Upgrade Exit Criteria
Network Management Components Upgrade Exit Criteria
Cisco Unified Intelligent Contact Management Enterprise Support Tools Server Upgrade Exit Criteria
Cisco Unified Intelligent Contact Management Enterprise Rogger/Progger Upgrade Exit Criteria
Cisco Real Time Administration Workstation, Historical Database Server, WebView Upgrade Exit Criteria
Peripheral, VRU and MRPG Gateways Upgrade Exit Criteria
Cisco Unified Contact Center Gateway Enterprise and Cisco Unified System Contact Center Gateway Upgrade Exit Criteria
Cisco Telephony Integration Object Server and Cisco Agent Desktop Server Upgrade Exit Criteria
Cisco Unified Outbound Option Upgrade Exit Criteria
Cisco Telephony Integration Object Server and Cisco Agent Desktop Agent/Desktop Clients Upgrade Exit Criteria
Cisco Unified Communications Manager Upgrade Exit Criteria
Cisco Unified Presence Upgrade Exit Criteria
Cisco Security Agent Management Console Upgrade Exit Criteria
Cisco Unified IP Phones Upgrade Exit Criteria
Cisco IP Communicator Upgrade Exit Criteria
Cisco Unified Customer Voice Portal Upgrade Exit Criteria
Cisco Unified IP IVR Upgrade Exit Criteria
Cisco Unity Connection Upgrade Exit Criteria
Related Documentation
Compatibility Guides
Component Release Notes and Installation and Upgrade Documents
Performing Your System Upgrade
This topic discusses in more detail the upgrade sequence for all the contact center components configured in specific deployment models for Cisco Unified Communications System Release 7.0(1).
Upgrade procedures for individual components are not described in this document, because they are available in individual component upgrade documents. See the Related Documentation section at the end of this topic for the appropriate upgrade documents and their URLs.
This topic contains the following sections:
•
Deployment Models
•Upgrading Components
•Related Documentation
 |
Note Many of the contact center component names have changed as part of Cisco Unified Communications System releases. Only the latest product names are used in this document, even when referencing products from previous releases.
|
Deployment Models
Upgrade procedures should be specifically tailored for each of the deployment models in the contact center test environment, because it is possible that each site includes different components.
Detailed information about these contact center deployment models at the different sites is available at: http://www.cisco.com/cisco/web/docs/iam/unified/ipcc701/Review_Tested_Deployment_Models.html
Listed in this section are the various deployment models tested in the Cisco Unified Communications contact center test environment:
•Single-Site Model
•Multisite Centralized Model
•Multisite Distributed Model
•Clustering over the WAN (CoW) Model
Compare these deployments to your specific deployment to best understand the upgrade process that is applicable in your environment. The following section provides the general upgrade sequence for the various contact center components in the different deployment models.
After you determine the general upgrade sequence, depending on the base release set in your network, use one of the upgrade strategies discussed in Upgrading Components to upgrade your components. Additional upgrade procedures for contact center components are discussed in Upgrading Contact Center Test Beds.
Single-Site Model
In the single-site model, upgrade the components in the following order:
1. Switches, routers and security components
2. Gatekeepers and voice and data gateways
3. Network management components
4. Contact center routing components
5. Agent management components
6. Agent desktop client software
7. Call processing components
8. Queuing and self-service components
|
Note In a Unified CVP implementation, it is recommended to perform the upgrade of the voice and data gateways in the same maintenance window as Unified CVP.
|
9. Messaging components
Multisite Centralized Model
In the multisite centralized model, upgrade the central site in conjunction with the remote sites.
Central Site
In the central site, upgrade the components in the following order:
1. Switches, routers and security components
2. Gatekeepers and voice and data gateways
3. Network management components
4. Contact center routing components
5. Agent management components
6. Agent desktop client software
7. Call processing components
8. Queuing and self-service components
|
Note In a Unified CVP implementation, it is recommended to perform the upgrade of the voice and data gateways in the same maintenance window as Unified CVP.
|
9. Messaging components
Remote Site
For the remote site(s), upgrade the components in the following order:
1. Switches, routers and security components
2. Voice and data gateways
3. Call processing endpoints
4. Agent management components
5. Agent desktop client software
Multisite Distributed Model
In the multisite distributed model, upgrade the components in each cluster site and any small remote sites as listed in the Multisite Centralized Model section.
|
Note Treat the upgrade of each cluster site as a separate stage in the overall system upgrade process.
|
Clustering over the WAN (CoW) Model
In the Clustering over the WAN (CoW) model, upgrade the components in the central sites first where CoW is implemented and then upgrade any remote sites as listed in the Multisite Centralized Model section.
|
Note Upgrade clustered components in the same upgrade period and stage at each of the central sites.
|
Upgrading Components
Once you have reviewed the general upgrade sequence for your specific deployment model, perform your upgrades based on the following upgrade strategies:
•Single-Stage Upgrade—Recommended for small single-site and multisite installations.
•Multistage System Upgrade—Recommended for medium and large single-site and medium multisite installations.
•Multisite Migration—To upgrade large, multisite contact center installations to the Cisco Unified Communications release set using the multisite migration upgrade strategy, you can use either the single-stage or multistage system upgrade procedures listed in this section.
See Chapter 4 "Planning Your System Upgrade" for detailed information about the above upgrade strategies and Chapter 5 "Preparing for Your System Upgrade" for the software release versions of the components involved in the upgrade. For more information about the number of seats in these various types of sites, see Table 4-2 in Chapter 4 "Planning Your System Upgrade".
The upgrade paths available for upgrading contact center components are defined in System Upgrade Paths in Chapter 4 "Planning Your System Upgrade". For components that are new to the target release and that you may want to install, see New Components and Features in Target Release Set in Chapter 4 "Planning Your System Upgrade".
See Table 6-3 in Related Documentation for a list of URLs to component-specific release notes and installation and upgrade documents. When performing the upgrade of each component, see the product-specific upgrade document for the relevant release for detailed information.
|
Note Some of the listed components might not apply to your specific installed base. Therefore, if there is an application, component, or feature listed that you do not already have installed in your environment, you need not upgrade them.
|
Upgrading Contact Center Test Beds
The contact center test sites are set up as three separate test beds:
•Test Bed 1—Cisco Unified Communications Manager Call Flows— Unified IP IVR test bed with Unified Communications Manager Post-Routed call flows. Use normal upgrade procedures based on the single-stage or multistage upgrade approaches discussed in Chapter 4 "Planning Your System Upgrade".
•Test Bed 2—Parent and Child Call Flows—The parent and child model has been deployed in this test bed and calls are routed from parent to child systems and child to child systems.
Upgrade all the parent systems at the data centers before upgrading the child systems at the data centers and remote sites. The child systems have to be compatible with the parent systems that are running the new software versions.
For detailed information about the deployment options and limitations for the Unified Communications Manager Post-Routed and Parent and Child call flows, see the Cisco Unified Contact Center Gateway feature at: http://www.cisco.com/en/US/docs/voice_ip_comm/uc_system/UC7.0.1/cc_system_arch/ch2model.html
•Test Bed 3—Cisco Unified CVP Post-Routed Call Flows—Cisco Unified CVP test bed with Unified CVP Post-Routed call flows. Use normal upgrade procedures based on the single-stage or multistage upgrade approaches discussed in Chapter 4 "Planning Your System Upgrade".
|
Note To verify the interoperability between clusters running different release set versions, some of the Unified Communications Manager clusters in Test Bed 3 have not been upgraded.
|
Single-Stage Upgrade
The single-stage upgrade process is recommended for small single-site and multisite installations and can be performed in a single maintenance window. This enables you to upgrade all the components in a brief period of time with no loss of functionality.
See Chapter 5 "Preparing for Your System Upgrade" for the software release versions of the components involved in the upgrade. Based on your environment and the base release set deployed in your network, upgrade the components in the order listed in Table 6-1.
Table 6-1 Single-Stage Upgrade Order for Contact Center Components
Upgrade Order
|
Components Being Upgraded
|
1
|
Core switch
|
2
|
Access switch
|
3
|
Cisco Catalyst 6500 Series Switch Firewall Services Module
|
4
|
Cisco Adaptive Security Appliance 5540
|
5
|
Cisco Security Agent Management Console
|
6
|
Cisco IOS Gateways (MGCP, H.323 and SIP)1
|
7
|
Cisco Unified CVP VXML Gateways
|
8
|
Cisco Aironet Access Point 1240AG
|
9
|
Cisco IOS-based Transcoders and Conference Bridges
|
10
|
Cisco Gatekeepers
|
11
|
Cisco Unified Operations Manager
|
12
|
Cisco Support Tools Server
|
13
|
Cisco Unified ICME Rogger/Progger
|
14
|
Real Time AW/HDS/Webview
|
15
|
Peripheral Gateway, Unified System Contact Center Gateway (Unified SCCG), Unified Contact Center Gateway Enterprise (Unified CCGE)
|
16
|
CTI OS Server
|
17
|
CAD Server
|
18
|
Cisco Unified Outbound Option
|
19
|
CTI OS Agent/Supervisor Desktop
|
20
|
CAD Agent/Supervisor Desktop
|
21
|
Cisco Unified Presence
|
22
|
Cisco Unified Communications Manager
|
23
|
JTAPI (upgrade if needed on client applications)
|
24
|
Cisco Security Agent and virus scanning software
|
25
|
Unified IP Phones firmware (if needed)
|
26
|
Cisco IP Communicator
|
27
|
Cisco Unified CVP system components
|
28
|
Cisco Unified IP IVR
|
29
|
Cisco Unity Connection
|
Multistage System Upgrade
A multistage system upgrade is the recommended approach for medium and large single-site and medium multisite installations. In this upgrade process, components are grouped together for upgrading in several stages or maintenance windows. Within each maintenance window, there is a recommended order for upgrading each component.
The grouping of the components into the stages may vary depending on the size of the networks being upgraded. For smaller networks, several separate maintenance windows may be collapsed into a single maintenance window. Additional stages may be necessary for larger sites.
After each maintenance window, we recommend that you verify that the operation of all basic and critical call types remains unaffected before you initiate the next upgrade stage listed in the table. See detailed information about the upgrade exit criteria and procedures for verifying component interoperability for each stage in Verifying Multistage System Upgrades. We also recommend that you maintain a list to track the components that have been upgraded and the ones yet to be upgraded.
See Chapter 5 "Preparing for Your System Upgrade" for the software release versions of the components involved in the upgrade. Based on your environment and the base release set deployed in your network, upgrade the components in the stages and in the sequence within each stage as listed in Table 6-2.
Verifying Multistage System Upgrades
Components that are upgraded in each stage must interoperate with components that have been upgraded in a previous stage as well as with components that have yet to be upgraded in subsequent stages to ensure the overall operation of the network.
Therefore it is important to verify this interoperability as well as check that basic call service has not been adversely affected during multistage system upgrade operations. This section provides detailed information about the verification procedures as you exit each system upgrade stage.
Exit Criteria for Multistage System Upgrade Stages
Table 6-3 provides exit criteria you need to execute after completing each system upgrade stage.
Table 6-3 System Upgrade Stages and Exit Criteria Matrix
| |
Multistage System Upgrade Stage
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
Switches and Routers Upgrade Exit Criteria
|
x
|
|
|
|
|
|
|
|
|
Security Components Upgrade Exit Criteria
|
x
|
|
|
|
|
|
|
|
|
Gatekeepers and Voice and Data Gateways Upgrade Exit Criteria
|
x
|
x
|
|
|
|
|
x
|
|
|
Cisco IOS Gatekeeper and Cisco Unified Border Element Gateway Upgrade Exit Criteria
|
|
x
|
|
|
|
|
|
|
|
Cisco Aironet Access Point 1240AG Upgrade Exit Criteria
|
|
x
|
|
|
|
|
|
|
|
Cisco IOS-based Transcoders and Conference Bridges Upgrade Exit Criteria
|
|
x
|
|
|
|
|
x
|
|
|
Network Management Components Upgrade Exit Criteria
|
|
|
x
|
|
|
|
|
|
|
Cisco Unified Intelligent Contact Management Enterprise Support Tools Server Upgrade Exit Criteria
|
|
|
x
|
|
|
|
|
|
|
Cisco Unified Intelligent Contact Management Enterprise Rogger/Progger Upgrade Exit Criteria
|
|
x
|
|
x
|
|
|
|
|
|
Cisco Real Time Administration Workstation, Historical Database Server, WebView Upgrade Exit Criteria
|
|
|
|
x
|
|
|
|
|
|
Peripheral, VRU and MRPG Gateways Upgrade Exit Criteria
|
|
|
|
|
x
|
|
|
|
|
Cisco Unified Contact Center Gateway Enterprise and Cisco Unified System Contact Center Gateway Upgrade Exit Criteria
|
|
|
|
|
x
|
|
|
|
|
Cisco Telephony Integration Object Server and Cisco Agent Desktop Server Upgrade Exit Criteria
|
|
|
|
|
x
|
|
|
|
|
Cisco Unified Outbound Option Upgrade Exit Criteria
|
|
|
|
|
x
|
|
|
|
|
Cisco Telephony Integration Object Server and Cisco Agent Desktop Agent/Desktop Clients Upgrade Exit Criteria
|
|
|
|
|
|
x
|
|
|
|
Cisco Unified Communications Manager Upgrade Exit Criteria
|
x
|
|
|
|
|
|
x
|
|
|
Cisco Unified Presence Upgrade Exit Criteria
|
|
|
|
|
|
|
x
|
|
|
Cisco Security Agent (CSA) Management Console Upgrade Exit Criteria
|
x
|
|
|
|
|
|
|
|
|
Cisco Unified IP Phones Upgrade Exit Criteria
|
|
|
|
|
|
|
x
|
|
|
Cisco IP Communicator Upgrade Exit Criteria
|
|
|
|
|
|
|
x
|
|
|
Cisco Unified CVP Upgrade Exit Criteria
|
|
|
|
|
|
|
|
x
|
|
Cisco Unified IP IVR Upgrade Exit Criteria
|
x
|
x
|
|
|
|
|
|
x
|
|
Cisco Unity Connection Upgrade Exit Criteria
|
x
|
|
|
|
|
|
|
|
x
|
Switches and Routers Upgrade Exit Criteria
After upgrading core routers and switches, verify the following:
1. Check the buffer log or console for error messages.
2. Verify that a dump file was not created in the flash memory.
3. Use the "show running-config" command to verify that the previous configuration was not deleted during the upgrade process.
4. Use the "show ip interface brief" command to verify that the configured interfaces are in up/up state.
5. Verify that the Unified IP Phones connected to the switches are powered up and register correctly with their primary Unified Communications Manager node.
Security Components Upgrade Exit Criteria
After upgrading Cisco Catalyst 6500 Services Switch, Firewall Services Module and Cisco Adaptive Security Appliance, verify the following:
1. In a deployment where Unified Communications Manager servers are separated by a Firewall Services Module/ Adaptive Security Appliance, place a call from a Unified IP Phone that is registered to one Unified Communications Manager to a Unified IP Phone that is registered to another Unified Communications Manager.
2. Verify that the database replication is successful between Unified Communications Manager servers which are separated by a Firewall Services Module/ Adaptive Security Appliance.
Gatekeepers and Voice and Data Gateways Upgrade Exit Criteria
After upgrading IOS gateways, verify the following:
1. At the Cisco IOS exec level, execute the following CLI commands:
–To check that the upgraded IOS target image is running:
show version
–To verify that the boot system is configured to boot the correct image:
show running-config
–To verify that configuration done previously (i.e. H.323/SIP dial-peer and MGCP) is not lost:
show running-config
–To verify that the ISDN connection status is at MULTIFRAME_ESTABLISHED:
show isdn status
–To verify that configured interfaces are in up/up state:
show ip interface brief
–To verify manually placed incoming calls:
show isdn history
–To verify IP routing from branch site to a data center:
ping or traceroute
–To verify IP routing from one branch site to another branch site:
ping or traceroute
–To verify system startup process after software reload:
show logging
2. Ensure that the following devices are configured and registered correctly: Gatekeeper, MGCP and H.323 gateways, trunks, and CTI Route Point.
3. Ensure that all MGCP end points (FXS, FXO, PRI, T1 CAS and BRI) are properly registered with Unified Communications Manager.
4. Manually spot check calls as appropriate:
–IP (SCCP and SIP) <-> PSTN via MGCP Gateway.
–IP (SCCP and SIP) <-> PSTN via SIP Gateway.
–IP (SCCP and SIP) <-> PSTN via H.323 Gateway.
5. Verify that a PSTN user who places an inbound call from the PSTN to a Unified IP Phone in a Unified Communications Manager cluster through gateways such as MGCP, SIP, and H.323 and puts the call on hold can hear Music-on-Hold (MOH) and can also finally resume the call.
Cisco IOS Gatekeeper and Cisco Unified Border Element Upgrade Exit Criteria
After upgrading the Cisco IOS gatekeeper and the Cisco Unified Border Element Gateway, verify the following:
1. To verify the running IVS version of IOS image (for example: Cisco IOS software, 3800 software (C3845-IPVOICE_IVS-M), type the following command:
show version
2. To check that the configuration is not lost, use the following command:
show running-config
3. Verify that all H.323 end points that are configured to register with the gatekeeper and gateway register properly.
4. Verify that Unified Communications Manager registers with the gatekeeper and gateway.
5. Make a call between two end points that uses the gatekeeper and gateway; verify that the call is successful and proper bandwidth is reduced in the gatekeeper for that call.
Cisco Aironet Access Point Upgrade Exit Criteria
After upgrading Cisco Aironet Access Point 1240AG, verify the following:
1. Verify that Unified IP Phones 7920 and 7921 register with Cisco Unified Communications Manager; and stay registered after the upgrade.
2. Make a call from IP Unified Phone 7920 and Unified IP Phone 7921 to another Unified IP Phone and ensure audio is available in both directions.
3. When the call is active, verify audio is available in both directions when Unified IP Phone 7920/21 phones roam between access points.
4. Verify if Unified IP Phone 7920/21 phones can register with different types of encryption.
Cisco IOS-based Transcoders and Conference Bridges Upgrade Exit Criteria
After upgrading Cisco IOS-based transcoders and conference bridges, verify the following:
1. Check if the complete configuration before the upgrade still exists.
2. Check if all DSPs are registered and are functioning normally.
3. Check if there are no error messages in the buffer log or console.
4. Check if no dump file is created in the flash memory.
5. To verify that the configuration is not lost, type the "show running-config" command.
6. To verify that the interfaces are in up state, type the "show ip interface brief" command.
7. To verify the system startup process, type the "show logging" command after reload.
8. Make an inbound call to a Unified IP Phone through a gateway (MGCP, SIP, H.323) and conference the call with another Unified IP Phone, using a conference bridge in the gateway.
Network Management Components Upgrade Exit Criteria
After upgrading network management components, verify the following:
1. Verify the software version and the build ID using CiscoWorks to ensure that the upgrade was successful.
2. Ensure that access to the Unified Operations Manager console is still available.
3. Ensure that access to all devices managed by Unified Operations Manager is still available.
Cisco Unified Intelligent Contact Management Enterprise Support Tools Server Upgrade Exit Criteria
After upgrading the Unified ICME Support Tools Server, verify the following:
1. Verify that the complete configuration prior to the upgrade still exists on the Unified ICME Support Tools server.
2. Ensure that access to the Unified ICME Support Tools server console is still available.
3. Ensure that access to all the devices managed by the Unified ICME Support Tools server is still available.
Cisco Unified Intelligent Contact Management Enterprise Rogger/Progger Upgrade Exit Criteria
After upgrading the Unified ICME Support Tools Server, verify the following:
1. Ensure that basic calls and call functionality such as transfers, conferences, call treatment and queuing by Unified IP IVR, etc. are working properly.
2. Verify that all previously registered endpoint devices have re-registered correctly.
3. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
4. After Side A Central Controller components have been upgraded, verify basic operations such as the following:
–Setup logs indicate no errors or failure conditions.
–All components can "ping" public and private IP addresses as applicable.
–Schema upgrade is successful for all databases and there is no loss of data integrity or data.
–Registry changes are correct and match the information in the setup logs.
–All component services start correctly without generating errors.
–All general activities such as ability to access SQL server and to run third-party software components like VNC or PCAnywhere, etc. are not stopped by Cisco Security Agent.
–"Ccagent" is in service and connected to any Peripheral Gateways located in Side A.
–Recovery process not required, no activity other than process start up.
–Configuration information is passed to the router by the logger. Replication process begins when the Historical Database Server comes online.
–Replication process begins with no errors.
–Database space allocation and % used are reported correctly.
–Unified ICME Support Tools server can acquire logs, capture registry information, and schedule collection of logs.
Cisco Real Time Administration Workstation, Historical Database Server, WebView Upgrade Exit Criteria
After upgrading the Real Time AW/HDS/Webview software, verify the following:
1. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
2. After Side A Central Controller components have been upgraded, verify basic operations such as the following:
–Setup logs indicate no errors or failure conditions.
–All components can "ping" public and private IP addresses as applicable.
–Schema upgrade is successful for all databases and there is no loss of data integrity or data.
–Registry changes are correct and match the information in the setup logs.
–All component services start correctly without generating errors.
–All general activities such as the ability to access SQL server and to run third-party software components like VNC or PCAnywhere, etc. are not stopped by Cisco Security Agent.
–"Rtsvr" is connected to the primary Administrative Workstation.
–Configuration information is passed to the router by the logger. Replication process begins when the Historical Database Server comes online.
–Real Time Administrative Workstation indicates that it is ready.
–Replication process begins with no errors.
–Authorized users are able to use the Configuration Manager on the Real Time Administrative Workstation
–Authorized users are able to log into WebView and can access both public and private reports and that all previously existing reports are still available.
–Previous settings for users are still valid when any application is opened.
–The "Validate All" script yields the same results after the upgrade as prior to the upgrade.
–All existing scripts can be opened, edited, or deleted and new scripts can be created.
–Database space allocation and % used are reported correctly.
–Unified ICME Support Tools server can acquire logs, capture registry information, and schedule collection of logs.
–Verify that configuration changes are possible.
Peripheral, VRU and MRPG Gateways Upgrade Exit Criteria
After upgrading the Peripheral, VRU and MRPG gateways, verify the following:
1. Ensure that basic calls and call functionality (such as transfers, conferences, call treatment and queuing by Unified IP IVR, etc.) are working properly.
2. Ensure that the peripheral is running properly on the upgraded gateway by verifying call flows, CTI desktops and other applications, Unified Outbound Option, etc.
3. Verify that all previously registered endpoint devices have re-registered correctly.
4. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
Cisco Unified Contact Center Gateway Enterprise and Cisco Unified System Contact Center Gateway Upgrade Exit Criteria
After upgrading the Unified CCGE and Unified SCCG, verify the following:
1. Ensure that basic calls and call functionality (such as transfers, conferences, call treatment and queuing by Unified IP IVR, etc.) are working properly.
2. Ensure that the peripheral is running properly on the upgraded gateway by verifying call flows, CTI desktops and other applications, Unified Outbound Option, etc.
3. Verify that all previously registered endpoint devices have re-registered correctly.
4. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
Cisco Telephony Integration Object Server and Cisco Agent Desktop Server Upgrade Exit Criteria
After upgrading the CTI OS and CAD Servers, verify the following:
1. Ensure that basic calls and call functionality (such as transfers, conferences, call treatment and queuing by Unified IP IVR, etc.) are working properly.
2. Verify that all previously registered endpoint devices have re-registered correctly.
3. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
Cisco Unified Outbound Option Upgrade Exit Criteria
After upgrading the Unified Outbound Option, verify the following:
1. Ensure that basic calls and call functionality (such as transfers, conferences, call treatment and queuing by Unified IP IVR, etc.) are working properly.
2. Verify that all previously registered endpoint devices have re-registered correctly.
3. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
Cisco Telephony Integration Object Server and Cisco Agent Desktop Agent/Desktop Clients Upgrade Exit Criteria
After upgrading the CTI OS and CAD agent client software, verify the following:
1. Ensure that basic calls and call functionality (such as transfers, conferences, call treatment and queuing by Unified IP IVR, etc.) are working properly.
2. Verify that all previously registered endpoint devices have re-registered correctly.
3. Check that no exceptions, errors, or unexpected events have occurred or found in the log buffer.
4. Check that agents are still able to log in and answer calls.
Cisco Unified Communications Manager Upgrade Exit Criteria
After upgrading Unified Communications Manager, verify the following:
1. Verify that no error messages have occurred during the upgrade process.
2. Check the upgrade log file for any errors.
3. Start all first node and subsequent node servers.
4. Verify that there is no replication failure between the first node and subsequent node servers.
5. Verify that SIP and SCCP IP Phones are registered with Cisco Unified Communications Manager.
6. Ensure that the following devices are configured correctly: gatekeeper, MGCP, H.323 gateways, trunks, and CTI route points.
7. Ensure that the media resources (conference bridges, MTP and transcoders) are configured correctly by checking their status.
8. Verify if the end users are able to connect to their CTI managers.
9. Check if the license usage is correct as reported in the License Unit Report.
10. Check if services on all servers in the cluster are up.
11. Perform the Cisco Unified Communications Manager first node and subsequent node process verification using the following Real Time Monitoring Tool feature verification process:
a. Verify if Multiple Route Patterns and Route Lists are configured and working properly.
b. Verify if Extension Mobility is configured and working properly.
c. Verify if Unified IP Phone Services are configured and working properly.
12. Ensure that all MGCP end points (FXS, FXO, PRI, T1 CAS and BRI) are properly registered with Unified Communications Manager.
13. Manually spot check calls as appropriate:
–IP (SCCP and SIP) <-> PSTN via MGCP Gateway
–IP (SCCP and SIP) <-> PSTN via SIP Gateway
–IP (SCCP and SIP) <-> PSTN via H.323 Gateway
14. Verify that a PSTN user who places an inbound call from the PSTN to a Unified IP Phone in a Unified Communications Manager cluster through gateways such as MGCP, SIP, and H.323 and puts the call on hold can hear Music-on-Hold (MOH) and can also finally resume the call.
Cisco Unified Presence Upgrade Exit Criteria
After upgrading Unified Presence, verify the following:
1. Verify that no error messages have occurred during the upgrade process.
2. Check the upgrade log file for any errors.
3. Verify the Static Route configuration.
4. Check if the license usage is correct as reported in the License Unit Report. Using the Real Time Monitoring Tool, check if the CPU usage is consistent over 5 minutes without any spikes.
Cisco Security Agent Management Console Upgrade Exit Criteria
After upgrading Cisco Security Agent (CSA) Management Console, verify the following:
1. Ensure that basic functionality of call flows that previously worked before the upgrade work the same and operate normally.
2. Check if the previous configuration still exists after the upgrade.
3. Check if access to the console is still available.
4. Check if all managed devices are visible.
Cisco Unified IP Phones Upgrade Exit Criteria
After upgrading Cisco Unified IP Phones, verify the following:
1. Verify that the phones are upgraded to the target firmware images as indicated in the Unified Communications Manager.
2. Verify access to the Corporate Directories in the Unified IP Phones.
3. Verify that Unified IP Phone services such as Fast Dial, Extension Mobility, etc. are working properly.
Cisco IP Communicator Upgrade Exit Criteria
After upgrading Cisco IP Communicator, verify the following:
1. After rebooting the PC, launch IP Communicator and verify that it registers correctly with Unified Communications Manager.
2. Place a call to IP Communicator and verify that audio works properly in both directions.
3. Place outbound, inbound, and PSTN calls from the IP Communicator and verify that the audio works properly in both directions.
4. Verify that additional call functionality such as hold, transfers, conferences, etc. work correctly.
5. Verify access to the Corporate Directories in the Unified IP Phones.
6. Verify that Unified IP Phone services such as Fast Dial, Extension Mobility, etc. are working properly.
Cisco Unified Customer Voice Portal Upgrade Exit Criteria
After upgrading Unified CVP, verify the following:
1. Verify that error messages did not display during the upgrade process.
2. Check the upgrade logs for error messages.
3. Ensure that the Unified CVP Operations, Administration, Monitoring and Provisioning (OAMP) Web interface is available for use.
4. Use the diagnostic page at http://<CVPHOST>:8000/cvp/diag to verify the status of the Unified CVP system.
5. Ensure that the Unified CVP Voice Browser is registered with the H.323 gatekeeper.
6. Check that the H.323 gatekeeper for Unified CVP Server is registered as an H.323 endpoint.
7. Verify that the appropriate voice prompt is heard when the call is made.
8. Ensure that the Unified CVP license is properly installed.
Cisco Unified IP IVR Upgrade Exit Criteria
After upgrading Unified IP IVR, verify the following:
1. Verify that no error messages have occurred during the upgrade process.
2. Check the upgrade log file for any errors.Verify if all required services are operational after the upgrade.
3. Verify if JTAPI is upgraded to the proper version and it is properly connected and synchronized to Unified Communications Manager.
4. Check if all CTI Ports are registered with Unified Communications Manager.
5. Check if all CTI Route Points are registered with Unified Communications Manager.
6. Check if a prompt is heard when a call is made.
7. Perform Telephony Synchronization and ensure that it is successful.
8. If you are using a CAD desktop, ensure that the desktop auto upgrades to the version bundled with Unified IP IVR.
9. Log in to IP Phone Agent, CAD Agent and CRSADMIN, and ensure that all the logins are successful.
10. Make an inbound call and ensure that the call is presented to Ready Agent.
11. If it is dual node, ensure one node is the Master while other node is in Slave state.
Cisco Unity Connection Upgrade Exit Criteria
After upgrading Unity Connection, verify the following:
1. Check the Cisco Unity Connection software version from the Command Line Interface (CLI) using the "show cuc" command
2. Check the software version on the active partition from the Cisco Unified OS Administration web page.
3. Check the status of the services either from the Serviceability page or through the CLI.
4. Check the status of voicemail ports in Unified Communications Manager.
5. Run the "Test Port" command from the Port page under Telephony Integrations.
6. Prior to the upgrade, activate the Message Waiting Indicator (MWI) by leaving a voicemail for a caller. After the upgrade, refresh the MWI status And verify that the MWI is still on.
7. Create a couple of subscribers and verify that supervised transfers and the MWI functionality work properly.
8. If authentication and encryption have been enabled for the ports, place a call from an endpoint that supports encryption into Unity Connection and verify that the RTP is encrypted.
9. If authentication and encryption have been enabled for the ports, place a call from an endpoint that supports authentication into Unity Connection and verify that the signaling is secure.
Related Documentation
The following sections list compatibility guides and installation documentation for Cisco Unified Communications System components:
•Compatibility Guides
•Component Release Notes and Installation and Upgrade Documents
For information about support for legacy products and third-party product interoperability with Cisco Unified Communications contact center products, see the Cisco Interoperability Portal at:
www.cisco.com/go/interoperability
Compatibility Guides
For compatibility and interoperability information about Unified Communications Manager, Unified Contact Center Enterprise, Unified IP IVR and other Cisco Unified Communications contact center products, see the following sites:
•Cisco Unified Communications Compatibility Tool:
http://tools.cisco.com/ITDIT/vtgsca
•Cisco Unified Communications Manager (CallManager) Compatibility Information: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
•Hardware and Software Compatibility Information for Cisco Unified Presence Release 7.0(1): http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
•Cisco Unified Contact Center Enterprise (Unified CCE) Software Compatibility Guide: http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/compatibilty_matrix/guide/ipcc75compat.pdf
•Hardware and System Software Specification (Bill of Materials), Cisco Unified Intelligent Contact Management & Cisco Unified Contact Center Enterprise & Hosted Editions: http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/user/guide/icm75bom.pdf
•Cisco Response Solutions (CRS) Software and Hardware Compatibility Guide:
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf
•Hardware and System Software Specification for Cisco Unified Customer Voice Portal (Unified CVP), Release 7.0(1), 7.0(2) at http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/customer_voice_portal/cvp7_0/reference/guide/cvp702bom.pdf
•Cisco Computer Telephony Integration Option: CTI Compatibility Matrix:
http://www.cisco.com/en/US/products/sw/custcosw/ps14/prod_technical_reference_list.html
•Cisco 7800 Series Media Convergence Servers: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html
•Cisco Unified Communications Manager Server Support Matrix at: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure0900aecd8062a4f9.html
•Cisco Unity Connection Supported Platforms List at: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps6509/product_data_sheet0900aecd80372879.html
•Cisco Unified Communications System Release Summary Matrix for Contact Center at: http://www.cisco.com/en/US/docs/voice_ip_comm/uc_system/unified/communications/system/versions/CCMtrix.html
•IP Communications System Test Release at: http://www.cisco.com/en/US/docs/voice_ip_comm/uc_system/GB_resources/ipcmtrix.htm
Component Release Notes and Installation and Upgrade Documents
Table 6-4 provides a listing of contact center components and URLs for related component release notes and installation and upgrade documents. These URLs link to webpages that list various release versions of these documents. Review the appropriate documents based on the release versions of the components in your base and target release sets.
