Contents

Downgrade Information

You can downgrade from Cisco IPVC 35xx MCU Release 4.1 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:

http://www.cisco.com/techsupport/contacts

New and Changed Information

New Software Features in Release 4.1

Cisco IPVC 35xx MCU Release 4.1 includes the following new features that have been added since Cisco IPVC 35xx MCU Release 4.0:

•DTMF conference control with out-of-band DTMF signals.

•Manual audio gain control

•Skinny Client Control Protocol (SCCP) conference limitation

•Enhanced Media Processor (EMP) mismatch indication

•MP failure indication

•Support for early media in Session Initiation Protocol (SIP)

Resolved Caveats - Release 4.1

The following caveats have been resolved since Cisco IPVC 35xx MCU Release 4.0:

•When working with transcoding services in See you see me mode, the Cisco IPVC 35xx MCU operates correctly if the current speaker uses a different video codec to the previous speaker.

•When using the Cisco IPVC 35xx MCU in CP4 asymmetric mode, the dynamic layout jumps from 1 to 4 (single screen to Continuous Presence (CP)) when the second participant joins.

•Rate matching with more than one output now operates correctly.

•Locked participants in a voice-activated single screen conference now appear correctly.

•H.235 and H.239 interoperability issues with Aethra endpoints is now resolved.

•Calls no longer disconnect when the SIP message Transport field is set to TLS.

•When using the Cisco Gatekeeper, the conference no longer disconnects after 15 minutes.

•The Conference Control interface now shows Asian language text.

•Voice activation video switching works when the current speaker is muted.

•H.239 and H.235 encryption interoperability issue with Tandberg endpoints which causes the video on the live and presentation channels to not open is now resolved.

•When working with the Cisco Gatekeeper and an alternate gatekeeper, if the Cisco IPVC 35xx MCU has an active conference and call, and the main gatekeeper is shut down, the Cisco IPVC 35xx MCU now always registers to the alternate gatekeeper.

Known Issues

The following is a list of known issues for Cisco IPVC 35xx MCU Release 4.1 are divided into the following categories:

General Issues

•When connecting a Cisco IPVC 35xx MCU configured as MP only to MCU-15, MCU-03A, or MCU-06A, the maximum call capacity is 26, 45, and 90 respectively, and not 150.

•The performance of the Conference Control interface on PCs with low CPU and very large conferences can be slow.

•Not all participants appear when using auto-switch in a CP cascaded conference and then switching to a full screen display.

•When changing the user name or password used to log into the Conference Control interface, it is impossible to perform Chair Control tasks until you log out and 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 be able to connect to the Cisco IPVC 35xx MCU using Telnet.

•Dynamic layout does not work for a child view when the Preserve Local View option 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.

•When connecting to an empty transcoded See you see me cascaded conference, the first participant experiences:

–Seeing themself but video is frozen when dialing in to the master conference.

–Occasional "slow entrance" (the video is built slowly) when dialing into the slave conference.

•When using the transcoded See you see me option, text overlay might not function correctly.

Compatibility Issues

•Do not register more than two Cisco IPVC 3540 Application Server (AS) Module for Data Collaboration Server (DCS) applications to the same Cisco IPVC 35xx MCU.

Interoperability Issues

•There is a lengthy delay when sending Far Endpoint Camera Control (FECC) data through a gateway.

•Video freezes repeatedly on the ISDN side of a 1920 Kbps call.

•The Cisco Gatekeeper does not support service prefixes that include the asterisk (*) character.

•The video image might freeze on TANDBERG endpoints working in asymmetric video encoding mode (sending H.261, receiving H.263). To resolve this issue, when configuring conference views, 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 recording 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 View Settings dialog box of the Services tab in the Administrator interface.

•H.264 support is not functional with SIP.

•Use the mc:g728nonstd advanced command if you experience audio problems when using VCON endpoints with the G.728 audio codec. Disable the G.728 codec by using the mc:g728std advanced command. The default setting for the mc:g728std advanced command is Disable. Use the default setting with all endpoints except VCON endpoints.

•Far End Camera Control (FECC) might not work properly when sent to Aethra endpoints.

Web/Control Issues

•To reconfigure the service profile processor definition from MP to Auto in the Conference View settings, you need to delete the current service and create a new one.

•We recommend that you use Microsoft Internet Explorer version 5.5 and later. You might encounter some interoperability issues when using Netscape 7.0.

•When logging on to the Administrator interface, you might hear the Microsoft Windows operating system audio error indication.

•When N/A appears in the Customize Views dialog box or the Statistics tab of the Conference Control interface, statistics reporting is not available for this channel.

•Do not manually refresh the Conference Control interface between inviting a cascaded conference and until it connects. Wait instead for the auto refresh of the Conference Control interface.

•In a 4 + 3 layout (Continuous Presence 2 x 2 in one quadrant of another Continuous Presence 2 x 2 layout), video positions do not appear correctly in the Conference Control interface.

Encryption Issues

•Encryption does not work with H.323 tunneling.

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

Note The Sony PCS-1 version 3.01 works with the standard H.239 implementation and the workaround is not necessary.

Related Documentation

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: