Collaboration Migration Plan The Network Guys, Inc



Download 118.19 Kb.
Date conversion09.06.2018
Size118.19 Kb.
XXXXXXXXXXX: Collaboration Migration Plan

The Network Guys, Inc.



Created on OCT 27,2014

Summary


This document serves as a resource for those individuals involved in the planning and execution of the migration for the CUCM, Unity, UCCX, and CIMP upgrades on virtualized Cisco UCS platforms. This document will also address the migration steps necessary for voice gateway, as well as any third party integrations.

High Level Plan


  1. 1. Pre-Upgrade Tasks

1.1. Disable VM Auto Start Feature

1.2. Disable VM LRO Settings

1.3. Stage Upgrade Files


  1. Phase One

    1. Install ATA 190 for faxing (TBD)

    2. Upgrade Voice Gateway IOS

    3. Upgrade CIMC and BIOs

    4. Upgrade ESXi

    5. Upgrade Voice Gateway IOS





  1. Phase Two

    1. Upgrade UCCX to 9.0(2)

    2. CUC 10.5(1) Upgrade

    3. CUCM 10.5(1) Upgrade

    4. Instant Messaging and Presence Upgrade

    5. Upgrade UCCX to 10.5(1)SU1

    6. Upgrade Agent Desktops

    7. Upgrade Jabber Clients

    8. Upgrade Agent Desktops

    9. User Acceptance Testing

    10. IPT Test Plan

    11. Customer Sign Off

  2. First Day of Service

  3. VCSC and VCSE upgrade to X8.2 (TBD)

Detailed Migration Tasks


The migration tasks identify current environment variables as well as lays the foundation for where the migration is going and how it will get there. The following topics are not in execution order, which allows the implementer the flexibility to arrange work tasks to suit the needs of the client.

Prime License Manager (PLM)


PLM is the new centralized licensing management software, co-resident with the CUCM Publisher server (no separate VM required) and hosts the licenses for CUCM, IM&P*, CUC and CER.

*IM&P s technically licensed as a part of CUCM, but is called out here for completeness.


Device Owner User ID Associations


To ensure the proper number of licenses are migrated based on currently installed licensing and current device usage, we will need to associate the Owner User ID to each device which belongs to an individual.

Migration Support


The Global Licensing Operations (GLO) Team is available 24 x 7 x 365 and has knowledgeable agents that can help.

Process your request and route it to the team best able to assist you. Expect a response within 48-72 hours.

Remember: Product licensing has a grace period from the time that users are configured on the system. For Unified CM and Unity Connection, the grace period is 60 days.

To obtain migration support, select one of the following options:



  • Open your service request through the web: https:/​/​tools.cisco.com/​ServiceRequestTool/​scm/​mgmt/​case

  • Open any service request through licensing@cisco.com (include Cisco.com user ID)

  • Open a service request by telephone using country-specific numbers: http:/​/​www.cisco.com/​en/​US/​support/​tsd_​cisco_​worldwide_​contacts.html

Resources


  • PLM 10.5 User Guide
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/plm/10_5_1/userguide/CPLM_BK_UD1156AD_00_user-guide-rel-1051.html


Voice Gateways

Voice gateways convert from one voice network to a different voice network. The bridge the gap between different networks, or similar networks with different operating parameters. The most common gateways connect your voice network to the PSTN, and connect your VoIP network with your legacy analog devices.

PSTN Voice Gateways

The PSTN voice gateway has one or more connections (aka circuits or lines) to a telephone company (aka telco), and connects to your VoIP network.



Name

Platform

Source Version

Target Version

Migration Method

SPC-PSTNGW01

2921

15.2(4)M1

15.3(3)M3

Upgrade IOS via FTP
















Upgrade Tasks

1. Upload IOS Image via FTP

2. Configure Boot Command

3. Reboot

4. Validate
Validation Tasks

1. Confirm Software Version

2. Place One or More Calls Through Gateway

Resources


  • CUCM 10.5(1) IOS Compatibility with 2900 Series Routers
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/unified/communications/system/versions/IPTMtrix.html#pgfId-1166008


  • Cisco IOS 15.3(3)M Features and Important Notes
    http://www.cisco.com/c/en/us/td/docs/ios/15_3m_and_t/release/notes/15_3m_and_t/153-3MNEWF.html



  • Cisco IOS Software Search
    http://tools.cisco.com/ITDIT/CFN/jsp/SearchBySoftware.jsp



  • Release notes

http://www.cisco.com/c/en/us/td/docs/ios/15_3m_and_t/release/notes/15_3m_and_t.html

Cisco Unified Compute System (UCS) Hardware


