Table of Contents. Welcome To the SRE Lab We hope you enjoy your stay!

Transcription

1 Meeting Server Lab

2 Table of Contents What is WebEx Meeting Server... 3 Lab Overview... 7 Task 1: Accessing The Lab Equipment Task 2: Connecting to Lab Workstations & Servers Section 1: Pre Deployment Configurations Section 2: Deploying CWMS 1.5 Virtual Machines Section 3: Configuring High Availability Section 4: Configure CUCM for CWMS Integration Section 5: Post Deploy CWMS Configurations Section 6: End User Usage of CWMS Joining Meetings from external devices by meeting number (Optional) Adding 2 nd Mobile Device to WebEx Meeting (Optional) Mobile Device Joining by Number (Optional) Connecting External Users with VPN Connection (optional) End Of Lab Welcome To the SRE Lab We hope you enjoy your stay! Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 2 of 173

3 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 3 of 173

4 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 4 of 173

5 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 5 of 173

6 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 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 approved cryptographic algorithms supported Localization Cisco WebEx Meetings Server is localized into 13 languages to support customers worldwide. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 6 of 173

7 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 7 of 173

8 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 Server Providing local device registration and call control Cisco Unified CM IM & Presence Server 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 8 of 173

9 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. This topology represents one CWMS pod, one student per pod Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 9 of 173

10 Lab Addressing Tables Internal and External Addresses Domain SiteB.com X instructor assigned pod number Subnet Masks /24 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 IP Address IP Address Domain\User Password Name External Internal SiteB-CUCM X Administrator Cisc0123 SiteB-IMP X Administrator Cisc0123 SiteB-CUC X Administrator Cisc0123 SiteB-AD X Administrator Cisc0123 SiteB-WS X SiteB\aace Cisc0123 StieB-WS X SiteB\bbad Cisc0123 CWMS X aace@siteb.com Cisc0123 CWMS X aace@siteb.com Cisc0123 IRP X (DMZ) aace@siteb.com Cisc0123 IRP X (DMZ) aace@siteb.com Cisc0123 vcenter X root Cisc0123 CWMSDeploy N/A N/A N/A IRPDeploy N/A N/A N/a 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 Version Cisco Unified Communication Manager Cisco Unified CM IM & Presence Cisco Unity Connection Student Remote Work Stations Windows 7 MS Active Directory Server Windows 2008 R2 64 Jabber PC Version Build vcenter 5.1 ESXi 5.1 CWMS A(2) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 10 of 173

11 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 CWMS devices Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 11 of 173

12 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. This section is for students that DO NOT have Cisco AnyConnect installed on their computer. Cisco AnyConnect Pre-Installed 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. Install and Connect with Cisco AnyConnect SSL VPN Client Step 1 Open a web browser and connect to 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 12 of 173

13 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 13 of 173

14 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 Step 11 Click Start All Programs Accessories Remote Desktop Connection, from the Student s personal computer Click Options Step 12 Step 13 Select Local Resource Tab Click Settings, under remote audio Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 14 of 173

15 Step 14 Step 15 Select Play on this computer & Do Not Record Click OK Step 16 Select the General tab Step 1 st RDP Session 2 nd RDP Session 3 rd RDP Session Step x x x.120 Step 18 siteb\aace siteb\bbad siteb\administrator Pod # WorkStation WorkStation Win2K8R2 AD Users siteb\aace siteb\bbad siteb\administrator Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 15 of 173

16 Step 19 Click Connect Step 20 Step 21 Enter Cisc0123, in the password field Click OK Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 16 of 173

17 Step 22 Your Remote Desktop should look something like this. Step 23 Repeat steps two more times to open the following two RDP sessions SiteB-WS02 - SiteB\BBad (on X.202) SiteB-Ad - SiteB\Administrator (on X.120) Step 24 Click Sign In, if either of your Jabber clients does not login. (both workstations Jabber client should be logged in and showing the contact list as shown above) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 17 of 173

18 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 18 of 173

