Meeting Server Lab Lab Guide Version 2.6
Table of Contents What is WebEx Meeting Server ................................................................... 3 Lab Overview .............................................................................................. 7 Task 1: Accessing The Lab Equipment ....................................................... 12 Task 2: Connecting to Lab Workstations & Servers ................................... 14 Section 1: Pre Deployment Configurations ................................................ 19 Section 2: Deploying CWMS 1.5 Virtual Machines ...................................... 26 Section 3: Configuring High Availability .................................................... 53 Section 4: Configure CUCM for CWMS Integration ..................................... 62 Section 3a: Configuring High Availability Revisited ................................... 80 Section 5: Post Deploy CWMS Configurations ............................................ 82 Section 6: End User Usage of CWMS ........................................................ 113 End Of Lab............................................................................................... 171
Welcome
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 2 of 171
What is WebEx Meeting Server Cisco WebEx Meetings Server is a highly secure, fully virtualized, behind-the-firewall conferencing solution that combines audio, video, and web conferencing in a single solution. With Cisco WebEx Meetings Server, you can respond to organizational requirements for higher productivity and employee-led innovation, as well as support more dynamic collaboration and flexible work styles. Cisco WebEx Meetings Server also helps you comply with strict security or data privacy requirements, and support locations where Internet access is regulated or restricted. It also allows you to manage your conferencing solution as a capital expenditure instead of an operational expenditure. With Cisco WebEx Meetings Server, you can:
Meet stringent requirements for data privacy and security by bringing Cisco WebEx conferencing behind the corporate firewall Build on your existing investment in Cisco Unified Communications, extending your existing implementation of Cisco Unified Communications Manager to conferencing Enhance individual and team productivity and collaboration with high-quality audio, video, and web conferencing Enable mobile workers to be more productive and engaged with the ability to participate in conferences using a variety of mobile devices Easily manage your entire conferencing environment with the solution's Administration Dashboard
How Cisco WebEx Meetings Server Works Cisco WebEx Meetings Server is a virtualized, software-based solution that runs on Cisco UCS® x86 Servers and VMware. It uses virtual appliance technology for rapid turn-up of services to end users. With Cisco WebEx Meetings Server, there are two options for enabling mobile users to more securely access WebEx conferences without going through a VPN. The first option is to deploy reverse proxy (or edge servers) in the enterprise perimeter (or DMZ). The second option, shown in Figure 1, is to deploy the reverse proxy servers behind your internal firewall, which eliminates all DMZ components and related information security concerns. In addition, Cisco WebEx Meetings Server uses simple port forwarding on ports 80 (HTTP) and 443 (SSL) to minimize the number of ports that need to be opened in your external and internal firewalls. Backend servers integrate with Cisco Unified Communications Manager (UCM) for high-quality teleconferencing. In large enterprise deployments, critical manageability requirements include user provisioning as well as the ability for users to sign in using their corporate credentials. Cisco WebEx Meetings Server supports these requirement by enabling you to utilize LDAP directory services for user management and authentication, or use the industry-standard SAML 2.0 Single Sign On.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 3 of 171
Figure 1. Full Deployment of WebEx Meetings Server behind a Firewall
Benefits for Your Organization Designed to meet stringent security requirements Cisco WebEx Meetings Server is installed behind your corporate firewall for physical security End-user sessions are encrypted using industry standard SSL 3.0, TLS 1.0, and TLS 1.2 All communications between the Cisco WebEx Meetings Server virtual servers are encrypted FIPS encryption can be turned on with a single policy setting, providing U.S. Department of Defense-level security Protect and build on your existing Cisco Unified Communications investments Designed for deployment on top of Cisco UCM, Cisco WebEx Meetings Server allows you to extend your investment in IP telephony to online meetings Align your conferencing capabilities with business and user expectations Deliver the same productive, fulfilling user experience as the SaaS-based version of WebEx conferencing, including: Document, applications, and desktop sharing Annotation and collaboration tools Personal Conferencing Number capabilities provide persistent host and attendee access codes for planned and ad-hoc audio-centric conferencing High-quality video with 360p screen resolution; full-screen video; up to seven simultaneous webcam video feeds and voice-activated switching Recording and playback Consistent cross-platform experience on Windows, Mac, smartphones, and tablets Hosts can schedule meetings directly from their Microsoft Outlook 2007 or 2010 calendars
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 4 of 171
Allow team members on the move to collaborate easily using their mobile devices Meet your organization's expectations for creating a more collaborative environment that connects a distributed, mobile workforce Meeting clients for mobile devices, including iPhones and iPads Start, join, schedule, and attend online meetings from mobile devices Chat, audio, call me, calendar, pass presenter Two-way video on iPad 2.0 and beyond Voice over Wi-Fi on iPad Support for Cisco Jabber™ for Windows (requiring Cisco Unified Presence) can enable users to easily move from a chat session to an online meeting Cisco WebEx Meetings Server is optimized for "bring your own device" (BYOD) enterprises, helping users to more securely sign in, host, and join meetings from mobile devices or Internet-connected PCs without requiring VPN access to the corporate network Easily manage your entire conferencing environment with a web-based dashboard A web-based Administration Dashboard (see Figure 2) makes it easy to manage your entire conferencing environment, including a real-time view of system processes and management reports on usage, licenses, and more Figure 2. Web-Based Administration Dashboard
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 5 of 171
Specifications Platform Requirements VMware v5.0 or v5.1 Cisco UCS servers: for smaller (50 and 250 user) systems: Cisco UCS C220 M3 or above; for larger (800 and 2,000 user) systems: Cisco UCS C460 M2 or above CUCM v 7.1, 8.6, 9.0 or 9.1 (for SIP trunk audio conferencing) Browsers, OS Support Browsers Internet Explorer 8, 9 Safari for Mac OS X Snow Leopard, Lion, Mountain Lion Latest versions of Chrome and Firefox on Mac OS X and Windows
Operating Systems Windows XP SP3, Windows Vista, Windows 7 32 and 64 bit, Windows Server OS 2008 R2 Mac OS X Snow Leopard, Lion, and Mountain Lion iPhone and iPad running iOS 5.1 and above
Integrations Desktop Integrations Microsoft Outlook 2007 SP2 Microsoft Outlook 2010 32- and 64-bit (all SPs) Audio Extends audio conferencing capabilities to Cisco UCM with dual stack IPv6 and IPv4 support SIP trunk audio conferencing supports G.722, G.711, and G.729 audio codecs with optional Transport Security Layer (TLS) and Secure Real-Time Transport Protocol (SRTP) encryption, with no reduction in system capacity High-fidelity G.722 audio conferencing on Cisco IP phones Security Meetings are secured using industry standard SSL 3.0 and 128- or 256-bit AES encryption NIST FIPS 140-2 approved cryptographic algorithms supported Localization Cisco WebEx Meetings Server is localized into 13 languages to support customers worldwide.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 6 of 171
Lab Overview Audience and Prerequisites This document is intended to assist solution architects, sales engineers, field engineers, and consultants in learning the deployment of CWMS and usage of the features of Cisco WebEx Meeting Server. This document assumes the reader has an architectural and administrative understanding of the CUCM and has reviewed the latest CUCM SRND. This is a complex lab with many servers and devices interacting with each other. It is strongly recommended that a dedicated and undisturbed four hour window of committed time is available to the student when completing this lab.
Lab Prerequisites Trainees of this lab should have a basic understanding of the following:
Cisco Unified Communication’s manager (CUCM) SIP call control and media establishment CUCM dial plan (ex. Route Patterns, Translation Patters, etc.) Basic Microsoft
About The Lab The WebEx Meetings Server (CWMS) lab is completely self-paced and virtualized. Although great lengths are taken to make all labs as true to real world as possible, this lab is a virtual lab where pods are cloned, unconventional techniques are utilized that would not typically be done in a production environment. In the lab, we will be using Remote Desktop Protocol (RDP), Jabber softphones as well as ManyCam for virtual PC cameras. The goal of the lab is for the attendee to become familiar with the setup and implementation of a redundant WebEx Meetings Server system. External access form the internet to CWMS attendees is enabled for the lab. For this, live external DNS is used. Although unconventional and for lab purposes only, we will be using SiteB.com for internal DNS URLs and cisco.com for external meeting URLs. Normally, you would have the same domain suffix internally and externally.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 7 of 171
Disclaimer This lab is primarily intended to be a learning tool. In order to convey specific information, the lab may not necessarily follow best practice recommendation at all times. This exercise is intended to demonstrate one way to configure the network, servers and applications to meet specified requirements for the lab environment. 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.
Lab Guide Key The following is a description of the conventions, colors, and notation used through this document: Sections with this background color and this icon touch on the business benefits of the step or task with items and talking points highlighting a value proposition of a Solution. Sections with this background color and this icon cover the technical description of the step or task, with items and talking points of interest to technical audiences. Sections with this background color and this icon provide a lab tip for the step or task. Sections with this background color and this icon are for scenario description: Provides background information for performing a step or task. Sections with this background color and this icon represent a warning: read this section for special instructions and considerations.
Pods There are 20 pods in this lab environment with a designation of one pod per student. Each pod is comprised of one site called SiteB. The student will deploy and configure CWMS Administrator, Internet Reverse Proxy on the students pod ESXi host. All but CWMS related configuration has already been performed on the CUCM, CUC, and IM&P servers for the student before class starts, to conserve time. Each pod will contain the following server configurations at the beginning of the lab:
CUCM 9.1.1 Server – Providing local device registration and call control Cisco Unified CM IM & Presence Server 9.1.1 – Providing Presence and Instant Messaging Cisco Unity Connection 9.11 – Providing Unified Messaging & Voice Mail Two Windows 7 Workstations – Student pod access and call clients vCenter 5.1 Appliance – Deploying and managing CWMS Administrator and Internet Reverse Proxy (IRP) ESXi 5.1 Host – Host server used to deploy and operate CWMS server devices
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 8 of 171
Lab Topology In this lab topology each device is a virtual machine (VM). This lab is operating on Unified Computer System (UCS) B-Series or C-Series systems. VMware ESXi 5.1 is the operating system and hypervisor running on each lab host computer. The lab UCS host computers are oversubscribed and are not following Cisco’s best practices for UC on UCS. Please follow the best practices outlined on the uc-virtualized web site, this web site can be found here. http://cisco.com/go/uc-virtualized This topology represents one CWMS pod, one student per pod
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 9 of 171
Lab Addressing Tables – Internal and External Addresses
Domain SiteB.com Subnet Masks /24
X instructor assigned pod number 20 total pods
Cisc0123 (C – i – s –c – zero – 1 – 2 - 3) is the password used throughout the lab for all workstations and systems.
Host Name SiteB-CUCM911 SiteB-IMP911 SiteB-CUC911 SiteB-AD SiteB-WS01 StieB-WS02 CWMS01 CWMS02 IRP01 IRP02 vCenter
IP Address External 172.16.X.110 172.16.X.112 172.16.X.115 172.16.X.120 172.16.X.201 172.16.X.202 172.16.X.140 172.16.X.141 172.16.X.142 172.16.X.143 172.16.X.130
IP Address Internal 10.1.2.110 10.1.2.112 10.1.2.115 10.1.2.120 10.1.2.201 10.1.2.202 10.1.2.140 10.1.2.141 10.1.1.142 (DMZ) 10.1.1.143 (DMZ) 10.1.2.130
Domain\User Administrator Administrator Administrator Administrator SiteB\SiteB-User01 SiteB\SiteB-user02
[email protected] [email protected] [email protected] [email protected] root
Password Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123 Cisc0123
X=Pod# This lab uses NAT to help distinguish different pods since all pods use the same IP addressing. If you use the VM Workstations to access the servers (CUMC etc.) you will need to use the INTERNAL addresses for the servers, if you use your local computer to access internal devices you will have to use the external (outside) address.
System Version Table Description Cisco Unified Communication Manager Cisco Unified CM IM & Presence Cisco Unity Connection Student Remote Work Stations MS Active Directory Server Jabber PC vCenter ESXi WEMS
Lab Guide Version 2.6
Version 9.1.1.10000-11 9.1.1.10000-11 9.1.1.10000-32 Windows 7 Windows 2008 R2 64 Version 9.1.3 Build 13181 5.1 5.1 1.5.1.6.A(2)
Presented by CAPO – Solutions Readiness Engineers
Page 10 of 171
Connectivity to the Lab Environment Detailed instructions will be given at the beginning of Task 1. Connectivity to the lab will be achieved through a VPN connection via Cisco AnyConnect and thereafter Remote Desktop Procedure (RDP) to the workstations.
Lab Pre-configuration There are many parts of the lab that are prebuilt and preconfigured before the start of class. Namely:
Basic Dial Plan
Users, Passwords, & PINs
Voice Mail Configuration
Jabber clients added to CUCM database
2 Windows 7 workstations per pod with Jabber running at startup and registered to CUCM
Microsoft Windows 2008 R2 server with AD, DNS, DHCP, NTP, FTP, NFS. Most DNS entries configured in advance
Site B is completely pre-configured with exception for the WEMS devices
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 11 of 171
Task 1: Accessing The Lab Equipment Complete this lab exercise to gain connectivity to the lab.
Activity Objective In this activity, you will learn the methods to access the lab equipment remotely.
Required Resources Student computer with high speed access to the internet
This section is for students that have Cisco AnyConnect installed on their computer.
Cisco AnyConnect Pre-Installed
This section is for students that DO NOT have Cisco AnyConnect installed on their computer.
Install and Connect with Cisco AnyConnect SSL VPN Client
The ASA might require an upgrade of the AnyConnect client on the student computer if an older version is installed Step 1 Launch the Cisco AnyConnect VPN client.
Step 1 Open a web browser and connect to https://sre-collab01.cisco.com/student
Step 2 Enter sre-collab01.cisco.com/student Step 3 Click Connect.
Step 2 Click Continue or Proceed Anyway, on security certificate error on the browser. Step 3 At the SSL VPN Portal, enter the Username and Password assigned by the Proctor at the start of the lab (username = cwmspodX). Step 4 Click Login.
Step 4 Enter the lab Username & Password (username = cwms-podX). The password will be assigned by the instructor at the start of the lab.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 12 of 171
Step 5 Click Continue on the Welcome Banner. Step 6 Once logged in the system will start trying to install AnyConnect into your computer’s memory and run from memory.
Step 5 Click OK to login
Step 7 If AnyConnect makes it to connected, continue on to Task 2 Step 6 Click Accept on the connection banner.
Step 8 If AnyConnect is unsuccessful, click the link to download the software to your computer, and install the software directly to your computer
Step 7 Continue to Task 2.
Step 9 Once Software is installed you will need to use AnyConnect to VPN into the lab using the Left Column, for students that already have AnyConnect installed
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 13 of 171
Task 2: Connecting to Lab Workstations & Servers Each pod has two student Windows 7 workstations, and a Windows 2008 R2 server acting as the site b Active Directory and Exchange server. In this section RDP connections to the two workstations and SiteB’s Active Directory server will be established. Step 10
Click Start All Programs Accessories Remote Desktop Connection, from the Student’s personal computer
Step 11
Click Options
Step 12
Select Local Resource Tab
Step 13
Click Settings, under remote audio
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 14 of 171
Step 14
Select Play on this computer & Do Not Record
Step 15
Click OK
Step 16
Select the General tab 1st RDP Session
Step
2nd RDP Session
3rd RDP Session
Step 17
172.16.x.201
172.16.x.202
172.16.x.120
Step 18
siteb\aace
siteb\bbad
siteb\Administrator
Pod # Users Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
Lab Guide Version 2.6
WorkStation 01 siteb\aace 172.16.1.201 172.16.2.201 172.16.3.201 172.16.4.201 172.16.5.201 172.16.6.201 172.16.7.201 172.16.8.201 172.16.9.201 172.16.10.201 172.16.11.201 172.16.12.201 172.16.13.201 172.16.14.201 172.16.15.201 172.16.16.201 172.16.17.201 172.16.18.201 172.16.19.201 172.16.20.201
WorkStation 02 siteb\bbad 172.16.1.202 172.16.2.202 172.16.3.202 172.16.4.202 172.16.5.202 172.16.6.202 172.16.7.202 172.16.8.202 172.16.9.202 172.16.10.202 172.16.11.202 172.16.12.202 172.16.13.202 172.16.14.202 172.16.15.202 172.16.16.202 172.16.17.202 172.16.18.202 172.16.19.202 172.16.20.202
Win2K8R2 – AD siteb\Administrator 172.16.1.120 172.16.2.120 172.16.3.120 172.16.4.120 172.16.5.120 172.16.6.120 172.16.7.120 172.16.8.120 172.16.9.120 172.16.10.120 172.16.11.120 172.16.12.120 172.16.13.120 172.16.14.120 172.16.15.120 172.16.16.120 172.16.17.120 172.16.18.120 172.16.19.120 172.16.20.120
Presented by CAPO – Solutions Readiness Engineers
Page 15 of 171
Step 19
Click Connect
Step 20
Enter Cisc0123, in the password field
Step 21
Click OK
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 16 of 171
Step 22
Your Remote Desktop should look something like this.
Step 23
Repeat steps 10 - 23 two more times to open the following two RDP sessions
Step 24
SiteB-WS02 - SiteB\BBad (on 172.16.X.202) SiteB-Ad - SiteB\Administrator (on 172.16.X.120)
Click Sign In, if either of your Jabber clients do not login. (both workstations Jabber client should be logged in and showing the contact list as shown above)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 17 of 171
Step 25
Click Yes, on the Security Alert on either of the WorkStations if the warning appears. (if the warning does not appear, skip to the next section)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 18 of 171
Section 1: Pre Deployment Configurations In this section the student will configure NON UC related items that are important for allowing CWMS to function properly such as Domain Name Services (DNS) and Exchange mail server settings. Activity Objective In this activity, you will learn the methods to:
Access and configure Microsoft DNS Administrator
Adding DNS A records in a Microsoft Windows 2008 R2 server
Configure Exchange Settings
Required Resources To complete this section of the lab you will need a computer that is connected to the lab via VPN, and an RDP connection to your pod’s SiteB-AD (172.16.X.120)
Adding DNS Entries The lab is using non-split-horizon DNS where all users (internal and external) access the WebEx site URL using the public virtual IP (VIP) address, and the administration web page for CWMS is accessed using a private VIP address. WHY - For this product, the primary difference between a split-horizon and a non-splithorizon network topology is that for a split-horizon system, internal users access the WebEx site URL using the private VIP address. External users (outside the firewall) access the WebEx site URL using the public VIP address. For a non-split-horizon network, all users (internal and external) access the WebEx site URL using the public VIP address. This is a schematic diagram of a non-split-horizon network topology.
Advantages of a Non-Split-Horizon Network Topology Tight control on the traffic that comes in and goes out of a network. Addresses more common, simple DNS network requirements.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 19 of 171
Disadvantages of a Non-Split-Horizon Topology Complex setup, but not as complex as the split-horizon network topology. Internal traffic is directed to the DMZ network. All network traffic from the Internet as well as from the internal (private network) will go to the Internet Reverse Proxy in the DMZ network, then come back to the internal virtual machines. Requires more ports to be opened in the firewall between the DMZ and internal network than the all internal network topology. Automatic system deployment (for 50, 250, or 800 concurrent user systems only) requires a more detailed setup in vCenter. Of the three network topologies, this configuration most affects network performance, since all of the meetings load is through the Internet Reverse Proxy. Because there are multiple hops, network latency is affected as well. This is a schematic diagram of a split-horizon network topology.
Advantages of a Split-Horizon Network Topology Tight control on the traffic that comes in and goes out of a network. There is a separation of network traffic hitting the system, enabling a more distributed spread of the load. The traffic coming in from the Internet will go to the Internet Reverse Proxy. The traffic coming from the internal (private network) will go directly to the internal virtual machines (Admin, and if applicable, Media and Web). Performance and network latency is better than a non-split-horizon DNS, but worse than an all internal network topology. Disadvantages of a Split-Horizon Topology Of the three different network topologies, this is the most complex setup. Requires sophisticated DNS mapping. Requires more ports to be opened in the firewall between the DMZ and internal network than the all internal network topology. Automatic system deployment (for 50, 250, or 800 concurrent user systems only) requires a more detailed setup in vCenter. Because of web redirection, for internal users, the WebEx site URL is replaced with the URL exposing the hostname of the virtual machine containing the web services as well as the Media virtual machines. This section of the lab has been added to emphasis the importance of DNS in regards to the functionality of Web Ex Meeting Server. All system and CWMS entries must be entered into DNS and all names fully resolvable for CWMS to deploy without failure.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 20 of 171
Step 26
From the SiteB-AD (172.16.X.120) RDP session opened earlier
Step 27
Click Start Administrative Tools DNS to open the DNS Manager tool
Step 28
Click the + (plus sign’s) next to SiteB-AD Forward Lookup Zone SiteB.com
Step 29
Select siteb.com to highlight it and right click
Step 30
Select New Host (A or AAAA)…, from the pop-up menu to create a new A record
Step 31
Enter CWMS01, in the name field
Step 32
Enter 10.1.2.140, in the IP Address field
Step 33
Check Create Associated Pointer (PTR) record
Step 34
Click Add Host
Step 35
Click OK, on the DNS record created successfully pop-up message
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 21 of 171
Step 36
Repeat Steps 30 – 35 to add the following DNS A record entries
Be careful and notice that the 3rd octet of the internal address is different than the DMZ addresses. Use this chart to help input seven more entries into DNS Host Internal Host DMZ Name IP Address Name IP Address CWMS02 10.1.2.141 IRP01 10.1.1.142 meetingadmin 10.1.2.150 IRP02 10.1.1.143 vcenter 10.1.2.130 meeting 10.1.1.139 esxi01 10.1.2.135
Step 37
Click Done, to close the new host pop-up window
Step 38
Review the DNS entries make sure they look like the following
Step 39
Close DNS Manager
Step 40
Click Start
Step 41
Enter CMD, in the search field
Step 42
Press Enter, to open the command prompt
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 22 of 171
Step 43
Enter nslookup, in the command prompt window
Step 44
Enter cwms01.siteb.com
Step 45
Press Enter, to activate the above command
Step 46
Observe and make sure the address is resolved by DNS
Step 47
Confirm the follow 3 enters also resolve in nslookup cwms02.siteb.com irp01.siteb.com irp02.siteb.com
Step 48
Enter exit, to close nslookup
Step 49
Enter ping cwms01.siteb.com
Step 50
Observe the address resolves to the appropriate IP address, but does not successfully ping the server because we have not deployed or powered on this server yet. The same should be true of the other three server (cwms02, irp01, irp02).
Step 51
Close the dos prompt
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 23 of 171
Configuration of Microsoft Exchange Access Policies By default Microsoft Exchange 2010 does not allow 3rd party devices to send email without being a known entity. For ease of use in the lab we are going to configure exchange to allow for Anonymous Users to send mail to the system. At various times during the usage of WebEx Meeting Server , such as when creating new users, WebEx will need to send email to the users. In the case of the lab the WebEx server sends the user password reset email to the lab Exchange server which in turns delivers it to the appropriate user. Step 52
From the SiteB-AD (172.16.X.120) RDP session opened earlier
Step 53
Click Start All Programs Microsoft Exchange Server 2010 Exchange management Console
Step 54
Click the + sign next to Microsoft Exchange On-Premises
Step 55
Click and Highlight Microsoft Exchange On-Premises (wait for status bar to complete)
Step 56
Click the + sign next to Server Configuration
Step 57
Click and highlight Hub Transport
Step 58
Click and highlight Default SITEB-AD receive connector in the center section of the Exchange Management Console
Step 59
Click Properties, under actions in the right side of the Exchange Management Console
Step 60
Click Permission Groups tab on the Default SITEB-AD properties pop-up window
Step 61
Click and select Anonymous Users
Step 62
Click Apply
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 24 of 171
Step 63
Click OK
v
Step 64
Close Exchange Management Console
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 25 of 171
Section 2: Deploying CWMS 1.5 Virtual Machines In this section the students will deploy two of four virtual machines (VM). The student will deploy CWMS01 and IRP01, and CWMS02 and IPR02 have been deployed for the student before class began. Activity Objective In this activity, you will learn the methods to:
Deploy CWMS Virtual Machines
Deploy Internet Reverse Proxy (IRP) Servers
Required Resources To complete this section of the lab you will need a computer that is connected to the lab via VPN, and an RDP connection to your pod’s SiteB-AD (172.16.X.120) WHY - This product is packaged as a VMware vSphere compatible OVA virtual appliance and not as a collection of software packages on a DVD. You must have vCenter to deploy the OVA or the product will not install. The one OVA file contains installs for all the different types of server that can be deployed as part of a CWMS system. Admin Virtual Machines – Provides Administrative Functions Internet Reverse Proxy Virtual Machines – Optional server but mandatory if public access is required of the system. Provides public access. Media Virtual Machines – Provides audio, video, telephony and meeting service. Included in the Admin VM in a 50 user system Web – Enable to users to schedule future meetings. Included in the Admin VM in a 50, 250, and 800 user system Cisco WebEx Meetings Server requires customers to run VMware ESXi 5.0, ESXi 5.0 Update 1, ESXi 5.1 or the corresponding VMware ESXi installable Cisco ISO Image. Both these editions contain the necessary drivers required to support the Cisco UCS Servers that are required by Cisco WebEx Meetings Server. System Sizes 50 concurrent users system Typically supports a company between 500 and 1000 employees Primary system (without HA) comprises an Admin virtual machine and an optional Internet Reverse Proxy (for public access)
250 concurrent users system Typically supports a company between 2500 and 5000 employees Primary system (without HA) comprises an Admin virtual machine, a media virtual machine, and an optional Internet Reverse Proxy (for public access)
800 concurrent users system
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 26 of 171
Typically supports a company between 8000 and 16,000 employees Primary system (without HA) comprises an Admin virtual machine, a media virtual machine, and an optional Internet Reverse Proxy (for public access)
2000 concurrent users system Typically supports a company between 20,000 and 40,000 employees Primary system (without HA) comprises an Admin virtual machine, 3 media virtual machines, 2 web machines, and an optional Internet Reverse Proxy (for public access)
Terms Used During the Deployment WebEx Site URL – Secure http URL for users to host and attend meetings WebEx Administration URL – Secure http URL for administrators to configure, monitor and manage the system Public VIP - IP Address that is used for the WebEx site URL. Even though it says public it is used for both internal and external users to access WebEx meetings when deploying a non-split horizon DNS system. Private VIP – IP Address for the Administration site URL, & IP address for WebEx site URL for internal users only , if you have a split-horizon DNS. Cisco WebEx Meetings Server comprises two groups of virtual machines: the internal virtual machines (Admin VMs) and the Internet Reverse Proxy virtual machines. All systems must comprise one or more internal virtual machines. The Internet Reverse Proxy is required only for systems where external users can host or attend meetings from the Internet and mobile devices. Without an Internet Reverse Proxy, only internal and VPN users can host or join meetings. Internal Virtual Machines Internal virtual machines refer to the Admin virtual machine, and if applicable, the Media and Web virtual machines. The internal virtual machines must be on a single, common VLAN or subnet. During the system deployment, you will see error messages if your IP address assignments violate this rule. The system design assumes that all the internal virtual machines, including any HA virtual machines, are connected together on a local LAN, offering high bandwidth, negligible packet loss, and latency under 1 ms, between these virtual machines. The Cisco WebEx Meetings Server system is not designed to be split between multiple data centers. Cisco recommends placing all the internal virtual machines on the same Ethernet switch (usually on the same rack as the virtual machines) with a minimum throughput of 1 Gbps for 50 user and 250 user systems 10 Gbps for 800 user and 2000 user systems If you decide instead to place the virtual machines on different Ethernet switches within the same datacenter, then your network must meet the requirements listed in this section. In this situation, the switch-to-switch trunk must meet the same networking characteristics as the L3 latency and throughput for a single physical switch. Internet Reverse Proxy Virtual Machines Cisco WebEx Meetings Server offers the option of deploying the Internet Reverse Proxy (or edge servers) in the DMZ to facilitate external access. This option provides two advantages. First, all external participants can securely access the WebEx conferences from the internet
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 27 of 171
without going through a VPN. Second, mobile users can join the meetings from a mobile device anywhere as long as there is internet connectivity. Note that the Internet Reverse Proxy is mandatory if mobile client access is enabled. Internet Reverse Proxy is used to terminate all inbound traffic from the internet inside the DMZ. The content is then forwarded to the internal virtual machines through an encrypted Secure Socket Layer (SSL) or Transport Layer Security (TLS) tunnel. This encrypted tunnel is established by the internal virtual machines connecting outbound to the Internet Reverse Proxy. Therefore, there is no need to open TCP ports inbound from the DMZ to the internal network on the internal firewall. However, some outbound ports from the internal network need to be opened on the internal firewall to allow communication with the Internet Reverse Proxy in the DMZ.
The Internet Reverse Proxy virtual machines share the same general networking requirements as the internal virtual machines. For the non-split-horizon and splithorizon DNS configuration, the Internet Reverse Proxy virtual machines are deployed in your DMZ network and not the internal network. Because it is common to separate the internal virtual machines from the Internet Reverse Proxy virtual machines on different racks, servers, and ESXi hosts, Cisco recommends: 50 and 250 user systems—dual redundant 1 Gigabit Ethernet links between the DMZ switches and the switches used by the internal virtual machines. 800 and 2000 user systems—dual redundant 10 Gigabit Ethernet links between the DMZ switches and the switches used by the internal virtual machines.
Sample Network Topology
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 28 of 171
Deploying Cisco WebEx Meeting Server (CWMS) & Internet Reverse Proxy (IRP) In this section the student will deploy two of the four CWMS VMs that are needed for this lab (two of the VMs have already been deployed for the student to save time).
Step 65
Open vSphere Client, on the SiteB-AD (RDP session created earlier) taskbar that you have a RDP session open to
Although VMware is switching from vSphere Client to vSphere Web client, for this lab we will continue to use the standard vSphere client due to various browser and remote access issues found during the development of this lab Step 66
Enter vcenter.siteb.com, in the IP address/Name field
Step 67
Enter root, in the user name field
Step 68
Enter Cisc0123 (C – i – s – c – Zero – 1 – 2 – 3), in the password field
Step 69
Click Login
Step 70
Click Ignore, to dismiss the Security Warning
Step 71
Select Hosts and Clusters, in the inventory section of the screen
Step 72
Click the + sign next to vcenter01
Step 73
Click the + sign next to CWMS
Step 74
Click the + sign next to 10.1.2.135, the pods ESXi host
Step 75
Click and highlight the host 10.1.2.135
Notice that IRP02 and CWMS02 virtual machines have already been created to reduce lab time and to be used during the HA portion of the lab. IRP02 is mislabeled in vCenter as IPR02, The host name is correct.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 29 of 171
Step 76
Select File Deploy OVF Template…
In this next section the lab guide is broken up into columns. Start in the middle column labeled CWMS01 to deploy the CWMS01 admin Virtual Machine (VM), when you finish the column come back to the top of the table and work down the right column labeled IRP01 to deploy the IRP01 VM.
CWMS01 Column
IRP01 Column
Take This Path For 1st VM Deployment
Take This Path For 2nd VM Deployment
Steps
CWMS01
IRP01
Click Browse Skip Step, ova file is already selected Browse to Desktop CWMS Skip, ova file is already selected Select cisco-webex-meeting-serverSkip, ova file is already selected 1.5.x.x.x(x).ova (x = version number) The Cisco WebEx Meeting Server OVA software has already been downloaded to the lab, but can be downloaded from CCO at http://goo.gl/G8Wmiu Skip, ova file is already selected Step 80 Click open Step 77 Step 78 Step 79
Step 81
Click Next
Lab Guide Version 2.6
Click Next
Presented by CAPO – Solutions Readiness Engineers
Page 30 of 171
Step 82
Click Next, after reviewing the OVF details (the next button will be grayed out till the Publisher finishes verifying about 15 seconds, ignore the invalid certificate warning)
Click Next, after reviewing the OVF details (the next button will be grayed out till the Publisher finishes verifying about 15 seconds, ignore the invalid certificate warning)
Step 83 Step 84
Click Accept, to accept the EULA Click Next
Click Accept, to accept the EULA Click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 31 of 171
Step 85 Step 86
Enter CWMS01, in the name field Click Next
Enter IRP01, in the name field Click Next
Step 87
Select 50 User Admin (default)
Select 50 User Reverse Proxy
Step 88
Click Next
Click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 32 of 171
Step 89
Select Thin Provision, for the Virtual Disk
Select Thin Provision, for the Virtual Disk
Format Format Make sure you select THIN PROVISION for this lab only to help reduce hard disk drive space required to operate a 20 pod lab. It is not recommended or supported by the TAC to use thin provisioning in a production network Click Next Step 90 Click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 33 of 171
Pod # Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod
01 02 03 04 05 06 07 08 09 10
CWMS01 VLAN 201 202 203 204 205 206 207 208 209 210
IRP01 VLAN 301 302 303 304 305 306 307 308 309 310
VLAN Chart for step 79 and 80 Step 91
Step 92
Step 93
Select VLan 2xy, (xy = pod# for exp pod 4 would be 204) on network adapter 1
Select VLan 3xy, (xy = pod#) on network adapter 1
You must click on Network Adapter 1 to see the drop down menu for the VLAN. Once you are done with Network 1, click to highlight Network 2 and the drop down will appear. Network 1 and Network 2 should have the same pod VLAN Select VLan 2xy, (xy = pod#) on network adapter 2 they must match
Select VLan 3xy, (xy = pod#) on network adapter 2 they must match
Ignore the Multiple source network warning
Ignore the Multiple source network warning
Click Next
Click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 34 of 171
Step 94
Enter the follow properties a. b. c. d. e. f.
Hostname = CWMS01 Domain Name = siteb.com IPv4 Address = 10.1.2.140 IPv4 Subnet Mask = 255.255.255.0 IPv4 Gateway = 10.1.2.1 Primary DNS = 10.1.2.120
Enter the follow properties a) b) c) d) e) f)
Hostname = IRP01 Domain Name = siteb.com IPv4 Address = 10.1.1.142 IPv4 Subnet Mask = 255.255.255.0 IPv4 Gateway = 10.1.1.1 Primary DNS = 10.1.2.120
Step 95 Step 96
Click Next Click Finish
Click Next Click Finish
Step 97
Wait for CWMS01 to finish (but you can deploy IRP01 at the same time) Click Close
Wait for IRP01 to finish and continue on
Step 98 Step 99
Repeat step 76 – 99 for IRP01 (Right Column) – Can be done while CWMS01 is deploying
Lab Guide Version 2.6
Click Close Continue on to next section below
Presented by CAPO – Solutions Readiness Engineers
Page 35 of 171
HOW – The network settings configured during the VM deployment are controlled though custom virtual machine properties. The OS (Linux in the case of CWMS) is scripted to inherit these properties upon boot of the VM. These settings are easy to change if needed, with the following steps.
Right Click, the VM that needs to be edited from within vCenter
Click Edit Settings, from the pop-up menu
Select Options, tab at the top of the properties window
Select Properties, from the settings list
Edit the desired settings on the right hand Property Configuration
Click OK, to finish editing settings
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 36 of 171
Edit Settings & Powering On Virtual Machines In this section the student will edit some of the settings for the two VMs that were deployed in the previous section. Once the settings are edited the student will power on each VM one at a time and watch the results on the VM console. Step 100 Highlight CWMS01, in vCenter Step 101 Right click CWMS01 Step 102 Select Edit Settings, from the pop up menu Step 103 Enter 7 GB, in the memory Step 104 Click CPU Step 105 Set Number of Virtual Sockets to 3
Step 106 Click OK Do not reduce the CWMS memory or CPU below the default in production networks; this is not supported by the TAC. These steps are only done to facilitate many students on less equipment in the lab.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 37 of 171
Step 107 Click and highlight IRP01 Step 108 Right click IRP01 Step 109 Select Edit Settings, from the pop up menu Step 110 Enter 2 GB, in the memory field Step 111 Set Number of Virtual Sockets to 3 Step 112 Click OK
Step 113 Click and highlight CWMS01 Step 114 Right click CWMS01 Step 115 Select Power Power On
Step 116 Click and highlight IRP01 Step 117 Press CTRL-B, on the keyboard to start IRP01 Step 118 Click and highlight CWMS02
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 38 of 171
Step 119 Click the green arrow just above the VMs to start CWMS02
Step 120 Power On IRP02, (any method desired) At this time all four VM in vCenter should be turned on and booting up, indicated by the green arrow on each VM
Later in the lab you will be testing your CWMS system in conjunction with a UC network. This network consist of a CUCM, CUC, IM&P, 2 Windows 7, and a Windows 2008 R2 server, all of these devices are managed by another vCenter on a different ESXi host. The student will not need to access these VMs for lab. Just in case you are wondering the proctors back-end vCenter looks as follows. The CWMS servers that where just deployed are on a Nested ESXi host Pxy-ESXi01.
Step 121 Click and highlight CWMS01 Step 122 Right click CWMS01
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 39 of 171
Step 123 Select Open Console, this will open a new pop-up window. After a few minutes (wait for it – about 5 min – good time to tweet (#paulstryer) about how great this lab is) you will see the following output (except the address at the bottom will be differ each time you deploy a CWMS VM)
Write down the URL at the bottom of the console output (COPY does not work), this is the only place you will find this URL.This URL will only be used once for initial setup of Primary CWMS admin server HINT: Use the Windows Snipping Tool to capture it without writing it down REMINDER – If you mouse is stuck inside of a VMware console use CTRL-ALT to get the mouse back
Post Deploy Configuration of CWMS01 (admin server) After the VMs have been deployed and turned on, the next step is to login to the primary admin server and step through the following configuration steps. Why – After the virtual machine deployment, the system provides the installer with a passphrase-embedded URL to begin the preliminary part of the configuration. During the configuration portion of the deployment, certain data will be input into the system. The following information is required for the CWMS system to function properly.
Field Name Public VIP Private VIP
Lab Guide Version 2.6
Description IP address for the WebEx site URL (site users access to host and attend meetings) IP address for the Administration site URL (for administrators to configure, monitor, and manage the system) IP address for the WebEx site URL (for internal users only, if you have a split-horizon DNS).
Presented by CAPO – Solutions Readiness Engineers
Page 40 of 171
WebEx Site URL WebEx Administration URL FQDN for the Internal VMs FQDN for the IRP
Secure http URL (all lowercase characters) for users to host and attend meetings. Secure http URL (all lowercase characters) for administrators to configure, monitor, and manage the system. Depending on the system size you selected, the fully qualified domain name (all lowercase characters) of the media and web virtual machines. If you plan to add public access, then you need to enter the fully qualified domain name (all lowercase characters) of the Internet Reverse Proxy virtual machine.
Be sure to add the virtual machine FQDNs, IP addresses, WebEx and Administration site URLs, and VIP addresses to your DNS servers before you start the system deployment. CWMS will use this information to check network connectivity during the deployment. To avoid any DNS issues, you may want to test these URLs and IP addresses before you start the OVA deployment. Otherwise, the system deployment will fail until you correct these errors.
Step 124 Open Internet Explorer, form the RDP session connected to SiteB-AD (172.16.x.120) Step 125 Enter the URL from the CWMS01 admin console (as seen in step 123 above) in the browsers address field of IE (the URL is cAsE sEnSiTiVe) Step 126 Click Continue to this website (not recommended)
Heed the warning DO NOT close the browser until this section is finished or you will have to start over by deleting the VM and re-deploying the OVA again.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 41 of 171
Step 127 Select English Step 128 Click Next
Step 129 Select Deploy a New System WHY – By selecting “Deploy new system” you are assuming this is a new system and not to be used with an existing system. Earlier it was shown that the bigger the number of users the more servers you will need to operate your WebEx meeting server environment. If the system was initially built for 50 users and is being upgraded to accommodate 2000 users, more server will need to be added to the existing system, in this case selecting “to expand the capacity of a current system” would be selected. Step 130 Click Next
Step 131 Click Next
Step 132 Select Install a primary system WHY – When using the manual method of deploying CWMS the administrator will install all the VM. The first admin and IRP server will be used in the primary mode, and if you install HA the second admin and IRP server will select “create a high availability (HA) redundant system. In this lab the student will perform this configuration twice once on the primary system and one on the HA or backup system, select primary the first time and HA the second time.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 42 of 171
Step 133 Click Next
Step 134 Select Manual Step 135 Click Next
Step 136 Select Create an Internet Reverse Proxy virtual machine (default) Step 137 Click Next
Step 138 Enter 10.1.1.139, public virtual IP address (VIP) for external access to meetings WHY – Inside the high availability system, there is a second network interface in the active administration and Internet Reverse Proxy virtual machine that is configured with the virtual IP address (VIP). The administration and WebEx site URLs use this virtual IP address to access the administration and WebEx sites. In the event of failover, the virtual IP address is moved over to the new active virtual machine. Thus, it provides access redundancy to the administration and WebEx site. Public VIP is the IP address that both external and internal users (non-split horizon) use to access meeting, and is a virtual address that points to the active IRP. Private VIP is the IP address that is used by the administrators to access the admin VMs.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 43 of 171
Earlier in this lab the students added entries pointing to the public and private VIPs in DNS Meetingadmin.siteb.com = 10.1.2.150 Meeting.siteb.com = 10.1.1.139
Step 139 Click Next
Step 140 Enter 10.1.2.150, for the private virtual IP (VIP) Step 141 Click Next
Step 142 Enter srecwmsXY.cisco.com (xy = pod#), in the WebEx site URL (must be in DNS) Step 143 Enter meetingadmin.siteb.com, in the WebEx Administration URL (must be in DNS)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Page 44 of 171
Step 144 Click Next
Step 145 Click Next, after reviewing network configuration
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 45 of 171
Step 146 Review the Hostnames and deploy the VM page, notice the system is waiting detect the presences of the IRP server. The student will return to this page and fill in the IRP01 information in a few steps
Remember DO NOT close the IE browser during this first CWMS initialization phase or the VM will have to be deleted and redeployed form the start.
Step 147 Switch to the vCenter, in the RDP session to the pod AD server Step 148 Highlight IRP01, in the left side navigation section of the vSphere client Step 149 Right Click IRP01 Step 150 Select Open Console, this will open up in a new pop-up window Step 151 Review the IRPs system check, and notice it is waiting connection from the Admin VM
Step 152 Return to the web browser with the hostnames and deploy the VMs web page the student was just configuring on.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 46 of 171
Step 153 Enter irp01.siteb.com, in the IRP FQDN field. This pairs the CWMS admin server with the IRP01 server Step 154 Click Detect Virtual Machines
Notice the IRP is Connected
Step 155 Click Next Step 156 Notice the system does a full system check, this will take a few minutes (ok maybe more then 5, go get a coffee and check email)
(NO they don’t spin)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 47 of 171
Notice all checked out OK
Step 157 Click Next Step 158 Review the VM installation completion, page Step 159 Click Continue
Step 160 Accept browser security certificates
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 48 of 171
Step 161 Enter siteb-ad.siteb.com, in the FQDN of the mail server (keep rest default) Step 162 Click Next
Step 163 Select San Francisco, for the time zone Step 164 Select U.S., for the local Step 165 Click Next
Step 166 Click Confirm, after reviewing settings
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 49 of 171
Step 167 Enter Alex, for the Administrator First Name Step 168 Enter Ace, for the Administrator Last Name Step 169 Enter
[email protected], for the Email address Step 170 Enter
[email protected], to confirm the Email address Step 171 Click Next
Step 172 Enter Cisc0123@ for the new password Step 173 Enter Cisc0123@ to confirm the new password Step 174 Click Submit
Step 175 Enter
[email protected], in the Email address field (default) Step 176 Enter Cisc0123@, in the password field Step 177 Click Sign In
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 50 of 171
If the browser is not waiting to login to the WebEx Administration web page, you can get there by entering the following URL – https://meetingadmin.siteb.com Step 178 Click Close, to close the Welcome pop-up screen (If it appears)
Step 179 Click X, welcome Alex Ace screen Step 180 Click X, to close the yellow VM needs attention warning at the top of the browser (If shown)
Step 181 Review the System Monitor, administration web page (the lab well explore more WebEx admin features over the next few sections of the lab guide)
Step 182 Switch to vCenter, in the RDP session to the AD server Step 183 Click and Highlight IRP01 Step 184 Right click and Open Console on IRP01
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 51 of 171
Step 185 Obverse IRP01 is now connected to Admin VM CWMS01.siteb.com. Previously this server was waiting for connection Step 186 Close the console when done observing
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 52 of 171
Section 3: Configuring High Availability In this section the student will pair the CWMS02 and IRP02, as was done in section 2. The CWMS02/IRP02 pair will be configured as the High Availability HA back up servers for the primary pair CWMS01/IRP01 Activity Objective In this activity, you will learn the methods to:
Pair CWMS02 & IRP02
Configure High Availability
Confirm HA
Required Resources To complete this section of the lab you will need a computer that is connected to the lab via VPN, and an RDP connection to your pod’s SiteB-AD (172.20.X.120) WHY
- Before You Begin You must have successfully deployed a primary system. The primary system is in maintenance mode. Create a backup of both the primary and HA systems.
Considerations Before Adding a High Availability System A high availability system is a redundant system that is added to, and becomes part of your system. It provides high availability in the event of a virtual machine failure. The High Availability (HA) system has the following constraints
The HA system must be at the same release version as the primary system. If you have updated the primary system, then be sure to do the same for the HA system. If you are entitled (with the appropriate service contract), then Cisco recommends you deploy the HA system using the OVA file that is the same base version (before any patches) as the primary system. The HA system size must be the same as the primary system. If you have added public access on the primary system, then you must add it to the HA system as well. The HA system's internal virtual machines must be on the same subnet as the primary system's internal virtual machines. If you have added public access, then the HA system's Internet Reverse Proxy virtual machine must be on the same subnet as the primary system's Internet Reverse Proxy virtual machine. Because this process adds virtual machines to your system, your current security certificate will become invalid and require an update unless you are using a selfsigned certificate. If you previously had an HA system, removed it, and are redeploying a new HA system, then you will not be able to reuse the virtual machines in the previous HA system. You must redeploy a new HA system with new virtual machines.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 53 of 171
Pairing CWMS02 & IRP02 In this section the student will pair up CWMS02 and IRP02 as was done in the previous section for CWMS01 and IRP01 Step 187 Switch to vCenter, in the RDP session to the AD server Step 188 Click and highlight CWMS02 Step 189 Select Open Console Step 190 Observe CWMS02, successfully power on, write down the new administrator URL (when finished continue on)
Step 191 Switch back to the vCenter (if not already on the vCenter) Step 192 Click and highlight IRP02 Step 193 Select Open Console Step 194 Observe IRP02, successfully power on (when finished continue on) Step 195 Switch back to Internet Explorer (IE), on the AD RDP session Step 196 Open a new Browser, tab Internet Explorer IE Step 197 Enter the URL seen in the console output when starting CWMS02 for example https://wems02.siteb.com/Deployment?passphrase=M9PCR84V – Case SeNsAtiVe DO NOT use the example from above, USE the link found at the bottom of the CWMS02 Console in vCenter – Every time you deploy CWMS VM a new passphrase is created for that specific deployment only.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 54 of 171
Step 198 Click Continue to this website (not recommended), to confirm the security certificate in the browser Step 199 Select English Step 200 Click Next
Step 201 Select Deploy a new system Step 202 Click Next
Step 203 Click Next, on the check your system size web page
Step 204 Select Create a High Availability (HA) redundant system WHY - In the previous section the student use the primary system setting for the CWMS01, and now that the 2nd admin is being configured the student is selecting High Availability (HA) Step 205 Click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 55 of 171
Step 206 Select Manual, deploy Step 207 Click Next
Step 208 Check Create an Internet Reverse Proxy virtual machine (default) Step 209 Click Next Step 210 Click Next, to confirm network configuration
Step 211 Enter irp02.siteb.com, in the Internet Reverse Proxy field (remember the IRP02 has already been powered on and is waiting) Step 212 Click Detect virtual machines Notice the IRP is not connected and is waiting
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 56 of 171
Noticed that IRP02 is connected
Step 213 Click Next Step 214 Wait for the System Check, to finish in about 5 minutes Step 215 Click Next If any red Xs you will have to check the acknowledgement before next
If all green check marks just click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 57 of 171
HA Completion Information Screen
Step 216 Close the HA browser tab and return to the CWMS01 Admin browser tab
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 58 of 171
Adding High Availability In this section the students will connect to CWMS01 admin web page the primary system, and add HA, enlisting CWMS02/IRP02 pair to play back up for the primary system. Step 217 Click System View More, under system in the center section. If you are logged out of meetingadmin.siteb.com the user =
[email protected] – password = Cisc0123@
Step 218 Click Add High Availability system
Step 219 Click Continue
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 59 of 171
Step 220 Enter cwms02.siteb.com, in the FQDN admin VM for HA field Step 221 Click Continue
Step 222 Click Add, to synchronize data from the primary to secondary system
Note: You cannot cancel this operation once you have started. During this operation we synchronize data from the primary system to the high availability system. Depending on the amount of data, as well as your networking speed, this operation can take up to 30 minutes. During this time, other administrators should not make changes to the system. Step 223 Click Continue, on the maintenance mode warning pop-up message. This will automatically put the system in maintenance mode and star the sync process
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 60 of 171
High Availability will take about 20 minuets to synchronize in the lab environment. At this point we will skip to configuration of the Cisco Unified Communications Manager (CUCM). After the CUCM configuration the student will return to the HA configuration in a section called 3a HA revisited.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 61 of 171
Section 4: Configure CUCM for CWMS Integration Understanding CUCM Integration and Operations with CWMS In this section the student will configure call control settings with CUCM to communicate with the CWMS servers. Activity Objective In this activity, you will learn the methods to:
Configure SIP Profiles & Trunks on CUCM
Configure Route Group, Route List, Router Pattern, Translations & SIP Routes on CUCM
Required Resources To complete this section of the lab you will need a computer that is connected to the lab via VPN, and an RDP connection to your pod’s SiteB-AD (172.20.X.120). Local browser on student computer to access CUCM administration page
WHY - Cisco WebEx Meetings Server support both Cisco Unified CM and Session Management Edition (SME). Cisco Unified CM is a central piece of the WebEx Meetings Server architecture that allows the following:
Attendees joining the teleconference by means of Cisco IP Phone or PSTN Integration of legacy or third-party PBXs with Cisco WebEx Meetings Server
Cisco Unified CM integrates with WebEx Meetings Server by means of SIP trunks to provide inbound and callback call control. Customer can choose to turn on security and run Transport Layer Security (TLS) and Secured Real-time Transport Protocol (SRTP) over the SIP trunk connection. A SIP trunk is configured in Unified CM with a destination address of the Load Balancer in WebEx Meetings Server, and then a route pattern (match the call-in access number configured in WebEx Meetings Server) must be used to route calls via the SIP trunk. A second SIP trunk is configured in Unified CM with a destination address of the Application Server in WebEx Meetings Server, and then a SIP route pattern must be used to route calls via the SIP trunk. When an attendee dials the access number to join the meeting, the first SIP trunk is used to send the call. After the call is connected and the caller enters the meeting ID, the Load Balancer issues a SIP REFER to Unified CM to send the caller to the Application Server that hosts the meeting via the second SIP trunk. The system administrator can configure a SIP trunk in WebEx Meetings Server that points to a Unified CM to perform callback. Attendees can provide a callback number and have the system out-dial the number to the attendees to join the bridge. In the case of attendees requesting callback, the WebEx Meetings Server sends the SIP request to Unified CM along with the callback number via the configured SIP trunk. It is imperative for Unified CM to be able to resolve all dial strings received from a callback request to join the meetings. Callbacks may also be disabled system-wide by means of site administration settings.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 62 of 171
Unified CM is in control of all toll restrictions to various countries or other numbers that most enterprises will block, because WebEx Meetings Server does not have any toll restriction blocking itself. WebEx Meetings Server supports the bidirectional SIP OPTIONS ping mechanism. The ping response from the remote end indicates that the remote end is active and whether it is ready to accept calls. Based on the response, WebEx Meetings Server or Unified CM can determine whether to send calls on the current SIP trunk or look for an alternate SIP trunk (if configured) to send calls. Note that SIP OPTIONS ping is supported in Cisco Unified CM 8.5 and later releases. Due to this reason, Cisco recommends using a compatible Cisco Unified CM version that supports SIP OPTIONS ping for Cisco WebEx Meetings Server deployment. Cisco WebEx Meeting server supports CUCM 7.1, 8.6 and 9.x
Configuring CUCM SIP Trunks In this section the student will add SIP trunks to the CUCM configuration to allow communication between CUCM and CWMS. Step 224 Open a browser on the students computer (local browser not the RDP computer) Step 225 Navigate to 172.16.xy.110 (xy = pod#) If navigating from one of the three Windows devices that the student has open via a RDP session be advised you will have to navigate to 10.1.2.110 address which is the NAT inside address of Cisco Unified Communications Manager. It is preferred to navigate from the students browser located on the student’s computer for ease of use.
Pod # Pod01 Pod02 Pod03 Pod04 Pod05 Pod06 Pod07 Pod08 Pod09 Pod010 Pod11 Pod12 Pod13 Pod14 Pod15 Pod16 Pod17 Pod18 Pod19 Pod20
CUCM Ext Address 172.16.1.110 172.16.2.110 172.16.3.110 172.16.4.110 172.16.5.110 172.16.6.110 172.16.7.110 172.16.8.110 172.16.9.110 172.16.10.110 172.16.11.110 172.16.12.110 172.16.13.110 172.16.14.110 172.16.15.110 172.16.16.110 172.16.17.110 172.16.18.110 172.16.19.110 172.16.20.110
Step 226 Click Cisco Unified Communications Manager
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 63 of 171
Step 227 Enable or acknowledge and browser security certificate warnings Step 228 Enter Administrator, in the username field Step 229 Enter Cisc0123, in the password field Step 230 Click Login
Configuring SIP Trunk Security Profiles Step 231 Click System Security SIP Trunk Security Profile
Step 232 Click Find WHY – A SIP profile comprises the set of SIP attributes that are associated with SIP Trunks and SIP endpoints. SIP profiles include information such as name, description, timing retry, call pickup URI, port addresses, and so on.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 64 of 171
Step 233 Click Non-Secure SIP trunk Profile
Step 234 Click Copy
Step 235 Enter CWMS Load Balancer, in the name field (leave everything else default) Step 236 Click Save
Step 237 Click Copy, on the security Profile just created Step 238 Enter CWMS Application Server, in the name field Step 239 Enter 5062, in the Incoming Port field Step 240 Click Save
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 65 of 171
Adding SIP Trunks In this section the student will configure two Security Profiles, and four SIP trunks to integrate CUCM with CWMS. Also a route plan needs to be configured WHY – CWMS integration into CUCM is purely a SIP integration. It is also worth noting that if CUCM is to receive calls on multiple trunks from the same IP address, they must listen on different ports. This is controlled in CUCM by configuring multiple Security Profile with different port numbers. Call scenarios that occur with a CUCM/CWMS integration are as follows 1. Calls dialing from CUCM into CWMS via the access number (lab access # 2999) 2. CWMS out-dials attendees upon entry into meeting 3. SIP Redirect/REFERs In CUCM, there are many ways to build dial plan and routing, which typically include SIP Trunks. For example, we can use a single SIP trunk to point to multiple destinations via DNS SRV records, we can use a single trunk while having with multiple IP destinations (available with CUCM 8.5+), and we can use multiple SIP trunks, each with one or more destinations. The actual route from CUCM to another entity is accomplished with a simple route pattern. With Number 1 above (when dialing into CWMS), regardless of the deployment size chosen, we are performing initial SIP call control with CWMS’s “Load Balancer Server” software mechanism in the media VM. This mechanism load-balances a call-in attendee by responding immediately to with a redirect on port 5062 to the Application Server containing an IVR function where the attendee can DTMF the meeting ID. After going through the CWMS IVR (entering your meeting ID and optional attendee ID), you might, depending on your deployment size, even see a SIP REFER to another media VM where the actual meeting is being handled (mentioned in call flow #3 above). This additional REFER will not occur in the 50 user deployment models seeing that only one media server function is active at any given time, however the initial redirect is always there. This inbound call mechanism is inherited from the WebEx Meeting Center with which CWMS shares a common architecture. WebEx out-dials, as mentioned in #2 above, redirects/REFERs need not occur, as CWMS knows which media server application instance a given meeting resides - therefore attendee out-dials will always leave the appropriate media server. In this lab architecture (one publisher and a 50 user redundant system), Two trunk types will be used (each trunk type distinguished with SIP Trunk Security Profile pair) as described above. One SIP Profile/Security Profile will be used for the Load Balancer Server (CUCM dialing into CWMS), and the other will be used for Redirects/REFERs from CWMS to CUCM. Because there are two redundant media server instances, The CUCM lab VM will need to handle possible 4 IP destinations. As described above, this can be done many different ways. In this lab this is accomplished with 4 SIP trunks: Two Load Balancer Trunks for call-in (which are routed to the Access Number 2999), and two SIP trunks for the SIP redirects/REFERs to the application server.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 66 of 171
Step 241 Click Device Trunks
Step 242 Click Add New Step 243 Select SIP Trunk Step 244 Click Next
Step 245 Fill in the following fields as follows a. Name = CWMS_LB01 b. Description = CWMS Load Balancer 01 c. Device Pool = Default d. Destination Address = 10.1.2.140 (Media Server Instance, in the lab with a 50 user system the media server is the same server as the WebEx Meeting Administration Server (CWMS01 in the lab) e. Port = 5060 (default) f. SIP Trunk Security Profile = CWMS Load Balancer g. SIP Profile = Standard SIP Profile h. Click Save i. Click OK, on the reset trunk message j. Click Reset k. Click Reset, on the pop-up window l. Click Close, on the pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 67 of 171
Step 246 Click Add New, while on the trunk page that was just created Step 247 Select SIP Step 248 Click Next
Step 249 Fill in the following fields as follows a. Name = CWMS_LB02 b. Description = CWMS Load Balancer 02 c. Device Pool = Default d. Destination Address = 10.1.2.141 (Media Server Instance, in the lab with a 50 user system the media server is the same server as the WebEx Meeting Administration Server (CWMS02 in the lab) e. Port = 5060 (default) f. SIP Trunk Security Profile = CWMS Load Balancer g. SIP Profile = Standard SIP Profile h. Click Save i. Click OK, on the reset trunk message j. Click Reset k. Click Reset, on the pop-up window l. Click Close, on the pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 68 of 171
Step 250 Click Add New, while on the trunk page that was just created Step 251 Select SIP Step 252 Click Next
Step 253 Fill in the following fields as follows a. Name = CWMS_AppSrv01 b. Description = CWMS Application Server 01 c. Device Pool = Default d. Destination Address = 10.1.2.140 (Media Server Instance, in the lab with a 50 user system the media server is the same server as the WebEx Meeting Administration Server) e. Port = 5062 f. SIP Trunk Security Profile = CWMS Application Server g. SIP Profile = Standard SIP Profile h. Click Save i. Click OK, on the reset trunk message j. Click Reset k. Click Reset, on the pop-up window l. Click Close, on the pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 69 of 171
Step 254 Click Add New, while on the trunk page that was just created Step 255 Select SIP Step 256 Click Next
Step 257 Fill in the following fields as follows a. Name = CWMS_AppSrv02 b. Description = CWMS Application Server 02 c. Device Pool = Default d. Destination Address = 10.1.2.141 (Media Server Instance, in the lab with a 50 user system the media server is the same server as the WebEx Meeting Administration Server (CWMS02 in the lab) e. Port = 5062 f. SIP Trunk Security Profile = CWMS Application Server g. SIP Profile = Standard SIP Profile h. Click Save i. Click OK, on the reset trunk message j. Click Reset k. Click Reset, on the pop-up window l. Click Close, on the pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 70 of 171
Adding Call Routing In this section a route plan will be configured on CUCM to interact with CWMS via the SIP trunks created in the previous section. Step 258 Select Call Routing Route/Hunt Route Group Step 259 Click Add New Step 260 Enter the following Information in the route group a. Route Group Name = CWMS_LB_RG b. Distribution Algorithm = Top Down c. Selected Devices = CWMS_LB01 & CWMS_LB02 (highlight each in the available devices and click add to route group) d. Confirm CWMS_LB01 is first in the selected devices list, if not highlight and use the up down arrows to move up and down e. Click Save
Step 261 Select Call Routing Route/Hunt Route List Step 262 Click Add New
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 71 of 171
Step 263 Enter the following Information in the route group a. Route List Name = CWMS_RL b. Description = CWMS Load Balancer Route List c. Cisco Unified Communication Manager Group = Default d. Click Save e. Click Add Route Group f. Route Group = CWMS_LB_RG-[NON-QSIG] g. Click Save h. Click OK, to the Route List reset warning i. Click Reset j. Click Reset, on the pop-up window k. Click Close, on the pop-up window
Step 264 Select Call Routing Route/Hunt Route Pattern Step 265 Click Add New
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 72 of 171
Step 266 Enter the following Information in the route group a. Route Pattern = 2999 b. Gateway/Route List = CWMS_RL c. Click Save d. Click OK, to Authorization Code pop-up window
Step 267 Select Call Routing SIP Route Pattern Step 268 Click Add New Step 269 Enter the following Information in the route group a. IPv4 Pattern = cwms01.siteb.com b. Description = CWMS App Server 01 SIP Redirect c. SIP Trunk/Route List = CWMS_AppSrv01 d. Click Save
Step 270 Click Copy, while still on the SIP route pattern previously created
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 73 of 171
Step 271 Enter the following Information in the route group a. IPv4 Pattern = cwms02.siteb.com b. Description = CWMS App Server 02 SIP Redirect c. SIP Trunk/Route List = CWMS_AppSrv02 d. Click Save
Step 272 Select Call Routing Translation Pattern Step 273 Click Add New Step 274 Enter the following Information in the route group e. Translation Pattern = \+1408555XXXX f. Description = Strip International from WebEx Meeting Server g. CallED Party Transformation Mask = XXXX h. Click Save Ensure you populate the CALLED Party Transform Mask and not the Calling Party Transform mask, as the fields appear similar
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 74 of 171
Setting up Conferencing for Jabber Conferencing capabilities enable users to create and attend meetings from Jabber client. Cisco WebEx Meetings Server provides on-premises meeting and conferencing services for Jabber client. UC Services and Service Profiles have already been configured from previous implementations. The student will add two more conferences in the UC Services and add them to the current student Service Profile. Once this change has been made the jabber Clients on both workstations will need to be restarted Step 275 Select User Management User Settings UC Service
Step 276 Click Find Step 277 Observe the list of preconfigured UC Services
Step 278 Click Add New Step 279 Select Conferencing, form the drop-down menu
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 75 of 171
Step 280 Click Next
Step 281 Enter the following Parameters a. b. c. d. e. f. g. h.
Product Type = WebEx (Conferencing) Name = CWMS01_SRV Description = CWMS Service Host name/IP Address = cwms01.siteb.com Port = 80 (default) Protocol = HTTP (default SSO Identity Provider = UNChecked Click SAVE
Step 282 Click Copy Step 283 Change the name to CWMS02_SRV Step 284 Change the host name/IP address to cwms02.siteb.com Step 285 Click Save
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 76 of 171
Step 286 Select User Management User Settings Service Profile
Step 287 Click Find Step 288 Select Student_SrvPro
Step 289 Scroll down to Conferencing Profile Step 290 Observe that it was previously configured
Step 291 Select CWMS01_SRV, in the primary drop-down box Step 292 Select CWMS02_SRV, in the secondary drop-down box Step 293 Leave the rest of the fields Default
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 77 of 171
Step 294 Click Save
Step 295 Switch to Pxy-WS01, (Alex Ace’s 172.16.x.201 RDP Session) Step 296 Click the Jabber, icon on the task bar at the bottom of the screen to bring it to top focus Step 297 Select File Options Step 298 Select Meetings, form the left navigation menu Step 299 Select Set up account, button the upper left Step 300 Observe it reads ciscoucft.webex.com
Step 301 Click Cancel, to close the meetings host account window Step 302 Click Cancel, on the jabber options window to close the window Step 303 Select File Exit, to close the Jabber client Step 304 Double Click the Jabber shortcut on the desktop to turn Jabber back on Step 305 Select File Options
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 78 of 171
Step 306 Select Meetings, form the left navigation menu Step 307 Select Set up account, button the upper left Step 308 Observe it now reads cwms01.siteb.com (ignore the account verification Warning, CWMS is not configured for users yet)
Step 309 Click Cancel, to close the meetings host account window Step 310 Click Cancel, on the jabber options window to close the window Step 311 Repeat steps 295 to 210, for Pxy-WS02 (Blake Bad 172.16.x.202 RDP Session) The Jabber client conference configuration will be demonstrated and tested in subsequent sections
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 79 of 171
Section 3a: Configuring High Availability Revisited Previously on CWMS the student was configuring HA in section three, and was stopped by the 20 min database synchronization. In this section the student will revisit the end of the HA configuration already in progress from Section 3. Step 312 Switch to SiteB-AD (AD 172.16.x.120 RDP Session) back to the browser pointing to CWMS01 Admin web page, this should be open in the RDP session pointing to the AD server Step 313 Click Done, if the synchronization is finished if not wait till finished and you see the screen below
Ignore the warnings at the top of the browser about one or more virtual machines need your attention, and SSL certificate
Step 314 Observe HA has status of good for both CWMS02 and IRP02
Step 315 Switch to vSphere client Step 316 Highlight CWMS02 Step 317 Right Click CWMS02 Open Console (if open select from task bar) Step 318 Observe the CWMS02 is connected to cwms01.siteb.com
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 80 of 171
Step 319 Close the CWMS02 console
Step 320 Switch back to the vCenter, main window Step 321 Highlight IRP02 Step 322 Right Click IRP02 Open Console (if open select from task bar) Step 323 Observe the WEMS is connected to cwms01.siteb.com Step 324 Close the IRP02 console
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 81 of 171
Section 5: Post Deploy CWMS Configurations Basic Setup of CWMS In this section the student will configure and explore some of the settings available from the CWMS administration web site.
Audio Configuration Step 325 Navigate to meetingadmin.siteb.com, (Skip if already here) from the local browser on the student’s pc, or use the browser in the RDP session on the AD servers. For this part of the lab you can use the same URL for inside or outside For ease of use it is preferred to use the browser on the students PC, as opposed to the browser in the RDP session. Step 326 Click and accept any browser security certificate messages Step 327 Enter
[email protected], in the user name field Step 328 Enter Cisc0123@, in the password field
Notice that the system is in maintenance mode, which means the system is not available for meetings. The system was left in Maintenance mode from the previous section when the student configured HA.
It takes the system about 30 min to reboot when switching off Maintenance mode. After all configuration is done later in this section Maintenance mode will be switch off so it is only done once during the lab.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 82 of 171
Step 329 Navigate to Settings Audio Step 330 Click Continue, to begin configuring CUCM audio integration
Step 331 Click Continue
Step 332 Click Continue, to enter maintenance mode
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 83 of 171
Step 333 Click Add, to add CUCM
Step 334 Enter 10.1.2.110, in the CUCM 1 IP Address field Step 335 Click Continue
Step 336 Click Continue
Step 337 Click Add, to add the Access Number
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 84 of 171
Step 338 Enter CWMS Call In, in the Phone Label field Step 339 Enter 2999, in the Phone Number field Step 340 Click Continue
Step 341 Click Finish
Step 342 Click OK, on the maintenance mode warning
Step 343 Scroll down to the Caller ID section of the audio configuration page Step 344 Enter +14085552999, in the Caller ID field Step 345 Check the Bypass pressing 1, field
Step 346 Scroll down click Save
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 85 of 171
Step 347 Click OK, on the maintenance mode warning
Turning off maintenance mode requires a reboot of all servers in the system. Before we turn off maintenance mode and reboot the server, the students will configure a few more items that also require maintenance mode. Step 348 Select Mobile, from the navigation section on the left side of the page Step 349 Check iOS WebEx applications, to enable mobile devices (checked by default)
Step 350 Select Video, from the navigation section on the left side of the web page Step 351 Observe HQ video is enabled by default
If you are using the local browser on your PC you will need to download the logo to your desktop from dropbox at http://tinyurl.com/CWMSSiteB before preforming the steps below If you are using the browser from within the RDP session on the AD server then follow the standard number steps below Step 352 Select Branding, from the navigation section on the left side of the web page
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 86 of 171
Step 353 Click Browse, next to the company logo field If you are using the local browser select the file that was downloaded from dropbox to your local computer desktop
Step 354 Select Desktop, from the left side under favorites (If on SiteB-AD RDP session) Step 355 Select CWMS, folder (If on SiteB-AD RDP session) Step 356 Select sitebLogo.jpg, from the listed files (If on SiteB-AD RDP session) Step 357 Click Open Step 358 Click Upload
Step 359 Scroll down click Save Step 360 Select Meetings, from the navigation section on the left side of the web page
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 87 of 171
Step 361 Observer 50 is the maximum participants based on the system size, and the record section is grayed out till we assign a NFS server to record the sessions
Step 362 Click System, at the top of the page Step 363 Click View More, under Server Configuration section
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 88 of 171
Step 364 Click Add A Storage Server Now
Step 365 Enter siteb-ad.siteb.com:/NFSShare (case sensitive and don’t forget the colon : ) Step 366 Click Continue
Step 367 Click Done, to finish the addition of the NFS Server configuration
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 89 of 171
Step 368 Observe both the Mail server and NFS server are properly configured and operational
Step 369 Click Settings Meetings, observe record is now selected. Record is grayed out before you add a NFS server settings
Step 370 Click Turn Off maintenance Mode, in the upper right corner of the web WebEx Admin web page
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 90 of 171
Step 371 Click Continue, to the restart warning
Step 372 Switch to SiteB-AD RDP session (172.16.x.120) Step 373 Switch to vCenter Step 374 Click and Highlight CWMS01 Step 375 Right Click CWMS01 Step 376 Select Open Console, observe that the VM is still in Maintenance mode but a status bar is moving across the center of the screen indicating that the shut down and restart of each VM is in progress. If you open the console for all four VMs you will see them all reboot This reboot should take about 10 min (in production this could take considerably longer), this would be a good coffee and Facebook break time. Check back with the console from time to time, once the system is fully restarted you can move on to the next section of the lab
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 91 of 171
Adding Users Manually Step 377 Navigate to meetingadmin.siteb.com, from the local browser on the student’s pc, or use the browser in the RDP session on the AD servers. For this part of the lab you can use the same URL for inside or outside (This might already be open from previous section of the lab) For ease of use it is preferred to use the browser on the students PC, as opposed to the browser in the RDP session. Step 378 Enter
[email protected], in the user name field Step 379 Enter Cisc0123@, in the password field Step 380 Click Login Step 381 Observe that all processes are Good, if not wait for them to all start and become good (green)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 92 of 171
Manually Adding Users Step 382 Click Users from the top menu Step 383 Click Add User
Step 384 Enter the following for the first user a. Account Type = Host b. First Name = Blake c. Last Name = Bad d. Language = English (default) e. Email address =
[email protected] f. Time Zone = San Francisco (Pacific Daylight Time, GMT -07:00) g. Click Save
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 93 of 171
Step 385 Observe the two users on the system at this point Alex Ace is the original administrator from when the system was deployed. Notice Ms. Ace cannot be deleted or edited
Black Bad is a host user on the system
Adding Users Via LDAP WHY - Directory integration enables your system to populate and synchronize your Cisco WebEx Meetings Server user database with the CUCM user database that is typically integrated with an LDAP directory. Directory integration simplifies user profile administration in the following ways: Imports user profiles from CUCM to Cisco WebEx Meetings Server. Periodically updates the Cisco WebEx Meetings Server database with new or modified user attributes in the CUCM database. Periodically checks the CUCM database for inactive user entries and deactivates their user profiles from the Cisco WebEx Meetings Server database. Enables the system to use LDAP authentication to authenticate Cisco WebEx Meetings Server directory Integration users against the external directory. Supports fully encrypted LDAP integration when Secure LDAP (SLDAP) is enabled on CUCM and the LDAP server. You can configure your system as follows: Use LDAP directory service for user management and authentication Use LDAP directory service for directory synchronization but use SSO for authentication Before You Begin Make sure all of the following prerequisites are met before you proceed with directory integration: We recommend that you schedule synchronizations during off-peak hours or on weekends to minimize the impact on your users.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 94 of 171
Make sure you have a supported version of Cisco Unified Communications Manager (CUCM). Refer to the Cisco WebEx Meetings Server System Requirements for more information. Obtain CUCM administrative user credentials (required to add a CUCM server for directory integration). You must configure AXL and LDAP directory service on CUCM before you can use the directory integration feature. CUCM is required to import users into your Cisco WebEx Meetings Server system. Use CUCM to do the following: Enable Cisco AXL WebService Enable Cisco DirSync Configure LDAP integration Configure LDAP authentication Make sure that all users who require hosting privileges are available in CUCM. Any user not in CUCM will not be able to sign in and host meetings (all
Step 386 Click Users Step 387 Click Directory Integration
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 95 of 171
Step 388 Click Add CUCM Server
Step 389 Enter the following CUCM information a. IP Address or FQDN = siteb-cucm911.siteb.com b. User Name = Administrator c. Password = Cisc0123 d. Click Save e. Observer the system will login to CUCM and test the connection, there should be a positive result displayed on the screen
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 96 of 171
Step 390 Click Enable LDAP Authentication
Step 391 Click Continue, to the LDAP Authentication warning
Step 392 Observe the LDAP Authentication
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 97 of 171
Step 393 Click Synchronize Now
Step 394 Observe Synchronize, finishes
Step 395 Click Save Step 396 Click Users, from the top menu Step 397 Observe the users from CUCM have been downloaded to the CWMS
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 98 of 171
Step 398 Switch to Pxy-WS01, (Alex Ace 172.16.x.201 RDP Session) Step 399 Click Outlook, from the task bar at the bottom of the screen Step 400 Click and Highlight the latest email from WEMS Admin (since AD and Exchange are on a share server with minable memory it might take a few seconds for the email to arrive at the inbox) Step 401 Observe that WEMS completed synchronizing the LDAP Directory Step 402 Minimize Outlook
WebEx Meeting Server Testing Step 403 Switch to Pxy-WS01 (Alex Ace 172.16.x.201 RDP session), (The student might already be on this RDP session from previous section) Step 404 Open Cisco Jabber, if not already open Be patient the first time you go off hook with the lab phone it takes about 10 seconds to get dial tone. You might have to make the first phone call twice on both workstations to get the WebEx Audio. The audio will not be perfect since there is no QoS in place to make this audio perfect. Step 405 Enter 2999 & press Enter, in the search or call field of Cisco Jabber
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 99 of 171
Step 406 Listen for the WebEx Auto Attendant Step 407 Observe the Caller ID, (Cisco WebEx) Step 408 Observe that Jabber status has moved from Available to On A Call, and returns to Available once the call is disconnected.
Step 409 Click Red Hand Set, to end the call once you hear WebEx answer the call
Installing PTools on WorkStation01 WHY – Productivity Tools WebEx Productivity Tools include the WebEx Meet Now and WebEx integrations with Microsoft Outlook. Using these, you can schedule, start or join online meetings quickly without having to go to your WebEx service website.
Step 410 Switch to the Pxy-WS01 (Alex Ace 172.16.x.201), the student might already be on the RDP session from previous section Step 411 Click IE, icon on the task bar of PodXY-WS01 (xy = pod#)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 100 of 171
Step 412 Enter https://srecwmsXY.cisco.com (XY = pod#), in the URL address filed and hit enter If the web page does not appear click the browser refresh button Step 413 Click Continue to this website (not recommended) Step 414 Enter
[email protected], Email Address filed Step 415 Enter Cisc0123, in the password field. (remember the password is now coming from the CUCM so we have dropped the @ at the end of the password since we added LDAP to CWMS) Step 416 Click Sign In
Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Step 417 Review the preference sittings, leave them all default Step 418 Click Done
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 101 of 171
Step 419 Click No Thanks, start using WebEx
Step 420 Close Outlook, if it is open Step 421 Click Downloads, in the upper right corner of the web page
Step 422 Click Download, under Productivity tools
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 102 of 171
Step 423 Click Run, at the bottom of the web page (or click Save File if using Firefox – Click Run on the pop-up)
Step 424 Click Next (It will take a little bit of time for this screen to appear)
Step 425 Select I Accept, radio button on the license agreement page Step 426 Click Next
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 103 of 171
Step 427 Click Next, to accept the default destination
Step 428 Click Yes, to allow software installs (This screen takes some time to appear)
Step 429 Click Finish
Step 430 Click Yes, to any certificate warnings (this pop-up will take 15 seconds to pop-up)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 104 of 171
Step 431 Enter srecwmsXY.cisco.com, (xy=pod#) Should be defaulted to your pod Step 432 Click Next Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Step 433 Enter
[email protected], in the email address field Step 434 Enter Cisc0123, in the password field Step 435 Select Remember Me (default) Step 436 Select Automatically sign in (default) Step 437 Click Sign In
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 105 of 171
Step 438 Observe the positive login pop-up at the bottom right side of the screen
Step 439 Click Continue to this website (not recommended), on the browser that opens Step 440 Click OK, after reviewing the web page
Step 441 Close the All browser window on Pxy-WS01
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 106 of 171
End User Password Change and First Login When a user is manually created in CWMS administration web page, an email is sent to that user. The user has to open this mail and click the create password link. This is the only place a password can be created for the user, so that user must be able to get the email. If LDAP authentication is used, there is not a create password email sent, and the user must use their LDAP password to get into WebEx. Step 442 Switch to PodXY-WS02, (xy=pod# Blake Bad 172.16.x.202 RDP Session) Step 443 Click Outlook, on the taskbar at the bottom of the screen Step 444 Observe in the Home menu there are no WebEx buttons, this is because PTtools has not been installed yet Step 445 Click and Highlight the latest email from CWMS, with the subject of Create a Password (due to memory limitations in the lab it might take a few seconds for the mail to be delivered)
Step 446 Click Create Password Step 447 Click Continue to this website (not recommended) Step 448 Enter Cisc0123, in the new password field Step 449 Enter Cisc0123, in the confirm new password field
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 107 of 171
Step 450 Click Submit
Step 451 Enter
[email protected], in the Email Address field if not already filled in for you Step 452 Enter Cisc0123, in the password filed, should fail Step 453 Click Sign In, to login to WebEx user page for Blake Bad
Step 454 Observe account preferences Step 455 Click Done
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 108 of 171
Step 456 Close Outlook Step 457 Click Download Now, to download the productivity tools
Step 458 Click Run
Step 459 Click Next If you don’t see the welcome install screen some times it opens behind other windows. Look for and click the Install Icon install program to top focus.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
in the taskbar to bring the
Page 109 of 171
Step 460 Select I Accept, radio button on the license agreement page Step 461 Click Next
Step 462 Click Next, to accept the default destination
Step 463 Click Yes, to allow software installs (this window takes about 15 seconds to pop-up, wait for it)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 110 of 171
Step 464 Click Finish
Step 465 Click Yes, to accept untrusted certificates Step 466 Enter srecwmsXY.cisco.com, (xy=pod#) Should be defaulted to your pod Step 467 Click Next
Step 468 Enter
[email protected], in the email address field Step 469 Enter Cisc0123, in the password field
Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Step 470 Select Remember Me (default) Step 471 Select Automatically sign in (default) Step 472 Click Sign In
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 111 of 171
Step 473 Click Continue to this website (not recommended), on the browser window that pop-up Step 474 Observe the web page that opens automatically once logged in Step 475 Click OK to close the browser
In Subsequent sections the student will explore some of the options made available to the user by installing the PTool on each workstation
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 112 of 171
Section 6: End User Usage of CWMS Starting a Meeting Using WebEx Assistant In this section the students will start meetings using the WebEx Assistant in the application tray. Step 476 Switch to Pxy-WS02 (Black Bad 172.16.x.202 RDP session), if not already using this workstation from previous section Step 477 Click the Up Arrow to open the system tray
Step 478 Right click WebEx Assistant Step 479 Click Meeting Now
Step 480 Click Set Meeting Preferences, for the first time in. A browser window will open
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 113 of 171
Step 481 Click Continue to web site (not recommended) Step 482 Scroll Down & click Update, to take the defaults
ZZZ Change picture should be Black Bad Meeting Step 483 Click the Up Arrow to open the system tray to try meeting now again
Step 484 Right click WebEx Assistant Step 485 Click Meeting Now
Step 486 Observe the PC communicating with the CWMS
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 114 of 171
Step 487 Click Yes or Accept any and all security certificate warnings
Step 488 Observe that Black Bad is now in a Web Ex meeting Step 489 Observe the Meeting Reminder that pops-up if Outlook happens to be open Step 490 Click X, in the upper right side to close the meeting reminder if one opens
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 115 of 171
Step 491 Enter 408-555-2002, to allow WebEx meeting server to call Blake back Step 492 Click Call Me
Step 493 Click Answer, on the Jabber call pop-up
Step 494 Observe Cisco Jabber session windows pop-up Step 495 Observe WebEx Audio connecting the call to the WebEx session
Step 496 Switch to the WebEx Meeting
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 116 of 171
Step 497 Observe that Blake Bad is the host, and has a call connected to the meeting
If CWMS cannot out-dial the pods softphone, try using the internal number of 2002. If the internal 2002 number works there is an issue with the translation pattern created early in the lab. If neither number works try resetting your SIP trunk to the WEMS server, and try both calls again
Step 498 Click the Invite and remind others to join icon on the WebEx desktop, or click Participants Invite and Remind…
or
Step 499 Enter
[email protected], in the invitees filed Step 500 Click Send
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 117 of 171
Step 501 Click Done, on the email conformation
Step 502 Switch to PodXY-WS01 (Alex Ace 172.16.x.201 RDP session) Step 503 Open Outlook Step 504 Observe the Jabber Meeting Reminder, in the lower right corner (if Jabber is on). The student could click Join on the Jabber reminder but the student is going to join from outlook in this section of the lab Step 505 Click the X to close the Jabber meeting reminder
Step 506 Open Outlook, with the icon on the task bar if not all ready open Step 507 Highlight and open the email from Blake Bad via Cisco WebEx Step 508 Click Accept, Send the Response Now, in the upper section of the reading pane
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 118 of 171
Step 509 Dismiss the Reminder pop-up from Outlook and Jabber Step 510 Click the Calendar icon in the lower left corner of Outlook
Step 511 Double Click and open the meeting that was just accepted (you might have to scroll up or down to find it depending on what time of day it is) Step 512 Click Join The Meeting
Step 513 Click Continue to this website (not recommended) Step 514 Enter Alex Ace, in the Name field Step 515 Enter
[email protected], in the email address field Step 516 Click Join
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 119 of 171
Step 517 Enter Cisc0123, in the password field that pop-ups Step 518 Click Sign In
Step 519 Click Install, if the browser is missing any software (Skip this step if you don’t get this screen)
Step 520 Click Yes, to allow the computer to install the software (you might have to click the flashing shield icon in the task bar to bring this to the foreground)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 120 of 171
Step 521 Click Yes, to any browser security Alerts
Step 522 Observe while the workstation is logged into the WebEx meeting
Step 523 Observe both Blake Bad and Alex Ace are now in the meeting Step 524 Enter 4085552001, in the audio conference call me filed Step 525 Click Call Me
Step 526 Click Answer, on the Jabber call pop-up
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 121 of 171
Step 527 Observe Cisco Jabber session windows pop-up Step 528 Observe WebEx Audio connecting the call to the WebEx session
Step 529 Switch to the WebEx Meeting Step 530 Observe that both Blake and Alex have audio connected to the meeting
Step 531 Click on the Jabber Icon, to bring Jabber to focus on Pxy-WS01 Step 532 Observe that Alex Ace is In A meeting
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 122 of 171
Step 533 Enter https://meetingadmin.siteb.com, on the students local browser if not already open In this section the lab is asking the student to use the local browser on the students desktop that is VPNed into the collab01 lab via Anyconnect. Using the students local browser is easier to use then the ones in the RDP session. The student can continue to use the browsers in the RDP session if wanted. Step 534 Enter
[email protected], in the Email Address field Step 535 Enter Cisc0123@, in the password field Step 536 Click Sign In
Step 537 Observe the one meeting from the perspective of the System Monitor (click Dashboard tab if you are not on this page)
Due to the nature of virtual labs you will not hear audio during this call, but you can see that audio is connected by looking in Jabber or in WebEX
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 123 of 171
Testing WebEx Meeting Server Features In this section the student will explore the many of the different features WebEx offers.
Meeting Video In this section the student will explore video within a meeting. The meeting created from the previous section should still be functioning. Due to the remote nature of this lab, the student is not able to introduce a video camera from the remote PC which is a virtual machines (VMs). In this lab we will simulate a camera on the remote PCs by running an application on the remote PCs called Maycam. Step 538 Click the Video button in Pxy-WS01 (Alex Ace 172.16.x.201 RDP Session)
Step 539 Observe Blake does not have video playing yet, and Alex has video streaming and is shown in the small window in the lower left (Max Headroom)
Step 540 Switch to Pxy-WS02 (172.16.x.202) RDP session
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 124 of 171
Step 541 Click the Video Button
Step 542 Observe that video for Blake is now streaming (crept keeper)
Step 543 Switch to Pxy-WS01 (Alex Ace 172.16.1.201 RDP session)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 125 of 171
Step 544 Observe that Alex can see both Blake’s and her own video
As stated before we are using an application called ManyCam to simulate video cameras being installed and active on the virtual workstations in this lab. If for some reason there is no video present when the camera icon is clicked or if the camera Icon is not there at all do the following to get ManyCam. a. b. c. d.
Click the ManyCam icon on the desktop of WorkStation01 or WorkStation02 Click the Source tab Click Image Gallery Click the image in the lower middle section of the screen. At this point you should see Max Headroom (workstation01), or the crept keeper (workstation02) in action in the preview window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 126 of 171
e. Minimize ManyCam f. Click the settings button in WebEx
g. Make sure Capture Device is set to ManyCam Virtual WebCam h. Click OK
i.
This should allow virtual video to stream between the two virtual workstations
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 127 of 171
Meeting Recording & Desktop Sharing In this section the student will explore the ability to record meetings, and use desktop sharing. Step 545 Click Record, from WebEx meeting on PodXY-WS02 the host
Step 546 Observe the record app in the lower right of the WebEx Meeting
Step 547 Click Share My Desktop icon on the desktop, or click Share My Desktop from the drop down menus, on Pxy-WS02 (172.16.x.202) RDP session
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 128 of 171
OR
Step 548 Double click the TestJabber.doc on the desktop of PodXY-WS02, to open the file in word Step 549 Switch to PodXY-WS01 RDP session Step 550 Observe that PodXY-WS01 is seeing the desktop share (you should see the word doc being shared) You might have to navigate to the WebEx meeting by clicking the WebEx icon on the task bar to bring WebEx meeting to the top
Drop-Down Sharing Menu In this section the student will explore usage of the drop-down sharing menu. Step 551 Move the mouse to the top of the screen to open (slides down from the top) the WebEx control panel
Step 552 Click Participants, to open the participants list Step 553 Click Chat, from the WebEx drop down tool bar
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 129 of 171
Step 554 Observe that both participants and Chat are now open while viewing the desktop share from the host
Step 555 Type a message in the Chat window and click Send
Step 556 Switch to PodXY-WS02, (Blake Bad 172.16.x.202 RDP session) Step 557 Drop Down the WebEx Tool bar and observe Chat is flashing
Step 558 Click Chat, to open the chat window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 130 of 171
Step 559 Click Participants, to open the participants windows Step 560 Observe the message from Black Bad
Step 561 Click Recorder, from the drop down WebEx tool bar
Step 562 Pause the recording by clicking the pause button
Step 563 Click Pause, again to resume the recording Step 564 Click the Stop, button on the recording controls
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 131 of 171
Step 565 Click Stop Recording, on the pop-up warning message (after the meeting a email will show up in the host inbox reminding them of the recording with a link to get to the recording. The recordings can also be found by login in to the WebEx user web page)
Step 566 Click X, on the Recording, and Chat windows to close them Step 567 From the dropdown WebEx tool bar click Annotate
Step 568 Observe the Annotation Tool bar
Step 569 Click and Hold the Left mouse button and drag your mouse across the shared document to add some drawings on the page Step 570 Click the T on the annotation tools to start the text tool Step 571 Click on the word doc and type
Step 572 Continue playing with the annotation tools Step 573 Switch to PodXY-WS01, (Alex Ace 172.16.x.201 RDP session) Step 574 Observe that the participants can see the hosts annotation Step 575 Switch to PodXY-WS02, (Blake Bad 172.16.x.202 RDP session) Step 576 Close the Annotation Tools, observe that the annotation goes away when you close the tool
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 132 of 171
Step 577 Click Assign Pass Keyboard and Mouse Control Blake Bad
Step 578 Switch to PodXY-WS01, (Alex Ace 172.16.x.201 RDP session) Step 579 Click Take Control, pop-up window
Step 580 Observe the green tool bar says You are controlling Black Bad’s desktop
Step 581 Switch to PodXY-WS02, (Blake Bad 172.16.x.202 RDP session) Step 582 Observe the green tool bar says Alex Ace is controlling your computer
Step 583 Click on PodXY-WS02 (Blake Bads) desktop, to take control back Step 584 Observe the green bar changes to You are sharing your desktop
Step 585 Click Stop Sharing, on the dropdown WebEx tool bar
Administrator System Monitor In this section the student will look at system monitor wile a meeting is active. Step 586 Navigate to meetingadmin.siteb.com, from the students local computer’s browswer Step 587 Click and accept any browser security certificate warnings Step 588 Enter
[email protected], in the Email Address Field
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 133 of 171
Step 589 Enter Cisc0123@, in the password field Step 590 Click Sign In Step 591 Click Close, on the pop-up welcome screen (if it appears) Step 592 Observe the system monitor details, notice that one meeting is in progress
Step 593 Return to the WebEx meeting on PodXY-WS02 (Blake Bad172.16.x.202 RDP session) Step 594 Click End Meeting, in the lower center of the web ex meeting window
Step 595 Click End Meeting, on the pop-up warning window
Step 596 Switch to PodXY-WS01 (Alex Ace 172.16.x.201 RDP session)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 134 of 171
Step 597 Click OK, on the end of meeting pop-up window
Step 598 Return to Internet Explorer (IE) on the students local computer browser, and observe the System Monitor, notice there are no meeting in progress (Wait for the auto refresh to clear the meeting)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 135 of 171
Scheduling Meetings via WebEx Web Page In this section the student will schedule a meeting using the WebEx user web page. Step 599 Switch to Pxy-WS01, (Alex Ace 172.16.X.201 RDP session) Step 600 Enter https://srecwmsXY.cisco.com (xy=pod#), in Alex Ace’s browser Step 601 Click and accept any browser security certificate warnings Step 602 Observe the SiteB.com logo in the upper right corner of the web page. The student added this when configuring Branding in the WebEx Admin configuration Step 603 Enter
[email protected], in the email address field Step 604 Enter Cisc0123, in the password field Step 605 Click Sign In
Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Step 606 Click X, to close the welcome at the top of the page (if presented) Step 607 Observe there are no upcoming meetings
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 136 of 171
Step 608 Click Schedule on the button bar
Step 609 Enter Yearly Funding Meeting, in the what field Step 610 Enter
[email protected], in the who filed, as you type the system should find Blake Bad’s info and pull it up and let you click below. Click the info the system pulls up
Step 611 Enter
[email protected], and click on the info the system pulls up Step 612 Enter
[email protected], and click on the info the system pulls up
Step 613 Click Alternate Host for Blake Bad Step 614 Enter 12345, in the meeting password field (please use harder passwords in production, we use simple passwords for ease of use in the lab)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 137 of 171
Step 615 Click Schedule It
Step 616 Open Outlook, if not open Step 617 Observe that both Outlook and Jabber both have meeting reminders for the Yearly Funding Meeting Step 618 Click Dismiss on the Outlook reminder Step 619 Click X, to dismiss the Jabber meeting reminder
Step 620 Click Outlook, to bring it to top focus Step 621 Click the Calendar, icon in the lower left corner to open the calendar
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 138 of 171
Step 622 Scroll up and down on today’s date to find the Yearly Funding Meeting Step 623 Observe that from the web page a meeting was scheduled and put into everyone who was invited calendars. (do not enter or accept this meeting, the student will enter this meeting via the web page)
Step 624 Switch back to the web page where the meeting was scheduled Step 625 Observe the page is ready and waiting to start the meeting since the meeting was scheduled for now when setup Step 626 Click Start
Step 627 Click Install, to install any needed browser software, (Iif asked)
Step 628 Click Yes, to any security alerts Step 629 Enter (408)555-2001 (if not already populated in the phone field)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 139 of 171
Step 630 Click Call Me
Step 631 Click Answer, on the Jabber incoming call pop-up
Step 632 Switch to Pxy-WS02, (Blake Bad 172.16.X.202 RDP Session) Step 633 Open Outlook if not already open Step 634 Click Dismiss, on the Outlook Reminder
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 140 of 171
Step 635 Click X, on the Jabber meeting reminder
Step 636 Open IE on Blake Bad’s workstation (Pxy-WS02) Step 637 Enter srecwmsXY.cisco.com, in the address field Step 638 Click Continue to this website (not recommended) Step 639 Click NO Thanks, to installing PTtools Step 640 Enter
[email protected], if asked to login Step 641 Enter Cisc0123, if asked to login Step 642 Observe there is one meeting schedule one into the WebEx user web site
Step 643 Click Join, to enter the Yearly Funding Meeting Step 644 Click Yes, to any and all security alerts
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 141 of 171
Step 645 Enter 408-555-2002, in the phone field if not populate Step 646 Click Call Me
Step 647 Click Answer, on the Jabber incoming call pop-up
Step 648 Switch to Pxy-WS01, (Alex Ace 172.16.x.201 RDP Session) Step 649 Click End Meeting
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 142 of 171
Scheduling Meetings from Microsoft Outlook In this section the student will schedule and access meetings via Microsoft Outlook. Step 650 Switch to P01-WS01 (172.16.x.201) RDP session Step 651 Open Outlook Step 652 Click Schedule Meeting, in the upper tool bar (if the two WebEx buttons are not present on the Home menu bar, close Outlook and re-open outlook)
Step 653 Click TO, button to add recipients Step 654 Select Blake Bad, from the attendee pop-up window Step 655 Click OK, to accept Blake as an attendee
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 143 of 171
Step 656 Enter Sales Meeting, in the subject filed Step 657 Enter WebEx, in the location filed Step 658 Click Add WebEx Meeting, from the top tool bar
Step 659 Enter 12345, in the meeting password field Step 660 Select Alternate Host, tab Step 661 Select Blake Bad, as the alternate host Step 662 Click OK, to accept information
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 144 of 171
Step 663 Click Send Step 664 Click Dismiss, on the sales meeting reminder (If appears) Step 665 Select Calendar, icon in the bottom left of Outlook
Step 666 Double click Sales Meeting, you might have to scroll up and down to find it
Step 667 Click Meeting Hyperlink or JOIN in the jabber pop-up, from the body of the calendar event. Take note of the meeting password 12345
Or
Both the outlook hyperlink and the Jabber Join button take you to the same place in the next step. Step 668 Click Continue to this website (not recommended)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 145 of 171
Step 669 Click Start
Step 670 Click Yes, on any security alerts Step 671 Click Call Me, in the audio conference pop-up window
Step 672 Click Answer on the Jabber pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 146 of 171
Step 673 Observe Cisco Jabber window will pop-up and you will hear WebEx announcing you are being connected to WebEx meeting
Step 674 Switch to the WebEx Meeting Window, by clicking the WebEx Meeting Icon on the task bar at the bottom of the screen
Step 675 Click the Web Cam icon to send video to other participants
Step 676 Switch to WorkStation02 RDP Session Step 677 Open Outlook Step 678 Click Dismiss All in the meeting reminder pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 147 of 171
Step 679 Click Yes to confirm dismiss all Step 680 Click Join, on the Jabber Meeting Reminder for the Sales Meeting
Step 681 Click Continue to this website (not recommended) Step 682 Enter Blake Bad in the name field Step 683 Enter
[email protected] in the email address field Step 684 Click Join
Step 685 Enter Cisc0123, in the password field when asked to sign in to Web Ex
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 148 of 171
Step 686 Click Install or Run, if asked to install the Cisco WebEx add-on
Step 687 Click the flashing Shield icon in the task bar to bring the install message to focus Step 688 Click Yes, to allow the install to change the computer
Step 689 Click Yes to any browser security alerts Step 690 Click Call Me on the Audio Conference pop-up window
Step 691 Click Answer on the Jabber pop-up window
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 149 of 171
Step 692 Switch to the WebEx Meeting Window, by clicking the WebEx Meeting Icon on the task bar at the bottom of the screen
Step 693 Observe that Alex Ace is sending video Step 694 Click the Camera icon to send video to other participants
Step 695 Switch to Pxy-WS01 (172.16.x.201) RDP Session Step 696 Observe that Black Bad is sending video
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 150 of 171
Joining Meetings from external devices by meeting number (Optional) In this section the student will join a meeting via a mobile device using the meeting number. Step 697 Install WebEx Meetings from the app store or market place to your mobile device Step 698 Open Web Ex 3.5.1 or newer on your mobile device
Step 699 Click the Sign In button
Step 700 Click Sign in through your corporate website
Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Step 701 Enter srecwmsXY.cisco.com (xy = pod#)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 151 of 171
Step 702 Click Next
Step 703 Click OK, on the sign in warning Step 704 Enter
[email protected] Step 705 Enter Cisc0123 in the password filed Step 706 Click Sign In
Step 707 Switch to Pxy-WS01, (172.16.x.201) RDP Session Step 708 Find the meeting number at the bottom of the WebEx meeting screen, or click the Meeting Info tab at the top of the meeting
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 152 of 171
Step 709 Click Join by Number, on the mobile device
Step 710 Enter the Meeting Number/Access Code for the meeting open in your lab Step 711 Click Join Meeting
DO NOT use the meeting number in the lab guide picture, use the number for the meeting shown on the students virtual workstation Step 712 Enter 12345, for the meeting password Step 713 Click OK
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 153 of 171
Step 714 Click Connect Using Internet, Audio conference
Step 715 Observe that the mobile device has been Muted, automatically
Step 716 Click the People icon button on the bottom of the mobile device to see the participants list
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 154 of 171
Step 717 Click the Video Camera, to see the meeting video. You should see one of the virtual workstation video’s on the top and a camera icon on the bottom
Step 718 Click the Video Camera icon on the bottom half of the screen, the student should see themselves in the video in the bottom
Step 719 Switch to Pxy-WS01, (172.16.x.201) RDP Session Step 720 Observe that Cindy Cool is in the participant list. She is Mobile, using Internet Audio, and is muted.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 155 of 171
Step 721 Click the Mute button on the mobile device to turn the audio on for the mobile device. After a few seconds you should see your picture pop to the top of the mobile device screen, and be visible on the virtual workstations also Step 722 Switch to Pxy-WS01 (172.16.x.201) RDP Session Step 723 Observe mobile video on Virtual workstation
Adding 2nd Mobile Device to WebEx Meeting (Optional) In this section the student will add a second mobile device to the meeting that is currently active. Step 724 From 2nd Mobile device start WebEx app
Step 725 Click App Store, to update WebEx App if needed
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 156 of 171
Step 726 Click Update
Observe the install process
Step 727 Click Open
Step 728 Click Sign In
Step 729 Enter srecwmsXY.cisco.com, (xy=pod#)
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Pod # Pod 01 Pod 02 Pod 03 Pod 04 Pod 05 Pod 06 Pod 07 Pod 08 Pod 09 Pod 10 Pod 11 Pod 12 Pod 13 Pod 14 Pod 15 Pod 16 Pod 17 Pod 18 Pod 19 Pod 20
WebEx Site URL srecwms01.cisco.com srecwms02.cisco.com srecwms03.cisco.com srecwms04.cisco.com srecwms05.cisco.com srecwms06.cisco.com srecwms07.cisco.com srecwms08.cisco.com srecwms09.cisco.com srecwms10.cisco.com srecwms11.cisco.com srecwms12.cisco.com srecwms13.cisco.com srecwms14.cisco.com srecwms15.cisco.com srecwms16.cisco.com srecwms17.cisco.com srecwms18.cisco.com srecwms19.cisco.com srecwms20.cisco.com
Page 157 of 171
Step 730 Enter
[email protected], in the Email field Step 731 Enter Cisc0123, in the password field Step 732 Click Sign In
Step 733 Click Join by Number, in the lower right corner Step 734 Enter the Meeting Number for the current meeting Step 735 Click Join Meeting
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 158 of 171
Step 736 Enter 12345, for the meeting password Step 737 Click OK
Step 738 Click Connect Using Internet, audio Conference
Step 739 Observe the message that you have joined the audio conference
Step 740 Observe the users has automatically been put on mute
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 159 of 171
Step 741 Click the People Icon, to see the current participants
Step 742 Click the Information button to see the current meeting information
Step 743 Click the Video Camera icon to send video from the mobile device Step 744 Click Start My Video, when ready to send video to the conference
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 160 of 171
Step 745 Observe the four participants are sharing video from the perspective of the iPad device
Step 746 Switch to Pxy-WS01, (172.16.x.201) RDP session Step 747 Click Share My Desktop
Step 748 Open a document or something to share on the desktop of Pxy-WS01 Step 749 Switch back to the 2nd mobile device, in this case a iPad
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 161 of 171
Step 750 Observe the shared desktop
Step 751 Click the Door and Arrow, icon in the upper right corner to leave the meeting on the 2nd device Step 752 Click Leave
Step 753 Click Settings Step 754 Click Acocunt
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 162 of 171
Step 755 Click Sign Out
Step 756 Click Sign Out, conformation
Step 757 Observe WebEx App returns to the first screen
Mobile Device Joining by Number (Optional) In this section the student will join a meeting with a mobile device via number Step 758 Click Join By Meeting Number
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 163 of 171
Step 759 Enter current Meeting Number Step 760 Enter Name Step 761 Click Join Meeting
Step 762 Enter 12345, in the meeting password field Step 763 Click OK
Step 764 Click Connect Using Internet, audio conference
Step 765 Observe the Joined to audio conference Message
Step 766 Observe the Auto Mute message
Step 767 Click the People Icon to observe the current participants
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 164 of 171
Step 768 Click the Camera icon to preview your mobile device video Step 769 Click Start My Video when ready to transmit video to the conference
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 165 of 171
Step 770 Observe three users in the meeting
Step 771 Click the Door with Arrow, to leave the meeting from the mobile device Step 772 Confirm Leaving the meeting There should still be a meeting between Alex Ace and Blake Bad, leave this meeting up to be used in the next section.
Connecting External Users with VPN Connection (optional) In some instances remote access will not be allowed due to the companies security policy, and the users will be forced to use a VPN to access WebEx Meeting Server. In this section the students will access the network via VPN and join meetings. Step 773 Open AnyConnect, on your mobile device. If your device does not have AnyConnect download and install it from the App store or Marketplace
Step 774 Select Add VPN Connections… Step 775 Enter CWMS Lab, in the description field Step 776 Enter sre-collab01.cisco.com/student
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 166 of 171
Step 777 Select Save
Step 778 Slide AnyConnect VPN to ON Step 779 Select Continue
Step 780 Enter cwms for the username Step 781 Enter the password giving by the proctor at the start of lab Step 782 Select Connect
Step 783 Select Accept, on the banner
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 167 of 171
Step 784 Observe that VPN connection has been created
Step 785 Open WebEx app
Step 786 Click Sign In
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 168 of 171
Step 787 Click Sign in through your corporate website
Step 788 Enter srecwmsXY.cisco.com, (xy=pod#) Step 789 Enter
[email protected], in the email address field Step 790 Enter Cisc0123, in the password field Step 791 Click Sign In
Step 792 Click Join, on the meeting that was started in the previous section
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 169 of 171
Step 793 Click Connect Using Internet, audio connection
Step 794 Observe the mobile device has entered the meeting using a VPN and the WebEx Meeting app
Step 795 End the meeting from the host when done exploring This is the end of the official lab; please feel free to continue to play with the current meeting, or any other part of the lab you wish to learn more about. Please END MEETING from the host of the meeting on all currently active meetings so no meetings are active when you are finished playing in the lab environment
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 170 of 171
End Of Lab This concludes the lab. On behalf of the Americas Partners Organization – Solutions Readiness Engineers we thank you for taking the time to complete this lab. We hope that this lab surpassed your goals and expectation and was a very useful and positive learning experience for increasing your knowledge of Cisco’s Collaboration products. Please don’t forget to complete your survey for today’s session. The Solutions Readiness Engineers have a YouTube channel that has step-by-step videos for each of our lab offerings. You can find our YouTube Channel here: http://youtube.com/CiscoFieldTrainers Thank you for taking our lab and as always thank you for using Cisco products.
Lab Guide Version 2.6
Presented by CAPO – Solutions Readiness Engineers
Page 171 of 171
