B Migration Lab Short Guide

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab
v3
First Published: 2022-08-29
Last Modified: 2022-08-29
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2022 Cisco Systems, Inc. All rights reserved.
CONTENTS
CHAPTER 1 About 1
About This Lab 1
Limitations/Disclaimer 1
Requirements 2
About This Solution 2
Transition Overview 3
Pre-Transition Steps and Consideration 4
Core Components Overview 5
Webex by Cisco Overview 5
Accelerate Teamwork with These Tools 6
Webex Hybrid Services 7
Available Hybrid Services 7
Webex Calling Overview 8
CHAPTER 2 Getting Started 9
About This Lab 9

Topology and Equipment Details 9
Session Users 11
Get Started 12
Creating Agent Install File 13
CHAPTER 3 Phase 0: Unified CM Calling 17
Mapping the Transition: Phase 0 – Unified CM Calling 17

Users in Phase 0 18
Validate PSTN Dialing – Optional Module 18

Testing Calls – Inbound from PSTN to Jabber Users 18
Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

iii
Contents
Testing Calls – Outbound to PSTN 19
CHAPTER 4 Phase 1: Hybrid Services 21
Mapping the Transition: Phase 1 – Hybrid Services 21

Users in Phase 1 22
User Synchronization 23
User Synchronization Using Directory Connector 23
Configuring Directory Connector for Identity Synchronization 23
Enable Hybrid Directory Connector 24
Configuring Webex Hybrid Messaging Service 28
Enabling the Message Connector 29
Enabling Hybrid Message Service for Users 32
Testing the Hybrid Message Service 32
Synchronize Organizational Contacts to Webex 33
Understanding Organizational Contacts 33
Synchronize Organizational Contacts through LDAP 34
Method 1 - Using LDAP Search Configuration 34
Method 2 - Using Custom Filter 36
Testing Organizational Contacts Migration 39
Migrate Personal Contacts to Webex App 39
CHAPTER 5 Phase 2: Webex Calling 47
Users in Phase 2 47
Configure Local Gateway for PSTN Calling 47

Adding a Telephone Number and Assigning to a Location 49
Configure Premises-Based PSTN 51
Local Gateway 51
Using Trunks 51
Add a Trunk 52
Option A: Add a Trunk Using PowerShell Script 52
Configuring the Local Gateway (Automated Method) 52
Option B: Add a Trunk Using Manual Steps 56
Add a Trunk 56
Local Gateway Configuration 57

iv
Contents
Local Gateway Certificate Configuration and Verification 60

Configuring SIP Profile 65
Migrate Calling from On-Prem UCM to Webex 78
Updating the On-prem Services 84
Updating the DNS SRV Records - Information Only 85
Sign into Webex after Migration 86
Test PSTN Calls via Local Gateway for Migrated Users 86
Test Calls – Inbound from PSTN to Webex 88
Testing Calls – Inbound from PSTN to Webex 89
Testing Calls – Outbound to PSTN 89

v
Contents

vi
CHAPTER 1
About
• About This Lab, on page 1
• Limitations/Disclaimer, on page 1
• Requirements, on page 2
• About This Solution, on page 2
• Transition Overview, on page 3
• Pre-Transition Steps and Consideration, on page 4
• Core Components Overview, on page 5
• Webex by Cisco Overview, on page 5
• Accelerate Teamwork with These Tools, on page 6
• Webex Hybrid Services, on page 7
• Available Hybrid Services, on page 7
• Webex Calling Overview, on page 8
About This Lab

This lab will walk you through detailed migration process of on-prem calling resources to Webex, including
migration steps for users (from Microsoft AD to Webex) and contact sync (both organizational and personal).
It also provides configuration process for Hybrid Messaging Service for users who would want to migrate
their environment in Phases.
Limitations/Disclaimer
Collaboration Transitions is focused on moving collaboration workloads from existing on-premises, hybrid,
and cloud products and solutions to the latest on-premises, hybrid, and cloud-delivered collaboration services.
As customers transition existing collaboration workloads to the newest collaboration applications and services,
they must understand the implications of this transition and the steps required to make the transition.
There are various ways this can be accomplished, depending on the situation and the customer's
goals/requirements. Please ensure that you consult all current official Cisco documentation before proceeding
with a design or installation. This lab is primarily intended to be a learning tool and may not necessarily follow
best practice recommendation at all times, in order to convey specific information.

1
About
Requirements
Requirements
Required Optional
Laptop Cisco AnyConnect
client
About This Solution

With the growth of cloud-delivered collaboration services, more and more customers are looking to move
their existing collaboration workloads to the cloud given the promises of reduced total cost of ownership,
simplified management, continuous feature delivery, increased scale, and superior reliability inherent in
cloud-based services. As customers look to make the transition from on-premises to cloud collaboration
services, it’s important for them to understand what the transition entails and the steps required to make the
transition.
Customers who wish to start leveraging Cisco cloud calling services should consider Cisco Webex. The cloud
calling service allows the customer to leverage the Cisco Webex global architecture for scale and connectivity.
Participants on the corporate network and remote participants outside the corporate network can communicate
using IP-based hardware endpoints or desktop or mobile soft client applications.
Customers who have an on-premises call control with Unified CM, desk and video IP endpoints have a choice
of transitioning the architecture toward a Cisco Webex Calling cloud architecture.

2
About
Transition Overview
The decision needs to be made based on customer’s functionality requirements. Customers that have the
following requirements should consider carefully before making this decision and may ultimately decide to
keep call control on-premises:
• Phone models other than Cisco 7800 and 8800 IP phone series.
• Complex or numerous integrations with other on-premises systems.
• Complex dial plan and/or highly granular classes of service.
• Calling predominately within the organization.
• Restrictive, limited, or unreliable Internet access.
• Stringent data privacy and ownership policies.
• Compliance requirement for on-premises or in-country media recording and storage.
Note More information can be found at https://www.cisco.com/go/ct
Transition Overview
This lab will focus on a phased transition. As shown in below image, the initial transition phase (Phase 1)
results in a hybrid deployment with dual call control where some devices are transitioned to cloud calling and
other devices maintain on-premises call control for registration and call routing.
The final transition phase (Phase 2) results in a pure cloud calling environment where calling services have
been fully transitioned to cloud call control.
Note It is possible that some organizations may maintain a hybrid dual call control deployment.

3
About
Pre-Transition Steps and Consideration
Pre-Transition Steps and Consideration

Below is a summary of pre-transition items/steps to consider when performing the transition from Unified
CM on-premises calling to Webex Calling.
Pre-Transition Consideration Summary

Perform network readiness assessment It is recommended to confirm network bandwidth availability,
ensure QOS requirements are met and FW ports are opened.
Perform initial readiness assessment of Prior to transition, to determine the feasibility and potential
existing deployment. modifications required, it is important to consider each of the
following aspects of your existing deployment. That includes
Licenses, Platform, Devices, Local Gateways, Network
Connectivity, Voicemail, Call Recording.
Understand Webex Calling region selection Cisco Webex Calling operates four regional platforms: North
America, EMEA, APJC (Japan) and APJC (Australia). Each
Webex Calling instance provides redundant data centers within
that region.
Each Webex Calling customer is provisioned on one of the
four Webex Calling instances. All provisioning information
of that customer is stored in that Webex Calling instance and
the SIP signaling of all endpoints and Local Gateways
provisioned for that customer is tied to the Webex Calling
instance the customer is provisioned on. Hence it is important
to select the right region for your deployment.
Analyze deployment dial plan Each user in Webex Calling is provisioned with an extension.
For inter-site dialing use non-overlapping abbreviated dialing
habits. For a smooth transition the set of dialing habits for users
before and after transitioning to Webex ideally should be the
same.
Inventory existing locations/ sites For transitioning the information for Extension Ranges,
DID,PSTN Steering Digit, Site Code ,Main Number VM
number, Concurrent calls during busy hour, Country, Time
Zone, Language, Contact/Address need to be collected.
Understanding PSTN access options A local gateway is required to create a connection between
Unified CM and Webex Calling as long as Unified CM and
Webex Calling coexist. PSTN in Webex Calling can either be
facilitated by a (CCP) provider via a Local GW or Cisco PSTN.

4
About
Core Components Overview
Pre-Transition Consideration Summary

Inventory existing endpoints/clients Before beginning the transition it’s important to inventory your
existing hardware and software endpoints. Having a complete
list of phone types, models, and quantities will ensure you can
adequately plan for transitioning endpoints and mitigating the
impact to your deployment for those devices that cannot be
migrated to cloud calling. The inventory should be used to
determine the endpoints to transition, the endpoints to replace
prior to the transition, and the endpoints that may remain
managed and registered to on-premises call control.
Inventory and plan for existing users Determine which users within the existing set of on-premises
transition to Webex Calling. calling users will be transitioned to Webex Calling. If all users
will be transitioned, but the number of users is large, it is a
good idea to move users in groups in order to ensure that IT
staff and support personnel are able to handle the transition
and any issues that may arise.
Core Components Overview

The target architecture for this lab migration includes several new components. This includes the Webex
Calling service for cloud-based calling, Webex client application, Cisco Directory Connector for identity
integration, Webex Meetings, and the Local Gateway IOS-XE router for PSTN access as well as
on-premises-to-cloud calling integration. Cisco PSTN and Cloud Connected PSTN (CCP) facilitated by a
provider partner is another option for PSTN access that will not be covered in this lab guide.
Webex by Cisco Overview

Never before have we seen business innovation this rapid, and competition this intense. Businesses will rise
and fall by the strength of the teams that fuel their agility. Teams that include not only internal colleagues,
but ecosystems of external experts and partners as well. To support your teams, you need tools that bring
people together easily and enable them to work together productively. At the same time, you need to meet
increasingly complex security and compliance requirements, which are key to keeping your information safe
and secure. It’s time for you to look at the team collaboration experience enabled by Webex by Cisco.
Webex is an easy-to-use collaboration solution that keeps people and teamwork connected anytime, anywhere.
With Webex, you create secure virtual workspaces for everything, from completing short-term projects to
solving longer-term business opportunities. Simplify day-to-day interactions with messaging and file sharing
that can be enhanced with third party app integrations for a seamless workflow. Increase productivity and
engagement with real-time communications. Start calls instantly, have high-quality video meetings with
screen-sharing at the touch of a button, and stay connected after. Express your ideas on digital whiteboards
that colleagues can add to at any time. When teamwork flows into meeting rooms, bring the Webex experience
with you. Just connect the app to a Webex device to start meetings wirelessly, share your screen, capture
life-size whiteboard drawings, and more. That’s Webex. Moving all your work forward. Are you in?
Communication needs to be agile, mobile, and collaborative—all thanks to mobile devices and evolving
innovations in infrastructure and applications. The Cisco Webex service makes instant communications and
live meetings possible through a deeply integrated set of industry-leading communications tools for an
unmatched collaboration experience—that only the Cisco cloud can deliver. Webex has a continuous delivery

5
About
Accelerate Teamwork with These Tools
model, which means features are released on a regular basis. Check help.webex.com to keep updated of all
the latest info.
Accelerate Teamwork with These Tools

Messaging and content sharing: Use teams and spaces to easily bring people together. Send messages, meet,
share files, and whiteboard. Spend less time chasing email and instant messaging, more time getting work
done.
Team-based meetings: Maximize productivity. Anyone in a space can schedule, start, and record meetings.
Keep work moving after the meeting in the connected workspace.
Whiteboarding: Collaborate on sketches in the app. Or take Webex capabilities to the next level with Webex
Board’s all-in-one wireless presentation, digital whiteboarding, and video conferencing.
Calling: Handle calls where you want—in the app, on an IP phone, or with a conference-room video device.
Deploy in the cloud with Webex Calling or connect to on-premises or partner-hosted telephony services.
Integrations and bots: Help users rely on fewer systems and apps by bringing them together in Webex. Use
integrations to streamline work flows and bots to automate actions. Visit the Webex App Hub to explore more.

6
About
Webex Hybrid Services
Webex Hybrid Services

