Guest

Cisco Unified MeetingPlace

Release Notes for Cisco Unified Videoconferencing 3500 Release 5.1.2

  • Viewing Options

  • PDF (160.1 KB)
  • Feedback
Release Notes for Cisco Unified Videoconferencing 3500 Release 5.1.2

Table Of Contents

Release Notes for Cisco Unified Videoconferencing 3500 Release 5.1.2

Contents

Introduction

System Requirements

Upgrading and Downgrading MCU Versions

Upgrading from a previous build of MCU version 5.x to MCU version 5.1.2

Downgrading from MCU version 5.1 to version 5.0

Downgrading from MCU version 5.1.2 to version 5.1.0

Upgrading and Downgrading EMP Versions

Upgrading from a previous build of EMP version 5.x to EMP version 5.1.1

Downgrading from EMP version 5.1.1 to version 5.1.0 or version 5.0.0

New and Changed Information

Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

Resolved Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

Open Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

Troubleshooting

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco Unified Videoconferencing 3500 Release 5.1.2


Revised: July 31, 2007, OL-14189-01

These release notes describe the new features and caveats for

Cisco Unified Videoconferencing 3515 MCU Release 5.1.2

Cisco Unified Videoconferencing 3545 MCU Release 5.1.2

Cisco Unified Videoconferencing 3545 EMP Release 5.1.1

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:

http://cisco.com/kobayashi/sw-center/sw-video.shtml

Contents

These release notes discuss the following topics:

Introduction

System Requirements

New and Changed Information

Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

Troubleshooting

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

The Cisco Unified Videoconferencing 3500 MCU is a high performance multipoint video conferencing and media processing system that provides 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.

System Requirements

Cisco Unified Videoconferencing 3500 Release 5.1.2 only operates with the following products:

Cisco Unified Videoconferencing 3515 MCU12 Release 5.1.2

Cisco Unified Videoconferencing 3515 MCU24 Release 5.1.2

Cisco Unified Videoconferencing 3545 MCU Release 5.1.2

Cisco Unified Videoconferencing 3545 EMP Release 5.1.1

You cannot install version 5.1.2 on older IP/VC products, including the Cisco IP/VC 3511 and 3540 Series products.

Upgrading and Downgrading MCU Versions

Upgrading from a previous build of MCU version 5.x to MCU version 5.1.2

Procedure


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 v5.1 Upgrade Utility.

Provide the target IP address.

Click Customize.

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.


Downgrading from MCU version 5.1 to version 5.0

Before You Begin

When downgrading to MCU version 5.0.0.58, ensure that you are using the appropriate software for your platform (3515 or 3545).

Procedure


Note Version.5.0 refers to either MCU version 5.0.1.0.12 (and siblings) or to MCU version 5.0.0.0.58 units. Version.5.1 refers to either MCU version 5.1.0.0.24 (and siblings) or to MCU version 5.1.1./5.1.2 (and siblings) units.



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.0 application with the MCU default configuration.

Run the MCU v5.0 Upgrade Utility.

Provide the target IP address.

Click Customize.

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 downgrade procedure.

Wait while the MCU performs the downgrade 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 downgrade has been performed successfully.


Step 3 Run the MCU v5.0 Upgrade Utility again.

Click Customize.

This time, ensure that the MCU Factory Default Configuration option is selected.

Ensure that all other Customize options are cleared.

Click Upgrade to perform the downgrade procedure. This time only the factory default configuration is uploaded.

Wait while the MCU performs the downgrade 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 downgrade has been performed successfully.


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.0 configuration .ini file.


Downgrading from MCU version 5.1.2 to version 5.1.0

Procedure


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.0 application with the MCU default configuration.

Run the MCU v5.1.0 Upgrade Utility.

Provide the target IP address.

Click Upgrade to perform the downgrade procedure.

Wait while the MCU performs the downgrade 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 downgrade has been performed successfully.


Step 3 (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.0 configuration .ini file.


Upgrading and Downgrading EMP Versions

Upgrading from a previous build of EMP version 5.x to EMP version 5.1.1

Procedure


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.


Downgrading from EMP version 5.1.1 to version 5.1.0 or version 5.0.0

Burn the EMP version 5.0 application as follows.

Procedure


Step 1 Run the EMP v5.0 Upgrade Utility.

Step 2 Provide the target IP address.

Step 3 Click Upgrade to perform the downgrade procedure.

Step 4 Wait while the EMP performs the downgrade 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 downgrade has been performed successfully.



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 for switched conferences.

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.

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.

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.

Set the sccpsendfctofirstvcall advanced command to 1 to enable SCCP flow control. The advanced command is set to 0 by default.

SCCP Partitioning resources support API. The MCU reports via the XML API the level of resources available for non-SCCP calls.

XML API Get Conferences List Request supports the use of a user name/password combination.

Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

This section includes the following topics:

Resolved Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

Open Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

Resolved Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

MCU resolved caveats are included in the following categories:

Endpoint Information Display in MCU Conference Control

Local View

Configuration and Web Interface

H.323 Dialing

DTMF Conference Control

T.120

Encryption

Video Quality

Audio Quality

H.239

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.

The MCU Conference Control web user interface launches correctly.

Local View

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.

The XSS vulnerability via the search facility in the online help is closed.

H.323 Dialing

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

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

Encryption and H.239 now function together correctly.

Video Quality

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.

Audio Quality

Enhanced audio quality in G.728 calls.

Background noise is eliminated in G.722 calls when endpoints are muted.

H.239

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.

Cascading

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.

Gateway Connectivity

The MCU functions correctly with ISDN gateway downspeeding or resync.

SCCP

Support added for multiple Hold/Resume operations

Open Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2

This section describes possible unexpected behaviors by Cisco Unified Videoconferencing 3500 MCU Release 5.1.2 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.2.

You can find the latest resolved caveat information for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2 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://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


MCU open caveats are included in the following categories:

Endpoint Information Display in MCU Conference Control

H.243

Encryption

Configuration

Video Quality

H.239

Cascading

SCCP

T.120

Web Reboot

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.

H.243

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.

The maximum number of parties is incorrectly displayed in the Services tab.

Encryption

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.

Configuration

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.

Video Quality

Joining more than 12 4CIF endpoints into a full-screen conference may result in significant video delays.

When there is a Cisco Unified Communications Manager cluster with an MCU conference bridge, and an endpoint registered to a remote Cisco Unified Communications Manager cluster calls into a SIP conference via the H.323 intercluster trunk, a Hold/Resume operation performed on the endpoint connected via the trunk causes a black video frame to be sent to local endpoint.

An MCU user may be unable to receive video from a remote MCU user when the remote party holds and then unholds a call while in a four-party conference.

H.239

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.

Cascading

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.

Multi-participant layout views are not available for meetings which cascade multiple EMPs.

SCCP

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.

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.

When dialing out from the MCU to an SCCP endpoint via an H.323 gatekeeper-controlled trunk, the bandwidth from the MCU to the endpoint is as specified in the MCU user interface, but the bandwidth from the endpoint to the MCU is the same as the default value set for the service in use.

In some cases, the SCCP partition cannot access all available ports.

When hosting conferences on the SCCP partition, the MCU does not tear down calls properly before resetting when an SCCP conference is in session.

T.120

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."

Web Reboot

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 an 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.


Troubleshooting

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 "disable" to allow a conference call of 96 participants with 4 registered EMP modules.

Related Documentation

You can access the following related documentation at: http://www.cisco.com/en/US/products/hw/video/ps1870/tsd_products_support_series_home.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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html