19 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 ( 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 19 of 173

20 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 20 of 173

21 Step 26 Step 27 Step 28 Step 29 From the SiteB-AD ( X.120) RDP session opened earlier Click Start Administrative Tools DNS to open the DNS Manager tool Click the + (plus sign s) next to SiteB-AD Forward Lookup Zone SiteB.com 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 Step 32 Step 33 Step 34 Enter cwms01, in the name field Enter , in the IP Address field Check Create Associated Pointer (PTR) record Click Add Host Step 35 Click OK, on the DNS record created successfully pop-up message Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 21 of 173

22 Step 36 Repeat Steps nine more times to add the following DNS A record entries in the chart below Be careful and notice that the 3 rd 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 cwms IRP meetingadmin IRP vcenter meeting esxi irpdeploy cwmsdeploy Step 37 Step 38 Click Done, to close the new host pop-up window Review the DNS entries make sure they look like the following Step 39 Step 40 Step 41 Step 42 Close DNS Manager Click Start Enter CMD, in the search field Press Enter, to open the command prompt Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 22 of 173

23 Step 43 Enter nslookup, in the command prompt window Step 44 Step 45 Step 46 Enter cwms01.siteb.com Press Enter, to activate the above command 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 Step 49 Step 50 Enter exit, to close nslookup Enter ping cwms01.siteb.com 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 23 of 173

24 Configuration of Microsoft Exchange Access Policies By default Microsoft Exchange 2010 does not allow 3 rd party devices to send 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 to the users. In the case of the lab the WebEx server sends the user password reset to the lab Exchange server which in turns delivers it to the appropriate user. Step 52 Step 53 Step 54 Step 55 From the SiteB-AD ( X.120) RDP session opened earlier Click Start All Programs Microsoft Exchange Server 2010 Exchange management Console Click the + sign next to Microsoft Exchange On-Premises Click and Highlight Microsoft Exchange On-Premises (wait for status bar to complete) Step 56 Step 57 Step 58 Step 59 Click the + sign next to Server Configuration Click and highlight Hub Transport Click and highlight Default SITEB-AD receive connector in the center section of the Exchange Management Console Click Properties, under actions in the right side of the Exchange Management Console Step 60 Step 61 Step 62 Click Permission Groups tab on the Default SITEB-AD properties pop-up window Click and select Anonymous Users Click Apply Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 24 of 173

25 Step 63 Click OK Step 64 Close Exchange Management Console Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 25 of 173

26 Section 2: Deploying CWMS 1.5 Virtual Machines In this section the students will deploy two CWMS Virtual Machines, one CWMS admin server and one CWMS IRP. This will give the student the experience of deploying CWMS VMS on to an ESXi server via vsphere client connected to vcenter. In the interest of saving time during the lab, the student will not wait for the deployment to finish. The lab has been constructed to give the student a complete deployment experience but reduce the time required to complete the lab. 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 ( 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 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 26 of 173

27 virtual machine, and an optional Internet Reverse Proxy (for public access) 800 concurrent users system 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 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 27 of 173

28 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 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 28 of 173

29 Deploying Cisco WebEx Meeting Server (CWMS) & Internet Reverse Proxy (IRP) In this section the student will deploy two virtual machines called CWMSDeploy and IRPDeploy. These two VMs will not be allowed to finish deploying to help save hard disk space and lab 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 Step 67 Step 68 Step 69 Step 70 Enter vcenter.siteb.com, in the IP address/name field Enter root, in the user name field Enter Cisc0123 (C i s c Zero 1 2 3), in the password field Click Login Click Ignore, to dismiss the Security Warning Step 71 Select Hosts and Clusters, in the inventory section of the screen Step 72 Step 73 Step 74 Click the + sign next to vcenter01 Click the + sign next to CWMS Click the + sign next to , the pods ESXi host Step 75 Click and highlight the host Notice that CWMS01, CWMS02, IRP01, and IRP02 virtual machines have already been created to reduce lab time. Next two VMs called CWMSDeploy and IRPDeploy will be deployed but not used in the lab, so the student gets the CWMS Deploy Experience. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 29 of 173

30 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 CWMSDeploy to deploy the CWMSDeploy admin Virtual Machine (VM), when you finish the column come back to the top of the table and work down the right column labeled IRPDeploy to deploy the IRPDeploy VM. CWMSDeploy Column Take This Path For 1 st VM Deployment IRPDeploy Column Take This Path For 2 nd VM Deployment Steps CWMSDeploy IRPDeploy Step 77 Click Browse Skip Step, ova file is already selected Step 78 Browse to Desktop CWMS Skip, ova file is already selected Step 79 Select cisco-webex-meeting-server- 1.5.x.x.x(x).ova (x = version number) Skip, ova file is already selected The Cisco WebEx Meeting Server OVA software has already been downloaded to the lab, but can be downloaded from CCO at Step 80 Click open Skip, ova file is already selected Step 81 Click Next Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 30 of 173

31 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 Click Accept, to accept the EULA Click Accept, to accept the EULA Step 84 Click Next Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 31 of 173

32 Step 85 Enter CWMSDeploy, in the name field Enter IRPDeploy, in the name field Step 86 Click Next Click Next Step 87 Select 50 User Admin (default) Select 50 User Reverse Proxy Step 88 Click Next Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 32 of 173

33 Step 89 Select Thin Provision, for the Virtual Disk Format Select Thin Provision, for the Virtual Disk 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 Step 90 Click Next Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 33 of 173

34 Pod # CWMS01 VLAN IRP01 VLAN Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod VLAN Chart for each pod Step 91 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 Step 92 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 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 Ignore the Multiple source network network warning warning Step 93 Click Next Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 34 of 173

35 Step 94 Enter the follow properties a. Hostname = CWMSDeploy b. Domain Name = siteb.com c. IPv4 Address = d. IPv4 Subnet Mask = e. IPv4 Gateway = f. Primary DNS = Enter the follow properties a) Hostname = IRPDeploy b) Domain Name = siteb.com c) IPv4 Address = d) IPv4 Subnet Mask = e) IPv4 Gateway = f) Primary DNS = Step 95 Click Next Click Next Step 96 Click Finish Click Finish Step 97 Repeat step for IRPDeploy (Right Column) Deploy IRPDeploy while CWMSDeploy is deploying, to speed up the lab Continue on to next section below, while the two VMs continue to deploy Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 35 of 173

36 Due to lab based issues the two VMs that are in the process of deploying will be canceled and not allowed to finish. The deployment just performed in step are the same steps used to create CWMS01, CWMS02, IRP01, IRP02 that will be used from this point on in the lab. Step 98 Click Cancel on CWMSDeploy Step 99 Click Yes to confirm Step 100 Click Cancel on IRPDeploy Step 101 Click Yes to confirm Make sure the two VMs being deployed are canceled above or the system will run out of hard disk space. If these two VMs deployments do not get cancled the system will not be able to restart the real VMs when setting high availability later in the lab. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 36 of 173

37 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 Property Configuration Click OK, to finish editing settings Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 37 of 173

38 Powering On Virtual Machines In this section the four VMs will be power on in various different ways, since there are many ways to do the same function in vcenter. Each VM will be turned on one at a time and watch the results on the VM console, in this next section. Step 102 Click and highlight CWMS01 in vcenter Step 103 Right click CWMS01 Step 104 Select Power Power On Step 105 Click and highlight IRP01 Step 106 Press CTRL-B, on the keyboard to start IRP01 Step 107 Click and highlight CWMS02 Step 108 Click the green arrow just above the VMs to start CWMS02 Step 109 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. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 38 of 173

39 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 110 Click and highlight CWMS01 in vcenter Step 111 Right click CWMS01 from the pop-up menu Step 112 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 (@pstryer) 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 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 39 of 173

40 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 initial 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 Description Public VIP IP address for the WebEx site URL (site users access to host and attend meetings) Private VIP 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). WebEx Site URL Secure http URL (all lowercase characters) for users to host and attend meetings. WebEx Administration URL Secure http URL (all lowercase characters) for administrators to configure, monitor, and manage the system. FQDN for the Internal VMs Depending on the system size you selected, the fully qualified domain name (all lowercase characters) of the media and web virtual machines. FQDN for the IRP 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 113 Open Internet Explorer, in the RDP session connected to SiteB-AD ( x.120) Step 114 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 115 Click Continue to this website (not recommended) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 40 of 173

41 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 when in a production install. In the lab if the browser gets closed, please inform your proctor and the VM will be shut off and turned back on. The difference of production and lab is the VMs are locked down in the lab and only need ot be shut down and restarted. In production they are not locked down so it you close the browser, the VM will need to be deleted and redeployed. Step 116 Select English Step 117 Click Next Step 118 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 119 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 41 of 173

42 Step 120 Click Next Step 121 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. Step 122 Click Next Step 123 Select Manual Step 124 Click Next Step 125 Select Create an Internet Reverse Proxy virtual machine (default) Step 126 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 42 of 173

43 Step 127 Enter , 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. Earlier in this lab the students added entries pointing to the public and private VIPs in DNS Meetingadmin.siteb.com = Meeting.siteb.com = Step 128 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 43 of 173