Increase the benefits of your on-premises unified communications and collaboration investment with Webex
Hybrid Services. They simplify connecting your existing network resources and on-premises unified
communications services to the Webex platform in the cloud. This provides even greater collaboration
capabilities, along with consistent, unified user and administrator experiences.
More and more, organizations are choosing collaboration services from the cloud. Why? Cloud services:
• Are easier and faster to deploy.
• Don't require the upfront capital investment of on-premises systems.
• Can free up IT staff to focus on other priorities.
Many organizations, however, are unable or unwilling to move all their services to the cloud. Often, they are
not ready to replace everything they have on premises, or they simply want to augment their current
collaboration tools with those from the cloud. But having tools from both the cloud and the premises can
create inconsistent, disjointed user experiences and tools that don't work together as one.
Cisco solves this problem with Webex Hybrid Services. These services connect what you have on-premises
with Webex in the cloud to provide a single integrated experience. If you like the capabilities of Webex, you
can integrate those capabilities with what you currently deploy for an even better end-user and administrator
experience.
Available Hybrid Services

Hybrid Calendar Service: This service integrates your on-premises Microsoft Exchange, Office 365, or
Google Calendar with Webex and Webex Meetings capabilities. Hybrid Calendar Service easily and
automatically creates a Webex workspace when scheduling meetings. For example, adding the phrase “@webex”
to the invite’s location field automatically populates the meeting join information. Hybrid Calendar Service
also allows Webex users to press a single button to join almost any upcoming meeting within the app itself
and on a video device.
Hybrid Directory Service:This service connects Active Directory to Webex and enables a user to see all
company contacts in the Webex app so that they can click to meet, message, or call. It also provides user
synchronization between Microsoft Active Directory and Webex user management. Hybrid Directory Service
simplifies the administrative experience by automatically synchronizing Microsoft Active Directory users
with Webex (creating, updating, deleting) so that users are always current in Webex.
Webex Video Mesh: This revolutionary capability removes the deployment decision of premises versus cloud
for Webex video meetings. It places our Webex meeting engine on-premises to provide local media processing.
The result is on-premises video quality and optimized Internet bandwidth. And it delivers this with simplicity,
flexibility, and rapid iteration of new functionality of the cloud.
Hybrid Data Security Service: Ideal for security-conscious customers, Cisco Hybrid Data Security Service
takes our industry-defining data security a step further by allowing customers to own and manage their own
keys on premises. You will still experience end-to-end encryption, helping ensure that all messages, files, and
whiteboards remain secure and available at all times, while retaining full access to features such as search.
With Webex, your data is private. This includes all content, messages, and files—even your whiteboard
drawings.

7
About
Webex Calling Overview
Webex Calling Overview

For businesses that have been waiting for a trusted brand to deliver a globally available, multi-tenant cloud-based
alternative to their on-premises PBX, the wait is over. Webex Calling delivers all the features of a traditional
PBX through a monthly subscription service. Important qualities include:
• An advanced set of enterprise-grade PBX features.
• A rich user experience that includes the Webex app for mobile and desktop users.
• Support for an integrated user experience with Webex Meetings and Webex devices, including Cisco IP
Phones 6800, 7800, and 8800 Series desk phones and analog ATAs.
• Delivery from a set of regionally distributed, geo-redundant data centers around the globe.
• Service that is available across a growing list of countries in every region.
• Protection of existing investment in any on-premises Cisco Unified Communications Manager (UCM)
licenses, through the Cisco Collaboration Flex Plan.
• A smooth migration to the cloud at your pace, through support of cloud and mixed cloud and on-premises
deployments.

8
CHAPTER 2
Getting Started
• About This Lab, on page 9
• Topology and Equipment Details, on page 9
• Session Users, on page 11
• Get Started, on page 12
• Creating Agent Install File, on page 13
About This Lab

This lab will walk you through detailed migration process of on-prem calling resources to Webex, including
migration steps for users (from Microsoft AD to Webex) and contact sync (both organizational and personal).
It also provides configuration process for Hybrid Messaging Service for users who would want to migrate
their environment in Phases.
Topology and Equipment Details

This demonstration includes several server virtual machines. Most of the servers are fully configurable using
the administrative level account. Administrative account details are included in the lab guide steps where
relevant and in the server details table.

9
Getting Started
Topology and Equipment Details
Name Description Host Name (FQDN) IP Address Username Password

CUCM1 Cisco Unified cucm1.dcloud.cisco.com 198.18.133.3 administrator dCloud123!
Communications
Manager 12.5
IM & P IM & Presence 12.5 cup1.dcloud.cisco.com 198.18.133.4 administrator dCloud123!
Exp-C Expressway-C vcsc.dcloud.cisco.com 198.18.133.152 admin dCloud123!
(Core) X12.5
Exp-E Expressway-E vcse.cbXXX.dc-YY.com Public IP (see admin Session Details
(Edge) X12.5 session details) > AnyConnect
Credentials >
Password*
Exp-Base Expressway-C exp-cc.dcloud.cisco.com 198.18.133.223 admin dCloud123!
Connector Host
X12.5
Local CSR1000V N/A 198.18.133.226 admin dCloud123!
Gateway
AD1 Active Directory, ad1.dcloud.cisco.com 198.18.133.1 administrator dCloud123!
DNS, AD FS
Exchange Microsoft Exchange mail1.dcloud.cisco.com 198.18.133.2 administrator dCloud123!
2016
Workstation Windows 10 wkst1.dcloud.cisco.com 198.18.1.36 cholland dCloud123!
1
Workstation Windows 10 wkst2.dcloud.cisco.com 198.18.1.37 aperez dCloud123!
2
Workstation Windows 10 wskt3.dcloud.cisco.com 198.18.1.38 kmelby dCloud123!
3
*You can find your unique Expressway-E password in your dCloud Session Details.

10
Getting Started
Session Users
Session Users
This table contains details on preconfigured users available for your session.
Note • Replace XXX and YY with your dCloud session's DNS number. Denote for use in this lab. Each dCloud
session has unique information. Do not use the information in the example.
• Replace ZZZZ with the last four digits of your dCloud Session ID number. Denote for use in this lab.
Each dCloud session has unique information. Do not use the information in the example.
User Name User Password Endpoint Internal Deployment Model

ID Devices Extension
Anita Perez aperez dCloud123! Jabber 6017 OnPrem /Hybrid
/Cloud
dCloudZZZZ! Webex
Charles Holland cholland dCloud123! Jabber 6018 OnPrem /Hybrid

/Cloud
dCloudZZZZ! Webex

11
Getting Started
Get Started
User Name User Password Endpoint Internal Deployment Model

ID Devices Extension
Taylor Bard tbard dCloud123! Jabber 6021 OnPrem /Hybrid
/Cloud
dCloudZZZZ! Webex
Kellie Melby kmelby dCloud123! Jabber 6050 OnPrem /Hybrid

/Cloud
dCloudZZZZ! Webex
Stefan Mauk Smauk dCloud123! Jabber 6072 OnPrem /Hybrid

/Cloud
dCloudZZZZ! Webex
Rebekah rbarretta dCloud123! Jabber 6088 OnPrem /Hybrid

Barretta /Cloud
dCloudZZZZ! Webex
Get Started
Follow the steps to schedule a session of the content and configure your presentation environment.
Step 1 Initiate your dCloud session. [Show Me How] (Skip if you are in a proctored environment.)
Note It may take up to 45 minutes for your session to become active.
Step 2 For best performance, connect to the workstation with Cisco AnyConnect VPN [Show Me How] and the local RDP
client on your laptop [Show Me How]
Step 3 The lab requires desk phones some to be loaded with latest firmware.
Step 4 The room devices (Webex Desk Series / Webex Room Series / Webex Board Series) also require vCE8.1+ firmware. If
you are in a proctored environment, your proctor should have installed the correct firmware on your room device. Another
way to update the room device is to download the .pkg file from cisco.com and upgrade the device directly. TIP: You
can click here to get help with the upgrade process.
Step 5 After confirming the devices have the correct firmware and are not in a factory reset state, perform a factory reset on
each device before starting the lab. (Skip if you are in a proctored environment.)
Note For best results, use either the Chrome or Firefox web browsers.
Step 6 To demonstrate Cisco Webex hybrid services, Cisco Jabber/Webex is used in the lab. You also have the capability to
attach a dCloud router and self-provision any physical phone to demonstrate hybrid services.
Step 7 Check that the Collaboration Edge capabilities are properly provisioned in your session.
• On Workstation 1, open a browser tab and go to Collaboration Admin Links > Cisco Expressway – C. Log in
with Username: admin and Password: dCloud123! Accept any security message you may be shown.
• Navigate to Configuration > Zones > Zones tab and confirm all Traversal client zones show SIP status as Active.
DefaultZone should show SIP status as On.
Note If any of these zones do not have an Active SIP Status, the session is corrupted and you will not be able to
proceed. Please End the current session and start up a new one. This does happen occasionally due to
automation errors.

12
Getting Started
Creating Agent Install File
Step 8 In order to run this lab, you need some information from the Session Details tab on your dCloud dashboard session page.
Obtain the Collaboration Edge domain information.
Important Each session has a unique domain. The image below is only an example. Do not use the information in the
image below for your session. It is highly recommended to take note of this information now so that you can
refer to it throughout the lab.

Before we start working on the lab, let's create an Agent file on Control Hub and install it on the Cisco UCM
server. The reason we are doing this before getting started with lab is, once the Agent file is installed, it takes
a couple of minutes to synchronize data (that we will use later in the lab) from On-Prem to Cloud. So, if we
can install the Agent file now and let it synchronize data, by the time we reach Phase 2, the migration in this
lab synchronization will be complete and data will be ready and we will not need to wait.
The Agent file that we generate and download from Webex Control Hub consists of proxy information taken
from Admin via Control Hub. It also consists of code that registers the primary agent with the Cisco (ucmgmt)
Cloud. Once installed on a Cisco UC system, it then connects to cloud to download various other services,
such as:
• Telemetry Service - The main service for Cisco Cloud Connected UC (CCUC), which sends inventory,
etc. to the CCUC cloud.
• Migration Service - Service dealing with many migration features. One of which is LDAP-Sync where
customers would like to migrate their UCM LDAP contacts and users into Webex.

13
Getting Started
Step 1 Open RDP connection to Workstation 1 at 198.18.1.36. Log in with dcloud\cholland and dCloud123!
Step 2 Open the Chrome browser from the task bar.
Step 3 From the home page, select Cisco Webex Links > Cisco Webex Control Hub. Log in with
cholland@cbXXX.dc-YY.com and dCloudZZZZ!
Note • Replace XXX and YY with your dCloud session's DNS number.
• Replace ZZZZ with your dCloud Session ID number.
Step 4 Navigate to Services > Connected UC. On the Connected UC page, click Enable Connected UC. Under the UC
Management card, click Get Started.

14
Getting Started
Step 5 Click Next on the Welcome to Cisco Control Hub page. Read the information for Create an Agent Install File. Name
the file dCloud-CCUC. Click Save.
Step 6 Webex Control Hub will create an agent install file that needs to be installed on each Unified Communications Manager.
The file creation will take a few minutes. Once it is created, DO NOT click Download. Click Next.
Step 7 On the Create Cluster Group page, enter the Cluster Group Name and Group Description of your choice. Click Save.
Click Next. Click Finish.

15
Getting Started
Step 8 You will be taken back to Connected UC page. Click Inventory under UC Management. (You might have to refresh
the page.) On the UC Management page, select Install Files on top-right corner.
Step 9 You will see the agent file you created above. Click Download. A new pop-up window will open with a couple of options
to download. Next to Version 12.5(SU2)-12.5(SU3), select Download. It will download the agent file to the workstation's
desktop.

16
CHAPTER 3
Phase 0: Unified CM Calling
• Mapping the Transition: Phase 0 – Unified CM Calling, on page 17
• Users in Phase 0, on page 18
• Validate PSTN Dialing – Optional Module, on page 18
Mapping the Transition: Phase 0 – Unified CM Calling

