Table Of Contents
Release Notes for Cisco Unified Videoconferencing 3500 Release 188.8.131.52.15
Revised: November 26, 2007, OL-12053-01
These release notes describe the new features and caveats for all versions of Cisco Unified Videoconferencing 3515 MCU, Cisco Unified Videoconferencing 3545 MCU and Cisco Unified Videoconferencing 3545 EMP release 184.108.40.206.15.
You can access the latest software upgrades and release notes for all versions of Cisco Unified Videoconferencing 3500 MCU on Cisco Connection Online (CCO) at the following URL:
These release notes discuss the following topics:
The Cisco Unified Videoconferencing 3500 are high performance multipoint video conferencing and media processing systems that provide extensive audio and video processing capabilities and web-based conference monitoring and management. The Cisco Unified Videoconferencing 3500 Series products support a wide range of telephony protocols and media communication networks and are interoperable with other video conferencing network devices.
Cisco Unified Videoconferencing 3500 Release 220.127.116.11.15 only operates with the following products:
•Cisco Unified Videoconferencing 3515 MCU12
•Cisco Unified Videoconferencing 3515 MCU24
•Cisco Unified Videoconferencing 3545 MCU
•Cisco Unified Videoconferencing 3545 EMP
You cannot install version 18.104.22.168.15 on older IP/VC products, including the Cisco IP/VC 3511 and 3540 Series products.
Note You should use a Java-compliant browser. Using browsers other than the Microsoft Internet Explorer version 6 family or later is strongly discouraged and may not be supported.
Upgrading MCU and EMP Versions
Upgrading from a previous build of MCU version 5.x to MCU version 22.214.171.124.15
Step 1 Save the current MCU custom configuration.
•Click Export on the MCU web user interface toolbar to export the MCU configuration to a *.ini file.
Step 2 Burn the MCU version 5.1 application with the MCU default configuration.
•Run the MCU version 5.1 Upgrade Utility.
•Provide the target IP address.
•Ensure that MCU Factory Default Configuration option is not selected.
•Ensure that all other Customize options are selected, including the Default MCU Configuration option.
•Click Upgrade to perform the upgrade procedure.
•Wait while the MCU performs the upgrade procedure and resets.
Note This may take a few minutes. Please wait until the procedure is fully completed and the Upgrade Utility reports that the upgrade has been performed successfully.
Step 3 After reset, the latest version is installed on the MCU.
Step 4 (Optional) Restore a previously saved MCU custom configuration.
•Click Import on the toolbar of the MCU web user interface to import a previously saved MCU version 5.x configuration .ini file.
Upgrading from a previous build of EMP version 5.x to EMP version 5.1.1
Step 1 Use the EMP Upgrade Utility to burn the version of the EMP software that operates with the version of the MCU.
After burning, the Upgrade Utility will reset the platform.
Step 2 After reset, the latest version is installed on the EMP.
New and Changed Information
The following section describes new features and changes that are pertinent to this release of Cisco Unified Videoconferencing 3500 Series products.
•Support for High Definition resolutions are supported in switched conferences with LifeSize endpoints only.
•High Capacity Personal Video—Optimized port capacity for audio-only and standard rate video conferences (of up to 384 Kbps).
•Auto-switch in cascaded conferences—Available for each live video layout on the master conference and for the local layout of the slave conference.
•SCCP flow control
–When there is only one video-enabled participant in the conference (i.e. the participant that opened the video channels), the MCU sends a flow control message to that station with a bit rate value of 0.
–When a second video-enabled participant joins the conference, the MCU sends a flow control message to the first participant with the original bit rate value.
–The effects on SCCP conference endpoints are as follows:
Regular— Lowering/returning bit rate as described above. If only one video-enabled participant is present, the participant sees a still image in the video window.
Modified (CUVA)—When the bit rate is set to 0, the video window closes. When the bit rate is returned to the original setting, the video window reopens.
Note The Modified (CUVA) setting is a combination of both the correct release and a CLI option on installation to achieve flow control. CUVA users may also set a registry key after installation to enable flow control, if they do not use the CLI option.
•FECC in cascaded conferences—Available for each live participant in the conference and for each layout.
•Presentation in cascaded conferences—Available for each participant in the conference, regardless of the viewed layout. Each participant can initiate a presentation session and all other conference participants can see the presentation.
•XML API Get Conferences List Request supports the use of a user name/password combination.
Caveats for Cisco Unified Videoconferencing 3500 MCU Release 126.96.36.199.15
This section includes the following topics:
MCU resolved caveats are included in the following categories:
Endpoint Information Display in MCU Conference Control
•The MCU Conference Control web user interface correctly displays the resolution for calls with asymmetric resolution (4CIF/CIF).
•The information icon for participants in child conferences in a cascaded topology functions correctly.
•Local view (defined in the custom layouts section of the advanced video settings) appears in the conference control and functions normally.
Configuration and Web Interface
•The boot configuration menu prompt now displays for several seconds after MCU initialization.
•HTTP access is no longer blocked when the security level is set to Maximum.
•Invalid service descriptions and prefixes containing the special characters <, > and & are no longer allowed.
•Participants can be invited to a conference using an H.323 identifier.
DTMF Conference Control
•The Conference Control menu can be called via DTMF by using either the ** or #* commands only (according to your configuration).
•T.120 interoperability with eConf, Microsoft Communicator and Microsoft NetMeeting applies for data and audio-only conferences.
–eConf/NetMeeting—A conference participant can start a data collaboration session (e.g. white board) regardless of endpoint type (eConf or NetMeeting), whether the call is dial-in or dial-out, and whether the protocol used is SIP or H.323.
–Communicator—T.120 is sent via the application media line regardless of whether or not you are working in an LCS environment.
•Encryption and H.239 now function together correctly.
•H.264 is now correctly opened in the main video channel when working with presentation view-enabled services and TANDBERG endpoints.
•Improved video quality in H.264 calls of up to 384 Kbps with TANDBERG endpoints.
•The MCU now more accurately identifies cases of poor video quality before activating QualiVision.
•Residual images from earlier conferences no longer display in new conferences.
•The Welcome slide displays correctly.
•Enhanced audio quality in G.728 calls.
•Background noise is eliminated in G.722 calls when endpoints are muted.
•TANDBERG MXP, TANDBERG classic and Aethra endpoints are interoperable with H.264 and presentation view-enabled services.
•Cascaded conferences with H.239 perform correctly with simultaneous presenters.
•Custom layouts in a master cascaded conference function correctly.
•Mute/Unmute All is supported in cascaded conferences.
•Cascaded conferences in a SIP environment are supported.
•The same participant number is displayed in the Conference Control user interface of the Master and Slave MCUs.
•Cascading no longer causes the EMP to reboot.
•Black screen no longer appears in cascaded conferences.
The MCU functions correctly with ISDN gateway downspeeding or resync.
•Support added for multiple Hold/Resume operations
Open Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1
This section describes possible unexpected behaviors by Cisco Unified Videoconferencing 3500 MCU Release 5.1, sorted by component. Unless otherwise noted, these caveats apply to all Cisco Unified Videoconferencing 3500 MCU 5.x releases up to and including Cisco Unified Videoconferencing 3500 MCU 5.1.
You can find the latest resolved caveat information for Cisco Unified Videoconferencing 3500 MCU Release 5.1 by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
MCU open caveats are included in the following categories:
Endpoint Information Display in MCU Conference Control
•On the statistics page, SIF resolutions may appear as CIF resolutions.
•Video resolution for participants in High Definition conferences may display incorrectly.
•If the H.323 registration mode is set to gateway when enabling H.243, then in cascaded conferences endpoints appear twice in the conference control. To resolve this, either disable H.243 or change H.323 registration mode to MCU.
Note Changing the H.323 registration mode to MCU may cause interoperability issues with the Cisco IOS H.323 Gatekeeper.
•With some ISDN endpoints that are connected through a gateway, H.243 conference control may not function.
•When H.243 is enabled, Far End Camera Control (FECC) to some TANDBERG endpoints may not function. To resolve this, disable H.243.
•Chair Control cannot be taken from the endpoint menu via H.243 commands in conferences which are assigned with a chair PIN code. Chair Control can be taken via the MCU DTMF conference control menus.
•Encryption does not function with TANDBERG endpoints that support both AES and DES and that are configured to only enable DES. To resolve this, enable AES in the endpoint.
•To fully utilize MCU port capacity when working with encryption, we recommend that you set the encryption mode to "Encryption required" in your service definition.
•Using `0' as the service prefix causes unpredictable results. Refrain from using `0' as the service prefix.
•Connect the MCU module and all registered EMP modules to the same IP switch.
•Joining more than 12 4CIF endpoints into a full-screen conference may result in significant video delays.
•In cascaded conferences with H.239, keep only one presentation open at any given time and close all other presentations. Using simultaneous presenters in a cascaded conference may result in the display of more than one presentation to participants.
•Enabling H.243 in the Settings > Conference Control section may cause H.239 interoperability issues with Aethra endpoints.
•Some ISDN endpoints connected to the MCU via a gateway may fail to send the presentation channel when using H.239 XGA.
•When working with H.239 XGA in a conference including Sony and Polycom or Sony and TANDBERG endpoints, the presentation video from the Polycom or TANDBERG endpoint may not appear on the Sony endpoint.
•In some cases, the presentation video may not be visible when working with TANDBERG endpoints. Stopping and restarting the presentation video resolves the problem.
•In a cascaded conference, the conference control of the child conference does not indicate the identity of the active speaker. A workaround is to view the conference from the parent MCU that does display this correctly.
•In a cascaded conference, the encryption status of individual participants may display incorrectly.
•Participants on the same Slave conference cannot control each other via the Master conference. Control is available via local layouts.
•It is not possible to create an ad hoc SIP conference from an existing conference.
•Voice Activation on a Slave conference is available using the following procedure only:
–In the Conference Control interface of the Master conference, drag and drop the Voice Activation asterisk (*) to one of the sub-frames.
–If auto-switching is enabled, disable it and then enable it again.
–If auto-switching is disabled, enable it and then disable it again.
•When connecting Sony PCS1 in SCCP mode using H.264, video may not open. A workaround is to use H.263 when connecting Sony PCS1 using SCCP.
•Using the TANDBERG Transfer button in an SCCP conference with only one participant results in a video freeze or no video. This does not happen in conferences with more than one participant.
•We recommend that you do not change SCCP settings in the Protocols > SCCP screen while there are ongoing SCCP calls.
•The video display to some attendees may not show all the participants when you invite more than three attendees to an SCCP conference. To solve this issue, disable the No self-see feature.
•In SCCP conferences, video channels are closed and may fail to reopen when you use the hold/resume mechanism.
•Changes to TFTP server IP addresses do not take effect until you reset the MCU.
•When modifying an active SCCP service to work with G.722 or G.728, inaccurate data may appear in the web user interface after the MCU reboots. To solve this issue, log out and then log back in to the MCU Administrator web user interface.
•Ensure that the "Ports allocated to SCCP" parameter is set to 0 when the SCCP protocol is disabled.
•The MCU is not capable of supporting 96 SCCP ports unless FECC is disabled.
•Inconsistent port availability on SCCP partition.
•The SCCP Subconference feature does not operate correctly.
•The maximum number of participants using FECC is limited to 72 per MCU. Additional participants are supported only if FECC functionality is disabled. A high load of simultaneously joining parties may also affect the total number of supported and limit this number to 72 even when their FECC functionality is disabled. Disabling FECC support on the MCU side removes these restrictions.
•Disconnect and/or reconnect issues occur when approximately 96 ports are in use.
•T.120 does not function across cascaded conferences.
•The Join Data Conference button on the MCU conference control page allows users to join T.120 data conferences from the computer running the conference control. This button is currently not available and will be re-added in a later patch.
•Set the configT120OutCallRecvOnly advanced command to 1 to modify T.120 default behavior on outgoing calls from "sendonly" to "recvonly". Return the value to 0 to revert the default behavior to "sendonly".
•When the MCU is reset while there are calls connected, the web "Restarting..." pop-up is not closed automatically upon MCU power up. Refresh your web browser to clear the pop-up.
•Do not reboot the MCU while a SCCP conference is active.
Note We strongly recommend that you do not reboot the MCU while the Conference Control interface is open and in use.
•When the Windows Start Navigation sound is enabled, a continuous clicking sound is heard when the Conference Control interface automatically refreshes. Disable this sound in the Sounds and Multimedia configuration of the Control Panel.
•The Conference Control web interface operates in polling mode with updates every 10 seconds. To refresh information on the screen, reselect the tab you are currently viewing. Pressing the browser Refresh button causes you to exit from the Conference Control and displays the login screen.
•The Conference Control and Login screens are best viewed in full screen mode (1024 x 768 fps).
•The MCU allows you to open multiple Conference Control browser screens at the same time. It is recommended that you close screens in which you are not currently working to avoid confusion and performing operations on the wrong conference.
•Set the Enable in-band DTMF detection advanced command to "Only during IVR" to allow a conference call of 96 participants with 4 registered EMP modules.
•Changing configuration settings sometimes requires a reboot of the system (for example, after enabling/disabling H.323 or other protocols). In such cases, the web user interface prompts the user to confirm the reboot. We strongly recommend that you do not use the system for videoconferencing until you have performed the reboot.
•We recommend that you set the Ethernet port speed and duplex parameters of both the MCU and the switch to Auto. Set these parameters to 100 Mbps full duplex only if you experience port speed negotiation problems. Ensure that the Ethernet port speed and duplex parameter values on the MCU and the switch are identical.
This section provides updates to the documentation.
Omissions about Registering the Online Help
In Release 5.1 of the Cisco Unified Videoconferencing 3545 MCU, 3515 MCU12, and the 3515 MCU24, the installation and upgrade guides and the configuration guides describe how to use the "file" path when registering the online help. Step 3 of the procedure should also include the HTTP path:
Step 3 In the Online help URL field of the Device Web tab, enter the directory path to the help files you installed on your PC.
Use this form:
where computerName is the name of the computer on the network and sharedDirectory is the path to the Online Help folder on the CD-ROM. For example:
Enter the directory path to the help files you installed on your PC. Paste the URL where the online help is located up to, but not including, the mcu folder as follows:
You can access the following related documentation at: http://www.cisco.com/en/US/products/hw/video/ps1870/prod_maintenance_guides_list.html.
•Configuration Guide for Cisco Unified Videoconferencing 3515 MCU12 and MCU24 Release 5.1
•Installation and Upgrade Guide for Cisco Unified Videoconferencing 3515 MCU12 and MCU24 Release 5.1
•Configuration Guide for Cisco Unified Videoconferencing 3545 MCU Release 5.1
•Installation and Upgrade Guide for Cisco Unified Videoconferencing 3545 MCU Release 5.1
•User Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
•Troubleshooting Guide for Cisco Unified Videoconferencing 3500 MCU Release 5.1
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.