Cisco WebEx Enabled TelePresence Configuration Guide
Cisco WebEx Enabled TelePresence Configuration Guide
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco WebEx Enabled TelePresence Configuration Guide 2013 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
i i i ii
Cisco WebEx Features and Important Notes Document Organization Related Documents
v v
vii 1-1
Cisco WebEx Enabled TelePresence Experience 1-1 Scheduling the Meeting 1-1 Starting/Joining the Meeting 1-2 Cisco TelePresence Meeting Experience 1-2 Cisco WebEx Meeting Experience 1-2 Recommended Screen Resolutions for Presentation Sharing Passing the Ball 1-3 Viewing the Meeting in WebEx 1-3 Understanding How Cisco WebEx Enabled TelePresence is Deployed SIP Video, Presentation and Audio 1-6 SIP Video, Presentation and PSTN Audio 1-7 Cisco TMS Scheduling Role 1-9 TelePresence Server and MCU Roles 1-9 Presentation Display Details for Multiple Presenters 1-9 Meeting Participant List 1-9
1-3
1-6
Understanding Cisco WebEx Enabled TelePresence Scheduling Flow 1-10 Scheduling with the Cisco WebEx and TelePresence Integration to Outlook Scheduling with the Cisco Smart Scheduler 1-13 Scheduling with the Cisco WebEx Scheduling Mailbox 1-15 Understanding Cisco WebEx Enabled TelePresence Call Flow 1-16 SIP Audio Call Flow 1-17 TSP Audio Call Flow with API Command to Unlock Waiting Room 1-19 TSP Audio Call Flow with Waiting Room and MCU as Host 1-20
1-11
Contents
1-22 2-1
2-1
Configuration Task Checklist 2-3 Cisco MCU 2-3 Cisco TelePresence Server 2-4 Cisco Video Communications Server 2-4 Cisco Unified Communications Manager 2-4 Cisco TelePresence Management Suite 2-6 Configure Audio for Cisco WebEx Enabled TelePresence Cisco WebEx Site Administration 2-7 Configuring Cisco MCU and TelePresence Server Contents Introduction
3-1 3-1 3-1
2-7
Required Settings for MCU 3-2 SIP 3-2 Content Mode 3-2 Video and Audio Codecs 3-2 Automatic Content Handover 3-3 Recommended Settings for MCU 3-3 Automatically Make Content Channel Important Outgoing Transcoded Codec 3-4 Adaptive Gain Control 3-4 Join and Leave Audio Notifications 3-5 Encryption 3-5 Required Settings for TelePresence Server SIP 3-6 Locally Managed Mode 3-6 Automatic Content Handover 3-6
3-5 3-3
Recommended Settings for TelePresence Server Display Setting 3-7 Configuring Call Control Introduction
4-1 4-1
3-7
Configuring Cisco TelePresence Video Communication Server Control and Expressway Prerequisites 4-2 Creating a New DNS Zone on VCS Expressway for WebEx 4-2
Cisco WebEx Enabled TelePresence Configuration Guide
4-1
OL-21352-02
Contents
Configuring Certificates from Intermediate Certificate Authorities Configuring Traversal Zones for MCUs with Encryption Enabled 4-4 Configuring Cisco Unified Communications Manager 4-4 Prerequisites 4-5 Configuring a SIP Trunk Between Unified CM and VCS Control Configuring Cisco TelePresence Management Suite Contents
5-1 5-1 5-2 5-1
4-3
4-5
Prerequisites
Configuring WebEx Users in Cisco TMS 5-4 User Requirements for Scheduling WebEx-enabled Meetings 5-4 Configuring Automatic User Lookup from Active Directory 5-5 Configuring Active Directory Lookup in Cisco TMS 5-5 How WebEx Bookings Work 5-5 Configuring a Cisco WebEx Enabled TelePresence User in Cisco TMS Configuring Port Reservations for MCU and TS in Cisco TMS Enabling Port Reservations for MCU 5-7 Enabling Port Reservations for TS 5-7 Configuring Hybrid Content Mode for MCU in Cisco TMS Configuring Conference Settings in Cisco TMS
5-8 5-7 5-6
5-6
Configuring Single Sign On in Cisco TMS 5-8 Prerequisites 5-9 Configuring SSO in Cisco TMS 5-10 Generating a Certificate for WebEx 5-10 Using an Existing Certificate Signed by a Trusted Authority 5-10 Creating a Key/Certificate Pair Signed by a Certificate Authority 5-11 Creating a Self-signed Key/Certificate Pair 5-11 Using OpenSSL to Generate a Certificate 5-12 Enabling Partner Delegated Authentication on the WebEx site 5-13 Enabling SSO in Cisco TMS 5-14 Supported Configurations for TMS to Schedule on Behalf of the WebEx Host
5-15 6-1
Configuring Cisco TelePresence Management Suite Extension for Microsoft Exchange Contents
6-1 6-1 6-2 6-2 6-2
Prerequisites
Configuring Cisco TMSXE for the WebEx and TelePresence Integration to Outlook
Contents
Installing the Cisco TMS Booking Service 6-2 Configuring IIS for HTTPS 6-3 Setting Up Communication Between Your WebEx Site and TMSXE 6-5 Configuring the Location Displayed for TelePresence Rooms in Outlook Installing the WebEx and TelePresence Integration to Outlook 6-6 Configuring Cisco TMSXE for the WebEx Scheduling Mailbox 6-6 Configuring the WebEx Scheduling Mailbox in Microsoft Exchange Adding the WebEx Mailbox to Cisco TMSXE 6-7 Additional Recommendations 6-7
6-6
6-5
7-1
Prerequisites
User Access to Cisco TMSPE 7-2 Creating a Redirect to Smart Scheduler Access Rights and Permissions 7-3 Time Zone Display 7-3 How Smart Scheduler Works Limitations
7-4 8-1 7-3
7-2
Prerequisites
8-1
Configuring SIP Audio for Cisco WebEx Enabled TelePresence 8-2 Configuring the WebEx Site in Cisco TMS to Use SIP Audio 8-2 Enabling Hybrid Audio on the WebEx Site 8-3 Configuring PSTN Audio for Cisco WebEx Enabled TelePresence 8-3 Configuring the WebEx Site in Cisco TMS to Use PSTN Audio 8-4 Enabling Hybrid Mode on the WebEx Site 8-4 Configuring PSTN Calls to Pass Through a PSTN Gateway to WebEx 8-4 Configuring PSTN Calls to Pass through a PSTN Gateway Registered to VCS 8-5 Configuring PSTN Calls to Pass through a PSTN Gateway Registered to Unified CM Configuring TSP Audio for Cisco WebEx Enabled TelePresence 8-7 Configuring MACC Domain Index and Open TSP Meeting Room Webex Settings Configuring the TSP Dial String 8-8 Configuring How the Conference is Opened 8-8 How TSP Integration Methods Affect Call Scenarios 8-8 How a TSP Meeting Works 8-10
Cisco WebEx Enabled TelePresence Configuration Guide
8-6
8-7
OL-21352-02
Contents
8-10 9-1
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Contents 9-1 Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Cisco TelePresence Cisco WebEx Integration Options 9-1 Assigning the Meeting Center TelePresence Session Type 9-3 Adding the Cisco TelePresence Session Type in the List of Users 9-3 Adding the Cisco TelePresence Session Type in the Edit User Screen 9-4 Installing the WebEx and TelePresence Integration to Outlook 9-5 Setting the Time Zone and Language Preferences for a Users WebEx Account 9-7 Where to Go Next
9-7 10-1
9-1
10-3 10-5
Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings Cisco TMS 10-5 MCU and TS 10-6 Endpoints 10-6 TMSXE 10-6 WebEx 10-7 Troubleshooting Contents
11-1 11-1
Verifying and Testing 11-1 Cisco WebEx Site Administration Online Help Troubleshooting Tips 11-1 Problems with Scheduling a Meeting 11-2 Problems with Starting or Joining a Meeting Problems During a Meeting 11-4 Problems with a TSP Audio Meeting 11-6
11-1
11-3
Managing System Behavior 11-8 Managing the Cisco WebEx Video View Window
11-9
Contents
OL-21352-02
Preface
Revised: April, 2013
This preface describes the purpose, audience, organization, and conventions of the Cisco WebEx Enabled TelePresence Configuration Guide and provides information about new features and how to obtain related documentation. This preface describes the following topics:
General Description, page i Audience and Scope, page i Cisco WebEx Features and Important Notes, page ii Prerequisites, page iv Document Organization, page v Related Documents, page v Obtaining Documentation and Submitting a Service Request, page vii
General Description
This document describes how to configure Cisco TelePresence applications for Cisco WebEx-to-Cisco Telepresence interoperability. The Cisco WebEx Enabled TelePresence Configuration Guide describes how to manage and monitor scheduled meeting interoperability between Cisco TelePresence System (CTS), Cisco TelePresence Server or MCU multipoint meetings, Cisco TMS, Cisco Unified Communications Manager (Cisco Unified CM), Cisco Video Communication Server (VCS) and the Cisco WebEx Meeting Center.
Preface
Supported Features
Cisco WebEx Enabled TelePresence provides the following key features:
Two-way video sharing with up to 720p screen resolution between the WebEx client and TelePresence endpoints Integrated audio and presentation sharing including application and desktop content sharing capability for all users in a meeting Integrated meeting scheduling using TelePresence Management Suite (Cisco TMS), which allows you to easily schedule Cisco WebEx Enabled TelePresence meetings Secure call control and connectivity enabled by media encryption provided by Cisco VCS Expressway Interoperability with third-party telepresence endpoints
Supported Feature
Audio
Description CTS participants have two-way audio with the Cisco WebEx meeting participants using G.711.
Note
Host
All Cisco TelePresence participants and the meeting organizer can be the default hosts. The MCU/TS dials in at the meeting start time automatically to connect all TelePresence participants. The MCU/TS becomes the host if the meeting organizer has not joined on WebEx yet. If the meeting organizer joins the meeting before the scheduled start time, they become the host.
ii
OL-21352-02
Preface
Table 1
Supported Feature
Scheduling
Description Use Cisco TMS, the WebEx and TelePresence Integration to Outlook, Smart Scheduler, or WebEx Scheduling Mailbox to schedule a Cisco TelePresence meeting with WebEx. Start your meeting either using One-Button-to-Push (OBTP) from scheduled Cisco TelePresence endpoints or using the Automatic Connect feature of Cisco TMS to connect all scheduled endpoints at the start time of your meeting. You can start the WebEx portion of a Cisco WebEx Enabled TelePresence meeting earlier than the scheduled time if you are the WebEx host. WebEx participants who try to join the WebEx meeting before the host, receive a message that the meeting has not started and they must wait to join until the scheduled start time or until after the WebEx host joins.
Note
Only scheduled meetings are supported for Cisco WebEx Enabled TelePresence Interoperability; non- scheduled TelePresence participants who want to join a Cisco WebEx enabled TelePresence meeting, must manually dial into the conference (MCU/TS) bridge. The meeting organizer reserves ports for video dial-in participants when scheduling the meeting.
See the Cisco TelePresence Management Suite Administrator Guide for meeting scheduling information.
Sharing
Cisco TelePresence users can share a presentation by connecting the video display cable of the TelePresence endpoint to their computer. Supported video display interfaces include VGA, DVI, HDMI, DisplayPort and Mini DisplayPort. Cisco WebEx Meeting Center clients can share the desktop or a selected application. Endpoints view and share Cisco WebEx presentation at 1024 x 768 (XGA) resolution. The resolution that endpoints are capable of sending may vary depending on the endpoint model, but the TS/MCU will transcode the presentation and send it to the WebEx cloud at 1024 x 768 resolution.
Note
The Cisco TelePresence user that is sharing with the video display cable needs to exit the Cisco WebEx Meeting Center client on their laptop before connecting the video display cable.
Two-way Video
Video quality is sent best effort from the Cisco TelePresence endpoint to Cisco WebEx and from Cisco WebEx to the Cisco TelePresence endpoint. The video from the CTS participants in the meeting are forwarded to the Cisco WebEx network, where they will be seen by Cisco WebEx participants along with other Cisco WebEx participants. Live video can be sent at minimum in Common Intermediate Format (CIF) format at 30 frames per second, at approximately 300-450 kbps up to a maximum of 720p. Presentations from the Cisco WebEx client are displayed on the local CTS projector, presentation display or with Presentation-in-Picture (PiP), depending on the capabilities of your CTS.
Note
All Cisco WebEx-enabled TelePresence meetings require the use of a Cisco TelePresence Server or MCU.
Feature Limitations
For a complete list of limitations and known issues for Cisco WebEx Enabled TelePresence, refer to the Cisco WebEx Enabled TelePresence release notes.
iii
Preface
Prerequisites
Table 2 lists Cisco WebEx Enabled TelePresence feature prerequisites.
Table 2 Cisco WebEx with the Cisco TelePresence System Prerequisites
Requirement Cisco TelePresence Management Suite (Cisco TMS) Cisco TelePresence Management Suite Extension for Microsoft Exchange (Cisco TMSXE) Cisco TelePresence Management Suite Provisioning Extension (Cisco TMSPE)
Description Cisco TMS is required for scheduling Cisco WebEx Enabled TelePresence meetings. Release 14.2 or later is required. Cisco TMSXE is required for scheduling Cisco WebEx Enabled TelePresence meetings through Microsoft Outlook using either the WebEx Productivity Tools Plug-in or WebEx Scheduling Mailbox Scheduling. Release 3.1 or later is required. Cisco TMSPE is required for scheduling Cisco WebEx Enabled TelePresence meetings using Smart Scheduler. Release 1.1 or later is required.
Note
Use of Smart Scheduler does not require the TMS provisioning option key.
Cisco TelePresence Video Communication Server (VCS) Cisco Unified Communications Manager (Unified CM) Cisco TelePresence Server
VCS Control and Expressway are a required as the call control solution. Release X7.2.2 or later is required. Unified CM is an optional call control solution that can be used with VCS for deployments with endpoints registered to Unified CM. Release 8.6.2 or higher is required. 9.1.1 is recommended. TelePresence Server can be used as a conference bridge for Cisco WebEx Enabled TelePresence meetings. Release 3.0 or later is required. Cisco TelePresence MCU can be used as a conference bridge for Cisco WebEx Enabled TelePresence meetings. Release 4.4 or later is required.
1. 2.
The Cisco WebEx Meeting Center site must be running release T28.10 or higher with the latest service pack. The Cisco WebEx site must be configured to support Cisco TelePresence Integration. See Chapter 9, Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account for more information.
Supported Endpoints
Any endpoint supported by TelePresence Server or MCU can join a Cisco WebEx Enabled TelePresence meeting.
iv
OL-21352-02
Preface
Table 2
Requirement
Description
Account ValidationMeeting Each user who is scheduling Cisco WebEx Enabled TelePresence meetings in Cisco scheduler's Cisco WebEx account. TMS, must have a host account on the WebEx site.
1.
The WebEx account username and password must be added into to each meeting schedulers user profile in Cisco TMS, along with the WebEx site they will use for scheduling. Cisco TMS validates authorized Cisco WebEx account holders. WebEx password is not required if Single-Sign-On (SSO) is configured in TMS. See Chapter 5, Configuring Cisco TelePresence Management Suite for more information.
2. Note
Bandwidth and CPU powerRecommendation for good video quality and integrating the Cisco TelePresence network with Cisco WebEx.
Network bandwidth should be at least 1.1 Mbps upstream between the MCU/TS and WebEx. For example, if you are anticipating 5 simultaneous Cisco WebEx calls, you will need to have five 1.1 Mbps bandwidth instances. Suggested CPU power (depends on running applications) is dual core CPU, 2.5 GHz memory running at least 2G.
Cisco WebEx Client Resource For detailed requirements, refer to the Cisco WebEx Enabled TelePresence release notes. RequirementsExpected resource allocation per meeting.
Document Organization
Information about configuring and using the Cisco WebEx Enabled TelePresence is provided in the following chapters:
Chapter 1, Information About the Cisco WebEx Enabled TelePresence Feature Chapter 2, First-Time Configuration Checklist Chapter 3, Configuring Cisco MCU and TelePresence Server Chapter 4, Configuring Call Control Chapter 5, Configuring Cisco TelePresence Management Suite Chapter 8, Configuring Audio Chapter 9, Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Chapter 10, Scheduling Cisco WebEx Enabled TelePresence Meetings Chapter 11, Troubleshooting
Related Documents
Related Topic
Cisco TelePresence Documentation
Document Link
Preface
Cisco TelePresence Video Communication Server (VCS) Cisco Unified Communications Manager (Unified CM) Cisco TelePresence Server Cisco TelePresence MCU
Cisco TelePresence Video Communication Server Cisco Unified Communications Manager Cisco TelePresence Server MCU 5300 Series MCU 4501 Series MCU 4500 Series MCU 4200 Series MCU MSE Series Go to your Cisco WebEx site home page. Log into your Cisco WebEx Meeting Center account and click on Support > User Guides in the left navigation pane. Refer to Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account. http://www.cisco.com/en/US/products/ps11338/products_user_guide_ list.html
Information about how to use Cisco WebEx meeting features. Specifying Cisco TelePresence Integration options and managing your Cisco WebEx Site.
Cisco WebEx Enabled TelePresence Documentation
Information for meeting organizers on how to schedule WebEx Enabled TelePresence meetings
vi
OL-21352-02
Preface
vii
Preface
viii
OL-21352-02
CH A P T E R
Contents
This chapter provides an overview of the Cisco WebEx Enabled TelePresence solution. It contains the following sections:
Cisco WebEx Enabled TelePresence Experience, page 1-1 Understanding How Cisco WebEx Enabled TelePresence is Deployed, page 1-6 Understanding Cisco WebEx Enabled TelePresence Scheduling Flow, page 1-10 Understanding Cisco WebEx Enabled TelePresence Call Flow, page 1-16
Scheduling the Meeting, page 1-1 Starting/Joining the Meeting, page 1-2 Cisco TelePresence Meeting Experience, page 1-2 Cisco WebEx Meeting Experience, page 1-2
1-1
At the scheduled start time of the meeting, the MCU/TelePresence Server calls into WebEx.
If the WebEx host has not joined the meeting, the MCU/TelePresence Server becomes the
WebEx host.
endpoint.
If meeting was scheduled using One-Button-to-Push (OBTP), participants using endpoints that
support OBTP press the button on their endpoint to join the meeting.
Participants using endpoints that dont support either Auto Connect or OBTP, join the meeting
WebEx Participants join the meeting using the link in the meeting invitation.
1-2
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Cisco WebEx Enabled TelePresence Experience
When the first WebEx participant joins, TelePresence systems appears in the list of WebEx participants (Figure 1-1 on page 1-4) and in the row of WebEx participants in Full Screen vview (Figure 1-2 on page 1-5). This indicates that it is a Cisco WebEx Enabled TelePresence meeting. individual TelePresence users are not listed in the WebEx participants list. Instead, only TelePresence systems is listed and is displayed in the active speaker window when a TelePresence participant is the active speaker. For Cisco WebEx participants to share their presentation with TelePresence participants, they must do the following:
1. 2. 3.
Log into the Cisco WebEx Web client on their laptops. Grab the ball or be designated as presenter by the WebEx host. Start application or desktop sharing.
* For a list supported mobile clients, refer to the Cisco WebEx Enabled TelePresence release notes.
Default View
When you log in to the meeting, the WebEx client displays the default view (see Figure 1-1). The default view displays a video window and participant list on the right and the presentation being shared on the left. The video window shows the current active speaker (either TelePresence or Webex).
1-3
Figure 1-1
Cisco TelePresence Server or MCU can be configured to display other TelePresence participants in the active speaker window. See Figure 1-3 for an example of Active Presence enabled by default on the TelePresence Server. MCU sends a full screen layout.
1-4
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Cisco WebEx Enabled TelePresence Experience
Figure 1-2
1-5
Figure 1-3
Cisco WebEx Meeting - Full Screen View with Cisco TelePresence Server in Active Presence Mode
SIP Video, Presentation and Audio, page 1-6 SIP Video, Presentation and PSTN Audio, page 1-7:
Using a gateway registered to Unified CM Using a gateway registered to Cisco VCS Control
1-6
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding How Cisco WebEx Enabled TelePresence is Deployed
Figure 1-4
Using a PSTN gateway registered to Unified CM - See Figure 1-5. Using a PSTN gateway registered to VCS - See Figure 1-6.
Note
1-7
Figure 1-5
Network Topology - SIP Video and Presentation with PSTN Audio Using Unified CM
Figure 1-6
Network Topology - SIP Video and Presentation with PSTN Audio Using VCS Control
1-8
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding How Cisco WebEx Enabled TelePresence is Deployed
Note
The WebEx site can be provisioned so that any WebEx attendee can grab the ball to present without the host passing them the ball or using the host key.
1-9
Scheduling with the Cisco WebEx and TelePresence Integration to Outlook, page 1-11 Scheduling with the Cisco Smart Scheduler, page 1-13 Scheduling with the Cisco WebEx Scheduling Mailbox, page 1-15
Note
Multiple deployments are possible at the same time. For example, when using Smart Scheduler, if Microsoft Exchange is deployed, the calendar of any rooms booked for a meeting is updated with the meeting details.
1-10
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Scheduling Flow
Table 1-1
1-11
Step # 1
Description User books meeting with Cisco WebEx and TelePresence Integration to Outlook.
Adds users Adds rooms Meeting request is sent to WebEx and books the WebEx portion of meeting. Date and time of meeting Meeting subject Audio dial-in information
If TSP audio, then the audio will contain additional info for the MCU to dial
SIP video and audio (if SIP audio) dial-in information for the bridge to dial into WebEx Meeting URL for participants to click
3 4 5 6 7 8 9
Cisco WebEx and TelePresence Integration to Outlook contacts TMSXE and does a booking request which includes the WebEx info from step 2. TMSXE sends a booking request with the same information to TMS. TMS confirms the meeting and returns the meeting details to TMSXE. TMSXE sends the meeting confirmation to the Cisco WebEx and TelePresence Integration to Outlook. Outlook invitation is sent back to Exchange to book the rooms and to also any added participants. TMSXE monitors the room mailbox to make sure the rooms accept the meeting. If user invited TelePresence rooms, TMS One-Button-to-Push information is sent to the TelePresence endpoints.
1-12
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Scheduling Flow
Table 1-2
Step # 1
Adds rooms Adds WebEx Clicks Save. TMSPE sends a booking request to TMS. TMS sends booking request to WebEx. WebEx books WebEx portion of meeting.
2 3
1-13
Step # 4
Description WebEx sends meeting details in response to the booking request from TMS:
SIP video and audio (if SIP audio) dial-in information for the bridge to dial into WebEx Meeting URL for participants to click
5 6 7 8
TMS responds to TMSPE with booking confirmation information. TMS sends confirmation email to user. User sends meeting invitation with meeting details to invitees. If user invited TelePresence rooms, TMS sends One-Button-to-Push information to the TelePresence endpoints.
1-14
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Scheduling Flow
1-15
Table 1-3
Step # 1
Adds rooms Adds WebEx Scheduling Mailbox (e.g. [email protected]) Adds participants Clicks Send Meeting request is sent to Exchange.
2 3 4 5
TMSXE monitors mailboxes for the rooms and the WebEx Scheduling Mailbox. TMSXE communicates with the booking API on TMS to request a WebEx Enabled meeting. TMS requests WebEx to book the WebEx portion of the meeting. WebEx sends meeting details in response to the booking request from TMS:
SIP video and audio (if SIP audio) dial-in information for the bridge to dial into WebEx Meeting URL for participants to click.
6 7 8
TMS responds to TMSXE with booking confirmation information. TMSXE sends email confirmation to meeting organizer. If user invited TelePresence rooms, TMS sends One-Button-to-Push information to the TelePresence endpoints.
SIP Audio Call Flow, page 1-17 TSP Audio Call Flow with API Command to Unlock Waiting Room, page 1-19 TSP Audio Call Flow with Waiting Room and MCU as Host, page 1-20 WebEx Audio (PSTN) Call Flow, page 1-22
1-16
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Call Flow
1-17
Table 1-4
Step # 1 2 3 4 5
Description MCU calls WebEx using SIP URI and the call is routed through VCS Control VCS control sends call to VCS-E through the traversal zone. VCS Expressway does a DNS lookup for example.webex.com. DNS resolves example.webex.com to the CUSP servers. VCS Expressway sends call to CUSP. This step is always encrypted (mandatory) (encryption is optional on previous steps). - VCS Expressway and the CUSP server verify each other's certificates. CUSP forwards the call to VCS Expressway inside the WebEx dmz. - This leg is encrypted also (mandatory). Media is connected. - Media is encrypted between the two VCS Expressways (across the Internet) - It's optional whether it's encrypted between the MCU and the VCS Expressway in the customer's site.
6 7
1-18
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Call Flow
TSP Audio Call Flow with API Command to Unlock Waiting Room
Figure 1-11 TSP Audio Call Flow with API Command to Unlock Waiting Room
Table 1-5
TSP Audio Call Flow with API Command to Unlock Waiting Room Steps
Step # 1 2a 2b 3a
Description TMS starts the conference on MCU, providing it with the SIP URI, telephone number (if using PSTN audio) and DTMF String (if using PSTN audio) to dial into WebEx MCU dials WebEx via SIP. (refer to Figure 1-10 for details). At the same time as step 2a, MCU dials PTSN call-in number for WebEx. WebEx notifies TSP provider using API command to start the audio conference, and as part of that, Webex tells the TSP provider that the conference type = telepresence and that it should unlock the waiting room. At the same time as step 3a, TSP provider prompts the MCU for the meeting access number.
3b
1-19
Step # 4a 4b 5 6
Description TSP provider unlocks waiting room, in response to step 3a. At the same time as step 4a, MCU sends DTMF tones it was prompted for in step 3b to TSP. TSP provider receives the DTMF tones. TSP provider places MCU into the audio conference.
TSP Audio Call Flow with Waiting Room and MCU as Host
Figure 1-12 TSP Audio Call Flow with Waiting Room and MCU as Host
1-20
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Call Flow
Table 1-6
TSP Audio Call Flow with Waiting Room and MCU as Host Steps
Step # 1 2a 2b 3 4 5 6
Description TMS starts conference on MCU, providing it with the SIP URI, telephone# (if using PSTN audio) and DTMF String (if using PSTN audio) to dial into WebEx MCU dials webex via SIP. (refer to Figure 1-10 for details). At the same time as step 2a, MCU dials PTSN call-in number for WebEx. TSP provider prompts the MCU for the meeting access number and host key. MCU sends DTMF tones and host key it was prompted for in step 3. TSP provider receives the DTMF tones. TSP provider unlocks the waiting room and places the MCU into the audio conference.
1-21
Table 1-7
Step # 1 2a 2b 3 4
Description TMS starts conference on MCU, providing it with the SIP URI, telephone number and DTMF string to dial into WebEx. MCU dials WebEx via SIP. (refer back to Figure 1-10 for details). At the same time as step 2a, MCU dials PSTN call-in number for WebEx. WebEx prompts the MCU for the meeting access number. MCU sends DTMF tones it was prompted for in step 3 to TSP.
1-22
OL-21352-02
Chapter 1
Information About the Cisco WebEx Enabled TelePresence Feature Understanding Cisco WebEx Enabled TelePresence Call Flow
Step # 5 6
Description WebEx receives the DTMF tones. WebEx places the MCU into the audio conference.
1-23
1-24
OL-21352-02
CH A P T E R
Contents
This chapter describes items and configuration tasks required to deploy Cisco WebEx Enabled TelePresence. It contains the following sections:
Server and Site Access Checklist, page 2-1 Configuration Task Checklist, page 2-3
Description and Source URL for the Cisco WebEx site. SourceProvided by the Cisco WebEx Account Team. Examplehttps://example.webex.com/example Detailed InstructionsConfiguring Cisco TelePresence Management Suite.
Hostname of WebEx site used by the customer. SourceProvided by the Cisco WebEx Account Team. Exampleexample.webex.com Detailed InstructionsConfiguring Cisco TelePresence Management Suite
2-1
Table 2-1
Description and Source Your unique address for accessing the Cisco WebEx Site Administration interface where you complete your initial Cisco WebEx setup configuration and manage and maintain your account after initial setup. This URL takes you directly to the WebEx Administration site. SourceProvided by the Cisco WebEx Account Team. Examplehttps://example.webex.com/admin Detailed Instructions Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
Cisco WebEx Site Administrator account username. SourceProvided by the Cisco WebEx Account Team. ExamplewebexAdmin Detailed Instructions Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
(Optional) Certificate pair, including public Used to authenticate Cisco TMS to the WebEx cloud for meetings certificate and private key from TMS. booked by users with WebEx accounts when Single Sign On (SSO) is enabled on TMS. When SSO is configured and a user schedules a WebEx-enabled meeting, the WebEx username in their Cisco TMS user profile is passed to the WebEx site to complete the booking. Detailed Instructions Configuring Single Sign On in Cisco TMS Client/server certificate for VCS Expressway. Because the call leg between the VCS Expressway and the WebEx cloud must be encrypted, a valid client/server certificate is required for the SSL handshake to occur so that secure signaling and media can take place. Detailed Instructions Creating a New DNS Zone on VCS Expressway for WebEx (step 3)
2-2
OL-21352-02
Chapter 2
Conference bridges:
Cisco MCU, page 2-3 Cisco TelePresence Server, page 2-4
2.
Call control:
Cisco Video Communications Server, page 2-4 Cisco Unified Communications Manager, page 2-4
3.
Scheduling:
Cisco TelePresence Management Suite, page 2-6
4.
Audio:
Configure Audio for Cisco WebEx Enabled TelePresence, page 2-7
5.
WebEx site:
Cisco WebEx Site Administration, page 2-7
Cisco MCU
Table 2-2 Checklist Configuring Cisco WebEx Enabled TelePresence on the MCU for the First Time
Detailed Instructions SIP, page 3-2 Content Mode, page 3-2 Video and Audio Codecs, page 3-2 Automatic Content Handover, page 3-3 Recommended Settings for MCU, page 3-3
Configure SIP Configure the Content Mode. Configure the Video and Audio Codecs. Configure the Automatic Content Handover. Configure Optional Recommended Settings:
Automatically Make Content Channel Important Outgoing Transcoded Codec Adaptive Gain Control Join and Leave Audio Notifications Encryption
2-3
Detailed Instructions SIP, page 3-6 Locally Managed Mode, page 3-6 Automatic Content Handover, page 3-6 Display Setting, page 3-7
Configure SIP Configure Locally Managed Mode Configure the Automatic Content Handover. Configure Optional Recommended Setting:
Display Setting
Detailed Instructions Creating a New DNS Zone on VCS Expressway for WebEx, page 4-2
Create a new DNS zone Set up a search rule for the WebEx domain Configure a valid Client/Server Certificate Turn on TLS Verify mode and enter TLS verify subject name. Configuring Traversal Zones for MCUs with Encryption Enabled, page 4-4
Step 2 Step 3
(If deploying with Unified CM) Configure a SIP Configuring a SIP Trunk Between Unified CM and VCS trunk between Unified CM and VCS Control. Control, page 4-5
2-4
OL-21352-02
Chapter 2
Detailed Instructions Configuring a SIP Trunk Between Unified CM and VCS Control, page 4-5
2-5
Detailed Instructions Configuring the Cisco WebEx Feature in Cisco TMS, page 5-2 Configuring WebEx Users in Cisco TMS, page 5-4 Configuring Hybrid Content Mode for MCU in Cisco TMS, page 5-7
Enable the WebEx feature in Cisco TMS. Configure WebEx users in Cisco TMS. Configure Hybrid Content Mode for MCU in Cisco TMS.
2-6
OL-21352-02
Chapter 2
Detailed Instructions
Configuring SIP Audio for Cisco WebEx Enabled Configuring SIP Audio for Cisco WebEx Enabled TelePresence, page 8-2 TelePresence:
Configure the WebEx Site in Cisco TMS to Use SIP Audio. Enable Hybrid Mode on the WebEx Site Configuring PSTN Audio for Cisco WebEx Enabled TelePresence, page 8-3
Step 2
Configure the WebEx Site in Cisco TMS to Use PSTN Audio Enable Hybrid Mode on the WebEx Site (Optional) Configure PSTN Calls to Pass Through a PSTN gateway to WebEx
Go to: Chapter 9, Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Required Task
Step 1 Step 2
Detailed Instructions Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
Enable Cisco TelePresence Integration (MC only). (Recommended) Enable TelePresence options:
List TelePresence on calendar Send invitation email to meeting host Display toll-free number to attendees
Step 3 Step 4
Set the Cisco TelePresence VOIP and video connection. Select the Cisco TelePresence PRO: Meeting Center TelePresence Session Type. Assigning the Meeting Center TelePresence Session Type
2-7
2-8
OL-21352-02
CH A P T E R
You must be running MCU software release 4.4 or a later or TelePresence Server 3.0 or later to use Cisco WebEx Enabled TelePresence features.
Contents
This chapter describes how to configure MCU and TelePresence Server for Cisco WebEx Enabled TelePresence meetings. It contains the following sections:
Required Settings for MCU, page 3-2 Recommended Settings for MCU, page 3-3 Required Settings for TelePresence Server, page 3-5 Recommended Settings for TelePresence Server, page 3-7
Introduction
This chapter describes specific settings on both MCU and TelePresence Server that are required or recommended for use with Cisco WebEx Enabled TelePresence meetings. In terms of deployment, both MCU and TelePresence Server must be registered to VCS directly and cannot be trunked to Unified CM. In terms of user experience, the active speaker from TelePresence to MCU or TelePresence Server is shown to WebEx users and the active speaker from WebEx to MCU or TelePresence Server is shown to TelePresence. TelePresence Server, by default, using a feature called ActivePresence, displays a full screen view of the active speaker and up to nine additional TelePresence participants in a row at the bottom of the screen. MCU, by default displays a full screen view of the active speaker. For more information about the screen layout options available, refer to the TelePresence Server and MCU documentation.
3-1
SIP, page 3-2 Content Mode, page 3-2 Video and Audio Codecs, page 3-2 Automatic Content Handover, page 3-3
For more information about MCU software, refer to the following link: http://www.cisco.com/en/US/products/ps12283/prod_release_notes_list.html
SIP
MCU calls to WebEx support SIP only. Make sure SIP is configured correctly on MCU. The call leg between MCU/TS, VCS Control, VCS Expressway and the WebEx cloud cannot be interworked.
Note
Content Mode
In Hybrid mode, the incoming content stream is passed through, giving the best possible quality to HD endpoints and it is also decoded and used to create a second, lower resolution stream for anyone who cannot receive the passthrough stream (SD endpoints). This uses up a video port but ensures that users get the advantages both of transcoding and passthrough. If content mode is set to Passthrough, a single video stream is sent to everyone in the meeting. If all participants are HD endpoints, they receive the best possible quality. However, if one or more participants can only receive SD video, then all participants receive SD video. Though Content Mode can be set on the MCU, Cisco recommends customers to set it using TMS. To configure hybrid content mode for MCU in TMS, refer to: Configuring Hybrid Content Mode for MCU in Cisco TMS, page 5-7.
Log into the MCU. Click Settings. The Settings page appears with the Conferences tab displayed. In the Advanced Settings section make sure H.264 is checked for the following:
3-2
OL-21352-02
Chapter 3
Configuring Cisco MCU and TelePresence Server Recommended Settings for MCU
Step 5
Video codecs to MCU Audio codecs from MCU Audio codecs to MCU
In the Advanced Settings section make sure G.711 is checked for the following:
Step 6
Log into the MCU. Click Settings. The Settings page appears with the Conferences tab displayed. Click the Content tab. For Automatic content handover, select Enabled. At the bottom of the page, click Apply changes.
Automatically Make Content Channel Important, page 3-3 Outgoing Transcoded Codec, page 3-4 Adaptive Gain Control, page 3-4 Join and Leave Audio Notifications, page 3-5 Encryption, page 3-5
3-3
Step 2
Click Settings. The Settings page appears with the Conferences tab displayed. In the Advanced Settings section, check Automatically make content channel important. At the bottom of the page, click Apply changes.
Step 3 Step 4
Log into the MCU. Click Conferences at the top of the page. The Conferences page appears with the Conference list tab displayed. Click the Templates tab. The Conference Templates page appears. Click the link for Top level. The Top level template configuration page appears. In the Content section, using the Outgoing transcoded codec menu, select H.264. At the bottom of the page, click Apply changes.
Step 3
Step 4
Step 5 Step 6
Log into the MCU. Click Conferences at the top of the page. The Conferences page appears with the Conference list tab displayed. Click the Templates tab. The Conference Templates page appears. Click the link for Top level. The Top level template configuration page appears. In the Parameters section, using the Adaptive Gain Control on join menu, select Enabled. At the bottom of the page, click Apply changes.
Step 3
Step 4
Step 5 Step 6
3-4
OL-21352-02
Chapter 3
Configuring Cisco MCU and TelePresence Server Required Settings for TelePresence Server
Log into the MCU. Click Settings. The Settings page appears with the Conferences tab displayed. In the Conference Settings section, for Audio Notifications, uncheck Join and leave indications. At the bottom of the page, click Apply changes.
Step 3 Step 4
Encryption
Cisco recommends that on MCUs with an encryption key, that the conference settings are configured to optionally encrypt the media. If encryption is set to require encryption of all media, then the main and content video sent to WebEx will be merged into a single stream and treated as a participant. To set encryption to optional, do the following:
Step 1 Step 2
Log into the MCU. Click Conferences at the top of the page. The Conferences page appears with the Conference list tab displayed. Click the Templates tab. The Conference Templates page appears. Click the link for Top level. The Top level template configuration page appears. In the Parameters section, using the Encryption menu, select Optional. At the bottom of the page, click Apply changes.
Step 3
Step 4
Step 5 Step 6
3-5
Locally Managed Mode, page 3-6 Automatic Content Handover, page 3-6
For more information about TS software, refer to the following link: http://www.cisco.com/en/US/products/ps11339/prod_release_notes_list.html
SIP
TelePresence Server calls to WebEx support SIP only. Make sure SIP is configured correctly on TelePresence Server.
Note
Refer to the TelePresence Server help for more information on how to configure SIP.
Log into the TelePresence Server. Go to Configuration > Operation mode. The Operation mode page appears. Using the Operation mode menu, select Locally managed. At the bottom of the page, click Apply changes.
Step 3 Step 4
Log into the TelePresence Server. Go to Configuration > System Settings. The System Settings page appears. Make sure Automatic content handover is checked. At the bottom of the page, click Apply changes.
Step 3 Step 4
3-6
OL-21352-02
Chapter 3
Configuring Cisco MCU and TelePresence Server Recommended Settings for TelePresence Server
Display Setting
Cisco recommends the display setting in TelePresence Server to be set to full screen, so that Webex video can be shown full size on a multiscreen endpoint. To enable full screen display in TelePresence Server, do the following:
Step 1 Step 2 Step 3 Step 4
Log into TelePresence Server. Go to Configuration > Default Endpoint Settings. In the Display section, for Full screen view of single-screen endpoints, select Allowed. At the bottom of the page, click Apply changes.
3-7
3-8
OL-21352-02
CH A P T E R
Introduction
This chapter describes how to configure call control for Cisco WebEx Enabled TelePresence meetings. To begin using Cisco WebEx Enabled TelePresence, you must configure the call control product(s) used in your video network. There are three possible call control scenarios:
Cisco TelePresence VCS Control and Expressway Endpoints are registered to VCS Control and/or Expressway only. Cisco Unified CM with VCS Control and Expressway Endpoints are registered to Unified CM only. Cisco TelePresence VCS Control and Expressway with Unified CM Endpoints are registered to VCS Control/Expressway and Unified CM.
Note
Using Unified CM as the call control solution requires VCS Control and Expressway to be deployed in order to communicate with WebEx, regardless of whether endpoints are registered to VCS Control and Expressway or not.
Prerequisites, page 4-2 Creating a New DNS Zone on VCS Expressway for WebEx, page 4-2 Configuring Traversal Zones for MCUs with Encryption Enabled, page 4-4
4-1
Chapter 4 Configuring Cisco TelePresence Video Communication Server Control and Expressway
Prerequisites
To configure WebEx in Cisco TelePresence VCS, the following are required:
Cisco TelePresence Video Communication Server (VCS) must be running firmware X7.2.2 or a later release. Endpoints in the network are registered to VCS Control or Expressway Conferencing Bridge(s) to be used (MCU or TelePresence Server) are already operational within the network VCS Control is in the private network VCS Expressway is in the DMZ and has access to the Internet Set zones and pipes appropriately (according to your networks requirements) to allow a minimum of 1.1 Mbps for WebEx calls. For more information about bandwidth controls, please refer to the Cisco VCS Administrator Guide at: http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/admin_guide/Cisco_VCS_Admi nistrator_Guide_X7-2.pdf
VCS Control is configured as the SIP Registrar/H.323 gatekeeper. In order for Cisco WebEx Enabled TelePresence to work, it is required to set up a VCS Control as a SIP registrar, enabling it to register SIP devices and route calls to them. VCS Control has the capability to be both an H.323 gatekeeper and a SIP registrar. Configuring VCS as a SIP registrar is done by configuring one or more SIP domains. The VCS will act as a SIP Registrar and Presence Server for these domains, and will accept registration requests for any SIP endpoints attempting to register with an alias that includes these domains. For details on how to configure SIP domains in VCS Control, refer to the Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Deployment Guide at: https://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basi c_Configuration_Cisco_VCS_Control_with_Cisco_VCS_Expressway_Deployment_Guide_X7-2. pdf
Intercompany TelePresence participants: If you want to allow participants from another company to be able to join via TelePresence, you must have a valid SIP SRV (secure SIP), non-secure SIP SRV or multiple SIP and H323 SRV records in place that resolve to the VCS Expressway for your configured SIP Domain so TelePresence participants can route to your VCS Expressway.
4-2
OL-21352-02
Chapter 4
Configuring Call Control Configuring Cisco TelePresence Video Communication Server Control and Expressway
b. c. d. e. Step 2
Set SIP Media encryption mode to Force encrypted. Turn on TLS Verify mode. In the TLS verify subject name field, enter sip.webex.com. Click Create Zone.
Set up a search rule with a higher priority than the search rule for the existing DNS zone (lower number priority) for the domain of WebEx. The following configuration is required:
Protocol: SIP Source: <Admin Defined>, default: Any Mode: Alias Pattern Match Pattern Type: Regex Pattern String: (.*)@(.*)(\.webex\.com).* Pattern Behavior: Replace Replace String: \1@\2\3 On Successful Match: Stop Target: <DNS Zone Created for WebEx> State: Enabled
For details on how to create and set up search rules for a DNS zone, refer to the Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Deployment Guide at: https://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_C onfiguration_Cisco_VCS_Control_with_Cisco_VCS_Expressway_Deployment_Guide_X7-1.pdf.
Step 3
Configure a valid Client/Server Certificate for your company. Typically the CName of the certificate is the routable domain to your companys VCS Expressway. It must be a certificate name agreed upon by WebEx, because they will be checking it. WebEx supports certificates issued by common certificate authorities. For more information, contact WebEx. For details on how to configure a client/server certificate, refer to the Certificate creation and use with Cisco VCS Deployment Guide at the following location: https://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Certifica te_Creation_and_Use_Deployment_Guide_X7-2.pdf
4-3
Go to Maintenance > Certificate Management > Trusted CA certificate. Click Show CA certificate. Select and copy the contents of the CA certificate, paste it into a new text file and save it. Open the CA certificate text file you just created and look for the root CA that issued your certificates. If it is not in the CA certificate text file, open the root CA certificate in a text editor, copy and paste its contents into the CA certificate text file. Open the intermediate CA certificate in a text editor, copy and paste it into the CA certificate text file and save the CA certificate text file. On the Trusted CA certificate page in VCS Expressway, click Upload CA certificate, select and upload the CA certificate text file.
Step 5 Step 6
Caution
If you choose not to do the following configuration, MCUs with encryption enabled will deliver the presentation content in the main video channel, instead of a separate stream. To support MCUs that have encryption enabled, do the following
Step 1
Set up a new traversal client zone from VCS Control to VCS Expressway
Make sure the new zone uses a different port number. On VCS Expressway, set up a new traversal server zone that connects to the VCS Control traversal zone set up in the previous step. In this new VCS Expressway traversal server zone, set media encryption to Force unencrypted. On VCS Control set up a search rule (at higher priority than the search rule that uses the default traversal zone) that matches WebEx traffic e.g. match = .*@example.webex.com
Note
The above configuration ensures that whether the MCU encryption is enabled or not, that the video and the presentation stay on separate channels. It also ensures the content from WebEx is not encrypted when sent to the MCU (even though it is encrypted across the internet).
4-4
OL-21352-02
Chapter 4
Prerequisites, page 4-5 Configuring a SIP Trunk Between Unified CM and VCS Control, page 4-5
Prerequisites
To configure WebEx in Cisco Unified Communications Manager (Unified CM), the following are required:
Cisco Unified CM 8.6.2 or 9.1.1. Endpoints in the network are registered to Unified CM Conferencing Bridge(s) to be used (MCU or TelePresence Server) are already operational within the network and registered to VCS VCS Control is deployed in the private network To ensure optimum SIP audio and video connectivity between MCU and TelePresence Server and the WebEx cloud, it is recommended to set region to permit a minimum of 1.3 Mbps. VCS expressway configured with the DNS zone.
4-5
4-6
OL-21352-02
CH A P T E R
Contents
This chapter describes how to configure Cisco TelePresence Management Suite (Cisco TMS) for Cisco WebEx Enabled TelePresence meetings. It contains the following sections:
Prerequisites, page 5-1 Configuring the Cisco WebEx Feature in Cisco TMS, page 5-2 Configuring WebEx Users in Cisco TMS, page 5-4 Configuring Hybrid Content Mode for MCU in Cisco TMS, page 5-7 Configuring Conference Settings in Cisco TMS, page 5-8 Configuring Single Sign On in Cisco TMS, page 5-8 Supported Configurations for TMS to Schedule on Behalf of the WebEx Host, page 5-15
Prerequisites
Cisco TMS software release 14.2 or later is required. Cisco TMSXE software release 3.1 or later is required, if using Microsoft Outlook to schedule meetings. There are two options for scheduling using Microsoft Outlook:
Using the WebEx Productivity Tools Plug-In for Microsoft Outlook Using WebEx Scheduling Mailbox
Cisco TMSPE software release 1.1 or later is required, if using Smart Scheduler to schedule meetings The WebEx integration option key must be installed on Cisco TMS before configuring the WebEx feature. MCU calls to WebEx support SIP only. The following settings must be configured for SIP:
5-1
In Cisco TMS: Allow Incoming and Outgoing SIP URI Dialing must be set to Yes in the Cisco
TMS Scheduling Settings for each MCU used for Cisco WebEx Enabled TelePresence meetings.
For MCU and TelePresence Server, refer to the Configuring Cisco TelePresence Management
Go to Administrative Tools > Configuration > WebEx Settings. The WebEx Settings page appears. See Figure 5-1.
Figure 5-1 Enabling WebEx in Cisco TMS
Step 2
Click Add Site. The WebEx Site Configuration page appears. See Figure 5-2.
5-2
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring the Cisco WebEx Feature in Cisco TMS
Figure 5-2
Step 3 Step 4
In the Host Name field, enter the hostname for the WebEx site. In the Site Name field, create a name for the WebEx site.
Note
The site name must follow the WebEx site URL like this: https://[HostName]/[SiteName]. For example: https://example.webex.com/example.
Step 5
For WebEx Participant Bandwidth, select the maximum bandwidth per meeting to allow from MCU to WebEx.
Note Step 6
(Optional) Default Site. If one or more WebEx sites already exist, you can designate the site as the default WebEx site, by selecting Yes.
Note
New users are automatically set to use the default site the first time they schedule a meeting with WebEx.
Step 7
For TSP Audio, select Yes if you are going to use TSP or PSTN audio.
If Yes is selected for TSP Audio, Cisco TMS will only use TSP audio. SIP audio will not work.
5-3
b. Step 10
Click Save.
Local accounts on the Windows Server where Cisco TMS is installed Accounts the server trusts through domain membership and Active Directory (AD)
For each user that successfully logs into Cisco TMS, a new user profile is created based on their username and the user is prompted to enter information into their profile. Existing Windows or AD user passwords are used but they are not stored in Cisco TMS. If a users Windows/AD password changes, they must use that updated password when logging into Cisco TMS.
WebEx username WebEx password (unless single sign on is enabled) The WebEx site on which they have an account.
Note
This WebEx site must also be added to Cisco TMS, as described in Configuring the Cisco WebEx Feature in Cisco TMS, page 5-2.
There are three ways to enable a Cisco TMS users account for WebEx scheduling:
Administrator edits the Cisco TMS users profile. For details, see Configuring a Cisco WebEx Enabled TelePresence User in Cisco TMS, page 5-6 The Cisco TMS user edits their profile by logging in to Cisco TMS and clicking their username at the bottom left corner of the Cisco TMS Web UI. Administrator enables Lookup User Information from Active Directory, Get WebEx Username from Active Directory and (optionally) Single Sign On (SSO). The benefits of having the Active Directory lookup features enabled are that the user account information including WebEx username is automatically added to each new Cisco TMS user. WebEx password must still be added by the administrator or user, however, if Single Sign On is enabled, WebEx password is not required. With the Active Directory and Single Sign On features enabled, only the WebEx site must be selected for the user, if there are multiple WebEx sites configured on Cisco TMS. If there is only on WebEx site, Cisco TMS will use that site. If there are multiple sites configured, Cisco TMS will automatically select the WebEx site designated as the Default, unless the users Cisco TMS profile is edited to specify a different WebEx site.
5-4
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring WebEx Users in Cisco TMS
For details, see Configuring Automatic User Lookup from Active Directory, page 5-5 and Configuring Single Sign On in Cisco TMS, page 5-8
Go to Administrative Tools > Configuration > Network Settings. In the Active Directory pane, set Lookup User Information from Active Directory to Yes. Enter information in the remaining fields in the Active Directory pane and click Save. For information about each field, refer to the Cisco TMS Help.
Go to Administrative Tools > Configuration > WebEx Settings. In the WebEx Configuration pane, use the Get WebEx Username from Active Directory menu to select the field in AD where you are storing the WebEx username. Click Save. For more information, refer to the Cisco TMS Help.
5-5
When Single Sign On (SSO) is enabled for the WebEx site, users with WebEx accounts can book WebEx-enabled meetings with Cisco TMS without requiring their WebEx password be stored in their Cisco TMS user profile. When SSO is configured and a user schedules a meeting, their WebEx username from their Cisco TMS user profile is passed to the WebEx site to complete the booking. For information about how to configure SSO, see Configuring Single Sign On in Cisco TMS, page 5-8. The remaining fields are not mandatory, but are used for other Cisco TMS features. Later, if you are using Active Directory, you can configure Cisco TMS to populate these fields automatically for new users.
Lookup User Information from Active Directory and Get WebEx Username from Active Directory are enabled, as described in Configuring Automatic User Lookup from Active Directory, page 5-5 Single Sign On is enabled, as detailed in Configuring Single Sign On in Cisco TMS, page 5-8. The user will use the default WebEx site for scheduling WebEx meetings
To configure a Cisco WebEx Enabled TelePresence user in Cisco TMS, do the following:
Step 1 Step 2 Step 3
Go to Administrative Tools > User Administration > Users Click New to add a new user or click the name of an existing user to add WebEx scheduling capabilities to their profile and click Edit. Enter Windows/AD Username, First Name, Last Name and Email Address.
If an existing user or AD lookup is enabled, some fields will already contain information.
For WebEx Username, enter the username for the users WebEx account. For WebEx Password, enter the password for the users WebEx account. For WebEx Site, select the WebEx site to which the user is registered.
Note Step 7
If no WebEx site is selected, the WebEx site configured as the default will be used.
Make any other settings in the Cisco TMS user profile and click Save.
5-6
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring Hybrid Content Mode for MCU in Cisco TMS
If port reservations are not enabled, the meeting is booked with 5 TelePresence ports and the invite is forwarded, additional participants up to the maximum available ports at that time are able to join on TelePresence. This could cause another scheduled meeting to fail. As a result, Cisco recommend s always enabling port reservations for MCU and TS.
Go to Systems > Navigator. Select an MCU. Click the Settings tab. Click Extended Settings. Set the Limit Ports to Number of Scheduled Participants menu to On. Click Save. Repeat steps 2 through 6 for all other MCUs.
Go to Systems > Navigator. Select a TS. Click the Settings tab. Click Extended Settings. Set the Port Reservation menu to On. Click Save. Repeat steps 2 through 6 for all other TSs.
5-7
Select the MCU and click Edit system settings. From the Settings tab, click Extended Settings. For Content Mode, select Hybrid and click Save.
Go to Administrative Tools > Configuration > Conference Settings. In the Conference Connection/Ending Options section, set the following options:
For Supply Contact Information on Extend Meeting Scheduling Conflict, select Yes.
Note
Supply Contact Information on Extend Meeting Scheduling Conflict is not supported on CTS, Jabber Video, and other endpoints that do not support direct messaging from TMS. For Show In-Video Warnings About Conference Ending, select Yes.
Note
Show In-Video Warnings About Conference Ending is not currently supported on MCU 44xx, 45xx, 84xx, 85xx and TS 70xx and 87xx-series products.
Step 3
Click Save.
A TMS Site Administrator manually enters the WebEx Username in a user's profile. When an organizer schedules a meeting with WebEx using Cisco TMS, Cisco TMS sends the meeting information to the WebEx site with that WebEx username designated as the WebEx host.
5-8
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring Single Sign On in Cisco TMS
Note
When a user has selected a WebEx site that has SSO enabled in TMS, Site Administrator privileges are required to edit the WebEx Username field. Users cannot edit their WebEx Username. Enable Cisco TMS to import WebEx usernames from Active Directory (AD)
Note
You can use any field in AD. Email address and username are the most commonly used. When an organizer schedules a meeting with WebEx using Cisco TMS, Cisco TMS requests AD for the WebEx username of the meeting organizer using the username and password that the Cisco TMS administrator filled in on the Network Settings page for AD lookup. When AD supplies Cisco TMS with the WebEx username of the organizer, Cisco TMS sends the meeting information to the WebEx site with that WebEx username designated as the WebEx host.
Prerequisites
Before configuring SSO in Cisco TMS, you must work with the WebEx Cloud Services team to determine the following information that needs to be configured in both Cisco TMS and in the WebEx cloud:
Partner Name This is typically the name of your company. If you have only one WebEx site, your WebEx site can be used. This value must be determined by the WebEx team, because it must be unique among all WebEx customers. Example: examplesso.webex.com Partner Issuer (IdP ID) This is the Identity Provider, which is your TMS. Your TMS administrator works with the WebEx team to generate this value. This value can be anything as long as the same name is used both in TMS and the configuration done by the WebEx Cloud Services team. Cisco recommends using a name to indicate your companys TMS. Example: exampletms SAML Issuer (SP ID) This is the Service Provider, which is WebEx. Your TMS administrator works with the WebEx team to generate this value. Cisco recommends using the full URL of your WebEx site, but you can use anything as long as the same name is used both in TMS and in the configuration done by the WebEx Cloud Services team. The full URL of your WebEx site is determined by the WebEx team. Example: https://examplesso.webex.com/examplesso AuthnContextClassRef This is the authentication context. The IdP authenticates the user in different contexts, e.g., X509 cert, Smart card, IWA, username/password). Use the default value automatically provided by TMS.
5-9
Ensure the WebEx site on which you want to enable SSO has been created in Cisco TMS. See Configuring the Cisco WebEx Feature in Cisco TMS, page 5-2 for details. Generate a certificate to secure the connection between Cisco TMS and the WebEx site. See Generating a Certificate for WebEx, page 5-10 for details. Enable Partner Delegated Authentication on the WebEx site. See Enabling Partner Delegated Authentication on the WebEx site, page 5-13 for details. Enable SSO in Cisco TMS. See Enabling SSO in Cisco TMS, page 5-14 for details.
2.
3.
4.
Public certificate must be in PEM format - to send to the WebEx Cloud Services team Certificate and private key bundled in a PKCS12-formatted file - for upload to Cisco TMS
You can generate a new certificate or use an existing one, such as the one used to enable HTTPS on your Cisco TMS server.
Using the Windows Certificate Manager Snap-in, export the existing key/certificate pair as a PKCS#12 file. Using the Windows Certificate Manager Snap-in, export the existing certificate as a Base64 PEM encoded .CER file. Provide this .CER file to the WebEX Cloud Services team. Use the PKCS#12 file you created in step 2, to upload to TMS in Enabling SSO in Cisco TMS, page 5-14
5-10
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring Single Sign On in Cisco TMS
Use Windows Certificate Manager Snap-in to export your existing certificate in a Base64 PEM file. Provide this Base64 PEM file to the WebEx Cloud Services team. Create a PKCS#12 key/certificate pair by using the command in step 10 of Using OpenSSL to Generate a Certificate, page 5-12. Use this PKCS#12 file to upload to TMS in Enabling SSO in Cisco TMS, page 5-14.
Create a new key/certificate pair to use for the WebEx SSO configuration using OpenSSL, following the steps in Using OpenSSL to Generate a Certificate, page 5-12. Create a Base64 PEM encoded version of the signed certificate using step 8 Using OpenSSL to Generate a Certificate, page 5-12 Provide this version of the certificate to the WebEx Cloud Services team. Create a PKCS#12 key/cert pair by using the command in step 10 of Using OpenSSL to Generate a Certificate, page 5-12. Use this PKCS#12 file to upload to TMS in Enabling SSO in Cisco TMS, page 5-14.
Follow the steps in Using OpenSSL to Generate a Certificate, page 5-12. In step 6, follow the procedure to create a self-signed certificate signing request. Follow steps 7 through 9 and provide the base64 PEM file of self-signed certificate to the WebEx Cloud Services team. Follow step 10 to create a PKCS#12 PFX file Upload to TMS in Enabling SSO in Cisco TMS, page 5-14.
5-11
Generate a private key Generate a certificate signing request (CSR) Have a certificate authority sign the CSR Provided the signed certificate to the WebEx team. Convert the signed certificate and private key into a PKCS#12 formatted file Upload the converted certificate and private key to TMS
In Windows, open a command prompt. Navigate to the openssl\bin installation directory. Generate a private key using following command: openssl genrsa -out tms-privatekey.pem 2048 Generate a certificate signing request (CSR) using the private key above: openssl req -new -key tms-privatekey.pem -config openssl.cfg -out tms-certcsr.pem Enter the data requested, including:
Step 4
Step 5
Country State or province Organization name Organization unit Common name (this is the Cisco TMS FQDN) (Optional) Email address, password, company name
Step 6
Send the Cisco TMS certificate signing request file tms-certcsr.pem to be signed by a trusted certificate authority (CA) or self sign a certificate signing request using OpenSSL or Windows CA.
For details on how to submit a certificate request to a trusted certificate authority, contact that certificate authority. To self-sign a certificate signing request using OpenSSL, use the following command. tms-certcsr.pem is your certificate signing request in PEM format. tms-privatekey.pem is your private key in PEM format. days is the number of days you'd like the certificate to be valid. openssl x509 -req -days 360 -in tms-certcsr.pem -signkey tms-privatekey.pem -out tms-cert.pem The resulting tms-cert.pem is your self-signed certificate.
To self-sign a certificate signing request using Windows CA, use Windows Certificate Manager Snap-in. For details on how to submit a certificate request using Windows Certificate Manager Snap-in, refer to the documentation for Windows Certificate Manager Snap-in.
5-12
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring Single Sign On in Cisco TMS
Step 7
When your certificate authority has signed your certificate request, they send a signed certificate to you, You should receive the signed certificate tms-cert.der back from the CA. If the certificate is on an email or web page and not in its own file, copy the contents starting with the -----BEGIN CERTIFICATE----- line and through the -----END CERTIFICATE----- line. Save the contents to a text file and name the file tms-cert.der.
Step 8
Convert the signed certificate from .der to .pem using the following OpenSSL command: openssl x509 -inform der -in tms-cert.cer -out tms-cert.pem
Note
If the certificate authority provides you the signed certificate in .pem format, you can skip this step.
Step 9 Step 10
Provide this signed certificate to the WebEx Cloud Services team. Combine the signed certificate .pem with the private key created in step 3: openssl pkcs12 -export -inkey tms-privatekey.pem -in tms-cert.pem -out tms-cert-key.p12 -name tms-cert-key You should now have a Cisco TMS certificate that contains the private key for SSO configuration to upload to Cisco TMS. Before uploading this certificate to TMS, you must enable partner delegated authentication on your WebEx site. For more information, refer to Enabling Partner Delegated Authentication on the WebEx site in the next section. After enabling delegated authentication, use the combined certificate and private key you generated in step 10 above to upload to Cisco TMS in step 4 of Enabling SSO in Cisco TMS, page 5-14 to complete the SSO configuration.
Request that the WebEx Cloud Services team add a Partner Certificate for your TMS, configured for SAML 2.0 federation protocol. Provide the public certificate for your TMS to the WebEx Cloud Services team. For details on how to create a certificate, see Generating a Certificate for WebEx, page 5-10. After the WebEx Cloud Services team notifies you that this step is complete, enable partner delegated authentication for both Host and Admin accounts in the Site Administration for your WebEx site, as described below. Proceed with the section Enabling SSO in Cisco TMS.
4.
Log into your WebEx administrative site and go to Manage Site > Partner Authentication. The Partner Delegated Authentication page appears.
5-13
Figure 5-3
Step 2
In the Partner SAML Authentication Access section, make sure both Host and Site Admin are checked and click Update.
Certificate Password (if required) Partner Name Partner Issuer (IdP ID) SAML Issuer (SP ID) AuthnContextClassRef
Note
Before enabling SSO, you must enable Partner Delegated Authentication on your WebEx site. For more information, refer to Enabling Partner Delegated Authentication on the WebEx site, page 5-13. To enable SSO in Cisco TMS, do the following:
Step 1 Step 2
Log into Cisco TMS, and go to Administrative Tools > Configuration > WebEx Settings. In the WebEx Sites pane, click the site name of the WebEx site on which you want to enable SSO. The WebEx Site Configuration pane appears. For Enable SSO, select Yes. The SSO Configuration pane appears.
Step 3
5-14
OL-21352-02
Chapter 5
Configuring Cisco TelePresence Management Suite Configuring Single Sign On in Cisco TMS
Click Browse and upload the PKS #12 private key certificate (.PFX) you generated in Generating a Certificate for WebEx, page 5-10. Complete the rest of the SSO configuration fields using the password and other information that you selected when generating the certificate. Click Save.
Figure 5-4
WebEx site does not use SSO and TMS does not have SSO configured (no partner delegated authentication relationship with the WebEx site)
5-15
WebEx host login: The WebEx username and password are stored in WebEx, and the user
personal profile. This must be maintained by the user, if they have access to the TMS, or by the TMS administrator. The TMS passes both username and password to WebEx at scheduling time.
2.
WebEx site does not use SSO, but TMS does have SSO configured (partner delegated authentication relationship with the WebEx site).
WebEx host login: The WebEx username and password are stored in WebEx, and the user
task) but the WebEx password is not stored in TMS. TMS is trusted to schedule for that user.
3.
WebEx site uses SSO, and TMS has SSO configured (partner delegated authentication relationship with the WebEx site).
WebEx host login: The WebEx user logs in through the SSO identity service provider. TMS scheduling: The host's WebEx username is stored in a TMS personal profile (a TMS admin
task) but the WebEx password is not stored in TMS. TMS is trusted to schedule for that user.
5-16
OL-21352-02
CH A P T E R
Contents
This chapter describes how to configure Cisco TelePresence Management Suite Extension for Microsoft Exchange (Cisco TMSXE) for scheduling of Cisco WebEx Enabled TelePresence meetings using the WebEx and TelePresence Integration to Outlook and WebEx Scheduling Mailbox. It contains the following sections:
Prerequisites, page 6-1 Deployment Best Practices, page 6-2 Scheduling Options with TMSXE, page 6-2 Configuring Cisco TMSXE for the WebEx and TelePresence Integration to Outlook, page 6-2 Configuring Cisco TMSXE for the WebEx Scheduling Mailbox, page 6-6
Prerequisites
Cisco TMSXE software release 3.1 or later is required. Cisco TMS software release 14.2 or later is required. Endpoints that are available as mailboxes for booking in a Cisco WebEx Enabled TelePresence meeting must be set to AutoAccept in Exchange. If a meeting organizer is scheduling a meeting in a different domain than the domain in which the TMSXE is hosted, The domain in which the TMSXE resides must be added to the list of sites in the Local intranet' zone on the meeting organizers computer, so that it trusts the TMSXE server. If the TMSXE is hosted in a domain that is outside of the domain of many or all users, this can be done most efficiently by your companys IT group for all users via a group policy or logon script. If this is not done, each time a user tries to schedule a meeting, they will be required to enter their TMSXE username and password.
6-1
A signed certificate that is trusted in the organization is required for TMSXE. To do this, you must generate a certificate signing request (CSR) from IIS to provide to the certificate authority (CA). The certificate can be a self-signed certificate or come from a trusted internal certificate authority or public certificate authority.
The server must have a minimum of 4GB RAM. A maximum of 50 telepresence endpoints are available for booking in Cisco TMS and Cisco TMSXE. For details on installation and configuration of TMSXE, refer to the Cisco TelePresence Management Suite Extension for Microsoft Exchange Installation Guide - Version 3.1
You add WebEx to your meeting using WebEx Meeting Options panel in Microsoft Outlook.
Using WebEx Scheduling Mailbox
You add WebEx to your meeting invitation directly from your email client by including a special invitee; the WebEx mailbox.
Configuring Cisco TMSXE for the WebEx and TelePresence Integration to Outlook
To configure Cisco TMSXE for scheduling using the WebEx and TelePresence Integration to Outlook, you must perform the following tasks:
Install the Cisco TMS Booking Service Set up communication between your WebEx site and TMSXE
6-2
OL-21352-02
Chapter 6
Configuring Cisco TelePresence Management Suite Extension for Microsoft Exchange Configuring Cisco TMSXE for the WebEx and TelePresence Integration to Outlook
On the Cisco TMSXE server, go to the Control Panel. Right-click Cisco TelePresence Management Suite Extension for Microsoft Exchange and select Change. This starts the installer and allows you to change your installation. Follow all instructions provided by the installer and opt to include Cisco TMS Booking Service.
Step 3
Note
Open the Server Manager console (Start > All Programs > Administrative Tools > Server Manager). In the Role View, select IIS Manager (Server Manager > Roles > Web Server > IIS Manger ). Double-click Server Certificates. In the Actions pane on the right, click Create Certificate Request. (Important) In the Common Name: field, enter the Fully Qualified Domain Name (FQDN) of the DNS name which users will type into the address bar in their browser to reach your website (site.cisco.com NOT site). If you have a different physical hostname than what users will type into their browsers to get to your site, make sure to put in the name users will use. In the Organization field, type your organization name. In the Organizational Unit field, type the name of your organization and click Next. In the City/locality field, type the city where the server resides and click Next. In the State/province field, type the state where the server resides. In the Country/Region field, select US (United States) and click Next. Leave the CSP at the default value. For the Bit Length, select 2048. Enter (or Browse to) a filename to save the certificate request (CSR), click Finish. Copy and paste the entire contents of the CSR file you just saved.
6-3
Chapter 6 Configuring Cisco TelePresence Management Suite Extension for Microsoft Exchange Configuring Cisco TMSXE for the WebEx and TelePresence Integration to Outlook
Provide the CSR file to your CA and wait for them to send a signed certificate back to you.
Double-click the Root CA certificate file and click Install Certificate. Click Next, place the radio button in Place all certificates in the following store and then click Browse. Place a check in Show Physical Stores. Expand the Trusted Root Certification Authorities folder, select the Local Computer folder, and click OK. Click Next and then Finish. You will receive the message: The import was successful".
Double-click the Intermediate CA certificate file and click Install Certificate. Click Next, place the radio button in Place all certificates in the following store and then click Browse. Place a check in Show Physical Stores. Expand the Intermediate Certification Authorities folder, select the Local Computer folder, and click OK. Click Next and then Finish. You will receive the message: "The import was successful".
Double-click the Intermediate CA certificate file and click Install Certificate. Click Next, place the radio button in Place all certificates in the following store and then click Browse. Place a check in Show Physical Stores. Expand the Intermediate Certification Authorities folder, select the Local Computer folder, and click OK. Click Next and then Finish. You will receive the message: "The import was successful".
In the IIS Manager console, go to the Server Certificates action pane, and click Complete Certificate Request. The Complete Certificate Request Wizard appears. Browse to the location where you saved your SSL server certificate, select it, then click Open. Enter a friendly name for your certificate (use the certificate's hostname if you're unsure). Then click OK.
6-4
OL-21352-02
Chapter 6
Configuring Cisco TelePresence Management Suite Extension for Microsoft Exchange Configuring Cisco TMSXE for the WebEx and TelePresence Integration to Outlook
Select your IIS Site. In the action pane on the right, under Edit Site, click Bindings. Click the Add button. In the Type dropdown, select https. In the SSL certificate dropdown, select your SSL certificate. Click OK.
To display the Select Attendees and Resources Address Book window, click the To... button in the Meeting window.
Select Attendees and Resources - Address Book
Figure 6-1
To display the Add Telepresence Rooms window, click the Add Telepresence Rooms button the Meeting Options pane.
6-5
Figure 6-2
Location in the Select Telepresence Rooms window is read from Active Directory upon startup of TMSXE for the Active Directory accounts of the enabled mailboxes and is provided to the WebEx and TelePresence Integration to Outlook. It is a simple text field, and not structured data. The location information is the same as what is displayed in the Location column in the Microsoft Exchange Address Book, shown in Figure 6-1. The structure and hierarchy displayed in the drop-down menu in the Exchange Address Book (Figure 6-1) is manually created by the Exchange administrator. This can be done by creating nodes, giving them a name and a search filter. A common use (besides geographical) is to structure the list using departments, groups or business units. For more information, refer to the documentation for Microsoft Exchange.
Configure the WebEx mailbox in Microsoft Exchange. Add the WebEx mailbox to Cisco TMSXE.
Create a new user mailbox for your WebEx Scheduling Mailbox (example: [email protected]). See Create a Mailbox (Exchange 2010 Help) or How to Create a Mailbox for a New User (Exchange 2007 Help) for instructions.
6-6
OL-21352-02
Chapter 6
Configuring Cisco TelePresence Management Suite Extension for Microsoft Exchange Configuring Cisco TMSXE for the WebEx Scheduling Mailbox
Give the EWS Service Account Full Mailbox Access to this mailbox. See Allow Mailbox Access (Exchange 2010 Help) or How to Allow Mailbox Access (Exchange 2007 Help) or How to Allow Mailbox Access (Exchange 2007 Help) for instructions.
Step 3
Turn off the Calendar Attendant for the mailbox. See Configure User and Resource Mailbox Properties (Exchange 2010 Help) or How to Disable the Auto-Processing of Meeting Messages (Exchange 2007 Help) for instructions.
b.
Make sure new requests are not automatically marked as tentative by disabling AddNewRequestsTentatively (Mark new meeting requests as Tentative if using the Calendar Settings tab) for the mailbox.
Log in to the server on which TMSXE is installed. From the Windows task bar, select Start > All Programs > Cisco > TMSXE Configuration. If Cisco TMSXE is already running, a message appears indicating you must stop the Cisco TMSXE service to start the configuration tool. Click Stop Service. The Cisco TMSXE Configuration window appears. Click the Exchange Web Services tab. In the WebEx Scheduling Mailbox field at the bottom of the window, enter the email address of the WebEx mailbox you created in Microsoft Exchange. Click Save. TMSXE validates the email address you provided and a message appears indicating your settings have been saved.
Step 7
Click Exit.
Additional Recommendations
Cisco also recommends using the following configurations for WebEx Scheduling Mailbox:
Using Exchange Management Console Mail Flow Settings or Powershell, stricten the message delivery restrictions as needed. For example, require senders to be authenticated, only allow from people in a specific group or similar. See Configure Message Delivery Restrictions (Exchange 2010 Help) or How to Configure Message Delivery Restrictions (Exchange 2007 Help) for instructions.
Using AD Users and computers or Powershell, set the Active Directory user account to disabled. See Disable or Enable a User Account for instructions.
6-7
6-8
OL-21352-02
CH A P T E R
Contents
This chapter describes how to configure Cisco TelePresence Management Provisioning Extension (Cisco TMSPE) for scheduling of Cisco WebEx Enabled TelePresence meetings using Smart Scheduler. It contains the following sections:
Prerequisites, page 7-1 Introduction, page 7-2 User Access to Cisco TMSPE, page 7-2 How Smart Scheduler Works, page 7-3 Limitations, page 7-4
Prerequisites
Cisco TMS software release 14.2 or later must be installed. Cisco TMSPE software release 1.1 or later must be installed and enabled in TMS. WebEx must be configured on TMS.
Cisco WebEx option key One or more WebEx sites Single sign-on or specified WebEx credentials for each user.
Cisco highly recommends that Single Sign On is configured for Cisco TMS and WebEx for easy addition and management of users.
Note
If Single Sign On is not configured In Cisco TMS, you must manually add a WebEx username and password for each Cisco TMS Smart Scheduler user that will schedule meetings with WebEx.
7-1
Chapter 7 Introduction
For details on how to configure TMS, refer to Configuring Cisco TelePresence Management Suite.
Introduction
Smart Scheduler is a part of the Cisco WebEx and TelePresence solution, allowing users to schedule telepresence meetings with WebEx. With Smart Scheduler users can schedule Cisco TelePresence meetings with and without WebEx. Any bookable system in Cisco TMS can be scheduled directly. Any system that is not supported by Cisco TMS booking can be scheduled as a call-in participant, including devices provisioned by Cisco TMSPE. The option to include WebEx in a meeting is available in the Smart Scheduler booking form if Cisco WebEx has been set up with Cisco TMS.
Note
The default date and time format for a new meeting is dd.mm.yyyy and 24-hour time format. Each user can change these default settings by clicking their name or the wrench icon in the upper-right portion of the Smart Scheduler window. This setting is saved as a cookie in the each browser used.
Users who already use Cisco TMS can also click the portal icon in the upper right corner to go to Smart Scheduler and FindMe.
Figure 7-1 Cisco TMS Portal Icon
7-2
OL-21352-02
Chapter 7
Configuring Cisco TelePresence Management Suite Provisioning Extension How Smart Scheduler Works
<META HTTP-EQUIV="Refresh" CONTENT="0; URL= https://<Cisco TMS Server Hostname>/tmsagent/tmsportal/#scheduler"> <title>Cisco TelePresence Management Suite Smart Scheduler</title> </head> <body> </body> </html>
A local account on the Cisco TMS Windows Server A domain account that the server trusts through Active Directory. By making the server a member of the domain, all trusted domain users can automatically use their existing Windows credentials.
A Cisco TMS user account will be created for them when they access the site if one does not exist already.
Note
The actual booking is not created directly by the individual user, but on their behalf by the Cisco TMSPE service user added during installation. Booking permissions will therefore be the same for all users.
When a domain user signs into Smart Scheduler and books a meeting, the request is passed to Cisco TMS. This communication goes through the Cisco TelePresence Management Suite Extension Booking API (Cisco TMSBA). The Cisco TMS user entered during installation of Cisco TMSPE is the service user for Smart Scheduler. This user creates the booking in Cisco TMS on behalf of the Cisco TMSPE user. If the Cisco TMSPE user does not already exist in Cisco TMS, it will be created at the same time as the booking.
4.
When the booking is complete, Cisco TMS sends an email confirmation to the user who booked the meeting. The message containing meeting details including route, scheduled systems, WebEx information, and so on, may then be forwarded to the other meeting participants.
7-3
Chapter 7 Limitations
Limitations
Cisco strongly recommends that meetings scheduled in Cisco TMS not be modified using Smart Scheduler, as this interface and does not support all features and options that may have been chosen for the meeting in Cisco TMS.
Exceptions to recurrent meeting series are not supported in Smart Scheduler. Any modification will be applied to all instances. Smart Scheduler will rename call-in participants added from Cisco TMS. Smart Scheduler is not compatible with the use of setup and teardown buffers in Cisco TMS scheduling. This is a limitation of the Cisco TelePresence Management Suite Extension Booking API.
7-4
OL-21352-02
CH A P T E R
Configuring Audio
Revised: April, 2013
Contents
This chapter describes how to configure audio for Cisco WebEx Enabled TelePresence. The following sections describe the audio deployment scenarios:
Configuring SIP Audio for Cisco WebEx Enabled TelePresence, page 8-2 Configuring PSTN Audio for Cisco WebEx Enabled TelePresence, page 8-3 Configuring TSP Audio for Cisco WebEx Enabled TelePresence, page 8-7
Prerequisites
To configure SIP or PSTN Audio, the following are required:
VCS Control/Expressway must be configured. For details, refer to: Chapter 4, Configuring Cisco TelePresence Video Communication Server Control and Expressway.
For details, see Configuring a SIP Trunk Between Unified CM and VCS Control, page 4-5
Your regions are configured for g.711.
If configuring PSTN audio, Gateway must be registered to VCS or Unified CM. MCUs/TelePresence Servers must be registered to VCS.
No support for MCUs/TelePresence Servers trunked to Unified CM.
Endpoints registered to VCS and/or Unified CM and able to call into MCUs/TelePresence Servers Familiarity with all of required products To deploy PSTN audio, MCU is required.
PSTN audio with TelePresence Server is not supported at this time.
8-1
Configuring Audio
If configuring TSP audio and the TSP provider offers a waiting room feature, the TSP provider must configure it to allow multiple hosts to log in to the audio conference, or the human host must be trained to not log in as a host. If multiple hosts are not enabled, each host that dials in disconnects the host that dialed in before it. For example, if the MCU dials in first, when the human host dials in later, they will disconnect the MCU. The human host still maintains host privileges on the WebEx client and can mute/unmute participants through that user interface if needed.
Note
Configuring the WebEx Site in Cisco TMS to Use SIP Audio Enabling Hybrid Audio on the WebEx Site, page 8-3
Note
SIP audio only supports WebEx audio (TSP audio is not supported).
Log into Cisco TMS. Go to Administrative Tools > Configuration > WebEx Settings. The WebEx Settings page appears. Click the name of the WebEx site you want to configure. The WebEx Site Configuration page appears. If a new site, enter the Site Name, Host Name and other required fields. For TSP Audio, select No. Click Save.
Step 3
8-2
OL-21352-02
Chapter 8
Configuring Audio Configuring PSTN Audio for Cisco WebEx Enabled TelePresence
Configuring the WebEx Site in Cisco TMS to Use PSTN Audio Enabling Hybrid Mode on the WebEx Site, page 8-4 Configuring PSTN Calls to Pass Through a PSTN Gateway to WebEx, page 8-4
8-3
Configuring Audio
Note
Cisco WebEx Enabled TelePresence always dials a fully qualified E.164 number beginning with the international escape character (+). For example: +14085551212. Make sure that VCS and/or Unified CM call routing is set up accordingly.
Log into Cisco TMS. Go to Administrative Tools > Configuration > WebEx Settings. The WebEx Settings page appears. Click the name of the WebEx site you want to configure. The WebEx Site Configuration page appears. If a new site, enter the Site Name, Host Name and other required fields. For TSP Audio, select Yes. Click Save.
Step 3
Caution
If the meeting organizer chooses a TelePresence Server when scheduling the meeting, Cisco TMS will automatically attempt to schedule the meeting using MCU. If an MCU is not available, the meeting will not be scheduled successfully.
Configuring PSTN Calls to Pass through a PSTN Gateway Registered to VCS, page 8-5 Configuring PSTN Calls to Pass through a PSTN Gateway Registered to Unified CM, page 8-6
8-4
OL-21352-02
Chapter 8
Configuring Audio Configuring PSTN Audio for Cisco WebEx Enabled TelePresence
On VCS, create a transform or search rule that transforms the globally routable number provided by WebEx (example: +14085551212) to a number with the tech-prefix of the gateway registered to VCS (example: 9#14085551212). This example transforms [email protected] to 9#[email protected] using the Regex pattern type:
For more information about configuring traversal zones, search rules and transforms in VCS, refer to the Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Deployment Guide at: https://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_C onfiguration_Cisco_VCS_Control_with_Cisco_VCS_Expressway_Deployment_Guide_X7-2.pdf
Figure 8-2 PSTN Audio Deployment with Gateway Registered to VCS and Endpoints Registered to Unified CM
Note
8-5
Configuring Audio
Log in to VCS Control. Go to VCS Configuration > Protocols > Interworking. For H.323 <-> SIP interworking mode select On and click Save.
Note
On VCS, create a search rule that takes the globally routable number with the international escape character (+) provided by WebEx (example: +14085551212) and routes it to Unified CM. On Unified CM, create a route pattern according to your dial plan to route these types of calls to the appropriate PSTN gateway registered to Unified CM.
For more information about configuring search rules on VCS, refer to the Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Deployment Guide at: https://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_C onfiguration_Cisco_VCS_Control_with_Cisco_VCS_Expressway_Deployment_Guide_X7-2.pdf For more information about configuring route patterns in Unified CM, refer to the documentation for your Unified CM version: https://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
8-6
OL-21352-02
Chapter 8
Configuring Audio Configuring TSP Audio for Cisco WebEx Enabled TelePresence
Figure 8-3
Configuring MACC Domain Index and Open TSP Meeting Room Webex Settings Configuring the TSP Dial String Configuring How the Conference is Opened How a TSP Meeting Works, page 8-10 Behavior of TSP Audio Meetings When the MCU Dials in as Host, page 8-10
Configuring MACC Domain Index and Open TSP Meeting Room Webex Settings
WebEx cloud services must configure these settings for you. Contact WebEx cloud services for more information.
8-7
Configuring Audio
Method 1: Configure the DTMF dial string for the MCU to enter the meeting as the host and unlock the meeting.
WebEx cloud services works with the TSP partner to create the proper DTMF dial string. If the WebEx host has already entered meeting, the DTMF dial string of the MCU will be heard
by meeting participants.
Note
A DTMF dial string is required, whether or not you are configuring the dial string for the MCU to enter the meeting as host. Contact WebEx cloud services for more information. Method 2: The WebEx TSP server sends the W2A_UpdateConference=2 API command to the TSP partner's bridge to unlock the meeting.
The TSP partner may have to recode their TSP adapter in order to recognize and properly
execute the unlock conference command.Contact your TSP provider to determine if they support this API command.
8-8
OL-21352-02
Chapter 8
Configuring Audio Configuring TSP Audio for Cisco WebEx Enabled TelePresence
Table 8-1
Scenario MCU is the first caller into the audio conference One or more attendees have already joined the audio conference (waiting room) before the MCU dials in. The host has already joined the audio conference before the MCU dials in.
If method 1 is used The MCU will have host role in the TSP audio conference The MCU will have host role in the TSP audio conference
If method 2 is used The MCU will not have the host role in audio. The MCU will not have the host role in audio.
Successful join
Successful join
No such extra DTMF tones will be Users who have heard. already joined the audio conference may hear the extra DTMF tones broadcast into the audio conference, which is the MCU following the DTMF sequence as though it were the host. Since method 2 is being used, the Audio conference partner should keep the conference may terminate. running until either: Depends on TSP implementation a. all attendees have left the some may not conference or terminate. Depends on host's selection in b. TSP API sends W2A_CloseConference WebEx GUI upon leaving conference (option to keep conference running) MCU should fail to join MCU should fail to join
The host (who had already joined the audio conference before the MCU dials in), hangs up while the conference is still underway.
Varies
DTMF failure The host joins via WebEx before the MCU dials in, and the host uses the WebEx GUI to lock the conference. (WebEx has decided to respect the hosts' locking of the conference in this case.)
8-9
Configuring Audio
The meeting is scheduled. A dial string is passed back to the MCU. At the scheduled start time, the MCU starts the meeting. TelePresence connects into WebEx via SIP. The TSP partner starts the audio conference on their bridge and they open up the conference. At the same time as TelePresence connects to WebEx via SIP, it also dials via PSTN into the TSP partner bridge using the DTMF dial string.
8-10
OL-21352-02
CH A P T E R
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
Revised: April, 2013
Contents
This chapter describes how to configure your WebEx site for Cisco WebEx Enabled TelePresence. It contains the following sections:
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account, page 9-1 Assigning the Meeting Center TelePresence Session Type, page 9-3 Installing the WebEx and TelePresence Integration to Outlook, page 9-5 Setting the Time Zone and Language Preferences for a Users WebEx Account, page 9-7
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
You have access to the Cisco WebEx Site Administration interface through your WebEx Account Team using a unique WebEx Site Administration URL and password. As a site administrator, you must log in to integrate and provision your account during first time setup. After you have completed the first-time setup, you can manage your account and access WebEx user and administration guides for the services and features that have been configured on your Cisco TelePresence system. Proceed to the following sections to complete first-time setup:
Cisco TelePresence Cisco WebEx Integration Options, page 9-1 Assigning the Meeting Center TelePresence Session Type, page 9-3
Log in to the WebEx Site Administration interface using your WebEx Site Administration URL and scheduling server password.
9-1
Chapter 9 Contents
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
Step 2 Step 3
On the left navigation bar under Manage Site, choose Site Settings. The Site Settings screen appears. Scroll down to OneTouch TelePresence Options, as shown in Figure 9-1.
Figure 9-1 Configuring Cisco WebEx Connection Settings
Step 4 Step 5
Click to select Allow Cisco WebEx OneTouch meetings (MC only). If not checked, Cisco WebEx will be disabled on this site and the rest of the Cisco TelePresence integration options will be grayed out. If you are deploying the Cisco WebEx Enabled TelePresence solution with the option to schedule meetings using the WebEx and TelePresence Integration to Microsoft Outlook, you must enter the host address for the TelePresence Management Suite Extension for Microsoft Exchange (TMSXE) in the Cisco TMS booking service URL field. For more information about configuring TMSXE, see Chapter 5, Configuring Cisco TelePresence Management Suite. Click to select List Cisco TelePresence meetings on calendar so that scheduled meetings appear on the Cisco WebEx calendar. Click to select Send invitation email to meeting host. This allows the meeting information email to be sent to the Cisco WebEx host after the meeting is scheduled. Click to select Display toll-free number to attendees. This enables the system to show the toll-free number that attendees can call to join the meeting. In the WebEx VOIP and video connection field, click one of the following:
Automatically encrypted UDP/TCP SSL(Recommended) Allows the TelePresence Server or MCU to connect over UDP with the Cisco TelePresence Gateway. If the UDP connection is not allowed, TelePresence Server or MCU will fall back to TCP. TCP SSLConnects over TCP over a SSL connection.
This selects the connection method between the Cisco WebEx client and the multimedia server (VOIP and video).
Step 10
(Optional) If you do not want users to use VoIP audio on this WebEx site, check the box Disable Hybrid VOIP. This disables VoIP for all meetings on the site, not only WebEx-enabled TelePresence meetings. Scroll to the bottom of the page and click Save to save your settings.
Step 11
9-2
OL-21352-02
Chapter 9
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Contents
Step 12
Proceed to Assigning the Meeting Center TelePresence Session Type to complete your setup.
Adding the Cisco TelePresence Session Type in the List of Users, page 9-3 Adding the Cisco TelePresence Session Type in the Edit User Screen, page 9-4
In the left navigation bar under Manage Users, choose Edit User List. The Edit User List screen appears, as shown in Figure 9-2.
Figure 9-2 WebEx Site Administration - Edit User List
Step 2
Identify which PRO column represents the Meeting Center TelePresence session type. Each Cisco WebEx user account has a corresponding set of Session Type check boxes that indicate which Cisco WebEx session types have been enabled for that user; Meeting Center TelePresence is one of the PRO sessions types. (Other session types, such as Meeting Center Pro meeting, can also have a PRO headline, as shown in Figure 9-2. ) To determine which column represents the Meeting Center Telepresence session type, click any of the "PRO" Session Type headers. A separate window opens that describes that session type, as shown in Figure 9-3. Locate the column that brings up the session type feature list titled "Supported Features in TelePresence"; this is the Meeting Center TelePresence session type.
Note
The number of session type columns is determined by how many session types the WebEx site supports.
Step 3
To verify that a user is assigned the Meeting Center TelePresence session type, locate the user entry on the Edit User list and select the check box for the appropriate PRO session type identifed in Step 2.
9-3
Chapter 9 Contents
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
Step 4
Scroll to the bottom of the page and click Submit. If you do not find the Meeting Center TelePresence session type, or if there is no Supported Features in TelePresence window present after you have clicked all PRO Session Types, the site is not proplerly configured for WebEx Enabled TelePresence.
Figure 9-3 Supported Features in TelePresence
Note
This session type will be assigned by default when you create new host accounts by using the Add User link on a TelePresence-enabled WebEx site. The user must have this session type assigned in order to schedule OneTouch meetings. If this site is an existing site updated to WebEx Enabled TelePresence, you must add the Meeting Center TelePresence session type to existing users.
Adding the Cisco TelePresence Session Type in the Edit User Screen
You can also set the Meeting Center TelePresence session type in the account settings for each individual user. Do the following while still on the Manage Users > Edit User List page:
Step 1 Step 2
Locate the user entry and click on it to open the Edit User window for that account. Scroll down to the Privileges section. The assigned session types are shown in the Session Type Allowed box, as shown in Figure 9-4.
9-4
OL-21352-02
Chapter 9
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Contents
Figure 9-4
Step 3 Step 4
Required. Check the box for PRO: Meeting Center TelePresence, as shown circled in red in Figure 9-4. Click the Update button at the bottom of the window to save your PRO: Meeting Center TelePresence Session Type setting. This completes setting meeting center Cisco TelePresence Session Type privileges in the Cisco WebEx Site Administration. Your Cisco WebEx account is now fully integrated and provisioned.
Tip
WebEx Site URL WebEx User Name WebEx Password TMSXE User Name TMSXE Password
Note
Open a browser and go your WebEx site. Under the Meeting Center tab select Support > Downloads. Next to Productivity Tools, click the Download now (Login Required) link.
9-5
Chapter 9 Contents
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
If you are already logged in to your WebEx site, the link will say Download now. If so, skip to Step 5. Enter your WebEx username and password and click Log In. Next to Productivity Tools, click the Download now link. The download begins and you are prompted to save the ptools.msi file. Click Save File. After the download is complete, open the ptools.msi and follow the on-screen instructions to install the WebEx Productivity Tools. Follow the on-screen instructions to install the WebEx Productivity Tools. During the installation you must enter you must log in to your WebEx site.
Figure 9-5 WebEx Productivity Tools Login
Step 11
Enter your WebEx Site URL, User Name, Password and click Login. After logging in, the WebEx Productivity Tools communicates with the server and then your are asked to log into TMSXE.
Figure 9-6 TMSXE Login
Step 12 Step 13
Enter your TMSXE User name and Password and click OK. When the message WebEx Productivity Tools are installed appears, click OK.
9-6
OL-21352-02
Chapter 9
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account Where to Go Next
Step 14
Close the Productivity Tools window. You can now open Microsoft Outlook and schedule WebEx Enabled TelePresence meetings using the WebEx and TelePresence Integration to Outlook.
Setting the Time Zone and Language Preferences for a Users WebEx Account
For best results, meeting organizers using Outlook for scheduling, should do the following:
Set their WebEx and Outlook time zones to the same time zone. If a meeting organizers WebEx and Outlook time zones do not match, meetings will not be scheduled at the same time in both WebEx and Outlook.
Make sure their preferred language is selected in their WebEx account. The selected language is the language that all invitees will see in the meeting invitation.
To set the WebEx time zone and preferred language for a WebEx account, users must do the following:
Step 1 Step 2 Step 3
Open a browser and go to your WebEx site. Click My WebEx. Enter your WebEx username and password and click Log In. The My WebEx Meetings page appears. In the right corner of the page, the current language and time zone settings are displayed. To change the language and time zone, click on the link that displays either the current language or time zone. The Preferences page appears. Using the Time zone and Language menus, select the time zone and language you wish to use for your WebEx Enabled TelePresence meetings. Click OK.
Step 4
Step 5 Step 6
Where to Go Next
For complete information about managing your Cisco WebEx Administration Site account, refer to the Help on your WebEx site.
9-7
Integrating Cisco TelePresence with Your Cisco WebEx Site Administration Account
9-8
OL-21352-02
CH A P T E R
10
Contents
This chapter provides a background on how to schedule Cisco WebEx Enabled TelePresence meetings, with tips and known issues. It contains the following sections:
Introduction, page 10-2 Scheduling WebEx Enabled TelePresence Meetings in Cisco TMS, page 10-3 Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings, page 10-5
10-1
Chapter 10 Introduction
Introduction
This chapter provides an overview of how to schedule WebEx Enabled TelePresence meetings using TMS and useful information, tips and known issues about WebEx Enabled TelePresence meetings. In addition to scheduling using TMS, there are up to 3 additional ways to schedule a WebEx Enabled TelePresence meeting:
Using the Cisco WebEx and TelePresence Integration to Outlook With the WebEx and TelePresence Integration to Outlook, users can schedule WebEx Enabled TelePresence meetings directly from Microsoft Outlook for Windows. Advanced options like adding external video and audio dial-in participants are also available. For scheduling information, refer to the WebEx and TelePresence Integration to Outlook Quick Reference Guide For additional information, including how to schedule a meeting on behalf of another person or to assign a delegate to schedule meetings for you, refer to the WebEx and TelePresence Integration to Outlook help available in Outlook or the user guide, available on your WebEx site.
Using the Cisco Smart Scheduler With Cisco Smart Scheduler, Macintosh, mobile and other non-Windows users can schedule WebEx Enabled TelePresence meetings using a simple web-based interface which is touch-screen friendly. For scheduling information, refer to the Cisco Smart Scheduler and WebEx Scheduling Mailbox Quick Reference Guide For additional information, including supported browsers and mobile platforms, refer to the Cisco TelePresence Management Suite Provisioning Extension (TMSPE) release notes.
Using the Cisco WebEx Scheduling Mailbox With the Cisco WebEx Scheduling Mailbox, users without the WebEx and TelePresence Integration to Outlook can create a TelePresence Enabled WebEx meeting in Outlook by inviting TelePresence rooms and then adding WebEx to the meeting by including a special invitee; the WebEx Scheduling Mailbox. The mailbox may be called simply webex or something different. It as configured by the administrator and provided to users. For additional information, refer to the Cisco TelePresence Management Suite Extension for Microsoft Outlook (TMSXE) Installation Guide and release notes. For scheduling information, refer to the Cisco Smart Scheduler and WebEx Scheduling Mailbox Quick Reference Guide
10-2
OL-21352-02
Chapter 10
Scheduling Cisco WebEx Enabled TelePresence Meetings Scheduling WebEx Enabled TelePresence Meetings in Cisco TMS
Cisco TMS
When scheduling conferences with Cisco TMS, it is not necessary for the user to worry about network protocols, MCUs, or gateways. Cisco TMS handles infrastructure choices and compatibility checking of all these things automatically. Advanced users may still tune and tweak the selected methods for the conference as needed. To schedule a Cisco WebEx Enabled TelePresence Meeting:
Step 1 Step 2
Step 3 Step 4
For Title, enter a conference title. It will be displayed in all Cisco TMS interfaces, and in email notifications about the meeting. For Type, select either Automatic Connect or One Button to Push.
Automatic Connect: Cisco TMS automatically connects all participants at the meeting start time. One Button to Push: Meeting dial-in information is automatically displayed on endpoints that support One Button to Push. Participants on those endpoints join the meeting by pressing a button. For endpoints that do not support One Button to Push, the meeting organizer adds a video dial-in number.
For information about additional types, refer to the TMS help. Set the Start Time and the End Time or Duration for the meeting. Make sure Include WebEx Conference is checked. Optionally, enter a WebEx Meeting Password.
10-3
Note
If you do not enter a password, WebEx will automatically generate one. It will be displayed on the Confirmation page, after you successfully schedule the meeting. Optionally, click Recurrence Settings to create a series of meetings that are tied together, such as a weekly or daily meeting.
Step 8
Note
Advanced settings are optional. Most settings will take their default values from the Conference Default values configured under Administrative Tools. Refer to the help for an overview of all available settings. For details on the Advanced Settings, click the Help button in Cisco TMS.
Note
If Secure is set to Yes, Cisco TMS will only allow systems that support encryption to participate in the conference. Optionally, add notes about the meeting in Conference Information, which will appear in the meeting invitation. In the Participant tab, click Add Participant and a new window will appear.
Step 9 Step 10
Available participants and a planner view with their availability is displayed based on existing scheduled and ad hoc meetings. The colored vertical lines represent your current requested time for the scheduled meeting. Click the tabs to have participants listed by type. If you have used scheduling before, the default tab is Last Used with quick access to the systems you have used recently. Hover over any system, or the blocks in the planner view, for additional detail about the system or scheduled meeting.
Step 11
Add participants to the meeting by selecting their checkbox and clicking the > button to add them to the list of selected participants on the right side of the window. Adding network infrastructure components like MCUs and Gateways is optional as Cisco TMS will handle this for you automatically. Use the External tab to add systems not managed by Cisco TMS, for example endpoints in other organizations, or telephone participants.
Step 12
For dial-out participants, enter their contact information, and Cisco TMS will automatically connect them to the conference at the scheduled time. For dial-in participants (including endpoints that do not support One-Button-to-Push), Cisco TMS will reserve the capacity needed to host the site in the conference and will provide you with precise dial-in information to forward to the participant.
Step 13
When all participants have been added, click OK. You are returned to the conference page, with the participant section of the page now showing your selected participants, and some additional tabs. These additional tabs allow advanced scheduling tasks such as altering how calls are connected, or setting specific MCU conference settings for the meeting.
Step 14
Use the Video Conference Master drop-down list to determine which system should be considered the meeting organizer. Not all telepresence systems support the necessary features for this functionality, and only systems that are eligible will be displayed in this list. This is the system that will be prompted:
to connect the conference if it is not scheduled for automated call launch. to extend the conference when it is about to expire.
10-4
OL-21352-02
Chapter 10
Scheduling Cisco WebEx Enabled TelePresence Meetings Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings
Step 15
Click Save Conference. When the conference is saved, Cisco TMS will do all the routing calculations to determine the best way to connect your selected participants.
showing the details of your meeting, including the participant list and listing how each of those participants are scheduled to connect to the conference and the exact dial string any participants must dial.
You will also receive an email confirmation from Cisco TMS with all meeting information,
including WebEx and video dial-in information, and an ICS attachment for saving the event in your Outlook (or a compatible) calendar. Open the ICS attachment and save it to your calendar.
If your WebEx site is set up to send email confirmations, you will receive two additional emails
from WebEx: 1. An email with the subject line Meeting Scheduled which contains the host key and the WebEx information for the meeting 2. An email with the subject line (Forward to attendees) Meeting Invitation which contains only the WebEx information for attendees.
to save the meeting. This may be due to lack of availability, lack of network resources, or no known route to connect the participants together.
Edit the conference settings to try to resolve the issue and try saving the conference again. Step 16
After successfully scheduling your meeting, invite people to the meeting using your calendar application. For information about the Cisco WebEx Enabled TelePresence meeting experience, see Cisco WebEx Enabled TelePresence Experience, page 1-1.
Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings
The following section contains useful information, including tips and known issues relating to Cisco WebEx Enabled TelePresence meetings. The information is divided into sections corresponding to each product that is part of the Cisco WebEx Enabled TelePresence Solution.
Cisco TMS
Cisco TMS can be configured so that meetings must be approved by the Cisco TMS administrator before getting booked. This feature can be used to regulate port usage at companies that want to limit / regulate usage. Cisco TMS limits the number of ports to the number selected under the external tab of the Cisco TMS meeting when it is scheduled. Starting a meeting early is supported for both TelePresence and WebEx using the Default Setup Buffer setting when scheduling the meeting.
10-5
Chapter 10 Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings
Note
Setup (and teardown) buffers are not supported when using Smart Scheduler, the WebEx and TelePresence Integration to Outlook, or any other client that uses the TMS booking API. Extending a meeting is supported for both TelePresence and WebEx using the Extend Mode setting when scheduling a meeting. Meeting extension is not guaranteed. If resources (ports) are fully booked at the scheduled end time of the meeting, the meeting will end. A meeting organizer scheduling a meeting using the WebEx and TelePresence Integration to Outlook, should never modify that meeting later in TMS. If the original meeting is modified later in TMS, the meeting information in TMS will fall out of sync with the meeting organizers Outlook calendar. The reason for this is that TMSXE does not have write access to the meeting organizer's calendar and, as a result, cant make any changes to it.
MCU and TS
At the start of the meeting, the MCU/TS calls into WebEx, even if there are no TelePresence or WebEx participants. The MCU/TSs role is different from a regular WebEx participant. When joining the meeting, if there is no meeting host currently in the meeting, the MCU becomes the default host and starts the meeting.
If there is already a WebEx host, MCU/TS will not become the host. If WebEx host leaves the meeting, the MCU/TS becomes the host and the meeting continues.
If MCU/TS leaves the meeting before the WebEx host leaves, the meeting continues. If MCU/TS leaves the meeting after the WebEx host leaves, the meeting ends. If WebEx host leaves the meeting after the MCU/TS leaves, the meeting ends. If WebEx host stays in the meeting after the MCU/TS leaves, the WebEx meeting continues. TS by default, sends video in the ActivePresence screen layout, which displays the active speaker in a full screen pane with additional participants appearing in up to six equally sized overlaid panes at the bottom of the screen (up to four panes for 2 and 4 screen endpoints). In full-screen mode in WebEx, WebEx participants appear in equally sized panes below the TelePresence video at the bottom of the window. MCU by default, sends video in a full-screen layout.
Endpoints
Participants joining the meeting from any TelePresence endpoint may not see the presentation from WebEx if they are using their endpoint as a computer monitor. Content presented from an EX60 can take a long time to appear. If the endpoint is registered to Unified CM, this can be resolved by enabling User-Agent passthrough in Unified CM.
TMSXE
When booking a meeting using Web Scheduling Mailbox, if TMSXE detects an error condition (ex: not able to connect with WebEx server), the error email is sent in plain text format to the meeting organizer.
10-6
OL-21352-02
Chapter 10
Scheduling Cisco WebEx Enabled TelePresence Meetings Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings
WebEx
A black silhouette is shown for a WebEx user when they do not have their camera on. In the WebEx Meeting Center, all TelePresence endpoints are displayed as one WebEx participant called TelePresence systems both in the Participant list and when a TelePresence user is the active speaker.
In the Meeting Center full screen view, the TelePresence systems participant appears as a
Audio quality can be bad for WebEx participants using Computer Audio when attending using the WebEx Meeting Center client on Windows or Mac. Cisco recommends users to call in with a phone using the audio conference number for the meeting. The meeting is started by the first participant who joins the meeting (host or other WebEx participant). The rest of the participants join the meeting. A non-host user can start the meeting only if the Join Before Host feature is enabled on the site, and its start time could be 5/10/15 minutes (set a time of scheduling) before the scheduled time. Otherwise, a non-Host has to wait for the meeting to be started by the host before they can join. If a WebEx audio only participant is talking, the last video participant to talk is displayed until the next video participant speaks. The user's Outlook time zone and WebEx account time zone must be the same for the meeting to be scheduled at the correct time in both Outlook and WebEx. When the WebEx portion of the meeting ends, the audio will end too. The link bandwidth between MCU and WebEx is set by the WebEx client with the lowest bandwidth. The bandwidth of the link can go up as soon as the WebEx client with the poorest bandwidth leaves the meeting. For example, if a WebEx client that joins the meeting is only capable of 360p, the maximum bandwidth for all participants will be 360p. When that participant leaves the meeting, if all other participants are capable of a higher bandwidth, like 720p, the bandwidth will go up for all participants.
10-7
Chapter 10 Information, Tips and Known Issues About WebEx Enabled TelePresence Meetings
10-8
OL-21352-02
CH A P T E R
11
Troubleshooting
Revised: April, 2013
Contents
Verifying and Testing, page 11-1 Troubleshooting Tips, page 11-1 Managing System Behavior, page 11-8
Troubleshooting Tips
This section provides troubleshooting tips for problems with the following aspects of a Cisco WebEx Enabled TelePresence meeting:
Problems with Scheduling a Meeting, page 11-2 Problems with Starting or Joining a Meeting, page 11-3 Problems During a Meeting, page 11-4 Problems with a TSP Audio Meeting, page 11-6 Managing System Behavior, page 11-8
11-1
Troubleshooting
Problem or Message The meeting organizer receives no e-mail from Cisco TMS to confirm the meeting is scheduled.
Recommended Action Check Cisco TMS configuration. If Cisco TMS configuration is correct, check antivirus/firewall program(s) to see if they are blocking the Cisco TMS from sending. If pushed to all but one endpoint, then check the network connection. If not pushed to any endpoints, check to see if Cisco TMS is down. In Administrative Tools > Configuration > WebEx Settings, select the WebEx site and make sure Connection Status is Connection OK. Check user profile WebEx account. Recommended Action: Check the WebEx Username/Password for the WebEx site in the user personal information page. Or the WebEx site user credential information may have changed. In this case, check with WebEx site administrator. Refer to Cisco TMS Troubleshooting information. This issue is not limited to Cisco WebEx Enabled TelePresence.
More than one scheduling server is managing the endpoint (CTS-Manager and Cisco TMS at the same time). Other causes:
Scheduled meeting type is not OBTP. Only OBTP meeting shows up in endpoint. Network connection failure between endpoint and Cisco TMS.
WebEx user doesnt exist on WebEx Symptom: Cisco TMS displays 'Unable site. to include WebEx conference. Incorrect Cause: WebEx site configured for this WebEx username or password.' organizer does not recognize the WebEx username/password configure for the meeting organizer.
No confirmation emails from WebEx Meeting is booked on the TMS but the WebEx does not exist.
email is not enabled on the WebEx site Endpoints booked for the meeting are configured as mailboxes in Exchange but are not set to AutoAccept invitations.
Check the WebEx site administrator. Ensure that all endpoints that are available as mailboxes for booking in a Cisco WebEx Enabled TelePresence meeting are set to AutoAccept in Exchange.
11-2
OL-21352-02
Chapter 11
Table 11-1
Problem or Message Weve hit a glitch in connecting to the telepresence scheduling system. Try again later. I don't see the WebEx option when scheduling a meeting in TMS.
Your WebEx Username and Password have not been added to your TMS user profile.
Edit your TMS user and enter your WebEx username and password and then save. The WebEx option should now appear in the TMS scheduling UI.
Problem or Message Cant join the WebEx meeting No endpoint can join the TelePresence meeting.
Possible Causes Meeting hasnt started yet TelePresence meeting doesnt exist. Call failed to be routed correctly.
Recommended Action wait for meeting to start 1. Check MCU/TelePresence Server to make sure conference was created. 2. Check MCU/TelePresence Server event log. 3. Check VCS search history.
TelePresence meeting didnt start early (Early Meeting Start) didnt work Single TelePresence participant cant join the meeting
Cisco TMS scheduled meeting doesn't support early start. Endpoint must wait until meeting has started to dial in. Not enough video and audio ports. Call routing issue for the endpoint to MCU or TelePresence Server
Check Setup Buffer and Tear Down Buffer settings Check event log for the meeting. Also check meetings in TelePresence Server or MCU. Administrator can lift the limit by changing the port value from the TelePresence Server Conferences page.
TelePresence participant can only join via audio only. No TelePresence participants can join the meeting
Not enough video ports are available. Meeting hasn't started yet. Cisco TMS scheduled meeting doesn't support early start. Endpoint must wait until meeting has started to dial in. Total audio and video ports for the MCU/TelePresence Server have been used up. Another cause is that the port video/audio limit for the meeting has been reached.
Increase the video ports in Cisco TMS, TelePresence Server or MCU. If total port capacity of MCU/TelePresence Server has been reached, no action is required. For the case of the meeting limit being reached, the administrator can lift the limit from the TelePresence Server Conferences page.
11-3
Troubleshooting
Possible Causes Content disabled on MCU. Video call from MCU/TelePresence Server to WebEx failed. Call failure occurs for several reasons: - WebEx SIP dialing fails to reach destination due to unresolvable SIP URI - WebEx server(s) down - Issues with search rules in VCS - Media Encryption setting in VCS
Recommended Action
Check MCU configuration and conference status. Verify search rules to ensure that SIP URI being routed correctly to WebEx site. Verify encryption setting in VCS for this zone. If failure persists after above actions are taken, contact WebEx site administrator. -
Video call from MCU/TelePresence Server to WebEx failed. Call failure occurs for several reasons: - WebEx SIP dialing fails to reach destination due to unresolvable SIP URI - WebEx server(s) down - Issues with search rules in VCS - Media Encryption setting in VCS
WebEx participant does not enable video. WebEx participant has a problem with their camera.
Make sure TelePresence and WebEx calls are connected. Check to see if participants who joined TelePresence are sending video. Check to see if WebEx users have joined and are sending video. Check TelePresence call statistics and make sure TelePresence endpoint is not muted. Check to see if WebEx users can hear each other. Check TelePresence statistics to see if audio is being received from the WebEx side. In PSTN/TSP audio case check that the audio call is connected.
11-4
OL-21352-02
Chapter 11
Table 11-3
Problem or Message Dont see presentation shared from WebEx side on TelePresence side
Possible Causes -
Recommended Action
Check TelePresence statistic for content channel status. Check to see if WebEx users can see content from each other. Check TelePresence statistic for content channel status. Check to see if WebEx users can see content from each other. Contact the WebEx administrator for assistance. Check TelePresence call statistics to see if content channel is established. Try to stop the restart sending content. Check current call statistics for content channel. Check to see if the SIP call encrypted. Check network bandwidth for possible poor network connection. Check call statistics for TelePresence participants. Make sure audio and video calls are linked in PSTN/TSP case. Check in Cisco TMS CCC or on MCU to see if audio call failed Call-in user merge requires the site to have 'TSP identity code' enabled in WebEx site administrator. If disabled, call-in merge will not work even if you dial the correct value, and #1 is correct for intercall. Check the bandwidth between TelePresence and WebEx. Check the bandwidth between TelePresence and WebEx.
Dont see presentation from WebEx on WebEx side Dont see presentation from TelePresence side on TelePresence side
Poor quality video from WebEx participants on TelePresence side Poor quality video from TelePresence participants on WebEx side Audio skewed from video (lip sync issues) Active speaker does not switch in
Poor network connection In the case of PSTN/TSP audio, lip sync cannot be guaranteed -
1. WebEx site administrator not Video for active speaker call-in participant does not switch in when they configured properly. speak and no phone icon associated with 2. Audio call failed. them. 3. If the MCU sends the wrong participant ID.
Poor quality presentation from TelePresence participants on WebEx side Video from a WebEx participant frozen
11-5
Troubleshooting
Table 11-3
Possible Causes TelePresence is booked for another meeting starting at the end of the current one.
Recommended Action
Check TelePresence log to see any cause for the call drop Check Cisco TMS booking list to confirm.
Problem or Message TelePresence joins audio of hosts previously scheduled meeting that had run beyond the scheduled end time.
Possible Causes The TelePresence system will dial into the hosts audio conference at the scheduled time. It is possible that the host is in a previous audio conference that is running overtime. Example: The host account used by TelePresence is that of a real WebEx host. If that host account has scheduled two back to back meetings (first one is WebEx meeting and the second one is TP+WebEx). Host starts first meeting and it runs overtime. But at the start time of the TelePresence+WebEx meeting, TelePresence dials into the TSP conference using the dumb-dial string, and may get into the conference. Result: TelePresence attendees hear the audio of the previous meeting. This may be a pretty well understood circumstance for customers due to the way TSP Audio works.
Recommended Action
Have TelePresence recite audio prompt after joining the TSP audio. Cisco Telepresence is now in the audio conference (or similar) (using API method does not resolve this)
TelePresence joins audio of hosts previously scheduled meeting where the host had exited with the keep audio conference running otpion
Similar to the above scenario - the host may have left the first meeting but used the keep audio conference open choice. Thus, as the audio conference of the first meeting continues, TelePresence eventually dials in. This may be a pretty well understood circumstance for customers due to the way TSP Audio works.
Have TelePresence recite audio prompt after joining the TSP audio. Cisco Telepresence is now in the audio conference (or similar) (using API method does not resolve this)
11-6
OL-21352-02
Chapter 11
Table 11-4
Problem or Message Host private conference code can break DTMF dumb dial entry method in some cases (dial in as host + host has already dialed in).
Possible Causes If the TSP has implemented a host private conference code (where the host uses a conference code that is not the same as the one used by the attendees, thus avoiding the need for the host to enter a PIN number), the audio prompt call flow might break the dumb-dial of the MCU if the host has already dialed into the conference. (in our testing, this is when we heard all the foreign language prompts from the TSP bridge - it was the bridge barking about the fact that the host conf code is already in use).
Recommended Action
Use API method....or... Advice to TSP partners: If using a hosts' private conference code , then consider allowing the TSP audio bridge to tolerate a second user dialing in using the host private conference code.
11-7
Troubleshooting
Table 11-4
Problem or Message Dial sequence cannot be issued on the fly via TSP API (unlike NBR)
Possible Causes The dial sequence for OT 2.0 integration with TSP's is only statically configurable in the Telephony Domain of site. This restricts a TSP somewhat, in case they might have different audio bridge infrastructures, different dial in numbers, etc. NBR, by contrast, allows for the static configuration as well as a dynamic configuration. The dynamic configuration is done by having the partner TSP Adapter send WebEx the NBR dial string at the time of meeting start via A2W_RspCreateConference[NBRPhon eNumber].
Recommended Action
Change the MCU logic, so that it starts the WebEx meeting and then collects the dial in string from WebEx at that time. The sequence will allow for WebEx to collect the dial string dynamically from the TSP as follows:
1. 2. 3.
TelePresence starts TelePresence meeting TelePresence starts WebEx meeting WebEx sends W2A_CreateConference to TSP TSP sends A2W_RspCreateConference to WebEx (this would contain the TP dial string) WebEx sends dial string to MCU MCU dials into the TSP bridge
4.
5. 6.
The TSP API and TSP Server would need to change (among other components, of course) The TSP Audio account info, used by the MCU dial string, is obsolete. Since the MCU collects and stores the TSP dial string at the time of meeting schedule, to be used at the time of meeting start (which can be many weeks later), there is a possibility that the dial string will be obsolete and hence the call into the TSP conference will fail. This will happen if the default (first) TSP Audio account is changed during the time between TelePresence meeting schedule and TelePresence meeting start.
The above suggestion will solve this problem (make the TelePresence equipment collect the TelePresence dial string from WebEx at the time of meeting start, instead of at the time of meeting schedule.
11-8
OL-21352-02
Chapter 11
11-9
Troubleshooting
11-10
OL-21352-02