In Phase 0 of this lab guide we will be focusing on on-prem deployments. A typical on-prem deployment
includes different collaboration infrastructure components on the network, a call control platform, and an
edge platform, hardware and software endpoints, and in some cases even conferencing and scheduling platforms.
In the Cisco architecture this would include Cisco Unified CM for call control, Cisco Expressway for remote
access and business-to-business (B2B) edge services, Cisco Meeting Server / Cisco Meeting Management
for on-premises conferencing, Cisco Unity Connection for voice messaging, and user-facing hardware (Cisco
IP Phones and Cisco Webex Room Endpoints) and software (Cisco Jabber/Webex) IP-based endpoints.

17
Users in Phase 0
Users in Phase 0
User Name User Password Endpoint Internal Deployment
ID Devices Extension Model
Charles cholland dCloud123! Cisco Jabber 6018 OnPrem
Holland
Anita Perez aperez dCloud123! Cisco Jabber 6017 OnPrem
Kellie Melby kmelby dCloud123! Cisco Jabber 6050 OnPrem
Validate PSTN Dialing – Optional Module

Module Overview
We will do inbound/outbound calls to make sure PSTN is working .
Pre-Requisites
For outbound dialing rules and patterns, visit Outbound Dialing Patterns and Blocked International Dialing
online.
Module Objectives
In this module, we will perform the following tasks either via physical phone or Webex/Jabber soft client:
• Test inbound calls to our users
• Test Outbound Calls
Testing Calls – Inbound from PSTN to Jabber Users
Step 1 For dialing inbound PSTN calls to your pod’s phones, information can be found in your dCloud session's Details tab or
in a text document found on the desktop of Workstation 1 named DN_to_DID.txt.
Step 2 Those DID can be dialed from your mobile numbers.
Step 3 With the DID number, dial one of your user's using a cell or desk phone, such as dial cholland DID number.
Step 4 Answer the call on your Jabber app/device.
Step 5 The call flow in dCloud is as follows:
a) Incoming DID comes into dCloud.
b) Platform gateways translate that DID into a four-digit extension (6XXX or 7XXX).
c) Call is routed through the local gateway into Unified CM and to the extension of the user.

18
Testing Calls – Outbound to PSTN

In dCloud, national calls are allowed to the datacenter region your session is located in. US West/East
datacenters are dc-05 or dc-01. EMEAR datacenter is dc-03. APJ datacenter is dc-02.
In the US datacenters you should be able to call any national number. Remember since the location is built
for the United States, Webex will add a +1 to any dialed number if needed. So a 10 digit number can be called
or a 1 + 10 digit number.
Dialing from an EMEAR or APJ session will be just a little different than US. Every session, no matter the
datacenter, the Webex Calling location is built for United States. Because of this, in the lab, dialing a national
number for the UK (EMEAR) or Singapore (APJ) requires you to dial a 00 + Country Code and then the
number (10 digit for UK and 8 digit for Singapore). For the EMEAR datacenter the country code is 44. For
the APJ datacenter the country code is 65.
When you dial 00 and the number, Webex Calling will route the number as is and not add +1. Then the call
flow for EMEAR and APJ sessions is as follows:
• Call comes into Local Gateway, sent to dCloud Gateway, which delivers it to the IP PSTN.
• The dCloud GW will strip the 00 off the number and add a plus (+) or localize it.
• The +E.164 or the localized number is now routed by the IP PSTN and rings the PSTN number.
Step 1 With the dialing explanation above, dial a PSTN number.

Step 2 Answer the call.

19

20
CHAPTER 4
Phase 1: Hybrid Services
• Mapping the Transition: Phase 1 – Hybrid Services, on page 21
• User Synchronization, on page 23
• Configuring Webex Hybrid Messaging Service, on page 28
• Synchronize Organizational Contacts to Webex, on page 33
• Synchronize Organizational Contacts through LDAP, on page 34
• Migrate Personal Contacts to Webex App, on page 39
Mapping the Transition: Phase 1 – Hybrid Services

In Phase 1 of this lab guide, we focus on hybrid deployments. The Phase1 transition results in a hybrid
deployment with dual call control where some devices are transitioned to cloud calling and other devices
maintain on-premises call control for registration and call routing. For the users, we will be using Cisco Webex
to log in. Users can log in on the Workstations provided in the demo or their personal devices.

21
Users in Phase 1
Users in Phase 1
Note • Replace XXX and YY with your dCloud session's DNS number. Each dCloud session has unique
information. Do not use the information in the example.
• Replace ZZZZ with the last four digits of your dCloud Session ID number. Each dCloud session has
unique information. Do not use the information in the example.
User Name User ID Password Endpoint Internal Deployment

Devices Extension Model
Kellie Melby kmelby dCloud123! Cisco Jabber 6050 Hybrid
Stefan Mauk smauk dCloud123! Cisco Jabber 6072 Hybrid
Adam amckenzie dCloud123! Cisco Jabber 6016 Hybrid
McKenzie
dCloudZZZZ! Webex

22
User Synchronization
User Name User ID Password Endpoint Internal Deployment

Devices Extension Model
Monica Cheng mcheng dCloud123! Cisco Jabber 6020 Hybrid
dCloudZZZZ! Webex
Anita Perez aperez dCloud123! Cisco Jabber 6017 Hybrid

dCloudZZZZ! Webex
User Synchronization
User Synchronization Using Directory Connector
•
Configuring Directory Connector for Identity Synchronization

What is Directory Connector?
Cisco Directory Connector is an on-premises application for identity synchronization in dcloud. Directory
Connector is an essential tool for synchronizing your Active Directory with the back-end Cisco identity store
and allows users to seamlessly use Cisco services such as Cisco Webex Meetings and Teams.
With Cisco Directory Connector, you can maintain your user accounts and data in the Active Directory, so
Active Directory becomes the single source of truth. When you make a change on-premises, it is replicated
to the cloud.
Module Objectives
In this module, we will replicate user accounts from On-prem AD server to the cloud using directory connector.
Module Notes
Note Because of the lab environment we will be installing directory connector on WKST1. In a production
environment, it is highly recommended to follow the Directory Connector Deployment Guide and install it
on a recommended machine. In the interest of time, this step has already been configured. The install file
for Directory Connector can be downloaded from customer management portal (Control Hub) in Users >
Manage Users > Turn on Directory Synchronization screens.
Pre-Requisites and Requirements
Important The Requirements for Directory Connector need to be followed in production deployments.

23
Enable Hybrid Directory Connector
Step 1 Go to the RDP session on WKST1 (cholland / dCloud123!).

Step 2 Click the Search icon
[ ]
in the taskbar. Search for Cisco Directory Connector. When found, click the application icon
[ .]

24
Step 3 At the Webex sign in screen, enter cholland@cbXXX.dc-YY.com and click Next.
Note Replace the XXX and YY with your session DNS information.
Step 4 Enter dCloudZZZZ! as the password in the next box and click Sign In.
Note Replace the ZZZZ with the last four digits of your Session ID information.
Step 5 Keep the radio button for AD DS selected and click Load Domains.
Step 6 In the drop-down list, choose dcloud.cisco.com and click Confirm.
Step 7 Click Yes on the automatically upgrade pop-up window. If you get the option to do Dry Run, click Not Now.
Step 8 Now that the Directory Connector is open, configure it to synchronize the users along with their pictures (avatars).
Step 9 Click the Configuration tab at the top.
Step 10 Click the Object Selection tab so you can specify the users to synchronize. The connector synchronizes the entire
domain’s users and groups by default. For the purposes of the lab, you only synchronize a set of users in a specific
Organizational Unit (OU).
Step 11 Uncheck the box next to Groups.
Step 12 Click Select located in the On Premises Base DNs to Synchronize section.
Step 13 Uncheck the top box next to DC=dcloud,DC=cisco,DC=com to de-select all the check boxes.
Step 14 Check the box next to dCloud and click Select. (You must ONLY select the dCloud container.)
Step 15 With exception to the Cloud Organization name, the Object Selection page should look like the image below.

25
Step 16 Click the Avatar tab and check the box next to Enabled.
Step 17 In the Avatar URI Pattern box, enter the following URI: http://ad1.dcloud.cisco.com/dCloud/directory/{mail:
.*?(?=@.*)}.jpg
Note On the desktop, there is a text document named Pattern.txt that you can copy the pattern from.
Step 18 Click Apply at the bottom of the screen.

Step 19 On the pop-up, click Apply Config Changes. Now you can complete a Sync Dry Run to verify the correct users
synchronize.
Step 20 Click the Dashboard tab at the top.

26
Step 21 Click the Sync Dry Run icon
[ ]
and click OK. You should see the eight users that will be added to your organization. Click Done.
Step 22 Now enable the synchronization. Click the Actions menu and choose Synchronization Mode > Enable Synchronization.
Step 23 Click No on the pop-up since you already performed a dry run.
Step 24 Click Enable Now on the pop-up to enable synchronization.
Step 25 Now complete a full sync. Click the Actions menu and choose Sync Now > Full.
Step 26 Click Yes on the pop-up.

