May 12, 2020 | view(s) | people thought this was helpful
Overview of One Button to Push (OBTP)
Set up One Button to Push (OBTP) so that when a scheduled meeting includes video devices, a green Join button appears on the devices right before the meeting begins, just as it does in the Cisco Webex Teams app.
Overview of One Button to Push (OBTP)
One Button to Push on Video Devices and Webex Boards
Users can schedule meetings and include video devices and Webex Boards that display the Join button by using any of these methods:
To provide One Button to Push on video devices, you deploy the Cisco Webex Hybrid Calendar Service. The details of the deployment depend on the type of calendar environment that you have, and on the
type of device.
One Button to Push Availability for Different Types of Meetings
The following tables show the situations in which the Hybrid Calendar Service can provide OBTP to either premises or cloud-registered
endpoints, depending on the calendar integration.
Table 1. Microsoft Exchange or Office 365 (Expressway-based Calendar Connector)
May 12, 2020| view(s) | people thought this was helpful
One Button to Push with Microsoft Exchange
One Button to Push with Microsoft Exchange
OBTP for Cloud-Registered Devices
How OBTP Works with Cloud-Registered Devices
Figure 1. OBTP for cloud-registered devices with the Expressway-based Calendar Connector
A user schedules a meeting using a keyword or video address, and invites a cloud-registered video endpoint by its room resource
calendar.
If the endpoint is available at that time, typically Microsoft Exchange automatically accepts the invitation on its behalf.
EWS notifications from Exchange alert the Calendar Connector that a meeting has been scheduled.
For Cisco Webex meetings, the Hybrid Calendar Service retrieves the join details from the Cisco Webex cloud and updates the
meeting invitation.
Just before the meeting time, cloud-registered devices receive OBTP information from the cloud.
OBTP for Cloud-Registered Devices Deployment Task Flow
Before you begin
If you haven't yet set up the Hybrid Calendar Service, see the Deployment Guide for Cisco Webex Hybrid Calendar Service instead of this article. If you've already got the service running, proceed with these instructions to add OBTP for cloud-registered
room devices and boards.
Schedule a meeting from the calendar and add a cloud-regisetered device.
Add the Hybrid Calendar Service to Places with Webex Room, Desk, and Board Devices
Before you begin
This task assumes that you've already created places for the Webex Room, Desk, or Board devices. If you need to create the
places, see Add Shared Devices to a Place.
1
From the customer view in https://admin.webex.com, go to Places, and then choose the place that you want to update.
2
Click Edit.
3
Toggle on the calendar service so that people can use One Button to Push (OBTP) from their Cisco Webex devices, and then click
Next.
4
Enter or paste the email address of the room mailbox. (For help locating this email address, see "Create and manage room mailboxes"
on the Microsoft Docs web site.)
This is the email address that will be used to schedule meetings.
5
Click Save.
Have Users Associate Their Personal Rooms with Cisco Webex Teams
To provide OBTP to Cisco Webex room and desk devices and Webex Boards when scheduling Webex Personal Room meetings, users must have their Personal Room
associated with their Cisco Webex Teams account. This can happen in one of the following ways:
The Webex site is managed on Cisco Webex Control Hub.
Users associate their Personal Room with Cisco Webex Teams for themselves.
Do this task for the test user account that you'll use to verify the setup, to check whether the Personal Room association
needs to be added.
1
Sign into the Cisco Webex Teams app.
2
Go to Meetings.
3
Under My Personal Room, if the Personal Room link is missing, enter it in the format https://company.webex.com/meet/username or company.webex.com/meet/username, enter your host PIN, and select Save.
In Outlook, Outlook Web Access, or https://mail.office365.com, create a new meeting, and then add @meet or @webex to the Location field.
2
Go to the Scheduling Assistant and click Add room, and choose the device you want to add.
3
Fill out other meeting information as needed, and send the invitation.
4
When the meeting is scheduled to begin, verify that the Join button appears on the device.
OBTP for Premises-Registered Devices
How OBTP Works with Premises-Registered Devices
Figure 2. OBTP for premises-registered devices with the Expressway-based Calendar Connector
A user schedules a meeting using a keyword or video address, and invites a premises-registered video endpoint by its room
resource calendar.
If the endpoint is available at that time, typically Microsoft Exchange automatically accepts the invitation on its behalf.
EWS notifications from Exchange alert the Calendar Connector and Cisco TMSXE that a meeting has been scheduled.
For Cisco Webex meetings, the Hybrid Calendar Service retrieves the join details from the Cisco Webex cloud and updates the
meeting invitation.
The Calendar Connector populates the description field with all available join details, and sets the value of the user attribute
"TMS:ExternalConferenceData" to the meeting's SIP URI.
EWS notifications from Exchange alert Cisco TMSXE of a meeting update.
Cisco TMSXE updates the meeting in Cisco TMS to Externally Hosted and sets the OBTP dial string.
Cisco TMS sends OBTP information for upcoming meetings to the endpoints.
Set up OBTP for Premises-Registered Devices
For premises-registered endpoints, OBTP works with Hybrid Calendar Service and the Productivity Tools plugin for meeting invitations:
Hybrid Calendar Service (scheduling keywords or supported video address) populates the user attribute "TMS:ExternalConferenceData"
with the SIP URI for TMS to set the OBTP dial string.
The Productivity Tools plugin populates the attribute "UCCapabilities" attribute with the SIP URI for TMS to set the OBTP
dial string.
TMS and XE Licensing is the same as if using on-premises resources. You require enough licenses to cover the number of endpoints
that will use OBTP. A TMS license is needed to manage the endpoint and to push the speed dial button on the touchpad at the
time of the scheduled conference. A TMS-XE license is needed for the endpoint to be scheduled in Exchange.
4
If you plan to deploy a hybrid Exchange environment with Office 365, enable TNEF for remote domains in Exchange Online. Having
TNEF disabled causes Exchange Online to strip the TMS:ExternalConferenceData and UCCapabilities attributes, breaking OBTP
for Unified CM-registered endpoints.
If you have on-premises conferencing, you can add OBTP with Cisco Webex Meetings and run both at same time. We support OBTP
functionality only; auto connect is not available.
Troubleshoot One Button to Push on Video Devices
No Join Button on Premises-Registered Devices
Problem In a hybrid Exchange environment, the Join button does not appear on any premises-registered device.
Possible Cause In hybrid Exchange environments, disabling TNEF for remote domains causes Exchange Online to strip the TMS:ExternalConferenceData
and UCCapabilities user attributes for the meeting. This breaks OBTP for Unified CM-registered endpoints. Without these attributes,
Cisco TMSXE cannot update the meeting in Cisco TMS, and Cisco TMS cannot set the OBTP dial string for the meeting.
Problem A device does not show the join button when meetings are about to start.
Possible Cause The device does not automatically accept meeting invitations.
Solution Check the resource calendar for the device, and see if it has accepted the meeting invitation. If not, configure the device's
resource mailbox to automatically accept meeting requests.
ProductWebex Boards, Webex Control Hub, Webex Hybrid Services
May 12, 2020| view(s) | people thought this was helpful
One Button to Push with Office 365
One Button to Push with Office 365 (Cloud-Based Service)
OBTP for Cloud-Registered Devices
How OBTP Works with Cloud-Registered Devices
Figure 1. OBTP for cloud-registered devices with the Hybrid Calendar Service for Office 365
A user schedules a meeting using a keyword or video address, and invites a cloud-registered video endpoint by its room resource
calendar.
If the endpoint is available at that time, typically Office 365 automatically accepts the invitation on its behalf.
The Microsoft Graph API posts a notification alerting the Hybrid Calendar Service that a meeting has been scheduled.
For Cisco Webex meetings, the Hybrid Calendar Service retrieves the join details from the Cisco Webex cloud and updates the
meeting invitation.
Just before the meeting time, cloud-registered devices receive OBTP information from the cloud.
OBTP for Cloud-Registered Devices Deployment Task Flow
Before you begin
If you haven't yet set up the Hybrid Calendar Service, see the Deployment Guide for Cisco Webex Hybrid Calendar Service instead of this article. If you've already got the service running, proceed with these instructions to add OBTP for cloud-registered
room devices and boards.
Schedule a meeting from the calendar and add a cloud-registered device.
Add the Hybrid Calendar Service to Places with Webex Room, Desk, and Board Devices
Before you begin
This task assumes that you've already created places for the Webex Room, Desk, or Board devices. If you need to create the
places, see Add Shared Devices to a Place.
1
From the customer view in https://admin.webex.com, go to Places, and then choose the place that you want to update.
2
Click Edit.
3
Toggle on the calendar service so that people can use One Button to Push (OBTP) from their Cisco Webex devices, and then click
Next.
4
Enter or paste the email address of the room mailbox. (For help locating this email address, see "Create and manage room mailboxes"
on the Microsoft Docs web site.)
This is the email address that will be used to schedule meetings.
5
Click Save.
Have Users Associate Their Webex Personal Rooms with Cisco Webex Teams
To provide OBTP to Cisco Webex room and desk devices and Webex Boards when scheduling Webex Personal Room meetings, users must have their Personal Room
associated with their Cisco Webex Teams account. This can happen in one of the following ways:
The Webex site is managed on Cisco Webex Control Hub.
Users associate their Personal Room with Cisco Webex Teams for themselves.
Do this task for the test user account that you'll use to verify the setup, to check whether the Personal Room association
needs to be added.
1
Sign into the Cisco Webex Teams app.
2
Go to Meetings.
3
Under My Personal Room, if the Personal Room link is missing, enter it in the format https://company.webex.com/meet/username or company.webex.com/meet/username, enter your host PIN, and select Save.
Use these steps to set up a test meeting and verify OBTP on a registered device.
1
In Outlook, Outlook Web Access, or https://mail.office365.com, create a new meeting, and then add @meet or @webex to the Location field.
2
Go to the Scheduling Assistant and click Add room, and choose the device you want to add.
3
Fill out other meeting information as needed, and send the invitation.
4
When the meeting is scheduled to begin, verify that the Join button appears on the device.
OBTP for Premises-Registered Devices
How OBTP Works with Premises-Registered Devices
Figure 2. OBTP for premises-registered devices with the Hybrid Calendar Service for Office 365
The organizer creates a meeting in Office 365 and then adds @meet in the Location field. The organizer invites users and video devices from the Office 365 directory.
Office 365 sends a notification to the Hybrid Calendar Service.
The Hybrid Calendar Service requests and receives the encryption key, and then uses it to encrypt the meeting information.
The Hybrid Calendar Service validates meeting creation and recipients and the Calendar Connector sends details to Cisco TMS.
The Cisco TMS creates the meeting on the on-premises conference bridge and sends the join details back to the Calendar Connector.
The connector updates the meeting invitation with the join details that are provided by Cisco TMS, and the updated join details
appear when invitees view the meeting in Office 365.
Just before the meeting time, the video devices that were invited to the meeting receive OBTP information from the Cisco TMS.
Cisco TMSXE is not part of this integration. The Calendar Connector handles the role of coordinating between Cisco TMS and
the calendar system.
Requirements for the Cisco TMS Integration
This integration requires the following components:
The cloud-based Hybrid Calendar Service with Office 365, deployed and configured
Cisco TelePresence Management Suite (TMS) 15.9 or later, installed and running, with the following configuration in place:
A valid CA-signed server certificate must be installed. This integration does not support self-signed certificates.
Each endpoint to be booked must already be added to Cisco TMS and licensed for general Cisco TMS usage.
The Cisco TMS must have the same option key that is required to book endpoints with Cisco TMSXE, which is either of the following:
Small deployments—One Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE) option key for every 25
telepresence endpoints that are integrated with Cisco TMS (part number L-TMS-MSEX-25).
Larger deployments—One Application Integration Package option key (part number L-TMS-APPINT).
If both types of option key are present, Cisco TMS only uses the Application Integration Package key.
If you already have TMSXE or Application Integration Package option keys:
If you are not currently using the option key, you can use it with the Hybrid Calendar Service integration.
If you are using the option key with Cisco TMSXE, contact your partner or sales team to request a second option key (or set
of keys) for the Hybrid Calendar Service integration. If you plan to migrate from Cisco TMSXE within a short period of time,
you can request a 90 day trial, and then reuse your original option key(s) once the migration to the Hybrid Calendar Service
is complete.
On-premises conference bridge resources, if used for this integration, must be configured (Cisco Meeting Server recommended).
Users' time zones in Cisco TMS must match their time zones in the calendar system. For instructions on setting the time zone
in Cisco TMS, see "User Administration" in the applicable Cisco TelePresence Management Suite Administrator Guide.
A single Cisco Expressway node (to serve as the Connector host between your Cisco TMS and the Hybrid Calendar Service), installed
and running
We currently support only a single Expressway node dedicated to hosting this integration. The node must not be running any
other hybrid service connectors. Also, this node must be the only Calendar Connector host in your Cisco Webex organization.
We recommend a maximum of 10,000 scheduling users for this integration.
Deployment Task Flow for the Cisco TMS Integration
To add the Cisco TMS integration to your Hybrid Calendar Service with Office 365 deployment, perform the following tasks.
Before you begin
If you haven't yet set up the Hybrid Calendar Service, see the Deployment Guide for Cisco Webex Hybrid Calendar Service instead of this article. If you've already got the service running, proceed with these instructions to add OBTP for premises-registered
devices.
Maps video device systems in Cisco TMS to the email addresses of Office 365 room mailboxes, so that the Hybrid Calendar Service
can recognize when users invite the devices to meetings and coordinate OBTP with Cisco TMS.
Connects your Expressway to the Cisco Webex cloud. This creates a resource in https://admin.webex.com and downloads connector software on to the Expressway.
Configures the details that the Calendar Connector needs to communicate with Cisco TMS and adds on-premises conference bridge
telephony details to invitations, if applicable.
Provide the following port access for the Expressway that will serve as your Calendar Connector host for the Cisco TMS integration:
Port access for HTTPS or secure web sockets outbound from Expressway to *.rackcdn.com, *.ciscospark.com, *.wbx2.com, *.webex.com,
*.webexcontent.com, and *.clouddrive.com: TCP port 443 (secure)
Port access for HTTPS outbound from Expressway to Cisco TMS: TCP port 443 (secure)
Configure the @meet Keyword Action
Do these steps if you want to have the integration schedule a meeting that is hosted with on-premises conference bridge resources
when users use this keyword.
By default, the @meet keyword creates a space in Cisco Webex Teams and adds join details for it.
With the Cisco TMS integration, when a scheduler invites a room to the meeting, Cisco TMS books the room and sends OBTP to
the associated devices. OBTP works regardless of how you configure the @meet keyword, and it also works for @webex.
From the Hybrid Calendar card for Exchange, click Edit settings.
3
In the Keywords section, for @meet, choose Cisco TelePresence Management Suite.
4
Click Save.
Configure Office 365 Room Mailboxes in Cisco TMS
Use this procedure to add the Office 365 room mailbox addresses of video devices one at a time in Cisco TMS. Alternatively,
you can use Bulk Upload to configure multiple addresses. For instructions, see "Bulk Room Email Mapping for Endpoints" in
the applicable Cisco TelePresence Management Suite Administrator Guide.
Before you begin
Each video system that users want to add to meetings must have a room mailbox in Office 365 in order for Cisco TMS to provide
OBTP. For help creating room mailboxes, see Creating and managing resource mailboxes in Office 365.
Gather the credentials of an organization domain account with Admin privileges to Cisco TMS.
1
If you have not already done so, create the room mailboxes in Office 365.
2
From a web browser, sign in to Cisco TMS.
3
Go to Systems > Navigator.
4
Locate and click the video system to configure with the room mailbox address.
5
On the Summary tab, click Edit Settings and enter the room mailbox address in the Email Address field.
6
Click Save.
7
Repeat steps 4 through 6 for each video device.
Register Expressway-C Connector Host to the Cisco Webex Cloud
Use this procedure to register a single Expressway-C node to the cloud and download connector software onto the Expressway-C. (We currently support only a single Expressway node for this integration.)
The TMS integration uses the Hybrid Calendar Service for Microsoft Exchange setup process, but ultimately you will link the
Calendar Connector to Cisco TMS. Once you link to Cisco TMS, you must not link any connector in your Cisco Webex organization
to Microsoft Exchange.
Before you begin
Make sure your Expressway-C is running on a version that's supported for hybrid services. See the Supported Versions of Expressway for Cisco Webex Hybrid Services Connectors documentation (https://help.webex.com/article/ruyceab) for more information about which versions are supported for new and existing registrations to the cloud.
Sign out of any open connections to the Expressway-C interface that are open in other browser tabs.
If your on-premises environment proxies the outbound traffic, you must first enter the details of the proxy server on Applications > Hybrid Services > Connector Proxy before you complete this procedure. Doing so is necessary for successful registration.
The Cisco Webex cloud rejects any attempt at registration from the Expressway web interface. You must first register your Expressway through
Cisco Webex Control Hub, because the Control Hub needs to hand out a token to the Expressway to establish trust between premises and cloud, and complete
the secure registration.
2
Click Set up on the Hybrid Calendar Service for Microsoft Exchange card, and then click Next.
Do not set up this integration if you already have an Expressway connector host for Microsoft Exchange or Office 365 registered
for your organization.
3
Choose Register a new Expressway with its Fully Qualified Domain Name (FQDN), enter your Expressway-C IP address or fully qualified domain name (FQDN) so that Cisco Webex creates a record of that Expressway-C and establishes trust, and then click Next. You can also enter a display name to identify the resource in Cisco Webex Control Hub.
To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Expressway-C.
Capitalization is not supported at this time.
4
Click Next, and for new registrations, click the link to open your Expressway-C. You can then sign in to load the Connector Management window.
5
Decide how you want to update the Expressway-C trust list:
A check box on the welcome page determines whether you will manually append the required CA certificates to the Expressway-C trust list, or whether you allow Cisco Webex to add those certificates for you.
Choose one of the following options:
Check the box if you want Cisco Webex to add the required CA certificates to the Expressway-C trust list.
When you register, the root certificates for the authorities that signed the Cisco Webex cloud certificates are installed automatically on the Expressway-C. This means that the Expressway-C should automatically trust the certificates and be able to set up the secure connection.
If you change your mind, you can use the Connector Management window to remove the Cisco Webex cloud CA root certificates and manually install root certificates.
Uncheck the box if you want to manually update the Expressway-C trust list. See the Expressway-C online help for the procedure.
When you register, you will get certificate trust errors if the trust list does not currently have the correct CA certificates.
See Certificate Authorities for Hybrid Services.
6
Click Register. After you're redirected to Cisco Webex Control Hub, read the on-screen text to confirm that Cisco Webex identified the correct Expressway-C.
7
After you verify the information, click Allow to register the Expressway-C for Cisco Webex Hybrid Services.
Registration can take up to 5 minutes depending on the configuration of the Expressway and whether it's a first-time registration.
After the Expressway-C registers successfully, the Cisco Webex Hybrid Services window on the Expressway-C shows the connectors downloading and installing. The management connector automatically upgrades itself if there is a newer
version available, and then installs any other connectors that you selected for the Expressway-C connector host.
Each connector installs the interface pages that you need to configure and activate that connector.
This process can take a few minutes. When the connectors are installed, you can see new menu items on the Applications > Hybrid Services menu on your Expressway-C connector host.
Troubleshooting Tips
If registration fails and your on-premises environment proxies the outbound traffic, review the Before You Begin section
of this procedure. If the registration process times out or fails (for example, you must fix certificate errors or enter proxy
details), you can restart registration in Cisco Webex Control Hub.
Certificate Authorities for Hybrid Services
The table lists the Certificate Authorities that your on-premises or existing environment must trust when using Cisco Webex Hybrid Services.
If you opted to have Cisco Webex manage the required certificates, then you do not need to manually append CA certificates to the Expressway-C trust list.
The issuers used to sign the Cisco Webex host certificates may change in future, and the table below may then be inaccurate. If you are manually managing the CA certificates,
you must append the CA certificates of the issuing authorities that signed the currently valid certificates for the hosts
listed below (and remove expired/revoked CA certificates).
To ensure Expressway downloads connectors from a trusted host
Common identity service
O=VeriSign, Inc., OU=Class 3 Public Primary Certification Authority
Windows Server 2003 or Windows Server 2008 hosting the Cisco Directory Connector
Expressway-C
To synchronize users from your Active Directory with Cisco Webex and to authenticate Cisco Webex Hybrid Services users
Cisco Webex
O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority
Expressway-C
Link the Calendar Connector to Cisco TMS
Before you begin
The Cisco TMS must have a valid CA-signed server certificate installed. This integration does not support self-signed certificates.
1
From the Expressway-C connector host, go to Applications > Hybrid Services > Calendar Service > Cisco Conferencing Services Configuration, and then click New.
2
Select Type as TMS under Conferencing Services Type.
3
Enter the username and password of the Cisco TMS administrator account that you want the Calendar Connector to use to connect to Cisco TMS.
Enter only the username, without the domain, in the username field.
4
Under TMS Server Details, enter the fully qualified domain name (FQDN) and domain in the respective fields.
Enter the NETBIOS domain name for the TMS Domain Name field.
5
Under Telephony Invite Details, enter the appropriate information for Toll Identifier, Toll Number, Toll Free Identifier, Toll Free Number, and Global Call-in Numbers (URL).
6
Click Save.
Cisco TMS is listed under Cisco Conferencing Services Configuration.
7
Click Cisco TMS and click Test Connection.
The Calendar Connector tests the connection to the Cisco TMS environment. If the test returns an error message, correct any errors in the configuration
and try the test again.
8
When you've confirmed the connection, go to Applications > Hybrid Services > Connector Management and click Calendar Connector Service.
9
Select Enabled from the Active drop-down list and click Save.
The Calendar Connector starts and the status changes to Running.
Add a Cisco Meeting Server to Cisco TMS
When you configure @meet to use the Cisco TelePresence Management Suite action, the Cisco TMS uses any bridge configured in the Administrative Tools > Configuration > Conference Settings > Advanced.
To allow users to schedule meetings on a Cisco Meeting Server using the Hybrid Calendar Service integration with Cisco TMS,
add the server using the steps in the Cisco Meeting Server section of the applicable Cisco TelePresence Management Suite Administrator Guide.
Test the Office 365 and Cisco TMS Integration
Use these steps to schedule a test meeting and verify the integration.
1
Test meeting scheduling with @meet:
In a web browser, sign in to https://outlook.office365.com with an Office 365 user account that is enabled for Hybrid Calendar
Service.
Click New > Calendar event.
Enter an event title in the Add a title for the event text box.
Enter @meet in the Add a location or a room text box.
In the People tab, invite users and add rooms (or other video devices) for OBTP.
Send the invitation.
The Hybrid Calendar Service updates the meeting with the join details.
2
In a web browser, sign in to Cisco TMS and go to Booking > List Conferences.
The test meeting and other meetings that are scheduled with @meet are listed in Cisco TMS with 'Calendar Connector' in the
External Service column.
You cannot edit Calendar Connector meetings in Cisco TMS.
Troubleshoot the Cisco TMS Integration
Use these tips to check the status of the various components of the Cisco TMS integration with the Hybrid Calendar Service.
1
Verify the number of users who are enabled for the Hybrid Calendar Service in https://admin.webex.com under Services.
2
Check the status of the connectors in Control Hub.
From the customer view in https://admin.webex.com, go to Services, and then click All Resources from the on-premises resources card.
From the resource card for the Cisco TMS integration, click the Node link below the resource FQDN or IP address.
3
Compare the status above to the status of the connectors on the Expressway connector host.
From Expressway, go to Applications > Hybrid Services > Connector Management.
Notable Behavior for the Cisco TMS Integration with Office 365
This section lists limitations and notable behavior for the Cisco TMS integration with Office 365.
Editing a meeting series during an active instance of the series results in the following behavior:
Cisco TMS updates all instances other than the in-progress instance.
The currently active instance becomes an exception in Cisco TMS.
This is the expected behavior, but differs from the behavior of Office 365, which updates the active instance as well.
A meeting that is scheduled more than 5 months in the future may not get immediately processed by the cloud-based Hybrid Calendar
Service for Microsoft Office 365. The service processes meetings that are 5-6 months in the future on a daily basis using
a sliding window, so once the meeting's scheduled date falls within the window, it will get processed and the meeting scheduled
in Cisco TMS.
This is a limitation of the cloud-based Hybrid Calendar Service for Microsoft Office 365 for all types of meetings.
ProductWebex Boards, Webex Control Hub, Webex Hybrid Services
May 12, 2020| view(s) | people thought this was helpful
One Button to Push with Google Calendar
One Button to Push with Google Calendar
OBTP for Cloud-Registered Devices
How OBTP Works with Cloud-Registered Devices
Figure 1. OBTP for cloud-registered devices with the Hybrid Calendar Service for Google Calendar
A user schedules a meeting using a keyword or video address, and invites a cloud-registered video endpoint by its room resource
calendar.
If the endpoint is available at that time, typically Google Calendar automatically accepts the invitation on its behalf.
The Google Calendar API posts a notification alerting the Hybrid Calendar Service that a meeting has been scheduled.
For Cisco Webex meetings, the Hybrid Calendar Service retrieves the join details from the Cisco Webex cloud and updates the
meeting invitation.
Just before the meeting time, cloud-registered devices receive OBTP information from the cloud.
OBTP for Cloud-Registered Devices Deployment Task Flow
Before you begin
If you haven't yet set up the Hybrid Calendar Service, see the Deployment Guide for Cisco Webex Hybrid Calendar Service instead of this article. If you've already got the service running, proceed with these instructions to add OBTP for cloud-registered
room devices and boards.
Schedule a meeting from the calendar and add a cloud-registered device.
Enable Calendar Resource Access
If you did not set up calendar resource access when initially deploying the Hybrid Calendar Service with Google Calendar,
do so now.
1
From https://admin.webex.com, go to Services, find the hybrid calendar card, and then go to the Google Settings.
2
In the Google Calendar section, under Calendar resources, check the My organization uses calendar resources (such as conference devices) check box.
3
Enter the name of an authorized access control list administrator account.
Add the Hybrid Calendar Service to Places with Webex Room, Desk, and Board Devices
Before you begin
This task assumes that you've already created places for the Webex Room, Desk, or Board devices. If you need to create the
places, see Add Shared Devices to a Place.
1
From the customer view in https://admin.webex.com, go to Places, and then choose the place that you want to update.
2
Click Edit.
3
Toggle on the calendar service so that people can use One Button to Push (OBTP) from their Cisco Webex devices, and then click
Next.
4
Enter or paste the Google resource email address from G Suite (Calendar > Resources).
This is the email address that will be used to schedule meetings.
5
Click Save.
Have Users Associate Their Personal Rooms with Cisco Webex Teams
To provide OBTP to Cisco Webex room and desk devices and Webex Boards when scheduling Webex Personal Room meetings, users must have their Personal Room
associated with their Cisco Webex Teams account. This can happen in one of the following ways:
The Webex site is managed on Cisco Webex Control Hub.
Users associate their Personal Room with Cisco Webex Teams for themselves.
Do this task for the test user account that you'll use to verify the setup, to check whether the Personal Room association
needs to be added.
1
Sign into the Cisco Webex Teams app.
2
Go to Meetings.
3
Under My Personal Room, if the Personal Room link is missing, enter it in the format https://company.webex.com/meet/username or company.webex.com/meet/username, enter your host PIN, and select Save.
Use these steps to set up a test meeting and verify OBTP on a registered device.
1
In https://calendar.google.com, click Create to start an event, and then add @meet or @webex to the Where field.
2
Click Rooms, and choose the device you want to add.
3
Fill out other meeting information as needed, and then click Save.
4
When the meeting is scheduled to begin, verify that the Join button appears on the device.
OBTP for Premises-Registered Devices
How OBTP Works with Premises-Registered Devices
The following diagram illustrates how the Hybrid Calendar Service interacts with Cisco TMS and the calendar system to provide the Join button for a meeting that is hosted by on-premises conference bridge resources.
Figure 2. OBTP for premises-registered devices with the Hybrid Calendar Service for Google Calendar
The organizer creates a meeting in Google Calendar and then adds @meet in the Location field. The organizer invites users and video devices from the Google Calendar directory.
Google Calendar sends a notification to the Hybrid Calendar Service.
The Hybrid Calendar Service requests and receives the encryption key, and then uses it to encrypt the meeting information.
The Hybrid Calendar Service validates meeting creation and recipients and the Calendar Connector sends details to Cisco TMS.
The Cisco TMS creates the meeting on the on-premises conference bridge and sends the join details back to the Calendar Connector.
The connector updates the meeting invitation with the join details that are provided by Cisco TMS, and the updated join details
appear when invitees view the meeting in Google Calendar.
Just before the meeting time, the video devices that were invited to the meeting receive OBTP information from the Cisco TMS.
Cisco TMSXE is not part of this integration. The Calendar Connector handles the role of coordinating between Cisco TMS and
the calendar system.
Requirements for the Cisco TMS Integration
This integration requires the following components:
The cloud-based Hybrid Calendar Service with Google Calendar, deployed and configured
Cisco TelePresence Management Suite (TMS) 15.9 or later, installed and running, with the following configuration in place:
A valid CA-signed server certificate must be installed. This integration does not support self-signed certificates.
Each endpoint to be booked must already be added to Cisco TMS and licensed for general Cisco TMS usage.
The Cisco TMS must have the same option key that is required to book endpoints with Cisco TMSXE, which is either of the following:
Small deployments—One Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE) option key for every 25
telepresence endpoints that are integrated with Cisco TMS (part number L-TMS-MSEX-25).
Larger deployments—One Application Integration Package option key (part number L-TMS-APPINT).
If both types of option key are present, Cisco TMS only uses the Application Integration Package key.
If you already have TMSXE or Application Integration Package option keys:
If you are not currently using the option key, you can use it with the Hybrid Calendar Service integration.
If you are using the option key with Cisco TMSXE, contact your partner or sales team to request a second option key (or set
of keys) for the Hybrid Calendar Service integration. If you plan to migrate from Cisco TMSXE within a short period of time,
you can request a 90 day trial, and then reuse your original option key(s) once the migration to the Hybrid Calendar Service
is complete.
On-premises conference bridge resources, if used for this integration, must be configured (Cisco Meeting Server recommended).
Users' time zones in Cisco TMS must match their time zones in the calendar system. For instructions on setting the time zone
in Cisco TMS, see "User Administration" in the applicable Cisco TelePresence Management Suite Administrator Guide.
A single Cisco Expressway node (to serve as the Connector host between your Cisco TMS and the Hybrid Calendar Service), installed
and running
We currently support only a single Expressway node dedicated to hosting this integration. The node must not be running any
other hybrid service connectors. Also, this node must be the only Calendar Connector host in your Cisco Webex organization.
We recommend a maximum of 10,000 scheduling users for this integration.
Deployment Task Flow for the Cisco TMS Integration
To add the Cisco TMS integration to your Hybrid Calendar Service with Google Calendar deployment, perform the following tasks.
Before you begin
If you haven't yet set up the Hybrid Calendar Service, see the Deployment Guide for Cisco Webex Hybrid Calendar Service instead of this article. If you've already got the service running, proceed with these instructions to add OBTP for premises-registered
devices.
Maps video device systems in Cisco TMS to their room mailbox email addresses in Google Calendar, so that the Hybrid Calendar
Service can recognize when users invite the devices to meetings and coordinate OBTP with Cisco TMS.
Connects your Expressway to the Cisco Webex cloud. This creates a resource in https://admin.webex.com and downloads connector software on to the Expressway.
Configures the details that the Calendar Connector needs to communicate with Cisco TMS and adds on-premises conference bridge
telephony details to invitations, if applicable.
Provide the following port access for the Expressway that will serve as your Calendar Connector host for the Cisco TMS integration:
Port access for HTTPS or secure web sockets outbound from Expressway to *.rackcdn.com, *.ciscospark.com, *.wbx2.com, *.webex.com,
*.webexcontent.com, and *.clouddrive.com: TCP port 443 (secure)
Port access for HTTPS outbound from Expressway to Cisco TMS: TCP port 443 (secure)
Configure the @meet Keyword Action
Do these steps if you want to have the integration schedule a meeting that is hosted with on-premises conference bridge resources
when users use this keyword.
By default, the @meet keyword creates a space in Cisco Webex Teams and adds join details for it.
With the Cisco TMS integration, when a scheduler invites a room to the meeting, Cisco TMS books the room and sends OBTP to
the associated devices. OBTP works regardless of how you configure the @meet keyword, and it also works for @webex.
From the Hybrid Calendar card for Exchange, click Edit settings.
3
In the Keywords section, for @meet, choose Cisco TelePresence Management Suite.
4
Click Save.
Configure Google Room Mailboxes in Cisco TMS
Use this procedure to add the Google Calendar room mailbox addresses of video devices one at a time in Cisco TMS. Alternatively,
you can use Bulk Upload to configure multiple addresses. For instructions, see "Bulk Room Email Mapping for Endpoints" in
the applicable Cisco TelePresence Management Suite Administrator Guide.
Before you begin
Each video system that users want to add to meetings must have a room mailbox in Google in order for Cisco TMS to provide
OBTP. For help creating room mailboxes, see Manage Calendar resources for more information.
Make sure that you have checked the My organization uses calendar resources (such as conference devices) check box in Control Hub, and entered the name of an authorized access control list administrator account. (From https://admin.webex.com, go to Services, find the hybrid calendar card, and then go to the Google Settings.)
Gather the credentials of an organization domain account with Admin privileges to Cisco TMS.
1
If you have not already done so, create the room mailboxes in the Google Admin console.
2
From a web browser, sign in to Cisco TMS.
3
Go to Systems > Navigator.
4
Locate and click the video system to configure with the room mailbox address.
5
On the Summary tab, click Edit Settings and enter the room mailbox address in the Email Address field.
6
Click Save.
7
Repeat steps 4 through 6 for each video device.
Register Expressway-C Connector Host to the Cisco Webex Cloud
Use this procedure to register a single Expressway-C node to the cloud and download connector software onto the Expressway-C. (We currently support only a single Expressway node for this integration.)
The TMS integration uses the Hybrid Calendar Service for Microsoft Exchange setup process, but ultimately you will link the
Calendar Connector to Cisco TMS. Once you link to Cisco TMS, you must not link any connector in your Cisco Webex organization
to Microsoft Exchange.
Before you begin
Make sure your Expressway-C is running on a version that's supported for hybrid services. See the Supported Versions of Expressway for Cisco Webex Hybrid Services Connectors documentation (https://help.webex.com/article/ruyceab) for more information about which versions are supported for new and existing registrations to the cloud.
Sign out of any open connections to the Expressway-C interface that are open in other browser tabs.
If your on-premises environment proxies the outbound traffic, you must first enter the details of the proxy server on Applications > Hybrid Services > Connector Proxy before you complete this procedure. Doing so is necessary for successful registration.
The Cisco Webex cloud rejects any attempt at registration from the Expressway web interface. You must first register your Expressway through
Cisco Webex Control Hub, because the Control Hub needs to hand out a token to the Expressway to establish trust between premises and cloud, and complete
the secure registration.
2
Click Set up on the Hybrid Calendar Service for Microsoft Exchange card, and then click Next.
Do not set up this integration if you already have an Expressway connector host for Microsoft Exchange or Office 365 registered
for your organization.
3
Choose Register a new Expressway with its Fully Qualified Domain Name (FQDN), enter your Expressway-C IP address or fully qualified domain name (FQDN) so that Cisco Webex creates a record of that Expressway-C and establishes trust, and then click Next. You can also enter a display name to identify the resource in Cisco Webex Control Hub.
To ensure a successful registration to the cloud, use only lowercase characters in the hostname that you set for the Expressway-C.
Capitalization is not supported at this time.
4
Click Next, and for new registrations, click the link to open your Expressway-C. You can then sign in to load the Connector Management window.
5
Decide how you want to update the Expressway-C trust list:
A check box on the welcome page determines whether you will manually append the required CA certificates to the Expressway-C trust list, or whether you allow Cisco Webex to add those certificates for you.
Choose one of the following options:
Check the box if you want Cisco Webex to add the required CA certificates to the Expressway-C trust list.
When you register, the root certificates for the authorities that signed the Cisco Webex cloud certificates are installed automatically on the Expressway-C. This means that the Expressway-C should automatically trust the certificates and be able to set up the secure connection.
If you change your mind, you can use the Connector Management window to remove the Cisco Webex cloud CA root certificates and manually install root certificates.
Uncheck the box if you want to manually update the Expressway-C trust list. See the Expressway-C online help for the procedure.
When you register, you will get certificate trust errors if the trust list does not currently have the correct CA certificates.
See Certificate Authorities for Hybrid Services.
6
Click Register. After you're redirected to Cisco Webex Control Hub, read the on-screen text to confirm that Cisco Webex identified the correct Expressway-C.
7
After you verify the information, click Allow to register the Expressway-C for Cisco Webex Hybrid Services.
Registration can take up to 5 minutes depending on the configuration of the Expressway and whether it's a first-time registration.
After the Expressway-C registers successfully, the Cisco Webex Hybrid Services window on the Expressway-C shows the connectors downloading and installing. The management connector automatically upgrades itself if there is a newer
version available, and then installs any other connectors that you selected for the Expressway-C connector host.
Each connector installs the interface pages that you need to configure and activate that connector.
This process can take a few minutes. When the connectors are installed, you can see new menu items on the Applications > Hybrid Services menu on your Expressway-C connector host.
Troubleshooting Tips
If registration fails and your on-premises environment proxies the outbound traffic, review the Before You Begin section
of this procedure. If the registration process times out or fails (for example, you must fix certificate errors or enter proxy
details), you can restart registration in Cisco Webex Control Hub.
Certificate Authorities for Hybrid Services
The table lists the Certificate Authorities that your on-premises or existing environment must trust when using Cisco Webex Hybrid Services.
If you opted to have Cisco Webex manage the required certificates, then you do not need to manually append CA certificates to the Expressway-C trust list.
The issuers used to sign the Cisco Webex host certificates may change in future, and the table below may then be inaccurate. If you are manually managing the CA certificates,
you must append the CA certificates of the issuing authorities that signed the currently valid certificates for the hosts
listed below (and remove expired/revoked CA certificates).
To ensure Expressway downloads connectors from a trusted host
Common identity service
O=VeriSign, Inc., OU=Class 3 Public Primary Certification Authority
Windows Server 2003 or Windows Server 2008 hosting the Cisco Directory Connector
Expressway-C
To synchronize users from your Active Directory with Cisco Webex and to authenticate Cisco Webex Hybrid Services users
Cisco Webex
O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority
Expressway-C
Link the Calendar Connector to Cisco TMS
Before you begin
The Cisco TMS must have a valid CA-signed server certificate installed. This integration does not support self-signed certificates.
1
From the Expressway-C connector host, go to Applications > Hybrid Services > Calendar Service > Cisco Conferencing Services Configuration, and then click New.
2
Select Type as TMS under Conferencing Services Type.
3
Enter the username and password of the Cisco TMS administrator account that you want the Calendar Connector to use to connect to Cisco TMS.
Enter only the username, without the domain, in the username field.
4
Under TMS Server Details, enter the fully qualified domain name (FQDN) and domain in the respective fields.
Enter the NETBIOS domain name for the TMS Domain Name field.
5
Under Telephony Invite Details, enter the appropriate information for Toll Identifier, Toll Number, Toll Free Identifier, Toll Free Number, and Global Call-in Numbers (URL).
6
Click Save.
Cisco TMS is listed under Cisco Conferencing Services Configuration.
7
Click Cisco TMS and click Test Connection.
The Calendar Connector tests the connection to the Cisco TMS environment. If the test returns an error message, correct any errors in the configuration
and try the test again.
8
When you've confirmed the connection, go to Applications > Hybrid Services > Connector Management and click Calendar Connector Service.
9
Select Enabled from the Active drop-down list and click Save.
The Calendar Connector starts and the status changes to Running.
Add a Cisco Meeting Server to Cisco TMS
When you configure @meet to use the Cisco TelePresence Management Suite action, the Cisco TMS uses any bridge configured in the Administrative Tools > Configuration > Conference Settings > Advanced.
To allow users to schedule meetings on a Cisco Meeting Server using the Hybrid Calendar Service integration with Cisco TMS,
add the server using the steps in the Cisco Meeting Server section of the applicable Cisco TelePresence Management Suite Administrator Guide.
Test the Google Calendar and Cisco TMS Integration
Use these steps to schedule a test meeting and verify the TMS integration.
1
Test meeting scheduling with @meet:
In a web browser, sign in to https://calendar.google.com with a Google Calendar user account that is enabled for Hybrid Calendar
Service.
Double-click today's date to schedule the test meeting.
Enter an event title in the text box where Add title displays.
Enter @meet in the text box where Add location displays.
Enter only one keyword in this field. Grouping of keywords, for example @meet @webex, is not supported.
In the Guests tab, invite users and add rooms (or other video devices) for OBTP.
Send the invitation.
The Hybrid Calendar Service updates the meeting with the join details.
.
2
In a web browser, sign in to Cisco TMS and go to Booking > List Conferences.
The test meeting and other meetings that are scheduled with @meet are listed in Cisco TMS with 'Calendar Connector' in the
External Service column.
You cannot edit Calendar Connector meetings in Cisco TMS.
Troubleshoot the Cisco TMS Integration
Use these tips to check the status of the various components of the Cisco TMS integration with the Hybrid Calendar Service.
1
Verify the number of users who are enabled for the Hybrid Calendar Service in https://admin.webex.com under Services.
2
Check the status of the connectors in Control Hub.
From the customer view in https://admin.webex.com, go to Services, and then click All Resources from the on-premises resources card.
From the resource card for the Cisco TMS integration, click the Node link below the resource FQDN or IP address.
3
Compare the status above to the status of the connectors on the Expressway connector host.
From Expressway, go to Applications > Hybrid Services > Connector Management.
Notable Behavior for the Cisco TMS Integration with Google Calendar
This section lists limitations and notable behavior for the Cisco TMS integration with Google Calendar.
Editing a meeting series during an active instance of the series results in the following behavior:
Cisco TMS updates all instances other than the in-progress instance.
The currently active instance becomes an exception in Cisco TMS.
This is the expected behavior, but differs from the behavior of Google Calendar, which updates the active instance as well.
ProductWebex Boards, Webex Control Hub, Webex Hybrid Services
.
Is this about?