Cisco Cisco Unified MeetingPlace Video Integration
9
Release Notes for Cisco Unified Videoconferencing 3500 Release 5.1.2
OL-14189-01
Caveats for Cisco Unified Videoconferencing 3500 MCU Release 5.1.2
•
Endpoint Information Display in MCU Conference Control, page 9
•
H.243, page 9
•
Encryption, page 9
•
Configuration, page 9
•
Video Quality, page 10
•
H.239, page 10
•
Cascading, page 10
•
SCCP, page 10
•
T.120, page 11
•
Web Reboot, page 11
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,
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.
IOS H.323 Gatekeeper.
•
With some ISDN endpoints that are connected through a gateway, H.243 conference control may not
function.
function.
•
When H.243 is enabled, Far End Camera Control (FECC) to some TANDBERG endpoints may not
function. To resolve this, disable H.243.
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.
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.
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.
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.
prefix.
•
Connect the MCU module and all registered EMP modules to the same IP switch.