Release Notes

New features introduced in 4.0(1.57)
Cisco TelePresence Server Software Release Notes (4.0(2.8)) Page 10 of 36
n Reporting on the state of conferences and participants has been improved as follows:
l Participant deletions can be requested per conference
l Connection state of enumerated participants is reported
l Current presenter is reported
l A new participant enumeration has been added. The new method returns more detailed information on
each connected participant, for example the participant's encryption status and media status.
n New methods have been added to control the feature keys and license keys on the TelePresence Server.
An API user can now query, add, and delete these keys.
Third Party Interop feature key requirement lifted
In this release, the TelePresence Server no longer requires the Third Party Interop feature key to host
conferences with multi-screen endpoints that are not third party interoperable.
In previous releases, the TelePresence Server would have required this key to host conferences with all
multi-screen endpoints except:
n Cisco TelePresence System T3
n TIP-compatible endpoints (eg. CTS).
In previous releases, the TelePresence Server would also have required the Third Party Interop key to host
multi-call participants, most notably participants using PSTN audio with the WebEx Enabled TelePresence
solution. The key is no longer required for such multi-call participants.
Scalability improvements
Increased calls per unit
Note: This feature is only available in the remotely managed mode of TelePresence Server operation. It is not
available in the locally managed mode.
Note: This feature requires Cisco TelePresence Conductor XC2.3.
The maximum number of calls that a TelePresence Server - or cluster of TelePresence Servers - can
concurrently process has been raised from 104 to 200. The maximum number of participants in a conference
is still 104, although this can be extended by cascading the conference.
The higher call limit does not imply changes to media processing or licensing limits; rather, it makes the
TelePresence Server adaptable to scenarios that scale the number of low-resource calls (eg. one blade for
200 audio calls) as well as those that scale the number of higher-resource calls (eg. 200 360p calls on a three-
blade cluster).
When hosting resource-intensive calls, the 200 calls limit will not be reached. For example, either the media
processing limit or the licensing limit will be reached first if you try to connect 200 720p calls.
Dynamic resource optimization improvements
Note: This feature is only available in the remotely managed mode of TelePresence Server operation. It is not
available in the locally managed mode.
This feature requires a management system that controls the TelePresence Server via its API. This
discussion refers to the Cisco TelePresence Conductor and its user interface.