Get help with Cisco Meeting Server and Cisco Meeting Apps

Find answers quickly with these FAQs.

» »

What are some of the feature differences I can expect to see when migrating from TelePresence Server to Cisco Meeting Server?

This page is a high-level view of some of the feature differences between TelePresence Server and Meeting Server. This is not an exhaustive list of differences – it only calls out some of the differences highlighted by customers whilst migrating from TelePresence Server to Meeting Server.


Cisco TelePresence Server

Cisco Meeting Server


Join/leave meeting audio notifications

Implemented via API parameters (audioJoinNotification, and audioLeaveNotification) and applied to Conductor conference template.

Implemented via joinToneParticipantThreshold and leaveToneParticipantThreshold applied in Call Leg Profiles in API. (Value of 0 disables. Value above 0 results in tones played only for that specified number of sites joining/leaving the call.)

Disabled by default.

See FAQ: How do I set up join/leave meeting audio notifications on Meeting Server?




Not supported


Active speaker and Audio symbol

Blue bar name box with audio symbol for active speaker.

ts active speaker icon


Thin blue line under grey name box of active speaker. No audio symbol.

 CMS active speaker



Participant name labels in PiPs/video panes

Name labels are enabled by default. (See displayShowEndpointNames  API command)

Name labels are disabled by default. If you wish to enable labels to display, you can do so via the Web UI or API.

Web UI:
To enable name labels global/cluster-wide to display, go to Call Settings > SIP call participant labels.

To enable name labels to display, go to the participantLabels parameter in the callLegProfile and set to “true”.

See Cisco Meeting Server API Reference Guide for more information.



Screen layouts to single screen endpoints


 ts cms screen layouts combined

- The core layouts Single, Overlay N+1 and equal are the same.
- Meeting Server goes up to 5x5 on equal (TelePresence Server goes up to 4x4).
- Meeting Server goes up to 9+1 on N+1 (TelePresence Server goes up to 12+1).
- Meeting Server also has an activity based layout (Auto layout).
- Meeting Server can specify any of the equal layouts rather than them just being an auto growing layout.

Dual screen layouts

Dual screen experience is experimental and turned off by default. This feature is also known as Enhanced Layout Experience, and multistream support.

Dual screen experience is fully supported and enabled by default. 



Participant overflow icon

Displays in the bottom right-hand corner with the number of additional participants not being displayed in the video panes/PiPs. This number includes video and audio-only participants.

Displays in the top right-hand corner with the number of total participants in the meeting. This number includes video and audio-only participants.


Immersive conferencing

Supports room switching and segment switching.


Supports room switching when displaying another immersive endpoint, i.e. all 3 segments from the same room are kept together when they are seen full screen.

When single screen endpoints view an Immersive endpoint in a Meeting Server conference they will only see the active segment display (when the segment is full screen / as a PiP) from an immersive room when it’s not full screen. (TelePresence Server will show all segments in the PiP.)


Grouped endpoints conferencing

TelePresence Server with Conductor supports 2/3/4 codecs grouped together for custom scenarios.

Not supported.




Assign licenses in a clustered environment across multiple call bridges—Conductor manages this centrally for TelePresence Server.

You can assign a single multiparty license across multiple Meeting Servers. However, each Meeting Server needs its own license file so Meeting Server customers need to go to the licensing registration portal: and share licenses across Meeting Server MAC addresses.

See Product License Registration information:

For more information, see: Multiparty Licensing (PMP and SMP) on Cisco Meeting Server:


Visual prompts

Gives visual prompts when entering passwords etc.

Gives no visual prompts when entering passwords etc.


Localization (Customizable)


Localization is free, and provided by Conductor or customizable via the API.

Localization and customization needs a branding license.

You can download the localized audio prompts from here.

See FAQ: How do I implement localized language prompts on my Meeting Server?

Audio and visual prompts, backgrounds and logos – (Customizable)

Customizable via the API.

Provides audio prompts, but not unique backgrounds by default. You can customize using the branding license.

You can customize the IVR background, PIN prompt related screens, and a lobby screen (for callers waiting for host).

Meeting Server is flexible and allows you to customize individual conferences.

For more information, see Cisco Meeting Server Customization Guidelines:

“Lecture” Conference Type

Supported (configurable conference type in conference templates).

You can use profiles to assign settings to different URIs. See FAQ: How do I set up “Lecture mode”?


Auto dial participant


Not supported.


Schedule and manage meetings

TMS and Conductor required.

TMS and Cisco Meeting Management required to schedule and manage meetings on Meeting Server.


Service preference

Set call quality on Conductor and apply the preference against a template.

Set call quality via API in call leg profile – you can set separate maximum quality levels for main video and content.

See Cisco Meeting Server API Reference Guide for more information.



See FAQ: “What logs can I collect from the Meeting Server?



Not applicable.

Cisco has a commercial migration to help with licenses. (There are no technical migration tools to simplify the process.)




Web UI

API - Firefox Poster, Chrome Postman, Chrome Advanced Rest Client

CLI – for platform config (MMP)

Meeting Server: Web UI used for single bridge. API for multiple call bridges and single bridges. CLI only used for platform and initial config (MMP).

Bulk changes




See Cisco Meeting Server API Reference Guide section “6.8 Bulk creating, updating and deleting coSpaces” for more information.

AD group sync

Configure the import of user account data from external sources (AD) with Cisco TMSPE. It uses the information supplied to set up a daily automatic synchronization.

Allows importing of users and auto-space creation via LDAP configuration (via web UI or API).

Set up API initiated sync, according to custom policy.

See Cisco Meeting Server API Reference Guide, Section 11.4 LDAP Sync Methods


From the Web UI, use the Sync now button at the bottom of the Configuration > Active Directory page to synchronize the LDAP servers.

Meeting Server does not have the full self-care functionality of TMSPE. Key differences:

TMSPE allows greater tailoring of the conferences created (different for different users, etc), provides enrollment mails, personal pins at creation, and provides a selfcare portal for the space management.

Meeting Server users have to use the CMA client (webbridge or native clients) to edit their space.


Provision through TMS or Conductor

Provision through API.