Cisco Webex Enablement Lab v5

Lab Guide
Cisco dCloud
Cisco Webex Enablement Lab v5
Last Updated: first update on 02-MARCH-2020
About This Lab

This guide for the preconfigured lab includes:
About This Lab
Requirements
About This Solution
Topology
Session Users
Get Started
Scenario 1. Initial Lab Overview and Setup
Scenario 2. Room Device and Feature Configuration
Scenario 3. Webex Hybrid Calendar Service (Quick Setup)
Scenario 4. Webex Edge for Devices
Scenario 5. Webex Edge Audio
Scenario 6. Webex Video Mesh
Scenario 7. Webex Calling
Scenario 8. O365 Integrations to Webex Teams
Scenario 9. Webex Hybrid Message Service Configuration
Scenario 10. Jabber Team Messaging Mode
Scenario 11. Webex Teams Client Features
© 2020 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 188
Lab Guide
Cisco dCloud
Scenario 12. Webex Meeting Troubleshooting
Scenario 13. Pro Pack for Cisco Webex Control Hub
Scenario 14. The Webex Board
Scenario 15. Webex Hybrid Call for Webex Devices
Scenario 16. Single Sign-On (SSO)
Appendix A. Cisco Webex Password Reset Procedures
Appendix B. Creating and Confirming an Application User
Appendix C. Directory Connector Configuration
Appendix D. Full Local Gateway Configuration
Appendix E. Webex Hybrid Calendar Service Full Configuration
Lab Guide
Cisco dCloud
Limitations/Disclaimer
To meet the specified requirements of this lab, these scenarios are intended to demonstrate one way to configure Cisco® Webex
Control Hub solutions. There are various ways that 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.
Customization Options
There are no customizable options associated with this lab.
Requirements
Table 1 outlines the requirements for this preconfigured demonstration.
Requirements
Required Optional
Cisco AnyConnect® client None
Laptop
Cisco Multiplatform Phone (MPP) for Webex Calling;

alternatively can use desktop or mobile calling clients
For room devices, you need one of the following:
Cisco Webex DX/Board/Room Kit
About This Solution

Cisco Webex® can be broken down into different services: Video Conferencing (Webex® Meetings), Team Collaboration (Webex
Teams™), Cloud Calling (Webex Calling).
Cisco Webex Meetings Overview
Although the digital age has made it easier to connect across borders without the cost and hassle of travel, the human connection is
still critical. Video has saturated every corner of our daily interactions, from social media to personal calls with friends and family.
Strong businesses start with strong relationships. And strong relationships are forged on a foundation of strong communication.
That’s why Cisco Webex Meetings puts video at the forefront of communication and collaboration to empower over 130 million
people to put their best face forward.
With Cisco Webex Meetings, we’re making it easier than ever for everyone to be seen, be heard, and work together effectively, even
when they are miles apart. Anyone can join a meeting from inside or outside the organization, using mobile, desktop, video room
devices (even a third-party device), or their browser. Everyone can enjoy consistent, easy meeting experiences and be fully engaged
in the meeting, without technical complexity. Organizations need to implement solutions that remove the complexity of the video
Lab Guide
Cisco dCloud
meeting experience—with crystal-clear audio and content sharing in the same meeting. For more effective, secure, and reliable
meetings, use Cisco Webex.
Benefits of Cisco Webex Meetings include:
• Simple video-first experiences from any device
o Engage in video-first meetings, with integrated voice and content sharing, to collaborate more effectively with
customers, partners, and employees without the need to travel
o Experience lifelike meetings by combining Cisco’s award-winning video room devices with Webex Meetings
o Or join from any third-party video device – even Microsoft Skype for Business
o Easily call back to your meeting using video system proximity detection
• Best mobile experience on the market
• Simple joining and scheduling
o No downloads and plug-ins required. Easily join your meeting with the Webex web app for the industry’s best
browser experience, with full meeting functionality on all major browsers
o One consistent join experience across all devices—just tap the big green button
o Join and host easily from any device—desktop, mobile, video, or browser—with no downloads or plug-ins
required
o Just add @webex for the simplest scheduling experience on the market today—even on mobile devices
• Integrated into the tools you use most
• Delivered on a secure, scalable global platform for an uncompromised experience

o Take the worry out of your meeting with multilayer security based on Cisco’s industry-leading expertise
without compromising the user experience
o Integrated audio
o Dedicated solutions for specialty meetings such as events, training, and remote support
Cisco Webex Teams 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 Cisco Webex.
Cisco Webex Teams is an easy-to-use collaboration solution that keeps people and teamwork connected anytime, anywhere. With
the Webex Teams app, you create secure virtual work spaces 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
Lab Guide
Cisco dCloud
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
Teams 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 Teams. 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
Teams has a continuous delivery 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 Cisco Webex Teams capabilities to the next level with Cisco 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
Cisco 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 Teams. Use integrations to
streamline work flows and bots to automate actions. Visit the Webex App Hub to explore.
Lab Guide
Cisco dCloud
Cisco Webex Hybrid Services
Increase the benefits of your on-prem unified communications and collaboration investment with Cisco Webex Hybrid Services. They
simplify connecting your existing network resources and on-premises unified communications services to the Cisco Webex Teams
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 Cisco Webex Hybrid Services. These services connect what you have on premises with Cisco Webex
Teams in the cloud to provide a single integrated experience. If you like the capabilities of Webex Teams, 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 Cisco
Webex Teams and Cisco Webex Meetings capabilities. Hybrid Calendar Service easily and automatically creates a Cisco Webex
Teams workspace when scheduling meetings. For example, adding the phrase "@meet" to the meeting invitation’s location field will
automatically create a Cisco Webex Teams workspace and populate the meeting join information in the meeting invitation. If no
workspace is needed, adding the phrase “@webex” to the invite’s location field automatically populates the meeting join
information. Hybrid Calendar Service also allows Cisco Webex users to press a single button to join almost any upcoming meeting
within the app itself and on a video device.
Lab Guide
Cisco dCloud
Hybrid Directory Service: This service connects Active Directory to Cisco Webex Teams and enables a user to see all company
contacts in the Cisco Webex Teams app so that they can click to meet, message, or call. It also provides user synchronization
between Microsoft Active Directory and Cisco Webex user management. Hybrid Directory Service simplifies the administrative
experience by automatically synchronizing Microsoft Active Directory users with Cisco Webex (creating, updating, deleting) so that
users are always current in Cisco Webex Teams.
Cisco Webex Video Mesh: This revolutionary capability removes the deployment decision of premises versus cloud for Cisco Webex
video meetings. It places our Cisco 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 Cisco Webex Teams, your data is private. This includes all content, messages, and files—even
your whiteboard drawings.
Hybrid Call Service for Cisco Webex devices: This service is ideal for organizations that want to consume a mixture of Premise and
Cloud registered endpoints as it offers maximum flexibility to your users.
You can use Hybrid Call Service to provide hybrid call functionality for room, desk, and Cisco Webex Board devices that are added to
Cisco Webex Places. Cisco Webex devices are registered to the cloud, and when they are enabled with Hybrid Call Service, they also
connect to the enterprise. Cisco Webex devices in the Place become a part of your existing on-premises dial plan, allowing these
devices to call user extensions or the PSTN, and receive incoming calls.
This capability enables a seamless transition between Premise registered and Cloud registered devices for your end users.
Cisco 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. Cisco 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 both the Cisco Webex Calling app, for mobile and desktop users, integrated with the
Cisco Webex Teams collaboration app
• Support for an integrated user experience with Cisco 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
Lab Guide
Cisco dCloud
Topology
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.
dCloud Topology
Lab Guide
Cisco dCloud
Equipment Details
Name Description Host Name (FQDN) IP Address Username Password

CUCM1 Cisco Unified Communications Manager 12.5 cucm1.dcloud.cisco.com 198.18.133.3 administrator dCloud123!
IM & P IM & Presence 12.5 cup1.dcloud.cisco.com 198.18.133.4 administrator dCloud123!
Exp-C Expressway-C (Core) X12.5 vcsc.dcloud.cisco.com 198.18.133.152 admin dCloud123!
Exp-E Expressway-E (Edge) X12.5 vcse.cbXXX.dc-YY.com Public IP (see admin dCloud123!

session details)
Exp-Base Expressway-C Connector Host X12.5 exp-cc.dcloud.cisco.com 198.18.133.223 admin dCloud123!
ESXi Host VMware ESXi 6.5 Host esxi1.dcloud.cisco.com 198.18.134.27 root dCloud123!
Webex-VMN Cisco Webex Video Mesh Node vmn1.dcloud.cisco.com 198.18.135.21 admin dCloud123!
Local Gateway CSR1000V N/A 198.18.133.226 admin dCloud123!
AD1 Active Directory, DNS, AD FS ad1.dcloud.cisco.com 198.18.133.1 administrator dCloud123!
Exchange Microsoft Exchange 2016 mail1.dcloud.cisco.com 198.18.133.2 administrator dCloud123!
Workstation 1 Windows 10 wkst1.dcloud.cisco.com 198.18.1.36 cholland dCloud123!
Workstation 2 Windows 10 wkst2.dcloud.cisco.com 198.18.1.37 aperez dCloud123!
Workstation 3 Windows 10 wskt3.dcloud.cisco.com 198.18.1.38 kmelby dCloud123!
Session Users
Table 3 contains details on preconfigured users available for your session.
User Details
Deployment
User Name User ID Password Endpoint Devices Internal Extension Model
Charles Holland cholland dCloud123! Cisco Jabber/Teams 6018 Hybrid
Anita Perez aperez dCloud123! Cisco Jabber/Teams 6017 Hybrid
Kellie Melby kmelby dCloud123! Cisco Jabber/Teams 6050 Hybrid
Rebekah Melby kmelby dCloud123! Cisco Calling App or MPP 86022 Cloud
Taylor Bard tbard dCloud123! Teams/Cisco Calling App or MPP 86021 Cloud
Lab Guide
Cisco dCloud
Get Started
BEFORE PRESENTING
Cisco dCloud strongly recommends that you perform the tasks in this document with an active session before presenting
in front of a live audience. This will allow you to become familiar with the structure of the document and content.
It may be necessary to schedule a new session after following this guide in order to reset the environment to its original
configuration.
PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION
Follow the steps to schedule a session of the content and configure your presentation environment.
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.
2. Click View to open the active session. (Skip if you are in a proctored environment.)
3. If you are connecting directly to the session from a stand-alone laptop or other device, install and access Cisco AnyConnect on
your laptop, using the AnyConnect credentials in the Cisco dCloud UI. [Show Me How]
• Recommended method: Use Cisco AnyConnect [Show Me How] and local laptop RDP client.
• Windows Users: It is recommended to use some version of Remote Desktop Manager to save the connections to each
virtual machine. An example of a manager is Microsoft’s Remote Desktop Connection Manager, which can be found at
https://www.microsoft.com/en-us/download/details.aspx?id=44989.
• Mac Users: It is recommended to use the Microsoft Remote Desktop (MRD) [ ] or CoRD [ ] applications to
connect to the virtual machines. MRD can be downloaded for free from the Mac App Store. CoRD can be downloaded free
at http://cord.sourceforge.net/. Each application gives you the capability to save the connections for each virtual machine. DO
NOT use the Microsoft remote desktop client that comes with your Mac. It will have security issues connecting to the
AD1 and Mail1 virtual machines.
4. The lab requires desk phones to be loaded with Multiplatform Phone (MPP) firmware.
5. The room devices (DX / Room Kit / Webex Board) 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 use http://upgrade.cisco.com/ to help in the upgrade
process.
6. After confirming the devices have the correct firmware and are not in a factory reset state, then 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.
Lab Guide
Cisco dCloud
7. To demonstrate Cisco Webex hybrid services, Cisco Jabber 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.
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. 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.
Session Details Tab Example
Lab Guide
Cisco dCloud
Scenario 1. Initial Lab Overview and Setup

This scenario will get you familiar with the base lab setup as well as cover a few initial tasks that need to be completed for later in
the lab. The Webex trial has already been started for you. Also Charles Holland, the customer organization administrator, has his
password already set to dCloud123! The steps to create a customer trial can be found at
https://collaborationhelp.cisco.com/article/en-us/npv2y12.
The users that will be used in the lab have also been configured and passwords set to dCloud123! This will help you focus deeper on
other topics rather than activating accounts and setting passwords. In a blank organization, you would create users by adding one by
one, importing a CSV file, using the directory connector, or a combination of all three. The steps to using directory connector for
importing users from Microsoft Active Directory can be found in Appendix C. Even though the users have already been configured,
you can still go through the directory connector steps if you want to learn how it is completed.
Steps
You will now verify the initial automation scripts ran properly to create your trial and set Charles’ password.
1. If not already connected, use Cisco AnyConnect to VPN into your lab session. The login credentials will be provided by your
proctor or displayed on the Session Details tab for your active session.
2. Create an RDP connection to Workstation 1 (198.18.1.36) and log in as dcloud\cholland with password dCloud123!
Ignore/accept any security warnings.
3. Open Microsoft Outlook using the icon in the taskbar [ ].
4. For profile name, enter Charles and click OK.
New Profile
5. In the Inbox, you should see an email with the subject line Welcome to Cisco Webex Trial and possibly one that has the subject
of Your password was updated. If you see any with the subject WEBEX LAB WARNING, read the email to see if there were any
issues with the spin up of the lab.
6. If you plan to go through the Office 365 scenario, find the email that has the subject CLOUD TRIALS EMAIL ADDRESS and
capture the email address that begins with trial. When creating the Office 365 trial, this will ensure a unique email address is
used. This email address will route to Charles Holland’s email box.
6. Open Chrome web browser to https://admin.webex.com and enter cholland@cbXXX.dc-YY.com. Click Sign In.
7. Enter dCloud123! as the password and click Sign In again.
Lab Guide
Cisco dCloud
8. Click Accept if prompted for Terms of Service.
9. You have now logged into the Cisco Webex Control Hub. This is where you will spend the bulk of your time configuring your
organization. This portal is where you will configure your Webex services. The first page is the Overview. This gives you a quick
look at all the services you have available and their statuses. You will also see some notification messages to keep you updated
with important information.
Auto-Assign User Licenses
In the Control Hub you have the ability to auto-assign user licenses to every new user. You do this by creating an auto-assign
template.
1. In the Control Hub, navigate to Users > Manage Users. Note that you have eight preconfigured users in the user list.
2. In the Licenses section, click Set up Auto-Assign Template.
3. In the Messaging column, check the box next to Webex Teams.
4. In the Meeting column, check all the boxes.
5. As you can see, you can assign other licenses on this page. For now, just assign the licenses mentioned above.
6. Click Next and then Save.
7. Click Manage Users again.
8. The Licenses section shows Activated.
9. Click the ellipsis [ ]. Here you can modify, deactivate, or delete the existing template. Leave the settings as is.
10. Close the Manage Users window.
Covert Users
If you want to manage users that signed up for Webex services using your organization's email domain, then you can claim those
users into your organization. Once you've claimed a user, you can assign licenses to them.
When you claim a user account, you can choose to immediately claim the user into your organization. Users that are immediately
claimed into your organization are moved right away. The user receives an email with a link to a sign in page where they have the
following options on how they would like to proceed with their old account:
• Change the email address associated with the old account
• Delete the old account and contents
If you delay the user claim, the user will have 14 days to decide what to do with the old account. If the user signed up for a Webex
Teams account, then the user can migrate their Webex Teams conversations from their old account to their new account. If they
don’t make a decision in 14 days, then the user is moved automatically. Webex Teams conversations are also moved automatically if
no decision is made in 14 days.
Lab Guide
Cisco dCloud
When you delay a user claim, the user is sent an email with a link to a sign in page with the following options:
• Change the email address associated with the old account.
• Transfer Webex Teams conversations from the old account to the new account.
• Delete the old account and contents.
Before you get the option to convert users, you must verify or claim the domain. This has been completed for you already. The steps
can be found here.
1. Navigate to the Overview page.
2. On the Onboarding card you should see at least two Potential new users. These are users that have signed into Webex Teams at
some point. You have the option to convert them over into your new customer organization.
3. Click the Review link. (You can also find this page on Users > Manage Users > Convert Users.)
4. On the new window you should see at least two users in the Potential Conversion list (if your RDP window size is small, you may
not be able to see the users on the screen). Leave the check boxes next to them checked.
5. Check the box next to Allow users to bring their Webex Teams conversations with them to allow the users to bring over their
previous conversations.
6. Click Next.
7. Because you created an auto-assign template, these new users will automatically be assigned those services you chose earlier.
Click Save and then Finish.
8. You will be brought to the Users page to verify the users have been added.
User Pre-Configuration Verification
As mentioned earlier, the base configuration of the lab has users preconfigured. These users also have the Webex Teams and Webex
Team Meetings services configured.
1. Select a user from the user list.
2. On the fly out window you will get an overview of what services the user has. Click Edit.
3. In the next pop up window, you will see at least two services configured for each user—Webex Teams and Webex Team
Meetings. Later in the lab you will configure different users for other services. For now, click Cancel.
4. On this page you will also notice you can configure a number of hybrid services for each user, which will be completed in
another scenario.
5. Click Administrator Roles.
6. Here you can allow a user access into Control Hub and give them full access or give them limited access.
Lab Guide
Cisco dCloud
Verify Charles has Webex Meetings with a Personal Room
Charles uses his Webex Meetings personal room throughout the lab so while you are in the Control Hub go ahead and verify Charles
has Webex Meetings configured as well as setup for a personal room.
1. Select Charles from the users list.
2. Under Charles services, click Meeting and then click the meeting site URL.
3. Scroll down and click User Privileges.

4. Verify Personal Room and Join meetings from video systems are checked. If either are not checked, check them now and click
Save.
Control Hub Timeout
To make things easier in the lab you can now set a time out of the login to Control Hub as well as the Webex Teams web client. The
default login timeout for Control Hub is 20 minutes. For lab purposes, you will set it for No timeout so it limits the amount of times
you have to log in.
1. Navigate to Settings and scroll down the page to Idle Timeouts.

2. Under the Webex Control Idle Timeout section, change the Control Hub timeout drop-down menu to No Timeout. For
production, your security team may take issue with having no timeout configured. Follow your organization’s security guidelines
when setting this parameter.
O365 Pre-Configuration (Optional)
Later in the lab, you will create integrations with Microsoft O365. To complete the integration, you will need to have your own O365
site. If you do not have a site, you can create an O365 trial very quickly. The O365 trial creation processes will take some time
(upward of ~60 minutes) to fully configure so it is highly recommended to start the O365 trial now so all the processes will be
completed by the time you reach the scenario. If you plan on going through the integration of O365, it can take some time. Go to
Scenario 8 now and complete the Initial Integration of O365 to Webex Teams section and then return to Scenario 2 below. If you do
not plan on going through the O365 integration scenario then you can continue on with the lab.
Lab Guide
Cisco dCloud
Scenario 2. Room Device and Feature Configuration