44 Step 129 Enter , for the private virtual IP (VIP) Step 130 Click Next Step 131 Enter srecwmsxy.cisco.com (xy = pod#), in the WebEx site URL (must be in DNS) Pod # WebEx Site URL Pod 01 srecwms01.cisco.com Step 132 Enter meetingadmin.siteb.com, in the Pod 02 srecwms02.cisco.com WebEx Administration URL (must be in DNS) Pod 03 srecwms03.cisco.com Pod 04 srecwms04.cisco.com Pod 05 srecwms05.cisco.com Pod 06 srecwms06.cisco.com Pod 07 srecwms07.cisco.com Pod 08 srecwms08.cisco.com Pod 09 srecwms09.cisco.com Pod 10 srecwms10.cisco.com Pod 11 srecwms11.cisco.com Pod 12 srecwms12.cisco.com Pod 13 srecwms13.cisco.com Pod 14 srecwms14.cisco.com Pod 15 srecwms15.cisco.com Pod 16 srecwms16.cisco.com Pod 17 srecwms17.cisco.com Pod 18 srecwms18.cisco.com Pod 19 srecwms19.cisco.com Pod 20 srecwms20.cisco.com Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 44 of 173

45 Step 133 Click Next Step 134 Click Next, after reviewing network configuration Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 45 of 173

46 Step 135 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 136 Switch to the vcenter, in the RDP session to the pod AD server Step 137 Highlight IRP01, in the left side navigation section of the vsphere client Step 138 Right Click IRP01 Step 139 Select Open Console, this will open up in a new pop-up window Step 140 Review the IRPs system check, and notice it is waiting connection from the Admin VM Step 141 Return to the web browser with the hostnames and deploy the VMs web page the student was just configuring Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 46 of 173

47 Step 142 Enter irp01.siteb.com, in the IRP FQDN field. This pairs the CWMS admin server with the IRP01 server Step 143 Click Detect Virtual Machines Notice the IRP is Connected Step 144 Click Next Step 145 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 ) Patience is a Virtue (NO they don t spin) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 47 of 173

48 Notice all checked out OK Step 146 Click Next Step 147 Review the VM installation completion, page Step 148 Click Continue Step 149 Click Continue to this website (not recommended) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 48 of 173

49 Step 150 Enter siteb-ad.siteb.com, in the FQDN of the mail server (keep rest default) Step 151 Click Next Step 152 Select San Francisco, for the time zone Step 153 Select U.S., for the locale Step 154 Click Next Step 155 Click Confirm, after reviewing settings Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 49 of 173

50 Step 156 Enter Alex, for the Administrator First Name Step 157 Enter Ace, for the Administrator Last Name Step 158 Enter for the address Step 159 Enter to confirm the address Step 160 Click Next Step 161 Enter for the new password Step 162 Enter to confirm the new password Step 163 Click Submit Step 164 Enter in the address field (default) Step 165 Enter in the password field Step 166 Click Sign In Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 50 of 173

51 If the browser is not waiting to login to the WebEx Administration web page, you can get there by entering the following URL Step 167 Click Close, to close the Welcome pop-up screen (If it appears) Step 168 Click X, welcome Alex Ace screen Step 169 Click X, to close the yellow VM needs attention warning at the top of the browser (If shown) Step 170 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 171 Switch to vcenter in the RDP session to the AD server Step 172 Click and Highlight IRP01 Step 173 Right click and Open Console on IRP01 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 51 of 173

52 Step 174 Obverse IRP01 is now connected to Admin VM CWMS01.siteb.com. Previously this server was waiting for connection Step 175 Close the console when done observing Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 52 of 173

