Cisco TMS Provisioning Extension

This topic describes the Cisco TelePresence Management Suite (TMS) Provisioning Extension features.

TMS Provisioning Extension simplifies scaling of video across the enterprise:

Benefits Description
Provisioning Scale Simplifies management of up to 100,000 telepresence users across disparate locations and networks Automated user account and phone book creation
Intuitive Meetings Intuitive Collaboration Meeting Rooms (CMRs) Configure personal CMR preferences.
Intuitive Scheduling Extend scheduling capability to everyone. Smart Scheduler simplifies the booking process for single and recurring telepresence meetings.
Endpoint Support Quick deployment with predefined templates Low touch provisioning for C, E, EX, MX, and SX Series endpoints and Cisco Jabber Video for TelePresence and iPad

The figure shows the main features and benefits of the Cisco TMS Provisioning Extension.

Note

Smart Scheduler is a part of Cisco TMS Provisioning Extension.

Integration of Cisco TMSXE with Microsoft Exchange

This topic describes the integration of Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE) with Microsoft Exchange.

Add Exchange mailboxes:

  • Create a User mailbox for TMSXE.
  • Create a Room mailbox for each endpoint.
  • Give the TMSXE user Full Access permission for each endpoint mailbox.
    1. Configure the endpoint mailbox properties.
    2. Configure the email address in the endpoint configuration on Cisco Unified Communications Manager.

Set the following on Microsoft Exchange for the endpoint mailbox:

  • Automatically accept invitations: True
  • Remove the Private flag for all meetings accepted by the mailbox: True
  • Delete Meeting Subject: False
  • Add organizer to the subject of a booking: False

Then start the TMSXE Configuration setup GUI, which is, in most cases, on a standalone server, and specify the following:

  • TMS Server IP address, username, and password
  • Exchange Server IP address, username, and password, as well as the email address of the sender

Add the video endpoints and map them to their email addresses.

Note

Use the Cisco TelePresence Management Suite display name as the mailbox name.

Schedule a meeting and test the integration.

Adding Cisco VCS Endpoints to Cisco Unified Communications Manager

This topic describes how to add Cisco TelePresence Video Communication Server (VCS) endpoints to Cisco Unified Communications Manager for scheduling.

  • Create an access control group with the following permissions:
    1. Standard AXL API access
    2. Standard CTI enabled
    3. Standard Serviceability
    4. Standard Cisco Unified Communications Manager Admin users
    5. Standard RealtimeAndTraceCollection
  • Create an application user for Cisco TMS:
    1. Add the user to the access control group.
    2. Assign all endpoints that you plan to add to Cisco TMS to the application user.

The application user is a service account that Cisco TelePresence Management Suite (TMS) uses to log into Cisco Unified Communications Manager and to control video endpoints for scheduling.

In Cisco TMS, do the following:

  • Add Cisco Unified Communications Manager and specify the application user with its credentials.
  • After integrating these systems, select the video endpoints from the received device list.

For Cisco TelePresence Video Communication Server, do the following:

  • Add the Cisco VCS endpoint to Cisco TMS, using its IP address.
  • Enter the administrator user credentials.

Recommended Cisco TMS Scheduling Deployment Mode

This topic describes the recommended Cisco TelePresence Management Suite (TMS) scheduling deployment mode.

Cisco TMS scheduling deployment models are Microsoft Outlook- and web-based scheduling.

Cisco TMS directly manages multipoint control units and Cisco TelePresence Servers from a scheduling perspective. The Cisco TelePresence Conductor is used with Cisco Unified Communications Manager for nonscheduled conferences and for optimized resource utilization when devices with different capabilities are conferenced together.

The Cisco TMS Extension for Microsoft Exchange (Cisco TMSXE) is another layer for scheduled conferences.

Cisco TelePresence Conductor Support

This topic describes the Cisco TelePresence Conductor support.

