Release Notes
New platforms for TelePresence Server
Cisco TelePresence Server Software Release Notes 3.1(1.95) Page 3 of 31
release notes for TelePresence Server version 3.0, and the associated administrator documentation, for
more details.
Feature name TelePresence Server on
7010 MSE8710 or
MCUMSE8510
Media 310/320 or MCU5300 Series
Remotely managed mode Yes Yes Yes*
Locally managed mode Yes Yes No*
SIP support Yes Yes Yes
H.323 support Yes Yes Not directly. Requires H.323 ↔ SIP interworking
by Cisco VCS.
FTP Yes Yes No
Clustering No Yes
‡
Yes
‡
G.723.1 Yes Yes No
Interlaced H.263 support Yes Yes No
Isolated media processor reboots No No Yes, on Media 320 or MCU5320, or
TelePresence Server clusters on these platforms
Replacing MCUsoftware with
TelePresence Server software
No Yes, on MCU
MSE8510
Yes, on MCU 5300 Series
Maximum screen licenses per unit 12 12
†
5 on Media 310, or MCU5310
†
10 on Media 320, or MCU5320
†
Table 1: Differences between TelePresence Server platforms
* Remotely managed mode is the only mode of operation of the TelePresence Server on these platforms,
hence they have no concept of the difference between these modes and there is no mention of operation
mode in the user interface.
‡ Running identical software on the units in a cluster is an absolute requirement for clustering but mixed
hardware is possible to a limited extent. For example, an MCUMSE8510 running TelePresence Server
software can be clustered with a TelePresence Server MSE8710, provided they have identical
TelePresence Server software versions. Similarly, a TelePresence Server on Media 310 can be clustered
with TelePresence Server running on an MCU5320.
† When TelePresence Server software is running on MCU hardware, it is possible to allocate screen licenses
to the application but TelePresence Server screen licenses are not interchangeable with MCU media port
licenses. See the software replacement documentation for more details, including how to use MCU capacity
to provide capacity for the TelePresence Server application.