다음을 통해 공유

Configure Cisco Telepresence Management suite for Microsoft Exchange

  • 아티클

This article explains integrating Cisco Telepresence Suite with Exchange Server 2016. Before that, let's have a brief on these components.

Cisco Telepresence Management Suite (Core Component of Video Collaboration):

This component in the Cisco IPT infrastructure provides the on-premises video collaboration. By this component, we would be able to configure, deploy, manage, schedule, analyze and track the telepresence utilization within an organization.

Cisco TMS helps in the following:

1) Helps Admins in the daily operations, configuration and maintenance of the telepresence network.
2) Helps consumers to use this telepresence network according to their customization. Like telepresence deployment as a service. Example: Setting up meeting rooms of multi-monitors, multi-microphones and multi-channel speaker systems which give stunning real like audio, video experience.
3) Helps in monitoring the Telepresence utilization and analyzing them.

What is Cisco TelePresence Management Suite Extension for Microsoft Exchange?

Cisco TelePresence Management Suite Extension for Microsoft Exchange (Cisco TMSXE) is an extension for Cisco TelePresence Management Suite that enables videoconference scheduling via Microsoft Outlook and replicates Cisco TMS conferences to Outlook room calendars.

Cisco TelePresence Management Suite Extension for Microsoft Exchange (Cisco TMSXE) is one of their extension for Cisco TelePresence Management Suite.

How it helps us in Scheduling the Meeting:

1) By having this it enables the option to Video Conferencing Scheduling via Microsoft Outlook.
2) Replicates Cisco TMS conferences settings to Outlook Room Calendars.
3) Makes end users book Audio/Video conferences based on the Meeting room Availability from Outlook.

Cisco TMSXE Installation:

This Cisco TMSXE server runs on a Windows Server Cisco TMSXE component that will be installed on this server along with booking service option chosen.
It similarly uses the IIS as web server. Enable HTTPS on the Default Website after the installation.

All the other configurations in Cisco components required for this integration like integrating with CUCM, CMS must be configured on the Cisco TMSXE and Cisco TMS server. There are more configurations on the TMS and TMSXE components which need to be performed before integrating with Exchange Server.

In a small deployment, the Cisco TMS and its extensions can be co-located on the same server. In large scale deployments, Cisco TMSXE extensions are separate and remote SQL instance is required. And separate Cisco TMS and Cisco TMSPE are always co-resident.

DNS Requirements:

The Cisco TMSXE server must be present on the same server VLAN where we have AD, Exchange servers. The communication will be authenticated using the Cisco TMSXE Exchange service user account.

EWS and Autodiscover must be reachable from the TMS and TMSXE server for them to function.

Licensing:

Each telepresence endpoints to be booked through Cisco TMSXE must be licensed for general Cisco TMS usage.

In our case from Exchange perspective, only the Meeting rooms where we need telepresence to be enabled must have the license.

Supported Exchange Server Versions:

  1. Office 365 (Active Directory Federation Services and the Windows Azure Active Directory Sync tool are required)
  2. Exchange Server 2016 CU1 (latest CU’s preferred)
  3. Exchange Server 2013 SP1 (latest CU’s preferred)
  4. Exchange Server 2010 SP3 (Latest Roll-ups preferred)
  5. Exchange Server 2007 (Latest Roll-ups preferred)

Exchange Requirements:

  1. TMSXE purely depends upon Exchange  AutoDiscover and EWS components to show the configured resource mailboxes availability

  2. Room Mailboxes added to Cisco TMSXE must have below configurations:

    a) Delete the subject
    b) Add the organizer’s name to the subject
    c) Remove the private flag on an accepted meeting

    3. Cisco TMSXE Service Account with Mailbox is required. This service account will be used in Cisco TMS to connect to Exchange, Cisco TMSXE and Cisco TMS.

Enable impersonation for the service user in Exchange to prevent throttling issues.

To enable impersonation run the below command:
New-ManagementRoleAssignment –Name:impersonationAssignmentName – Role:ApplicationImpersonation –User:[ServiceUser]

Certificate Requirements:

HTTPS is the default communication protocol for communicating with Cisco TMS and with Exchange Web Services.

The certificateCertificate can be issued from a Trusted CA, since this is only server to server communcation between the Exchange CAS services (EWS/AutoDiscover) and TMSXE services no public SSL is required.

So, the TMSXE server certificate issued from Trusted CA should have the below:

  1. Should have the host name of the TMSXE server.
  2. Should have the host name of the Exchange servers for the EWS and Autodiscover services in secure communication.

To verify that we have certificates that are valid and working:

  1. Launch Internet Explorer on the Cisco TMSXE server.
  2. Enter the URL for the Exchange CAS and verify that the URL field turns green.
  3. Enter the URL for the Cisco TMS server and verify that the URL field turns green.

Below will be the Work Flow:

https://exchangequery.files.wordpress.com/2017/06/cisco-tms.png?w=600

  1. End User Books a meeting through Outlook addin.https://exchangequery.files.wordpress.com/2017/06/tp.png?w=600
  2. Exchange Checks the resource Mailboxes availability and books the meeting and sends initial confirmation.
  3. Cisco TMSXE communicates with Exchange and passes them on to Cisco TMS.
  4. Cisco TMS checks system and WebEx availability and attempt to book routing resources for the telepresence.

Additional Tips:

  1. The Cisco TMS is dependent only on resource calendars which are configured for this Telepresence feature.
  2. Cisco TMSXE does not have permissions to modify the calendars of personal mailboxes.
  3. All the other configurations  required for this integration must be configured on the Cisco TMSXE and Cisco TMS server.