In this scenario, you will register the room device (DX/SX/Room Kit/Room 55-70/MX/Webex Board) and also turn on Facial
Recognition and Webex Assistant for the organization.
Configuring Organization Device Features
9. In this section, you will configure the Facial Recognition and Webex Assistant features for your organization.
1. Go back to your browser window, which should be logged into the Cisco Webex Control Hub (https://admin.webex.com).
2. Click the Settings tab.
3. Scroll down to the Facial Recognition section and click Review Setting.
4. On the next pop up window, click Turn On Name Labels.
5. Users have to opt-in to the service before it will start working. Navigate to https://settings.webex.com/main/profile/name-
label/enroll with a computer or mobile device with a camera.
6. Sign in as Taylor Bard tbard@cbXXX.dc-YY.com / dCloud123!
7. Once logged in, click Get started.
8. Allow access to your camera, if prompted. Follow instructions and click Take photo.
9. Once photo is taken, click Done.
10. Go back to the Control Hub.
11. On the Settings page, scroll down to the Cisco Webex Assistant section and check the box to enable.
10. Now the Webex Assistant is enabled for all supported devices in the organization. The list of supported devices and usage
instructions can be found here. Users can turn on/off the Webex Assistant on each device individually via the Settings menu.
Adding a Room Device
1. Navigate to Devices.
2. Click Add Device.
3. Choose Place and then click Next.
4. Choose New Place. In the box that appears, enter a place name.
5. Click Next.
6. Choose Other Cisco Webex device and then click Next.

7. Keep Free Calling selected and click Next.
The next screen will show a 16-digit code to put into your DX/SX/Room Kit/Room 55-70/MX/Webex Board, which you will use in the
next steps. The following instructions start from a factory reset condition, which is recommended for this lab.
8. On the Welcome screen of the room device, tap Start.
Lab Guide
Cisco dCloud
9. On the network screen, tap the blue right arrow.
10. On the Choose a call service screen, tap Cisco Webex.
11. Enter the 16-digit code provided by the management portal and tap the blue right arrow. Continue through the rest of the
setup until you reach the home screen.
12. Go back to the management portal and click the [ ].

The room device should be registered to Cisco Webex. You can now see it listed online on the Devices page on the Cisco Webex
Control Hub (may need to refresh page).
Adding Devices in Bulk
11. You also have the ability to add devices in bulk from the Control Hub.
2. Click Import/Upload CSV file.
3. On the next pop-up window, click download CSV template.
4. Open the CSV file and you will see the format of what is needed to add devices in bulk.
5. In production, you would fill out the CSV file and use the import function to add the devices. You won’t need to import in the lab
since you have a small amount of devices. Click Cancel.
Administering a Room Device
Sometimes you might need to change the settings on a room device, such as turning down the ultrasound volume to help with
pairing with multiple devices in a room. The Cisco Webex management portal makes it easy to update room device settings. There
are two ways to remotely configure the device—from the Control Hub or on the device web portal directly.
1. On the Devices page, select the device you added in the previous section.
2. Scroll down the fly-out window to the Configurations section and click the link next to Advanced Configurations (Access XXX
Configurations). In this window, you are able to configure a number of device configurations without needing direct network
access.
3. Search for ultra and click the Audio > Ultrasound > MaxVolume > option that appears.
4. Use the slider to take the volume down to 20 and then click Apply.
NOTE: In training environments with multiple room devices, you might need to turn the volume down even lower to
prevent pairing with the person’s device next to you. Once you turn the volume down lower, you will need to hold your
mobile close to the room device to pair.
5. Click the [ ].
6. Feel free to look through the other configuration options that are available. When finished, click Close.
You can also access the Devices Admin page directly if you have network access to the device from your computer.
Lab Guide
Cisco dCloud
NOTE: In order to complete this section, you need to make sure your computer and room device are on the same network
or make sure the room device can be reached over the network from your computer. You should be able to access it if
you are on the same network and connected with AnyConnect to dCloud because of split tunneling. If you can’t reach
your device, you may need to disconnect from AnyConnect. You WILL NOT be able to reach the room device from the
Workstation 1 or Workstation 2 virtual machines inside the lab.
7. Go back to your own browser window (not Workstation 1 browser inside the lab), which should be logged into the Cisco Webex
Control Hub (https://admin.webex.com).
8. Click the Devices tab.
9. Select the room device you added in the previous section.
10. In the fly-out window, scroll to the bottom of the page and click Launch Web Portal and then Proceed.
11. If the network routing is there to access the device you will come to the System Information page.
12. Feel free to browse around the Management page to see other settings you can configure. Close the tab open to the room
device when you are finished.
Device Branding
The Control Hub allows you, as the Administrator, to set branding on your devices as well as customize messages displayed on the
device.
1. In the Webex Control Hub for your customer, click the Settings tab.
2. Scroll to the Branding section. You have different options that you can change the branding. Click See examples to view the
different options.
3. Once you have read over the different states (Wake-up flow and Awake state), click Done.
4. Select the radio button for Upload your company’s brand visuals for all devices.
5. As you will see the text below the upload boxes give you the recommended sizes for the brand image and logos. You can quickly
complete a Google image search such as 3840X2160 picture or 272x272 image to find a sample brand image or logo to test
with. If you exceed the recommendations, you will get a message that the image was resized. This will take a few minutes to
process.
6. Once you have an image for the background or logo selected, use the boxes to upload your image(s) and click Save and then
Continue.
7. In a few moments, the image should appear on your room device.
Lab Guide
Cisco dCloud
Cisco Webex Teams Mobile App
1. Before you test the functionality of the current setup, take out your iOS or Android device, open the app store, and download
the Cisco Webex Teams app. If you already have Cisco Webex Teams installed, sign out of it.
2. Sign in to Cisco Webex Teams as Taylor Bard (tbard@cbXXX.dc-YY.com) with password dCloud123! Skip through the initial
profile setup screens till you get into the app. Sign in to another client with Kellie Melby (kmelby@cbXXX.dc-YY.com) with
password dCloud123! (See note below if you received an activation message after entering the email address.)
NOTE: When logging in with a lab user, if at any time you are asked to activate the user account, you will need to access
the user’s email to activate. To do this, browse to https://mail1.dcloud.cisco.com/owa and sign in with dcloud\username /
dCloud123! (usernames are always first initial and last name). You must either be on a session’s VPN to use your own
browser or connect via one of the workstations inside the lab. After logging into the email, look for the latest email address
about activating your Webex Teams Account. If you don’t see the email, you can click the Resend link on the login page
from earlier. After clicking the Get Started Now link within the email, enter a password of dCloud123! when prompted. (If
you received an email with a six-digit number, then enter that into the previous Web page.)
3. Since Proximity is on by default in the app, once it is opened, you should see the room device in the Message list. If it does not
pair, hold your mobile device closer to the room device. In a training environment with multiple rooms systems, it may be
difficult to pair your mobile device with the correct room device. If you are having trouble pairing automatically, you can try the
steps below to pair manually.
a. Tap the avatar for Taylor and tap Devices.
b. Toggle on Manual Connection Option.
c. Go back to the Spaces list and tap Connect to a device.
d. Search for the name you gave your device.
e. When prompted for a pin, enter the one displayed at the top right of your video device.
4. With Taylor connected to the room device, search for Kellie, call her, and answer the call from Kellie’s client.
5. Mute the endpoints to stop feedback.
6. Wait for the call to show up on the Cisco Webex Teams app and, when it does, answer it from the room device. Mute Kellie’s
client to stop feedback.
7. The room device and the client are now on a video call. Name labels if setup will be displayed on DX, SX, MX, Room Series
devices and Webex Boards that are Webex registered. Name labels are sent from Room Series devices and Webex Boards that
are Webex registered. For update info on name labels, visit here.
8. Move the call from the room device to your mobile by tapping your finger on the screen to bring up the menu options and
tapping the ellipses icon [ ].
9. Tap Move Call and you will see a notification of the discovered device. Simply tap the Move button.
10. After the call moves to your mobile, tap the [ ] button.
11. Now you should have a video call between your mobile device and the phone.
Lab Guide
Cisco dCloud
12. To move the call back from the device, simply repeat Steps 8 and 9 above and move the call back from the endpoint to your
device.
13. End the call from your mobile by tapping [ ] and then tapping the Hang up button.
NOTE: The move call feature is also available on the Cisco Webex Teams desktop client. To use, just click Move call in
the active call window and it will move to your room device or back to your desktop.
DX Whiteboarding
Within a call on the DX, you can now utilize the whiteboard feature. The whiteboard feature can be utilized outside of a space call
but there is no ability to save the document. If you want to save the whiteboard, you must be on a call that has been initiated from
within a space.
1. Pair your Webex Teams client to the DX and initiate a call to another user/s on a Webex Teams client. This can be a 1:1 or group
space meeting.
2. After connecting to the call/meeting, tap the Whiteboard icon on the DX and choose New whiteboard.
3. Start drawing on the DX and you will notice you can view/edit the whiteboard on your paired mobile client. Also, the other
user/s in the call/meeting will be able to view or make edits.
4. When finished, end the call/meeting.
Room Device Alerts
You have the ability to get alerts from your devices to inform you when the devices go offline, have issues, or have issues resolved.
You can enable this globally or individually for each device. You will enable them globally.
1. In the Webex Control Hub for your customer, click the Devices tab.
2. At the top right of the page click My Alerts. (If you are on the device individually, it will be Manage Alerts.)
3. Toggle on both toggles for alert when device goes offline and when device has issues.
4. Power off your registered room device.

5. Log into Charles’ Webex Teams client on Workstation 1. (cholland@cbXXX.dc-YY.com / dCloud123!)
6. In a few minutes you should receive an alert from the Control Hub Alerts bot telling you that your device went offline. Note that
these notifications are sent to the Administrator who set up the alerts.
7. Power back on your device after receiving alerts.
You have now tested the calling/sharing functionality of the mobile app and a room device.
Lab Guide
Cisco dCloud
Room Device Software
Within Control Hub, you have the ability to have more control of your room device software as well as get more information about
the stable and preview releases.
1. In the Webex Control Hub for your customer, click the Devices tab (should already be on the page).
2. At the top right of the page, click Software.

3. On this page you are given information about the stable and preview software. In most cases you will want to have your users
running on the stable software because as the name says it is most stable and TAC supported. In special cases you might want to
try out the newer features that aren’t generally available yet, then you can use the preview software.
4. Scroll down to the Stable software section.

In this section you can see how many devices are running the stable software. If you click View Devices, you will be taken to a list of
devices running the stable software. Also in this section you are given the dates of release for the current version and upcoming
version.
5. Click Show Details.
6. You now see what changes were made in this release. You can click Read more to get more detail on the features.
7. Scroll down the Preview software section.
8. Here you will see the same information as the stable software section, but you are also given the ability to report bugs. Take
note of the warning that this software channel is not supported by TAC.
9. At the bottom of the page you have a link that will take you to view the release information for older version of software.
10. All room devices are put on the stable software release by default. If you would like to run any devices on the preview software
you will need to change each device individually. This is found on the Place that the room device is in.
11. Navigate to Places.
12. Select the place you created earlier when adding your room device.
13. On the flyout window you will see in the Device Settings section which software channel the device is running.
14. Using the dropdown list, change the software channel to Preview.
15. Within a few minutes the software will be downloaded and installed as well as reboot. If at any time you want to go back to the
stable version you can use this list box and the device will downgrade.
Lab Guide
Cisco dCloud
Scenario 3. Webex Hybrid Calendar Service (Quick Setup)

With Hybrid Calendar Service, you can connect your on-premises Microsoft Exchange, Office 365 or Google's G Suite Calendar
(Google Calendar) environment to Cisco Webex. This integration makes it easier to schedule and join meetings, especially when
mobile; no plugins are required.
Hybrid Calendar Service has no Cisco call control dependency—you can use this service to extend features to Cisco Webex users,
even if you use a third-party UC solution.
Simple Meeting Scheduling
To simplify scheduling a meeting, your users can type scheduling keywords and modifiers in the location field of their calendar
invitation.
To Do This… Use Any of These in the Location

Create a Cisco Webex Teams space for @webex:space
meetings, or host the meeting through Cisco
Webex Teams @meet
@meet:space
@spark (deprecated)
Include a clickable link for your Webex Personal @webex

Room
@webex:myroom
@meet:myroom
Your Personal Room URL (for example, https://<company>.webex.com/meet/<hostID>)
Meetings List and Join Button
The meetings list in Cisco Webex Teams lets users see upcoming meetings for the next four weeks. Users see a Join button in the
meetings list and a scheduled meeting notification five minutes before the meeting starts.
Users can add Cisco Webex room and desk devices and Webex Boards to a meeting to make conferencing resources available. If the
device is enabled for the Hybrid Calendar Service, the green Join button appears on the device. (The Join button is also known as
One Button to Push, and is also available to devices that are registered to Cisco Unified Communications Manager, and managed by
Cisco TelePresence Management Suite.) Hybrid Calendar Service-enabled room and desk devices can also show meetings to which
they've been invited in the meetings list.
You can view the full setup guide at https://www.cisco.com/go/hybrid-services-calendar.
Quick Setup Information
In this scenario, you will configure the hybrid calendar connector using quick steps so you can dedicate your time to newer features.
The calendar service is required to be configured to be able to test the next scenario, Webex Edge for Devices. If you have never
gone through the full configuration and want to see what you are missing then you can view all the steps in Appendix E.
Lab Guide
Cisco dCloud
Configuring Expressway – C Connector Host
You will now add a new Expressway-C Connector Host to the Customer Organization for use with Cisco Webex Hybrid Services. This
Expressway-C server will have all the required connectors for Cisco Webex Hybrid Services Calendar and Call. You will need to
complete these steps from Workstation 1 within the lab.
1. Return to the Cisco Webex Control Hub you have open. Verify you are still logged in as Charles Holland and connected to your
sessions VPN.
2. On the left-hand menu within the portal, click Services.
3. Under Hybrid Calendar Exchange, click Set Up.
4. Click Next on the Hybrid Calendar Service Setup pop-up window.

5. At the first radio button, select and enter exp-cc.dcloud.cisco.com into the box and click Next.
6. For cluster name, enter HS Cluster 1.
7. Click Next again.
8. Click Next once more to open a new browser tab to the Expressway. Ignore/accept/proceed through any security warnings.
9. Log into the Expressway as admin with password dCloud123! (Should be prepopulated)
10. Check the box for I want Cisco to manage the Expressway CA certificates required for this trust.
11. Click Update software & verify connection.
12. After successful verification, click Register. (If prompted to login into Webex, enter cholland@cbXXX.dc-YY.com / dCloud123!
for the username / password.)
13. 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 Calendar Connector. The Management Connector manages all the connectors on the Expressway-C server. The
third connector, Call, will install once you enable the Hybrid Call Service later in the lab.
Lab Guide
Cisco dCloud
Exchange Pre-configuration
Microsoft Exchange was pre-configured with an impersonation account and a throttling policy to use with the Cisco Webex Calendar
Service. The impersonation account needs to be a mail-enabled account to use as the Service Account. The account does not have to
be an administrator, but it must have a mailbox. To read more about the impersonation account needed, click here. In this lab an
account called hcalendar will be used as the impersonation account. For your reference, the following are the commands to
configure exchange with the hcalendar impersonation account.
a. New-ManagementRoleAssignment -Name CalendarConnectorAcct -Role ApplicationImpersonation -User dcloud\hcalendar
b. New-ThrottlingPolicy -Name "CalendarConnectorPolicy" -EWSMaxConcurrency unlimited -EWSMaxBurst unlimited -

EWSRechargeRate unlimited -EWSCutOffBalance unlimited -EWSMaxSubscriptions 5000
c. set-ThrottlingPolicyAssociation -Identity dcloud\hcalendar -ThrottlingPolicy CalendarConnectorPolicy
d. New-Mailbox -Name 'Webex Room Device' -Alias 'webexrd' -room
Linking Expressway-C to Microsoft Exchange
You will now use a script to configure the Expressway-C host for the Cisco Webex calendar service.
NOTE: As mentioned earlier, if you want to view what is being configured, refer to Appendix E. The appendix can also be
used in case of script failure.
1. Before starting the script, on Workstation 1 verify your connectors have the status as shown in the screenshot below. This page
should already be open from earlier. If not, browse to the Expressway-C (198.18.133.223), log in (admin/dCloud123!), and
navigate to Applications > Hybrid Services > Connector Management.
Connector Management
2. On Workstation 1, open the Webex folder on the desktop.

3. Run the config_calendar.bat file by double clicking the file and letting the script run fully. Script will mention clicking buttons
again due to error, these can be ignored.
4. After Internet Explorer closes, continue to the next section and leave the remote connection to Workstation 1 up.
Lab Guide
Cisco dCloud
Enabling the Calendar Service for Charles
You will configure Charles manually for the Calendar Service. You can configure multiple users in bulk using a CSV template.
1. Go back to the Cisco Webex Control Hub.

2. Click Users from the menu on the left.
3. Find Charles Holland in the list and click his account.
4. In the Hybrid Services section, click Calendar Service.

5. Click the toggle next to Calendar Service to turn it on and click Save.
It will take about five minutes for the status to go from Pending Activation to Activated.
NOTE: Calendar activation will not start until each user has logged into a Cisco Webex Teams client once. This is for all
services, not just the calendar service.
6. Verify Charles is activated for the Calendar Service. If it is not, you can continue on with the lab for now. When you test in the
next scenario, his account will need to be activated.
Charles Activated Calendar Service
NOTE: Sometimes it takes a while for users to show as activated in the Control Hub. The Expressway-C connector host
sometimes shows the users activated quicker. On the connector host, navigate to Applications > Hybrid Services >
Calendar Service > Calendar Connector Status. If the users have been activated, you will see the number of users next to
Successfully Subscribed Users.
16. The calendar service is now configured but you will not test the configuration just yet. You will complete the testing after going
through the Webex Edge for Devices scenario. You’ll notice you did not modify the room device either for the calendar service.
You will do that in the next scenario when the device is registered to UCM since it works the same as it does when registered to
the cloud.
Lab Guide
Cisco dCloud
Scenario 4. Webex Edge for Devices

In this scenario, you will work through installing and configuring Webex Edge for Devices Connector tool.
Our customers are split over two deployment types—On-Prem or Cloud Registered. Our successful history has a huge prem-
registered footprint, but recent innovations have a cloud dependency, such as ideation/co-creation, intelligence /AI, a single-pane-
of-glass to manage at scale, and analytics.
Our customers are more and more open to cloud; however, they often need time to move their sometimes very large on-premises
installed base. They can also have the need for a migration strategy to cover the movement and also to cover the exceptions where
the endpoint cannot be moved but have the need for Cloud features.
The Webex Edge for Devices Connector tool provides support for two different operations:
• Mass migration of on-premises registered Webex devices to the Webex Cloud
• Linking of on-premises registered Webex devices to Webex Control Hub to allow access to Webex Cloud features
For the purpose of this exercise, you will only be working through the second operation of providing Webex Cloud features to an on-
premises registered Webex device.
Lab Guide
Cisco dCloud
Features and Benefits

Features and Benefits – Webex Device Linking
Features Benefits
Device Call Control and Media stays local Business critical Call Control and Media stay on-premises
- Even if cloud connection is lost
Scalable management and analytics Additional visibility gained through Cisco Webex Control Hub – ‘single pane of glass’
- Device analytics detailing historical usage
- Proactive alerts for device status
Access to cloud services and innovations - Support for Hybrid Calendar service and One Button to Push on Webex device without the
need for TMS/TMSXE
- Webex Assistant
Super simple setup No additional requirement for additional Firewall ports to be opened up
- HTTPS connection to the cloud
Overview - Steps Required
1. Download and install Webex Edge for Devices Connector tool
2. Configure an Application Account for Webex Edge for Devices Connector tool
3. Register Webex device to Unified CM over MRA
4. Configure Webex Edge for Devices Connector tool to connect to Unified CM
5. Link devices to Webex Control Hub through the Webex Edge for Devices Connector tool
6. Configure cloud features on the newly linked Webex Device
7. Test Cloud features
Lab Guide
Cisco dCloud
Installing Webex Edge for Devices Connector Tool
You will now download the Webex Edge for Devices connector tool and install. This will be completed on Workstation 1.
1. If not already connected, connect to Workstation 1 on 198.18.1.36:

• Username: dcloud\cholland
• Password: dCloud123!
2. Open Chrome and go back to the Cisco Webex Control Hub (admin.webex.com) and login if needed cholland@cbXXX.dc-
YY.com / dCloud123!
3. Within Webex Control Hub, navigate to Devices.
4. At the top right of the Devices window, click Resources.

5. Scroll down to Tools. On the Cisco Webex Device Connector tile, click Download.
6. Select Download for Windows. You will find the download (devicetool.msi) on the desktop of Workstation 1. Click Done after
verifying download completed successfully.
7. Double click the devicetool.msi file to start the installation process. Click on Run to proceed. The Cisco Webex Device Connector
Setup screen will display.
8. Click Next to continue. Check the License Agreement box and then click Next, leave the default install location and click Next
and then Install. Click Finish when done.
Configure an Application Account for Webex Edge for Devices Connector Tool
For the Webex Edge for Devices Connector tool to query Unified CM for a list of relevant devices for linking, there is the requirement
that an application user will need to be created with the role of Standard AXL API Access. The Webex Edge for Devices Connector
tool will use this account to communicate with Unified CM. For this lab, this user has been created for you. You will find the
necessary steps to create this user and assign permissions in Appendix B. The user is configured with other roles to also be used
within other parts of this lab. Only the Standard AXL API Access role is necessary for the Webex Edge for Devices Connector tool to
communicate with Unified CM.
NOTE: If linking devices by CSV or TMS Overview Export, the above user is not required.
Register Webex Device to Unified CM over MRA
Webex Edge for Devices is designed to provide Webex Cloud features to on-premises registered Webex devices. To demonstrate this
within the lab, a Webex device needs to be registered to Unified CM. For the purpose of this lab, the easiest way to achieve this is
via MRA on the Expressways in the dCloud lab as the Expressways are already configured for these services.
Lab Guide
Cisco dCloud
NOTE: If you have already registered your Webex room device to Webex Control Hub, you will need to delete the
registration in Webex Control Hub and factory reset the Webex device. The following steps guide through de-registering
and factory reset of the device. If you have not registered the Webex device to Webex Control Hub, you can jump to Step
6 below.
1. From Workstation 1, go back to your browser window, which should be logged into the Cisco Webex Control Hub.
2. Navigate to Devices. Your cloud registered Webex device will be listed here. Click on the Webex device name and in the fly out
card on the right, scroll down the screen to see the MAC Address for the device. Highlight the MAC Address and copy it. You will
need it later.
SUGGESTION: Create a new Notepad file on the desktop and paste the MAC address there. The separators in the MAC
address will need to be removed – as an example AB:1D:2C:38:82:6E would be saved as AB1D2C38826E in the Notepad
file.
3. Back at the Devices page, to the left of the device there is a small checkbox (as shown here) , select the
check box. You will see the line above will say 1 device selected and to the right of this you will see a trash can with Delete
Devices next to it. Click Delete Devices.
4. The Delete Devices dialogue box will show up asking you to confirm deletion of the device. Click on the check box next to Delete
resulting empty places followed by the red Delete button. Once deletion has taken place, click Done.
5. From the Webex device, click on the Device Name at the top left of the screen and then Settings > Factory Reset and Reset
again to confirm.
6. In a new browser tab on Workstation 1, navigate to Collaboration Admin Links > Cisco Unified Communications Manager.
7. Click Cisco Unified Communications Manager and login with the following (should be pre-populated):
• Username: administrator
8. Navigate to Device > Phone and then click Find.
17. A number of common devices have been pre-configured for you on the lab’s base configuration. These include a Cisco Webex
DX70, DX80, Room Kit, and Room Kit Mini. They each have been assigned to Charles Holland and configured with his line
number of 6018. If you are using a different device you will need to create it manually mirroring what is configured on the
preconfigured devices. The next steps are modifying the preconfigured devices.
9. Find the device you are using and click on the Device Name (it starts with SEP).
10. From the Phone Configuration page, enter the real MAC Address of the device into the MAC Address field. If it was cloud
registered before, you made a note of the MAC Address above. If it was not registered, the MAC Address is shown on a label
underneath the device.
11. Scroll down the screen to find the Product Specific Configuration Layout section. Within the section click SystemUnit in the list,
you will see General Settings and CrashReporting options displayed. Under General Settings, locate the Name field and give
your device a name.
Lab Guide
Cisco dCloud
12. Click Save, OK, Apply Config, OK.
13. Once the device has been factory reset, you will see the Welcome Screen. Select Start and then the blue next arrow at the top
of the screen.
14. Select Other Services > Cisco UCM via Expressway and enter the following:
• Username: cholland
• Domain: cbXXX.dc-YY.com
15. Select the blue arrow at the top right and you will see Setup Done!.
16. Return back to browser tab for Unified CM and refresh the page showing the device belonging to Charles Holland. The Real-
Time Device Status should state:
• Registration: Registered with Cisco Unified Communications Manager cucm1.dcloud.cisco.com
• IPv4 Address: 198.18.133.152
Configure Webex Edge for Devices Connector Tool
1. Return to Workstation 1.
2. If the Webex Edge for Devices tool is not already open, click the Windows Start button on Workstation 1. Click on Cisco Webex
Device Connector shown under Recently Added.
3. The starting page of the tool will ask for your Cisco Webex Administrator Username and Password. Enter:
• Username: cholland@cbXXX.dc-YY.com
• Click Sign In
4. From the What would you like help with? screen, select I want cloud features for my on-premises registered devices.
5. From the Configure Webex Edge for Devices screen, select Link devices registered with Cisco Unified Communications
Manager.
NOTE: Within the lab the Webex devices are registered to Unified CM. The other options to Link Webex devices would be
via either a CSV import or the import of the TMS Overview Export. These additional options are shown on the
configuration screen, they are not covered within this lab.
6. In the next screen, enter the following:
• Host: cucm1.dcloud.cisco.com
• Username (Standard AXL API Access): webex
7. Click Connect.
Lab Guide
Cisco dCloud
8. From the error page, click Proceed without certificate validation.
NOTE: We are using Self Signed Certificates in the lab and these have not been added to the users Certificate directory
for the Webex Device Connector tool. This is the reason for the ‘Failed to connect’ message.
9. You will now be presented with a list of the Webex devices available for linking to the cloud. Click Link next to the device you
registered to Charles Holland.
10. The status will change from Link to Linking. Once Linking has completed, the status will change to Linked [ ].
Configure Cloud Features
IMPORTANT: In this section you will be enabling the Hybrid Calendar Service for the Webex device. If you have not
already configured and enabled the core service with Webex Control Hub, go to either Scenario 3 (Exchange On-
Premises) or Scenario 8 (Exchange On-Line) and enable the Hybrid Calendar core service, Webex site configuration, and
enablement of Calendar Service for users before proceeding with this section.
1. Go back to your browser window, which should be logged into the Cisco Webex Control Hub (https://admin.webex.com).
2. Navigate to Places within Cisco Webex Control Hub.
This will show the new place that has been created through the Webex device linking process completed in the previous section. The
place will be named the same name you entered into the device on Unified CM. It will also show that the place contains a Webex
device.
3. Click the place name. From the right-hand side of the browser window you will see a fly out window appear.
4. Click on Edit in the Services area.
5. In the Edit Services screen you will see that the Calendar Service is deactivated. Click on the toggle to enable the service, then
click Next.
6. Enter the email address for the resource mailbox configured webexrd@cbXXX.dc-XX.com (this was preconfigured for you on
Exchange).
7. Click Save.
8. Calendar Services will now be shown for the Webex Device and the status will show as Pending Activation. After a few minutes
this will change to Activated.
Activated Calendar Services
Lab Guide
Cisco dCloud
Test Creating a Cisco Webex Teams Space for Meetings, or Host the Meeting through Cisco Webex
Teams with OBTP
1. If not already connected, create an RDP connection to Workstation 1 (198.18.1.36) and log in with these credentials:
2. If not open already, open Outlook using the icon in the taskbar [ ].
3. Click Calendar at the bottom of Outlook and then click New Meeting [ ].
4. Add Anita Perez, Taylor Bard, and Kellie Melby in the To line.
5. Enter a relevant Subject.
6. For Location, enter one of the following to create a space meeting:
• @webex:space
• @meet
• @meet:space
7. For OBTP, click the Rooms… button at the end of the Location field.
8. Choose the room mailbox you created earlier on the Exchange server and click OK.
9. Click No to the update the location pop-up.
10. Set the start time for today and a time in the future from what your workstation clock reads. Set the time at least ten minutes in
the future for OBTP and meeting notifications to work.
11. Enter some relevant text in the body of the message, if you like.
12. Verify one of the keywords from above are still in the location field and click Send.
The Calendar Connector now reads the keyword from the location field and populates the Webex Teams space information into the
meeting invite, as well as creates a Cisco Webex Teams space with all the participants. After a few moments, open the meeting you
created and you should see the Webex Meeting information located at the bottom of the invite. If it has not populated, close the
meeting and reopen after a few more moments.
13. Bring up Webex Teams on Workstation 1 and log in cholland@cbXXX.dc-YY.com / dCloud123!
14. If you used the space keywords you will notice there is a space in your account with a name that is the same as the meeting
invite subject.
15. Click the space and you will notice the meeting details were also posted into this space.
16. Click the Meetings [ ] icon to view meetings list. Select the meeting to view participants including room devices. You can see
if the users accepted the invite as well.
17. You should also see the meeting listed on your room device.
Lab Guide
Cisco dCloud
18. Six minutes before scheduled meeting: Once you receive the join notification on your Webex Teams app, click the notification
and then Join With Video.
NOTE: To save time, while you are waiting for this space meeting to start, you can go ahead and schedule another
Webex Meeting as shown in the next section.
19. On your room device, notice it shows Charles has already joined the meeting. Now tap Join to go straight into the meeting in
progress.
20. End the meeting when you are finished. Feel free to schedule more meetings using the other keywords.
Test Including a Clickable Link for Your Webex Personal Room with OBTP
Now you will test scheduling a Webex Meeting functionality with OBTP.
1. If the previous meeting is still in progress, right click the meeting in the calendar and select Cancel Meeting then click Send
Cancelation to free up the room devices. Room devices can’t be double booked.
3. Add Anita Perez, Taylor Bard, and Kellie Melby to the To line.
5. For Location, enter one of the following addresses to create a meeting using your own Webex personal room:
• @webex
• @webex:myroom
• @meet:myroom
• https://cbXXXYY.webex.com/meet/cholland
6. For OBTP, click the Rooms… button at the end of the Location field.
11. Verify the keyword is still in the location field and click Send.
The Calendar Connector now reads the keyword from the location field and sets up the meeting. After a few moments, open the
meeting you created and you should see the Webex meeting information located at the bottom of the invite. If it has not populated,
close the meeting and reopen after a few more moments.
12. Six minutes before scheduled meeting: Once the host, Charles, receives the join notification on his Webex Teams app, click on
the notification and then Join With Video.
Lab Guide
Cisco dCloud
13. On your room device, notice it shows Charles has already joined the meeting. Now tap the Join button to go straight into the
meeting in progress.
14. End the meeting when you are finished.
You have successfully tested the Exchange Hybrid Calendar Service using the keyword functionality as well as One Button to Push,
meeting lists, and join notifications.
Lab Guide
Cisco dCloud
Scenario 5. Webex Edge Audio

In this scenario, you configure the Cisco Webex Edge Audio solution. This follows the configuration listed in the Cisco Webex Edge
Audio Customer Configuration Guide.
Edge Audio is an audio solution where calls originating within the enterprise go through your company network, over the internet,
and into the cloud. Similarly, calls that initiate from Webex during a meeting route through the internet to leverage your on-
premises audio routing.
Dial-in Scenario
The above figure shows a typical dial-in scenario. The purple phones represent dial-in users who are calling numbers that are set up
with Edge Audio. All on-network users that dial numbers configured with Edge Audio will have their call route into the Unified CM,
through the Expressways, and into the Webex cloud.
The orange phone represents a user in your enterprise that is dialing into a meeting using a number that is not configured to route
over Edge Audio. Since the user is dialing an unconfigured number, the call routes through the Session Border Controller, over the
PSTN, and into the Webex cloud.
The gray phone represents an off-network user. Off-network users who dial into Webex meetings will not route over Edge Audio.
Their calls route over the PSTN and into the Webex cloud.
Lab Guide
Cisco dCloud
Callback Scenario
The above figure shows a typical callback scenario. The green phones represent callback users on your network that are set up to
have calls route to them.
The grey phone represents an off-network user. If an off-network user selects the callback option when connecting their audio, then
the call routes over the PSTN and into the Webex cloud.
This guide explains how each of the network components, Unified CM, Expressway-C, and Expressway-E, must be configured for calls
going into the Webex cloud from your enterprise (dial-in), and how to handle calls that are initiated from Webex to flow into your
enterprise (callback).
To set up Edge Audio, you must first collect the necessary dial-in information from Cisco Webex Site Administration or Cisco Webex
Control Hub—dial-in numbers and the Lua Normalization script. You will use this information to set up the dial-in numbers that users
will use to dial-in to their Webex services.
The setup of Edge Audio can be broken down into four main steps:
• Obtain dial-in numbers and Lua script
• Configure Unified CM
• Set Up Expressway-C
• Set Up Expressway-E
Lab Guide
Cisco dCloud
Each of these steps are explained in detail in this scenario and represented in the figure below.
Detailed Configuration Steps
The Lua Script with Edge Audio
You must specify call routing rules in Unified CM using Webex numbers in order for calls using those numbers to route to the Webex
cloud. You also need a (Lua) normalization script to create the trunk in Unified CM. You can access these phone numbers and the Lua
script from Webex Site Administration or Control Hub.
Lab Guide
Cisco dCloud
If you manage your Webex sites in Webex Site Administration, or have completed the Site Linking process, then follow the
instructions for Collect Dial-in Numbers and Lua Script from Webex Site Administration. (Not detailed in this lab.)
If you set up and manage your Webex sites in Control Hub, then follow Collect Dial-in Numbers and Lua Script from Webex Control
Hub. (Instructions detailed below for this lab.)
Edge Audio is a global service that uses a Lua script to maintain proper call routing. The Lua script makes the following call
translations:
• It updates the host portion of the request URI so that Expressway can route calls to the Edge Audio.
• It appends the x-cisco-site-uuid parameter to the request URI referencing the Webex site.
• It updates the SIP To header user part that is required for Edge Audio processing.
Collecting Dial-in Numbers and Lua Script from Webex Control Hub
1. On Workstation 1, go back to the Cisco Webex Control Hub.
2. Navigate to Services. Under the Meetings card, click Sites.
3. For later in the lab, take note of the site URL listed. Select the site and click Configure Site in the fly-out window.
4. On the next screen under Common Settings, click Edge Audio.
5. Under Dial-in Settings, click Click here to expand the dial-in numbers.
6. You will need to write down/capture one Phone Number for the datacenter that your dCloud session is located in. This will be
used later in the lab. Use the domain assigned to your session to determine the location using the table below.
Webex Dial-in Number
dCloud Datacenter Country / Phone Label

US West (dc-05) or US East (dc-01) United States Toll (Pick one number for a listed city)
EMEAR (dc-03) United Kingdom
APJ (dc-02) Singapore toll
7. Scroll to the bottom of the dial-in numbers and click Generate Lua Script. Click Export.
8. The .lua script will save to the desktop of Workstation 1.
9. Close the pop-up window.
Configuring the Cisco Unified Communication Manager
To route calls from your enterprise to the Webex cloud, you need to set up routing rules and trunks in Unified CM Administration.
Create SIP Normalization Script Using Webex LUA Script
Use the Lua script that was exported form the Webex Control Hub to create a new SIP Normalization Script in Unified CM.
1. If not already logged into Unified CM, in a new browser tab navigate to Collaboration Admin Links > Cisco Unified
Communications Manager.
Lab Guide
Cisco dCloud
2. Click Cisco Unified Communications Manager and login with (should be prepopulated):
3. Navigate to Device > Device Settings > SIP Normalization Script.
4. Click Add New.
5. Give the script a name such as cbXXXYY_webex_edge_audio. (XXX and YY correspond to your sessions Webex site name) Leave
all other settings at default.
6. Toward the bottom of the page, click Import File.
7. Click Choose File, browse to your desktop and select the .lua script that was exported earlier.
8. Click Import File and then Close. The Content box is updated with the Lua script after it’s imported.
9. Click Save.
Setting the Early Offer Support for Voice and Video Calls in a SIP Profile
In the lab a new SIP Profile is created. If you already have a SIP Profile configured for Early Offer you could use that instead of
creating a new one.
1. Navigate to Device > Device Settings > SIP Profile and click Find.
2. Click the Copy icon [ ] next to Standard SIP Profile For Cisco VCS.
3. Configure the name as Edge_Audio.
4. Near the bottom of the page, select Best Effort (no MTP inserted) for Early Offer support for voice and video calls.
5. Click Save.
Creating a SIP Trunk Security Profile
1. Navigate to System > Security > SIP Trunk Security Profile and click Add New.
2. Name the trunk Edge_Audio.
3. For Device Security Mode, leave the selected choice as Non Secure. In production you may want to select Encrypted instead.
4. For Incoming Port enter 5070. (a non-conflicting port is being used instead of 5060 or 5061)
5. Click Save.
Lab Guide
Cisco dCloud
Edge Audio and the G.722/G.711 Codecs
Edge Audio supports the G.722 and G.711 codec. You don’t need to configure those codecs on your Unified CM for Edge Audio to
work, but because those codecs use less bandwidth than other codecs, configuring it might help improve the quality of service for
the deployment. In the lab you will create a separate region and device pool as an example. In production you may already have
device pools and regions configured for G.722 and G.711. If that is the case then new ones don’t have to be configured just for Edge
Audio.
1. In the lab, Unified CM G.722 is already advertised but for reference to configure navigate to System > Enterprise Parameters
and for Advertise G.722 Codec choose Enabled. Then click Save.
2. Navigate to System > Region Information > Region and click Add New.
3. Configure the name as Edge_Audio and click Save.
4. Select both Default and Edge_Audio from the Regions list.
5. For Audio Codec Preference List, select Factory Default lossy.
6. For Maximum Audio Bit Rate, select 64 kbps (G.722, G.711).
7. Click Save.
Now you will configure a device pool to set the region to.
8. Navigate to System > Device Pool and click Find.
9. Click the Copy icon next to dCloud_DP.
10. Configure the name as Edge_Audio.
11. For Region, choose Edge_Audio and click Save.
Creating a New Trunk Between Unified CM and Expressway-C
A new trunk needs to be created to the Expressway-C rather than modifying an existing one.
1. Navigate to Device > Trunk and click Add New.
2. For Trunk Type, choose SIP Trunk. Leave as None type and click Next.
3. Configure the following parameters from the table below.
Lab Guide
Cisco dCloud
Edge Audio SIP Trunk Configuration
Setting Configuration
Device Name Edge_Audio
Device Pool Edge_Audio
Inbound Calls > Calling Search Space Call_Everyone
SIP Information > Destination Address 198.18.133.152 (Exp-C address. Also keep port at 5060)
SIP Information > SIP Trunk Security Profile Edge_Audio

SIP Information > SIP Profile Edge_Audio
SIP Information > DTMF Signaling Method RFC 2833
Normalization Script cbXXXYY_webex_edge_audio
4. Click Save, OK, Reset, Reset, Close.
Creating a Route Group
1. Navigate to Call Routing > Route/Hunt > Route Group and click Add New.
2. For Route Group Name, enter Edge_Audio_RG.
3. From the Available Devices box, select Edge_Audio and click Add to Route Group.
4. Click Save.
Creating a Route List
1. Navigate to Call Routing > Route/Hunt > Route List and click Add New.
2. For Name, enter Edge_Audio_RL.
3. For Cisco Unified Communications Manager Group, choose Default.
4. Click Save.
5. Once the page refreshes click Add Route Group.
6. From the Route Group drop down list, select Edge_Audio_RG-[NON-QSIG].
7. Click Save and then OK.
Creating Route Patterns
The phone number that was captured earlier must be configured as route patterns. This is the number that users will dial to start
and join their Webex meetings.
These numbers include all possible numbers that can be used with Edge Audio. Depending on your configuration, country, or region,
you might not want to create route patterns for all the numbers.
For lab purposes you will configure a route pattern for one number in the list. You will need to choose the correct dial in number
that corresponds to what dCloud datacenter you are taking the lab. If you didn’t take down the number earlier, you should still be on
the page in Control Hub to obtain it.
Lab Guide
Cisco dCloud
1. Navigate to Call Routing > Route/Hunt > Route Pattern and click Add New.
2. Configure the following parameters in the table below.
Route Pattern Configuration
Pattern Definition > Route Pattern Number obtained at the beginning of the scenario minus the
plus (+). For example if the number obtained was +44-203-
478-5290 then for the route pattern enter 442034785290.
Capture this number in your notes because you will need it
later.
Pattern Definition > Route Partition Base_PT
Pattern Definition > Gateway/Route List Edge_Audio_RL
3. Click Save, OK, OK.
Configuring a Cluster Fully Qualified Domain Name
In order to route calls properly into Unified CM, the Cluster Fully Qualified Domain Name must be updated to add the domain given
to your lab session.
1. Navigate to System > Enterprise Parameters.
2. Complete a search for fully, which will bring you to the Cluster Fully Qualified Domain Name parameter.
On the lab’s base config, cucm1.dcloud.cisco.com is already configured. Leave that setting in the box and add the domain of your lab
session in front of the cucm1.dcloud.cisco.com entry followed by a space separating the two. For example, if your domain was
cb106.dc-01.com, then the settings should be: cb106.dc-01.com cucm1.dcloud.cisco.com. (See the example below.)
Cluster Fully Qualified Domain Name Setting
3. Click Save.
Configuring Expressway-C
Configuring Expressway-C Neighbor Zone
1. In a new browser tab, navigate to Collaboration Admin Links > Cisco Expressway-C.
2. Login with admin / dCloud123! (should be prepopulated).
3. Navigate to Configuration > Zones > Zones and click New.
Lab Guide
Cisco dCloud
Edge Audio Expressway-C UCM Neighbor Zone Configuration
Configuration > Name UCM Neighbor for Edge Audio
Configuration > Type Neighbor
H.323 > Mode Off
SIP > Port 5070 (Same port number as SIP Trunk Secure Profile)
SIP > Transport TCP
Authentication > Authentication policy Treat as authenticated
Location > Peer 1 Address cucm1.dcloud.cisco.com
Advanced > Zone Profile Custom
Advanced > SIP parameter preservation On
5. Click Create Zone.
Configuring Expressway-C Traversal Client Zone
1. On the Zones page, click New.
Edge Audio Expressway-C Traversal Client Zone Configuration
Configuration > Name Traversal Client for Edge Audio
Configuration > Type Traversal client
Connection credentials > Username cisco2
Connection credentials > Password dCloud123!

H.323 > Mode Off
SIP > Port 7005
SIP > Media encryption mode Force Encrypted
SIP > SIP parameter preservation On
Location > Peer 1 Address vcse.cbXXX.dc-YY.com
Lab Guide
Cisco dCloud
Configuring an Expressway-C Search Rule
1. Navigate to Configuration > Dial plan > Search rules and click New.
Edge Audio Expressway-C Search Rule Configuration
Configuration > Rule Name Outbound Edge Audio
Configuration > Priority 98
Configuration > Protocol SIP
Configuration > Source Named
Configuration > Source Name UCM Neighbor for Edge Audio

Configuration > Request must be authenticated Yes
Configuration > On successful match Stop
Configuration > Target Traversal Client for Edge Audio
3. Click Create search rule.
Configuring Expressway-E
Configuring Expressway-E Secure Traversal Server Zone
1. From Workstation 1, in a new browser tab navigate to Collaboration Admin Links > Cisco Expressway-E.
2. Proceed through and accept the security warning, if prompted. Login with admin / dCloud123!
3. Navigate to Configuration > Zones > Zones and click New.
Edge Audio Expressway-E Traversal Server Zone Configuration
Configuration > Name Traversal Server for Edge Audio
Configuration > Type Traversal server
Connection credentials > Username cisco2
H.323 > Mode Off

SIP > Port 7005
SIP > Media encryption mode Auto (default)
Authentication > Authentication policy Treat as authenticated
Lab Guide
Cisco dCloud
Configuring Expressway-E Webex Zone (X8.11 and later)
NOTE: In the lab, the expressways are at version X8.11+. In earlier versions this zone is not available to be configured so
a regular DNS zone must be used. Click here to view that configuration in needed.
4. On the Zones page click New.
5. For type choose Webex.

Configuring an Expressway-E Search Rule
1. Navigate to Configuration > Dial plan > Search rules and click New.
Edge Audio Expressway-E Search Rule Configuration
Configuration > Rule Name Outbound Edge Audio

Configuration > Source Name Traversal Server for Edge Audio
Configuration > Request must be authenticated Yes
Configuration > Target Webex Zone
Expressway-E Mutual TLS Configuration
1. Navigate to Configuration > Protocols > SIP.

2. For Mutual TLS mode, choose On. (Leave the default port of 5062 for Mutual TLS port.)
3. Click Save.
NOTE: The next step in a production environment is to verify the correct firewall ports are opened as well as verifying the
correct certificates are installed on the Expressway-E. These have already been taken care of in the base lab. For more
information of what is required, see Open Required Firewall Ports.
Lab Guide
Cisco dCloud
Edge Audio Callback Settings
The next configuration is for the Edge Audio callback settings. Before starting the callback settings configuration, a DNS SRV record
must be configured at your site with the following considerations:
• DNS SRVs must point to a Mutual TLS port on the Expressway-E (port 5062)
• DNS SRVs must include all the Expressway-E target A records in the cluster, with each having port 5062
This configuration has already been completed in the dCloud platforms DNS server. An SRV record of _sips._tcp.mtls.cbXXX.dc-
YY.com was configured for your session to allow MTLS on port 5062.
Call Routing from Webex Edge Audio
You must allow E.164 numbers to traverse your Expressway-E and route calls based on your configuration. This ensures proper call
routing for users that are on your network and connect to your Unified CM, and users that are off you network, like those connected
to a mobile phone. Also, to prevent things like toll fraud, call policy rules are used on the Expressway-E. In order to allow Edge Audio
inbound calls from Webex you will be creating a new call policy rule as well.
Call Routing for Expressway-E
1. On the Expressway-E, navigate to Configuration > Dial plan > Search rules and click Clone next to the Outbound Edge Audio
search rule you created earlier.
2. Change the following parameters from the table below.
NOTE: It’s very important when adding regex patterns string that there are no trailing spaces.
Edge Audio Expressway-E Search Rule Configuration
Configuration > Rule Name Inbound Edge Audio
Configuration > Source name Webex Zone
Configuration > Mode Alias pattern match
Configuration > Pattern type Regex
Configuration > Pattern string (.*)@mtls\.cbXXX\.dc-YY\.com;.*x-cisco-webex-service=audio (replace XXX and YY with your sessions domain info)
Configuration > Pattern behavior Replace
Configuration > Replace string \1@cbXXX.dc-YY.com (replace XXX and YY with your sessions domain info)
Configuration > Target Traversal Server for Edge Audio
Lab Guide
Cisco dCloud
Call Policy Rules
Now you will create a new policy rule to allow incoming Webex Edge Audio calls.
1. On the Expressway-E, navigate to Configuration > Call Policy > Rules and click New.
Edge Audio Expressway-E Call Policy Rule Configuration
Source type Zone
Originating Zone Webex Zone
Destination pattern .*
3. Click Add.
4. Find the new Webex Zone rule at the bottom of the list and use the up arrows [ ] to move it up to the top of the call policy list.
Call Routing for Expressway-C
1. On the Expressway-C navigate to Configuration > Dial plan > Search rules and click Clone next to the Outbound Edge Audio
search rule you created earlier.
Edge Audio Expressway-C Search Rule Configuration
Configuration > Rule Name Inbound Edge Audio
Configuration > Source Name Traversal Client for Edge Audio
Configuration > Target UCM Neighbor for Edge Audio
3. Click. Create search rule
Apply Edge Audio Callback Settings from Control Hub
1. Back on the Control Hub (admin.webex.com), navigate to Services. Under the Meetings card, click Sites.
2. Select the site listed and click Configure Site in the fly-out window.
3. On the next screen under Common Settings, click Edge Audio. Webex Edge supports call back using extensions.
4. Under Country/Region, choose Extension.
5. For Expressway DNS SRV enter mtls.cbXXX.dc-YY.com.
6. Click Add. (Connectivity check status should be Successful)
Lab Guide
Cisco dCloud
7. Under Callback Settings for Country/Region choose the region based on the dCloud datacenter list from the table below.
Callback Settings
dCloud Datacenter Dial in number

US West (dc-05) or US East (dc-01) United States of America (1)
EMEAR (dc-03) United Kingdom (44)
APJ (dc-02) Singapore (65)
8. For Expressway DNS SRV, enter mtls.cbXXX.dc-YY.com.
9. Click Add. (Connectivity check status should be Successful)
10. IMPORTANT: Scroll down to the bottom of the page and click Apply Settings and then click OK.
11. After clicking Apply Settings, verify that the Apply Settings button is greyed out.
NOTE: After you apply the settings, the callback country shows up immediately in Control Hub, but it could take up to 30
minutes for the settings to apply to the database. Until settings apply to the database, calls route over their previously
configured country settings.
12. Also, on this page notice the default setting for Retry call using PSTN Audio is checked by default. When Edge Audio callback is
enabled for one or more countries then Webex routes calls over the Internet. By default, if there are DNS, TCP, or TLS
connectivity issues, or a call fails with a 380 or a 400-699 SIP error response, then Webex retries the call over a PSTN
connection.
Testing Webex Edge Audio
1. On Workstation 1 open and sign into the Cisco Jabber client with cholland@cbXXX.dc-YY.com for the email and then
cholland/dCloud123! for the username/password.
2. Using the web browser inside Workstation 1 or your own web browser, navigate to https://cbXXXYY.webex.com (your session
Webex URL that you captured in the Control Hub at the beginning of this scenario).
NOTE: If the Webex meeting site URL does not work, verify the URL in Control Hub. Navigate to Services > Meeting >
Sites > Site Name. Alternate URLs that could be used are https://cbXXXYYa.webex.com, https://cbXXXYYb.webex.com,
or https://cbXXXYYc.webex.com.
3. If not automatically signed in already, sign in with Charles Holland (cholland@cbXXX.dc-YY.com / dCloud123!)
4. Click Start a Meeting.

5. You may be prompted to download the Webex Meetings app. Feel free to download and install if you don’t already have the
Webex Meetings application installed. Open the application and sign in with Charles’ account. If you want to join using the
browser instead then click Join from your browser instead.
6. In the Webex Meeting app click Start Meeting. (If you are using a browser, skip to next step. Also run through all the
coachmarks that you are prompted with.)
Lab Guide
Cisco dCloud
7. Click the meeting information icon [ ] at the top left of the screen. (It will appear when you move your mouse.)
8. Capture the Meeting Number and Attendee ID.

9. In Jabber, test Webex dial-in by dialing the exact number you configured as a route pattern in Unified CM earlier from Cisco
Jabber.
10. Once connected, when prompted, enter the Meeting ID and the Attendee Number listed on the Call in screen.
You now are connected via audio to the Webex meeting.
You can verify that you are traversing the expressways by logging onto either the Expressway C or E and view the zones. You should
see one call for the Edge Audio and Webex zones that you created earlier.
11. Now, test call back. First you’ll test a full number.
12. Disconnect the call from Jabber to the Webex meeting but leave the Webex meeting active.
13. In the Meetings app, click the More Options icon [ ] and choose Audio connection. Then click into the picklist drop-down
and choose Call me.
14. Leave country code selected (+1 for US datacenter, +44 for EMEAR datacenter, +65 for APJ datacenter), enter the number 972-
555-6018 and click Connect (Switch if you are connected to the computer’s audio).
15. Your Cisco Jabber client rings, answer it when it does.
16. When prompted, press 1 to enter the meeting.
17. (Optional) Check the Expressways to view the call using the Edge Audio zones.
18. When finished, end the call.
19. Call back to Charles using his extension. On the Call me option, click the drop-down icon and choose Call me at an internal….
20. Enter 6018 as the phone number and click Connect.
21. Answer the call and, if you like, verify the Expressway zones.
22. When finished, end the call.
Next you will test PSTN fallback. You will test this using the real DID assigned to your session for Charles. This number 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. Get that
number now. You can alternatively use your mobile number.
First you will need to tweak your working configuration to effectively break the call from coming in through the Expressways. If you
make a call now, the call will traverse the Expressways and route out the dCloud PSTN to make the call. If you use Charles’ DID
number, the PSTN will route back in through the same dCloud gateway to Charles’ phone and ring. If you dialed your mobile number
and it is a national number of the datacenter your session is in, the call will ring your mobile using the dCloud PSTN. Feel free to test
calling the numbers now and observe the zones for Edge Audio increases to 1.
There are many ways to break the config but in the lab you will do this by disabling the inbound search rule on the Expressway-E.
23. Go to the Expressway-E and navigate to Configuration > Dial Plan > Search rules.
Lab Guide
Cisco dCloud
24. Check the box next to Inbound Edge Audio and click Disable at the bottom.
Now when calls come in they will not be able to find a way into Unified CM so the call will fail and choose the alternate fallback
option.
25. Call back to Charles using the DID number or your own mobile number. On the Call me option, click Use a different phone….
26. Enter the number and click Connect. Note that the failover could take about 30-40 seconds or sooner.
27. When finished testing fallback, don’t forget to enable the search rule again on the Expressway-E.
Lab Guide
Cisco dCloud
Scenario 6. Webex Video Mesh

In this scenario, you will go through the steps to configure the Webex Video Mesh Service. Cisco Webex Video Mesh is a
revolutionary capability that can ensure your users enjoy high-quality audio, video, and content by bridging on-premises and cloud
resources.
End users are looking for outstanding meeting experiences with rich audio, video, and content sharing. They want to join a meeting
from whatever device they choose, and enjoy a great, consistent experience on each one.
Providing this experience to users is not always simple. IT has to deliver scalability, reliability, and reduce costs, along with these
great experiences to all their users. One of the most complex decisions can be whether or not to deploy cloud-based or premises-
based meetings. Each meeting deployment model has its own benefits, and IT must choose between them.
Cisco Webex Video Mesh uses a Webex Video Mesh Node, software that is installed on a Cisco UCS ® server and managed by Cisco
Webex Control Hub. Once installed on your network, the Video Mesh Node communicates with the Cisco Webex service in the cloud
and can be used by devices registered to the Cisco Webex service or to Cisco Unified CM.
When joining a meeting, the devices communicate with Cisco Webex in the cloud to find the most appropriate Video Mesh Nodes
for the meeting. Then the media (audio, video, content) is sent to the Video Mesh Node for processing. This can be a single node on
the enterprise network or multiple nodes, cloud and on-premises cascaded together to create the meeting. In either case, the user
experience is exactly the same.

Features Benefits
Local media processing for Cisco Webex Media no longer needs to go to the cloud and back for call processing. Media stays on-premises,
on-premises meeting attendees providing:
- Improved quality through reduced latency
- Faster connection to other users and to meetings
- Cost savings due to more efficient Internet bandwidth usage
Automatic overflow to the cloud if on- Improved reliability
premises resources are full or unavailable
Centralized management and visibility - No more fragmented tools – A single centralized management portal, called Cisco Webex Control
across premises cloud Hub, to manage your on-premises media nodes and Cisco Webex Organization
- Removes the guesswork on capacity usage, with consolidated administrator visibility into resource
use
- Simplified resource planning and utilization management
Automatic software updates Easy to maintain – The Video Mesh Node is an extension of the Cisco Webex service on your premises
that is synchronized with software updates such as security fixes, bug fixes, and features enhancements
deployed in the cloud.
Ease of deployment - Each Cisco Webex Video Mesh Node deploys in as little as 10 minutes
- Simple to deploy and add capacity when needed
Capabilities included with purchase of any Low cost – No additional subscription fees and no overage fees.
Cisco Webex Meetings
The full setup steps, including initial deployment, can be found in Deployment Guide for Cisco Webex Video Mesh.
Lab Guide
Cisco dCloud
Deploying Video Mesh Node
You will now download the Video Mesh Node and deploy onto a VMware ESXi host. This will be completed on Workstation 1.
1. Connect to Workstation 1 on 198.18.1.36:

2. Open Chrome and go back to the Cisco Webex Control Hub (admin.webex.com) and login if needed cholland@cbXXX.dc-
YY.com / dCloud123!.
3. Within the portal on the left-hand menu, click Services.
4. Under Video Mesh, click Set up.

5. Select No, I need to install and configure the software.
6. IMPORTANT: Select Limited capacity 90 day demo. (Full capacity will not work in the lab.)
7. Click Next and then click Ok.
8. Wait for the videomesh_demo.ova to be downloaded to the Workstation 1 desktop.
9. After the ova download completes, open the VMware vSphere client using the icon on the desktop or taskbar .
10. Login to esxi1 with root / dCloud123!
11. Navigate to File > Deploy OVF Template.
12. Browse to the desktop and choose the videomesh_demo.ova that you downloaded earlier and click Next.
13. Click Next on the OVF Template Details page.
14. For name enter vmn1 and click Next.
IMPORTANT: Choose Thin Provision and then click Next. (Only thin provisioning will work in the lab.)
15. Keep the Network Mapping at the defaults and click Next.
NOTE: Dual NIC is available to use with the Video Mesh Node. In the lab, you will use a single NIC.
16. Check the box to Power on after deployment and then click Finish.
17. Wait for the OVA to deploy and then click Close.
18. Expand the host esxi1 and select the vmn1 virtual machine.
19. Click the Console tab.

You should see the media node booting up. Wait for the screen to stop refreshing and until you see the login prompt read ciscoecp_
followed by a string of numbers and letters. (NOT localhost) When the screen stops refreshing click inside the window and press
your Enter/Return key. It will take a few minutes for the node to fully boot up after powering on.
Lab Guide
Cisco dCloud
20. Login with admin/cisco.
21. When prompted for enter cisco.
22. Enter a new password of dCloud123! (will need to be entered twice)
23. After a successful password reset, press enter on the security warning.
24. Arrow to Edit Configuration and press Enter.
NOTE: In production, if you were configuring a dual NIC, you would configure option 5 as well.
25. Press Enter to proceed.
26. Press Enter to choose Static.
27. Enter the following parameters from the table below.
Video Mesh Node Configuration
Hostname vmn1
Domain dcloud.cisco.com
IP Address 198.18.135.21
Mask 255.255.192.0
Gateway 198.18.128.1
DNS 198.18.133.1
NTP 198.18.128.1 (Scroll down to find. Also clear the other NTP servers)
Video Mesh Node Configuration
Lab Guide
Cisco dCloud
Video Mesh Node Configuration(con’t)
21. Highlight Save and press Enter.

22. Press Enter to Save Changes & Reboot.
23. Press Enter to select Done.
24. To release your mouse out of the console window, press the Control+Alt keys.
25. You can minimize the vSphere Client.
NOTE: Keep in mind when registering the Video Mesh Node below, it will take about two minutes to reboot.
Configuring the Video Mesh Node Control Hub
You will now add a new Video Mesh Node to the Customer Organization for use with Cisco Webex Meeting Services.
2. Within the portal, on the left-hand menu, click Services.
3. Under Video Mesh, click Set up.
4. Keep Yes, I’m ready to register my Video Mesh Node and click Next.
Since this is the first node and cluster, you’ll need to create a new cluster.
5. Select the radio button for Create a new cluster.
6. In the first box enter: Video Mesh Cluster 1

7. In the second box enter: vmn1.dcloud.cisco.com
8. Click Next.
9. Read over but leave the Service Configuration settings as is and click Next.
Lab Guide
Cisco dCloud
10. Leave the Upgrade Schedule settings as is and click Next.
11. Click Next on the SIP TLS Configuration page.
12. Click Go to Node. (Read the note below if you received an error during add.)
NOTE: This requires a pop-up to see the web page of the Video Mesh Node. Make sure your browser allows pop-ups or
you will not see the Video Mesh Node webpage. Also, click through warning in Chrome by clicking Advanced and then
Yes to proceed.
13. This opens a new browser tab to the Video Mesh Node. Accept any certificate warnings you may receive. Login with Charles if
needed (cholland@cbXXX.dc-YY.com / dCloud123!). After the page fully opens, check the box next to Allow Access to the
Webex Video Mesh Node.
14. Click Continue.
15. After connecting to the cloud, you will get a Registration Complete screen. Close that browser tab.
After connecting, there is no further configuration to be completed. The Webex Control Hub automatically starts managing the
Video Mesh Node. If you go back to the management portal, the configuration you can do is de-register/deactivate the
node/service, move the node to another cluster, change video quality, or update management email notifications.
Because the lab uses the demo version of the Video Mesh Node, you will get an alarm on the number of CPUs configured. This is
expected and you can ignore this alarm. Also, the firmware will auto-upgrade after connecting to the cloud. During the upgrade, it
will show as an Outage when it reboots a number of times. After the upgrade happens, it will go to Operational.
There is also a local administration page that can be accessed.
1. Browse to https://vmn1.dcloud.cisco.com/setup from Workstation 1.
2. The login will be the CLI username/password set at the initial setup, which in this lab is admin/dCloud123! Enter that and login.
3. The first page you come to is the Overview page. This page includes information on the node as well as its health and
connectivity tests. Later on, when you make test calls, you can come back here to view the call crossing the node.
4. Navigate to Network. On this page you also can update host, NTP, and network settings.
5. Navigate to Troubleshooting. On this page you can send logs to Cisco as well as packet captures. There are also a number of
other tools you can use for troubleshooting purposes. Feel free to look around at the options.
To view the utilization reports on your media node, go to the Analytics tab in the Control Hub. Click Video Mesh from the top right
of the page. For capacity planning and reporting, Cisco Webex Control Hub provides a simple snapshot of the meeting activities
across the organization. They can quickly assess overflows, including where they occurred and how much overflow they had. This
gives the administrator the trending analysis to understand if additional capacity is needed on-premises and to plan for additional
Video Mesh Nodes.
Reports are near real time and are updated roughly every minute. A new adoption report is available that show the types of devices
that are in the different clusters. Unfortunately, the trial organizations that dCloud creates won’t be able to see any reports. Below
are some screen shots of what they would look like.
Lab Guide
Cisco dCloud
Video Mesh Node Reports
Lab Guide
Cisco dCloud
Configuring Unified CM SIP Traffic Routing for Video Mesh
Configure SIP trunks to route SIP dial-in and dial-out for Cisco Webex meetings to Video Mesh Nodes. SIP devices don't support
direct reachability, so you must use Unified CM configuration to establish a relationship between on-premises SIP devices and your
Video Mesh clusters. You can create a trunk routing policy that reflects cluster preferences, and is highly available and resilient to
device failures. If you use Unified CM Session Management Edition (SME), configure trunks on the Unified CM SME and leaf systems
so that inbound and outbound calls are evenly distributed across the Unified CM servers within the Session Management cluster.
Typically, each site will have a dedicated Unified CM cluster associated with it. These clusters will be connected through inter-cluster
SIP trunks. Each cluster will have call-in trunks to the local site for the Video Mesh Nodes.
You can also configure your deployment to handle failure or overflow conditions. This configuration helps if there's an outage or if
the Video Mesh clusters reach capacity. If the SIP meeting or call cannot be established with a cluster, the meeting or call will
overflow to the cloud.
1. Connect back to Workstation 1 (198.18.1.36 – cholland/dCloud123!) and open Chrome (if not already).
2. If not already open to Unified CM, navigate from the home page to Collaboration Admin Links > Cisco Unified Communications
Manager.
3. Select the Cisco Unified Communications Manager link and login with administrator / dCloud123! (should be prepopulated).
First, you will need to create a new SIP Profile.
4. Navigate to Device > Device Settings > SIP Profile and click Find.
Lab Guide
Cisco dCloud
5. Find Standard SIP Profile For Cisco VCS in the list and click the copy icon [ ] next to it.
6. Enter Video_Mesh for the name.

7. Scroll down to the Trunk Specific Configuration and set Early Offer support for voice and video calls to Best Effort (no MTP
inserted).
Early Offer
8. Click Save.
Next, you will create a SIP Security Profile.
9. Navigate to System > Security > SIP Trunk Security Profile.
10. Click Add New.
11. For name enter Video_Mesh.
12. Use the default settings and click Save.
Next, create the trunk to the Video Mesh node.
• In a Unified CM only deployment, add a single trunk.

• In an SME deployment, add a trunk between Unified CM and SME and another trunk between SME and Video Mesh Node.
Both trunks must have the same settings specified below.

14. On the next screen, choose SIP Trunk for Trunk Type.
15. Leave the rest at default and click Next.
Lab Guide
Cisco dCloud
16. Configure the parameters using the table below.
Hybrid Service Trunk Configuration
Device Information > Device Name Video_Mesh
Device Information > Device Pool dCloud_DP
Outbound Calls > Calling and Connected Party Deliver URI and DN in connected party, if available (This setting enables blended identity.
Info Format It allows the SIP Trunk to transmit the enterprise-side party’s directory URI to Cisco
Webex)
SIP Information > Destination Address 198.18.135.21 (HMN address and also keep port at 5060)
SIP Trunk Security Profile Video_Mesh
SIP Profile Video_Mesh
17. Click Save, OK, Reset, Reset, and then Close.
Next, create a new route group for calls to the Video Mesh Node/s.
18. Navigate to Call Routing > Route/Hunt > Route Group and then click Add New.
19. Enter the name Video_Mesh_RG.
20. Change the Distribution Algorithm to Top Down.
21. In the Route Group Member Information section, add the Video_Mesh by selecting it and clicking Add to Route Group.
22. For a backup path, select the SIP_Trunk_To_Exp-C device and click Add to Route Group.
This trunk is used for B2B calls and will be used if the video mesh node route is unavailable or full causing an overflow to the cloud
situation. Using the top down algorithm assures the video mesh node is always used first.
23. Verify the Video_Mesh trunk is listed first in the Selected Devices box and then click Save.
Next, create a new route list for calls to Video Mesh Nodes and Expressway.
24. Navigate to Call Routing > Route/Hunt > Route List and then click Add New.
25. Enter the name Video_Mesh_RL.
26. Set the Cisco Unified Communications Manager Group to Default.
27. Click Save.
28. In the Route List Member Information section, click Add Route Group, and then choose Video_Mesh_RG-[NON-QSIG].
29. Leave the defaults for the other settings, and then click Save and OK.
30. Click Save.
Lab Guide
Cisco dCloud
Next, create a SIP route pattern for the Webex site. You will be creating a default pattern to match all Webex sites.
31. Navigate to Call Routing > SIP Route Pattern and click Add New.
32. For IPv4 Pattern, enter the WebEx URL: *.webex.com.
33. For Route Partition, select Base_PT.
34. For SIP Trunk/Route List, select Video_Mesh_RL.
35. Click Save.
Enabling Webex Entitlements
You will now enable Charles’ Webex entitlements to use later in the lab. (If you already completed the Webex Edge Audio scenario,
you can skip this section.)
1. Go back to the Control Hub and log back in if needed with Charles with these credentials:
• Username: cholland@cbXXX.dc-YY.com
2. Click Users.
3. Select Charles Holland from the list.
4. Under Services, click Meeting.
5. Click the meeting site URL.
6. Click User Privileges.
7. Verify the Person Room and Join meetings from video systems checkboxes are selected. If it isn’t, check the box and click Save.
Enabling Hosting Webex Collaboration Meeting Room Meetings on the Video Mesh Node
Earlier you created a SIP route pattern on Unified CM pointed to the WebEx site *.webex.com. In order for calls to collaboration
meeting rooms (CMR) to be hosted by the Video Mesh node, you must change a setting in the CMR section of the common settings
for the Webex site, to allow the Video Mesh Node to connect to Webex. In the default configuration, CMR meetings will always be
routed out through the expressways and hosted in the cloud.
1. In the Control Hub, click Services.
2. Under Meeting, click the Sites.
3. Select the site in the list and click Configure Site in the fly-out window.
4. Under Common Settings, click Collaboration Meeting Rooms (CMR).
5. At the top of the page for Media Resource Type, choose Video Mesh and click Update at the bottom right.
Lab Guide
Cisco dCloud
NOTE: It takes about 30+ minutes for the configuration to apply after clicking update. You also need to verify the Video
Mesh Node you added earlier has finished all its updates to Services. Also, the Video Mesh card should read Operational
at the bottom of the card.
The configuration is now set to use the Video Mesh Node for on-premises users connecting to a Webex meeting.
Testing On Premise Devices Using Video Mesh Node
In the lab, the quickest way to verify your configuration so that on-prem devices will use the Video Mesh Node for Webex meetings
is to use Jabber on the workstations to make a call into the Webex site and verify if calls are going across the Expressways or not.
1. On Workstation 1, open Cisco Jabber and log in using these credentials (if not already logged):
• Email: cholland@cbXXX.dc-YY.com
• Username: cholland
2. Open another Chrome tab and navigate to Collaboration Admin Links > Cisco Expressway-C. (NOT Connector Host)
3. Login with admin/dCloud123! (should be prepopulated).
4. Navigate to Configuration > Zones > Zones.
You are going to be monitoring the number of calls going across the Expressway. If calls are using the Expressway to go out then you
will see the number of calls for the zones Traversal Client for B2B Video and UCM Neighbor for B2B increase to 1. If that is
happening, calls are not being hosted on the Video Mesh Node. Right now, since there are no calls in progress, the number is at 0.
Now you will make a call to Webex with Jabber.
5. Open Jabber and call meet@cbXXXYY.webex.com.
6. When it connects successfully you see a message displayed that reads: Enter the meeting number, followed by #.
7. Leave the call connected and go back and refresh the Expressway-C zones page.
If the number is still at zero then the Jabber client is using the Video Mesh Node to route the call. However, if the calls increase to 1,
the Expressway is routing the call, which is not the desired result. This could mean the connection from the cloud has not trickled
down or that your configuration has not been setup correctly. As mentioned earlier it could take around 30+ minutes for the settings
to trickle down. Also if the video mesh node is going through upgrades from adding it earlier then it will use the Expressway route
until the video mesh node is fully operational. So you may want to continue on with the rest of the lab and come back later to test.
Remember you can also go to the Video Mesh Node directly https://vmn1.dcloud.cisco.com/setup/ (admin/dCloud123!) and view the
number of calls in progress traversing the node on the Overview page.
8. End the call if it hasn’t already ended automatically. Exit Jabber for now.
Lab Guide
Cisco dCloud
Scenario 7. Webex Calling

Imagine being able to leverage enterprise-grade cloud calling, mobility, and PBX features, along with Cisco Webex Teams for
messaging, Webex Meetings for meetings, and calling from a soft client or Cisco phone. That's exactly what Cisco Webex Calling has
to offer, along with a smooth transition to the cloud for customers with 100 or more users and existing on-premises PBX
infrastructures.
Cisco Webex Calling notes:
• Calling subscriptions for telephony users and common areas
• Secure and reliable cloud services delivered by trusted regional service providers
• The Cisco Webex Calling App for desktop and mobile devices, providing comprehensive calling capabilities for mobile
workers
• Webex Teams access for every user, adding rich unified communications and team collaboration services
• Cisco Webex Meetings as an optional, integrated add-on to provide the premium meetings experiences that enterprise
users expect
• Local Gateway for PSTN
• Sold through the Value Added Reseller (VAR) channel
• Fully Webex branded
• Enterprise must procure PSTN and minutes separately
• Cisco MPP endpoint support only
• Call invocation from Webex Teams client
Configuring Taylor and Rebekah with Webex Calling
1. On Workstation 1 in the Webex Control Hub (https://admin.webex.com) select Users from the left-hand menu. (If not logged in
already use cholland@cbXXX.dc-YY.com and password dCloud123!)
2. Click Rebekah from the user list and click Edit.

3. Check the box for Webex Calling and click Next.
4. Choose dCloud for the Location, leave Phone Number as None, and enter 86022 for the Extension.
NOTE: In the lab you will be using Extension only for the users and features. The Phone Number option is to assign a real
PSTN number to the user’s phone. There are no real PSTN services setup for the lab.
5. Click Finish.
6. In the flyout window, scroll down to Settings and click Calling Behavior.
Lab Guide
Cisco dCloud
There are many different ways of making calls in Teams. By default, the user will be selected for the organization setting, which can
be found on the Settings page. You’ll notice that Rebekah has been configured for Calling in Webex Teams, which is also the
organization setting at the moment. When you added the Webex Calling services and set a phone number, this option was selected
for the user automatically. This is what we need selected in the lab, so no changes are needed.
7. Edit Taylor’s user account—add the Webex Calling service and set his Extension as 86021.
8. For testing purposes later, configure one more user with Webex Calling. Use the Extension of 86024. This will be the user that
will be initiating the calls into the system to test calling features. You can also use the room device configured in a section
coming up in the lab guide.
Configuring a Multiplatform Phone (MPP) for Taylor using Global Discovery Service (GDS)
This feature uses a 16-digit activation code that is generated by Cisco Global Discovery Service (GDS) and the Webex Calling Platform
to onboard and provision the device with the associated Webex platform. When the code is provided to a user/administrator, the
code is entered into the MPP Phone. The MPP phone communicates with GDS and redirects the phone to the hosting platform. The
MPP phone communicates with the Webex platform and uses the activation code to authenticate with the platform. If
authentication is successful, the MPP MAC address is stored onto the platform and the phone is provided with the provisioning
server location. The phone reboots and downloads the user configuration from Device Management.
This feature is supported on the following Cisco MPP devices:
• 6821, 6841, 6851
• 7811, 7821, 7832, 7841, 7861
• 8811, 8832, 8841, 8845, 8851, 8861, 8865
If you have a physical MPP phone, use the following instruction to register it along with other phones you would like to use. If you do
not have a physical MPP phone then the Webex Teams app will suffice for this lab. You can skip to the next section if you just want
to use Webex Teams to make calls.
1. On the Control Hub, click Devices.
3. Choose Existing User and click Next.
4. Search for Taylor Bard, select him from the list, and click Next.
5. Select the device type from the drop-down menu.
6. Keep By Activation Code selected and click Next.
NOTE: If your phone has not been factory reset, do that now. If the phone has already been factory reset and powered
on, reboot the phone to have it attempt the registering process again.
7. Once the phone boots after a factory reset, enter the activation code onto the phone and press Continue.
After a few minutes, the phone should reboot and register. It may take a few minutes before the device is listed on the devices page
in Control Hub after registering.
Lab Guide
Cisco dCloud
NOTE: At this time in Control Hub, the phone device status will always read Status Unavailable. Phone status is coming
soon but hasn’t been released at the time of writing this guide.
Configuring a Room Device with Webex Calling
You can assign Webex Calling telephone numbers to room devices. As with the users you will be assigning and extension since there
is no Cloud Connected PSTN service provider configured for you lab organization.
1. On the Control Hub, click Places.
NOTE: The steps below assume you already added a device in Control Hub earlier. If you don’t have a device added to
Control Hub, follow the steps in the Add a Room Device section in this guide and follow the steps to add a new device. If
your device is still registered to Unified CM for the Webex Edge for Devices scenario then delete the Place created first
and create a new one registered to the cloud. If it was registered to UCM then you will need to factory reset the device to
change the registration back to cloud. Once you have a device registered, come back to these steps. You can also add a
fake device if you just want to go through the steps.
2. Select your device and click Edit in the fly-out window.
3. Choose the Cisco Webex Calling radio button and click Next.
4. Enter 86023 for the extension and click Save.
You now will be able to dial the extensions of your other users from your room device.
Using Software Client with Webex Calling
For your other users, use Webex Teams to make and receive calls. (If you do not have a physical phone for Taylor, use Webex Teams
for him as well.)
1. Open Webex Teams with one of your other users either on your own computer or mobile devices and login. For example,
Rebekah’s login info would be:
• Username: rbarretta@cbXXX.dc-YY.com
Configuring Calling Features
Now that you have the clients installed and logged into you will go through and configure the calling features. You will first go
through and configure everything first and then at the end complete testing.
Lab Guide
Cisco dCloud
Adding New Calling Features
Next, you will be creating the call features. It does take time for these features to be provisioned into the system. Due to the
provisioning time, you will add all the features first and then go back and configure them.
1. In the Control Hub, navigate to Services and click the Features link located on the Call card.
You will notice there is already an Auto Attendant configured. This needed to be created and assigned during the startup of your
session. You will be editing this feature later.
2. Click New Feature and click Hunt Group on the pop-up screen.
3. Use the drop-down menu and choose dCloud from the list.
4. Click Save and Done.

You will assign an extension for the hunt group a little later.
Notice on the pop up that appeared, it takes a minute for the feature to be provisioned, which is why you will go ahead and create
the rest of the features now. At any time, you can click Orders at the top right of the page to view the status of all the
features/orders you are creating.
5. Click New Feature and then click Paging Group.
6. For Location, choose dCloud.
7. Click Save and then Done.
8. Click New Feature and then click Call Queue.
9. For Location, choose dCloud.
10. Click Save and then Done.
Configuring Calling Features
While you are waiting on all the features to provision you can go ahead and start configuring some features now. The first one is the
hunt group.
Configuring Hunt Group
Next, you will configure the hunt group you added earlier. You may want to set up hunt groups in the following scenarios:
• A Sales team that wants sequential routing—an incoming call rings one phone, but if there's no answer, the call goes to the
next agent in the list.
• A Support team that wants phones to ring all at once so that the first available agent can take the call.
1. If the hunt group is not yet showing on the call features page, refresh the page.
2. On the Hunt Group card, click the ellipsis [ ] and then click Edit.
Lab Guide
Cisco dCloud
You’ll notice it will open a new tab to the Webex Calling portal. This will be the case for each feature you created. From here on
instead of going to Control Hub and clicking Edit, you will configure everything within the Webex Calling portal now.
3. Enter a relevant name for the hunt group such as Hunt Group.
4. For the Phone Number, choose (empty) from the drop-down list.
5. Enter 86030 for the Extension.
6. Enter a name for Caller ID.
Hunt Group Configuration
7. At the bottom right of the page, click Save.
8. After the page refreshes, click Call Routing from the menu on the left.
9. Select the radio button for One at a time. By default, Top Down is selected. This option will always start in order of the
assignment set in the Phones section. The call will ring the users one at a time, always starting with the same user and ringing in
the same order. The user configured at the top of the Assigned list will ring first, followed by the users listed beneath, in
sequential order. To view more information on the types of call routing and what each does, visit Calling Admin Portal – Modify
Hunt Group online. This page also gives an overview of hunt groups and explains in more detail the configuration, including
configuration not covered in the lab.
10. Check the box for Advance after a set number of rings and configure 3 rings.
12. After the page refreshes, click Phones from the menu on the left.
13. Click within the Find and Assign search and choose Taylor Bard and Rebekah Barretta.
15. After the page refreshes, click the [ ] at the top right of the page to close the hunt group configuration.
Lab Guide
Cisco dCloud
Configuring Call Queue
Call queues temporarily hold calls in the cloud when all users (agents) assigned to receive calls from the queue are unavailable.
Queued calls are routed to an available agent when he/she is no longer on an active call. Each call queue is assigned a Lead Number,
which is a telephone number outside callers can dial to reach users assigned to the call queue. Call queues are also assigned an
internal extension, which can be dialed internally to reach users assigned to the call queue.
In the lab you will be configure a basic call queue. To view more information on call queues as well as more advanced configurations,
click here.
1. From within the Webex Calling portal, click Advanced Services.
2. In the Call Routing list, click Call Queues.

3. Click Assign for the one call queue you configured earlier from Control Hub.
4. Enter a relevant name for the call queue, such as Call Queue.
5. For the Phone Number, choose (empty) from the drop-down list.
6. Enter 86031 for the Extension.
7. Enter a name for Caller ID.
Call Queue Configuration
9. After the page refreshes, click Queue Settings from the menu on the left.
10. Check the box for Play ringing tone to callers when their call is sent to an available agent.
11. Check the box for Mark calls as overflow after queue wait time and enter 80 into the box.
12. Expand Advanced Settings.
13. Check the box next to Welcome message is mandatory.
14. Toggle on Estimated Wait Message for Queued Calls.
Lab Guide
Cisco dCloud
15. Select the radio button for Announce Queue Position.
16. Toggle on Hold Music.
18. After the page refreshes, click Call Routing from the menu on the left.
19. Under Call Routing, choose One at a time.
Now, you need to assign licenses and agents to add to the queue.
21. After the page refreshes, click Agents from the menu on the left.
22. Click within the Find and Assign search and choose Taylor Bard and Rebekah Barretta.
24. After the page refreshes, click the [ ] at the top right of the page to close the call queue configuration.
Configuring Auto Attendant
Auto Attendant ensures calls are answered and that callers' needs are met. You can add greetings, set up menus, and route calls to
an answering service, a hunt group, a voicemail box, or a real person. You can create a 24-hour schedule or provide different options
when your business is open or closed. You can even route calls based on caller ID attributes to create VIP lists or handle calls from
certain area codes differently.
As mentioned earlier, Auto Attendant was already created for you at the beginning of the lab. Adding a new Auto Attendant would
be like any of the features you configured earlier.
2. In the Call Routing list, click Auto Attendants.
3. You will be taken to the Auto Attendant configuration page. A number and schedule has been created for you. For testing
purposes you will later edit the assigned Time Schedule to ensure calls go through no matter when you are completing the lab.
4. Click Actions and then choose Edit Service.

5. For Extension, enter 86020.
7. After the page refreshes, click Schedule from the menu on the left.
8. On the next screen, click Edit Time Schedule.
9. Under Schedule Events each day is represented by an event name. It starts with 1 being Sunday, 2 being Monday, and so on.
Click Edit for the event that corresponds to the day you are taking the lab. For example, if you are taking the lab on Thursday,
click Edit for Event 5.
10. To verify you choose the correct event, click Reoccurrence. You should see the day chosen under Recur On.
11. Click Event.
Lab Guide
Cisco dCloud
12. Change the Name to read the day (Sunday, Monday, Tuesday, etc.) to make it easier to determine later.
13. For lab purposes check the box next to All Day Event. This will ensure no matter what time it is the calls will go through when
you test later.
14. Click Save.
Feel free to edit the events for other days of the week, especially if you plan on using the lab on other days.
15. After editing the days of the week, click Save.
16. At the bottom right of the Schedule page click Save.
17. After the page refreshes, click Menu from the menu on the left.
18. Use the drop-down menus for each number, configure the following parameters from the table below for Business Hours.
Auto Attendant Business Hours Configuration
0 Exit Menu
1 Dial By Extension
2 Dial By Name
3 Transfer To Extension Without Prompt
Enter 86021 for the Number
Description: Dial Taylor
4 (need to click Transfer To Extension Without Prompt
Show More to Enter 86030 for the Number
view) Description: Hunt Group
5 Transfer To Extension Without Prompt
Enter 86031 for the Number
Description: Call Queue
Lab Guide
Cisco dCloud
You will be testing those configured numbers later but feel free to configure other numbers if you would like for testing. To view
more information about configuring an Auto Attendant, including a description on what each option does and how to configure a
custom greeting, click here.
20. After the page refreshes, click the [ ] at the top right of the page to close the auto attendant configuration.
Next you will configure a voice portal password so you can record a prompt for the auto attendant.
21. Click Advanced Services and then the Site Package Settings tab.
22. In the list, click Voice Portals.
23. For the number listed on the Voice Portals page, click Actions > Edit Service.
24. For extension, enter 86032.
25. Enter 1357 as the New passcode and Confirm new passcode.
26. Click Save.

27. After the page refreshes, click the [ ] at the top right of the page to close the voice portal configuration.
Lab Guide
Cisco dCloud
Now you can dial in to record your voice prompts for the auto attendant.
28. From your phone dial the extension number (86032) for the Voice Portal.
29. Press the [*] key when prompted and enter your passcode.
30. For the mailbox ID, enter the extension for the Voice Portal (86032) and then the pound key [#].
31. Enter the 1357 passcode and then [#].
32. Press 1 to change the Auto Attendant greeting.
33. Press 1 to change the business hours greetings.
34. Press 1 to change the greeting.
35. Record the new greeting to greet callers to your company and list the options configured above. When finished recording, press
#.
36. After recording, press 2 to listen to the greeting you recorded or 1 to re-record the greeting.
37. Hang up when you are finished creating the greeting for the auto attendant.
Configure Call Pickup
Group Call Pickup enables a user to answer any ringing line within their pickup group. A pickup group is a group administrator-
defined set of users within a Site, to which the Call Pickup feature applies. The Group Call Pickup feature requires Call Pickup groups
to be added, modified, and removed as well as assigning specific users to that pickup group.
Before the Call Pickup service can be used, the following conditions must be met:
• A user can only be assigned to one Call Pickup group.
• A Call Pickup group may only have assigned users from the same site.
• A site may have multiple Call Pickup groups.
• Call Pickup group names must be unique.
• Assigning a user to a Call Pickup group removes the Barge-in restriction if enabled for that user.

2. Under Call Routing, click Call Pickup.
3. In the pop-up, choose the dCloud location and click Select.
4. Click Add.
5. Enter a Group Name and then click Save.
6. When the page refreshes, in the Available section, check the boxes for Taylor and Rebekah and click the right arrow [ ] to
move them to Assigned.
7. Click Save.
Lab Guide
Cisco dCloud
Configuring Call Park
The Call Park feature allows a defined group user to park a call against other available members of a Call Park group, which may be
picked up by other members of the group at their phone.
What to know before getting started:
• A user can only be assigned to one Call Park group.
• A Call Park group may only have users from same site.
• A site may have multiple Call Park groups.
• Call Park group names must be unique.

2. Under Call Routing, click Call Park.
3. Click Add.
4. Enter a Group Name and then click Save.
5. After the page refreshes, in the Available section, check the boxes for Taylor and Rebekah and click the down arrow [ ] to
move them to Assigned.
6. Click Save.
Note there is Global Settings at the top of the page, which you can configure settings for all the Call Park groups that are configured.
Configuring Paging Group
The Group Paging service allows a user to set up a one-way call to a group of up to 75 target users by dialing a number or extension.
The Group Paging service makes a simultaneous call to all the assigned targets and announces to the originator that the system is
ready for paging. After speaking, the originator ends the page by hanging up the call.
2. Under Productivity Services click, Group Paging.

3. Click Edit next to the one paging group you configured earlier in the Control Hub.
4. Give the paging group a Name.
5. For Extension, enter 86033.

6. To the right of the page, under More Options, click Paging Targets.
7. In the Available section, check the boxes for Taylor and Rebekah and click the down arrow [ ] to move them to Assigned.
9. At the bottom right on the main paging group page, click Save.
Lab Guide
Cisco dCloud
Testing Calling Features
Now that the calling features have been configured, it’s now time to test them.
NOTE: To test Webex Calling features, the test user must be set up for Webex Calling. Please use Taylor and Rebekah
for this section.
You should have Taylor configured for a phone or logged him into a Webex Teams. Rebekah should be logged into a
Webex Teams client as well. As mentioned earlier, since Taylor and Rebekah have been configured for all the calling
features it would be best if you have another user configured and logged into a Webex Teams client to initiate all the calls.
If that’s not possible, you can call in with either Taylor or Rebekah. All tests below will assume a third user calling into
the system and Taylor and Rebekah answering the calls.
Testing Auto Attendant, Hunt Group, and Call Queue
Earlier, when you configured the auto attendant you recorded a greeting and configured the options. As a reminder, the options
were configured with the following parameters from the table below.
0 Not Used
1 Dial By Extension
2 Dial By Name
3 Dial Taylor directly
4 Transfer to Hunt Group which Taylor and Rebekah are called
5 Transfer to Call Queue which Taylor and Rebekah are called
Ideally you need three users to fully test these features. You have configured Taylor and Rebekah for the hunt group and call queue
so a third user calling in can test routing to both users.
1. Dial the extension of the Auto Attendant (86020) with your third user.
2. Test option 1 and enter an extension of either Taylor or Rebekah. The call should forward to the extension.
3. Test option 2 and using the keypad enter the first or last name of Taylor or Rebekah. The call should forward after the first three
characters are entered. Answer the call. If you decline, the call will be sent to voicemail.
4. Test option 3. Taylor’s phone should ring.

5. Test option 4. Taylor or Rebekah’s phone/client should ring (depending on who was first in the list), decline the call and observe
the call fall over to the other user.
6. Test option 5. Observe the following points:

• You should hear a voice prompt telling you to wait for the next available agent. It will also notify you of your position in the
queue.
• Taylor or Rebekah’s phone/client will ring.
Lab Guide
Cisco dCloud
• If you decline the incoming call, it will fall over to the other agent.
• If you let the call ring, it will continue to prompt the user based on the timer you sent.
• After the time you set, it will fall over to the other user to answer and eventually register a busy signal if no one answers.
Feel free to test any other options you configured for the Auto Attendant.
Testing Call Pickup
Next you will test Call Pickup. Ideally you need three users to fully test this feature. You have configured Taylor and Rebekah in the
pickup group. In this case you need a third user to dial one of them and the other user, not called, to initiate the pickup.
1. Initiate a call to Rebekah from your third user the Webex Teams client.
2. Do not answer with Rebekah. On Taylor’s phone/client dial, *98 to pick up the call.
3. When you are finished, end the call.
Testing Call Park
Next you will test Call Park. Ideally you need three users to fully test this feature. You have configured Taylor and Rebekah in the call
park group. In this case you need a third user to dial one of them, park the call, and pick the call up with the other user or the same
user.
1. Initiate a call to Taylor or Rebekah from your third user the Webex Teams client.
2. Answer the call on the phone or client. You can park the call as follows:
• Answer the call on the phone. Press the Transfer softkey or physical transfer button. Enter *68 and then when you hear the
long beep enter the five-digit extension of the user you just called or another user and then the # key. The call will be
parked at that extension and you will hear hold music on the dial-in user’s client.
• Answer the call on the phone. Press the Park softkey. Press # key and when you hear the long beep, press the # key again to
park the call on the user’s extension.
• Answer on the client. Click the More button [ ], and choose Transfer. Enter *68 and then when you hear the long beep
enter the five-digit extension of the user you just called or another user and then the # key. The call will be parked at that
extension and you will hear hold music on the dial-in user’s client.
3. To retrieve the call from the phone or client, dial *88. When prompted, enter the five-digit extension of where you parked the
call followed by the # key.
4. End the call when you are finished.
Lab Guide
Cisco dCloud
Testing Paging Group
Next you will test the Paging Group feature, possibly. This feature may or may not work in your environment. You will need to have
to satisfy the following requirements:
• Paging requires multicast routing using the IP address 239.192.16.240. Make sure that IP address is free for multicast
routing only.
• Paging groups only work with the Cisco IP Phone 7800 or 8800 Series.
• You need at least two users in the group that are assigned to one of the phone types listed in the previous bullet. At least
one of the phones need to be registered. In the lab, you assigned Taylor and Rebekah to the paging group so each of these
users need to have a 7800 or 8800 phone registered to them.
• If one of the requirements above are not met, the paging group will not work and you will receive a busy tone or a message
stating the number is not available.
1. Initiate a call from Taylor’s MPP phone to the Paging Group extension (86033).
2. You will hear Paging come through the speaker on all the other phones in the group. After a few seconds of hearing paging on
the other phones, you will hear Paging system ready on Taylor’s phone. You then can speak on Taylor’s phone and hear your
voice come through on the other phones.
Local Gateway
Up until now you have been testing all internal calls with no PSTN access. In this section you will explore the local gateway feature.
With this feature you are able to use your existing PSTN and provide PSTN connectivity to your cloud registered phones. There are a
few options when configuring a local gateway for your site. In this lab you will configure a local gateway that uses Unified CM for call
routing from/to the PSTN. This is shown below.
Local Gateway with Cisco Unified CM
Lab Guide
Cisco dCloud
The call routing in Unified CM has been completed for you so you can concentrate on configuring the local gateway. The call flow
into the dCloud session works as follows:
a. Call comes to a dCloud PSTN DID number.
b. The dCloud gateway translates that number into a four-digit extension and sends it to Unified CM.
o These numbers can be found in the Phone Numbers sections in your dCloud session’s details page. They can
also be found on the desktop of Workstation 1 in a text file named DN_to_DID.txt.
c. Unified CM translation pattern matches on four of those extensions and prefixes the number with an 8.
o Four extensions used in the lab are: 6020, 6021, 6022, 6023.
d. That translated number matches a route pattern that sends the call to the trunk pre-configured for the local gateway.
o The pre-configured trunk uses a SIP Trunk Security Profile configured for incoming port 5065.
First task is creating the local gateway in the Control Hub. You will need the information provided after creation to build your local
gateway.
1. In Control Hub, navigate to Services and click the Locations link on the Call card.
Each location can be assigned a local gateway. In the lab, you have one location that you will be configuring a local gateway for. The
gateway is hosted in your dCloud session.
2. Select the dCloud location.
3. On the fly-out window, click Local Gateway.
4. Click Edit > Continue > Manage.
5. Using the drop-down menu, choose Create New Local Gateway.
6. Enter dCloud for the name for the gateway and then click the green checkmark [ ]. (Ensure you enter a name before clicking
the checkmark.)
7. After a few moments, information will be displayed on the page. You will need this information to configure the local gateway.
Capture the info now. It’s recommended to open a text 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.
Lab Guide
Cisco dCloud
Sample Local Gateway Config
8. Once you gathered the information, scroll to the bottom of the pop-up window and click the link that reads Retrieve Username
and Reset Password.
You will receive a pop-up message that says your password will be reset. This is okay since this is the first time you are retrieving the
username and password. However, it is very important to understand that any time you click this link, it will reset the password. If
you already have a local gateway configured with a previous password, then this reset will break the local gateways connection to
Webex. So you will want to keep this information in a safe place and not lose it.
Lab Guide
Cisco dCloud
9. Click Yes on the pop-up message.
10. Capture the Username and Password. You will also use this during the local gateway configuration.
Sample Local Gateway Username and Password
11. One you are finished capturing the username and password, click Done.
12. After gathering all the information, click Back.
13. Choose dCloud on the Local Gateway drop-down menu.
14. Check the two boxes that appear and then click Save.
Local Gateway Configuration
Now you will configure your local gateway with the information you received in the previous section.
NOTE: For easier config so you can copy and paste, all the commands can also be found in a text document on the
desktop of Workstation 1 named LGW_Config.txt.
1. Connect to Workstation 1 and open PuTTY using the icon on the desktop [ ]. (if you are VPNed into the dCloud session, you
can also use your local SSH client.)
2. Double click the Local Gateway saved session to SSH to the local gateway at 198.18.133.226.
3. Login with admin / dCloud123!
4. Using the configuration below you will create a dummy PKI Trustpoint and call it dummyTp. Assign the trustpoint as the default
signaling trustpoint under sip-ua. cn-san-validate server is needed to ensure that 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
Lab Guide
Cisco dCloud
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 setup. Finally disable TLS v1.0 and v1.1 by enabling v1.2 exclusivity as shown in the table below.
Local Gateway Trustpoint Configuration
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
end
Local Gateway Trustpoint Configuration
5. The default trustpool 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.
Lab Guide
Cisco dCloud
Local Gateway Certificate Configuration and Verification
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
6. Enter the following commands to turn on the Local Gateway/CUBE application on the platform.
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 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
exit
allow-connections sip to sip
media statistics
media bulk-stats
no supplementary-service sip refer
no supplementary-service sip handle-replaces
fax protocol pass-through g711ulaw
stun
stun flowdata agent-id 1 boot-count 4
stun flowdata shared-secret 7 104D000A061811021F0725282D3B303A
sip
g729 annexb-all
early-offer forced
end
Explanation of Commands above:
ip address trusted list – Toll Fraud Prevention
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 Information section of the Configuration Guide for
Cisco Webex Calling Customers document according to the regional Webex Calling data center the customer is connected to (North
Lab Guide
Cisco dCloud
America, EMEA, Australia, Beta). The configuration on the previous page includes all the existing Webex data centers as of writing of
this document and as listed in tables 1 to 4 of the configuration guide referenced above.
Lab Guide
Cisco dCloud
media statistics
Enables media monitoring on the LGW.
media bulk-stats
Enables the control plane to poll the data plane for bulk call statistics.
Allows this platform to bridge two VoIP SIP call legs. It is disabled by default.
no supplementary-service sip refer and no supplementary-service sip handle-replaces
Disables REFER and replace dialog ID in Replaces header with the peer dialog ID.
Enables audio codec for fax transport.
stun
Enables STUN globally. When a call is forwarded back to the Webex Calling user (i.e 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
Webex’s 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
Lab Guide
Cisco dCloud
g729 annexb-all
Allow all variants of G729
sip
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.
7. 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, dcloud9001_lgu is used. Make sure you replace that with your Trunk Group OTG/DTG
information.
Sample Configuration Mapping
Lab Guide
Cisco dCloud
Local Gateway SIP Profile Configuration
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=dcloud9001_lgu>"
rule 30 request ANY sip-header P-Asserted-Identity modify "sips:(.*)" "sip:\1"
8. Configure Codec Profile, STUN definition, and SRTP Crypto suite as shown and explained in the table below.
Configuration
voice class codec 99
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
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

Allows both g729 and g711(mu and a-law) codecs for sessions. Will be applied to all the dial-peers.
Specifies SHA1_80 as the only SRTP cipher-suite that will be offered by LGW/CUBE in the SDP in offer and answer. Webex Calling
only supports SHA1_80. This command will be applied to voice class tenant 200 (discussed later) facing Webex.
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.
9. Configure voice class tenant 200 as shown below. However, 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.
Lab Guide
Cisco dCloud
Sample Configuration Mapping
NOTE: Do not use these as they are only shown here for reference. Use the configuration gathered earlier in Control Hub
when adding the Local Gateway. (See tables below.)
• Registrar Domain: 40462196.cisco-bcld.com

• Trunk Group OTG/DTG: dcloud9001_lgu
• Line/Port: dCloud0014_LGU@40462196.cisco-bcld.com
• Outbound Proxy Address: la01.sipconnect-us10.cisco-bcld.com
• Username: dCloud9001_LGU
• Password: %bjQQp*xut
Lab Guide
Cisco dCloud
Local Gateway Tenant Configuration
Configuration
voice class tenant 200
registrar dns:40462196.cisco-bcld.com scheme sips expires 240 refresh-ratio 50 tcp tls
credentials number dCloud0014_LGU username dCloud9001_LGU password %bjQQp*xut realm BroadWorks
authentication username dCloud9001_LGU password %bjQQp*xut realm BroadWorks
authentication username dCloud9001_LGU password %bjQQp*xut 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
The CUBE multi-tenant feature enables specific global configurations for multiple tenants on SIP trunks that allow differentiated
services for tenants.
Registrar server for the Local gateway with the registration set to refresh every two minutes (50% of 240 seconds).
Credentials for Trunk Registration challenge.
Authentication challenge for calls.
no remote-party-id
Disable SIP Remote-Party-ID (RPID) header as Webex Calling supports PAI, which is enabled using CLI asserted-id pai (see below).
Webex servers.
connection-reuse
To use the same persistent connection for registration and call processing.
srtp-crypto 200
Lab Guide
Cisco dCloud
Specifying SHA1_80 defined in voice class srtp-crypto 200.
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.
Media source interface facing Webex.
no pass-thru content custom-sdp”
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.
Webex Access SBC.
Transparently pass across privacy header values from incoming to the outgoing leg.
10. Next, configure the following voice class tenants.
Lab Guide
Cisco dCloud
Local Gateway Voice Class Tenant Configuration
Configuration
! Voice class tenant 100 will be applied on all OUTBOUND dial-peers facing CUCM
session transport udp
url sip
error-passthru
! Voice class tenant 300 will be applied on all INBOUND dial-peers from CUCM
11. Configure the following voice class URIs for URI-based dialing.
Local Gateway Voice Class Configuration
Configuration
! - Defines Webex Access SBC’s signaling VIA port
voice class uri 200 sip

pattern :8934
! - Defines Unified CM signaling VIA port for the Webex Calling trunk

pattern :5065
12. Configure the following voice class server-groups.
Local Gateway Server-Group Configuration
Configuration
voice class server-group 301
ipv4 198.18.133.3 port 5065
The config above defines the Unified CM trunk’s target host IP address and port number of Unified CM Group’s node. Unified CM
uses port 5065 for inbound traffic on the Webex Calling trunk. The trunk and truck security profile with port number has been
preconfigured for you in the lab.
13. Configure the following outbound dial-peers shown in the table below.
Lab Guide
Cisco dCloud
Local Gateway Outbound Dial-Peer Configuration
Configuration
! - Outbound dial-peer towards Webex
dial-peer voice 201 voip

description Outgoing dial-peer to Webex
destination-pattern .T
session protocol sipv2
session target sip-server
voice-class codec 99
dtmf-relay rtp-nte
voice-class stun-usage 200
no voice-class sip localhost
voice-class sip tenant 200
srtp
no vad
! - Outbound dial-peer towards Unified CM’s Webex Calling Trunk

description Outgoing dial-peer to Unified CM Webex Calling Trunk for inbound from Webex
session server-group 301
dtmf-relay rtp-nte
no vad
14. Configure the following dial-peer groups (DPG).
Local Gateway Dial-Peer Group Configuration
Configuration
! - Define dial-peer group 200 with outbound dial-peer 201 as the target for Unified CM --> LGW --> Webex Calling path
voice class dpg 200

dial-peer 201 preference 1
! - Define dial-peer group 300 for outbound dial-peer 301 for Webex --> LGW --> Unified CM path
voice class dpg 300

15. Configure the following inbound dial-peers.
Lab Guide
Cisco dCloud
Local Gateway Inbound Dial-Peer Configuration
Configuration
! - Inbound dial-peer for incoming Webex call legs

description Incoming dial-peer from Webex
destination dpg 300
incoming uri via 200
dtmf-relay rtp-nte
srtp
no vad
! - Inbound dial-peer for incoming Unified CM call legs with Webex as the destination

description Incoming dial-peer from Unified CM for Webex
destination dpg 200
dtmf-relay rtp-nte
no vad
That completes the local gateway configuration. Now save.
16. Type end at the command prompt.
17. To save type copy run start and press Enter/Return twice.
NOTE: To view all the local gateway configuration in one place, go to Appendix D.
Before testing the configuration, verify the local gateway shows online in Control Hub.
18. Go back to the Control Hub and login if needed (cholland@cbXXX.dc-YY.com / dCloud123!).
19. Navigate to Services and click Locations on the Call card.
20. Click the dCloud location.
21. On the flyout window under PSTN Connection you should see dCloud for Local Gateway. Click Local Gateway.
22. Choose Edit > Continue.

23. Select dCloud from the drop-down menu and click Manage.
24. For Status it should read Online. After verifying the status, click the X to close the window.
Lab Guide
Cisco dCloud
Online and Registered Local Gateway
Local Gateway Testing
Now that you have a fully configured local gateway, you can test calling in/from the PSTN as well as call devices registered to Unified
CM.
Call from MPP/Webex Teams to on-prem Jabber client.
1. Open Jabber on Workstation 1. (If you didn’t login previously in the lab, login with cholland@cbXXX.dc-YY.com. Once you get a
username/password prompt, enter cholland/dCloud123! for the username/password.)
2. From you MPP or Webex Teams client, dial 972-555-6018.
3. Answer the call on Jabber.

You’ll notice that the caller ID for the user will be a full E.164 number that is not assigned to the user. This is expected. Since the
users were configured with extensions only the system will use the main number configured for the location. To view the main
number configured for the dCloud location navigate in Control Hub to Services and click Numbers on the Call Card. You’ll notice the
caller ID number you saw earlier is listed with the indicator of [ ]. This number also happens to be configured for the Auto
Attendant.
Another thing to note is Webex Calling will add a +1 to the beginning of the number called. This is because this location was
configured for the United States. If the location was configured for another region, it would send the called number with a plus (+)
and the country code.
4. End the call.
Call from on-prem Jabber client to MPP/Webex Teams.

1. From the Jabber client, dial one of your users or auto attendant extensions. Extensions you configured in the lab were:
a. 86020 – Auto Attendant
b. 86021 – Taylor Bard

c. 86022 – Rebekah Barretta
d. 86023 – Room Device
Lab Guide
Cisco dCloud
2. Answer on the MPP or Webex Calling client.
This call is routed over the trunk that pre-configured for you. Also, a pre-configured route pattern of 860XX that points to a route list
configured with this trunk is used in the call flow.
3. End the call.
Call from PSTN to MPP/Webex Teams.
Now you will test calls from/to the PSTN. The DID numbers to dial from the PSTN are located in your dCloud session details. They are
also located on the desktop of Workstation 1 in a text file named DN_to_DID.txt.
1. With the DID number, dial one of your users or the Auto Attendant using a real cell or desk phone.
2. Answer the call on your Webex Teams app/device.
3. 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. Unified CM has a pre-configured translation pattern configured that will prefix an eight (8).
d. With the translation it will hit the preconfigured 860XX route pattern that points to a route list that has the local gateway
SIP trunk in it. The SIP trunk is configured into a route group and added to the route list.
e. Call is routed through the local gateway into Webex and to the extension of the user.
Call from MPP/Webex Teams 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 will route the number as is and not add +1. Then the call flow for EMEAR and APJ sessions
in Unified CM is as follows:
• Call comes into Unified CM and depending on the datacenter hits either the 00.44! (UK) or 00.65! (SNG) translation
patterns.
• The translation pattern will strip the 00 off the number and add a plus (+)
• The now +E.164 number will hit one of the +44/+65 route patterns and route to the dCloud PSTN gateway.
1. With the dialing explanation above dial a PSTN number.

2. Answer the call.
Lab Guide
Cisco dCloud
You’ll notice that the incoming caller ID number will begin with a 919, 408, 44, or 64 number (depending on sessions datacenter).
This is expected due to the way the dCloud PSTN is setup. The caller ID will always show as the DID assigned to the session that
maps to the 7800 DN.
3. End the call.
Local gateway debugging.
To troubleshoot call setup failures on the local gateway, proceed as shown below.
Local Gateway Debugging
Configuration
! - Collecting debugs in Local Gateway’s logging buffer
-----------------------------------------------------------------
LocalGateway#conf t
LocalGateway(config)#no logging console
LocalGateway(config)#no logging monitor
LocalGateway(config)#service timestamps debug datetime msec
LocalGateway(config)#logging buffered 9999999 debugging
LocalGateway(config)#service sequence-numbers
LocalGateway(config)#no logging rate-limit
LocalGateway(config)#exit
! - The following debugs will assist in troubleshooting call failures for this lab:
“debug ccsip message”

“debug voip ccapi inout”
You can view the debugs by issuing the “show log” command.
Lab Guide
Cisco dCloud
Scenario 8. O365 Integrations to Webex Teams

Initial Integration of O365 to Webex Teams
This section will walk through the setup of Webex features with Office 365. In order to complete this section you will need to use
your own O365 site. If you don’t have one available, you can create a trial as follows:
NOTE: If you created the O365 trial and setup users already during Scenario 1 then you can skip to the next section and
continue.
1. On your lab’s Workstation 1, navigate to this url: https://aka.ms/e5trial
2. In the first box, enter the email that you captured earlier in Scenario 1. The email begins with trial.
3. Click Next and then click Create new account.
4. Enter the user info:
• First/Last name: Charles Holland
• Business Phone number can be fake (e.g. 417-555-1234)
• Company name can be anything
• Company size can be any size
• Country or region use United States
5. Click Next.
6. Enter a phone number to verify you aren’t a robot and click Send Verification Code. (It must be a real number that can receive a
text or call.)
7. Enter verification code and click Verify.

8. Enter a domain name. This can be anything you want just make sure to capture the information for later.
9. After checking for availability, click Next when you have chosen an available domain.
10. On Create user ID, you can use Charles user ID as well (cholland).
11. For simplicity, use dCloud123! for the password.
12. Click Sign up.
13. After verification and ID creation, click Go to Setup.

14. Click Get Started and then skip past domain page by clicking the Exit and continue later link.
Lab Guide
Cisco dCloud
15. Note the following when setting up the O365 trial:
• Along with the initial account you create, create at least one more O365 user during the trial setup steps. This additional
account will be used for testing co-editing with O365 documents.
o After arriving at the portal.office.com page, expand Users and click Active users.
o Click [ ] on the Active users page.
o Fill out the information for the user. (To make things simple, feel free to use information from another lab use such as
Anita Perez [aperez].)
o Click Password. Select Let me create the password, set the password to dCloud123! and uncheck Make this user
change their password when they first sign in.
o Click Next.
o Check the box for Office 365 E5 and click Next.
o Click Next on the Optional settings page.
o Click Finish adding and then Close.

• The online Outlook on Word applications will be used for testing. There is no need to install to your computer.
IMPORTANT: Don’t forget to write down the O365 user login information.
Continue on with this section once you completed the initial setup of the O365 trial as well as created at least two users (the user to
create the trial is considered one of the two users).
Cisco Webex allows you to choose which enterprise content management platform your users access in Cisco Webex Teams. You will
now allow users to connect to the O365 trial you created earlier.
1. In Webex Control Hub, navigate to Services and click Settings on the Message card.
2. Scroll down to the Content Management section and click Edit Settings.
3. Check the box for Microsoft and select the radio button for Enable linked folders.
4. Enter the domain you created with your trial e.g. trialdomain.onmicrosoft.com.
5. Click Save.
6. Back on the Content Management section select the radio button for Globally enable all users and then click Yes. (You could
optionally enable individual users for this but for lab purposes it’s quicker to enable globally.)
Lab Guide
Cisco dCloud
Synchronize Azure Active Directory Users into Cisco Webex Control Hub
NOTE: If you jumped down to this section to get the O365 trial setup processes started then you can stop here and jump
back to Scenario 2 to continue on with the lab. It may take upward to ~60 minutes before OneDrive and SharePoint are
fully ready in O365. You will not be able to complete the ECM section until those are ready on the O365 site. To verify if
they are ready, you can go to the O365 admin center (admin.microsoft.com) and click the menu icon [ ] and if you see
Setting up… for OneDrive [ ] and/or SharePoint [ ] then you will need to go through the ECM section.
You have multiple ways of creating users in Control Hub – individually, through CSV, or directory synchronization. In this section, you
will focus on the setup of synchronizing Azure Active Directory (Azure AD) with Control Hub. With syncing to Azure AD, there are no
on-premises infrastructure or connectors required. This integration keeps your user list in sync whenever a user is created, updated,
or removed from the application in Azure AD. You also have the ability to synchronize an on-premises Active Directory to Control
Hub using the directory connector installed on a domain computer in your on-premises environment. These steps are covered in
Appendix C.
The integration between Azure Active Directory users and Webex Control Hub uses the System for Cross-Domain Identity
Management (SCIM) API. SCIM is an open standard for automating the exchange of user identity information between identity
domains or IT systems. SCIM is designed to make it easier to manage user identities in cloud-based applications and services. SCIM
uses a standardized API through REST.
Add Cisco Webex from the Azure Application Gallery
You initially created a couple users in O365 earlier during the trial creation. Now it’s time to create the application to use for syncing
to the Control Hub.
1. Navigate to https://portal.azure.com and log in as your O365 administrator.
2. In the search box at the top, search for Enterprise applications and select Enterprise applications from the list.
3. Click New application.

4. In the Add from the gallery section, search for Cisco Webex.
5. In the search results, highlight and then click Add.
Configure Azure AD for User Synchronization
Use this procedure to set up provisioning from Azure AD and obtain a bearer token for your organization. The steps cover necessary
and recommended administrative settings.
First you will need to obtain your organization ID from the Control Hub.
1. Go back to the Webex Control Hub and at the bottom of the left hand menu click the customer name (CbXXX.Dc-01.Com XXXXX
LB Dcloud-Webex-Org).
2. Copy the Organization ID listed on the Info page.

3. Go back to the Azure portal and select Provisioning from the left hand menu.
Lab Guide
Cisco dCloud
4. Change the drop-down menu to Automatic.
5. In the Tenant URL box enter https://api.ciscospark.com/v1/scim/{OrgId}
a. Replace {OrgId} in the URL with the organization ID you obtained earlier. i.e.
https://api.ciscospark.com/v1/scim/1c618175-e42a-4101-acdd-3ee603811ab2
6. Follow the steps below to get the Secret Token:
a. In a new browser tab or window and navigate to

https://idbroker.webex.com/idb/oauth2/v1/authorize?response_type=token&client_id=C4ca14fe00b0e51efb414ebd4
5aa88c1858c3bfb949b2405dba10b0ca4bc37402&redirect_uri=http%3A%2F%2Flocalhost%3A3000%2Fauth%2Fcode&s
cope=spark%3Apeople_read%20spark%3Apeople_write%20Identity%3ASCIM&state=this-should-be-a-random-string-
for-security-purpose
b. If prompted, sign in as Charles Holland (cholland@cbXXX.dc-YY.com / dCloud123!).
c. Ignore the This site can’t be reached error page received, this is normal.
d. In the browser address bar, copy the access_token listed in the URL string between Token= and the &token. This
generated bearer token is valid for 365 days (after which it expires).
Access Token
NOTE: It’s recommend to save this token in a safe place for your records. If you lose it or it expires, you will need to
complete the process above to obtain a new bearer token.
7. Back in the Azure portal, copy the access token copied above into the Secret Token box.
8. Click Test Connection. You should receive a successful message after the test.
9. Enter cholland@cbXXX.dc-YY.com in the Notification Email box and check the box for Send an email notification when a failure
occurs.
10. Click Save.
11. Expand the Mappings section.
12. Click the Synchronize Azure Active Directory Users to Cisco Webex link to view the default mappings.
13. Keep the default settings and click the X at the top right of the page to go back to the Provisioning page.
It is recommended to use the default mapping and not change any settings. By default, userPrincipalName in Azure AD maps onto
email in Control Hub. If you make any changes and need to revert them, you can check the Restart default mappings box to bring
back to the default settings.
14. Scroll down and toggle Provisioning Status to On.
15. For Scope, choose Sync only assigned users and groups (default). (if scope isn’t visible: click Save, navigate from the
Provisioning page, and come back.)
Lab Guide
Cisco dCloud
16. Click Save (if possible).
Add Users to Application in Azure AD
If you didn't choose all users and groups for the provisioning scope, use this procedure to choose users that you want to synchronize
to the Webex cloud. This option lets you create a subset of users to access any applications in your Webex organization.
Azure Active Directory uses a concept called Assignments to determine which users should receive access to selected apps. In the
context of automatic user provisioning, only the users and/or groups that are Assigned to an application in Azure AD are
synchronized to Control Hub.
1. Within the Cisco Webex application, click Users and groups in the left-hand menu.
2. Click Add user.
4. On the initial O365 trial you get a basic set of Azure features. The basic features do not include group assignment. Because of
that you will see the warning that reads Groups are not available for assignment due to your Active Directory plan level in the
Groups option. So, for now you will add the users individually.
3. Click Users and click all the users in the list. Do not click the room device if you created one earlier.
4. After selecting each user, click Select and then Assign.
5. The users will sync incrementally, which by default is 40 minutes. To force a sync, go to the Provisioning page, toggle
Provisioning Status to Off and click Save. Then toggle Provision Status to On and click Save again.
6. If prompted, click Yes to restart synchronization.
7. Click the Refresh icon [ ]. You should see users with the number totaling the users you added to the application earlier. If you
expand View provisioning details you should the last completed cycle time.
8. After the sync, go back to the Control Hub and click Users. You should now see the O365 users you added to the application in
the user list.
Setting Users Passwords
In order to test the O365 integrations, you will need to set the passwords for the users synced from O365 to Control Hub.
1. If you created an Auto-Assign template in Scenario 1 then the Messaging and Meeting services will be configured automatically.
Click Save and Finish. If you didn’t configure an Auto-Assign template then you need to select each user, click Edit, and under
the Messaging column for Webex Teams as well as all the boxes in the Meeting column. Then click Save and Finish.
2. You need to login to that user’s O365 mailbox in order to activate the Webex account.
3. To login to the onmicrosoft.com account, browse to https://outlook.office365.com/ and login. (Its recommended to use another
browser or private/incognito mode for each user.)
4. Set the time zone of the location you are currently in.
5. To activate the Webex Teams account, find the email from Cisco and select it.
6. Click the Activate button inside the email.
Lab Guide
Cisco dCloud
7. Set your password to dCloud123! and click Save & Sign In.
8. Complete the same steps for the other users that you configured to activate their Webex Teams accounts.
Deploying Cloud-Based Hybrid Calendar Service for O365
Webex Teams can utilize the Hybrid Calendar service using O365. No Expressway-C connector host is required in this setup.
Connecting Control Hub to O365
1. In the Webex Control Hub navigate to the Services page.
2. Click Set Up on the Hybrid Calendar Office 365 card.

3. Click Authorize on the Hybrid Calendar setup screen.
4. Enter/select the admin user onmicrosoft.com email address you used to setup your O365 trial with and then click Next.
5. If prompted, enter the password you created and then click Sign in.
6. Click Accept to grant permissions to the Webex Teams Calendar Service.
7. Enter an email addresses of one of the onmicrosoft.com users you setup and click Test.
8. Click Done.
Enabling the Hybrid Calendar Service with O365 for Users
1. Navigate to the Users page in Control Hub and select one of the O365 users.
2. Click the Calendar Service.
3. Toggle on the service [ ] and click Save.
4. Wait for the Calendar Service to show Activated. (For testing purposes, you can just enable one O365 account.)
Enabling the Hybrid Calendar Service with O365 for Devices
Create the room device on O365.
1. Browse to the Microsoft 365 admin center (admin.microsoft.com) and login using your onmicrosoft.com admin account.
2. Navigate to Show all > Resources > Rooms & equipment and click Add.
3. Leave the Type as Room.
4. Configure a Name and Email. Take note of the email address.
5. Click Add and then Close after it finishes adding.

Add/Edit the place in Control Hub.
6. Navigate to Places in Control Hub.
Lab Guide
Cisco dCloud
Control Hub, go to Add a Device section and follow the steps to add a new device. If your device is still registered to
Unified CM for the Webex Edge for Devices scenario then delete the Place created first and create a new one registered
to the cloud. Once you have a device registered, come back to these steps. You can also add a fake device if you just
want to go through the steps.
7. Select the place you created earlier and then click Edit from the fly-out window. (If you did not register a room device, follow
the procedure in the note above.)
8. Toggle off Calendar and click Save. (If already toggled off, toggle on Calendar, click Next, and skip the next step below.)
9. Click Edit again and toggle back on Calendar and click Next.
10. Enter the email address of the O365 room resource that you configured at the beginning of this section and click Save.
11. Wait for the Calendar Service to become Activated.
Testing the Hybrid Calendar Service with O365
1. Browse to https://outlook.office365.com/ and login with the user you enabled the calendar service with earlier. (This should be
open from before, if not it’s recommended to use another browser or private/incognito mode.)
2. Navigate to the calendar and create a New event.
3. Enter a Title.
4. For OBTP, click within Invite attendees field, type the name of the room device and select it. Also add two or more users in the
invite box.
5. Set the start time for today and a time in the future from what your current time zone is. (Remember you set this when you first
logged into Outlook. You can click the time zone icon to set the time zone as well.) Set the time at least ten minutes in the
future for OBTP and meeting notifications to work.
6. In the Location field [ ], enter one of the scheduling keywords such as @webex:space or @meet. Full list can be found here.
7. Click Send.
8. If you used one of the create-a-space keywords, log into a Webex Teams client like the web client https://teams.webex.com with
your O365 user and verify a space was created. You can also verify in the calendar invite that the Join details are listed.
9. Once you receive the Join notification on the Webex Teams app (six minutes before scheduled meeting), click on the
notification and then Join With Video.
10. On your room device, notice it shows the user has already joined the meeting. Now tap Join to go straight into the meeting in
progress.
You have successfully tested the Cloud-Based O365 Hybrid Calendar Service using the keyword functionality as well as One Button to
Push, meeting lists, and join notifications.
Lab Guide
Cisco dCloud
Testing Enterprise Content Management (ECM) Using O365
At the beginning of this scenario, you completed all the configuration to allow users to connect to their O365 accounts with Webex
Teams in order to share and edit content using OneDrive or SharePoint. If you created an O365, trial you need to verify Microsoft
has completed the OneDrive and SharePoint setup on their end. To verify if they are ready, you can go to the O365 admin center
(admin.microsoft.com) and click the menu icon [ ] and if you see Setting up… for OneDrive [ ] and/or SharePoint [
] then you will need to wait to go through the ECM section. If OneDrive and/or SharePoint is ready for use then the
users will not be able to connect to their own accounts to share file. The first thing is to create an O365 Word document and save it
to OneDrive for use later.
Creating a SharePoint Site and Word Document for Testing
1. Navigate to https://www.office.com and sign in with the O365 administrator account. (You’ll see why later.)
2. Click SharePoint, go through any coachmarks. Click Create site on the next page.
3. Select Team site. Enter a site name and description.

4. For Privacy settings choose Public – anyone in the organization can access this site.
5. Click Next.
6. Add your other users as additional owners and click Finish.

7. After going through the coachmarks, click Documents in the left-hand menu.
8. Click New > Word document.
9. Add some text to the document. The document is auto saved for you. You can rename the document by clicking the name
Document at the top center and entering a new name.
Once you are finished editing the document you will need to sign into Webex Teams desktop client with your O365 user as well as
another user to share the document with so they can edit it too. You can use the Webex Teams clients on Workstations 1 and 2
within the lab for testing. If you already signed in with Charles and/or Anita then sign them out for now and sign in with the O365
accounts.
10. On Workstation 1, after logging into Webex Teams, you will need to connect to the O365 account by clicking on the users
avatar circle and selecting Settings from the menu.
11. Click Accounts and then Add account.
12. Login with the O365 user that created the document earlier.
13. Check the box next to Consent on behalf of your organization and then click Accept.
NOTE: As the O365 admin you can accept the permissions for all the users so they will not be prompted when they login.
If the box is not checked then every user must accept the permissions. Only O365 administrators will get the box to
consent on behalf of the organization.
14. Once authenticated, you will see your cloud account appear. Click Save.
Lab Guide
Cisco dCloud
15. Create a Webex Teams space with your other O365 user/s and start a conversation.
16. Click the paper clip and choose Share from OneDrive or SharePoint Online.
17. Click the user account.
18. Once again click the box next to Consent on behalf of your organization and then click Accept. Again, users will not get the
prompt now to ask for permissions.
19. Under Shared Libraries, click the site you created in SharePoint and then select the document and click Open.
20. Keep People in your organization selected.
21. Check the box next to Allow editing and click Apply.
22. Press Enter/Return to send the document to the space.
23. On Workstation 2, sign into Webex Teams with another O365 user or use the web client (teams.webex.com) in another
browser.
You will need to connect this user to O365 in Webex Teams before you can edit the document.
24. Click on the documents within the space. You will notice it will open the Account window to allow you to connect to the O365
account.
25. Click Add account and sign in with your other O365 user. (Notice that you do not get a prompt to accept the permissions this
time.)
26. After the cloud accounts appear, click Save.
27. Now select the document in the space again. This time the document will open for editing.
28. Edit the document as needed.
29. Go back to Workstation 1 and view the document edits. You will be able to make and see edits from all users in real time.
You can also link the site you created in SharePoint to this space.
30. On the top right of the Webex Teams app, click the ellipsis [ ] and then Files.
31. Click Link to Online Folder.
32. If prompted, select your O365 account and enter the password.
33. After logging in, select your SharePoint site name under Shared Libraries and then click Open.
34. Click Close.
35. You now have two options in the files area, Shared in space, which uses the Webex cloud storage, and Linked folder, which uses
the SharePoint site for storage. Click Linked folder.
You should now see the document you created earlier in SharePoint.
You have successfully tested Enterprise Content Management using O365.
Lab Guide
Cisco dCloud
Scheduling, Starting, or Joining Cisco Webex Meetings from Microsoft Teams
The Cisco Webex Meetings app can help you invite people to your Webex meeting so people can join easily. All that you need to do
is set the Webex site URL for the Webex site that you want your team to use for meetings. You must have a host account on that
Webex site to use this app. If your Webex account is enabled for a Personal Room, you can use the app to share a link to a meeting
in your Personal Room.
Enabling the Cisco Webex Meetings App for Microsoft Office 365
Team owners and team members can see and install the Cisco Webex Meetings app in the Microsoft Teams Store only after the
Global Administrator for Microsoft Office 365 has used the following steps to give permission.
1. Browse to the Microsoft Teams admin center (admin.teams.microsoft.com) and login using your onmicrosoft.com admin
account.
2. Navigate to Teams apps > Permission policies.
3. Click Org-wide app settings and verify Allow third party apps is toggled on. If you turn off this switch, all external third-party
apps are disabled. Make sure that you allow external apps in Microsoft Teams.
Configuring Your Site for the Cisco Webex Integration with Microsoft Office 365
1. In Control Hub, navigate to the Services page and click Sites on the Meeting card.
2. Take note of the site URL for later and then click the site URL. Click Configure Site on the flyout window.
3. Under Common Settings, click Site Options.
4. Under Third-Party Integration, check Automatically link users with this Webex site if their Webex account email address
matches their Microsoft Office 365 email address.
5. Click Add New Authorization.
6. After signing in with your O365 admin, click Accept to grant the permissions.
7. After adding the authorization, click Update. (It can take up to five minutes for the update to finalize.)
Configuring Microsoft Teams to Use Cisco Webex Meetings
Now that the administrative tasks are complete, users can now use the Cisco Webex Meetings app within Microsoft Teams.
Microsoft Teams will need to be configured. For the lab, you will be using the Microsoft Teams web app.
1. In a web browser navigate to teams.microsoft.com and sign in with your Office 365 admin user.
2. After going through the coachmarks, click Teams on the left-hand menu.
3. Click Create team and then Build a team from scratch.

4. Choose Public.
Lab Guide
Cisco dCloud
5. Give the team a name and click Create.
6. After the team is created, add your other user/s that you created earlier.
7. Click Close when finished adding users.
8. In the main window, click the Add a tab icon [ ] to open a new tab.
9. Search and select the Cisco Webex Meetings app.
10. On the pop-up window, click Add. Click Save on the next window.
This will now open a new Webex tab. A chat also started between your account and the Cisco Webex Meetings bot. You can go over
to the chat and view the commands by typing help into the chat.
You will notice a message at the top stating your Webex site has not been set for your team yet. Follow the instructions as shown in
the next steps.
11. Click the Posts tab.
12. At the bottom in the Start a new conversation box, enter @Cisco Webex Meetings site cbXXXYY.webex.com (verify the URL
matches what you captured earlier in Control Hub).
13. Verify the bot is actually mentioned in the message and send the message to the team.
14. If successful you should see a message that state you changed the Webex site to cbXXXYY.webex.com
15. Go back to the Webex tab to verify your Webex room details are shown and you now have the ability to start a meeting.
16. Feel free to start an instant meeting or schedule a meeting using this tab.
17. You can also use the @Cisco Webex Meetings inside the conversations tab of the channel to run commands.
This also created this same Webex tab for everyone that is on the team. You can view this by opening another browser on the other
lab workstation and logging into teams.microsoft.com as another O365 user. It will show up as a new tab [ ]. You added
the tab to the General channel. If you create more channels, the tab can be added to those just as you did before.
18. In one of the channels you added the Webex tab to, select the Posts tab.
19. In the chat box start typing @Cisco Webex Meetings and when the bot appears, select it.
20. After selecting the bot you can click What can I do to get a list of commands.
Lab Guide
Cisco dCloud
Bot Commands
Feel free to test any of the commands listed by clicking on the command or typing it in the box. Try the join command. That will post
a link into the chat with a Join button that all users can click to join a meeting easily.
Join Webex Meeting
Lab Guide
Cisco dCloud
Scenario 9. Webex Hybrid Message Service Configuration

This service is ideal for organizations that have users on Cisco Webex Teams 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 1-to-1 instant
messages between Cisco Webex Teams client and Cisco Jabber client registered to Unified CM IM and Presence service. Hybrid
Message Service enables Cisco Jabber users to see the presence status of Cisco Webex Teams users based on their Teams client
activity.
You can find the full Webex Hybrid Messaging overview and setup guide here.
Enabling the Message Connector
1. Re-open the Cisco Webex Control Hub.
2. Navigate back to the management portal. On the Services tab, on the Hybrid Message card, click Set Up.
3. On the Hybrid Message Service Setup pop-up window, click Next.
4. Click Select an existing Expressway cluster to add resources to this service. Use the drop-down list box to choose HS Cluster 1
(This was named in the Calendar Service scenario. If you named it something different then choose that.)
NOTE: If you skipped the hybrid calendar section, you will need to register a new Expressway now. This was completed in
the hybrid calendar section earlier. To do that, select the first radio button and enter exp-cc.dcloud.cisco.com into the box,
click Next, and lastly enter HS Cluster 1 as the name. Then you can continue with the next step below.
5. Click Next.
6. Click Go to Expressway.
7. Login with:
• Username: admin
NOTE: Again, if you skipped the hybrid calendar section, you will need to finish registration of the new Expressway now.
This was completed in the hybrid calendar section earlier. To do that, check the box for I want Cisco to manage the
Expressway CA certificates required for this trust. Then click Register. On the next screen, check the box next to Allow
Access to the Expressway and click Continue.
In a moment, the Message Connector appears in the list. The Service Status will go from Not installed, 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.
Lab Guide
Cisco dCloud
Configuring an Application Account for Message Connector
A requirement for the Message Connector is an application user needs to be 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 Appendix B, you will find the necessary steps to create this user and assign permissions. The user is configured
with other roles to also be used with the call service. Only the one role mentioned above is necessary for the hybrid messaging
service.
Configuring the Connection to IM and Presence Service
To enable Hybrid Message Service, you must link Message Connector to your IM and Presence Service cluster by entering server
information for the publisher node. This step builds a bridge between IM and Presence Service and the Cisco Webex cloud, with the
connector acting as a broker between the two.
The connector on Expressway maintains a resilient connection between your Hybrid Message Service cluster and the cloud. You only
need to add the publisher to the Expressway-C connector configuration. If a specific node goes down in the cluster, the connector
will move to another server.
1. On the Connector Management page click the Configure IM and Presence Servers link. You can also navigate to Applications >
Hybrid Services > Message Services > Message Service Configuration.
2. Click New.
Edge Audio Expressway-E Traversal Server Zone Configuration
IM and Presence Publisher node address cup1.dcloud.cisco.com
Message Connector AXL account name webex

Message Connector AXL account password dCloud123!
4. Click Add.
5. Click Message Connector is not running, No status info available link, (also found at Applications > Hybrid Services > Message
Service > Message Service Overview).
6. Choose Enabled for the Active setting and then click Save.
7. 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.
Enabling Hybrid Message Service for Users
Users will need to be enabled for the Hybrid Message Service. For lab purposes you will enable one user, Anita Perez, for this
service. In production you can enable multiple users in bulk through a CSV template.
1. Open the tab for the Control Hub and login if needed (cholland@cbXXX.dc-YY.com / dCloud123!).
Lab Guide
Cisco dCloud
2. Click the Users tab and select Anita Perez from the list.
3. Under Hybrid Services, click Message Service.
4. Toggle the Hybrid Message Service on [ ]and then click Save.
5. On the main user pages, wait for the Messaging Service to change its status to Activated.
Testing the Hybrid Message Service
1. Connect to Workstation 2 (198.18.1.37) with these credentials:
• Username: dcloud\aperez
2. On Workstation 2 open Webex Teams client and login with these credentials (Sign out of O365 user if logged on earlier):
• Username: aperez@cbXXX.dc-YY.com
3. On Workstation 1 open Cisco Jabber if it’s not already. Use cholland@cbXXX.dc-YY.com for the email and then
cholland/dCloud123! for the username/password.
4. Start a 1:1 conversation with Charles from Anita’s Webex Teams client. Send a message to Charles.
5. Back on Workstation 1, in Charles’ Jabber client, you should see the message from Anita. Respond back to Anita. Also notice
Anita’s status reads @ Cisco Webex Teams.
Please be aware that the 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.
Lab Guide
Cisco dCloud
Scenario 10. Jabber Team Messaging Mode

This deployment option provides a core set of Webex Teams messaging features from the cloud while keeping your customer’s
calling services on-premises. Customers now have persistent one-to-one chats and team spaces, a new presence experience,
advanced file sharing capabilities, and a powerful way to search in your Jabber application – all while keeping the advanced calling
features that users know and love. Want more great news? There’s no need for customers to change their on-premises calling
infrastructure.
Team messaging mode shows our commitment to customers. It provides a new team workflow in your customer’s Jabber
environment. We use the power of the Webex platform to integrate with our existing solutions and deliver a unique blended
experience. IT administrators can provide new, cloud-delivered experiences while leveraging their on-premises or partner-managed
calling services. Customers will also have the added benefit of native interoperability between Jabber team messaging mode and
Webex Teams, as they leverage the same cloud platform. No forced migrations, no user islands. We are focused on productive user
workflows through a cloud evolution – not migration.
Reach out to your Jabber customers. Start a conversation about moving their messaging to the cloud with team messaging mode.
They will reap the benefits of a modern messaging experience and reduce maintenance from moving their messaging to the cloud.
See the new features, included team messaging mode in this video.
Enabling Kellie for the Messaging Service
1. Connect to Workstation 3 (198.18.1.38) with these credentials:
• Username: dcloud\kmelby
2. Open Cisco Jabber with these credentials:

• Email: kmelby@cbXXX.dc-YY.com
• Username: kmelby
Notice Kellie, who is currently connect to IM and Presence, has a number of contacts that are also in groups. During the migration
these contacts will also migrated over to Webex Teams.
3. Open the Webex Control Hub (admin.webex.com) and login if needed (cholland@cbXXX.dc-YY.com / dCloud123!).
4. Navigate to Services and click the Settings link on the Message card.
5. Scroll to the bottom of the page and toggle on the Enable Jabber team messaging mode feature.
NOTE: If the internal voice service domain is different than what is configured in the Control Hub, then you would leave
the first box unchecked. In the lab, Jabber is setup to use the Webex teams domain. When you logged into Jabber with
the cbXXX.dc-YY.com email, you set the voice services domain in the Jabber client.
6. Check both boxes and click Finish.
7. Navigate to the Users page and select Kellie from the list.
Lab Guide
Cisco dCloud
8. Under Services, click Messaging.
9. Toggle on the three toggles listed: Enable Jabber team messaging mode, Contact Migration Required, and Enable Jabber
calling.
10. Click Save.
11. On Workstation 3, exit Kellie out of Jabber (cog wheel [ ] and then Exit) and reopen Jabber.
12. To speed things along, click the cog wheel [ ] and choose Help > Refresh configuration and click OK.
13. After refreshing the configuration, within five minutes or less, Kellie will receive a Jabber pop up stating that configuration
changes have been detected. When the pop up is received, click Sign out.
Using Jabber with Teams Messaging Mode
1. After Jabber signs out, click Sign In.
You will notice that when Jabber reopens you will receive a Webex Teams sign-in screen now.
2. Enter Kellie’s Webex Teams password dCloud123! and click Sign In.
Because you turned on the toggle Contact Migration Required, Kellie receives a pop up to migrate her contacts.
3. Click OK.
You will notice you have a Call Setting notification [ ] at the bottom. Since SSO hasn’t been implemented yet you will need to
enter the on-prem credentials for Unified CM to resume calling.
4. Click Kellie’s avatar and choose Settings.
5. Choose Accounts from the left-hand menu.
6. Enter kmelby / dCloud123! for the username / password and click Apply.
7. If the update applied correctly, click OK.
After the update you’ll notice all the groups and contacts remain. Test using Jabber in this new mode to get a feel of the changes.
Somethings you can try are:
• Have a chat conversation with Anita.
• Make a call with Kellie’s Jabber and view the new presence status on Anita’s Teams client.
• In Jabber, create a new Teams space with multiple participants using the plus icon [+].
• Create a new space quickly with a Jabber group by moving over the group name and clicking the chat button [ ].
If you haven’t already, watch this video that was mentioned at the beginning of the section. It gives a quick overview of what’s new
in this mode. Feel free to try other workflows.
Lab Guide
Cisco dCloud
Scenario 11. Webex Teams Client Features

In this scenario, you will take a look at some of the features of the Cisco Webex Teams client. You may use your own client in this
scenario; however, the steps will use the clients installed on Charles and Anita’s workstations. Find an updated list of Webex Teams
features on https://help.webex.com/en-us/8dmbcr/What-s-New-in-Cisco-Webex-Teams.
You’ll notice as your presence status changes in Webex, your avatar will change to reflect the status. Use the following page as a
guide as to what each avatar state means on https://help.webex.com/docs/DOC-18266.
NOTE: Currently, any presence status can only be seen by people within your own organization.
Presence: Do Not Disturb (DND)
Along with Active status, which tells people how long it’s been since you’ve been active, you now have the ability to set DND from
your desktop or mobile app.
1. If not already, log in to Cisco Webex Teams on Workstation 1 with Charles’ account cholland@cbXXX.dc-YY.com and password
of dCloud123!.
2. If a space hasn’t been created with Anita, click the [ ] button and start up a 1:1 space with her. Click Contact a Person, search
for Anita, and add her to the space.
3. Send her a message.
4. On Charles’ Cisco Webex Teams desktop client, click Charles’s avatar and you can see his availability of Active. Click Availability;
notice you have the ability to set a DND timer, which all users can see. You can set this via the mobile client if you tap the Me
icon and then the Do Not Disturb toggle.
DND Timer for Desktop and Mobile
Lab Guide
Cisco dCloud
Presence: Out of the Office (OoO)
With the use of Calendar Connector, you configured earlier in the lab, you now have the ability to reflect your out of office status
from Outlook to Webex.
NOTE: This feature will only work if the calendar services has been enabled in the organization and the user has been
activated for the calendar service.
1. On Workstation 1, open Outlook.
2. Click the File tab at the top left.
3. Click Automatic Replies.

4. Select the radio button for Send automatic replies.
5. Check the box next to Only send during this time range.
6. If not already set, set a Start time to a time in the past (to turn on immediately).
7. Set an End time to a time in the future.
8. Add some text to the box at the bottom such as: I am currently out of the office.
9. Click the tab Outside My Organization.
10. Add some text to the box here as well.
11. Click OK.
Setting OoO
12. Return to Charles’ Webex Teams client. The OoO check is triggered by a Webex Teams action such as search, @mentions, or
going to a 1:1 space. Once it changes it will read Out of Office until one minute before the end time you set. If you didn’t set a
Lab Guide
Cisco dCloud
time range, then your status would just read Out of Office. Trigger the OoO change by sending a message to Anita using their
space. It may take a few minutes after configuring OoO to take effect in Webex Teams.
Charles OoO
13. Go to the space you have with Anita and send her a message. Once you do that you should see your status change. If not, wait a
few more minutes and try again.
14. Go to Workstation 2 and go to the space with Charles. The status will be set there as well as if you completed a search for his
name.
Charles OoO
Scheduling Cisco Webex Space Meetings
With Cisco Webex Teams, you can invite everyone from your space to meet at a scheduled date and time. You can create a meeting
invitation for Microsoft Outlook, if you have it, or copy meeting information to your calendar.
After you create the invitation in Outlook or another calendar, you can invite people who aren't members of your space by adding
their email address. When people who aren't members of the space join the meeting, they wait in the meeting lobby until a
member of the space joins and clicks Let In. Anyone who doesn't have a Cisco Webex account is prompted to create one before
joining the meeting. You can also remove email addresses from your Outlook or other calendar invitation.
Meeting scheduling is not available for the following:
• People with free or messaging-only accounts
• Spaces with 26 or more people
Lab Guide
Cisco dCloud
First, create a new space with Charles and Anita. You may add additional people if you would like.
1. On Workstation 1, open the Cisco Webex Teams client and make sure Outlook is opened.
2. Click the plus icon [ ] and choose Create a Space.
3. Enter a name for the space such as Team Meeting.
4. Add Anita and, if desired, some other people.

5. Once everyone has been added, click Create.
Create Space
6. Send a message to the space.
7. Select the Activity menu [ ] and select Schedule [ ].

You will now see a Create Meeting Invite page.
8. Click Schedule a meeting and click Open.

9. Bring Outlook back to the foreground and wait for the meeting invite to appear. You’ll notice that all the information was
copied over from the space.
10. Feel free to change the Start/End time, add a reoccurrence, or add a message. Once completed, click Send.
11. Open the calendar entry that was created and click the Join Cisco Webex Teams Meeting link that was generated.
12. It will first open the link in your web browser and then you will need to click Open Webex Teams on the pop up. If you check the
box next to Always open these types of links in the associated app then you won’t have to click the icon next time; it will just
open automatically.
13. Click Start With Video.
14. Go to Workstation 2.
Since Charles started the meeting, Anita will receive a notice to join in her Webex Teams desktop client. Also notice the space shows
the avatar of all the participants that have joined already. In this case, only Charles has joined so you only see his avatar.
15. Click the toast that shows at the bottom right of the screen and then click Join With Video.
Lab Guide
Cisco dCloud
16. From your mobile client, log in as one of the other users in the space.
17. Tap Join on your mobile Webex Teams app to join the meeting in progress. You now see Anita’s and Charles’ avatars in the
meeting.
Sharing a Screen during a Call
You have the ability to share your screen from your desktop or mobile app.
1. While in the previous call from either your desktop or mobile app, click share screen [ ].
2. If you are on the desktop app, choose what you want to share and you will start the screen share. The mobile app will start
sharing your screen immediately.
3. Stop sharing any time by clicking Stop.
You have now tested Cisco Webex meetings and scheduled meetings. As the meeting is connected, feel free to test other meeting
activities and management such as sharing content, message, uploading/viewing files, muting participants using roster window, etc.
The meeting will continue to stay up until the last person leaves. You can also start an ad-hoc meeting by going into the space and
clicking Call.
4. End the meeting by ending the call on all Webex Teams clients.
Meeting Notifications
You have the ability to change when Webex Teams notifies you of an upcoming meeting.
1. In the Webex Teams client, click Charles’ avatar and choose Settings.
2. Select Notifications.
3. On the right side under Scheduled Meetings you can see the options for being notified.
Pop Out Spaces
We all love multi-tasking and pop out spaces will help us do exactly that. You can pop out multiple spaces into new Webex Teams
windows. This allows you to focus on those important spaces and conversations without getting distracted by other unread spaces
or notifications. There are two ways to open in a new window.
• In the Webex Teams client, find a space and double click on it to pop out to another window.
• Right click on another space and choose Open in a new window.
Lab Guide
Cisco dCloud
Peek in a Space
Catch up on those unread messages later! When you see you have an unread message in a space, but you know you don't have time
to follow up on it right now. With peek in a space, the space isn't marked as read and no read receipt is sent. However, if you reply
then a read receipt is sent but you're still in peek mode.
1. In the Webex Teams client on Workstation 1, find a space Charles shares with Anita and make sure that space is not open.
2. On Workstation 2, send a message to that space.

3. Back on Workstation 1, right click on the space and choose Peek in space.
4. As you can read the messages in the space, however it stays unread. Go back to Workstation 2 and view the space again.
5. You will notice that Charles’ avatar does not show at the bottom of the space as read.
Message Options
You have a number of different options now to reply to a message or act on a message. These include threading, quoting,
forwarding, editing, or flagging.
1. In the Webex Teams client on Workstation 1, find a space and hover the mouse over a message.
2. If it is a message you sent you can click the pencil icon [ ] to edit the message. Find a message and try it out. After sending the
update you will notice the word Edited next to the time the message was previously sent.
3. You also have an option to start a thread by using the reply icon [ ]. Give it a try.
4. Another option for replying to a message is quoting a message by using the quote icon [ ]. Try it out to see that it takes the
message and adds your message to it. Once sent, it places as the last message in the space.
5. You can forward messages to other spaces by using the forward icon [ ]. This will quote the message in a space of your
choosing. Give that a try.
6. You can flag messages by using the flag icon [ ]. This will help you organize messages that you would like to come back to
later. Flag a message.
7. Using the Filter by option under the search bar, you will see a number of different options that includes Flags. Take a view of all
the different options you have to filter by now and then click the Flags option to see the message you just flagged. It will show
up in the list and, if you select it, then the space will open where that message is and bring you to directly to that message in the
space.
8. Lastly you can delete your message by using the trash can icon [ ].
Lab Guide
Cisco dCloud
Using the Whiteboard to Collaborate on the Cisco Webex Teams Client
In addition to existing collaboration possibilities such as sharing files and sending messages, the whiteboard activity gives you
another way to work with your colleagues. You can quickly create visuals and share them in your spaces or with your team during a
call.
1. Open one of the Cisco Webex Teams clients using any user from the space created earlier for the scheduled meetings task.
2. Within the space, click the Activities menu (ellipses icon).
3. Click Whiteboard [ ].
4. Click New whiteboard at the top.
5. Start drawing something on the whiteboard. When you are finished, click Share and then Post snaphot [ ].
6. Close out the whiteboard and see that the whiteboard snapshot is now in the space.
7. From another client, click Activities menu in the space. Click Whiteboard and then click the whiteboard created by the other
user.
8. Make some edits to the drawing on the other client. Changes are automatically saved and updated to other users in real time.
9. At the bottom of the current whiteboard you can tap/click All whiteboards to view all the whiteboards in this space. Feel free to
create more whiteboards by tapping/clicking New again.
10. If you like, you can also delete any whiteboards that were created.
Moderated and Announcement Spaces
In some Webex Teams spaces, you may want the ability to restrict space settings such as adding/removing people, editing space
name, assign other moderators, etc. In this case you can turn any space into a moderated space.
1. Select the Team Meeting room you created earlier.
2. Click the [ ] icon and choose the Moderate space option. Click Yes on the pop-up window.
3. Select the activity menu and choose People.
4. You can see that you have been made the only moderator of the space. You can right click any person and choose Assign as
Moderator.
Sometimes you may want to create spaces that are only used for announcements. These spaces will only let moderators post
messages/files, start calls, schedule meetings, or create whiteboards.
5. Turn a moderated space into an announcement space by clicking the icon again and choosing Turn on announcement
mode. Click OK on the pop-up window.
Lab Guide
Cisco dCloud
6. When a participant views an announcement space, they will see a message as shown below.
Announcement Space Message
Starting/Joining CMR Meeting
Within the Webex Teams client you have the ability to start an instant CMR meeting or join a meeting using a video address.
1. Click the Calendar icon [ ].
2. At the top of the page you should see your personal room URL. Click the cog wheel [ ].
NOTE: If you do see personal room details then you can ignore this note. If you needed to check the box for Personal
Room earlier for Charles and it is the same day you checked the box then you may not see his room details automatically.
They will need to be manually set. Other users in the org should have this set automatically. Because Charles was the
first user created in the org, the overnight process that sets the preferred Webex site needs to run first to set his default
personal room automatically. You can go ahead and set his personal room manually or use another user to complete the
steps below.
Here you can copy your meeting information. You can also edit the information such as the URL or host PIN by clicking the Edit link.
3. Click Cancel on the window to go back to the client.
4. You will notice a green Start Meeting button. By clicking this button and then Start with Video it will immediately start a
meeting in your personal room. Feel free to try that now.
5. If you started a meeting, you can end it.
6. On the top right corner ,you can enter a video address, click the green button, and then Start with Video. You can try calling
any video address now or use the address of Charles’ personal room, cholland@cbXXX.dc-YY.com.
NOTE: If the Webex meeting site URL does not work, verify the URL in Control Hub at Services > Meeting > Sites > Site
Name. Alternate URLs that could be used is https://cbXXXYYa.webex.com, https://cbXXXYYb.webex.com, or
https://cbXXXYYc.webex.com.
Calling Behavior
An admin can change the Webex Teams calling behavior when calling telephone numbers. This was mentioned in the Webex Calling
scenario as well. You will now cover another calling behavior available for users.
Lab Guide
Cisco dCloud
Calling in Webex Teams (Unified CM)
You have the ability to register Webex Teams to an existing Unified CM call control environment. This works just like Cisco Jabber
does today with the use of a Cisco Unified Client Services Framework (CSF) device. If you already have Cisco Jabber configured and
working then Webex Teams will use the same CSF device to register. Because it uses the same CSF device you cannot use Jabber and
Teams at the same time if Teams is configured to register to Unified CM. When Webex Teams is registered to Unified CM, it opens
up more calling features such as desk phone control and midcall features like hold and resume. You can view a complete overview of
this calling solution as well as a deployment guide.
You will now configure Charles for this calling behavior.
1. Go back to Control Hub and navigate to the Users page.
2. Select Charles from the list. Scroll down to the Settings section on the fly-out window.
3. Click Calling Behavior.
4. As you can see the default calling behavior is to use the Organization Setting: Calling in Webex Teams for dialing telephone
numbers. You can change the organizational setting on the Settings page. For now, you will just modify Charles’ calling behavior.
NOTE: As you can see, there are multiple calling behaviors listed. You will not cover all of these in the lab but feel free to
test them later. For example, having the Cisco Jabber App selected will cause a call from Webex Teams to cross-launch
Cisco Jabber and use that client for calling telephone numbers. You can test that scenario on Workstation 2 with Anita.
5. Select the radio button for Calling in Webex Teams (Unified CM).
6. Click Save.
7. Back on Workstation 1, sign out and exit Cisco Jabber if it’s open.
NOTE: Webex Teams uses the same CSF device used by Jabber to make calls. Both apps cannot use the CSF device at
the same time so one application must be closed, which is why you just closed Jabber.
8. If you have Webex Teams open, you may see a restart button [ ] after the change. If you do click, that button and then click
Update to restart/update the client. If you don’t see that button, sign out of the client and then sign back in.
9. In a few moments you should see a new icon appear at the bottom left of the client [ ]. Click that icon to open the settings
for Phone Services. You can also get to this setting by click the avatar and then Settings > Phone Services.
10. Enter cholland / dCloud123! for the username / password fields and click Save.
11. Click OK on the pop-up notice.
12. Once the credentials are applied, the phone warning icon will disappear. When this happens, you are ready to make calls.
You will now be able to make and receive calls through the PSTN. Feel free to test calls to/from the PSTN with the numbers you used
previously in the lab.
Lab Guide
Cisco dCloud
Scenario 12. Webex Meeting Troubleshooting

This scenario goes through different features that the Cisco Webex Control
Analytics
With the Cisco Webex Control Hub, you have access to analytics to provide usage trends and valuable insights on which to base
further adoption strategies to promote and optimize collaboration across teams. Advanced analytics capabilities are integrated as
part of Webex Control Hub. Customers are able to understand how different services are being used across the organization and
effectively grow adoption to maximize productivity gains. Administrators are able to monitor capacity and performance to optimize
resource utilization as part of proactive management. Administrators or IT help desk staff can diagnose and shorten case resolution
time.
An intuitive graphical interface allows administrators access to usage, adoption, and other important information. Interactive data
visualizations explore data as it automatically adapts to parameters specified in real time.
Access to historical data for the last 90 days is standard. Data is aggregated and presented in multiple reports. Administrators may
access these reports at any time within Webex Control Hub.
Pro Pack for Webex Control Hub offers additional features that allow you to further explore data and correlate insights that would
otherwise be unknown. It enables data exploration with different dimensions, such as time, location, and person. It also offers a
diagnostic feature that allows real-time access to Webex meeting details, such as meeting duration and participants list.
Unfortunately, in a lab with only a few users and devices it’s difficult to obtain the full scope of what is provided with the analytics
and reporting data. Going through the lab you should have some data populated but not much. Feel free to click the Analytics tab
and drill down on the reports in each section: Messaging, Calling, Care, Video Mesh, Devices, and Meetings. To view more info on
the reports provided click here.
Troubleshooting
Pro Pack for Webex Control Hub also offers a Webex meeting troubleshooting capability. Technical staff can quickly resolve support
requests and search for meetings in real time as they occur. Both host email address and meeting ID are valid search criteria, with an
optional date selection of the last seven days. Meeting time is shown per the administrator’s profile time zone, which can also be
modified via a drop-down menu. When a meeting is located, conference ID, start time, duration, meeting name, number of
participants, and status are reported.
Administrators can drill down into an individual meeting to retrieve additional participants and session-level details. Each participant
connection per device is shown on a separate line. Join meeting time and duration of audio and video sessions are displayed on each
line, if available.
In the lab you will be using the Webex meetings application. To get the best experience its best to dial in from multiple devices
including a mobile device. If your mobile device is on your local carrier network it could help in seeing poor quality when connecting
to the meeting. First you will need to download the meetings app to your mobile device using your devices app store. Also download
the desktop app. If you don’t already have the meetings app installed on your desktop, the steps below will walk you through
obtaining the install file. This can be installed on the labs workstations or your local workstation. It’s recommended to use your own
workstation.
Lab Guide
Cisco dCloud
Download and Install the Desktop Webex Meetings Application
Now install the Webex Meetings desktop application. If you already have the application installed, you can skip this section.
1. Using your web browser, navigate to https://cbXXXYY.webex.com.
NOTE: If the Webex meeting site URL does not work, verify the URL in Control Hub in Services > Meeting > Sites > Site
Name. Alternate URLs that could be used are https://cbXXXYYa.webex.com, https://cbXXXYYb.webex.com, or
https://cbXXXYYc.webex.com.
2. Sign in with Charles’ account (cholland@cbXXX.dc-YY.com / dCloud123!).
3. Click Download from the menu on the left.

4. Click the Download button.
5. Install the downloaded application and sign in with Charles after installation completes.
Start Meeting and Join from Other Devices
Now start a new meeting using the desktop app and join from other devices.
1. In the Webex Meetings application, click Start a Meeting and then Start Meeting.
2. Using the meeting details connect into the meeting with other devices. This can be from the mobile app (preferred), Teams app,
room device, etc. Meeting info can be found by clicking the info button [ ] at the top left of the screen.
Troubleshooting the Meeting
After the meeting has started and you have joined the meeting from different devices you can now view the near real time meeting
data.
1. In the Webex Control Hub, click Troubleshooting.
2. In the Email box, enter Charles’ email address (cholland@cbXXX.dc-YY.com) and press Enter/Return.
3. All the meetings you’ve started in the lab will be listed including the one at the top which should be In Progress. Click that
meeting. (It might take up to 10 minutes before the meeting appears in the list.)
You should now see a graph of users that are joined in the meeting along with any devices you used to dial in with. Note that it could
take up to 10 minutes for all the data to appear correctly. At any time you can click the refresh button [ ] to obtain the latest
data.
4. Click the Participants tab at the top right to view the list of users with connection info.
5. Back on the Meeting Details tab, move your mouse over any parts of the graph to obtain more info on the device/user,
including join time, VoIP quality, etc.
Lab Guide
Cisco dCloud
You’ll notice a legend on the right side of the graph. If you dialed in with a mobile device on a bad connection, you may see some
poor data in red.
Also on the right you will see the meeting overview such as host information and meeting type. You can also see whether the
meeting was recorded or if screen share was used.
The default graph is the Audio information.
6. Scroll back up to the graph and click Video.
You’ll see information about the video data as you did with audio such as video quality, latency, and packet loss.
Feel free to keep the meeting connected and wait for more data to come in. You can also try making your connection back to see if
you can make the data show poor quality. Also feel free to share your screen or test any other features.
When you have completed testing, end the meeting. Remember you can always go back to view the meeting data on the
Troubleshooting page.
Lab Guide
Cisco dCloud
Scenario 13. Pro Pack for Cisco Webex Control Hub

In this Scenario, you will configure many Pro Pack features that you can get with Cisco Webex. There are two types of services—
standard and Pro Pack. The standard services come free with Cisco Webex with no additional add-ons. The Pro Pack add-on provides
additional services. For more information on Pro Pack for Cisco Webex Control Hub go, visit
https://collaborationhelp.cisco.com/article/en-us/np3c1rm.
Compliance – eDiscovery Search and Extraction Tool
eDiscovery comes free with Webex under the standard offering; however, with the standard offering you will only be able to go back
and search up to 90 days. With Pro Pack, your search is unlimited.
With the eDiscovery search and extraction tool, you can access unlimited data to search and retrieve information within Cisco
Webex Teams spaces. Use email addresses, space IDs, keywords, and specific time limits to narrow the search.
As a compliance officer, you can use Cisco Webex Control Hub to search through any conversation in the Cisco Webex Teams app.
You can look for a specific person in your company, find any content they have shared, and then generate a report of your findings.
You can also look through a specific space for information.
Visit https://collaborationhelp.cisco.com/article/en-us/DOC-21569 to view more information about eDiscovery, including information
about the compliance officer role and the reports provided.
First, you will need to assign the compliance officer role to a user. Only an administrator can configure this role. Also, for security
reasons, an administrator cannot assign the compliance officer role to themselves.
Configuring a User for the Compliance Office Role
1. Return to the Control Hub portal (https://admin.webex.com) and log in as Charles, if needed.
2. Click the Users tab.

3. Select Eric from the user list.
4. On the fly-out window, click Service Access.
5. Check the box for Compliance Officer and click Save.
Generating Data for Searching
In order to have search results, you will need to generate some messages with users.
1. Send messages using the Webex Teams client. You can use an existing space or create a new one.
2. In the messages, use some unique words to be searched.
3. After sending some messages, move to the next section.
Lab Guide
Cisco dCloud
Searching and Extracting the Data
Now that there are messages in the system to view, you will now use the eDiscovery search and extraction tool to find that data.
1. Log out of the Webex Control Hub as Charles and login with Eric esteele@cbXXX.dc-YY.com and password dCloud123!
2. Accept the Terms of Service.
3. In the Email Address box, enter the email address of the user you generated the data with earlier. If you had the space ID, then
you could also search within that space only using the Space Names box. Note that multiple users and spaces can be searched
at once.
4. Enter a name in the Report Name box
5. Click the Search & Generate Report button that appears at the bottom right of the screen.
6. You will be now taken to the Reports tab. It will take some time for the request to finish. In order for you to download and view
the reports you ned to download and install the eDiscovery Download Manager.
7. Click the Download Manager tab at the top right of the screen.
8. Click the download button for your operating system and install.
9. After installation go back to the Reports tab and click the download icon [ ] next to the report you generated.
10. When prompted, click Open eDiscovery Download Manager.
11. Pick your Download Location and the click Full Report.
12. Once download finishes, click Open Folder.
All the messages for this user will be extracted into .eml files. You will have to use your operating system to search within these files
for the messages you need. You can open these .eml files individual using a text editor or email client.
Compliance – Events API for DLP and Archival
Whether you’re a standard customer or a Pro Pack customer, you can use the Events API to integrate with your existing Data Loss
Prevention (DLP) software. You can even check for policy violations and take action to resolve any issues. However, if you’re a Pro
Pack customer, you can monitor events that occurred more than 90 days ago. Events include posting messages, files, and adding
users to spaces. You can also use the Events API to integrate with your existing archiving software to achieve an unlimited amount of
Cisco Webex data.
Setting up DLP or archiving software is beyond the scope of this lab. However, you can view and run the APIs manually to see the
data that can be retrieved.
A user will need the compliance officer role in order to use the Event APIs.
1. Navigate to https://developer.webex.com in the same browser you used for the eDiscovery tool and Log In. If needed, log in as
Eric, the compliance officer (esteele@cbXXX.dc-YY.com/dCloud123!).
2. Click the Documentation link.

3. Click the API Reference menu on the left to expand it.
Lab Guide
Cisco dCloud
4. In the menu you can view all the different public APIs that are available to use with Webex Teams. For now, click the Events
menu item and then List Events.
If you have never used the Cisco Webex for Developers site before, there is a test mode. This allows you to use the APIs directly from
the website to see how they work. You will do that now with the Events API.
5. Verify Try it is selected.
The developer site already inputs your bearer token from when you logged in so all you have to do is run the API. Notice under the
Query Parameters section you can narrow your search. For now, leave all options empty.
6. Scroll toward the bottom and click Run.
You will get the response to the API on the right side of the screen. As you can see the response has all the posting of messages,
files, and adding users to space events. Since this is a new org with a few users that have only created events up until now in the lab,
the response is quite minimal. Multiply that by 100s or 1000s of users creating messages, uploading files, adding users to spaces and
you can see this response would be very large. You wouldn’t want to run and sort through this for a live production organization.
This is where DLP software comes in to capture this data and sort through it for you as well as act on any events if, say, a violation
you set has occurred. Also, as mentioned before, this information can be redirected to an archival system to keep an unlimited
amount of data.
Compliance – Flexible Retention Policy
If you’re a Pro Pack customer, you can set retention times for content that is created and shared by people in Cisco Webex to align
with your organization’s policies. Any data older than the retention time is removed and irretrievable. You will set this in the Control
Hub as an organizational administrator.
1. Navigate back to the Control Hub https://admin.webex.com/ and log in as Charles (cholland@cbXXX.dc-YY.com and password
dCloud123!).
2. Click Settings from the left-hand menu.
3. Scroll down to the bottom of the page to the Retention section.
By default, and the only option for standard users, the retention time is set to Indefinitely.
4. Select the different options available to see the available retention times for Pro Pack users.
Security – Enforcing PIN Lock
To ensure that content is secure in the Cisco Webex Teams app, you can set up a PIN lock. After a PIN lock has been enabled, people
can only use Cisco Webex Teams on mobiles with PINs or lock screens.
1. On the Control Hub, click Settings from the left-hand menu if you are not there already from the previous exercise.
2. At the top of the page in the Security section, check the box for Users can only launch the Cisco Webex Teams app on mobile
devices protected with lock screens.
3. If you have the ability to turn off your PIN on your mobile device you can test this feature by turning off the PIN, then open the
Cisco Webex Teams client and log in with one of the users in the lab.
Lab Guide
Cisco dCloud
When you open the mobile app you will be presented with a pop up that tells you a passcode is required and in order to keep using
the app you will need to set a passcode. The only option available is then to log out.
Security – Block External Communication
To secure your organization's data and prevent data being shared outside of your organization, you can control whether people can
communicate in Webex Teams spaces with anyone outside of your organization.
1. On the Control Hub, click Settings from the left-hand menu if you are not there already from the previous exercise.
2. Scroll to External Communications.
3. Check the box for Block your users from inviting external contacts to Cisco Webex Teams spaces and prevent your users from
joining external Cisco Webex Teams spaces.
Existing external people in spaces and existing external spaces are not removed with this setting.
This setting does not apply to bots.
People in your organization can't do the following:
• Add people from outside your organization into spaces owned by your organization.
• Join external spaces.
• Create spaces with external people.
People in your organization may be able to make calls to external people in the following scenarios:
• If your users make calls using a Webex SIP address. For more information, see Cisco Webex SIP Addresses.
• If you have an on-premises call environment and assign Hybrid Call Service to your users. For more information, see the
Deployment Guide for Cisco Webex Hybrid Call Service.
• If you have cloud calling through Cisco Webex Calling (formerly Spark Call) and assign the Cisco Webex Calling (formerly
Spark Call) service to your users.
4. Open a Webex Teams client and start a 1:1 or group space with a user that does not have the cbXXX.dc-YY.com domain.
When you try to add the user, you will receive a pop up warning stating that you can only contact people from your company.
5. Click OK on the message.
6. If you have an outside account that is logged into Webex Teams, try adding one of the lab users to a space.
When you try to add a lab user, you will receive a pop up warning stating that they can’t join spaces from other companies.
Security – File Sharing Controls
You can control how people share files in Cisco Webex Teams. If you want to prevent data loss, eliminate malware concerns, and
apply policy controls on specific Cisco Webex Teams apps, you can restrict users from downloading, previewing, and uploading files
to the Cisco Webex Teams app.
1. Navigate to the Services page and on the Message card, click Settings.
Lab Guide
Cisco dCloud
You will see multiple types of restrictions for Cisco Webex Teams apps and bots:
• Preview and download files
• Upload files
• Whiteboard and Annotations
• Disable the ability to use the GIPHY integration to send GIFs
• Turn off/on the preview for shared links
Some points to note when choosing polices:
• If you choose Preview and download files for a Cisco Webex Teams app or for bots, then the Upload files is automatically
selected for the Cisco Webex Teams app or for bots.
• If you choose to apply restrictions to whiteboards and annotation, then the restrictions are only applied to new spaces,
existing spaces with whiteboards and annotations are not impacted.
2. Set some or all of the restrictions listed.
Once you check the box in the download and preview dropdown, you’ll notice that the same box will be selected in the upload
section. If you check the box in the upload section then you can still allow the download and preview to be available.
After enabling one of the options, with a lab user go to that app type and try to complete the task you disallowed.
If you disabled upload then you will notice that when you try to send the message you will receive and error stating that you are
unable to send the message. If you disabled download then the app will not allow you to download the item.
Security – Revoke Access
When people lose their mobile phone, or somebody leaves your organization, you can remotely revoke their access and wipe any
cached Cisco Webex content from their mobile phones.
1. In the Control Hub, click Users.
2. Select a user that you have logged into Cisco Webex Teams with previously.
3. Click Security.
4. At the bottom of the window, click Reset Access.
This will revoke all the tokens for this user. Keep in mind that this process can take up to six hours. You can delete the user to
remove their access immediately.
Lab Guide
Cisco dCloud
Scenario 14. The Webex Board

The Cisco Webex Board: All-in-One Device for Team Collaboration
With the Cisco Webex Board, you can wirelessly present, whiteboard, video or audio conference, and even annotate shared content.
It has everything you need for team collaboration at the touch of a finger. Use the Cisco Webex Teams app to connect with virtual
team members through the devices of their choice.
Key features of the Cisco Webex Board include:
• Designed with you in mind: Enjoy an easy-to-use, touch-based, high-quality collaboration experience. Cisco Webex Board
integrates the most common tools needed for team collaboration in a physical meeting rooms into a single elegant device.
• Connect virtual teams through the app: You can store everything you create on the Webex Board in the cloud and
associate it with a virtual room. Team members can use the Cisco Webex Teams app to pick up where they left off in the
physical room and continue working anywhere.
• Intelligently anticipates your needs: The Webex Board automatically wakes up when you enter the room. It detects your
Webex Teams app-supported device and suggests an activity, such as call, whiteboard, or wirelessly share your
presentation.
• Technology for natural experiences: A powerful 4K camera captures a high-resolution, wide-angle image of nearly the
entire room. A 12-microphone array delivers crisp, clear audio, automatically amplifying and modulating voices so that all
meeting participants sound great.
In this scenario, you can use a Cisco Webex Board along with what you’ve already completed in the lab so far. The Webex Board you
are using will most likely be already connected to the Cisco Webex service. If not, you would add the Webex Board as you would any
other room device which was shown earlier in the lab. The Webex Board DOES NOT have to be connected to the same Webex
organization you configured during this lab.
Local Webex Board Functionality
The first thing you can do is use the Webex Board as a local whiteboard.
Calling
1. Tap the Webex Board to bring up the main screen, if not already. You will see three options—Call, Whiteboard, and Share
screen. If at any time, you want to return to the home screen, you can tap the home button at the bottom center of the display.
2. Tap Call.
Here you can dial a user to call.
3. From the Webex Board, call one of your Webex Teams users in the lab that is logged into your local client by dialing
username@cbXXX.dc-YY.com and answer on your Webex Teams client. Make sure to mute both sides to eliminate feedback.
4. On the Webex Board, you have options to mute audio/video, change volume, and end call. If you don’t see these options, tap
the screen. You can also swipe up from the bottom to get the volume controls.
Lab Guide
Cisco dCloud
5. You’ll notice your local video disappears while in the call. You can make it persistent by tapping the screen, then tapping your
video, and then tapping Pin Selfview. Notice how wide of an angle the built-in 4K camera can reach. Move around the room and
test the Best View feature. The video should zoom to allow the best view for the sending video.
6. If you have multiple people, test the microphone quality by having at least one user on the Webex Teams app leave the room
and continue the conversation with the person/s on the Webex Board. If there is room, walk around the Webex Board room and
continue to have a conversation. Notice, on the remote end, the person will be able to be heard clearly from anywhere they go
in the Webex Board room due to the built-in 12-microphone array. Microphone performance may differ in large training
environments with multiple people in the room. The approximate mic range is around nine meters (almost 30 feet).
7. Press the home button and tap Whiteboard.
8. Start drawing something on the board.
9. On your Webex Teams client you will see the whiteboard live and see any changes made immediately. To make any edits on
your client, tap/click the edit button [ ]. At any time, if you want to stop sharing, you can tap Done and then Stop sharing.
10. End the call from Webex Board by tapping Return to call bar on top of screen, then tap the X to end call.
11. You can view the Webex Board’s SIP address or Settings by tapping the name at the top center of the screen. You also have the
ability to restart the Webex Board from this menu.
Screen Sharing
You also have the ability to do a screen share.

1. From the home screen, tap the Share screen icon.
You’ll notice that you have two options to share a screen—HDMI cable or wirelessly using the Webex Teams client.
2. If you have an HDMI cable, feel free to test the screen sharing using it first. The HDMI port is located on the rear near the
bottom/center of the display.
After testing HDMI, share your screen with the Cisco Webex Teams desktop client.
3. Open your Cisco Webex Teams desktop client and click the name of the paired board at the bottom left of the client and choose
Share Screen.
4. Select a screen or application to share.
After a few moments, the screen share will start. You can end your screen you by clicking [ ] at the top of your desktop
screen or by tapping the Webex Board and then tapping Stop sharing. However, keep the screen shared for the next section.
Annotate
You have the ability to annotate on a screen share.

1. If you aren’t still sharing your screen from the previous section, do so now.
2. Tap the Webex Board screen and click the Annotate button at the top left of the screen.
This will take a screen capture of the current share so you can start annotating. It will also end the screen share from your device.
3. Feel free to annotate anywhere on the screen.
Lab Guide
Cisco dCloud
4. Once you are finished you can tap the Done button at the bottom left of the screen. You will be asked if you want to resume the
screen share. Tap Stop. This will close out the annotation screen and place it in the Files folder on the Webex Board.
5. You will be brought into the Files screen. Choose the screen capture you were annotating. From here you can continue
annotating by tapping the annotate button at the bottom left of the screen.
6. You can also save your progress to a Webex Teams space by tapping the export button at the bottom right of the screen and
choosing Save to Webex Teams. Do this now.
7. On the next screen, verify your work is selected and then tap the right blue arrow to continue.
On the next screen, you should see your name from the paring earlier. You can also add other people into the new space you are
creating now.
8. Keep the screen as is or add additional people to the new space if you would like. Once you are finished, tap the blue
checkmark.
9. Go to your Webex Teams client and verify the new space has been created with the snapshot located in the Whiteboards
container.
10. Your board was automatically connected to this new space. Close it now by going to the home screen and tapping Close this
space at the bottom of the screen
White Boarding
Next, you’ll use the white boarding feature as you did earlier in the calling section.
1. From the home screen, tap the Whiteboard icon.
2. Start a new whiteboard or use an existing one and utilize the colors listed at the bottom of the screen. Along with the different
colors, you also have an eraser with a clear all function. Use the Webex Board pen or your own fingers to draw. There is also an
undo button.
3. After drawing on your first whiteboard, leave the drawing there and tap the New whiteboard icon at the bottom left of the
screen.
4. Create another drawing on this new whiteboard.
5. When you are finished drawing, tap the All whiteboards icon at the bottom left of the screen. You are now viewing all local
whiteboards.
You are now viewing all local whiteboards.
6. You have the ability to delete all or some whiteboards by tapping the Trash can icon at the bottom left of the screen.
A circle appears at the bottom right of each whiteboard. If you tap any of your whiteboards, a checkmark appears in this circle. Once
a checkmark is put onto one of the whiteboards you can tap the red checkmark icon at the bottom left of the screen the then tap
Delete to delete the selected whiteboards. Do not delete any right now.
7. Tap Cancel.
As a security feature, all whiteboards will be deleted once the Webex Board goes to sleep. You can manually put the Webex Board to
sleep by resting your finger on the home button and a five second countdown timer will start.
Lab Guide
Cisco dCloud
8. Rest your finger on the home button to start the sleep process but once it starts, tap the Webex Board screen to cancel. Go back
into the whiteboards and view all whiteboards again.
Emailing Local Whiteboard
While in a white boarding session in a meeting room there might be a need to email the whiteboard for viewing. Before you can
email a whiteboard you will need to configure your email server settings.
1. On the home screen, tap the name of the board at the top and tap Settings.
2. On the next screen, tap Advanced Settings and then Email server configuration.
3. Toggle on Enable exporting to email and then enter valid settings for your outbound mail server.
4. When finished, tap the blue checkmark.
5. Open a whiteboard and create some markings.
6. Once finished tap the save button at the bottom right of the screen and tap Email.
7. Select the whiteboards to email and tap the blue arrow.
8. Enter the email addresses of the recipients and when finished tap the blue checkmark to send.
9. You can view the PDF attachment when the email is received.
Webex Board Functionality with a Webex Teams Space
The Webex Board on its own is great but it becomes even greater connected to a Cisco Webex Teams space where you can set up a
new space and add multiple file types such as documents, presentations, photos, etc. After creating the space, add a few of your
demo users to the space.
Move Whiteboards
1. If not already, go back into Whiteboard on the Webex Board to show all whiteboards.
2. On one of your Webex Teams clients, pair with the Webex Board and open an existing space or create one.
3. Open the activity menu. At the bottom of the menu, choose Open on Webex Board. This option will be available if you are
paired with the Webex Board.
You’ll notice once you are connected you will have more icons on the screen. Also, the space name will be at the top left of the
screen and the Webex Board name at the center will be gone.
4. Tap Whiteboard.
You will now notice that you are given the option to move all the whiteboards you had created locally into the space. If there are
multiple whiteboards, you can swipe across on the whiteboards to view each one that will be added.
5. Tap the blue check mark to move all whiteboards into the space. You should see all the whiteboards that you created locally on
the Webex Board.
Now you should see all the whiteboards that you created locally on the Webex Board in the space of each client. Feel free to
continue editing any of these whiteboards. When you are finished, go back to the home screen.
Lab Guide
Cisco dCloud
Call (Meeting)
Earlier you made a call from the Webex Board, which was a point to point call. This time you will make a call but it will initiate a
Webex Meeting.
1. From the home screen, tap Call.
Instead of getting a keyboard to dial a number, you go straight into making the space call.
Other Webex Team clients connected to this space will receive a notification to join the meeting.
2. Join the meeting from one or more of the clients.
3. While in the meeting, press the Home button on the Webex Board.
If you have more than one client connected to the meeting, you will see those clients video in their own circle at the top with the
prominent speaker as the background. In here you can open back up the whiteboards in the space and continue to work on them
together. As you switch from different applications on the Webex Board, you’ll see the video of the remote users stay at the top of
the screen so you can see them continually while you are navigating or working. Stay connected to the call.
Files
1. From the home screen, tap Files.
2. To test different file types in the space. Open different files types in the space, such as PowerPoint, Word, etc. If none are
available you will need to upload them to the space so the Webex Board can open them.
If you opened a PowerPoint, Word doc, or PDF, notice you can advance the slides/pages using the slide viewer at the right of the
screen. You can change the slide/pages by sliding your finger up and down on the slide/page. You can hide/unhide the slide view by
tapping the screen and tapping the [ ] icon at the bottom right of the screen. You can also zoom using two fingers and dragging
them away from each other. Zoom is available on other items as well, such as photos. When you are finished opening different file
types, continue on with the lab.
People
Within People, you can view the list of users inside this space and if you are in a call you can view the list of participants. You also
have the ability to mute the audio/video of other users.
1. From the home screen, tap People.

2. View the list of users in this space as well as the participants in the current call.
3. End the call on all devices.
4. Once you are finished using the Webex Board, tap Close this space at the bottom center of the screen.
You will see the space name disappear and the name of the Webex Board reappear. Also, the number of options reduces to three. If
you go back into Whiteboard, you’ll note that all the whiteboards are no longer there locally.
Lab Guide
Cisco dCloud
Scenario 15. Webex Hybrid Call for Webex Devices

Call Service Connect is a hybrid service that connects the Cisco Webex Control Hub and your enterprise phone system so that they
behave as one. By extending your on-premises call control to the cloud, Webex cloud devices can make and receive calls using.
Your organization's call activity continues as usual, but extends to the cloud through the Expressway E and C pair. That is how users
can receive/make PSTN calls from Webex devices.
Call Service Connect requires an Expressway pair for SIP calls, which can be an existing pair already in place for B2B or MRA
deployments.
The two key parts of this feature are:
• Mutual TLS: For Call Service Connect, your Expressway-E server must establish a mutual TLS relationship with the Cisco
Webex Control Hub. This security allows both the cloud and your enterprise to identify each other. Trusted root certificates
must be installed on both sides.
• Webex-RD (Remote Device) (Still Spark-RD at the time of writing this guide): This device is attached to a user's work
number. It links a user's Cisco Webex account SIP identity to the enterprise SIP identity. From a technical standpoint, the
Webex-RD masks outbound calls from Cisco Webex with a user's work number. Incoming calls ring both the user's Cisco
Webex Teams app and desk phone.
This feature builds upon Call Service Aware, which complements enterprise calls with instant content sharing, convenient access to
your call history, and the option to redial callers from anywhere. Call Service Aware supports and is a prerequisite for Call Service
Connect.
The following points provide a functional overview of this feature:
• Hybrid Call Services for Cisco Webex Devices will create and use a Cisco Webex Remote Device (Cisco Webex-RD) in on-
premises Unified CM to route calls to enterprise extensions, users, and PSTN.
• Features from on-premises phones (such as hold, transfer, and conference) can include the Cisco Webex device.
• Any calls from Places to PSTN or on-premises extensions are anchored to the Cisco Webex-RD in Unified CM.
• You can view the full deployment guide here.
Configuring Call Service Connect in Cisco Webex Control Hub Management
In this section, you will begin the initial setup in Cisco Webex Control Hub. This includes specifying the desired site name for your
company to create SIP addresses for all users, enable Call Service Connect, and then specify the SIP destination to point to your
Expressway-E with mutual TLS. In this lab, we have a working Expressway-C/E pair that handles B2B and MRA. There is also a
requirement for a DNS SRV record that points to the SIP mutual TLS port on your Expressway-E server. This SRV has been pre-
configured for you and is publicly available on the internet for your session.
The first task is to configure a custom SIP domain for your organization so your users can be directly dialed.
1. Re-open your browser to the Control Hub.
2. On the left-hand menu, click Settings. Scroll to the SIP Address for Cisco Webex Calling section to view the Control Hub
configuration.
Lab Guide
Cisco dCloud
As you can see, the prefix for your SIP domain is displayed. This was configured for you already during the base setup. In the lab, we
have used the @cbXXX.dc-YY.com domain assigned to your session. The lab had you shorten it to cbXXXYY to make it easier to dial
users. After it is configured, the platform will create real SIP addresses and DNS records that are reachable on the Internet.
Configuring Domain Verification
Domain verification is essential to the security and integrity of your organization. Verification proves to us that you own a particular
domain and is required for some services to work, such as Call Service Aware and Call Service Connect.
If your company has multiple domains, add each domain one at a time. For example, if you have users in sales.example.com and in
support.example.com, you must add both domains.
If your organization enforces email addresses, you are presented with warnings about possible user lockout. You are forced to verify
and remove domains in a particular order to prevent administrator lockout. When adding domains, for example, you must add the
administrator domain first, followed by all other domains.
For every domain that you add, you receive a verification token that you must add to your DNS TXT record. If you add multiple
domains and, therefore, receive multiple tokens, we recommend that you keep each token in a separate DNS TXT record. If that is
not possible (for example, if your private domain does not support more than one DNS TXT record or you can only edit SPF or
custom records), please contact Cisco Technical Support for manual verification.
When adding a verification token to a DNS TXT record, we recommend two things:
• Enter the token as a separate line at the beginning of your DNS TXT record.
• Enter the token with the following prefix: cisco-ci-domain-verification=<token>. This unique identifier helps you with
search functions in the future and distinguishes Cisco verification tokens from other information presented in your DNS TXT
record.
The previous explanation was for your information only. In the lab, the DNS TXT record has already been created for your session.
The domain verification should have been pre-configured for you but let’s verify.
On the Settings page above SIP Address for Cisco Webex Calling, there is a Domains section. During the base setup the domain was
pre-configured for you and verified. So the following steps are for your reference only and do not need to be completed in the lab.
(If by chance the domain is not listed and verified then you can complete the steps to finish the configuration.)
1. Click Add Domain.

2. The domain that was assigned to your session is listed in the box. If it is not, enter it now.
3. Click Add.
4. The status will now register as pending. [ ].
5. Click the ellipse [ ] and choose Verify Domain from the menu.
You will see a pop-up screen that lists a DNS verification token.
As mentioned earlier, you would then take that verification token and create a TXT record on your DNS server that resolves to the
domain you are adding. Once the TXT record is created then you would then click Verify to verify the domain. If the verification
token is found and matched, the domain status changes to verified.
Lab Guide
Cisco dCloud
If a verification token was not added successfully, try adding it to your DNS server again. Wait for the DNS cache to update and look
at the Time To Live (TTL) of the TXT record in your DNS server. TTL can be configured to allow your error to be cached for many
hours or days.
In this lab, you will not have to add the DNS TXT record because it has been already added for you.
6. Click Verify.
After clicking Verify, your status should now show as verified [ ].
Enabling the Call Connector
1. Click the Services tab. Under Hybrid Call, click Set Up.
2. On the Hybrid Call Service Setup pop-up window, click Next.
3. Select Select an existing Expressway cluster to add resources to this service. Use the drop-down list box to choose
HS Cluster 1. (This was named in the Calendar Service scenario. If you named it something different, then choose that.)
NOTE: If you skipped the hybrid calendar section, you will need to register a new Expressway now. This was completed
in the hybrid calendar section earlier. To do that, select the first radio button and enter exp-cc.dcloud.cisco.com into
the box, click Next, and lastly enter HS Cluster 1 as the name. Then you can continue with the next step below.
4. Click Next.
5. Click Go to Expressway.
6. Login with admin/dCloud123!
NOTE: Again, if you skipped the hybrid calendar section, you will need to finish registration of the new Expressway now.
This was completed in the hybrid calendar section earlier. To do that, check the box for I want Cisco to manage the
Expressway CA certificates required for this trust. Then click Register. On the next screen, check the box next to
Allow Access to the Expressway and then click Continue.
When you activated this service, a new Call Connector was initiated to download and install to the Expressway-C connector host
using the Management Connector. After the Service Status of the Expressway host reads Not configured, that tells you the Call
Connector was successfully downloaded and installed.
Configuring Call Service to Connect SIP Destination
1. Back on the Control Hub on the Services tab, click Edit settings under Hybrid Call.
2. On the Call Service page, scroll to the Call Service Connect section.
3. Click Activate to turn on the service.
4. In the SIP Destination box that appears after turning the services on, enter mtls.cbXXX.dc-YY.com and click Save. (Remember to
replace the XXX and YY with the specific numbers assigned to your session.)
Lab Guide
Cisco dCloud
Call Service Settings
This now points to the DNS SRV record that was created for your session, which is _sips._tcp.mtls.cbXXX.dc-YY.com.
While you are on this page, notice some settings that are available.
General section it gives you an option, like the calendar service earlier, to send an email notification if there are service-impacting
alarms or software upgrades.
Scrolling down to the bottom of the Call Service Connect section, you will see you have the option to upload your own self-signed
certificates.
Lastly, you can deactivate the service on this page, which will remove the services from all users and remove the connector from the
expressway connector host.
Configuring Call Connector on Expressway-C Connector Host
In the next few sections, you will configure the Expressway-C host for the Cisco Webex Hybrid Call aware service.
1. Return to the Expressway connector host browser tab opened earlier.
2. On the Connector Management page, click the Call Connector link. Also found by selecting Applications>Hybrid Services>Call
Service>Unified CM Servers.
3. Click the Cisco Unified CM servers configured link.
4. Click New.
Unified CM Servers
Unified CM Address cucm1.dcloud.cisco.com
Username webex
Password dCloud123!
Lab Guide
Cisco dCloud
Unified CM Servers Configuration
NOTE: The webex user account was pre-configured for you. If you would like to view the details on how to create this
account go to Appendix B.
6. Click Verify Credentials.
7. After the page refreshes, a new Call Service Connect Configuration section appears.
8. Configure the following from the table below.
NOTE: Fields will show up after changing the drop-down menu to Automatic.
Call Service Connect Configuration
Cisco Webex Remote Device Configuration Type Automatic
Device Pool dCloud_DP

Location Hub_None
Calling Search Space Call_Everyone
Reroute Calling Search Space Call_Everyone
9. Click Add.
CTI and AXL Statuses may show UNABLE_CONNECT status. You can ignore this status, as it will change later.
10. Navigate to Applications > Hybrid Services > Call Service > Call Service Overview.
11. Change the Active drop-down menu to Enabled and then click Save.
After the page refreshes, the Status should read running [ ].
Configuring Cisco Unified CM for Call Service Connect
In the next few sections you will configure the Expressway-C host and Unified CM for the Cisco Webex Hybrid Call service connect.
You will now configure Cisco Unified Communications Manager to receive calls directly from Expressway-E through Expressway-C
and assist with cloud-to-enterprise URI routing.
Lab Guide
Cisco dCloud
NOTE: Cisco Webex Control Hub does not support caller ID masking. If caller ID is blocked, users might experience
problems during a call, such as seeing a guest caller ID when they are actually talking to a colleague. To avoid these
problems, be aware of these high-level configuration points:
- The SIP trunk between Expressway-C and Unified CM must send caller ID.
- Caller ID for any users who are entitled for Call Service Connect must not be blocked at the originating cluster or
anywhere in the call path, such as on inter cluster trunks.
1. Go back to your web browser tab for Unified CM (https://198.18.133.3/ccmadmin) and log in, if needed, with these credentials:
2. Next, you will configure the Cluster Fully Qualified Domain Name parameter. If you already completed the Webex Edge Audio
scenario then you have completed this task already. If this is the case, skip to step 7.
3. Navigate to System > Enterprise Parameters.
4. Search (CTRL+F) for “fully”, which will bring you to the setting Cluster Fully Qualified Domain Name.
5. There will already be a FQDN of cucm1.dcloud.cisco.com. Leave that FQDN in the box and enter your sessions domain name at
the beginning, cbXXX.dc-YY.com, and then leave a space in between the two domains. Remember to replace the XXX and YY
with your specific domain information.
Cluster Fully Qualified Domain Name
NOTE: The domain name that you are using for Webex must be the first in the list. The Cisco Webex Control Hub uses
the first entry and ignores any other ones.
6. Click Save.
7. Navigate to Device > Device Settings > SIP Profile then click Find.
8. Click the Copy icon [ ] next to the existing profile called Standard SIP Profile For Cisco VCS.
9. Change the Name to Standard SIP Profile For Cisco Webex Hybrid Call. Also change the description if you would like.
10. Toward the bottom of the page, for the Early Offer support for voice and video calls setting in the Trunk Specific Configuration
section, choose the option Best Effort (no MTP inserted).
Lab Guide
Cisco dCloud
Early Offer Support for Voice and Video Calls
11. Click Save.
NOTE: Because the lab has an existing Expressway-C/E pair that runs MRA and B2B, you will need to create a separate
SIP Trunk Security Profile that uses a different port. The C/E pair currently uses port 5560. It’s recommended to use 5561
for hybrid services.
12. Navigate to System > Security > SIP Trunk Security Profile then click Find.
13. Click the Copy icon [ ] next to the existing profile called Non Secure SIP Trunk Profile.
14. Change the Name to Non Secure SIP Trunk Profile for Webex Hybrid Call and add a Description, if you would like.
15. Change the Incoming Port to 5561 and click Save.
17. Change the Trunk Type to SIP Trunk. Leaving the rest as default, click Next.
18. Configure the following settings from the table below.
Hybrid Services Trunk Configuration
Device Information > Device Name Webex_Hybrid_Call
Device Information > Device Pool dCloud_DP

Outbound Calls > Calling and Connected Party Info Deliver URI and DN in connected party, if available
Format
SIP Information > Destination Address 198.18.133.152 (This is the existing Expressway-C used for B2B/MRA)
SIP Information > SIP Trunk Security Profile Non Secure SIP Trunk Profile for Webex Hybrid Call
SIP Information > SIP Profile Standard SIP Profile For Cisco Webex Hybrid Call
19. Click Save, OK, Reset, Reset, and Close.

Lastly, configure a SIP route pattern that matches the cloud URI IPv4 pattern sent out this new SIP trunk to the Expressway-C server.
20. Navigate to Call Routing > SIP Route Pattern. Click Add New.
Lab Guide
Cisco dCloud
SIP Route Pattern
IPv4 Pattern *.[rooms][calls][meet].webex.com
Description Routing to Cisco Webex

SIP Trunk/Route List Webex_Hybrid_Call
NOTE: You are using a more specific pattern because earlier in the lab you configured *.webex.com for video mesh,
which points to a different trunk. That trunk points to the video mesh node which is not supported. Using this pattern will
ensure you point directly to the expressway and use the correct zones.
22. Click Save.
Configuring the Expressway-E for Hybrid Call Service
Enterprise calls are routed over the Expressway-C/E pair. In this lab, you will modify these Expressway servers to support Call Service
Connect. In the lab, this pair is currently fully functional to support MRA and B2B, so some of the configured traversal zones already
exists. You will modify this existing traversal configuration as well as create a new configuration to support Call Service Connect.
1. If not already open from before, from Workstation 1, in a new browser tab navigate from the homepage to Collaboration
Admin Links > Cisco Expressway-E.
2. Log in with these credentials:
• Username: admin
3. Now, you will configure mutual TLS. If you completed the Webex Edge Audio scenario you have already completed these steps
and can skip to step 8.
4. Navigate to Configuration > Protocols > SIP.

5. For Mutual TLS Mode, select On from the drop-down menu.
6. Keep the Mutual TLS port at 5062.
7. Click Save.
8. Navigate to Configuration > Zones > Zones and click the link for DefaultZone.
Since this is an existing Expressway-E server, you need to set Enable Mutual TLS on Default Zone to Off. This is currently the default
setting, so there is nothing to configure. However, if this were a new Expressway-E server dedicated to Call Service Connect, this
setting would need to be changed to On.
Lab Guide
Cisco dCloud
Configuring Expressway-E Webex Zone (X8.11 and Later)
At this point, you need to create a new DNS Zone that allows your Expressway-E server to identify and route calls between Cisco
Unified CM and the Cisco Webex Control Hub.
1. On the Expressway-E server, navigate to Configuration > Zones > Zones and click New.
NOTE: In the lab, the expressways are at version X8.11+. In earlier versions this zone is not available to be configured so
a regular DNS zone must be used. Click here to view that configuration, if needed. If you already created this zone in the
Webex Edge Audio section then skip the following three steps.
3. For type, select Webex.
4. Click Create zone.
Configuring a Secure Traversal Server Zone to Expressway-C
Create a dedicated traversal server zone on Expressway-E. Though Cisco Webex traffic can coexist on the same traversal zone with
MRA or B2B, we recommend you create a dedicated traversal server zone on Expressway-E, specifically for handling Hybrid Call
signaling and media. That way, any settings for B2B or MRA won't affect Cisco Webex traffic and vice versa.
Cisco Webex Traversal Zone
Configuration > Name Traversal Server for Webex Hybrid Call
Configuration > Type Traversal server

Connection credentials > Username cisco
H.323 > Mode Off
SIP > Port 7006
SIP > TLS verify mode On
SIP > TLS verify subject name vcsc.dcloud.cisco.com
SIP > Media encryption mode Force encrypted
SIP > Preloaded SIP routes support On
Lab Guide
Cisco dCloud
Creating Search Rules on Expressway-E
You will now create two search rules that will perform the following:
• Identify calls from the Cisco Webex Control Hub and route them through the traversal zone to Expressway-C.
• Identify calls from Cisco Unified CM and route them through the DNS zone to Cisco Webex Control Hub.
1. Navigate to Configuration > Dial Plan > Search rules and click New.
Expressway-E Search Rule Configuration
Configuration > Rule name Inbound Webex Hybrid Call
Configuration > Description Route traffic from Webex to Exp-C

Configuration > Source name Webex Zone
Configuration > Target Traversal Server for Webex Hybrid Call
4. Click New.
Expressway-E Search Rule Configuration
Configuration > Rule name Outbound Webex Hybrid Call
Configuration > Description Route traffic from Unified CM to Webex

Configuration > Source name Traversal Server for Webex Hybrid Call
Configuration > Pattern string .+@.+\.(calls|rooms|meetup)\.webex\.com.*
Configuration > Pattern behavior Leave
Configuration > Target Webex Zone
Lab Guide
Cisco dCloud
Configuring the Expressway-C for Call Service Connect
Next, you will configure the other side of the Expressway-C/E pair to support Call Service Connect. Just like the Expressway-E server
you modified earlier, you will modify an existing configuration as well as make new configurations.
Configuring a Secure Traversal Client Zone to Expressway-E
Just like the zones on the Expressway-E server, it is recommended to create a dedicated traversal zone for Cisco Webex on the
Expressway-C.
1. If not already open from earlier, open a new browser tab to the Expressway-C server (vcsc.dcloud.cisco.com) and log in as
admin with password dCloud123!
2. Navigate to Configuration > Zones > Zones.
3. On the Zones page, click the New.
Traversal Zone for Cisco Webex
Configuration > Name Traversal Client for Webex Hybrid Call
Configuration > Type Traversal client

Connection credentials > Username cisco
Connection credentials > Password dCloud123!
H.323 > Mode Off
SIP > Port 7006
SIP > TLS Verify Mode On
SIP > Media Encryption Mode Force encrypted
SIP > Preloaded SIP routes support On
Location > Peer 1 address vcse.cbXXX.dc-YY.com
Creating a Neighbor Zone for Each Unified CM Cluster
You will now configure the zone to the Cisco Unified CM cluster to which you want to route. Each zone can accommodate six peer
addresses, which supports a Cisco Unified Communications Manager cluster with six nodes. The Cisco Unified Communications
Manager cluster to which this zone will route must be a home cluster. It cannot be an SME or other intermediate routing agent.
The exact port to use for each zone depends on the SIP trunk security profile configured on Cisco Unified CM. Because you have B2B
and MRA configured on these Expressways, it is recommended to use a different port so the new configuration does not interfere
with your existing setup. Port 5062 is what is recommended but any port can be used. In this lab, you will be using 5561 as you
configured earlier on the SIP Trunk Security profile. You will not reuse any existing neighbor zones to Cisco Unified CM for Jabber
MRA.
Lab Guide
Cisco dCloud
1. On the Expressway-C Zones page, click New.
Expressway-C Neighbor Zone Configuration
Configuration > Name UCM Neighbor for Webex Hybrid Call
Configuration > Type Neighbor

H.323 > Mode Off
SIP > Port 5561
SPI > Transport TCP
Location > Peer 1 address cucm1.dcloud.cisco.com
Configure Search Rules on Expressway-C
Now, you will create two search rules, as you did on the Expressway-E server, to route traffic between Unified CM and the cloud.
1. Navigate to Configuration > Dial Plan > Search rules and click New.
Expressway-C Search Rule Configuration
Configuration > Rule name Inbound Webex Hybrid Call
Configuration > Description Route traffic from Exp-E to Unified CM

Configuration > Source name Traversal Client for Webex Hybrid Call
Configuration > Target UCM Neighbor for Webex Hybrid Call
4. Click New.
Expressway-C Search Rule Configuration
Configuration > Rule name Outbound Webex Hybrid Call
Configuration > Description Route traffic from Unified CM to Exp-E

Configuration > Source Any (default)
Lab Guide
Cisco dCloud

Configuration > Pattern string .+@.+\.(calls|rooms|meetup)\.webex\.com.*
Configuration > Pattern behavior Leave
Configuration > Target Traversal Client for Webex Hybrid Call
Configuring Hybrid Call Service for Cisco Webex Devices
The following points provide a functional overview of the feature:
• Hybrid Call Services for Cisco Webex Devices will create and use a Cisco Webex Remote Device (Cisco Webex-RD) in on-
premises Unified CM to route calls to enterprise extensions, users, and PSTN.
• Features from on-premises phones (such as hold, transfer, and conference) can include the Cisco Webex device.
• Any calls from Places to PSTN or on-premises extensions are anchored to the Cisco Webex-RD in Unified CM.
Creating a Directory Number for a Place
Use Cisco Unified CM Administration to configure directory numbers that you want to later assign to devices in a place. You'll also
assign directory URIs to the directory numbers.
1. On Workstation 1 (198.18.1.36), open Chrome. From the home page, navigate to Collaboration Admin Links > Cisco Unified
Communications Manager.
2. Click Cisco Unified Communications Manager and log in as administrator/dCloud123!
3. Navigate to Call Routing > Directory Number and click Add New.
4. For the new directory, enter the details from the table below.
Directory Number Configuration
Directory Number Information > Directory Number \+19725557800
Directory Number Information > Route Partition Base_PT

Directory Number Information > Alerting Name Hybrid Device
Directory Number Information > ASCII Alerting Name Hybrid Device
Directory Number Setting > Calling Search Space Call_Everyone
5. Click Save.
6. After the page refreshes, in the Directory URIs section, enter hdevice@cbXXX.dc-YY.com in the URI box.
7. Choose Base_PT for the partition.
8. Click Save.
Lab Guide
Cisco dCloud
Creating a Unified CM Account for a Place
Even though the devices are registered to the cloud, you can associate a number to them from an on-premises Cisco Unified
Communications Manager (Unified CM). You can use a Unified CM end-user account to represent a place. The place contains Cisco
Webex-registered devices in a physical location.
This account is not tied to a real user. Instead, the account stands in for the devices and provides a PSTN number or extension from
the Unified CM dial pool to the devices in the place.
The call connector for your hybrid call environment associates the place with the account for the device. The connector identifies
the Unified CM cluster that can service that particular place, assigns a directory number and URI, and assigns a Cisco Webex SIP
address. Behind the scenes, the Cisco Webex Remote Device (Cisco Webex - RD) ties together activity in the cloud and the premises.
Some points to consider:
• The email address domain must be one of your verified domain entries in the Cisco Webex Control Hub.
• You require Hybrid Call Service Aware and Connect to be enabled for your organization, but you don't have to enable the
corresponding Cisco Webex user account for Hybrid Services in Cisco Webex Control Hub.
• The Mail ID must be an exact match between both Cisco Webex and on-premises.
• Email address must be unique. Do not use the same account for multiple Cisco Webex places or a Cisco Webex user and a
place.
• The Directory URI for the user must match the Directory URI for the directory number that you created for the place.
• The Telephone Number is the number that will show up on your hybrid-enabled place. You could also use an internal
number or extension. If you have multiple devices in the place, the directory number is assigned to all of them, like shared
lines. From a technical standpoint, a call to this number is sent to the assigned Cisco Webex SIP address, which Cisco Webex
forks to all the devices in the place.
1. Navigate to User Management > End Users.
2. Click Add New.
3. For the new directory, enter the following settings from the table below.
User Configuration
User Information > User ID hdevice
User Information > Last Name Device

User Information > First Name Hybrid
User Information > Directory URI hdevice@cbXXX.dc-YY.com
User Information > Telephone Number See the dCloud session details for the Hybrid Device
DID that translates to the 7800 DN. Also the number
can be found on the desktop of workstation 1 in the text
document named DN_to_DID.txt.
User Information > Mail ID hdevice@cbXXX.dc-YY.com
4. Click Save.
Lab Guide
Cisco dCloud
Creating and Updating a Place for Hybrid Calling
The final step is to update the place you created earlier for your room device.
1. Go back to the Cisco Webex Control Hub (https://admin.webex.com) and choose the Places menu.
Control Hub, go to the Add a Room Device section and follow the steps to add a new device. If your device is still
registered to Unified CM for the Webex Edge for Devices scenario then delete the Place created first and create a new
one registered to the cloud. Once you have a device registered come back to these steps. You can also add a fake device
if you just want to go through the steps.
2. Select the place you created earlier and then click Edit from the fly-out window.
3. Select the Hybrid Calling radio button and click Next.
4. Enter hdevice@cbXXX.dc-YY.com for Mail ID from Unified CM. If pre-populated, delete the Password and leave this blank.
Click Save.
5. Wait for the Call Service to be activated before testing. (See figure below showing activated call service.)
Call Service Activated
Testing the Hybrid Room Device
Once the call service activates, you should now see the DID displayed on the top left of the screen. You can now dial this number
from any PSTN phone and it will ring the room device. You can also dial outbound to the PSTN as well. For outbound dialing rules
and patterns, visit Outbound Dialing Patterns and Blocked International Dialing online.
NOTE: The DID might not show up immediately if you registered the room device before the call service showed as
activated. If the call service has activated and you don’t want to wait for the number to show up, you can restart the
device. It should be displayed after restart.
Lab Guide
Cisco dCloud
Scenario 16. Single Sign-On (SSO)

In this scenario, you have the choice to configure single sign-on with Microsoft Azure or the on-premises AD FS. Without configuring
SSO, you would be using the basic authentication Cisco Webex provides. With that, every user has to set a password the first time
they log in to Cisco Webex. You saw that going through the lab. With SSO, you can utilize the passwords in Azure or Active Directory
so your users only have to use their domain login to sign in to Webex instead of a separate login provided by Cisco Webex.
You can only have one provider configured at a time. You can configure one, disable, and configure the other if you would like. The
first configuration steps will cover Microsoft Azure. You will use the trial and users you created in the O365 Integrations to Webex
Teams scenario. You could also use your own O365 organization if you would like. The second set of steps in configuring SSO in the
lab will be using Microsoft AF FS. Both require for you to download the Cisco Webex Metadata, which you will do now.
Downloading Cisco Webex Metadata
The Cisco Webex Metadata file, which is an XML file, contains all the information necessary for the AD FS environment to
successfully communicate with the Cisco Webex authentication service.
1. Go back to the Control Hub and sign in with Charles if needed. (cholland@cbXXX.dc-YY.com / dCloud123!)
2. On the Overview page, scroll to the bottom of the page to the Licenses card. (or Users card if there are users found for
conversion. Users are not required to be converted for this lab.)
3. Click the cog wheel [ ] next to Single Sign-On.
4. Click the radio button for Integrate a 3rd-party identity provider (Advanced) and click Next.
5. Click the Download Metadata File button, which starts a download of an XML in the format of idb-meta-<org-ID>-SP.xml to the
desktop.
6. Close the Export Directory Metadata screen.
5. To make sure you aren’t locked out of the Control Hub, you will make your O365 administrator an administrator of Control Hub.
7. Navigate to Users and select the O365 administrator you created earlier.
8. Scroll down and select Administrator Roles.
9. Select the radio button for Full administrator privileges and click Save.
Configure Single-Sign On Application Setting in Azure
The full configuration for SSO with Azure can be found in Cisco Webex Control Hub Single Sign-On Integration with Microsoft Azure
online. Note the following:
Lab Guide
Cisco dCloud
For SSO and Cisco Webex Control Hub, IdPs must conform to the SAML 2.0 specification. In addition, IdPs must be configured in the
following manner:
• Set the NameID Format attribute to urn:oasis:names:tc:SAML:2.0:nameid-format:transient
• Configure a claim on the IdP to include the uid attribute name with a value that is mapped to the attribute that is chosen in
Cisco Directory Connector or the user attribute that matches the one that is chosen in the Cisco Webex identity service.
(This attribute could be E-mail-Addresses or User-Principal-Name, for example.) See the custom attribute information in
https://www.cisco.com/go/hybrid-services-directory for guidance.
• Use a supported browser. We recommend the latest version of Mozilla Firefox or Google Chrome.
• Disable any popup blockers in your browser.
• In Azure Active Directory, provisioning is only supported in manual mode. This document only covers single sign-on (SSO)
integration.
1. Go back to the Azure portal (https://portal.azure.com) and sign in with the O365 administrator.
2. In the search box at the top, search for Enterprise Applications and select it from the list.
3. If you configured Azure user synchronization earlier in the lab then select Cisco Webex from the list of applications. You will use
the same application used for user sync. If you did not configure user sync earlier then follow the next sub-steps.
a. Click New Application.
b. In the Add from the gallery section, search for “Cisco Webex”.
c. In the search results, highlight Cisco Webex and then click Add.
4. Navigate to the Single sign-on tab and select SAML. The page will refresh with more configuration options.
5. Click Upload metadata file.
6. Use the open file icon [ ] to select the metadata XML file downloaded earlier and click Add.
7. On the fly-out window that appears, copy the full URL listed in the Reply URL box and paste it into the Sign on URL box.
Sign on URL
8. Click Save and close the fly-out window.
Lab Guide
Cisco dCloud
9. Click the Edit icon [ ] for User Attributes & Claims.
10. If uid is already listed in the Required claim section then skip down to the note below.
11. Click Add new claim.
12. Configure the following:
a. Name: uid
b. Source: Attribute (default)
c. Source attribute: user.userprincipalname
Claim Configuration
13. Click Save.
NOTE: Cisco Webex expects to have an attribute called uid that normally matches the email address of the user (in
Azure, it normally maps to userprincipalname). You must map the attribute to the one that is used to create the user in
Webex Control Hub.
On the Users Attributes & Claims page, the attributes aside from the one that you configured in this step are not relevant
to this integration. You can choose to delete them or just leave them on this screen.
14. Close the User Attributes & Claims page by clicking the .
15. Navigate to the Users and Groups tab on the left.

16. If you completed the user synchronization task earlier then you should have already assigned users to this application. Those
users should be displayed in the list. If you did not complete the user synchronization task, then click Add user and add your
O365 users to the application.
17. Navigate back to the Single sign-on page.
18. On the SAML Signing Certificate section, click the Download link next to Federation Metadata XML and save it to your
computer.
Lab Guide
Cisco dCloud
Import the IdP Metadata and Enable Single Sign-On after a Test
Now that Azure is configured you need to upload the metadata file downloaded from the Azure portal and upload to Control Hub.
1. Navigate back to the Control Hub.

2. Click Settings and scroll to the Authentication section.
3. Click Modify for Single Sign-On.
4. Select the radio button for Integrate a 3rd-party identity provider (Advanced) and click Next.
5. Since you downloaded the Control Hub metadata file earlier, click Next.
6. Click the link that reads file browser and open the Cisco Webex.xml file you downloaded from the Azure portal.
7. After a successful upload click Next.

8. Click Test SSO Connection.
9. A new tab will open and if you are using the same browser you are logged into with the Azure portal with then you should see a
Single Sign-on succeeded message. If you get a login page then login with one of your O365 users.
10. Close the browser tab that opened for the SSO test.
11. Scroll down the page and select the radio button for The test was successful. Enable Single Sign On (if the test was successful)
and click Save.
12. Using one of your Webex Teams clients, sign in with one of your O365 users and notice the new SSO authentication flow.
You have now configured your O365 users to use Azure SSO to login into Webex.
Remember you do have users configured on the on-premises Active Directory server. Since these users do not exist in the O365
organization, they will not be able to log in anymore. In order to allow them to login again, you must disable SSO.
13. You may need to refresh the Settings page by navigating to another page and back to see the status change for SSO. Do that
now if you do not see for SSO.
14. Once you see Enabled for SSO, click Modify.
15. Click the Modify link and select the radio button for Use the built-in identity service for user authentication (Simple).
16. Wait for an SSO Warning pop up and then click Ok.
17. You should see a success message at the bottom right of the screen. Click the X to close the Enterprise Settings window.
Configuring AD FS for Cisco Webex
In this section, you will configure AD FS installed on your session’s AD server to support SSO with Cisco Webex. To accomplish this
task, you use self-signed certificates; publicly trusted signed certificates are highly recommended. As you will see in a moment, in
order for every device to use Cisco Webex they will need to install the Root CA certificate of the AD server. If you were using a
publicly trusted CA to sign your certificates, you would not be required to install the root CA certificate manually on every device.
Note that the certificate common name (CN) must match the AD FS identifier URL.
Lab Guide
Cisco dCloud
If you configured SSO above using Azure, you must make sure you disable the configuration. You can only configure one SSO
provider in Control Hub.
NOTE: You might notice in the topology that we are not using an AD FS proxy server. Because of this, the connection is
straight to the AD FS server from Webex. This is a huge security risk having an internal server accessible from the
internet and should not be used as a best practice for a production environment. Chances are if you have SSO up and
running already and have users accessing internal resources externally, you have a proxy server in place. However, this
lab is more concerned with you knowing how to configure Webex SSO with AD FS and not setting up AD FS itself. Even if
the lab used a proxy server, the configuration would be the same and your entire configuration to connect Webex would
be on the AD FS server as is shown in this scenario.
Configuring AD FS for Cisco Webex
1. Create a remote desktop connection to the AD FS (AD1) server (198.18.133.1) and log in as dcloud\administrator with
password dCloud123! Click Yes/Accept/Continue on any certificate warnings.
2. Open Chrome. From the home page, navigate to Cisco Webex Links > Cisco Webex Control Hub.
3. Sign in with Charles. (cholland@cbXXX.dc-YY.com / dCloud123!).
4. You will need to copy the metadata file you downloaded earlier in the scenario to use with Azure to the AD server. If you did not
download the file or you want to download again, then follow the sub-steps below.
a. On the Overview page, scroll to the bottom of the page to the Licenses card. (Or Users card if there are users found for
conversion. Users are not required to be converted for this lab.)
b. Click the cog wheel [ ] next to Single Sign-On.
c. Click the radio button for Integrate a 3rd-party identity provider (Advanced) and click Next.
d. Click the Download Metadata File button, which starts a download of an XML in the format of idb-meta-<org-ID>-
SP.xml to the desktop.
e. Leave the Export Directory Metadata screen open.
5. Open AD FS Management by using the icon [ ] in the taskbar.
6. Expand Trust Relationships and click the Relying Party Trusts folder.
Relying Party Trusts
7. Under Actions, click Add Relying Party Trust….
Lab Guide
Cisco dCloud
Add Relying Party Trust
8. Click Start to start the Trust Wizard.
9. Click the radio button for Import data about the relying party from a file.
10. Click Browse. Click the idb-meta….xml metadata file you downloaded to the desktop from Cisco Webex and click Open.
Choose Metadata File
11. Click Next.
12. Enter Cisco Webex as the Display name and click Next.
13. Keep I do not want to configure multi-factor authentication settings for this relying party trust at this time selected and click
Next.
14. Keep Permit all users to access this relying party selected and click Next.
15. On the Ready to Add Trust screen, click Next.
16. Keep the check box checked and click Close.
Lab Guide
Cisco dCloud
Creating AD FS Claim Rule to Allow Authentication from Cisco Webex
The first rule you create tells AD FS which fields to map to Cisco Webex to identify a user.
1. In the Edit Claim Rules for Cisco Webex window, click Add Rule….
2. Keep Send LDAP Attributes as Claims selected and click Next.
3. For Claim rule name, enter Attributes.
4. For Attribute store, click Active Directory.

5. For mappings, map the E-Mail-Addresses LDAP attribute to the uid Outgoing Claim type as seen below. The uid types are not in
the drop-down menu; just type it in manually.
Attribute Claim Rule
6. Click Finish.
7. Click Add Rule… again.
This next rule provides AD FS with the spname qualifier attribute that Cisco Webex would not otherwise provide.
8. Click Send Claims Using a Custom Rule from the Claim rule template drop-down menu and click Next.
9. Type custom in the Claim rule name box.
Lab Guide
Cisco dCloud
10. On the desktop, open the file called Custom rule.txt and copy/paste everything in that text document into the Custom rule:
box. It needs to be modified based on your org as follows:
c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname"] => issue(Type =
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", Issuer = c.Issuer, OriginalIssuer =
c.OriginalIssuer, Value = c.Value, ValueType = c.ValueType,
Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"] =
"urn:oasis:names:tc:SAML:2.0:nameid-format:transient",
Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/namequalifier"] =
"https://adfs.cbXXX.dc-YY.com/adfs/services/trust",
Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/spnamequalifier"] =
"https://idbroker.webex.com/35a15b0a-0eg1-4029-9f63-a8c54df5df59");
• Replace cbXXX.dc-YY.com with the domain assigned to your session.
• The last URL needs to be modified to match the URL found in the Cisco Webex metadata file downloaded earlier. Open that
XML file with WordPad or Notepad and copy the URL that is listed at the beginning for the EntityDescriptor entityID tag, as
shown below. This URL is specific to your organization so it will not be exactly as the screen shot below.
NOTE: It is easier to copy the URL if you open the XML in Notepad or WordPad.
Idbroker URL in the Metadata XML File
Lab Guide
Cisco dCloud
6. The completed rule should look similar to the figure shown below.
Custom Claim Rule
11. Click Finish and then OK.
Configuring Cisco Webex to Use AD FS as SSO Identity Service Provider (IDP)
Now you need to download the Metadata from AD FS and upload to Cisco Webex.
1. Re-open Chrome on the AD1 server and open a new tab.

2. Browse to https://adfs.cbXXX.dc-YY.com/FederationMetadata/2007-06/FederationMetadata.xml. You need to change
cbXXX.dc-YY.com to match the domain you were given for this session.
3. As soon as you browse to that address, click Advanced and then Proceed. The FederationMetadata.xml file will be
automatically downloaded to your Desktop.
4. Go to the desktop and verify the FederationMetadata.xml file is on the desktop.
Lab Guide
Cisco dCloud
Uploading a FederationMetadata.xml File to Webex
Now you upload the FederationMetadata.xml file you created during the AF FS configuration.
1. Go back to the Chrome tab that was open to the Cisco Webex Control Hub from earlier. It should still be at the Export Directory
Metadata screen.
Export Directory Metadata Screen
2. Click Next.
3. Click the radio button for Allow self-signed certificate in Metadata (less secure) since you are using a self-signed certificate.
NOTE: You might need to scroll to view the option. This is not the default option and it MUST be selected for SSO to work
in the lab. It will also cause the FederationMetadata.xml file to not upload properly if this option is not selected.
4. Click the link that reads file browser.
5. In the Open window, click the FederationMetadata.xml file from the desktop and click Open.
Lab Guide
Cisco dCloud
You should receive a Successfully imported IdP metadata file screen.
Successful Import
6. Click Next.
7. Click Test SSO Connection.
This opens a new browser tab to test SSO.
8. Sign in as cholland with password dCloud123! Note the “i” in the password is the number one (1) and not an exclamation mark
(!).
If successful, you should see a Single Sign-on succeeded message. If it fails, refer to the steps below.
SSO Successful
9. Close that browser tab.

10. If you had a successful test, on the Test SSO Setup screen click the radio button for The test was successful. Enable Single Sign
On and click Save. If it was not successful, click the second radio button, go back through to check your configuration, and try
again. If you mistyped the login information, you need to close your browser to clear the login cache information.
SSO has now been enabled for your organization.
Lab Guide
Cisco dCloud
11. Close the RDP connection to AD1.
IMPORTANT: To prevent future issues in the lab, if you have any browsers logged into the management portal as
Charles using the basic authentication, log out now and log back in using the SSO credentials.
NOTE: If SSO ever fails for the customer organization, the partner administrator can log into the partner portal and access
the customer organization from there. Since you do not have access to the partner administrator account in the lab, if you
need to disable SSO for some reason then navigate to the C:\dcloud folder and right click the disable_sso.ps1 file and
choose Run with PowerShell. After the script finishes, SSO will be disabled for the organization.
In the lab, you will get an error each time you are signed out of Cisco Webex. This is due to the Single Logout Service that
is not configured on AD FS but is in the default metadata file downloaded from AD FS. To prevent this error on logout, you
can either configure Single Logout or delete the following out of the FederationMetadata.xml file and re-upload to Webex.
The AD FS Single Logout service goes beyond the scope of this lab.
Testing SSO on Workstation 1
Now you can test logging in using SSO from an account you have enabled for Cisco Webex Teams. First, you can test from
Workstation 1.
1. If not connected already, create an RDP connection to Workstation 1 (198.18.1.36) and log in as dcloud\cholland with password
dCloud123!
2. Open Cisco Webex Teams using the icon on the desktop.
3. Agree to the terms and enter the email address of Charles cholland@cbXXX.dc-YY.com and click Next.
4. You should reach the AD FS single sign-on page.
5. Enter cholland for the username and dCloud123! for the password, which is the Active Directory password for all users in this
lab.
6. Click Sign in.
Your Cisco Webex Teams application should now log in successfully using SSO.
Lab Guide
Cisco dCloud
NOTE: Throughout the lab, if you ever get a sign-in failed message, you probably need to clear your browser’s cache
because you are logging on with multiple user accounts. The fastest way is to close your browser completely or you can
use separate browsers for each user.
Installing the AD CA Root Certificate
This section guides you to install the CA certificate for the AD server onto your own laptops and mobile devices. The reason you
tested SSO first from within Workstation 1 is that the CA certificate is already installed on it as well as Workstation 2. Since you are
using a self-signed certificate in this lab, you need to install this CA certificate to your mobile devices as well as you own computer. If
they are not installed, the Webex Teams app shows a completely white screen after submitting the email address for the user.
To download the CA certificate, open your browser and navigate to https://dccacert.s3.us-east-2.amazonaws.com/dcloud-AD1-

CA.cer. This downloads a dcloud-AD1-CA.cer file.
1. Open this/these certificate/s on your device and install it/them. Basic instructions are below.
• For Mac, open the certificate and Add it to the login keychain.
o After adding the certificate, in Keychain Access window (if not open, then open Keychain Access app) complete a
search for dcloud-ad1-ca and open the certificate to view the properties.
o Once open, expand Trust and change the When using this certificate drop-down list box to Always Trust. Then close
out the certificate and keychain access.
Installing dCloud Root Cert
Lab Guide
Cisco dCloud
• For iOS, email yourself the certificate, open it on the device, and go through the screens to install it. Then navigate to
Settings > General > About > Certificate Trust Settings and trust the dcloud-AD1-CA certificate you just installed.
• For Android, rename the .cer extension to .crt. Email yourself the certificate, open it on the device, and go through the
screens to install it.
• Note that certain web browsers, like Firefox, may require you to import the certificate into the browser itself.
Testing SSO with Your Own Browser
In this section, you will test SSO using Anita. First, check to see if Anita received an email from Cisco Webex.
1. From your own computer, open a different web browser and/or clear the browser cache if you have used it already to log into
Webex Teams with a different user. You can also use the private/incognito mode of your current browser.
2. Navigate to https://teams.webex.com.
3. Enter the email address aperez@cbXXX.dc-YY.com and then click Continue.
4. Go to the Cisco dCloud SSO page. Accept or proceed through and certificate warnings. (Remember you are using self-signed
certificates in the lab.)
5. Sign in as aperez with the password dCloud123!
6. You should now be logged into Webex Teams. Feel free to log in with any of the users in the organization anywhere you would
like: web, mobile, or desktop. All user passwords are dCloud123!
Lab Guide
Cisco dCloud
Appendix A. Cisco Webex Password Reset Procedures

In some cases, it may be necessary to reset the password of a Cisco Webex user account. The following are the steps to complete a
password reset for Charles Holland.
1. Navigate to the Webex Teams web client (https://admin.webex.com) and enter the email cholland@cbXXX.dc-YY.com.
2. Click Next.
3. On the next page, verify it looks similar to the image below with exception to the XXX and YY parts of the domain. If it does look
similar, continue to the next step.
Correct Sign-in Screen
4. If your screen looks similar to the sign-in the image above, click the Forgot password? link at the bottom.
5. An email was sent to Charles with reset instructions. Using remote desktop, connect to Workstation 1 (198.18.1.36), log in as
dcloud\cholland with password dCloud123! Open Outlook if not open already. (You can also use OWA to access every users
email account by going to https://mail1.dcloud.cisco.com/owa and signing in with dcloud\{username} and password dCloud123!)
6. You will see an email in the inbox with the subject Password Reset. Within that email, click Reset password.
7. A browser window will open. Enter dCloud123! in the New Password and Confirm new password boxes.
8. Click Save & Sign In.
9. Close out the browser and continue on with the lab.
Lab Guide
Cisco dCloud
Appendix B. Creating and Confirming an Application User

The following steps show how to create an application user for use with the Cisco Webex Call connector on the Expressway.
1. Browse to https://198.18.133.3/ccmadmin.
2. Log in as administrator with password dCloud123!
3. Navigate to User Management > User Settings > Access Control Group and click Add New.
4. For name, enter Webex Call Connector and click Save.
5. In the Related Links drop-down menu, choose Assign Role to Access Control Group and click Go.
Assign Roll to Access Control Group
6. Click Assign Role to Group and then click Find.
7. Check the boxes next to:
• Standard AXL API Access
• Standard CTI Allow Control of all Devices
• Standard CTI Allow Control of Phones supporting Connected Xfer and conf
• Standard CTI Allow Control of Phones supporting Rollover Mode
• Standard CTI Enabled
8. After clicking those boxes, click Add Selected and then click Save.
Role Assignment
9. Navigate to User Management > Application User and click Add New.
10. For User ID, enter webex.

11. Enter dCloud123! in the Password and Confirm Password fields.
12. Scroll to the bottom of the page and click Add to Access Control Group. Click Find.
Lab Guide
Cisco dCloud
13. Check the box next to Webex Call Connector and then click Add Selected.
14. Click Save.
Lab Guide
Cisco dCloud
Appendix C. Directory Connector Configuration

Cisco Directory Connector is the on-premises application for identity synchronization. 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.
In this lab, there is an Active Directory server to import users from your domain to Cisco Webex. The Directory Connector is installed
on Workstation 1. The Directory Connector can be installed on any trusted member of the windows domain. To save time in the lab,
the Directory Connector was pre-installed for you. The install file can be downloaded from the customer management portal in the
Users > Manage Users > Turn on Directory Synchronization screens.
NOTE: To read more about the directory connector, download the Deployment Guide.
1. Minimize Chrome and Outlook. Click the Search icon [ ] in the taskbar and in the search box in the task bar to search for
Cisco Directory Connector. When found, click the application icon [ ].
2. At the Webex sign in screen, enter cholland@cbXXX.dc-YY.com and click Next.
3. Enter dCloud123! as the password in the next box and click Sign In.
4. Keep the radio button for AD DS selected and click Load Domains.
5. In the drop-down list, choose dcloud.cisco.com and click Confirm.
6. Click Yes on the automatically upgrade pop-up window.
7. Now that the Directory Connector is open, configure it to synchronize the users along with their pictures (avatars).
8. Click Not Now to defer the dry run until later.
9. Click the Configuration tab at the top.
10. Click the Object Selection tab so you can specify the users to synchronize.
The Object Selection page gives you the ability to choose specific 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).
11. Uncheck the box next to Groups.
12. Click the Select button located in the On Premises Base DNs to Synchronize section.
Lab Guide
Cisco dCloud
13. Uncheck the top box next to DC=dcloud,DC=cisco,DC=com to de-select all the check boxes.
14. Check the box next to dCloud and click Select. (You must ONLY select the dCloud container.)
Select OU
7. With exception to the Cloud Organization name, the Object Selection page should look like the screen shot below.
Object Select Tab
Lab Guide
Cisco dCloud
15. Click the Avatar tab and check the box next to Enabled.
Enable Avatar
16. 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.
17. Click Apply at the bottom of the screen.
18. On the pop-up, click Apply Config Changes.
Now you complete a Sync Dry Run to verify the correct users synchronize.
19. Click the Dashboard tab at the top.
20. Click the Sync Dry Run icon [ ] and click OK.
You should see the seven users [ ] that will be added to your organization. There is also one Object that Matched,
which is Charles Holland’s account. If it doesn’t show this, then confirm your settings again.
21. Click Done.
Lab Guide
Cisco dCloud
Now enable the synchronization.
22. Click the Actions menu and choose Synchronization Mode > Enable Synchronization.
Enable Synchronization
23. Click No on the pop-up since you already performed a dry run.
24. Click Enable Now on the pop-up to enable synchronization.
Now complete a full sync.
25. Click the Actions menu and choose Sync Now > Full.
Full Sync
26. Click Yes on the pop-up.

8. 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 showing: .
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 the Launch Event Viewer button in the directory connector. Then navigate to Applications
and Services Logs > Cisco Directory Connector to view all the events.
27. Verify the users have synchronized by maximizing the Chrome web browser that you have open on Workstation 1, which is
connected to the Webex Control Hub (https://admin.webex.com).
28. In the portal, click the Users tab [ ]. (Refresh the page, if you are already there.)
Lab Guide
Cisco dCloud
9. You should see a list of eight users along with their avatars and user information such as email address and name.
NOTE: Users will stay in the Invite Pending status until they log in to Webex Teams and activate their account as well as
set their password.
29. Currently, Charles is the only administrator in the organization. Taylor Bard is another engineer that requires administrative
access to the Webex Control Hub. Select Taylor Bard from the user list.
30. In the fly-out window, select Roles and Security.
31. Click the radio button next to Full administrator privileges.
Full Administrator Privileges
32. Click Save.
10. You will need to disable the directory connector later in the lab to add users manually. While you are here go ahead and disable
the directory connector now.
33. In the directory connector navigate to Actions > Synchronization Mode > Disable Synchronization.
34. Click Yes to disable.
35. Close the Directory Connector on Workstation 1.
You have now successfully synchronized the customer’s on-premises Active Directory, configured users to their Cisco Webex Control
Hub Organization, and assigned another full administrator to the organization.
Lab Guide
Cisco dCloud
Appendix D. Full Local Gateway Configuration

The following is the full configuration that was completed in the lab of the local gateway for reference. Remember the items in red
are places that you need your own lab’s configuration. The figures below were used to create the config.
Sample Local Gateway Config
Lab Guide
Cisco dCloud
Sample Local Gateway Username and Password
crypto pki trustpoint dummyTp
revocation-check crl
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 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
media statistics
media bulk-stats
Lab Guide
Cisco dCloud
no supplementary-service sip refer
no supplementary-service sip handle-replaces
stun
sip
early-offer forced
g729 annexb-all
pattern :8934
pattern :5065
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
stun usage firewall-traversal flowdata
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>"
Lab Guide
Cisco dCloud
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=dcloud9001_lgu>"
rule 30 request ANY sip-header P-Asserted-Identity modify "sips:(.*)" "sip:\1"
voice class dpg 200
voice class dpg 300
voice class server-group 301
ipv4 198.18.133.3 port 5065
no remote-party-id
connection-reuse
srtp-crypto 200
url sips
error-passthru
asserted-id pai
Lab Guide
Cisco dCloud
sip-profiles 200
session transport udp
url sip
error-passthru
crypto 1 AES_CM_128_HMAC_SHA1_80
description Outgoing dial-peer to Webex
session target sip-server
no voice-class sip localhost
Lab Guide
Cisco dCloud
dtmf-relay rtp-nte
srtp
no vad
description Outgoing dial-peer to Unified CM Webex Calling Trunk for inbound
session server-group 301
dtmf-relay rtp-nte
no vad
description Incoming dial-peer from Webex
destination dpg 300
dtmf-relay rtp-nte
srtp
no vad
description Incoming dial-peer from Unified CM for Webex
Lab Guide
Cisco dCloud
destination dpg 200
dtmf-relay rtp-nte
no vad
sip-ua
transport tcp tls v1.2
crypto signaling default trustpoint dummyTp cn-san-validate server
Lab Guide
Cisco dCloud
Appendix E. Webex Hybrid Calendar Service Full Configuration

With Hybrid Calendar Service, you can connect your on-premises Microsoft Exchange, Office 365, or Google's G Suite Calendar
(Google Calendar) environment to Cisco Webex. This integration makes it easier to schedule and join meetings, especially when
mobile; no plugins are required.
Hybrid Calendar Service has no Cisco call control dependency—you can use this service to extend features to Cisco Webex users,
even if you use a third-party UC solution.
To simplify scheduling a meeting, your users can type scheduling keywords and modifiers in the location field of their calendar
invitation.
To Do This… Use Any of These in the Location

Create a Cisco Webex Teams space for @webex:space
meetings, or host the meeting through Cisco
Webex Teams @meet
@meet:space
@spark (deprecated)
Include a clickable link for your Webex Personal @webex
Room
@webex:myroom
@meet:myroom
Your Personal Room URL (for example, https://<company>.webex.com/meet/<hostID>)
Meetings List and Join Button
The meetings list in Cisco Webex Teams lets users see upcoming meetings for the next four weeks. Users see a Join button in the
meetings list and a scheduled meeting notification five minutes before the meeting starts.
Users can add Cisco Webex room and desk devices and Webex Boards to a meeting to make conferencing resources available. If the
device is enabled for the Hybrid Calendar Service, the green Join button appears on the device. (The Join button is also known as
One Button to Push, and is also available to devices that are registered to Cisco Unified Communications Manager, and managed by
Cisco TelePresence Management Suite.) Hybrid Calendar Service-enabled room and desk devices can also show meetings to which
they've been invited in the meetings list.
You can view the full setup guide at https://www.cisco.com/go/hybrid-services-calendar.
Configuring Expressway – C Connector Host
You will now add a new Expressway-C Connector Host to the Customer Organization for use with Cisco Webex Hybrid Services. This
Expressway-C server will have all the required connectors for Cisco Webex Hybrid Services Calendar and Call.
1. Return to the Cisco Webex Control Hub you have open. Verify you are still logged in as Charles Holland and connected to your
sessions VPN.
2. Within the portal, on the left-hand menu, click Services.
3. Under Hybrid Calendar Exchange, click Set Up.
4. Click Next on the Hybrid Calendar Service Setup pop-up window.
Lab Guide
Cisco dCloud
5. At the first radio button, select and enter exp-cc.dcloud.cisco.com into the box and click Next.
6. For cluster name, enter HS Cluster 1.
7. Click Next again.
8. Click Next once more to open a new browser tab to the Expressway.
9. Log into the Expressway as admin with Password: dCloud123!
10. Check the box for I want Cisco to manage the Expressway CA certificates required for this trust.
11. Click Update software & verify connection.
12. After successful verification, click Register. (If prompted to login into Webex enter cholland@cbXXX.dc-YY.com / dCloud123!
for the username / password.)
13. 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 Calendar Connector. The Management Connector manages all the connectors on the Expressway-C server. The
third connector, Call, will install once you enable the Hybrid Call Service later in the lab.
Configuring Exchange
You will now configure an impersonation account to use with the Cisco Webex Calendar Service. The impersonation account needs
to be a mail-enabled account to use as the Service Account. The account does not have to be an administrator, but it must have a
mailbox. In this lab, you will use Charles’ account as the impersonation account.
1. Create a remote desktop connection to the Exchange (MAIL1) server (198.18.133.2) and log in using these credentials:
• Username: dcloud\administrator
2. Open the Exchange Management Shell [ ] using the icon located on the taskbar.
To make copying and pasting of the commands easier, there is a text document on the desktop called Calendar Service.txt. Open
that text document. If you’ve already gone through this configuration before, feel free to copy all the commands in at once (after the
management shell fully opens and you see the [PS] C:\Windows\system32 prompt displayed) and move to step 7.
Lab Guide
Cisco dCloud
The first thing you need to do is assign the account to be used as the impersonation account (hcalendar).
3. Once you get a [PS] prompt, copy the first command in the text document and paste it into the Exchange Management Shell
window at the [PS] prompt and press Enter. The command is:
new-ManagementRoleAssignment -Name CalendarConnectorAcct -Role ApplicationImpersonation -User dcloud\hcalendar
Add Impersonation Role
Next, you will create a throttling policy. A custom throttling policy helps the Calendar Connector work smoothly:
• In Exchange Server 2013, the policy removes EWS limits from the impersonation account, to avoid max concurrency issues.
• In Exchange Server 2010, the policy overrides the default policy. The default is tailored for user load, not for an enterprise
application.
Lab Guide
Cisco dCloud
4. Copy the second command in the text document and paste it into the Exchange Management Shell window. Press Enter. The
command is:
New-ThrottlingPolicy -Name "CalendarConnectorPolicy" -EWSMaxConcurrency unlimited -EWSMaxBurst unlimited -
EWSRechargeRate unlimited -EWSCutOffBalance unlimited -EWSMaxSubscriptions 5000
Add Throttling Policy
Now you will apply the throttling policy to the impersonation account (hcalendar).
5. Copy the third command listed in the text document and paste it into the Exchange Management Shell window. Press Enter.
The command is:
set-ThrottlingPolicyAssociation -Identity dcloud\hcalendar -ThrottlingPolicy CalendarConnectorPolicy
Apply Throttling Policy to hcalendar
Lab Guide
Cisco dCloud
6. To confirm the mailbox is using the new policy, copy the fourth command listed in the text document and paste it into the
Exchange Management Shell window. Press Enter. The command is:
get-ThrottlingPolicyAssociation -Identity dcloud\hcalendar
Confirm Throttling Policy Assignment
7. We will test One Button to Push (OBTP) later; however, while you are on the exchange server now, go ahead and configure a
room mailbox for your room device by entering the following commands in the PowerShell window.
New-Mailbox -Name 'Webex Room Device' -Alias 'webexrd' -room
NOTE: You must restart the Microsoft Exchange RPC Client Access service. To make this easier, there is a batch file to
do this process for you.
8. Double click to run the Restart RPC Client Access.bat file [ ] on the desktop. The batch file should only take a few seconds
to run and the window closes when it is finished.
9. You can now close the Notepad and Exchange Management Shell windows and close the remote desktop connection to the
Exchange server.
Next, you will link the Calendar Connector to Microsoft Exchange.
Linking Expressway-C to Microsoft Exchange
In the next few sections, you will configure the Expressway-C host for the Cisco Webex calendar service. If you haven’t been through
the calendar service configuration on the Expressway-C used with Cisco Webex, it is recommended to go through to learn how to
configure it manually. However, just as the lab guide did for SSO, there is a quick configuration script to run to configure the
Expressway-C host. If you have already been through the configuration and would like to have it completed for you, skip to the
Calendar Connector Quick Configuration section.
Lab Guide
Cisco dCloud
1. Go back to the browser tab for the Expressway-C connector host.
2. On the Connecter Manager page, click the Configure Microsoft Exchange Servers link (Or can also access by navigating to
Applications > Hybrid Services > Calendar Service > Microsoft Exchange Configuration.)
3. Click New.
4. Enter the following configuration parameters from the table below.
Microsoft Exchange Configuration Parameters
Service Account Username dcloud\hcalendar
Service Account Password dCloud123!
Display Name mail16
Type Exchange On-Premises (default)
Enable this Exchange server Yes (default)
NTLM Authentication checked (default)
Basic Authentication checked (default)
TLS Verify Mode Off
Autodiscover Use Autodiscover (default)
Active Directory domain dcloud.cisco.com
Query Mode ldap
Email Address cholland@cbXXX.dc-YY.com
NOTE: In this lab, we will not be using TLS. TLS requires CA signed certificates to be installed on Exchange and the
Expressway. Those steps are in the full setup guide.
5. Click Add.
Configuring the Webex Site
Now you will configure the details for the Webex Meeting Center with CMR Cloud site. You will use the Webex site that was created
during the Webex trial creation process earlier.
For the @webex functionality to work for users in your production environment, verify the following:
• You have at least one Webex Meeting Center with CMR Cloud site.
• The email address in each user's Webex account matches the user's Exchange email address.
1. On the Expressway-C connector host, navigate to Applications > Hybrid Services > Calendar Service > Cisco Conferencing
Services Configuration.
2. Click New.
Lab Guide
Cisco dCloud
Cisco WebEx Meetings Site Configuration
Fully Qualified Site Name cbXXXYY.webex.com (Can verify site URL in Control Hub under Services)
Username Leave blank (delete the contents if there is anything listed in the box)
Password Leave blank (delete the contents if there is anything listed in the box)
Default Site Yes (default)
Example Cisco Webex CMR Configuration
4. Click Add.
Starting the Calendar Connector
1. Navigate to Applications > Hybrid Services > Connector Management.
2. Click the Calendar Connector link.
3. Change the Active drop-down menu to Enabled.
4. Click Save.
After a few moments, the page refreshes and the Status should change to Running [ ]. Since you configured the calendar
connector manually, skip the next section, Calendar Connector Quick Configuration, and move to the section called Enable the
Calendar Service for Users.
Enabling the Calendar Service for Users
Enable two users (Charles and Anita) for the Calendar Service. You will configure these two users manually. You can configure
multiple users in bulk using a CSV template. Later, in another scenario in the lab, you will have the opportunity to configure the user
services in bulk using this method. For now, you configure them individually.
Lab Guide
Cisco dCloud
2. Click Users from the menu on the left.
3. Find Charles Holland in the list and click his account.
4. In the fly-out window, click Edit.
5. Verify all the boxes in the Message and Meeting columns are checked and if not check all boxes and click Save. If they are
selected, click Cancel.
6. In the Hybrid Services section, click Calendar Service.
7. Click the toggle next to Calendar Service to turn it on and click Save.
It will take about five minutes for the status to go from Pending Activation to Activated. While you are waiting, go ahead and verify
the same services for Anita Perez.
NOTE: Activation will not start until each user has logged into a Cisco Webex Teams client once. Since you haven’t
logged into Anita’s account earlier, then you will do that after enabling her account with the Webex services.
8. Click Places on the menu on the left.
9. Select the place you created earlier and click Edit.
NOTE: If you skipped over the room device creation, you can create one now. Click New Place. Give the place a name
and click Next. Choose Other Cisco Webex device and click Next.
10. Toggle on the Calendar option and click Next.
11. Enter the email address of the room mailbox alias you created earlier on Exchange, webexrd@cbXXX.dc-YY.com.
12. Click Save. (Or click Next if you are just now creating a new place.)
NOTE: Enter the activation code into your room device now, if you created a new device. Then close out the Add Place
window.
Lab Guide
Cisco dCloud
The place’s Calendar Service will take about five minutes to become activated.
13. Verify both Charles’s and the room device are activated for Calendar Service. If it is not, wait until they are activated. See note
below.
Charles and Room Device Activated Calendar Service
NOTE: Sometimes it takes a while for users to show as activated in the Control Hub. The Expressway-C connector host
sometimes shows the users activated quicker. On the connector host, navigate to Applications > Hybrid Services >
Calendar Service > Calendar Connector Status. If the users have been activated, you will see the number of users next to
Successfully Subscribed Users.
Test Creating a Cisco Webex Teams Space for Meetings, or Host the Meeting through Cisco Webex
Teams with OBTP
1. If not already connected, create an RDP connection to Workstation 1 (198.18.1.36) and log in with these credentials:
2. If not open already, open Outlook using the icon in the taskbar [ ].
4. Add Anita Perez, Taylor Bard, and Kellie Melby to the To line.
Lab Guide
Cisco dCloud
6. For Location, enter on of the following to create a space meeting:
• @webex:space
• @meet
• @meet:space
7. For OBTP click Rooms… at the end of the Location field.
12. Verify one of the keywords from above are still in the location field and click Send.
The Calendar Connector now reads the keyword from the location field and populates the Webex Teams space information into the
meeting invite, as well as creates a Cisco Webex Teams space with all the participants. After a few moments, open the meeting you
created and you should see the Webex Meeting information located at the bottom of the invite. If it has not populated, close the
meeting and reopen after a few more moments.
13. Bring up the Cisco Webex Teams client on Workstation 1 and log in with cholland@cbXXX.dc-YY.com / dCloud123!
10. If you used the space keywords, you will notice there is a space in your account with a name that is the same as the meeting
invite subject.
14. Click the space and you will notice that meeting details were also posted into this space.
15. Click the Meetings [ ] icon to view meetings list. Select the meeting to view participants including room devices. You can see
if the users accepted the invite as well.
16. Six minutes before scheduled meeting: Once you receive the join notification on your Webex Teams app, click the notification
and then Join With Video.
NOTE: To save time, while you are waiting for this space meeting to start, you can go ahead and schedule another for a
Webex meeting as shown in the next section.
18. End the meeting when you are finished. Feel free to schedule more meetings using the other keywords.
Lab Guide
Cisco dCloud
Test Including a Clickable Link for Your Webex Personal Room with OBTP
Now you will test scheduling a Webex Meeting functionality with OBTP.
1. If the previous meeting is still in progress, right click the meeting in the calendar and select Cancel Meeting then click Send
Cancelation to free up the room devices. Room devices can’t be double booked.
3. Add Anita Perez, Taylor Bard, and Kellie Melby to the To line. You may also add your own email address if you like.
5. For Location, enter one of the following addresses to create a space meeting:
• @webex
• @webex:myroom
• @meet:myroom
• https://cbXXXYY.webex.com/meet/cholland
6. For OBTP click Rooms… at the end of the Location field.
7. Choose the room mailbox you created earlier on the Exchange server and then click OK.
11. Verify the keyword is still in the location field and click Send.
The Calendar Connector now reads the keyword from the location field and setups up the meeting. After a few moments, open the
meeting you created and you should see the Webex meeting information located at the bottom of the invite. If it has not populated,
close the meeting and reopen after a few more moments.
12. Six minutes before scheduled meeting: Once the host, Charles, receives the join notification on his Webex Teams app, click on
the notification and then Join With Video.
Lab Guide
Cisco dCloud
You have successfully tested the Exchange Hybrid Calendar Service using the keyword functionality as well as One Button to Push,
meeting lists, and join notifications.

Cisco Webex Enablement Lab v5

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Cisco Webex Enablement Lab v5

Caricato da

Copyright:

Formati disponibili

Lab Guide

Cisco Webex Enablement Lab v5

Last Updated: first update on 02-MARCH-2020

About This Lab

About This Lab

Scenario 1. Initial Lab Overview and Setup

Scenario 2. Room Device and Feature Configuration

Scenario 3. Webex Hybrid Calendar Service (Quick Setup)

Scenario 4. Webex Edge for Devices

Scenario 5. Webex Edge Audio

Scenario 6. Webex Video Mesh

Scenario 7. Webex Calling

Scenario 8. O365 Integrations to Webex Teams

Scenario 9. Webex Hybrid Message Service Configuration

Scenario 10. Jabber Team Messaging Mode

Scenario 11. Webex Teams Client Features

Scenario 12. Webex Meeting Troubleshooting

Scenario 13. Pro Pack for Cisco Webex Control Hub

Scenario 14. The Webex Board

Scenario 15. Webex Hybrid Call for Webex Devices

Scenario 16. Single Sign-On (SSO)

Appendix A. Cisco Webex Password Reset Procedures

Appendix B. Creating and Confirming an Application User

Appendix C. Directory Connector Configuration

Appendix D. Full Local Gateway Configuration

Appendix E. Webex Hybrid Calendar Service Full Configuration

There are no customizable options associated with this lab.

Cisco Multiplatform Phone (MPP) for Webex Calling;

About This Solution

Cisco Webex Meetings Overview

Benefits of Cisco Webex Meetings include:

• Simple video-first experiences from any device

• Best mobile experience on the market

• Simple joining and scheduling

• Integrated into the tools you use most

• Delivered on a secure, scalable global platform for an uncompromised experience

Cisco Webex Teams Overview

Accelerate Teamwork with these Tools

Cisco Webex Hybrid 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

Available Hybrid Services

Cisco Webex Calling Overview

• An advanced set of enterprise-grade PBX features

• Service that is available across a growing list of countries in every region

Name Description Host Name (FQDN) IP Address Username Password

IM & P IM & Presence 12.5 cup1.dcloud.cisco.com 198.18.133.4 administrator dCloud123!

Exp-C Expressway-C (Core) X12.5 vcsc.dcloud.cisco.com 198.18.133.152 admin dCloud123!

Exp-E Expressway-E (Edge) X12.5 vcse.cbXXX.dc-YY.com Public IP (see admin dCloud123!

Local Gateway CSR1000V N/A 198.18.133.226 admin dCloud123!

AD1 Active Directory, DNS, AD FS ad1.dcloud.cisco.com 198.18.133.1 administrator dCloud123!

Exchange Microsoft Exchange 2016 mail1.dcloud.cisco.com 198.18.133.2 administrator dCloud123!

Workstation 1 Windows 10 wkst1.dcloud.cisco.com 198.18.1.36 cholland dCloud123!

Workstation 2 Windows 10 wkst2.dcloud.cisco.com 198.18.1.37 aperez dCloud123!

Workstation 3 Windows 10 wskt3.dcloud.cisco.com 198.18.1.38 kmelby dCloud123!

Anita Perez aperez dCloud123! Cisco Jabber/Teams 6017 Hybrid

Kellie Melby kmelby dCloud123! Cisco Jabber/Teams 6050 Hybrid

PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION

NOTE: It may take up to 45 minutes for your session to become active.

Session Details Tab Example

Scenario 1. Initial Lab Overview and Setup

3. Open Microsoft Outlook using the icon in the taskbar [ ].