Conference scheduling is available with Cisco TMS 14.3 and Cisco TelePresence Conductor XC2.2

  • Only conference monitoring was available previously.
  • Multipoint control unit registered to Cisco VCS is managed by Cisco TelePresence Conductor and scheduled by Cisco TMS.

In future versions, Cisco TelePresence Conductor can be connected with Cisco Unified Communications Manager, and Cisco TelePresence Management Suite (TMS) will be able to schedule conferences as well. With Cisco TelePresence Conductor, the conferencing management is virtualized, separated from the physical hardware, and managed centrally in Cisco TelePresence Conductor.

Limitations and recommendations for Cisco TelePresence Conductor are as follows:

  • Cisco TMS cannot properly reserve ports for meetings that are scheduled by Cisco TelePresence Conductor.
  • As a result, conference resources are not assured.
  • The recommendation for scheduled meetings is to directly manage and schedule the Cisco TelePresence Server and multipoint control units with Cisco TMS.

Calendaring Options

This topic describes the calendaring options in the Cisco TelePresence Management Suite (TMS).

Cisco TMS extensions are available for the following:

  • Microsoft Exchange (TMSXE)
  • IBM Lotus Notes (TMSXN)
  • TMS Booking API (TMSBA)

Cisco TMS application

  • Book from TMS web-based interface
  • Smart Scheduler with simplified GUI is part of Provisioning Extension (TMSPE) for self-service

The Cisco TMS scheduling extension products are as follows:

  • The Cisco TMS Smart Scheduler interface, included with the Cisco TMS Provisioning Extension (Cisco TMSPE), allows simple, intuitive booking of single-instance and recurrent telepresence meetings.
  • Cisco TMS supports Microsoft Exchange Server 2007 and 2010 calendar integration through the Cisco TMS Extension for Microsoft Exchange (Cisco TMSXE).
  • Cisco TMS supports IBM Lotus Domino Server calendar integration through Cisco TMS Extension for IBM Lotus Notes (Cisco TMSXN).
  • Custom-built scheduling interfaces for other calendaring products are supported through the Cisco TMS Extension Booking API (Cisco TMSBA).

Call Launch Options

This topic describes the call launch options that are provided by Cisco TelePresence Management Suite (TMS).

The table specifies the call launch options:

Call Launch Option Description
One Button to Push Conference dial-in information is automatically presented on endpoints that support OBTP.
Automatic Connect Cisco TMS automatically connects all the participants at the specified time and date.
Manual Connect At the specified time and date, the system listed as the VC master will be prompted to begin the call. The call is automatically connected when the VC master initiates the call.
No Connect This option reserves the room and generates the call route, but does not connect the route. You can start the conference with the participants in the Conference Control Center by clicking Connect.
Reservation This option reserves the room but does not initiate any connections.

OBTP can be used on the touch control, phone, or with a remote control. This option is the simplest for the user, because the user does not need to know the conference number, ID, or a PIN. The user simply selects the correct meeting, pushes one button, and is connected to the conference. After pushing the button, a call is launched to the multipoint control unit to join the conference.

With Automatic Connect, the multipoint control unit dials the endpoints and the user must answer the call to join the meeting. The default is to try three times to reach the endpoint. You can enable AutoAnswer to automatically connect the endpoint to the conference, but this approach may create “empty rooms” in your conference.

With Manual Connect and No Connect, an administrator must log in and start the meeting. With Reservation, only the room is reserved without a video endpoint.

Cisco TMS Conference Port Reservation

This topic describes port reservation in Cisco TelePresence Management Suite (TMS).

  • How it works:
    1. Cisco TMS creates a temporary meeting on the Cisco TelePresence Server or multipoint control unit with the correct number of media ports.
    2. Cisco TMS knows how many media ports each conference bridge has, and it will not let users overbook the system.
  • Set up the port reservation:
    1. On the multipoint control unit, enable media port reservation.
    2. Specify the number of audio and video ports for reservations.
    3. The conference is created by Cisco TMS with a defined date and time.
    4. Optionally, limit the ports to the number of scheduled participants.