53 Section 3: Configuring High Availability In this section the student will pair the CWMS02 and IRP02, as was done in the second half of section 2 to pair CWMS01 and CWMS02. 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 ( 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 53 of 173

54 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 176 Switch to vcenter, in the RDP session to the AD server Step 177 Click and highlight CWMS02 Step 178 Select Open Console Step 179 Observe CWMS02, successfully power on, write down the new administrator URL (when finished continue on) Step 180 Switch back to the vcenter (if not already on the vcenter) Step 181 Click and highlight IRP02 Step 182 Select Open Console Step 183 Observe IRP02, has successfully powered on, and is waiting for connection Step 184 Switch back to Internet Explorer (IE), on the AD RDP session Step 185 Open a new Browser tab Internet Explorer IE Step 186 Enter the URL seen in the console output when starting CWMS02 for example 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 random passphrase is created for that specific deployment only. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 54 of 173

55 Step 187 Click Continue to this website (not recommended), to confirm the security certificate in the browser Step 188 Select English Step 189 Click Next Step 190 Select Deploy a new system Step 191 Click Next Step 192 Click Next, on the check your system size web page Step 193 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 2 nd admin is being configured the student is selecting High Availability (HA) Step 194 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 55 of 173

56 Step 195 Select Manual, deploy Step 196 Click Next Step 197 Check Create an Internet Reverse Proxy virtual machine (default) Step 198 Click Next Step 199 Click Next, to confirm network configuration Step 200 Enter irp02.siteb.com, in the Internet Reverse Proxy field (remember the IRP02 has already been powered on and is waiting) Step 201 Click Detect virtual machines Notice the IRP is not connected and is waiting Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 56 of 173

57 Noticed that IRP02 is connected Step 202 Click Next Step 203 Wait for the System Check, to finish in about 5 minutes Step 204 Click Next If any red Xs appear you will have to check the acknowledgement box before you click next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 57 of 173

58 If all green check marks appear, just click Next to continue on Observe the HA Completion Information Screen Step 205 Close the HA browser tab and return to the CWMS01 Admin browser tab Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 58 of 173

59 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. Due to time constraints in the lab, the student will configure HA right up to the point of enabling HA, but will cancel the configuration at that point. HA can take 45 or more minutes to synchronize the databases. Step 206 Click System View More, under system in the center section. If you are logged out of meetingadmin.siteb.com web page then log back in with the user = aace@siteb.com password = Cisc0123@ Step 207 Click Add High Availability system Step 208 Click Continue Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 59 of 173

60 Step 209 Enter cwms02.siteb.com, in the FQDN admin VM for HA field Step 210 Click Continue Step 211 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. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 60 of 173

61 Step 212 Click CANCEL, on the maintenance mode warning pop-up message. This will automatically put the system in maintenance mode and start the database sync process Make sure to click CANCEL here, the function of synchronizing the databases takes 45 or more minutes. The rest of the HA section will be for reference only, and not steps that the student will need to perform. Step 213 Click CANCEL AGAIN The following steps denoted with the arrows are not to be done in the lab, the following are the last steps of configuring HA after the database synchronization, and would be what is seen if the HA was allowed to continue. Click Done, if the synchronization is finished if not wait till finished and you see the screen below Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 61 of 173

62 Observe HA has status of good for both CWMS02 and IRP02 Switch to vsphere client Highlight CWMS02 Right Click CWMS02 Open Console (if open select from task bar) Observe the CWMS02 is connected to cwms01.siteb.com Close the CWMS02 console Switch back to the vcenter, main window Highlight IRP02 Right Click IRP02 Open Console (if open select from task bar) Observe the IRP is connected to cwms01.siteb.com Close the IRP02 console Please move on to Section 4 and continue configuring the lab and following the steps. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 62 of 173

63 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. In this section the system will still be configured as if the HA system was completed to allow the student to become familiar with configuring a fully HA system. 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 ( 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 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 63 of 173

64 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. 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 214 Open a browser on the students computer (local browser not the RDP computer) Step 215 Navigate to 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 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 # CUCM Ext Address Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 64 of 173

65 Step 216 Click Cisco Unified Communications Manager Step 217 Enable or acknowledge any browser security certificate warnings Step 218 Enter Administrator, in the username field Step 219 Enter Cisc0123, in the password field Step 220 Click Login Configuring SIP Trunk Security Profiles Step 221 Click System Security SIP Trunk Security Profile Step 222 Click Find Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 65 of 173

66 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. Step 223 Click Non-Secure SIP trunk Profile Step 224 Click Copy Step 225 Enter CWMS Load Balancer, in the name field (leave everything else default) Step 226 Click Save Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 66 of 173

67 Step 227 Click Copy, on the security Profile just created Step 228 Enter CWMS Application Server, in the name field Step 229 Enter 5062, in the Incoming Port field Step 230 Click Save Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 67 of 173

68 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 to route calls to and from CWMS. 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 68 of 173

69 Step 231 Click Device Trunk Step 232 Click Add New Step 233 Select SIP Trunk Step 234 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 69 of 173

70 Step 235 Fill in the following fields as follows a. Name = CWMS_LB01 b. Description = CWMS Load Balancer 01 c. Device Pool = Default d. Destination Address = (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 Step 236 Click Add New, while on the trunk page that was just created Step 237 Select SIP Trunk Step 238 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 70 of 173

71 Step 239 Fill in the following fields as follows a. Name = CWMS_LB02 b. Description = CWMS Load Balancer 02 c. Device Pool = Default d. Destination Address = (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 Step 240 Click Add New, while on the trunk page that was just created Step 241 Select SIP Trunk Step 242 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 71 of 173

72 Step 243 Fill in the following fields as follows a. Name = CWMS_AppSrv01 b. Description = CWMS Application Server 01 c. Device Pool = Default d. Destination Address = (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 Step 244 Click Add New, while on the trunk page that was just created Step 245 Select SIP Trunk Step 246 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 72 of 173

73 Step 247 Fill in the following fields as follows a. Name = CWMS_AppSrv02 b. Description = CWMS Application Server 02 c. Device Pool = Default d. Destination Address = (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 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 248 Select Call Routing Route/Hunt Route Group Step 249 Click Add New Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 73 of 173

74 Step 250 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 251 Select Call Routing Route/Hunt Route List Step 252 Click Add New Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 74 of 173

75 Step 253 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 254 Select Call Routing Route/Hunt Route Pattern Step 255 Click Add New Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 75 of 173

76 Step 256 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 257 Select Call Routing SIP Route Pattern Step 258 Click Add New Step 259 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 260 Click Copy, while still on the SIP route pattern previously created Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 76 of 173

77 Step 261 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 262 Select Call Routing Translation Pattern Step 263 Click Add New Step 264 Enter the following Information in the route group e. Translation Pattern = \ XXXX 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 77 of 173

78 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 265 Select User Management User Settings UC Service Step 266 Click Find Step 267 Observe the list of preconfigured UC Services Step 268 Click Add New Step 269 Select Conferencing, form the drop-down menu Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 78 of 173

79 Step 270 Click Next Step 271 Enter the following Parameters a. Product Type = WebEx (Conferencing) b. Name = CWMS01_SRV c. Description = CWMS Service d. Host name/ip Address = cwms01.siteb.com e. Port = 80 (default) f. Protocol = HTTP (default g. SSO Identity Provider = UNChecked h. Click SAVE Step 272 Click Copy Step 273 Change the name to CWMS02_SRV Step 274 Change the host name/ip address to cwms02.siteb.com Step 275 Click Save Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 79 of 173

80 Step 276 Select User Management User Settings Service Profile Step 277 Click Find Step 278 Select Student_SrvPro Step 279 Scroll down to Conferencing Profile Step 280 Observe that it was previously configured Step 281 Select CWMS01_SRV, in the primary drop-down box Step 282 Select CWMS02_SRV, in the secondary drop-down box Step 283 Leave the rest of the fields Default Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 80 of 173

81 Step 284 Click Save Step 285 Switch to Pxy-WS01, (Alex Ace s x.201 RDP Session) Step 286 Click the Jabber, icon on the task bar at the bottom of the screen to bring it to top focus Step 287 Select File Options Step 288 Select Meetings, form the left navigation menu Step 289 Select Set up account, button the upper left Step 290 Observe it reads ciscoucft.webex.com Step 291 Click Cancel, to close the meetings host account window Step 292 Click Cancel, on the jabber options window to close the window Step 293 Select File Exit, to close the Jabber client Step 294 Double Click the Jabber shortcut on the desktop to turn Jabber back on Step 295 Select File Options Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 81 of 173

82 Step 296 Select Meetings, form the left navigation menu Step 297 Select Set up account, button the upper left Step 298 Observe it now reads cwms01.siteb.com (ignore the account verification Warning, CWMS is not configured for users yet) Step 299 Click Cancel, to close the meetings host account window Step 300 Click Cancel, on the jabber options window to close the window Step 301 Repeat steps 285 to 300, for Pxy-WS02 (Blake Bad x.202 RDP Session) The Jabber client conference configuration will be demonstrated and tested in subsequent sections Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 82 of 173

83 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 302 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 303 Click and accept any browser security certificate messages Step 304 Enter aace@siteb.com, in the user name field Step 305 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 83 of 173

84 Step 306 Navigate to Settings Audio Step 307 Click Continue, to begin configuring CUCM audio integration Step 308 Click Continue Step 309 Click Continue, to enter maintenance mode Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 84 of 173

85 Step 310 Click Add, to add CUCM Step 311 Enter , in the CUCM 1 IP Address field Step 312 Click Continue Step 313 Click Continue Step 314 Click Add, to add the Access Number Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 85 of 173

86 Step 315 Enter CWMS Call In, in the Phone Label field Step 316 Enter 2999, in the Phone Number field Step 317 Click Continue Step 318 Click Finish Step 319 Click OK, on the maintenance mode warning Step 320 Scroll down to the Caller ID section of the audio configuration page Step 321 Enter , in the Caller ID field Step 322 Check the Bypass pressing 1, field Step 323 Scroll down click Save Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 86 of 173

87 Step 324 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 325 Select Mobile, from the navigation section on the left side of the page Step 326 Check ios WebEx applications, to enable mobile devices (checked by default) Step 327 Select Video, from the navigation section on the left side of the web page Step 328 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 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 329 Select Branding, from the navigation section on the left side of the web page Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 87 of 173

88 Step 330 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 331 Select Desktop, from the left side under favorites (If on SiteB-AD RDP session) Step 332 Select CWMS, folder (If on SiteB-AD RDP session) Step 333 Select siteblogo.jpg, from the listed files (If on SiteB-AD RDP session) Step 334 Click Open Step 335 Click Upload Step 336 Scroll down click Save Step 337 Select Meetings, from the navigation section on the left side of the web page Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 88 of 173

89 Step 338 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 339 Click System, at the top of the page Step 340 Click View More, under Server Configuration section Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 89 of 173

90 Step 341 Click Add A Storage Server Now Step 342 Enter siteb-ad.siteb.com:/nfsshare (case sensitive and don t forget the colon : ) Step 343 Click Continue Step 344 Click Done, to finish the addition of the NFS Server configuration Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 90 of 173

91 Step 345 Observe both the Mail server and NFS server are properly configured and operational Step 346 Click Settings Meetings, observe record is now selected. Record is grayed out before you add a NFS server settings Step 347 Click Turn Off maintenance Mode, in the upper right corner of the web WebEx Admin web page Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 91 of 173

92 Step 348 Click Continue, to the restart warning Step 349 Switch to SiteB-AD RDP session ( x.120) Step 350 Switch to vcenter Step 351 Click and Highlight CWMS01 Step 352 Right Click CWMS01 Step 353 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 CWMS01 & IRP01 are rebooting, but CWMS02 & IRP02 are NOT rebooting. If HA had been allowed to finish, all four servers would be rebooting This reboot should take about 10 to 12 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 92 of 173

93 Adding Users Manually Step 354 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 355 Enter aace@siteb.com, in the user name field Step 356 Enter Cisc0123@, in the password field Step 357 Click Login Step 358 Observe that all processes are Good, if not wait for them to all start and become good (green) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 93 of 173

94 Manually Adding Users Step 359 Click Users from the top menu Step 360 Click Add User Step 361 Enter the following for the first user a. Account Type = Host b. First Name = Blake c. Last Name = Bad d. Language = English (default) e. address = bbad@siteb.com f. Time Zone = San Francisco (Pacific Daylight Time, GMT -07:00) g. Click Save Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 94 of 173

95 Step 362 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 95 of 173

96 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 363 Click Users Step 364 Click Directory Integration Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 96 of 173

97 Step 365 Click Add CUCM Server Step 366 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 97 of 173

98 Step 367 Click Enable LDAP Authentication Step 368 Click Continue, to the LDAP Authentication warning Step 369 Observe the LDAP Authentication Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 98 of 173

99 Step 370 Click Synchronize Now Step 371 Observe Synchronize, finishes Step 372 Click Save Step 373 Click Users, from the top menu Step 374 Observe the users from CUCM have been downloaded to the CWMS Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 99 of 173

100 Step 375 Switch to Pxy-WS01, (Alex Ace x.201 RDP Session) Step 376 Click Outlook, from the task bar at the bottom of the screen Step 377 Click and Highlight the latest from CWMS Admin (since AD and Exchange are on a share server with minable memory it might take a few seconds for the to arrive at the inbox) Step 378 Observe that CWMS completed synchronizing the LDAP Directory Step 379 Minimize Outlook WebEx Meeting Server Testing Step 380 Switch to Pxy-WS01 (Alex Ace x.201 RDP session), (The student might already be on this RDP session from previous section) Step 381 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 382 Enter 2999 & press Enter, in the search or call field of Cisco Jabber Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 100 of 173

101 Step 383 Listen for the WebEx Auto Attendant Step 384 Observe the Caller ID, (Cisco WebEx) Step 385 Observe that Jabber status has moved from Available to On A Call, and returns to Available once the call is disconnected. Step 386 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 387 Switch to the Pxy-WS01 (Alex Ace x.201), the student might already be on the RDP session from previous section Step 388 Click IE, icon on the task bar of PodXY-WS01 (xy = pod#) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 101 of 173

102 Step 389 Enter (XY = pod#), in the URL address filed and hit enter If the web page does not appear click the browser refresh button Step 390 Click Continue to this website (not recommended) Step 391 Enter aace@siteb.com, Address filed Step 392 Enter Cisc0123, in the password field. (remember the password is now coming from the CUCM so we have dropped at the end of the password since we added LDAP to CWMS) Step 393 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 394 Review the preference sittings, leave them all default Step 395 Click Done Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 102 of 173

103 Step 396 Click No Thanks, start using WebEx Step 397 Close Outlook, if it is open Step 398 Click Downloads, in the upper right corner of the web page Step 399 Click Download, under Productivity tools Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 103 of 173

104 Step 400 Click Run, at the bottom of the web page (or click Save File if using Firefox) Step 401 Click Next (It will take a little bit of time for this screen to appear) Step 402 Select I Accept, radio button on the license agreement page Step 403 Click Next Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 104 of 173

105 Step 404 Click Next, to accept the default destination Step 405 Click Yes, to allow software installs (This screen takes some time to appear) Step 406 Click Finish Step 407 Click Yes, to any certificate warnings (this pop-up will take 15 seconds to pop-up) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 105 of 173

106 Step 408 Enter srecwmsxy.cisco.com, (xy=pod#) Should be defaulted to your pod Step 409 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 410 Enter aace@siteb.com, in the address field Step 411 Enter Cisc0123, in the password field Step 412 Select Remember Me (default) Step 413 Select Automatically sign in (default) Step 414 Click Sign In Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 106 of 173

107 Step 415 Observe the positive login pop-up at the bottom right side of the screen Step 416 Click Continue to this website (not recommended), on the browser that opens Step 417 Click OK, after reviewing the web page Step 418 Close All browser windows on Pxy-WS01 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 107 of 173

108 End User Password Change and First Login When a user is manually created in CWMS administration web page, an 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 . If LDAP authentication is used, there is not a create password sent, and the user must use their LDAP password to get into WebEx. Step 419 Switch to PodXY-WS02, (xy=pod# Blake Bad x.202 RDP Session) Step 420 Click Outlook, on the taskbar at the bottom of the screen Step 421 Observe in the Home menu there are no WebEx buttons, this is because PTtools has not been installed yet Step 422 Click and Highlight the latest from CWMS, with the subject of Create a Password (due to memory limitations in the lab it might take a minute for the mail to be delivered) Step 423 Click Create Password Step 424 Click Continue to this website (not recommended) Step 425 Enter Cisc0123, in the new password field Step 426 Enter Cisc0123, in the confirm new password field Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 108 of 173

109 Step 427 Click Submit Step 428 Enter in the Address field if not already filled in for you Step 429 Enter Cisc0123, in the password filed Step 430 Click Sign In, to login to WebEx user page for Blake Bad Step 431 Observe account preferences Step 432 Click Done Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 109 of 173

110 Step 433 Close Outlook Step 434 Click Download Now, to download the productivity tools Step 435 Click Run (wait for it sometimes little slow) Step 436 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. in the taskbar to bring the Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 110 of 173

111 Step 437 Select I Accept, radio button on the license agreement page Step 438 Click Next Step 439 Click Next, to accept the default destination Step 440 Click Yes, to allow software installs (this window takes about 15 seconds to pop-up, wait for it) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 111 of 173

112 Step 441 Click Finish Step 442 Click Yes, to accept untrusted certificates Step 443 Enter srecwmsxy.cisco.com, (xy=pod#) Should be defaulted to your pod Step 444 Click Next Step 445 Enter in the address field Step 446 Enter Cisc0123, in the password field Step 447 Select Remember Me (default) Step 448 Select Automatically sign in (default) Step 449 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 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 112 of 173

113 Step 450 Click Continue to this website (not recommended), on the browser window that pop-up Step 451 Observe the web page that opens automatically once logged in Step 452 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 113 of 173

114 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 453 Switch to Pxy-WS02 (Black Bad x.202 RDP session), if not already using this workstation from previous section Step 454 Click the Up Arrow to open the system tray Step 455 Right click WebEx Assistant Step 456 Click Meeting Now Step 457 Click Set Meeting Preferences, for the first time in. A browser window will open Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 114 of 173

115 Step 458 Click Continue to web site (not recommended) Step 459 Scroll Down & click Update, to take the defaults Step 460 Click the Up Arrow to open the system tray to try meeting now again Step 461 Right click WebEx Assistant Step 462 Click Meeting Now Step 463 Observe the PC communicating with the CWMS Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 115 of 173

116 Step 464 Click Yes or Accept any and all security certificate warnings Step 465 Observe that Black Bad is now in a Web Ex meeting Step 466 Observe the Meeting Reminder that pops-up if Outlook happens to be open Step 467 Click X, in the upper right side to close the meeting reminder if one opens Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 116 of 173

117 Step 468 Enter , to allow WebEx meeting server to call Blake back Step 469 Click Call Me Step 470 Click Answer, on the Jabber call pop-up Step 471 Observe Cisco Jabber session windows pop-up Step 472 Observe WebEx Audio connecting the call to the WebEx session Step 473 Click the Keypad and press 1 Step 474 Switch to the WebEx Meeting Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 117 of 173

118 Step 475 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 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 CWMS server, and try both calls again Step 476 Click the Invite and remind others to join icon on the WebEx desktop, or click Participants Invite and Remind or Step 477 Enter aace@siteb.com, in the invitees field Step 478 Click Send Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 118 of 173

119 Step 479 Click Done, on the conformation Step 480 Switch to PodXY-WS01 (Alex Ace x.201 RDP session) Step 481 Open Outlook Step 482 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 483 Click the X to close the Jabber meeting reminder Step 484 Open Outlook, with the icon on the task bar if not all ready open Step 485 Highlight and open the from Blake Bad via Cisco WebEx Step 486 Click Accept, Send the Response Now, in the upper section of the reading pane Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 119 of 173

120 Step 487 Dismiss the Reminder pop-up from Outlook and Jabber Step 488 Click the Calendar icon in the lower left corner of Outlook Step 489 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 490 Click Join The Meeting Step 491 Click Continue to this website (not recommended) Step 492 Enter Alex Ace, in the Name field Step 493 Enter in the address field Step 494 Click Join Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 120 of 173

121 Step 495 Enter Cisc0123, in the password field that pop-ups Step 496 Click Sign In Step 497 Click Install, if the browser is missing any software (Skip this step if you don t get this screen) Step 498 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 121 of 173

122 Step 499 Click Yes, to any browser security Alerts Step 500 Observe while the workstation is logged into the WebEx meeting Step 501 Observe both Blake Bad and Alex Ace are now in the meeting Step 502 Enter , in the audio conference call me filed Step 503 Click Call Me Step 504 Click Answer, on the Jabber call pop-up Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 122 of 173

123 Step 505 Observe Cisco Jabber session windows pop-up Step 506 Observe WebEx Audio connecting the call to the WebEx session Step 507 Click the Keypad and press 1 Step 508 Switch to the WebEx Meeting Step 509 Observe that both Blake and Alex have audio connected to the meeting Step 510 Click on the Jabber Icon, to bring Jabber to focus on Pxy-WS01 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 123 of 173

124 Step 511 Observe that Alex Ace is In A meeting Step 512 Enter 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 513 Enter aace@siteb.com, in the Address field Step 514 Enter Cisc0123@, in the password field Step 515 Click Sign In Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 124 of 173

125 Step 516 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 Testing WebEx Meeting Server Features In this section the student will explore the many 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 517 Click the Video button in Pxy-WS01 (Alex Ace x.201 RDP Session) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 125 of 173

126 Step 518 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 519 Switch to Pxy-WS02 ( x.202) RDP session Step 520 Click the Video Button Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 126 of 173

127 Step 521 Observe that video for Blake is now streaming (crept keeper) Step 522 Switch to Pxy-WS01 (Alex Ace RDP session) Step 523 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. Click the ManyCam icon on the desktop of WorkStation01 or WorkStation02 b. Click the Source tab Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 127 of 173

128 c. Click Image Gallery d. 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 e. Minimize ManyCam f. Click the settings button in WebEx g. Make sure Capture Device is set to ManyCam Virtual WebCam h. Click OK Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 128 of 173

129 i. This should allow virtual video to stream between the two virtual workstations Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 129 of 173

130 Meeting Recording & Desktop Sharing In this section the student will explore the ability and functionality of record meetings, and use desktop sharing. Step 524 Click Record, from WebEx meeting on PodXY-WS02 the host Step 525 Observe the record app in the lower right of the WebEx Meeting Step 526 Click Share My Desktop icon on the desktop, or click Share My Desktop from the drop down menus, on Pxy-WS02 ( x.202) RDP session Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 130 of 173

131 OR Step 527 Double click the TestJabber.doc on the desktop of PodXY-WS02, to open the file in word Step 528 Switch to PodXY-WS01 RDP session Step 529 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 530 Move the mouse to the top of the screen to open (slides down from the top) the WebEx control panel Step 531 Click Participants, to open the participants list Step 532 Click Chat, from the WebEx drop down tool bar Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 131 of 173

132 Step 533 Observe that both participants and Chat are now open while viewing the desktop share from the host Step 534 Type a message in the Chat window and click Send Step 535 Switch to PodXY-WS02, (Blake Bad x.202 RDP session) Step 536 Drop Down the WebEx Tool bar and observe Chat is flashing Step 537 Click Chat, to open the chat window Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 132 of 173

133 Step 538 Click Participants, to open the participants windows Step 539 Observe the message from Black Bad Step 540 Click Recorder, from the drop down WebEx tool bar Step 541 Pause the recording by clicking the pause button Step 542 Click Pause, again to resume the recording Step 543 Click the Stop, button on the recording controls Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 133 of 173

134 Step 544 Click Stop Recording, on the pop-up warning message (after the meeting a 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 545 Click X, on the Recording, and Chat windows to close them Step 546 From the dropdown WebEx tool bar click Annotate Step 547 Observe the Annotation Tool bar Step 548 Click and Hold the Left mouse button and drag your mouse across the shared document to add some drawings on the page Step 549 Click the T on the annotation tools to start the text tool Step 550 Click on the word doc and type Step 551 Continue playing with the annotation tools Step 552 Switch to PodXY-WS01, (Alex Ace x.201 RDP session) Step 553 Observe that the participants can see the hosts annotation Step 554 Switch to PodXY-WS02, (Blake Bad x.202 RDP session) Step 555 Close the Annotation Tools, observe that the annotation goes away when you close the tool Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 134 of 173

135 Step 556 Click Assign Pass Keyboard and Mouse Control Blake Bad Step 557 Switch to PodXY-WS01, (Alex Ace x.201 RDP session) Step 558 Click Take Control, pop-up window Step 559 Observe the green tool bar says You are controlling Black Bad s desktop Step 560 Switch to PodXY-WS02, (Blake Bad x.202 RDP session) Step 561 Observe the green tool bar says Alex Ace is controlling your computer Step 562 Click on PodXY-WS02 (Blake Bads) desktop, to take control back Step 563 Observe the green bar changes to You are sharing your desktop Step 564 Click Stop Sharing, on the dropdown WebEx tool bar Administrator System Monitor In this section the student will look at system monitor while a meeting is active. Step 565 Navigate to meetingadmin.siteb.com, from the students local computer s browser Step 566 Click and accept any browser security certificate warnings Step 567 Enter aace@siteb.com, in the Address Field Step 568 Enter Cisc0123@, in the password field Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 135 of 173

136 Step 569 Click Sign In Step 570 Click Close, on the pop-up welcome screen (if it appears) Step 571 Observe the system monitor details, notice that one meeting is in progress Step 572 Return to the WebEx meeting on PodXY-WS02 (Blake Bad x.202 RDP session) Step 573 Click End Meeting, in the lower center of the web ex meeting window Step 574 Click End Meeting, on the pop-up warning window Step 575 Switch to PodXY-WS01 (Alex Ace x.201 RDP session) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 136 of 173

137 Step 576 Click OK, on the end of meeting pop-up window Step 577 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 137 of 173

138 Scheduling Meetings via WebEx Web Page In this section the student will schedule a meeting using the WebEx user web page. Step 578 Switch to Pxy-WS01, (Alex Ace X.201 RDP session) Step 579 Enter (xy=pod#), in Alex Ace s browser Step 580 Click and accept any browser security certificate warnings Step 581 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 582 Enter aace@siteb.com, in the address field Step 583 Enter Cisc0123, in the password field Step 584 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 585 Click X, to close the welcome at the top of the page (if presented) Step 586 Observe there are no upcoming meetings Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 138 of 173

139 Step 587 Click Schedule on the button bar Step 588 Enter Yearly Funding Meeting, in the what field Step 589 Enter 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 590 Enter ccool@siteb.com, and click on the info the system pulls up Step 591 Enter ssmith@siteb.com, and click on the info the system pulls up Step 592 Click Alternate Host for Blake Bad Step 593 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 139 of 173

140 Step 594 Click Schedule It Step 595 Open Outlook, if not open Step 596 Observe that both Outlook and Jabber both have meeting reminders for the Yearly Funding Meeting Step 597 Click Dismiss on the Outlook reminder Step 598 Click X, to dismiss the Jabber meeting reminder Step 599 Click Outlook, to bring it to top focus Step 600 Click the Calendar, icon in the lower left corner to open the calendar Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 140 of 173

141 Step 601 Scroll up and down on today s date to find the Yearly Funding Meeting Step 602 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 603 Switch back to the web page where the meeting was scheduled Step 604 Observe the page is ready and waiting to start the meeting since the meeting was scheduled for now when setup Step 605 Click Start Step 606 Click Install, to install any needed browser software Step 607 Click Yes, to any security alerts Step 608 Enter (408) (if not already populated in the phone field) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 141 of 173

142 Step 609 Click Call Me Step 610 Click Answer, on the Jabber incoming call pop-up Step 611 Switch to Pxy-WS02, (Blake Bad X.202 RDP Session) Step 612 Open Outlook if not already open Step 613 Click Dismiss, on the Outlook Reminder Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 142 of 173

143 Step 614 Click X, on the Jabber meeting reminder Step 615 Open IE on Blake Bad s workstation (Pxy-WS02) Step 616 Enter srecwmsxy.cisco.com, in the address field Step 617 Click Continue to this website (not recommended) Step 618 Click NO Thanks, to installing PTtools Step 619 Enter bbad@siteb.com, if asked to login Step 620 Enter Cisc0123, if asked to login Step 621 Observe there is one meeting schedule one into the WebEx user web site Step 622 Click Join, to enter the Yearly Funding Meeting Step 623 Click Yes, to any and all security alerts Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 143 of 173

144 Step 624 Enter , in the phone field if not populate Step 625 Click Call Me Step 626 Click Answer, on the Jabber incoming call pop-up Step 627 Switch to Pxy-WS01, (Alex Ace x.201 RDP Session) Step 628 Click End Meeting Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 144 of 173

145 Scheduling Meetings from Microsoft Outlook In this section the student will schedule and access meetings via Microsoft Outlook. Step 629 Switch to P01-WS01 ( x.201) RDP session Step 630 Open Outlook Step 631 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 632 Click TO, button to add recipients Step 633 Select Blake Bad, from the attendee pop-up window Step 634 Click OK, to accept Blake as an attendee Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 145 of 173

146 Step 635 Enter Sales Meeting, in the subject filed Step 636 Enter WebEx, in the location filed Step 637 Click Add WebEx Meeting, from the top tool bar Step 638 Enter 12345, in the meeting password field Step 639 Select Alternate Host, tab Step 640 Select Blake Bad, as the alternate host Step 641 Click OK, to accept information Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 146 of 173

147 Step 642 Click Send Step 643 Click Dismiss, on the sales meeting reminder (If appears) Step 644 Select Calendar, icon in the bottom left of Outlook Step 645 Double click Sales Meeting, you might have to scroll up and down to find it Step 646 Click Meeting Hyperlink or JOIN in the jabber pop-up, from the body of the calendar event. Take note of the meeting password Or Both the outlook hyperlink and the Jabber Join button take you to the same place in the next step. Step 647 Click Continue to this website (not recommended) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 147 of 173

148 Step 648 Click Start Step 649 Click Yes, on any security alerts Step 650 Click Call Me, in the audio conference pop-up window Step 651 Click Answer on the Jabber pop-up window Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 148 of 173

149 Step 652 Observe Cisco Jabber window will pop-up and you will hear WebEx announcing you are being connected to WebEx meeting Step 653 Switch to the WebEx Meeting Window, by clicking the WebEx Meeting Icon on the task bar at the bottom of the screen Step 654 Click the Web Cam icon to send video to other participants Step 655 Switch to WorkStation02 RDP Session Step 656 Open Outlook Step 657 Click Dismiss All in the meeting reminder pop-up window Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 149 of 173

150 Step 658 Click Yes to confirm dismiss all Step 659 Click Join, on the Jabber Meeting Reminder for the Sales Meeting Step 660 Click Continue to this website (not recommended) Step 661 Enter Blake Bad in the name field Step 662 Enter in the address field Step 663 Click Join Step 664 Enter Cisc0123, in the password field when asked to sign in to Web Ex Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 150 of 173

151 Step 665 Click Install or Run, if asked to install the Cisco WebEx add-on Step 666 Click the flashing Shield icon in the task bar to bring the install message to focus Step 667 Click Yes, to allow the install to change the computer Step 668 Click Yes to any browser security alerts Step 669 Click Call Me on the Audio Conference pop-up window Step 670 Click Answer on the Jabber pop-up window Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 151 of 173

152 Step 671 Switch to the WebEx Meeting Window, by clicking the WebEx Meeting Icon on the task bar at the bottom of the screen Step 672 Observe that Alex Ace is sending video Step 673 Click the Camera icon to send video to other participants Step 674 Switch to Pxy-WS01 ( x.201) RDP Session Step 675 Observe that Black Bad is sending video Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 152 of 173

153 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 676 Install WebEx Meetings from the app store or market place to your mobile device Step 677 Open Web Ex or newer on your mobile device Step 678 Click the Sign In button Step 679 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 680 Enter srecwmsxy.cisco.com (xy = pod#) Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 153 of 173

154 Step 681 Click Next Step 682 Click OK or Continue, on the sign in security warning Step 683 Enter Step 684 Enter Cisc0123 in the password filed Step 685 Click Sign In Step 686 Switch to Pxy-WS01, ( x.201) RDP Session Step 687 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 154 of 173

155 Step 688 Click Join by Number, on the mobile device Step 689 Enter the Meeting Number/Access Code for the meeting open in your lab Step 690 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 691 Enter 12345, for the meeting password Step 692 Click OK Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 155 of 173

156 Step 693 Click Connect Using Internet, Audio conference Step 694 Observe that the mobile device has been Muted, automatically Step 695 Click the People icon button on the bottom of the mobile device to see the participants list Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 156 of 173

157 Step 696 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 697 Click the Video Camera icon on the bottom half of the screen, the student should see themselves in the video in the bottom Step 698 Switch to Pxy-WS01, ( x.201) RDP Session Step 699 Observe that Cindy Cool is in the participant list. She is Mobile, using Internet Audio, and is muted. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 157 of 173

158 Step 700 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 701 Switch to Pxy-WS01 ( x.201) RDP Session Step 702 Observe mobile video on Virtual workstation Adding 2 nd 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 703 From 2 nd Mobile device start WebEx app Step 704 Click App Store, to update WebEx App if needed Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 158 of 173

159 Step 705 Click Update Observe the install process Step 706 Click Open Step 707 Click Sign In Step 708 Enter srecwmsxy.cisco.com, (xy=pod#) 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 Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 159 of 173

160 Step 709 Enter in the field Step 710 Enter Cisc0123, in the password field Step 711 Click Sign In Step 712 Click Join by Number, in the lower right corner Step 713 Enter the Meeting Number for the current meeting Step 714 Click Join Meeting Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 160 of 173

161 Step 715 Enter 12345, for the meeting password Step 716 Click OK Step 717 Click Connect Using Internet, audio Conference Step 718 Observe the message that you have joined the audio conference Step 719 Observe the users has automatically been put on mute Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 161 of 173

162 Step 720 Click the People Icon, to see the current participants Step 721 Click the Information button to see the current meeting information Step 722 Click the Video Camera icon to send video from the mobile device Step 723 Click Start My Video, when ready to send video to the conference Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 162 of 173

163 Step 724 Observe the four participants are sharing video from the perspective of the ipad device Step 725 Switch to Pxy-WS01, ( x.201) RDP session Step 726 Click Share My Desktop Step 727 Open a document or something to share on the desktop of Pxy-WS01 Step 728 Switch back to the 2 nd mobile device, in this case a ipad Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 163 of 173

164 Step 729 Observe the shared desktop Step 730 Click the Door and Arrow, icon in the upper right corner to leave the meeting on the 2 nd device Step 731 Click Leave Step 732 Click Settings Step 733 Click Account Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 164 of 173

165 Step 734 Click Sign Out Step 735 Click Sign Out, conformation Step 736 Observe WebEx App returns to the first screen Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 165 of 173

166 Mobile Device Joining by Number (Optional) In this section the student will join a meeting with a mobile device via number Step 737 Click Join By Meeting Number Step 738 Enter current Meeting Number Step 739 Enter Name Step 740 Click Join Meeting Step 741 Enter 12345, in the meeting password field Step 742 Click OK Step 743 Click Connect Using Internet, audio conference Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 166 of 173

167 Step 744 Observe the Joined to audio conference Message Step 745 Observe the Auto Mute message Step 746 Click the People Icon to observe the current participants Step 747 Click the Camera icon to preview your mobile device video Step 748 Click Start My Video when ready to transmit video to the conference Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 167 of 173

168 Step 749 Observe three users in the meeting Step 750 Click the Door with Arrow, to leave the meeting from the mobile device Step 751 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 752 Open AnyConnect, on your mobile device. If your device does not have AnyConnect download and install it from the App store or Marketplace Step 753 Select Add VPN Connections Step 754 Enter CWMS Lab, in the description field Step 755 Enter sre-collab01.cisco.com/student Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 168 of 173

169 Step 756 Select Save Step 757 Slide AnyConnect VPN to ON Step 758 Select Continue Step 759 Enter cwms-podxy for the username Step 760 Enter the password giving by the proctor at the start of lab Step 761 Select Connect Step 762 Select Accept, on the banner Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 169 of 173

170 Step 763 Observe that VPN connection has been created Step 764 Open WebEx app Step 765 Click Sign In Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 170 of 173

171 Step 766 Click Sign in through your corporate website Step 767 Enter srecwmsxy.cisco.com, (xy=pod#) Step 768 Enter in the address field Step 769 Enter Cisc0123, in the password field Step 770 Click Sign In Step 771 Click Join, on the meeting that was started in the previous section Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 171 of 173

172 Step 772 Click Connect Using Internet, audio connection Step 773 Observe the mobile device has entered the meeting using a VPN and the WebEx Meeting app Step 774 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 3.2 Presented by CAPO Solutions Readiness Engineers Page 172 of 173

173 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: To access the videos for this Cisco WebEx Meeting Server Lab directly go to the following links CWMS Lab Part CWMS Lab Part CWMS Lab Part Thank you for taking our lab and as always thank you for using Cisco products. Lab Guide Version 3.2 Presented by CAPO Solutions Readiness Engineers Page 173 of 173