Table Of Contents
Release Notes for Cisco IPVC 3511 MCU, Cisco IPVC 3511 MCU with EMP (E), and Cisco IPVC 3540 MCU Release 4.0
March 31, 2005
This document describes all of the notable fixes, outstanding issues, features, and capabilities for Cisco IPVC MCU Release 4.0 for the following Cisco products:
•Cisco IPVC 3511 Multipoint Control Unit (MCU)
•Cisco IPVC 3511 Multipoint Control Unit (MCU) with EMP (E)
•Cisco IPVC 3540 Multipoint Control Unit (MCU) module
Use these release notes with Cisco IPVC 3511 MCU and Cisco IPVC Administrator Guide for Release 3.2.
Note In this document, these products are named Cisco IPVC 35xx MCU unless otherwise noted.
These release notes discuss the following topics:
You can downgrade from Cisco IPVC 35xx MCU Release 4.0 to Release 3.5.33. You can download Release 3.5.33 from Cisco Connection Online (CCO), or you can contact the Cisco Technical Assistance Center (TAC) for additional information. For a complete list of Cisco TAC contacts, go to this URL:
New and Changed Information
New Software Features in Release 4.0
Cisco IPVC 35xx MCU Release 4.0 includes the following new features that have been added since Cisco IPVC 35xx MCU Release 3.5.24:
SCCP Continuous Presence Support
Cisco IPVC 35xx MCU now features Skinny Client Control Protocol (SCCP) Continuous Presence support (CP). For further information on how to configure a Cisco IPVC 35xx MCU service, see "Creating a Service" in Chapter 3 of the Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide.
SCCP H.264 Support
Cisco IPVC 35xx MCU Release 4.0 now extends H.264 support for SCCP.
SCCP Conference Control
Cisco IPVC 35xx MCU Release 4.0 now provides SCCP conference control.
Improved Video Quality Through QualiVision™
QualiVision™ provides improved video quality in networks with packet loss. You can specify policies for filtering video update requests from endpoints that are connected to conferences, which are hosted on the Cisco IPVC 35xx MCU. To do so, click the Settings tab in the Administrator interface; then click QualiVision settings.
The QualiVision Settings section appears only if you enable the Show QualiVision Settings advanced
command. In the QualiVision Settings section, you can configure outgoing and incoming channel classification settings, as well as intra-frame limits.
Note We recommend that you use the default settings for channel classification and intra-frame limiting options
Configuring Outgoing Channel Classification Settings
In the QualiVision Settings section, click Outgoing channel classification to display the Outgoing channel classification dialog box. Table 1 summarizes the fields in the Outgoing channel classification dialog box.
Configuring Incoming Channel Classification Settings
In the QualiVision Settings section, click Incoming channel classification to display the Incoming channel classification dialog box. Table 2 summarizes the fields in the Incoming channel classification dialog box.
Configuring Intra-Frame Limiting Settings
In the QualiVision Settings section, click Intra frame limiting settings to display the Intra frame limiting dialog box. In this dialog box, you can configure the rate of intra-frames that the Cisco IPVC 35xx MCU sends according to the endpoint class.
Cisco IPVC 35xx MCU Release 4.0 now features encryption that is based on the H.235 standard and supports the following encryption algorithms:
•DES, with an encryption key of 56 bits.
•AES, with an encryption key of 128 bits.
Cisco IPVC 35xx MCU encryption operates in either one of the following modes or can be disabled entirely:
•Best effort—This mode implements a "best effort" encryption algorithm. If an endpoint supports encryption, the endpoint connects in an encrypted way. If not, the endpoint connects without encryption.
•Encryption required—This mode only connects encrypted calls. Encryption can either be AES 128 or DES 56. Non-encrypted calls are not allowed to connect.
•Strong encryption required—This mode only allows AES 128 encrypted calls. Endpoints that do not support AES 128 are not allowed to connect.
Note An encrypted call uses double the resources of a regular call for all bandwidth rates. Cisco IPVC 35xx MCU capacity when encryption is supported is therefore half of regular capacity.
Table 3 summarizes the Cisco IPVC 35xx MCU encryption capabilities.
The following channels support encryption:
•Far End Camera Control (FECC)
Note All channels (audio, video, FECC, incoming, and outgoing) on the same call must have the same encryption levels. If the same encryption on all channels cannot be achieved, the call disconnects.
H.264 Continuous Presence Support
Cisco IPVC 35xx MCU Release 4.0 now features H.264 Continuous Presence support for video layouts up to CP4.
To configure CP4:
Step 1 In the Conference View section of the Add (or Edit) Service dialog box, click Add View or Edit Conference View.
The Edit View dialog box appears.
Step 2 In the Video Schemes section, click Add.
The Add Video Scheme dialog box appears.
Step 3 In the Video format field, select H.264.
Step 4 Click OK.
Step 5 In the Use Processor field, choose EMP.
Step 6 Click OK.
Access Control List
An administrator can use the access control list in the Security tab of the Configuration Board to specify which IP ranges can have access to the Administrator interface.
Initially Muted Mode Disable Option
For the first participant in a conference, you can now disable the initially muted mode. This way, all participants are automatically in muted mode, except for the first participant. This mode is useful for lecture scenarios in which the lecturer dials in ahead of the other participants.
Unified Cisco IPVC 35xx MCU-EMP Quality of Service Settings
Cisco IPVC 35xx MCU Quality of Service (QOS) settings now automatically download to all Enhanced Media Processors (EMPs) connected to the Cisco IPVC 35xx MCU.
This section contains important notes about Cisco IPVC 35xx MCU Release 4.0.
To use some of the new features in Cisco IPVC 35xx MCU Release 4.0, you must use a Cisco IPVC Enhanced Media Processor (EMP) with Release 3.0.5. With a valid Software Application Support plus Upgrades (SASU) contract, you can download Cisco IPVC EMP Release 3.0.5 software online through Cisco Connection Online (CCO).
SCCP EMP Resources
At boot up, the Cisco IPVC 35xx MCU reports EMP resources associated with SCCP conferences to Cisco CallManager. These resources are reserved and subtracted from the remaining resources available to H.323 conferences.
Resolved Caveats - Release 4.0
Caveats resolved since Cisco IPVC 35xx MCU Release 3.5.24 are listed in three sections:
•The mute and unmute buttons on the Control Bar of the Participants tab function correctly.
•Registration and unregistration for XML notifications through the XML connection function correctly.
•The indication for a dialed unknown number displays properly in the Conference Control web user interface.
•Memory leak when DCS is registered to the Cisco IPVC 35xx MCU fixed.
•Audio transcoding in SCCP (DDTS CSCuk55763).
•Web server can correctly handle an incoming request with a long cookie.
•Internet Explorer operates correctly on switching between the MC/Board/System applets when using Sun JVM 1.4.0.
•Conference Control displays correctly at resolutions higher than 1024 x 768 fps.
•Improved interoperability with Aethra and Alcatel endpoints.
•Improved video switch-over to an active speaker whose endpoint does not respond to Video Fast Update (VFU) requests.
•Dynamic layout now responds when disconnecting an active endpoint.
•Improved video quality in sequences containing fast motion.
•Visible artefacts no longer appear on high-contrast video.
•EMP no longer disconnects when a single-screen conference with rate matching is in progress and a second conference with the same service is repeatedly opened and closed.
•You can now use the smallest font size in text overlay.
The following is a list of known issues for Cisco IPVC 35xx MCU Release 4.0:
The following is a list of known general issues:
•The Cisco IPVC 35xx MCU can only register to the SIP proxy at boot up or reboot if the SIP proxy is already up and running.
•The EMP card cannot occupy a system slot in the chassis.
•Web conference control performance on PCs with low CPU and very large conferences might be slow.
•Not all the participants appear when using autoswitch in a CP cascaded conference and then switching to a full screen display.
•When changing the user name or password that is used to log in to the system, it is impossible to perform chairman operations in the conference control until you log out and then log in again with the new user information.
•When changing the Cisco IPVC 35xx MCU security mode from High or Maximum to Standard, you must restart the Cisco IPVC 35xx MCU to telnet to it.
•Dynamic layout does not work for a child view when Preserve Local View is applied to the child view.
•If video output is set to more than 1000 Kbps, video input can be limited when using H.261 or H.263 codecs with specific layouts.
•If you use a layout with 10 or more sub-frames with video output of 704 Kbps or higher, video input is limited to 320 Kbps when using the H.261 codec.
The following is a list of known compatibility issues:
•Do not register more than two DCS applications to the same Cisco IPVC 35xx MCU.
•Configuring H.323 tunneling and H.323 Fast Start together can cause unexpected behavior on the Cisco IPVC 35xx MCU.
•Cascading does not work well when the Cisco IPVC 35xx MCU is set to H.323 Fast Start.
•When working with transcoding services in See you, see me mode, if the current speaker uses a different video codec than the previous speaker, the See you, see me mode automatically changes to All see one mode. All see one mode reverts back to See you, see me mode when the video codec used by the next speaker matches the video codec used by the current speaker.
The following is a list of known interoperability issues:
•ISDN endpoints cannot send a 4CIF stream.
•There is a delay when sending FECC data via a gateway.
•Video freezes repeatedly on the ISDN side of a 1920 Kbps call.
•The Cisco IOS Gatekeeper does not support service prefixes that include an asterisk (*).
•The video image might freeze on TANDBERG endpoints working in asymmetric video-encoding mode (sending H.261, receiving H.263). To resolve this issue, ensure that the H.263 scheme on the Cisco IPVC 35xx MCU is set as the first priority, and H.261 is set as the second priority.
•When using multiple video-encoding modes, we recommend that you define codecs in decreasing numerical order. For example, define an H.264 video scheme before an H.263 video scheme in the Video Settings dialog box, which you can access from the Administrator interface Services tab.
•Use the mc:g728nonstd advanced command if you experience audio problems when using endpoints with the G.728 audio codec. Disable the G.728 codec with the mc:g728std advanced command. The default setting for the mc:g728std Advanced Command is Disable. Use the setting with all endpoints except VCON endpoints.
•FECC might not work properly when sent to Aethra endpoints.
•H.264 support is not functional with SIP.
Web and Control Issues
The following is a list of known web and control issues:
•To reconfigure the service profile processor definition from MP to Auto in the Conference View settings, delete the current service profile and create a new service.
•We recommend that you use Microsoft Internet Explorer version 5.5 and later releases.
•You might encounter some interoperability issues when using Netscape 7.0 browser.
•When logging in to the Cisco IPVC 35xx MCU web interface, you might hear the Windows operating system audio error indication.
•When N/A appears in the Customize Views list of the Participant List tab and Statistics tab in the Conference Control interface, statistical reporting is not available for this channel.
•Do not manually refresh the Conference Control web page in the time between inviting a cascaded conference and it connects: wait for the autorefresh.
•In 4+3 layout (Continuous Presence 2x2 in one quadrant of another Continuous Presence 2x2 layout), video positions do not display correctly in the web interface.
The following is a list of known encryption issues:
•Encryption does not work with H.323 tunneling.
•Encryption does not work with an H.239 service using more than one video scheme.
H.239 Dual Video Issues
The following is a list of known H.239 Dual Video issues:
•When Polycom VSX-7000 does not transmit a presentation, change the presentation layout in the Cisco IPVC 35xx MCU service to 30 frames per second (fps).
•Older versions of Sony endpoints implement a non-standard H.239. Due to this non-standard implementation, the presentation channel does not open when working with endpoints of other vendors.
–Sony PCS-1 version 3.01 works with the standard H.239 implementation and the workaround is not necessary.
•There are interoperability issues when working with Aethra endpoints using an XGA presentation layout.
For additional information about Cisco MeetingPlace products or about obtaining documentation or technical support, see the Guide to Cisco MeetingPlace Conferencing Documentation and Support at the following URL:
For information about Cisco IPVC 35xx MCU functionality related to Cisco CallManager 4.1, see Cisco CallManager 4.1 documentation at the following URL:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.