A user wants to schedule a meeting with five participants on Monday from 2:00 p.m. (1400) to 4:00 p.m. (1600). Cisco TMS creates a temporary meeting at the correct time with the correct number of port resources for the five users, assuming that the resources are available at the scheduled time.

The setup steps take you through the setup process and show you how to prevent multipoint control unit oversubscription.

Nonscheduled calls may consume ports for scheduled conferences. The best practice is to dedicate each Cisco TelePresence Server or multipoint control unit to scheduled or nonscheduled meetings, but not both.

An unscheduled call can use ports that are reserved by Cisco TMS for scheduled conferences. In this case, oversubscription can occur. To prevent oversubscription, uncheck the Allow Bookings check box for the relevant multipoint control units. This action will create two multipoint control unit groups:

  • The schedule-enabled multipoint control units are managed by Cisco TMS.
  • Access is based on the best effort principle on the multipoint control units that are used for nonscheduled (ad hoc) conferences. Cisco TMS does not size ports on these multipoint control units, so overbooking can occur.

Specify the following information to adjust and optimize resource utilization:

  • Specify default set up and tear down buffer, which reserves ports.
  • Select Extend Scheduled Meeting Mode: Off, Endpoint Prompt, or Automatic Best Effort

Specify the default setup buffer and default teardown buffer. These buffers specify how early a user can dial into a meeting, and how long the bridge remains open after the meeting ends.

Note

Ports are reserved for buffers during setup and tear down.

The Extend Scheduled Meeting Mode parameter specifies what happens at the end of the scheduled meeting time:

  • Off: The meeting is disconnected.
  • Endpoint Prompt: Prior to the end of the meeting, the user is asked if the meeting should be extended.
  • Automatic Best Effort: If resources are available, the meeting is extended by 15 minutes for a maximum of 16 times. However, if any of the endpoints in the conference have bookings within the next 15-minute period, the meeting is disconnected for all endpoints.
Note

If a recording device is included in the meeting, and the recording device stays as the last party in the meeting, the call is extended without other participants left in the meeting.

Cisco TMS Conference Call Routing

This topic describes conference call routing in Cisco TelePresence Management Suite (TMS).

  • IP zones are used for conference call routing and grouping devices together.
  • After the zones are set up, configure the dial plan.

After setting up Cisco TMS, the first task is to configure IP zones. IP zones are logical groups in Cisco TMS. These groups are used for scheduling purposes.

In the figure, there are two IP zones, UK and SJ. The endpoints are grouped together with the multipoint control unit in the UK zone. When a meeting is scheduled, Cisco TMS sees that all (or the majority) of the participants are in the UK zone and selects a resource from the UK zone, if a different zone is not specified. End users do not need to know which resources are used.

For the dial plan, specify a Numeric ID Base, Numeric ID Step, and Numeric ID Quantity. For example, if you specify the base ID 81127600, the ID step 1, and the ID quantity 31, then 31 E.164 alias numbers are created and managed by Cisco TMS on the multipoint control unit. The lowest conference number available is selected. This behavior cannot be modified.

Cisco TMS Scale and Management

This topic describes the scale and management scenarios in the Cisco TelePresence Management Suite (TMS).

  • All devices that appear in the Navigator are directly managed devices.
  • All users in the TMS Provisioning Directory are provisioned users.

Cisco TMS can support rapid, large-scale deployments of up to 100,000 telepresence users, endpoints, and soft clients across disparate customer locations, including up to 5000 direct-managed devices.

Cisco TMS has no direct communication with endpoints. Cisco TMS moves the configuration, for example, to the Cisco TelePresence Video Communication Server (VCS).

For Cisco Unified Communications Manager customers, Cisco Prime Collaboration takes over the provisioning. New devices such as the Cisco DX Series can only be registered with Cisco Unified Communications Manager. The Cisco Jabber Video for TelePresence migration path is to use Cisco Jabber for Windows, iOS, or Android with Cisco Unified Communications Manager and Cisco Unified Communications IM and Presence.