The high level details of the hardware migration are as follows:

Name

Platform

Source Version

Target Version

Migration Method

ESXI01.mnscha.local

Cisco UCS C220 m3sbe

1.4(6c)

ESXi 5.0.0



2.0(1a)

ESXi 5.5.0-1746018-

Custom-Cisco-5.5.1.3


Upgrade via HUU


ESXI02.mnscha.local

Cisco UCS C220 m3sbe

1.4(6c)

ESXi 5.0.0



2.0(1a)

ESXi 5.5.0-1746018-

Custom-Cisco-5.5.1.3


Upgrade via HUU


Upgrade Tasks per Server

  1. Disable VM Auto Start Feature

  2. Disable VM LRO Settings

  3. Shutdown all Virtual Machines (VM)

  4. Mount HUU ISO via CIMC KVM

  5. Unmount HUU ISO Disconnect/Connect the Power Supplies Units (PSU

  6. Patch CIMC for Shellshock Vulnerability (disable SSH)

  7. Mount ESXi ISO via CIMC KVM

  8. Boot into ESXi Installer

  9. Upgrade ESXi

  10. Unmount ESXi ISO

  11. Patch ESXi for Heartbleed Vulnerability

  12. Enable VM Auto Start Feature

  13. Validate


Validation Tasks

1. Confirm Software Version

2. Login and Access User Interface
CIMC Shellshock Patch Tasks

1. Disable CIMC SSH Feature


ESXi Heartbleed Patch Tasks

1. Upload Patch to DataStore

2. Enable Local Tech Support Mode

3. Install Patch

4. Generate New Certificates

5. Reboot


BE6K

http://docwiki.cisco.com/wiki/Cisco_Business_Edition_6000

http://docwiki.cisco.com/wiki/Supported_System_Capacities

http://docwiki.cisco.com/wiki/Implementing_Cisco_Business_Edition_6000

ESXi 5.5x Upgrade guides

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/BE6000/hypervisor/CUCM_BK_BBE47946_00_be6000-hypervisor-upgrade.html


http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-FE668788-1F32-4CB2-845C-5547DD59EB48.html
http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.upgrade.doc/GUID-77D42D81-F47E-4FE9-B4B2-B15AB16C9C1A.html#GUID-77D42D81-F47E-4FE9-B4B2-B15AB16C9C1A
ESXi Requirements

http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#VMware_vSphere_ESXi_Version_Support_for_Call_Processing_and_System_Management_Applications

http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#ESXi_Major.2FMinor_Versions.2C_Maintenance.C2.A0Versions_and_Patches.2FUpdates

ESXi 5.5U1 Release notes

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/OL_26617.html#17032
ESXi Heartbleed Vulnerability http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2076665 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008939

 CIMC Shellshock Vulnerability

https://tools.cisco.com/bugsearch/bug/CSCur03816
Cisco Bash Code injection Vulnerability Patch

http://www.cisco.com/web/software/282204704/18582/CiscoBashCodeInjectionVulnerabilityPatchv2.pdf


CUCM 10.x

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unified_Communications_Manager_(CUCM)

CUC 10.x

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unity_Connection

http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#ESXi_Major.2FMinor_Versions.2C_Maintenance.C2.A0Versions_and_Patches.2FUpdates

UCCX 10.5x

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unified_Contact_Center_Express

VCSc/e X8.1-X8.2

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_TelePresence_Video_Communications_Server

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-2/Cisco-VCS-Basic-Configuration-Control-with-Expressway-Deployment-Guide-X8-2.pdf


Endpoints


The high level details of the migration of the endpoints are as follows:

Device

Protocol

#

Source Software

Target Software

Migration Method



























































































Cisco 7940

SCCP

12

P00308010200

P0030801SR02

Post-upgrade

Cisco 7941

SCCP

106

SCCP41.9-3-1SR2-1S

SCCP41.9-3-1SR4-1S

SCCP41.9-4-2-1S



Post-upgrade

FDOS-bug fix



Cisco 7960

SCCP

1

P00308010200

P0030801SR02

Post-upgrade

Cisco 7961

SCCP

22

SCCP41.9-3-1SR2-1S

SCCP41.9-3-1SR4-1S

SCCP41.9-4-2-1S



Post-upgrade

FDOS bug fix







































cmterm-devicepack10.5.1.11010-1.cop.sgn MD5 = 600e9adae15f5bc7a175f8d6d93ce123

Upon registration to the new 10.5(1) system, all endpoints will change firmware versions and register without issue.


Resources


  • CUCM 10.5 Device Compatibility
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/unified/communications/system/versions/IPTMtrix.html#pgfId-1164438


  • Cisco IP Phone 7937 have not been validated on CUCM 10.5(1); however CUCM 10.5(1) does ship with the above stated target software for these phones.
    Source: PDI Help Desk ref:_00D30QUu._50080YNqFn:ref



  • Cisco IP Phone ATA186 Firmware Readme

http://www.cisco.com/web/software/282074215/25561/cmterm-ata-sccp.3-2-4-Readme.html

  • Cisco ATA186 Is not compatible with CUCM 10.0(1) and later

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/matrix/10_x/CUCM_BK_CD1DB914_00_compat_matrix/CUCM_BK_CD1DB914_00_compat_matrix_chapter_010.html#CUCM_RF_C0D1197F_00


  • Cisco IP Phone 7937 Firmware Readme
    http://www.cisco.com/web/software/282074289/52353/7937_1.4.4_ReadMe.txt


  • Cisco IP Phone 7940/7960 Firmware Readme
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7960g_7940g/firmware/8_1_2/english/release/notes/796040_812_sr1.html


  • Cisco IP Phone 7941/7961/7970 Firmware Readme
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/7900_series/firmware/9_3_1SR4/english/release_notes/P790_BK_RF3660D6_00_rn-9_3_1sr4-7900-series.html




Analog Voice Gateways


There are no analog voice gateways in the network at this time.

Hostname

Model

Source Version

Target Version

Upgrade Method














































Cisco Unified Contact Center Express (UCCX)


UCCX is primarily  offers sophisticated call routing and comprehensive contact management capabilities. It includes an embedded reporting solution that offers a comprehensive view of contact center statistics.

For a performance boost, you will want to disable disk IO throttling prior to the upgrade, and then re-enable it post upgrade.

utils iothrottle status

utils iothrottle disable

utils iothrottle enable
The high level details of the migration of this application are as follows:

Source Version

Target Version

Migration Method

9.0.2.10000-71 Version 9.0(2)

10.5.(1)SU1 Ver10.5.1.11001-49

Two Step upgrade

This will be a two step process. We will upgrade to version 9.0(2)SU2 using Cisco’s osadministration web interface , verify inactive version, switch versions

We will then upgrade to version 10.5(1)SU1 using Cisco’s osadministration web interface , verify inactive version, modify ESXI host, and switch versions, and apply Bash Environment patch if needed (see CSCur02861). We will confirm this by running 'show packages active bash' before and after the patch.

Agents will upgrade their version of clients on the next login.

Upgrade Tasks

1. Stage Upgrade Files

2. Disable IO Throttling

3. Mount 9.0(2)SU2 Upgrade File

4. Upgrade to 9.0(2)SU2 and Do Not Switch Version

5. Switch Version

6. Install Refresh Upgrade COP File

7. Shutdown

8. Modify VM Settings: Operating System and RAM

9. Power On

10. Mount 10.5(1)SU1 Upgrade File

11. Upgrade to 10.5(1)SU1 and Do Not Switch Version

12. Switch Vesion

13. Unmount Upgrade File

14. Enable IO Throttling

15. Validate


Validation Tasks

1. Confirm Software Version

2. Check Real Time Monitoring Tool (RTMT) For System Status

3. Check UCCX Datastore Status

4. Place One or More Calls Through System

5. Login One or More Agents


Shellshock Patch Tasks

1. Install Shellshock COP File


Resources


http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/release/docs/UCCX_BK_U06B1057_00_unified-ccx-documentation-guide.html

  • UCCX Software Compatibility guide

http://docwiki.cisco.com/wiki/Unified_CCX_Software_Compatibility_Matrix_for_10.5(1)_SU1

  • UCCX 10.5(1) release notes

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/release/docs/UCCX_BK_UBDB029E_00_uccx-release-notes-105.html

  • ESXI host modification post upgrade

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unified_Contact_Center_Express#Steps_to_increase_RAM_after_upgrade_.28L2_and_RU.29_in_10.0.281.29

  • UCCX installation and Upgrade guide

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_10_5/install/guide/UCCX_BK_C2650101_00_cisco-unified-contact-center-express.html




Cisco Unified Communications Manager (CUCM)


CUCM is the central component of the phone system, and as such connections to all other voice components are made through this device.

The high level details of the migration of this application are as follows:



Source Version

Target Version

Migration Method

9.1(1a) Build 9.1.1.20000-5

10.5.1 Build 10.5.1.10000-7

Direct Upgrade:
10.0(1)SU2, 10.0(1)SU1, 10.0(1), 9.1(2)SU2a, 9.1(2)SU2, 9.1(2)SU1, 9.1(2), 9.1(1a)


Upgrading to 10.5(1)


Upgrading to 10.5(1) starts with downloading the ISO file from cisco.com, and then hosting it on an FTP server for CUCM to download locally. The Publisher node is upgraded first, then rebooted in to the new version, followed by upgrading the Subscriber node second and rebooted in to the new version.

After the upgrade to CUCM, the endpoints should not change nor require a change, nor shall Unity or CER. Though, a test plan should be executed to validate the upgrade.



Upgrade Tasks

1. Stage Upgrade Files

2. On Publisher

a. Disable LDAP Sync and Extension Mobility

b. Disable IO Throttling

c. Install RSA-3 Keys COP File

d. Shutdown

e. Modify VM Settings: Operating System

f. Power On

g. Mount Upgrade File

h. Upgrade and Automatic Switch Version

i. Unmount Upgrade File

j. Patch for Shellshock Vulnerability

k. Enable LDAP Sync and Extension Mobility

l. enable IO Throttling

m. Validate


2. On Subscriber

a. Disable LDAP Sync and Extension Mobility

b. Disable IO Throttling

c. Install RSA-3 Keys COP File

d. Shutdown

e. Modify VM Settings: Operating System

f. Power On

g. Mount Upgrade File

h. Upgrade and Automatic Switch Version

i. Unmount Upgrade File

j. Patch for Shellshock Vulnerability

k. Enable LDAP Sync and Extension Mobility

l. enable IO Throttling

m. Validate


Validation Tasks

1. Confirm Software Version

2. Check Real Time Monitoring Tool (RTMT) For System Status

3. Place One or More Calls Through System


Shellshock Patch Tasks

1. Install Shellshock COP File


BASH


http://www.cisco.com/web/software/282204704/18582/CiscoBashCodeInjectionVulnerabilityPatchv2.pdf

  • ESXI host modification post upgrade



Cisco Unity Connection (CUC) and Unity


CUC is primarily the voice messaging platform for the phone system. Responsible for greeting callers, taking messages and delivering the messages, as well as notifications to end users.

The high level details of the migration of this application are as follows:



Source Version

Target Version

Migration Method

9.1.1.20000-32

10.5(1) Build 10.5.1.10000-7

Direct Upgrade

Upgrade Tasks

1. Stage Upgrade Files

2. On Publisher

a. Disable LDAP Sync and Extension Mobility

2. Disable IO Throttling

d. Install RSA-3 Keys COP File

e. Shutdown

f. Modify VM Settings: Operating System

g. Power On

h. Mount Upgrade File

i. Upgrade and Automatic Switch Version

j. Unmount Upgrade File

a. Patch for Shellshock Vulnerability

c. Enable LDAP Sync and Extension Mobility

e. enable IO Throttling

d. Validate



Validation Tasks

1. Confirm Software Version

2. Check Real Time Monitoring Tool (RTMT) For System Status

3. Place One or More Calls Through System


Shellshock Patch Tasks

1. Install Shellshock COP File


Resources


  • Documentation Guide CUC 10.x

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/roadmap/10xcucdg.html

  • CUC 10.5(1) Release Notes
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/release/notes/10_5_1cucrn.html



  • Upgrade Guide for CUC 10.x

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrugx/10xcucrug010.html

  • ESXI host modification post upgrade





  • COBRAS Documentation
    http://ciscounitytools.com/Applications/General/COBRAS/COBRAS.html


Cisco IM and Presence (CIMP)


Source Version

Target Version

Migration Method

9.1.1.10000-8

10.5(1) Build 10.5.1.10000-9

Refresh Upgrade to Target

Upgrade Tasks

3. On Publisher

1. Stage Upgrade Files

2. Install RSA-3 Keys COP File

3. Disable IO Throttling

4. Shutdown

5. Modify VM Settings: Operating System

6. Power On

7. Mount Upgrade File

8. Upgrade and Automatic Switch Version

9. Unmount Upgrade File

10 Enable IO Throttling

11. Patch for Shellshock Vulnerability

12. Validate



Validation Tasks

1. Confirm Software Version

2. Login two or more Jabber Clients and Test Functionality
Shellshock Patch Tasks

1. Install Shellshock COP File


Prime License Manager (PLM)

  • PLM is the new centralized licensing management software, co-resident with the CUCM Publisher server (no separate VM required) and hosts the licenses for CUCM, IM&P*, CUC and CER.

  • *IM&P s technically licensed as a part of CUCM, but is called out here for completeness.

  • UCCX will be licensed individually as it is today. Voice gateways are not licensed. Clients are licensed via the server they connect to.



  • Upgrade Tasks

  • 1. CUCM

1. Add to Inventory

2. Upload LCU Report

3. Email Licensing Support

4. Receive and Install Licenses



  • 2. CUC

1. Add to Inventory

2. Migrate Licenses

3. Email Licensing Support

4. Receive and Install Licenses

4. UCCX

N/A



Important Notes

  • Uninstalled PAKs

  • Unused PAKs need to be installed on respective applications before upgrade to PLM.

  • Setting Manual MAC Addresses

  • Cisco recommends converting dynamically created MAC Addresses for licensed servers to statically defined MAC Addresses.

  • Removing PLM from CoRes Servers

  • “In a coresident deployment, you have the option to remove Cisco Prime License Manager if it is not being used. For example, in a Cisco Unified Communications Manager cluster, Cisco Prime License Manager is installed on publisher nodes and subscriber nodes. Since the Cisco Prime License Manager only needs to be active on a single node to manage the licensing of all nodes, you may choose to remove Cisco Prime License Manager from the nodes where it is inactive.”

  • Source: PLM User Guide

  • To conserve system resources we will remove PLM from the CUCM Subscriber, CUC Publisher, and CUC Subscriber after the upgrade.

  • Device Owner User ID Associations

  • To ensure the proper number of licenses are migrated based on currently installed licensing and current device usage, we will need to associate the Owner User ID to each device which belongs to an individual.

  • License Upgrade Support

  • The Global Licensing Operations (GLO) Team is available 24 x 7 x 365 and has knowledgeable agents that can help.

  • Process your request and route it to the team best able to assist you. Expect a response within 48-72 hours.


Cisco TelePresence Video Communication Server (VCSC)


VCSC controls session management and control of telepresence conferences.

The high level details of the migration of this application are as follows:



Source Version

Target Version

Migration Method

X7.2.1

X8.2.2

N/A (separate upgrade project)










VCSC release notes:

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/release_note/Cisco-VCS-Release-Note-X8-2-2.pdf

*Note that when upgrading to a new major release, for example from X7.n to X8.n you need to supply a valid release key as a part of the upgrade process.

Cisco Emergency Responder (CER) N/A


Source Version

Target Version

Migration Method











Resources


  • CER 10.0 Administration Guide (Covers Installation and Administration)
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/10_0_1/english/administration/guide/CER0_BK_CA66317A_00_cisco-emergency-responder-administration-10_0.html

Cisco Unified Attendant Console (UAC) N/A

Resources


  • UAC Standard Installation Files
    \Google Drive\Applications\Cisco\CUACS\CUACS_SV_10.5.1.1543



  • UAC Standard Server-less 10.5 Release Notes
    http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucmac/cuacs/10_5_1/release_notes/CUACS10511543RN.pdf


  • UAC Standard Installation and Configuration Guide
    http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucmac/cuacs/10_5_1/install_admin_guide/CUACS1051GUIDE.pdf


  • UAC Standard Server-less Video Training
    https://www.youtube.com/channel/UC-m-KJ4Apcqa5td3QMc2oHg


  • UAC Support Page (Hosted by Arc)
    http://www.cisco.com/go/ac


Third Party Application Integrations


In some cases, the phone system is integrated with third-party (non-Cisco) software and/or hardware systems, which need to be managed during a migration to new hardware, software, as well as renaming and re-IP Addressing.

Changes and Enhancements


During the migration, there may be opportunities to introduce enhancements to the system, and in some cases changes will be necessary to increase project success. In either case, all changes and enhancements are documented below.

Setting Device Owner User ID, Line Appearance Associations and End User Control


Setting the device owner user ID allows the Prime License Manager (PLM) accurately account for device usage and application of the appropriate license level.

Setting the Line Appearance Association allows Jabber to accurately determine a user’s status: whether they’re on the phone or not.

Setting the End User Control does two things: allows the user to manage the device in Self Care Portal and Sets the user’s primary extension.

We will use BAT’s Phone Export All Details feature, modify the data to include Owner User ID information, and then use BAT’s Phone Import and Override Configuration feature to apply the changes.

We will use BAT’s User Line Appearance Update feature to set Line Associations.

We will use BAT’s User Update User with the ignore character supplied such that we only modify the Controlled Device and the Primary Extension.



In the event that BAT cannot be leveraged for this task, a manual update may be required.

Phones with no users

Users with one phone

Users with more than one phone











Resources


  • Cisco Unified Reporting – Unified CM User Device Count


  • CUCM BAT Administration Guide
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/bat/10_0_1/CUCM_BK_CDB9A6A4_00_cucm-bulk-administration-guide-100.html



The database is protected by copyright ©ininet.org 2016
send message

    Main page