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.


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.

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.

Endpoint and Infrastructure Support

This topic describes the supported endpoints and infrastructure in a Cisco TelePresence Management Suite (TMS) environment.

Scheduled conferencing resources must be registered to Cisco TelePresence Video Conferencing Server (VCS) and not trunked to Cisco Unified Communications Manager.

Cisco TMS Release 13.2 and later releases allow access to Cisco TelePresence System and TX Series endpoints for scheduling.

Cisco TelePresence SX, EX, MX, C, and Profile Series endpoints that are registered on Cisco Unified Communications Manager can also be scheduled with Cisco TMS Release 13.2 and later releases.

Cisco TMS Overview

This topic describes the main or core Cisco TelePresence Management Suite (TMS) functions.

Cisco TMS is the core platform (base system) and supports the following:

  • A booking API
  • Scheduling extension for Exchange and Lotus Notes
  • Provisioning extension for video endpoints

Cisco TMS is the base system and can be enhanced with an extension to integrate with Microsoft Exchange or Lotus Notes to reserve video conference resources from the Microsoft or Lotus Notes calendar.

In addition, an API can be used to book conference resources in Cisco TMS using different systems or applications. In addition, the provisioning extension can be used for endpoint registration and smart scheduling.

Cisco TMS Platform Overview

This topic describes the resources that are required by Cisco TelePresence Management Suite (TMS).

Cisco TMS 14.x runs on a Windows-based server and requires the following virtual resources in a virtual machine:

  • Standard deployment with TMS and TMSXE in one VM requires 2 vCPUs, 8 GB vRAM, 60 GB vDisk, and 1 vNIC
  • Operating system is Windows Server 2003, 2008, or 2012.
    1. Install the operating system, Cisco TMS, and SQL server on virtual disk 1.
    2. Install the database on virtual disk 2.
  • The license system supports the following:
    1. Up to 1000 directly managed systems
    2. Up to 40 multipoint control units and Cisco TelePresence Servers
    3. Cisco TelePresence Provisioning extension

Cisco TMS can be virtualized. The supported operating systems to host Cisco TMS are as follows:

  • Windows Server 2003 SP1 or later, 32 bit
  • Windows Server 2003 R2 SP1 or later, 32 bit
  • Windows Server 2008 SP2 or later, Standard 32 bit and 64 bit
  • Windows Server 2008 R2 SP1 or later, Standard 64 bit (Recommended)
  • 4.0 .NET Framework Full (extended) version must be installed prior to running the Cisco TMS installer

The server operating system must be English, Japanese, or Chinese. Standard, Enterprise, and DataCenter editions are supported on both Windows Server 2003 and R2. Using the latest service pack is recommended for all versions.

For a large deployment, two VMs are required, where one is the Cisco TMS server and the other is used for the Cisco TMS Extension for Microsoft Exchange (TMSXE). The VM resources for a large deployment vary slightly per virtual machine:

  • 4 vCPUs
  • 8 GB vRAM
  • 200 GB vDisk
  • 1 vNIC with 1 Gbps

Testing was performed on a Cisco UCS C220 M3S Rack Server platform. To fully utilize Cisco TMS, an external Microsoft SQL server is required. Use options keys for capacity or features to enhance the base version functionality.

Business Needs for Cisco TMS

This topic describes the business needs for Cisco TelePresence Management Suite (TMS).

Cisco TMS is used for resource management to mitigate issues such as these:

  • User cannot connect to conference because no resources are reserved.
    1. Ad hoc user may use all multipoint control unit capacity so customers cannot call in.
    2. This leads to unexpected and unwanted user experience.
  • Oversubscription with booking cannot yet be prevented.
    1. Monitor the resource utilization to control usage.
    2. Adjust or enhance your multipoint control unit farms

Other issues that Cisco TMS can help to resolve:

  • Users do not know their login data.
    1. When does the meeting start?
    2. Which conference number to dial?
    3. Too much time is required for all participants to dial into the meeting.

These scenarios describe unexpected and unwanted user experiences with video conference resources:

  • Users want to dial in but conference video resources are not available.
  • Users want to dial in but do not know the dial-in information, so in most meetings there are users that arrive late.
  • Users do not know how to start a conference.

Cisco TMS helps resolve these issues:

  • You can reserve resources for your conference.
  • Cisco TMS simplifies the process of joining a conference.