Release Notes

New features introduced in 4.0(1.57)
Cisco TelePresence Server Software Release Notes (4.0(2.8)) Page 17 of 36
Support for cascaded conferences
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 is not supported on Cisco TelePresence Conductor XC2.3.
The TelePresence Server software now supports cascading, which is the ability for one TelePresence Server
to invite another TelePresence Server into a conference.
The cascading feature allows for up to 500 participants in a single conference. This is a nominal limit for
testing and support purposes - as it is the maximum number supported by the roster list - but there is no fixed
limit applied by the software. You may be able to achieve higher numbers but we cannot guarantee support
beyond the nominal limit.
The audio, video, and content contribution from an endpoint connected to one of the linked TelePresence
Servers will be shown to all participants in the cascade. There can only be one master and one slave in each
cascade link, but you can configure multiple links to create a star (hub and spoke) topology.
Cascade links must be configured via the TelePresence Server's remotely managed mode API.
Cascading is supported on all TelePresence Server platforms, although it is not supported in locally managed
mode. Cascading is not supported between a TelePresence Server and other conference bridges, eg. Cisco
TelePresence MCU Series.
Security improvements
Console password
Password protection has been added to the TelePresence Server console (the serial console on physical
hardware or the virtual machine console). When the feature is enabled, the console does not respond until the
user logs in with TelePresence Server administrator credentials.
The feature is disabled by default, to prevent locking out users who upgrade to this version, but we
recommend enabling it immediately after upgrade. You can toggle the password protection via the web
interface but this feature is not exposed via the API.
Static ARP and NDP
Static ARP (Address Resolution Protocol) and NDP (Neighbor Discovery Protocol) enable administrators to
manually bind MAC addresses to IPv4 or IPv6 addresses respectively. This feature enhances security by
giving administrators certainty over the binding, which can potentially be compromised if it is automatically
resolved.
On the TelePresence Server console, administrators can manually create, edit, and delete static ARP or
NDP entries, or show a list of current entries. When resolving an IP address to a MAC address, the
TelePresence Server first tries to do so using the static binding table, but will fall back on ARP (or NDP) if
there is no entry for the requested IP address.
You can only access the static bindings feature via the console.
Netstat
The TelePresence Server now provides a real time list of all its network connections. This information is
available via the netstat command on the console or on the Network > Netstat page of the web interface.