Cisco Cisco TelePresence MCU 4510 Release Notes
Call Home messages are sent to
https://tools.cisco.com/its/service/oddce/services/DDCEService
. At that point,
you may need to update your firewall to allow the reports through, by adding the domain
tools.cisco.com
and opening
port 443 for outbound TCP traffic.
The MCU has a separate dedicated trust store to verify the connection to the Call Home server. (The MCU 4.5 has
three trust stores - One for HTTPS connections, one for SIP connections and one for Call Home connections.) The
MCU has a certificate pre-installed, however, it is possible to delete and upload new certificates. You can also reset
the certificate to default.
three trust stores - One for HTTPS connections, one for SIP connections and one for Call Home connections.) The
MCU has a certificate pre-installed, however, it is possible to delete and upload new certificates. You can also reset
the certificate to default.
The MCU can send 'inventory' data (i.e. basic system information such as serial number, hardware platform and
software version) to the Call Home service. If automatic reporting is enabled, inventory data is sent each time the
device starts up.
software version) to the Call Home service. If automatic reporting is enabled, inventory data is sent each time the
device starts up.
Device inventory reports are always available. Media resource or unit-wide diagnostic logs may also be available
depending on whether an unexpected shutdown or media resource restart has occurred.
depending on whether an unexpected shutdown or media resource restart has occurred.
Note
: If you have any questions about a Call Home report please contact Cisco TAC.
The user interface has a new Call Home settings page (Logs > Call Home) to allow the MCU to be configured to send
diagnostic logs automatically in the event of an unexpected restart. Logs can also be submitted manually from this
page.
diagnostic logs automatically in the event of an unexpected restart. Logs can also be submitted manually from this
page.
Two new warning banners are introduced in this release to display in the user interface in the event of an unexpected
device restart or unexpected media resource restart. Both of these banners can be dismissed from the Call Home
page.
device restart or unexpected media resource restart. Both of these banners can be dismissed from the Call Home
page.
Serviceability Improvements
This release introduces several improvements to the serviceability of the MCU, as follows:
Isolated Media Processor Reboot
The MCU (MCU 8510, MCU 5300 Series, and MCU 4500 Series) is now more resilient in the unusual circumstance of
individual media processor failure. On the MCU, 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 processor gracefully.
individual media processor failure. On the MCU, 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 processor gracefully.
Note that some participants may experience a loss of audio and/or video in the unlikely event of a media processor
failure, although it should come back after a pause of about 30 seconds.
failure, although it should come back after a pause of about 30 seconds.
In the case of a processor failure, the MCU isolates the processor as well as it can, while rebooting the processor, as
follows:
follows:
■
The MCU tries to reallocate tasks from the failed processor to other media resources if available. Participants
may see a glitch while the tasks are recovered.
may see a glitch while the tasks are recovered.
■
If there are no spare media resources available, the affected participants will experience a loss of audio
and/or video but the calls will stay up while the affected processor reboots.
and/or video but the calls will stay up while the affected processor reboots.
■
The processor reboots in about 30 seconds and audio/video to the affected participants will resume.
■
It is also possible for presentation in a conference to be stopped. The user will have to re-initiate presentation
manually in this case.
manually in this case.
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.
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 improved diagnostics include:
5
Cisco TelePresence MCU Series Software Maintenance Release Notes