Step 27 In the Current Synchronization section, you can see the progress of user creation and avatar uploads. After the sync
completes, in the Last Synchronization section, you should see a status of No Errors.
Note If you received any Sync errors/warnings, try completing another full sync. You can also view the
errors/warnings in the Event view by clicking Launch Event Viewer in the directory connector. Then
navigate to Applications and Services Logs > Cisco Directory Connector to view all the events.
Step 28 Verify the users have synchronized by opening the Web browser on WKST1. Browse to Webex Control Hub
(https://admin.webex.com). Log in as cholland@cbXXX.dc-YY.com with the password of dCloudZZZZ!
Note Remember to replace XXX and YY with the info in your session detail page.

27
Configuring Webex Hybrid Messaging Service
Step 29 In the Control Hub portal, click the Users tab
[ .]
(Refresh the page, if you are already there.)
Step 30 You should see a list of 10 (two new) users along with their avatars and user information such as email address and
name. Notice the two new users (Adam McKenzie and Monica Cheng) have the status as Verified. It indicates those
users came from a trusted source, but they haven’t logged into Webex yet.
You have now successfully synchronized the customer’s on-premises Active Directory and configured users to their
Webex Control Hub Organization.
Configuring Webex Hybrid Messaging Service

Module Overview
Cisco Webex Hybrid Message Service connects your Cisco Unified Communications Manager, IM and
Presence Service (IM and Presence Service) to Cisco Webex to enable interoperability with Cisco Webex.
This service is ideal for organizations that have users on Cisco Webex who need to exchange messages with
users on Cisco Unified Communications Manager IM and Presence (UCM IM&P) Service. Hybrid Message
Service enables exchange of instant messages between Cisco Webex and Cisco Jabber registered to Unified
CM IM and Presence service. Hybrid Message Service enables Cisco Jabber users to see the presence status
of Cisco Webex users based on their Webex client activity.
You can find the full Webex Hybrid Messaging overview and setup guide here.
Pre-Requisites
• To complete this module, you will need to have CUCM and IMP with minimum version of 11.5(1) SU3
or later.
• All publisher nodes to be running AXL service.
• If you have multiple IMP clusters, you must have ICSA working across them. (Not part of this lab.)

28
Enabling the Message Connector
Module Objectives
In this module, we will perform the following tasks:
• A requirement for the Message Connector is to have an application user created with the role of Standard
AXL API Access. The Message Connector will use this account to communicate with Unified CM IM
and Presence Service. For this lab, this user has been created for you. In the Appendix, you will find the
necessary steps to create this user and assign permissions. The user is also configured with other roles
that can be used with future updates. Only the one role mentioned above is necessary for the hybrid
messaging service.
• Enable Hybrid Messaging for kmelby and smauk.
• Send messages between on-prem-registered (Jabber) users (cholland and Aperez) and
Webex-registered (cloud) users (kmelby and smauk).
Step 1 If not already open from earlier, log in to WKST1. Open a new browser tab to https://admin.webex.com. Log in using
cholland@cbXXX.dc-YY.com / dCloud123!
Step 2 Under Services on the left-hand menu within the portal, select Hybrid.
Step 3 Click Setup on the Hybrid Message Service Setup tile. In the popup window, click Next.
Step 4 At the first radio button, select and enter exp-cc.dcloud.cisco.com into the box and click Next.
Note The DNS entry for exp-cc.dcloud.cisco.com is already created as part of this lab.
Step 5 For a display name for Expressway cluster, enter HS Cluster 1.

Step 6 Click Next again.
Step 7 Click Next once more to open a new browser tab to the Expressway. Ignore/accept/proceed through any security
warnings.
Step 8 If prompted, log into the Expressway as admin with password dCloud123! (Should be prepopulated.)
Step 9 Check the box for I want Cisco to manage the Expressway CA certificates required for this trust.
Step 10 Click Update software & verify connection.
Step 11 After successful verification, click Register. (If prompted to log in into Webex, enter cholland@cbXXX.dc-YY.com /
dCloudZZZZ! for the username / password.)
Step 12 On the next screen, check the box next to Allow Access to the Expressway and then click Continue. In a few moments,
you return to the Expressway and two Hybrid Services connectors will download and install. These connectors are
Management and Message Connector. The Service Status for Message Connector will go from Not Installed, to Installing,
to Not Configured. When the Service Status of the Expressway host reads Not configured. That status tells you the
Message Connector was successfully downloaded and installed.
Step 13 If not already logged in, from WKST1 log in into expressway connector(exp-cc.dcloud.cisco.com).
Step 14 Log in with:
• Username: admin
• Password: dCloud123!

29
Step 15 On the Connector Management page, click Configure IM and Presence Servers. You can also navigate to
Applications > Hybrid Services > Message Services > Message Service Configuration.
Step 16 Click New.
Step 17 Configure the following parameters from the table below.
Setting Configuration
IM and Presence Publisher node address cup1.dcloud.cisco.com
Message Connector AXL account name webex
Message Connector AXL account password dCloud123!
Step 18 Click Add.

Step 19 Click Message Connector is not running, No status info available, (also found at Applications > Hybrid Services
> Message Service > Message Service Overview).
Step 20 Choose Enabled for the Active setting and then click Save.
Step 21 Navigate to Applications > Hybrid Services > Message Service > Message Service Status. The Node Status should
be Operational. If it is not, wait until the service goes operational. You might need to refresh the page to view the
updated status.

30

31
Enabling Hybrid Message Service for Users
Enabling Hybrid Message Service for Users

Users will need to be enabled for the Hybrid Message Service. For lab purposes, we will enable one user,
Kellie Melby, for this service. In production, you can enable multiple users in bulk through an CSV template.
Step 1 Open the tab for the Control Hub and log in, if needed (cholland@cbXXX.dc-YY.com / dCloudZZZZ!).
Step 2 Click the Users tab and select Kellie Melby, Stefan Mauk, and Anita Perez one by one from the list.
Step 3 Under Hybrid Services, click Message Service.
Step 4 Toggle the Hybrid Message Service on
[ ]
and click Save.
Step 5 On the main user page, wait for Messaging Service to change its status to Activated.
Testing the Hybrid Message Service

In the lab environment, be aware users could experience a delay of up to one hour before reliably being able
to send messages from Webex Teams to Cisco Jabber. In this case, you might want to skip testing for now if
it’s not working and come back later to test again.

32
Synchronize Organizational Contacts to Webex
Step 1 Connect to Workstation 2 (198.18.1.37) with these credentials:

• Username: dcloud\aperez
Step 2 On Workstation 2, open Jabber client and log in with these credentials (Sign out other users if logged on from earlier):
• Username: aperez@cbXXX.dc-YY.com
Step 3 On Workstation 3 or your personal device, open the Webex client if it’s not already. Use kmelby@cbXXX.dc-YY.com
for the email and kmelby/dCloudZZZZ! for the username/password.
Step 4 Start a conversation between Anita (on-premises registered Jabber client) and Kellie (cloud registered Webex client).
This concludes the scenario.
Synchronize Organizational Contacts to Webex

Understanding Organizational Contacts
Organizational contacts are identities which are imported or synchronized into Webex, and you can search
all users and organization contacts in an organization through Webex app and all Webex devices.
Use the Control Hub-based tool to migrate or synchronize your organizational contacts to Webex. For
on-premises deployments, organizational contacts are configured in the LDAP server as contact objects or in
the Cisco Unified Communications Manager as end-users. You can configure rules in Control Hub-based tool
to classify users in the Unified CM database into end users and contacts.
This tool:
• Synchronizes users and contacts from Unified CM or LDAP server to Webex.
• Automatically detects updates in Unified CM based users and contacts and updates the changes into
Webex.
• Lets you set a schedule for the periodic sync to synchronize users and contacts from LDAP server into
Webex.
• Lets you configure periodic audits to make sure Unified CM users and contact data doesn't get out of
sync with Webex.
You can select only one source of users from either the Unified CM or LDAP server. If you configure directory
connector, then you cannot synchronize users through the tool.
If you do not have Cisco Cloud connectivity, then use the CSV file through Control Hub to import your org
contacts.

33
Synchronize Organizational Contacts through LDAP
Agent Install: You must set up the on-premises servers in your organization to communicate with Cisco
Cloud for data sync. To create this communication link, Cloud-Connected UC agent must be installed on
UCM. Migration tools will leverage this connection for migration and synchronization of on-prem user and
device information to Webex cloud.
LDAP Sync: Organizations use external Active directory services such as Microsoft AD or open LDAP-based
directories to store user and contact objects. This tool fills the gap of synching org contacts from multiple
external ADs to Webex contact service.
Important Make sure you have created the Agent install file on Control Hub and installed it on Cisco UCM server as
instructed before starting with Phase 0 above.
Synchronize Organizational Contacts through LDAP

Method 1 - Using LDAP Search Configuration
SUMMARY STEPS
1. Continuing on Workstation1 (as dcloud\cholland and dCloud123!), go back to the browser tab where
you have Cisco Webex Control Hub open. If logged out, log in with cholland@cbXXX.dc-YY.com
and dCloud123!
2. Under Services, click Updates & Migrations. On the Migrations page, you will find different migration
cards. Click Get Started for User/Contact Synchronization (you might have to scroll down to see this
card).
3. On the User/Contact Synchronization page, click Go to settings under the Prerequisite drop down.
4. On the Settings page, configure the following for LDAP Server (the second option):
5. Go to Periodic synchronization and choose the time to start the synchronization in the next two minutes
from the current time. Click Save and Proceed on top-right corner to save all the configurations we just
updated.
6. Once the configuration changes are saved, you will be taken back to the updates and migrations page.
Under the Status section, drop down the status option and click View synchronization logs to see the
status of the synchronization. The status will change from Pending to In Progress to Completed. Once it's
done, you will see a number of total contacts that have been synced. As shown in the reference below.
7. To verify the contacts that are synced, on the left side page go to Management > Users. On the Users
page, select the Contacts option. It should list the same number of users that are synced in the step
. evoba

34
Method 1 - Using LDAP Search Configuration
DETAILED STEPS
Command or Action Purpose

Step 1 Continuing on Workstation1 (as dcloud\cholland and
dCloud123!), go back to the browser tab where you have
Cisco Webex Control Hub open. If logged out, log in with
cholland@cbXXX.dc-YY.com and dCloud123!
Step 2 Under Services, click Updates & Migrations. On the
Migrations page, you will find different migration cards.
Click Get Started for User/Contact Synchronization
(you might have to scroll down to see this card).
Step 3 On the User/Contact Synchronization page, click Go to
settings under the Prerequisite drop down.
Step 4 On the Settings page, configure the following for LDAP a. Toggle the radio button for LDAP Periodic sync.
Server (the second option):
b. Drop down the option for Cluster Configuration. Click
Add Configuration and configure the following:
1. Cluster name: drop down and choose
StandAloneCluster - cucm1.dcloud.cisco.com
2. Configuration: drop down and choose Use Unified
CM LDAP Search Configuration
3. Click Add.

35
Method 2 - Using Custom Filter

Step 5 Go to Periodic synchronization and choose the time to
start the synchronization in the next two minutes from the
current time. Click Save and Proceed on top-right corner
to save all the configurations we just updated.
Step 6 Once the configuration changes are saved, you will be taken
back to the updates and migrations page. Under the Status
section, drop down the status option and click View
synchronization logs to see the status of the
synchronization. The status will change from Pending to
In Progress to Completed. Once it's done, you will see a
number of total contacts that have been synced. As shown
in the reference below.
Step 7 To verify the contacts that are synced, on the left side page
go to Management > Users. On the Users page, select the
Contacts option. It should list the same number of users
that are synced in the step
o b a

Let's use the custom filter to sync contacts in the entire organization and who report to manager Taylor Bard.
The contacts are already added in Active Directory, so you have to just update the filters on Control Hub, as
described here.

36
SUMMARY STEPS
1. Continuing on Workstation1 (as dcloud\cholland and dCloud123!), go back to the browser tab where
you have Cisco Webex Control Hub open. If logged out, log in with cholland@cbXXX.dc-YY.com
and dCloud123!
2. Under Services, click Updates & Migrations. On the Migrations page, you will find different migration
cards. Click Get Started for User/contact Synchronization (you may have to scroll down to see this
card).
3. On the User/Contact Synchronization page, click the Prerequisite drop down and choose Go to settings.
4. On the Settings page, configure the following for the LDAP Server:
5. Once the configuration changes are saved, you will be taken back to the Updates and Migrations page.
There you will see a new Status section. Drop down the Status option and click View synchronization
logs to see the status of the synchronization and number of total contacts that have been synced.
6. To verify the contacts that are synced, on the left side of the page, go to Management > Users. On the
Users page, select the Contacts option. It should list the same number of users that are synced in the step
above. Now it should show total of five contacts - two from the previous section synchronization and
three from the current synchronization.
DETAILED STEPS

Step 1 Continuing on Workstation1 (as dcloud\cholland and
dCloud123!), go back to the browser tab where you have
Cisco Webex Control Hub open. If logged out, log in with
Step 2 Under Services, click Updates & Migrations. On the
Migrations page, you will find different migration cards.
Click Get Started for User/contact Synchronization (you
may have to scroll down to see this card).
Step 3 On the User/Contact Synchronization page, click the
Prerequisite drop down and choose Go to settings.
Step 4 On the Settings page, configure the following for the LDAP a. Toggle the radio button on for LDAP Periodic sync,
Server: if you have not yet toggled it on already in the method
above.
b. Drop down the option for Cluster configuration. Click
Add Configuration and configure the following. (If
you have already configured the cluster configuration
above, first click Delete configuration and then click
Add Configuration.)
1. Cluster name: drop down and choose
StandAloneCluster - cucm1.dcloud.cisco.com or
keep as is if you have configured it above
2. Configuration: drop down and choose custom filter
3. LDAP System: drop down and choose Microsoft
AD

37

4. Synchronization type: drop down and choose
Contact
5. Custom Filter:
(&(objectClass=contact)(manager=CN=Taylor
Bard,OU=dCloud,DC=dcloud,DC=cisco,DC=com))
6. LDAP Search Base:
DC=dcloud,DC=cisco,DC=com
7. UC Directory Service Profile: drop down and
choose LDAP
8. Click Add.
9. Under the Periodic synchronization, choose the
time to start the synchronization in next two minutes
from the workstation time. Click Save and Proceed
in top-right corner to save all the configurations we
just updated.
Step 5 Once the configuration changes are saved, you will be taken
back to the Updates and Migrations page. There you will
see a new Status section. Drop down the Status option and
click View synchronization logs to see the status of the
synchronization and number of total contacts that have been
synced.

38
Testing Organizational Contacts Migration

Step 6 To verify the contacts that are synced, on the left side of
the page, go to Management > Users. On the Users page,
select the Contacts option. It should list the same number
of users that are synced in the step above. Now it should
show total of five contacts - two from the previous section
synchronization and three from the current synchronization.
Testing Organizational Contacts Migration

SUMMARY STEPS
1. Continuing on WKST1 (as cholland), minimize the browser and go to Webex. Search for the contacts
you synchronized above. You should be able to find them, as shown below.
DETAILED STEPS

Step 1 Continuing on WKST1 (as cholland), minimize the browser
and go to Webex. Search for the contacts you synchronized
above. You should be able to find them, as shown below.
Migrate Personal Contacts to Webex App

Understanding Personal Contacts
Use Control Hub to migrate your end users' Jabber contacts, both directory contacts and custom contacts to
Webex personal contacts. Contact migration to cloud is a one-time import that enables you to search, look
up, call, message, or invite your contacts like Jabber.
End users define Webex Personal Contacts in the Webex app.
Jabber Custom Contacts refer to non-directory contacts who are outside of your organization and contacts
that are stored in the database of Cisco Unified Communications Manager - IM and Presence Service.
Before you start a real-life migration of your users' personal contacts, make sure you meet the following
requirements:
• Get familiar with Control Hub.
Webex Control Hub is the management interface for the Webex platform. For more information, see Get
Started with Webex Control Hub.
• Access Control Hub with full administrator privileges.

39
With full administrator privileges, you can assign one or more roles to any user in your organization.
Ensure to assign a user with administrator privilege so you can migrate the rest of your Jabber custom
contacts. For more information, see Assign Organizational Account Roles in Webex Control Hub.
• Ensure the on-premises applications from where you plan to migrate the personal contacts, such as Cisco
Unified Communications Manager (Unified CM), Unified CM - IM and Presence Service is at version
11.5 or later to use the Control Hub migration wizard.
• Use Bulk Administration to download the end users file from Cisco Unified Communications Manager
(Unified CM) and the contacts file from Unified CM - IM and Presence.
Use the Import/Export menu in the Cisco Unified Communications Manager application to import the
users. See the Import Contacts Using the Bulk Administration for detailed information.
• Ensure your migration task conforms to a maximum of 500 contacts per user and a maximum of 10,000
contacts in a single file. We recommend listing the same type of contacts in a single file.
Step 1 Navigate to the RDP session for WKST3. (Kellie Melby: dcloud\kmelby and dCloud123!
Step 2 Open Cisco Jabber from the desktop and log in with kmelby@dcloud.cisco.com and dCloud123!
Step 3 Make sure you have a few contacts in Jabber so you can validate them being migrated to Webex after migration. You
can add some directory/custom contacts, if you'd like, in addition to existing contacts.
Step 4 You can log out of Jabber and log back in as smauk@dcloud.cisco.com and dCloud123! to verify if Stefan
has some contacts. You can choose to add some contacts for him also for testing purpose.
Step 5 You can repeat Step 4 for any other users in the demo to have some contacts available for them on Jabber before
migration.
Step 6 Switch to WKST1. (Charles Holland: dcloud\cholland and dCloud123!)
Step 7 Open a new browser tab. Navigate to Collaboration Admin Links > Cisco Unified CM IM/Presence Admin. Log
in with administrator and dCloud123!
Step 8 Navigate to Bulk Administration > Contact List > Export Contact List. Click Find. It will list all the users on the
current IM and Presence server.

40
Step 9 Click Next.

Step 10 On the following screen, give a File Name of your choice for the contacts lists file, leave the Job Description as is,
and select the radio button for Run Immediately and click Submit.
Step 11 Do this step ONLY if you have any of your contacts without IM addresses. Go to Bulk Administration > Non-Presence
Contact List. Choose Export Non-Presence Contact. On the export page, give a File Name of your choice and select
the radio button for Run Immediately under Job Description and click Submit. It will export the contacts lists of all
users.

41
Step 12 Go to Bulk Administration > Upload/Download Files and click Find.

Step 13 Look for the file name you chose above. Select the file and download it. It will download the contacts file in .csv format
to the Workstation 1 desktop. If you also exported non-presence contact list, you will download this file separately (one
file after the other, so it won't zip the files).

42
Step 14 Once the files are downloaded, go back to the previous tab where you have the Webex Control Hub page opened. If
timed out, log in again with cholland@cbXXX.dc-YY.com and dCloud123!
Step 15 Go to Services > Updates & Migrations.
Step 16 Click Get Started on the Migrate Personal Contacts to Webex App migration card.
Step 17 Under the Import On-premises Date, click to drop down the option and choose Directory URI IM Address Scheme.
Click Choose a File to upload the contact list exported file (which you performed in the steps above). On the file
explorer, choose the exported file and click Open.
Step 18 Wait until the file is uploaded to Webex.

Step 19 Once the file is uploaded, you will find the contacts information under Import On-premises Data. ((your numbers
may vary from the image below depending on the number of users/contacts you added.) Click Review for Sync.

43
Step 20 If there are any contacts that could not be migrated, they will be listed on the Migrate page.
Step 21 You can click Bulk Edit and download the XLSX file to see/fix the issues. You might need to scroll all they way to
the right to see the Failure reason.
Step 22 For now, we can ignore the issue and click Migrate Contacts on the Migrate page.
Step 23 Enter any Task Name of your choice for this migration. Click Confirm and Migrate.
Step 24 Once the task has been submitted, you can see the status of the task under Updates and Migrations.
Step 25 Once the status shows as Completed, the contacts migration is done. You can download the migration summary report
from the same status indicator row.
Step 26 Switch to WKST3 (dcloud\kmelby & dCloud123!). Quit/close the Cisco Jabber if it is logged in.
Step 27 Open Cisco Webex from the desktop and log in with kmelby@cbXXX.dc-YY.com and dCloud123!
Step 28 Once logged in, click the contacts [ ] on the left-side pane. Observe that your contacts from Jabber have been
migrated. If you had any unresolved warnings/issues during migration, you will see those contacts will not migrate
until you fix them before attempting migration again.

44
Step 29 Go through this step only if you have exported non-presence contacts.
a. Switch back to WKST1 (dcloud\cholland & dCloud123!).
b. Go to the browser tab where you had Webex Control Hub page opened. If logged out, log in with
c. Go to Services > Updates & Migrations. Choose Migrate Personal Contacts to Webex App.
d. As we have uploaded a contacts exported file in the steps above, we need to delete that file before you can upload
a new file for non-presence contacts exported file.
e. Click the three dots towards the right for Import On-premises Data and choose Delete to delete the previously
uploaded file. On the pop-up window, add check marks to agree for both options that the data will be deleted and
click Delete again.
f. Under Import On-premises Data dropdown, choose Directory URI IM Address Scheme. Click Choose a File to
upload the non-presence contact list exported file (in steps above). On the file explorer, choose the exported file
and click Open. (It takes around two minutes to upload the file. Then it will populate the contacts information.)

45
g. Click Review for Sync and verify if there are any warnings or issues. Click Migrate Contacts. On the new pop-up
window, give a Task Name of your choice and click Confirm and Migrate.
h. You can monitor the status of migration on the main Updates & Migrations page like before.

46
CHAPTER 5
Phase 2: Webex Calling
• Configure Local Gateway for PSTN Calling, on page 47
• Configure Premises-Based PSTN, on page 51
• Add a Trunk, on page 52
• Local Gateway Configuration, on page 57
• Local Gateway Certificate Configuration and Verification, on page 60
• Configuring SIP Profile, on page 65
• Migrate Calling from On-Prem UCM to Webex, on page 78
Users in Phase 2
User Name User Password Endpoint Internal Deployment
ID Devices Extension Model
Charles cholland dCloud123! Cisco Jabber 6018 Cloud
Holland
Anita Perez aperez dCloud123! Cisco Jabber 6017 Cloud
Kellie Melby kmelby dCloud123! Cisco Jabber 6050 Cloud
Stefan Mauk smauk dCloud123! Cisco Jabber 6072 Cloud
Configure Local Gateway for PSTN Calling

Module Overview
In this section, we will configure a local gateway for a single customer site to route calls from/to Webex
Calling endpoints and the PSTN SIP Provider without CUCM in the call path. The figure below is applicable
to a single or a multi-site deployment.

47
Configure Local Gateway for PSTN Calling
Pre-Requisites
• ISR 4321, 4331, 4351, 4431, 4451, 4461, CSR 1000v (vCUBE) – (Latest of IOS-XE 16.12 or 17.3)
• Catalyst 8300 series
• ISR 1100 (IOS-XE 16.12+)
Reference:
htps:/www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudColaboration/broadcloud/webexcaling/customers/cisco-webex-caling-configuration-guide/cisco-webex-caling-configuration-guide_chapter_0100.html
Module Objectives
In this module, we will perform the following tasks:
• Register a local gateway to Control Hub

48
Adding a Telephone Number and Assigning to a Location
• Configure a local gateway to route PSTN calls

• We will not be doing any test calls till after the UCM is shut down
Step 1 On Workstation 1, open the Webex Control Hub (https://admin.webex.com). (If not logged in already, use
cholland@cbXXX.dc-YY.com and password dCloudZZZZ!)
Step 2 Navigate to Services > Calling from the left-hand menu.
Step 3 Click Add Numbers (on the Numbers tab).
Step 4 Before we can add numbers, we need to add the PSTN connection type. Under Choose a Location to Add Numbers,
click Edit PSTN.
Step 5 Under Connection Type, choose the Premises-based PSTN card and click Next.
Step 6 Click the Routing Choice drop-down and choose None. Click to add a check mark to confirm the routing changes.
Click Next.
Step 7 Click Add Numbers Now.

49
Step 8 This time the PSTN connection type should be loaded as you set up above (Premises-based PSTN). Click Next.
Step 9 In the Enter phone numbers separated by commas box, add one unique number starting with 417555 and a random
string of four numbers at the end (such as 4175550123. Press Enter/Return on your keyboard. Click Save. Click Close.
Step 10 At the top of the page, click Locations and select the dCloud location.

50
Configure Premises-Based PSTN
Step 11 In the fly-out window, select the drop-down menu for Main Number and choose the fake number you created in the
previous steps. Click Save.
Configure Premises-Based PSTN

Local Gateway
The figure above displays a Webex Calling deployment without any existing IP PBX and is applicable to a
single or a multi-site deployment. For all calls that do not match the customer’s Webex destinations, Webex
sends those calls to the Local Gateway assigned to the site for processing. Local Gateway routes all calls
coming from Webex to the PSTN and vice versa. The PSTN gateway may be a dedicated platform or co-resident
with the Local Gateway (the focus of this Scenario). The dedicated PSTN gateway variant of this deployment
is a preferred option for Webex Calling deployments.
The first task is creating the local gateway in the Control Hub. You will need the information provided after
creation to build your local gateway.
Using Trunks
The benefits of using dialplans, route groups, and trunks are as below:
• It allows load balancing and failovers across trunks to premises (scale, redundancy)
• Communication between cloud connected PSTN users and premises users
• Ability to route calls to different premises PBXs based on:
• E.164s/DIDs
• ESNs (e.g., 8+site code+extension)
• SIP URIs (Webex Calling to PBX only)

51
Add a Trunk
• “Tandem” functionality to route calls between premises PBXs

• Broader range of migration and co-existence scenarios with premises PBXs, including “mixed” sites
with premises users and Webex Calling users
• Better visibility of call routing decisions
Add a Trunk
Option A: Add a Trunk Using PowerShell Script
Configuring the Local Gateway (Automated Method)
If you want to explore the Local Gateway configuration, review commands, or show your customer on how
to configure you can continue to next section (Next section would be existing steps under Add a Trunk).
However, if you are ONLY interested migration scenario and would prefer to have Local Gateway configured
automatically continue with this session.
Step 2 There will be a PowerShell script located on desktop with name Add_Trunk.ps1. Right-click on the file and choose
Edit.
Step 3 The file/script will be open in PowerShell. Click [ ] to run the script.
Note The script will run and add a new trunk (dCloud-GW) to Webex Control Hub using the APIs. While adding
this trunk the Webex Control Hub generates some important information that needs to be added/configured
on the Cube. This script captures that information and automatically updates the gateway configuration
file (LGW_Config.txt) located on the desktop. This way, the file is ready be copied and pasted on to the
Cube and alleviates you from having to manually enter those commands and saves you time.
Step 4 Open the LGW_Config.txt file on the desktop. Scroll down to the sections voice class sip-profiles 200 and voice class
tenant 200. Notice this file is updated with newly added trunk information that is required to configure the cube.

52

53
Step 5 Open Putty
[ ]
from the task bar or desktop. (If you used VPN to connect to dCloud session, you could use your local SSH client as
an alternative.)
Step 6 Double-click the saved Local Gateway session to load the host name or manually enter IP address 198.18.133.226.
Step 7 Log in with admin / dCloud123!
Step 8 Go back to the LGW_Config.txt file you opened before and copy all the information from the file. (Tip: Ctrl + A
to select all and right-click to select Copy). Go to the Putty session and right-click anywhere on the window. This will
load the configuration to the Cube.

54
Step 9 Give around two to three minutes for the Local Gateway/Trunk to become active.
Step 10 Open a Chrome browser (or go back to browser tab where you had Webex Control Hub opened previously). Click the
Webex Links drop-down on the home page and choose Cisco Webex Control Hub.
Step 11 Log in using the credentials cholland@cbXXX.dc-YY.com and dCloudZZZZ! (Your session domain
cbXXX.dc-YY.com is found under your Session Details tab.)
Step 12 Go to Services > Calling and click the Locations tab on Calling page.
Step 13 On the Locations tab, click the location name dCloud. In the fly-out window, select PSTN Connection, which is in
Unassigned stage as shown below.
Step 14 On the next page (Connection Type), choose Premises-based PSTN and click Next.
Step 15 Click the Routing Choice drop-down and choose the newly added trunk dCloud_GW. Add a check mark to confirm
the effects of the change. Click Save.

55
Option B: Add a Trunk Using Manual Steps
Step 16 Click the Call Routing tab. Select the available trunk dCloud_GW. On the fly-out window, click Trunk Info under
Details. Notice that status of the Trunk is Online as shown below.
Option B: Add a Trunk Using Manual Steps

Add a Trunk
Step 1 In Webex Control Hub under Services, click Calling. Click the Call Routing tab.
Note Each location can be assigned a trunk. In the lab, you have one location that you will be configuring a trunk
for that will connect to the local gateway in your dCloud session.
Step 2 Click Add Trunk. Select the dCloud location. For trunk name, enter Hussain. Click Save.
Step 3 After a few moments, information will be displayed on the page. You will need this information to configure the local
gateway. Capture the information now. It is recommended to create the Lab_info.txt document on Workstation 1 and
copy the information there. You will need the Registrar Domain, Trunk Group OTG/DTG, Line/Port, and Outbound
Proxy Address.

56
Local Gateway Configuration
Step 4 Click the X to close out the window after capturing the information.
Step 5 Click the Locations tab, and click the dCloud location.
Step 6 In the flyout window, click Manage.
Step 7 Click the box for Premises-based PSTN. Click Next.
Step 8 Choose the Hussain trunk from the list and check the box to confirm changing the PSTN routing.
Step 9 Click Save.

Now you will configure your local gateway with the information you received in the previous section.

57
Note All the commands can also be found in a file on the desktop of Workstation 1 named LGW_Config.txt. Please
open LGW_Config.txt with Notepad++ or Wordpad.
Step 1 Connect to Workstation 1 and open PuTTY using the icon on the desktop
[ .]
(If you used VPN to connect to the dCloud session, you can also use your local SSH client.)

58
Step 2 Double-click the LocalGateway saved session to SSH to the local gateway at 198.18.133.226.
Step 3 Log in with admin / dCloud123!
Step 4 Before we proceed with the Local Gateway configuration, we need to ensure that a master key must be pre-configured
for the password with the commands shown below before it can be used in the credentials and/or shared secrets. Type 6
passwords are encrypted using AES cipher and user-defined master key. We will use Password123 as our master key.
Configuration
configure terminal
key config-key password-encrypt Password123
password encryption aes
end
Step 5 Using the configuration below, create a dummy PKI Trustpoint and call it dummyTp.
Step 6 Assign the trustpoint as the default signaling trustpoint under sip-ua. The cn-san-validate server is needed to ensure
LGW establishes the connection only if the outbound proxy configured on the tenant 200 (described later) matches with
CN-SAN list received from the server. The crypto trustpoint is needed for TLS to work even though a local client certificate
(i.e. mTLS) is not required for the connection to be set up.
Step 7 Finally disable TLS v1.0 and v1.1 by enabling v1.2 exclusivity and set tcp-retry count to 1000 (5 seconds), as shown
below.
Configuration
configure terminal
crypto pki trustpoint dummyTp
revocation-check crl
exit
sip-ua
crypto signaling default trustpoint dummyTp cn-san-validate server
transport tcp tls v1.2
tcp-retry 1000
end

59
Local Gateway Certificate Configuration and Verification

Step 1 The default trust pool bundle does not include the DigiCert Root CA certificate needed for validating the server-side
certificate during TLS connection establishment to Webex. The trustpool bundle must be updated by downloading the
latest Cisco Trusted Core Root Bundle from http://www.cisco.com/security/pki, as shown below.
Configuration
! Check if the DigiCert Root CA certificate exists
show crypto pki trustpool | include DigiCert
! – If not, update as shown below
configure terminal
crypto pki trustpool import clean url http://www.cisco.com/security/pki/trs/ios_core.p7b
end
! Verify
show crypto pki trustpool | include DigiCert

60
Step 2 Enter the following commands to turn on the Local Gateway/CUBE application on the platform.

61
Configuration

62
Configuration
configure terminal
voice service voip
ip address trusted list
ipv4 85.119.56.128 255.255.255.192
ipv4 85.119.57.128 255.255.255.192
ipv4 185.115.196.0 255.255.255.128
ipv4 185.115.197.0 255.255.255.128
ipv4 128.177.14.0 255.255.255.128
ipv4 128.177.36.0 255.255.255.192
ipv4 135.84.169.0 255.255.255.128
ipv4 135.84.170.0 255.255.255.128
ipv4 135.84.171.0 255.255.255.128
ipv4 135.84.172.0 255.255.255.192
ipv4 199.59.64.0 255.255.255.128
ipv4 199.59.65.0 255.255.255.128
ipv4 199.59.66.0 255.255.255.128
ipv4 199.59.67.0 255.255.255.128
ipv4 199.59.70.0 255.255.255.128
ipv4 199.59.71.0 255.255.255.128
ipv4 135.84.172.0 255.255.255.128
ipv4 135.84.173.0 255.255.255.128
ipv4 135.84.174.0 255.255.255.128
ipv4 199.19.197.0 255.255.255.0
ipv4 199.19.199.0 255.255.255.0
ipv4 139.177.64.0 255.255.255.0
ipv4 139.177.65.0 255.255.255.0
ipv4 139.177.66.0 255.255.255.0
ipv4 139.177.67.0 255.255.255.0
ipv4 139.177.68.0 255.255.255.0
ipv4 139.177.69.0 255.255.255.0
ipv4 139.177.70.0 255.255.255.0
ipv4 139.177.71.0 255.255.255.0
ipv4 139.177.72.0 255.255.255.0

63
Configuration
ipv4 139.177.73.0 255.255.255.0
exit
allow-connections sip to sip
media statistics
media bulk-stats
no supplementary-service sip refer
no supplementary-service sip handle-replaces
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
stun
stun flowdata agent-id 1 boot-count 4
stun flowdata shared-secret 0 Password123$
sip
g729 annexb-all
early-offer forced
end
Explanation of Commands above.

ip address trusted list – Toll Fraud Prevention
This is to explicitly enable the source IP addresses of entities from which Local Gateway expects legitimate VoIP calls,
for example, Webex peers, Unified CM nodes, IP PSTN. By default, LGW blocks all incoming VoIP call setups from
IP addresses not in its trusted list. IP Addresses from dial-peers with session target ip or Server Group are trusted by
default and need not be populated here.
IP addresses in this list need to match the IP subnets from the Port Reference section of the Configuration Guide for
Cisco Webex Calling Customers document
(https://help.webex.com/en-us/b2exve/Port-Reference-Information-for-Cisco-Webex-Calling#id_119637). The configuration
on the previous page includes all the existing Webex data centers as of the writing of this document.
media statistics
Enables media monitoring on the LGW.

media bulk-stats
Enables the control plane to poll the data plane for bulk call statistics.
allow-connections sip to sip
Allows this platform to bridge two VoIP SIP call legs. It is disabled by default.
no supplementary-service sip referand no supplementary-service sip handle-replaces
Disables REFER and replaces the Dialog ID in the Replaces header with the peer dialog ID.
fax protocol pass-through g711ulaw
Enables audio codec for fax transport.

64
Configuring SIP Profile
stun
stun flowdata agent-id 1 boot-count 4
stun flowdata shared-secret 0 Password123$
Enables STUN globally. When a call is forwarded back to a Webex user (such as when both the called and calling parties
are Webex subscribers and have the media anchored at the Webex SBC), the media cannot flow to the local gateway as
the pin hole is not opened.
The STUN bindings feature on the local gateway allows locally generated STUN requests to be sent over the negotiated
media path. The shared secret is arbitrary as STUN is only used to open the pinhole in the firewall and allow media
latching to take place in the Webex Access SBC.
STUN password is a pre-requisite for LGW/CUBE to send STUN message out. IOS/IOS-XE-based firewalls can be
configured to check for this password and open pin-holes dynamically (i.e. without explicit in-out rules). But for the
LGW deployment case, the firewall is statically configured to open pin-holes in the outbound direction based on Webex
SBC subnets, so the firewall should just treat this as any inbound UDP packet, which will trigger the pin-hole opening
without explicitly looking at the packet contents.
sip
g729 annexb-all
Allows all variants of G729.

early-offer forced
This command forces the LGW/CUBE to send the SDP information in the initial INVITE message itself instead of waiting
to send the information till it gets an acknowledgement from the neighboring peer.

In this section, we will configure only the SIP profile 200 as shown in the figure below, using only the trunk
group OTG/DTG parameter for rule 20.
Step 1 Configure the following SIP profile required to convert SIPS URIs back to SIP as Webex does not support SIPS URI
in the request/response messages (but needs them for SRV query, for example, _sips._tcp.<outbound-proxy>).
rule 20 modifies the From header to include the Trunk Group OTG/DTG parameter from Control Hub to uniquely
identify a LGW site within an enterprise. In the example below, hussain3350_lgu is used. Make sure you replace the
example with your respective Trunk Group OTG/DTG information.
Note Do not use the example hussain3350_lgu; it is shown for reference in the table below. Use your respective
Trunk Group OTG/DTG information.

65
Local gateway SIP profile Configuration

configure terminal
voice class sip-profiles 200
rule 9 request ANY sip-header SIP-Req-URI modify "sips:(.*)" "sip:\1"
rule 10 request ANY sip-header To modify "<sips:(.*)" "<sip:\1"
rule 11 request ANY sip-header From modify "<sips:" "<sip:\1"
rule 12 request ANY sip-header Contact modify "<sips:(.*)>" "<sip:\1;transport=tls>"
rule 13 response ANY sip-header To modify "<sips:(.*)" "<sip:\1"
rule 14 response ANY sip-header From modify "<sips:(.*)" "<sip:\1"
rule 15 response ANY sip-header Contact modify "<sips:(.*)" "<sip:\1"
rule 20 request ANY sip-header From modify ">" ";otg=hussain3350_lgu>"
rule 30 request ANY sip-header P-Asserted-Identity modify "sips:(.*)" "sip:\1"

66
Step 2 Configure Codec Profile, STUN definition, and SRTP Crypto suite as shown and explained below.
Configuration
voice class codec 99
codec preference 1 g711ulaw
codec preference 2 g711alaw
exit
voice class srtp-crypto 200
crypto 1 AES_CM_128_HMAC_SHA1_80
exit
voice class stun-usage 200
stun usage firewall-traversal flowdata
exit

67
Explanation of commands above:

voice class codec 99
Allows both g711(mu and a-law) codecs for sessions. Will be applied to all the dial-peers.
voice class srtp-crypto 200
Specifies SHA1_80 as the only SRTP cipher-suite that will be offered by LGW/CUBE in the SDP in offer and answer.
Webex only supports SHA1_80. This command will be applied to voice class tenant 200 (discussed later) facing
Webex.
voice class stun-usage 200
Defines STUN usage. Will be applied to all Webex facing (2XX tag) dial-peers to avoid no-way audio when a Unified
CM Phone forwards the call to another Webex phone.
Step 3 Configure voice class tenant 200 as shown below. However, be sure to use the parameters obtained from the Control
Hub as shown in the mapping below and not as displayed under the voice class tenant 200 in this document.
Note Do not use these examples as they are only shown here for reference. Use the configuration gathered earlier
in Control Hub when adding the Local Gateway.
• Registrar Domain: 40462196.cisco-bcld.com
• Trunk Group OTG/DTG: hussain3350_lgu
• Line/Port: Hussain8789_LGU@40462196.cisco-bcld.com
• Outbound Proxy Address: la01.sipconnect-us10.cisco-bcld.com
• Username: Hussain3350_LGU
• Password: bjljJ2VQji
Local gateway tenant configuration: Configuration

68
voice class tenant 200

registrar dns:40462196.cisco-bcld.com scheme sips expires 240 refresh-ratio 50 tcp tls
credentials number Hussain8789_LGU username Hussain3350_LGU password 0 bjljJ2VQji realm BroadWorks
authentication usernameHussain3350_LGU password 0 bjljJ2VQji realm BroadWorks
authentication usernameHussain3350_LGU password 0 bjljJ2VQji realm 40462196.cisco-bcld.com
no remote-party-id
sip-server dns:40462196.cisco-bcld.com
connection-reuse
srtp-crypto 200
session transport tcp tls
url sips
error-passthru
asserted-id pai
bind control source-interface GigabitEthernet1
bind media source-interface GigabitEthernet1
no pass-thru content custom-sdp
sip-profiles 200
outbound-proxy dns:la01.sipconnect-us10.cisco-bcld.com
privacy-policy passthru
Explanation of Commands above:


69
This CUBE multi-tenant feature enables specific global configurations for multiple tenants on SIP trunks that allow
differentiated services for tenants.
registrar dns:40462196.cisco-bcld.com scheme sips expires 240 refresh-ratio 50 tcp tls
Registrar server for the Local Gateway with the registration set to refresh every two minutes (50% of 240 seconds).
credentials number Hussain8789_LGU username Hussain3350_LGU password bjljJ2VQji realm BroadWorks
Credentials for Trunk Registration challenge.

authentication username Hussain3350_LGU password bjljJ2VQji realm BroadWorks
authentication username Hussain3350_LGU password bjljJ2VQji realm 40462196.cisco-bcld.com
Authentication challenge for calls.

no remote-party-id
Disable SIP Remote-Party-ID (RPID) header as Webex supports PAI, which is enabled using CLI asserted-id pai (see
below).
sip-server dns:40462196.cisco-bcld.com
Webex servers.
connection-reuse
To use the same persistent connection for registration and call processing.
srtp-crypto 200
Specifying SHA1_80 defined in voice class srtp-crypto 200.

session transport tcp tls
Setting transport to TLS.

url sips
SRV query has to be SIPS as supported by the access SBC; all other messages will be changed to SIP by sip-profile
200.
error-passthru
SIP error response pass-thru functionality.

asserted-id pai
Turn on PAI processing in LGW/CUBE.

Signaling source interface facing Webex Calling

Media source interface facing Webex Calling

Default command under tenant.

sip-profiles 200
To change SIPS to SIP and modify Line/Port for INVITE and REGISTER messages as defined in voice class sip-profiles
200.
outbound-proxy dns:la01.sipconnect-us90.cisco-bcld.com
Webex Calling Access SBC.

70
privacy-policy passthru
Transparently pass across privacy header values from incoming to the outgoing leg.
Step 4 Next, configure the following voice class tenants.
Local Gateway Voice Class Tenant Configuration

! Voice class tenant 100 will be applied on all OUTBOUND dial-peers facing the IP PSTN
session transport udp
url sip
error-passthru
! Voice class tenant 300 will be applied on all INBOUND dial-peers from the IP PSTN
Step 5 Configure the following voice class URIs for URI-based dialing.
Configuration
! - Defines ITSP’s host IP address
voice class uri 100 sip
host ipv4:198.18.133.3
Step 6 Configure voice class uri 200 as shown.

71
Configuration
! - Defines pattern to uniquely identify a Local gateway site within an Enterprise
voice class uri 200 sip
pattern dtg=XXXXXXXX.lgu
Important Use the parameters obtained from the Control Hub as shown in the mapping below and not as displayed
under the voice class uri 200 in this document.
The pattern defined within voice class uri 200 is configured to match the unique Trunk Group OTG/DTG parameter
obtained from the Control Hub earlier and also defined in rule 20 of the voice class sip-profiles 200.
Note Local Gateway today doesn’t support the underscore “_” in the match pattern. As a workaround, we used
the dot wildcard “.” (match any) to match the underscore “_” within hussain3350_lgu (example displayed
in this document).
Step 7 Configure the following outbound dial-peers shown below.

72
Configuration
! - Outbound dial-peer towards IP PSTN
dial-peer voice 101 voip
description Outgoing dial-peer to IP PSTN
destination-pattern BAD.BAD
session protocol sipv2
session target ipv4:198.18.133.3
voice-class codec 99
voice-class sip tenant 100
dtmf-relay rtp-nte
no vad
! - Outbound dial-peer towards Webex
description Inbound/Outbound Webex Calling
destination-pattern BAD.BAD
session target sip-server
voice-class stun-usage 200
no voice-class sip localhost
dtmf-relay rtp-nte
srtp
no vad

73
Step 8 Configure the following dial-peer groups (DPG).

74
Configuration
! - Defines dial-peer group 100. Outbound dial-peer 101 is the target for any incoming dial-peer invoking dial-peer
group 100. We will apply DPG 100 to
! - incoming dial-peer 200 defined later for Webex Calling --> LGW --> PSTN path
voice class dpg 100
description Incoming WxC(DP200) to IP PSTN(DP101)
dial-peer 101 preference 1
! - Define dial-peer group 200. Outbound dial-peer 201 is the target for any incoming dial-peer invoking dial-peer
group 200. We will apply DPG 200 to
!- incoming dial-peer 100 defined later for the IP PSTN --> LGW --> Webex Calling path.
voice class dpg 200
description Incoming IP PSTN(DP100) to WxC(DP201)
dial-peer 201 preference 1
Step 9 Configure the following inbound dial-peers.

75
Configuration
! - Inbound dial-peer for incoming IP PSTN call legs
description Incoming dial-peer from IP PSTN
destination dpg 200
incoming uri via 100
dtmf-relay rtp-nte
no vad
! - Inbound dial-peer for incoming Webex Calling call legs, with the call destined for IP PSTN
description Inbound/Outbound Webex Calling
max-conn 150
destination dpg 100
incoming uri request 200

76
That completes the local gateway configuration. Now you will save.
Step 10 Type end at the command prompt.

Step 11 To save, type copy run start and press Enter/Return twice.
Step 12 Before testing the configuration, verify the local gateway shows online in Control Hub. Go back to the Control Hub
and log in, if needed (cholland@cbXXX.dc-YY.com / dCloudZZZZ!).
Step 13 Navigate to Services > Calling > Call Routing. Click your trunk defined Hussain. On the fly-out window under
Details click Manage.
Step 14 For Status, it should read Online. After verifying the status, click the X to close the window.
Step 15 Finally, need to set the calling behavior between Webex Calling and on-premises. Go to Services > Calling and select
Service Settings on the Calling page. Scroll down to find Call Routing between Webex Calling and Premises and
choose the radio button for Legacy behavior. Click Save. It says not recommended but, as this is a lab environment,
that is okay.

77
Migrate Calling from On-Prem UCM to Webex
Attention The Migration Card in Webex Control Hub covers both migrating Calling and migrating Enterprise Phones
to multiplatform (MPP) firmware. If you are planning to migrate both calling and phones, continue with this
section.
If you want to skip the Calling migration and just try out the Phone migration (Enterprise to MPP), you can
skip this section and move to the stand-alone section entitled Migrate Enterprise Phones to Multiplatform
(MPP) Firmware.
If you are planning to migrate physical phones (Cisco 88XX or 78XX, etc.) register them with Cisco UCM.
When you connect the phones to the dCloud router, they will auto-register with 12XXXX series extensions.
You can assign those auto-registered phones to a particular user (such as Charles, Anita, etc.) using the
self-provisioning tool. Dial 1111 or press Self Provisioning on auto-registered phone and choose option 1.
Enter the extension number of the user (60XX) that you want to register the phone to and follow the rest of
the prompts. ALTERNATIVELY, there are already a few devices (88XX and 78XX) that have been added
with dummy MAC addresses to Cisco UCM. You can just log in to UCM and update the MAC with your
respective phone and they will be provided. In this lab, we will register physical phones to Charles Holland
and Anita Perez, but you can register the phones to any other user as well.
Migrate Unified CM settings for users, devices, numbers, and locations to Webex Calling platform for a better
user experience and to leverage the enterprise-grade Webex cloud calling, mobility, messaging, and calling
services. The migration automates the firmware license generation, verifies the device eligibility, and assigns
phone numbers to users and devices for Webex calling services.
Prerequisites
Before you start your migration, make sure that you meet the following requirements:
• Access Webex Control Hub as an organization administrator. For more information, see Assign
Organizational Account Roles in Cisco Webex Control Hub.
• Create Webex Locations with PSTN assigned for each Location. For more information, see Configure
Cisco Webex Calling for Your Organization.
• Obtain the BAT/CSV files for the Unified CM users and devices. For more information, see Cisco Unified
Communications Manager Bulk Administration Tool (BAT).
• Ensure phones on Unified CM that you are migrating are using Phone Load version 12.5 or later. For
more information, see Install or Upgrade Cisco IP Phone Firmware.
• Identify any DNs from Unified CM that are mapped to multiple Device Pools in Unified CM. This tool
cannot migrate these DNs. You can use Add and Assign Devices in Bulk for migration.
• Ensure all your end users from Unified CM are provisioned as Webex Users via Cisco Directory Connector
or other means. For more information, see User and Contact Synchronization and Install Cisco Directory
Connector.
Step 2 Open the Chrome browser from the taskbar.

78
Step 3 Click the Collaboration Admin Links drop-down and select Cisco Unified Communications Manager. If you have
configured Single Sign-On using Okta or Azure in a previous scenario, you will use those credentials to login; otherwise,
log in with administrator and dCloud123!
Step 4 Navigate to Bulk Administration > Import/Export > Export. If you are planning to migrate phones too, ensure you
have registered physical phones.
Step 5 Click Select All and give your choice of name for the Tar File Name (for example, UnifiedCM_Data_Export). Scroll
down to the Job Information section and select the radio button for Run Immediately. Click Submit.
Step 6 Cisco Unified CM will start exporting the data. Go to Bulk Administration > Job Scheduler to check the status of
your submitted job in the previous step. It takes around five minutes for the data to be exported. You can click Find to
see a list of all jobs running. It will display all current/past jobs and their status. Please wait for the job status to change
to Completed.
Step 7 Once the job is completed, go to Bulk Administration > Upload/Download Files. Click Find. You will see the
exported data tar file. Click to add a checkmark next to the file and select Download Selected. The file will be
downloaded to the Workstation 1 desktop.

79
Important As part of this Migration of Calling from Cisco UCM to Webex lab, we will shut down the Cisco UCM
in an upcoming step. Before proceeding, please make sure you have exported all UCM data after registering
physical phones to Cisco UCM.
Step 8 Open a new tab on Chrome. Click Cisco Webex Links and choose Cisco Webex Control Hub.
Step 9 Log in with cholland@cbXXX.dc-YY.com and dCloudZZZZ! (Your unique cbXXX.dc-YY.com domain can
be found under the Session Details tab of your dCloud session.)
Step 10 Once logged into Webex Control Hub, go to Services in the left-side pane and choose Migrations.
Step 11 On the Migrations page, find Update to the new Webex. In the Migrate Calling from On-prem UCM to Cisco
Webex Cloud card, select Get Started.
Step 12 Click to drop down Step 1: Review the Prerequisites and give it a quick read. This talks about configuring the PSTN
gateway, which we completed above with the E.164 number assignment, having the tar file generated from UCM,
phone load versions, etc.
Step 13 Minimize Step 1 and click to drop down Step 2 Import Data. Here we will import the data we exported from UCM.
Click Choose a File and choose the file you exported/downloaded in the steps above. Click Open.

80
Step 14 Webex Control Hub will start importing data. Once the import is completed, information will populate. Click Start
New Task to start the migration.
Step 15 On Migrate to Webex Calling, give the task a name of your choice, for example, Migrate_Calling-0920. Click Next.
Step 16 On the Map Unified CM Device Pools to a Webex Calling Location page, click the Webex Calling Loctaion drop-down
option and choose dCloud. Click Next.
Step 17 It will take a minute to process. Once completed, click to add a check mark for dCloud and select the numbers assigned
to a Webex Calling location. Click Next.

81
Step 18 Click Next on the Manage Numbers in Selected Webex Calling Locations page. It will list all users from the UCM and
their extension number. Click Next.
Step 19 Click Next on the Assign Numbers to Webex Users or Workspaces page. If any of the devices is a workspace, such as
a common cubicle or huddle room, you can click the Edit icon (pencil) on the right side of the respective row and
toggle the option for Workspace. We have only users in this lab so we don't have to do this. Also, if you do not want
to migrate any users/devices, you can click the Delete option for that specific row, as shown below. Click Next.

82
Step 20 On the Manage Devices to be Migrated to Webex Calling page, you will see users, extensions, their physical devices
such as IP phones and soft clients, etc. Webex Control Hub will highlight any device that is incompatible with Webex
Calling due to the firmware version, model type, etc., as shown below. The device highlighted in with the color orange
is for informational purpose only; there is no action needed. Click Next.
Step 21 On the Review page summarizes the migration, lists any known issues, etc. Once you look over and verify that
information, click Prepare to Migrate.
Step 22 It will give a warning messaging saying proceeding will exclude records with errors and prepare the rest of the phones
for this Webex Calling migration task. Click Accept and Continue.
Step 23 It will start preparing the migration task and give you status summary. Give a quick read of those steps. Click Done to
close the summary page.
Step 24 It will take you back to the home overview page. Go to Services in the left-side pane and choose Migrations. It lists
the migration task we just created and shows its current status. Wait until the status reads either Ready for Migration
or Ready with Errors. (If errors, you can click on the task and review the error messages. Those error messages are
just for review purposes only and will not alter the migration in this lab. Go back to the Migrations page.) Click Complete
Migration. It opens a new pop-up window with the next steps that required to execute to complete the migration. Read
them and click Download Files.

83
Updating the On-prem Services
It will download files to update phones based on their model. You can ignore the downloaded files and continue to next
step as this is not part of this guide.
This completes the Migration section.
Updating the On-prem Services

As we will be transitioning all users to Webex Calling and all endpoints will be transitioned to cloud registration,
we will update appropriate on-premises infrastructure now that cloud calling is in use. Updates to the
infrastructure include the following steps.
Note As this is the lab environment, we will SSH into CUCM and IMP servers to issue shutdown command. Or
you can click on your dCloud session page and shutdown the CUCM and IMP from Servers tab.
Step 1 If not already open from earlier, log in to WKST1. Open PuTTY sessions to cucm1.dcloud.cisco. Log in using
administrator / dCloud123!
Step 2 Issue the following command to shut down the CUCM server: Utils system shutdown. You will be prompted Do you
really want to shutdown? Type Yes and press Enter/Return.

84
Updating the DNS SRV Records - Information Only
Step 3 Open a new PuTTY session to cup1.dcloud.cisco. Log in using administrator / dCloud123!
Step 4 Issue the following command to shut down the IMP server: Utils system shutdown. You will be prompted Do you
really want to shutdown? Type Yes and press Enter/Return.
Updating the DNS SRV Records - Information Only
Important This section is for information only. As this is the lab environment, we will not be deleting any SRV records.
Do no perform these steps.
Step 1 (Information Only) Remove on-premises call control and messaging DNS SRV records from the on-premises DNS
server(s) including cisco_uds._tcp.<domain>, cup_login._tcp.<domain>. These SRV records are no longer required for
Webex Teams client service discovery.
Step 2 (Information Only) Remove edge-related DNS SRV records from the public DNS system including
collab_edge._tls.<domain>. These SRV records are no longer required for client service discovery of collaboration edge
services.

85
Sign into Webex after Migration
Sign into Webex after Migration

We can now use Webex to log in for all of our users in the org. We can also make and receive calls between
those users.
Step 1 At this stage, we can log in into Webex on our personal devices or can use workstations provided in the demo. Please
sign out of all Jabber clients.
Step 2 If using a workstation in this demo, open Webex on WKST1 and log in as cholland@cbXXX.dc-YY.com and
dCloud123!
Step 3 Open RDP connection to WKST2 (as dcloud\aperez dCloud123!) if not already logged in.
Step 4 Open Webex on WKST2. Log in as aperez@cbXXX.dc-YY.com and dCloudZZZZ!
Now that you have the clients installed and logged in, you are able to send messages between users, set Presence status,
and make internal calls. You can see users using the Webex Calling service by clicking the user image and selecting
Phone Service.
Note If you have any issues with phone services for Charles Holland (on WKST1), try logging into Webex as
Taylor Bard (tbard@cbXXX.dc-YY.com/dCloudZZZZ!)
Test PSTN Calls via Local Gateway for Migrated Users

Prior to testing PSTN calls via the local gateway for the newly migrated users, the following change needs
to be done to allow PSTN calling in this lab environment.

86
Test PSTN Calls via Local Gateway for Migrated Users
Note As this is the lab environment make sure at this stage your CUCM and IMP servers are shut down. Don't
proceed with the steps below if your CUCM or IMP servers are still shutting down.
Step 1 If using a workstation in this demo, go to https://198.18.133.5 (advance through security warnings). Enter admin as
username and dCloud123! as the password. Click LOGIN NOW.
Step 2 Go to Configuration > Interface and click Ethernet.
Step 3 Select GigabitEthernet1.
Step 4 Under Configure Interface GigabitEthernet1, click Port Configuration. Change the IP Address* to 198.18.133.3
and click Update & Apply to Device.

87
Test Calls – Inbound from PSTN to Webex
Once you see a configuration successfully applied notification, you can test PSTN calls for the migrated user the same
way you dialed/tested PSTN calling using Jabber.
Step 5 Open Webex on WKST1, which should already be logged in as cholland@cbXXX.dc-YY.com. Recall from earlier
modules that this user was setup to use Jabber for PSTN calls prior to migration. We will now place calls to and receive
calls from PSTN for this user using Webex (registered to Webex Calling) and via the local gateway as the PSTN option.
Test Calls – Inbound from PSTN to Webex

Procedure

Step 1 To make inbound PSTN calls to your pod’s phones, find
your information in your dCloud session Details page or
in the text document found on the desktop of Workstation
1 named DN_to_DID.txt. (Those DID numbers can be
dialed from your mobile number.)
Step 2 With the DID number, dial one of your users (that are
logged into Webex) using a real cell or desk phone.
Step 3 Answer the call on Webex. Verify the call is successfully The call flow in dCloud is as follows:
connected and hang up after few seconds.
a. Incoming DID goes into dCloud.

88
Testing Calls – Inbound from PSTN to Webex

b. Platform gateways translate that DID into a four-digit
extension (6XXX or 7XXX).
c. Call is routed through the local gateway to the extension
of the user.
Testing Calls – Inbound from PSTN to Webex
Step 1 For dialing inbound PSTN calls to your pod’s phones, information can be found in your dCloud session details page or
in a text document found on the desktop of Workstation 1 named DN_to_DID.txt.
Step 2 Those DID can be dialed from your mobile numbers.
Step 3 With the DID number, dial one of your users (that are logged into Webex) using a real cell or desk phone.
Step 4 Answer the call on Webex.
Step 5 The call flow in dCloud is as follows:
a) Incoming DID comes into dCloud.
b) Platform gateways translate that DID into a four digit extension (6XXX or 7XXX).
c) Call is routed through the local gateway to the extension of the user.

In dCloud, national calls are allowed to the datacenter region your session is located in. US West/East
datacenters are dc-05 or dc-01. EMEAR datacenter is dc-03. APJ datacenter is dc-02.
In the US datacenters you should be able to call any national number. Remember since the location is built
for the United States, Webex will add a +1 to any dialed number if needed. So a 10 digit number can be called
or a 1 + 10 digit number.
Dialing from an EMEAR or APJ session will be just a little different than US. Every session, no matter the
datacenter, the Webex Calling location is built for United States. Because of this, in the lab, dialing a national
number for the UK (EMEAR) or Singapore (APJ) requires you to dial a 00 + Country Code and then the
number (10 digit for UK and 8 digit for Singapore). For the EMEAR datacenter the country code is 44. For
the APJ datacenter the country code is 65.
When you dial 00 and the number, Webex Calling will route the number as is and not add +1. Then the call
flow for EMEAR and APJ sessions is as follows:
• Call comes into Local Gateway, sent to dCloud Gateway, which delivers it to the IP PSTN.
• The dCloud GW will strip the 00 off the number and add a plus (+) or localize it.
• The +E.164 or the localized number is now routed by the IP PSTN and rings the PSTN number.
Step 1 With the dialing explanation above, dial a PSTN number.

89
Step 2 Answer the call.

90

B Migration Lab Short Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B Migration Lab Short Guide

Uploaded by

Copyright:

Available Formats

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab

CHAPTER 2 Getting Started 9

About This Lab 9

CHAPTER 3 Phase 0: Unified CM Calling 17

Mapping the Transition: Phase 0 – Unified CM Calling 17

Validate PSTN Dialing – Optional Module 18

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Testing Calls – Outbound to PSTN 19

CHAPTER 4 Phase 1: Hybrid Services 21

Mapping the Transition: Phase 1 – Hybrid Services 21

CHAPTER 5 Phase 2: Webex Calling 47

Configure Local Gateway for PSTN Calling 47

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Local Gateway Certificate Configuration and Verification 60

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

About This Lab

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

About This Solution

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Note More information can be found at https://www.cisco.com/go/ct

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Pre-Transition Steps and Consideration

Pre-Transition Consideration Summary

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Pre-Transition Consideration Summary

Core Components Overview

Webex by Cisco Overview

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Accelerate Teamwork with These Tools

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Webex Hybrid Services

Available Hybrid Services

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Webex Calling Overview

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

About This Lab

Topology and Equipment Details

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Name Description Host Name (FQDN) IP Address Username Password

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

User Name User Password Endpoint Internal Deployment Model

Charles Holland cholland dCloud123! Jabber 6018 OnPrem /Hybrid

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

User Name User Password Endpoint Internal Deployment Model

Kellie Melby kmelby dCloud123! Jabber 6050 OnPrem /Hybrid

Stefan Mauk Smauk dCloud123! Jabber 6072 OnPrem /Hybrid

Rebekah rbarretta dCloud123! Jabber 6088 OnPrem /Hybrid

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Creating Agent Install File

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

• Replace ZZZZ with your dCloud Session ID number.

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Mapping the Transition: Phase 0 – Unified CM Calling

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Validate PSTN Dialing – Optional Module

Testing Calls – Inbound from PSTN to Jabber Users

Brief Lab Guide: Migrating On-Premises Calling to Cisco Webex Lab v3

Testing Calls – Outbound to PSTN

Step 1 With the dialing explanation above, dial a PSTN number.