Release Notes

New features introduced in 4.0(1.57)
Cisco TelePresence Server Software Release Notes (4.0(2.8)) Page 9 of 36
Figure 7: The TelePresence Server's "you are muted" icon
Participants will see this icon when their audio contributions are muted from the TelePresence Server side.
This mute can be applied by the participants themselves, using *6, or by another authorized party.
Participants may also see a message about having been muted.
This icon does not appear when the participant uses the endpoint's own mute control.
Note: The TelePresence Server places its conference status icons on the left hand edge of the display, near
the top. In some cases the endpoint's own icons will also be visible but these are usually in a different region
of the display.
Notification banner changes
This release includes new or updated notification banners for the following important conditions:
n Unexpected media resource restart
n Unexpected device restart
n Font file missing
The banners provide suggestions or links to help you resolve the noted conditions and will disappear when
the condition is resolved.
Note: If you are upgrading a TelePresence Server MSE 8710, you will probably see the banner about the
missing font file. If this is the case, it is the notification that is new, and not the absence of the font file. You
can download the font file from the Software download page for 3.0(2.48). There are more detailed
instructions for Upgrading the font (optional) [p.34] later in this document.
New technology
Support for mixed IP scheme networks
The TelePresence Server can now negotiate IPv4 and IPv6 destinations for media in SIP, whether IPv4 or
IPv6 is being used as the transport.
The TelePresence Server now supports the ANAT semantics (Alternative Network Address Types) to
establish media streams to both IPv4 and IPv6 addresses within a SIP call. The ANAT semantics are also
used by Cisco Unified Communications Manager.
API improvements
The XML-RPC API has been extended in this release to support the new features. There are also
improvements to the data returned in some API methods, and better coverage for licensing features that were
previously only available via the web interface.
The API maintains backward compatibility with version 3.1. See the Cisco TelePresence Server API
reference for details of the following changes: