PDF(263.5 KB) View with Adobe Reader on a variety of devices
Updated:January 9, 2015
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This section describes new and changed information in Cisco Collaboration Meeting Rooms (CMR) Hybrid (formerly called WebEx Enabled TelePresence), beginning with Update 4:
New in Update 4
This release of CMR Hybrid features the following improvements:
Support for TelePresence Conductor
– Provides management and scheduling of conference bridges in both Unified CM and Cisco VCS-centric deployments
– More efficient usage of bridge resources
Support for WebEx Meeting Center WBS29.11
– Provides low-bandwidth warning and automated retest in WebEx Meeting Center client. If, for reasons of low network bandwidth or conditions (such as CPU or RAM use) that are local to the WebEx application, the WebEx application is not able to maintain the 1.2 Mbps bit rate, users will see a “low-bandwidth” warning message instead of receiving TelePresence video. In WBS29.11 and later, the WebEx meeting center client automatically retests the WebEx participant’s connection to the WebEx Cloud periodically to assess whether any network or local conditions have been remedied. If they are able to send and receive video at a bit rate of 1.2 Mbps or greater, it will resume sending and receiving video automatically.
– When the WebEx host leaves a meeting, they can choose to allow other participants to continue the meeting or to end the meeting for all participants.
– For a complete list of new features, known issues and limitations of WBS29.11, refer to the:
Support for Cisco TelePresence Server on Virtual Machine and Multiparty Media 310/320
Improved presentation share quality
– Provides up to 1080p using TelePresence Server or TelePresence Server on Virtual Machine
– TelePresence Server enhancements including favoring resolution over frame rate for presentation
Important Changes to Certificates in the WebEx Cloud
On January 29, 2015, Cisco is changing to a 4096-bit certificate under different root certificate authorities (CAs) than used today. These certificates are used to secure traffic to and from the WebEx cloud components and VCS Expressway or Expressway-E. Previously, WebEx used a certificate issued under the root CA
DST Root CA X3 to secure traffic between the customer premises and WebEx. Customers have been required to make sure their VCS Expressway or Expressway-E stores the root certificate
DST Root CA X3 that trusted our existing certificate on the WebEx cloud servers. Beginning January 29, 2015, we are revoking our certificate and replacing it with three new certificates that will be issued by three different Root authorities. Customers are required to store new root certificates that support the new WebEx certificates.
If your VCS Expressway or Expressway-E does not have the three new root certificate authority certificates in its Trusted CA Certificate list, calls to WebEx may fail.
For details on where to find and how to install the new root CA certificates on your VCS Expressway or Expressway-E, refer to Configuring the Trusted CA Certificate List on the Cisco Expressway-E Cisco VCS Expressway on page 103 of the:
WebEx presentation quality is reduced by TelePresence when using MCU. The WebEx cloud reduces the maximum resolution and frame rate supported between TelePresence and WebEx to XGA/15.
This is due to the following factors:
– The maximum presentation resolution supported by different TelePresence models varies.
– The TelePresence MCU does one shared-encode presentation channel adjusted down to the lowest-common denominator for all participants in the meeting.
The Share Web Content feature of WebEx Meeting Center is not supported in a CMR Hybrid meeting. Selecting this feature in the WebEx Meeting Center application will display a message that it is unavailable. The Share Web Browser feature is supported, allowing you to control what participants see and hear on a web page, but it does not support participants navigating the site independently (example: filling out a Web form) in the WebEx Content Viewer.
Quality of TelePresence Reduced by WebEx Participants. Video and audio from WebEx participants can be poor due to uncontrolled environments where poor lighting conditions and background noise can make seeing and hearing that participant difficult.
Ask important participants to attend from a TelePresence room or make sure ahead of time that they have set up their WebEx PC or Mobile client for best results:
– A fast, well-performing PC or Tablet
– High quality USB or integrated camera in a properly-illuminated office or cubicle environment
– Great quality PC audio or a separate IP telephone with full-duplex speaker phone or high-quality headset or handset
When the WebEx presenter switches to full-screen video view while sharing his or her screen, application, or document, sharing is paused on the attendee side (the last-shared screen freezes). When the presenter exits full-screen video view, sharing will automatically resume. Attendees will stay in full-screen video view when the presenter stops sharing and will automatically exit full-screen video view when the presenter starts sharing again.
The time zone for the WebEx site must match the time zone for the Cisco TelePresence Management Suite (TMS); otherwise the meeting time will not be synchronized.
When making Daylight Savings Time changes between your WebEx site and the Cisco TelePresence Management Suite, it is possible your meeting may be an hour off schedule; if this happens, rescheduling will be required. If this problem occurs with a meeting series where some instances occur before Daylight Savings Times begins and some occur after, it is recommended that you create two meeting series: one meeting series that ends before the Daylight Savings Time begins and a second meeting series that starts after Daylight Savings Time begins.
Notes for Existing Customers
Existing CMR Hybrid customers are not required to change to the new Unified CM-centric deployment model. If upgrading to Unified CM 9.1(2) or 10.5(2) or later, customers can trunk their bridges directly to Unified CM with no changes in configuration on VCS Control or VCS Expressway. Unified CM 10.5(2) or later is highly recommended.
Notes for New Customers
New customers are highly encouraged to use the new Unified CM-centric deployment model. Customers who have already purchased VCS, however, are recommended to follow the original CMR Hybrid deployment model with bridges registered to VCS Control.
Required Products for Cisco CMR Hybrid
This section lists the specific products required for Cisco CMR Hybrid.
In Table 1 below, each product and the specific version required are provided.
Note Unified CM is only required if you are going to deploy Cisco CMR Hybrid with endpoints registered to Unified CM.
Table 1 Required Products for Cisco CMR Hybrid
Cisco WebEx Meeting Center
Note For best performance, Cisco highly recommends enabling Globally Distributed Meetings (GDM) on the WebEx site.
WBS29.11 or later
Cisco TelePresence Management Suite (TMS)
14.6 or later
Cisco TelePresence Management Suite Provisioning Extension (TMSPE)**
Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE)***
Cisco TelePresence Conductor
XC3.0.2 required for TSP audio
Either of the following call control products:
Cisco TelePresence Video Communication Server (VCS)
X7.2.3 or later is supported for H.323 registration
Cisco Expressway (Required for the Unified CM-centric deployment model)
Note Traversal licenses are still required with Expressway when doing business-to-business or business-to-consumer calls.
Note A Unified CM license is required to purchase Cisco Expressway.
Cisco Unified Communications Manager (Unified CM)
Required for deployments with bridges trunked to Unified CM
Optional for deployments with bridges registered to VCS Control
10.5.1 is required for Microsoft Lync interoperability.
Cisco TelePresence Server (TS)*
*Customers can deploy either MCU or TS or both. At least one MCU or TS must be deployed for Cisco CMR Hybrid to work.
**Required for scheduling with Cisco WebEx Smart Scheduler.
***Required for scheduling with Cisco WebEx and TelePresence Integration to Outlook.
Ordering and Deploying CMR Hybrid
Please work with an approved partner or your Cisco account team to order and deploy CMR Hybrid.
To order and deploy CMR Hybrid, follow these steps:
Step 1 Submit an Assessment to Quality (A2Q) form using the online tool, available from the Cisco account team.
Step 2 After the A2Q form is approved, your WebEx Meeting Center site is provisioned for CMR Hybrid.
Note A WebEx site provisioning form is no longer required. A sales order form is no longer required for customers deploying TMS 14.4 or later and TelePresence Server 4.0 or later. No additional licensing for these is required.
Step 3 After your WebEx site is provisioned for CMR Hybrid, your deployment partner configures your TelePresence infrastructure components to complete the deployment.
CMR Hybrid Deployment Playbook
A comprehensive, step-by-step guide for partners deploying CMR Hybrid is available in the CMR Hybrid Community:
VCS Expressway must be assigned a static IP address.
Firewall must have port 5061 open to allow access to Expressway.
If this port is not configured correctly, calls will not take place correctly.
Cisco WebEx and TelePresence Integration to Outlook Requirements
The following section provides the requirements for meeting organizers to schedule meetings using the WebEx and TelePresence Integration to Outlook.
WebEx and TelePresence Integration to Outlook requires one of the following Microsoft Outlook versions:
Microsoft Outlook 2007 for Windows
Microsoft Outlook 2010 for Windows
Scheduling with Microsoft Outlook for Mac is not supported at this time. Mac users can schedule meetings using Smart Scheduler or TMS.
Scheduling using the Outlook plug-in provided with another version of the WebEx Productivity Tools is not supported when the WebEx and TelePresence Integration to Outlook is installed. Only one plug-in can be installed and used on a single computer.
The WebEx and TelePresence Integration to Outlook works with WebEx Meeting Center only. WebEx Meetings is not supported at this time.
The WebEx and TelePresence Integration to Outlook does not currently support sending HTML email invitations.
For information about scheduling CMR Hybrid meetings with the WebEx and TelePresence Integration to Outlook, see the:
The WebEx and TelePresence Integration to Outlook allows a WebEx user to assign a delegate to schedule or edit meetings on their behalf.
For example, if you need to host WebEx meetings on a regular basis, you can give your assistant permission to schedule meetings for you.
After being given permission, your delegate can schedule, edit, cancel, and start meetings for you.
To assign a delegate to schedule meetings for you, you must do both of the following:
1. On your WebEx site, give the delegate scheduling permission.
2. In Microsoft Outlook, share your calendar with the delegate.
For details on how to assign a delegate to schedule meetings for you and how to schedule meetings for another host, refer to the following chapters in the WebEx and TelePresence Integration to Outlook User Guide provided by Cisco:
Chapter 3, “Assigning a Delegate to Schedule WebEx Meetings for You”
Chapter 4, “Scheduling for Another Host”
This information is also available in the online help for the WebEx and TelePresence Integration to Outlook in Microsoft Outlook.
To access the help, do the following:
In the main Microsoft Outlook window, click the Schedule Meeting menu and select Help.
Cisco Smart Scheduler Requirements
The following section provides the requirements for meeting organizers to schedule meetings using Cisco Smart Scheduler.
Smart Scheduler requires one of the following browsers:
Internet Explorer - version 9 or later
Mozilla Firefox - version 15 or later
Safari - version 6.0.2 or later
Chrome - version 24 or later
For information about scheduling CMR Hybrid meetings with Cisco Smart Scheduler, see the:
Configuring Early Offer is required for a Unified CM-centric deployment, where bridges are trunked and endpoints are registered to Unified CM. For details, refer to the Configuring Call Control chapter of the:
WebEx Hybrid Audio plans for CMR Hybrid may be provisioned for generating a PSTN call from the MCU/TelePresence Server for the audio stream from the TelePresence participants. Please make sure that a valid call-path exists from your MCU/TelePresence Server through an ISDN GW or similar, commonly found in Unified CM deployments.
Endpoint Compatibility for Features
Any standard SIP and H.323 video device registered to VCS or Unified CM can be part of the meeting as long as it can connect to either the MCU or the TelePresence Server. For details, refer to the release notes for MCU and TelePresence Server.
One-Button-to-Push (OBTP) and Automatic Connect are the supported dialing methods (Conference Types) that TMS uses to connect endpoints to a meeting. With OBTP, participants join the meeting using a button on the endpoint. With Automatic Connect, TMS automatically dials and connects endpoints at the start of the meeting.
Table 2 TMS Conference Types Supported by Cisco TelePresence Endpoints
CTS and TX-series endpoints
SX-20, EX, MX, or C-series endpoints registered to Unified CM
SX-20, EX, MX or C-series endpoints registered to VCS
MXP series, T150 and E20 endpoints
NO (Manual Dial)
Jabber, Jabber Video, WebEx Meeting Center and Mobile Clients
One Button to Click
Unsupported third-party endpoints
YES (MCU out-dials endpoint)
Note As there is only one conference type per meeting, OBTP and Automatic Connect cannot be set for the same meeting. If the meeting organizer schedules a meeting using OBTP and includes endpoints that do not support OBTP, a meeting participant using an endpoint that does not support OBTP must manually dial a call-in number or URI from that endpoint to join the meeting. All other endpoints that support OBTP will be able to press a single button on the phone, touch panel or remote control to join the meeting.
WebEx Meeting Center Requirements
This section provides the requirements for WebEx Meeting Center:
To send or receive video with a resolution of 720p (HD resolution), ensure that your system meets the following minimum requirements.
– A webcam capable of producing HD video. WebEx supports most webcams of this type
– A computer with at least 2 GB of RAM and a quad-core processor
– A fast, reliable network connection
– A computer with at least 2 GB of RAM and a dual-core processor
– A fast, reliable network connection
To send or receive video with a resolution of 360p (SD resolution), ensure that your system meets the following minimum requirements.
– A webcam capable of producing HD/SD video. WebEx supports most webcams of this type
– A computer with at least 1 GB of RAM and a quad-core processor
– A fast network connection
– A computer with at least 1 GB of RAM and a dual-core processor
– A fast network connection
WebEx Meeting Center for Windows - Minimum system requirements
XP 32-bit (SP3), 2003, Vista 32-bit/64-bit, Windows 7 32-bit/64-bit
One of the following browsers:
– Internet Explorer 6, 7, 8, 9 (IE 9 supports Windows 7 only)
– Firefox: latest (32-bit)
– Chrome: latest
Sun Java 5 or higher
Recommend ActiveX be enabled for Internet Explorer
Intel or AMD processor (1GHz or faster)
At least 512 MB RAM (at least 2 GB RAM for Vista)
WebEx Meeting Center for Mac - Minimum system requirements
Mac OS X 10.5, 10.6, 10.7, 10.8
One of the following browsers:
– Safari 4/5/5.1
– Firefox latest
– Chrome latest
Apple Java 5 or higher
At least 512 MB RAM
Supported Screen Resolutions for Presentation Sharing
To utilize the full screen while presenting, Cisco recommends setting your computer to a 4:3 aspect ratio screen resolution. The following screen resolutions are recommended:
1024 x 768
1152 x 864
1280 x 1024
1600 x 1200
Mobile Client Support
iOS and Android WebEx Mobile clients release 5.0 now support TelePresence-enabled WebEx meetings. They can receive and send video, and they can display the content shared by TelePresence, Windows and Mac WebEx participants, but they cannot share content in TelePresence-enabled WebEx meetings.
BlackBerry clients can join on audio, but cannot send or receive video or display or content share.
Table 3 Mobile Client Support
Send Audio to TelePresence
Send Video to TelePresence
Share Content to TelePresence
Receive Audio from TelePresence
Receive Video from TelePresence
Display Content from TelePresence
Send/Receive Video via Cellular
WebEx Session Type
* Sending and receiving video with the BlackBerry 10 mobile client is not supported.
Recurring WebEx-enabled meetings are supported with the following exceptions:
Cisco Smart Scheduler does not support making changes to a single instance of a recurring meeting.
WebEx cannot be added to single instance of a non-WebEx-enabled recurring meeting.
WebEx cannot be removed from a single instance of a WebEx-enabled recurring meeting.
Rescheduling the time of a single instance of a recurring WebEx-enabled meeting is not supported.
Deleting an instance of a recurring WebEx-enabled meeting is not supported.
Removing rooms from a single instance of a recurring meeting is supported using Cisco TMS only.
Although exceptions to a recurring meeting series will be supported for WebEx-only meetings on CMR Hybrid sites in WBS29.11, changes to a single instance of a recurring meeting (exceptions) are not supported in WBS29.11 for CMR Hybrid meetings. Creating an exception meeting in a meeting series either using Cisco TelePresence Management Suite (TMS)-based scheduling methods (Cisco TelePresence Management Suite Administrator, Cisco Smart Scheduler, and so on.), or using mobile calendars synced to Microsoft Exchange that connect to TMS may result in meetings where the WebEx portion of the meeting cannot be joined through WebEx applications if the exception falls beyond the last regular meeting occurrence in the meeting series.
Cisco CMR Hybrid Features
Scheduling Meetings Using the TMS Admin Booking UI
One-Button-to-Push and Auto Connect conference types supported.
Scheduling Meetings Using the Smart Scheduler UI
Scheduling Meetings Using the WebEx and TelePresence Integration to Outlook
WebEx Audio via SIP or PSTN
TSP Audio via PSTN
WebEx Account Single Sign On (SSO)
Two-way Video and Content Share
Scheduling Using WebEx Scheduling Mailbox
Using any mail client that supports Microsoft Exchange, invite TelePresence rooms and a specific WebEx scheduling email address to create a CMR Hybrid meeting.
Cisco CMR Hybrid Meeting Experience
This section provides a basic overview of the end user experience of the following:
At the scheduled start time of the meeting, the MCU/TS calls into WebEx.
– If the WebEx host has not joined the meeting, the MCU/TS becomes the default WebEx host.
TelePresence participants join the meeting.
– If meeting was scheduled using Auto Connect, TMS dials and connects each supported endpoint.
– If meeting was scheduled using One-Button-to-Push (OBTP), participants using endpoints that support OBTP press the button to join the meeting.
– Participants using endpoints that don’t support either Auto Connect or OBTP, join the meeting by dialing the video dial-in number listed in the meeting invitation.
WebEx Participants join the meeting.
– The WebEx host and attendees click the Join Using WebEx button or link in the meeting invitation.
– If a WebEx participant is currently connected to a TelePresence system, a message appears asking them if they are currently sharing a presentation using TelePresence and provides them the option to continue sharing on TelePresence.
Note Starting a meeting early is supported using the Setup Buffer setting when scheduling the meeting in TMS. The WebEx host may start the WebEx portion of the meeting early, whether or not any TelePresence participants have joined the call.
During the Meeting
During the meeting, participants have the following experience:
TelePresence participants see and hear WebEx participants.
– If WebEx participants do not have a camera or their camera is turned off, a black silhouette is displayed to WebEx and TelePresence participants and WebEx participants when they are the active speaker.
WebEx participants see and hear TelePresence participants.
– In the default Meeting Center view, WebEx participants see the active speaker from either WebEx or TelePresence.
– In the Meeting Center full screen view, WebEx participants see the active speaker from either WebEx or TelePresence in a large image and the other WebEx participants in a row of smaller images below the active speaker.
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. The WebEx host cannot see a complete list of all WebEx and TelePresence participants.
– In the Meeting Center full screen view, the “TelePresence systems” participant appears as a black silhouette, as shown in Figure 1
Figure 1 “TelePresence systems” in Full Screen View
TelePresence users share a presentation by simply plugging in their computer to the display cable of the endpoint and (if required) pressing a presentation button to start content sharing to TelePresence and WebEx.
WebEx users share a presentation by taking the ball and then selecting the content to present. If the WebEx site does not allow WebEx participants to take the presenter ball, then the WebEx host must pass the ball to the WebEx participant.
The WebEx host may mute all or individual WebEx participants, however it is not possible for the host to mute the TelePresence participants.
When a WebEx participant who joined via audio speaks, the video of the last active WebEx participant who has video turned on is displayed instead of a silhouette image.
The link bandwidth between MCU/TS 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 WebEx 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. The minimum bit rate a WebEx application must process from the WebEx Cloud to be able to receive both video and application or screen sharing (formerly called “desktop sharing”) content is 1.2 Mbps. Less than that will result in the WebEx application showing only the shared application or screen.
TelePresence Server, 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.
Ending the Meeting
Behavior of how a meeting ends depends on the following four factors:
1. If the meeting organizer sets Extend Mode when scheduling the meeting in TMS to allow the meeting to extend beyond its scheduled end time
2. If Resource Availability Check on Extension is enabled in TMS, with Extend Conference Mode set to Automatic Best Effort or Endpoint Prompt and configured to use the Conference Type: No Connect or One Button To Push.
3. When the WebEx host leaves the meeting
4. When the MCU/TS leaves the meeting
Note Extending a meeting is supported for both TelePresence and WebEx using the Extend Mode setting when scheduling a meeting in TMS.
Ending the Meeting at the Scheduled End Time
The meeting ends at the scheduled end time under any of the following circumstances:
The WebEx host ends the meeting at the scheduled end time of the meeting.
The meeting organizer, when scheduling the meeting in TMS, did not set the meeting to extend.
The TelePresence portion of the meeting ends if there are not enough video ports available to extend the TelePresence portion of the meeting.
The TelePresence portion of the meeting ends if Extend Conference Mode in TMS is not set to enable extension of the meeting.
Extending the Meeting Beyond the Scheduled End Time
The meeting extends beyond the scheduled end time under any of the following circumstances:
The TelePresence meeting extends if the meeting organizer, when scheduling the meeting in TMS, sets the meeting to extend and there are resources available to extend the meeting.
The TelePresence meeting extends if Resource Availability Check on Extension is enabled in TMS, in conjunction with Extend Conference Mode set to Automatic Best Effort or Endpoint Prompt and must only be used with the Conference Type: No Connect or One Button To Push.
The WebEx meeting extends if the host stays in the meeting after the scheduled end time of the meeting.
Note TelePresence meeting extension is not guaranteed. If resources (ports) are fully booked at the scheduled end time of the meeting, the TelePresence meeting will end.
The following are known issues in CMR Hybrid:
Symptoms: TMS Scheduled CMR Hybrid meetings using TSP audio that are hosted on a TelePresence Server behind TelePresence Conductor fail to send audio between the TSP bridge and the TelePresence bridge.
Conditions: Conductor XC3.0 with any version of a remotely managed TelePresence Server
Additional Information: Caused by the TelePresence Conductor including the audioIndex parameter in the wrong portion of the message it sends to set up the TS-WebEx call group. As a result, the TelePresence Server continues to listen for SIP audio from the main WebEx call and ignores the TSP bridge.
Issue fixed in Conductor XC3.0.2.
Symptom: TelePresence dials into the wrong audio conference.
Conditions: WebEx Meeting Center Site (version WBS29.10 or WBS28.12EP21) provisioned with CMR Hybrid and TSP audio. Use Productivity Tools plug-in to schedule meetings via Microsoft Outlook for Windows. Select audio account 2 and schedule meeting. Expected results would be that the DTMF dial sequence will return with dial sequence for audio account 2, but the actual results are that the DTMF dial sequence returns with audio account 1 information.
Workaround: Upgrade WebEx Meeting Center site to WBS29.12.
Issue fixed in WebEx Meeting Center WBS29.12.
Symptom: CMR Hybrid dials the phone number from the wrong TSP audio account.
Conditions: WebEx Meeting Center site version: WBS29.10EP1. If two or more TSP audio accounts are configured in a host account, and the one marked as default is not the bottom one, CMR Hybrid will dial the phone number from the bottom (wrong) TSP audio account.
Workaround: Upgrade WebEx Meeting Center site to WBS29.10EP3.
Issue fixed in WebEx Meeting Center WBS29.10EP3.
Symptom: MCU/TelePresence Server displays random WebEx characters during CMR Hybrid meeting. Random user ID string displayed as username of TelePresence Server/MCU.
Conditions: MCU/TelePresence Server registered to Unified CM 10.5.1.
Workaround: Register MCU/TelePresence Server to VCS instead of Unified CM.
Additional Information: WebEx implemented the addition of the “display name” of “Cisco WebEx meeting” in the Contact header of 200 Ok response to the INVITE. VCS B2BUA only supports “display name” in the To header of 200ok. B2BUA filters out “Display name” in the Contact and will not pass through PAI and RPID it received. As the workaround, Cisco configures the CUSP from the WebEx cloud side to insert a Display name “Cisco WebEx Meeting” in the To header in 200 Ok before 200 Ok is forwarded to the VCS on the customer’s premises.
Symptom: User cannot add WebEx to or remove WebEx from an instance of a recurring TelePresence meeting.
Conditions: Meeting organizer schedules recurring TelePresence meeting. Meeting organizer attempts to add WebEx to or remove WebEx from an instance of the recurring meeting.
For a complete list of caveats for the individual hardware components in Cisco CMR Hybrid, refer to the release notes for each on Cisco.com.
What’s Not Supported in Cisco CMR Hybrid
The following are not supported in the Cisco CMR Hybrid solution:
Third Party Audio without TSP Link
Cisco TelePresence Multipoint Switch (CTMS)
The Cisco TelePresence Multipoint Switch (CTMS) is not a supported conferencing component for Cisco CMR Hybrid meetings. Customers who must use CTMS, must continue to use Cisco TelePresence WebEx OneTouch 1.0 for combined WebEx and TelePresence meetings.
Existing TelePresence WebEx OneTouch 1.0 customers who want to use CMR Hybrid will have to migrate from CTS-Manager and CTMS to TMS and TelePresence Server and/or MCU. Contact Cisco for more information.
Cisco Unified Video Conferencing (CUVC)
Third-party MCU or conferencing bridges, including:
– Radvision, Avaya, Polycom, etc.
WebEx Training Center, Event Center, Sales Center and Node
WebEx MeetingPlace, WebEx Meetings, Cisco WebEx Meetings Server