Release Notes
New features in 3.1
Cisco TelePresence Server Software Release Notes 3.1(1.95) Page 13 of 31
make it more robust to corrupt or invalid incoming bitstreams.
Isolated media processor reboot
The TelePresence Server on Media 320 is now more resilient in the unusual circumstances of individual
media processor failure. On Media 320 models, or mixed Media 310/320 clusters, if a media processor fails it
will not cause the whole device to fail. This means that the other parts of the device software can maintain
the state of the conferences—except for the tasks performed by that particular processor—while recovering
the processorgracefully.
Note:Some participants may experience a loss of video in the unlikely event of a mediaprocessor failure,
although it should come back after a pause of about 30 seconds.
In the case of a processor failure, the TelePresence Server isolates the processor as well as it can, while
rebooting the processor, as follows:
n The TelePresence Server tries to reallocate tasks from the failed processor to other media resources if
available. Participants may see a glitch while the tasks are recovered.
n If there are no spare media resources available, the affected participants will experience a loss of video but
the calls will stay up while the affected processor reboots.
n The processor reboots in about 30 seconds and video to the affected participants will resume.
Improved diagnostic logging
This release features increased diagnostic detail, particularly in the core system and media processing
software, which is continuously monitored and, in the event of a failure, stored for troubleshooting purposes.
After a failure, the diagnostic log can be retrieved via the web interface.
The new diagnostics include:
n Improved Cisco TACdiagnostic options in the event of system failures.
n Deeper detail about the TelePresence Server - model and serial numbers, software version, and last reboot
reason.
n Information about each media processor, including the state of the active decoders and encoders at the
time of failure.
n Information about the endpoint associated with each decoder, and the participant display name.
API message log
This release introduces APImessage logging to the TelePresence Server. All inbound API messages are
recorded in a circular buffer that is written out to a file when the log is requested.
Additional logging options
This release introduces an option to disable the output of event log messages to the TelePresence Server's
serial console. This output has been disabled by default to improve performance.
While disabled, the event log messages are still output to the serial console during startup; from the time the
TelePresence Server powers up until the media resources are available. After that time, no event log
messages are output to the serial console, even though other system messages will occasionally be output.
You can re-enable serial output of event log messages on the Configuration >System settings page, but
we recommend that you refrain from doing so unless it is under the guidance of the Cisco Technical