Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Video Integration Limitations and Restrictions

From DocWiki

Jump to: navigation, search

Cisco Unified MeetingPlace, Release 6.x > Cisco Unified MeetingPlace Video Integration


Limitations and Restrictions

This section contains the following information:

See also the Release Notes for Cisco Unified MeetingPlace Video Integration Release 5.4 and Release 6.0, and Video Administration Release 5.6 here:

Apple Safari Restrictions

Cisco Unified MeetingPlace Web Conferencing does not support joining a video conference from the Apple Safari client. Users attending a web conference by using Safari cannot see the Use My Video Endpoint Number field and cannot join video conferences.

Configuration Considerations for Video Administration

  • Cisco Unified MeetingPlace Video Administration can set only one Cisco MCM gatekeeper as its Cisco Internal Gatekeeper's neighbor.
  • In certain countries, such as the United States, an area code is usually dialed with a phone number. In such cases, under Resource Management > Gateway in Video Administration, check the Always Dial Area Code check box.
  • Ensure that terminal area codes are defined correctly and that domestic long-distance prefixes are omitted. DID numbers are currently assigned on a per-endpoint basis rather than on a per-meeting basis. This is an internal configuration and cannot be changed by using the Video Admin Configuration Tool or the Video Administration web interface.
  • To ensure that web pages and pop-up windows are displayed normally, we recommend that you set the screen resolution to a standard resolution, such as 800 x 600 pixels or 1024 x 768 pixels. The minimum recommended resolution is 800 x 600 pixels, and the recommended font size is Normal or Large.
  • The MCU service template name and description, terminal name, and gateway service prefix can contain only ASCII text. Unicode and other double-byte characters (such as Chinese, Japanese, Korean, and Hebrew characters) should not be used.
  • Video Administration supports the Cisco Unified Videoconferencing 3500 MCU version 5.1 only in normal capacity configuration mode. High capacity mode is not supported. Additionally, high definition endpoints are not supported.

Database Unavailable During Initialization of Video Administration

If the database is not available during Video Administration initialization, restart the service when the database is available. If the connection between the database and Video Administration is lost after Video Administration initialization, Video Administration will function normally once the database is operating.

Expected Behavior for Video Administration

  • If an MCU is taken offline, in-session meetings running on the MCU are canceled. The meeting records are moved to the History tab in the All Meetings and My Meetings sections.
  • Taking an MCU offline and causing a large number of conferences to be rescheduled may result in an out-of-memory error.
  • Cisco Unified Videoconferencing MCU version 4.x features, such as Encryption and Qualivision, function properly with Video Administration but are not displayed as meeting type information or in the In-Meeting Control user interface.
  • If someone calls from an audio phone that has video capability to the video

conference, the system shows the endpoint with video and audio capability, even if the user only is using the audio capabilities.

Limitations of Video Administration

  • Cascading cannot take place between a Cisco Unified Videoconferencing MCU version 4.x and an MCU version 5.0. Video Administration supports cascading only by using the same service on each MCU.
  • Disconnecting Video Administration from an MCU while a conference is taking place may cause terminal participants in that conference to be disconnected.
  • For cascaded MCU conferences, only one terminal participant on a slave MCU can be displayed on the conference layout.
  • If the No Self-See setting is selected for an MCU service, when dragging terminals to the layout box on the In-Meeting Control screen, certain terminals are not displayed since they comply with the No Self-See restriction.
  • The Subconf list on the In-Meeting Control screen displays inconsistent information for a cascaded conference.
  • Video Administration does not support the Force Conference PIN Protection field in the MCU service definition.
  • When scheduling a conference with 3G terminals, a terminal defined with a bandwidth of 64Kbps video is actually connected at 64Kbps audio. A workaround for this problem is to define the 3G terminal as an IP terminal whose E.164 number is a combination of the 3G Gateway service number and the phone number of the 3G terminal.
  • When scheduling an MCU meeting with a meeting password, when the MCU authorizes a terminal by using the meeting password, Video Administration does not receive notification of the authorization event. Video Administration can determine this information only by polling MCU conference status, which may cause a delay in the notification of the authorization event to Cisco Unified MeetingPlace.
  • In the Resource Management section of Video Administration, when you change the settings for a terminal, the changes are not reflected on the Terminals tab of the Meeting Templates and My Meetings sections.
  • Reporting on a large number of conferences (on the Upcoming tab or the History tab) may cause an out-of-memory error.
  • Adjusting the server clock disrupts the status of any recurring meetings that are scheduled.
  • Each time you restart the Video Administration application, allow a few minutes for the service to initialize correctly. It is possible that some meetings may need to be extended during this time. In that case, meetings are not extended.
  • The External conference authorization policy field on the Settings > Conference Management page must be set to None.
  • If a meeting is set in waiting room mode, an H.323 terminal cannot unlock the meeting unless it is designated as the host terminal of this meeting.
  • MeetingPlace Video Integration does not support endpoint-initiated ad-hoc or virtual room meetings by dialling a service prefix plus random number to form a meeting ID.
  • Video Administration does not support the “auto” service in the H.320 gateway where the bandwidth is negotiated dynamically when a terminal connects.
  • Video Blade fragmentation issues may occur when one meeting is scheduled on a Video Blade using a desktop service, and a second meeting is scheduled on the same Video Blade using a high rate service. Even though the combined port usage of the two meetings may be less than the capacity of a Video Blade, the meeting may still fail if the desktop meeting occupies the Video Blade DSP resource in such a way that only whole ports are left available for the high rate meeting, and only 1 or 2 ports are available. This is a rare event.
  • When dialing into a Video Administration meeting, the MCU meeting ID is displayed on the endpoint monitor.
  • Terminals in restricted mode (56K) cannot access a gateway in unrestricted mode (64 Kbps).
  • Adjusting the server clock disrupts the status of any recurring meetings that are scheduled.
  • Upload of a high definition continuous presence MCU service to another MCU that does not support high definition continuous presence is not supported.
  • MCU features, such as encryption and Qualivision, function properly but are not displayed as meeting type information or in the in-meeting control user interface.
  • When working with an MCU service that supports presentation view, the presentation view should be the second layout in the service definition on the MCU.
  • When inviting multiple endpoints to a meeting, by default Video Administration sends the invitation request to the MCU for each endpoint in sequence without any delay between the requests. Sometimes this can cause a timing issue with the MCU so that not all the endpoints can connect successfully. To resolve this issue, go to Configuration Tool > General Settings and set the Command Delay value to 100 to 200 milliseconds.
  • For Release 5.4(2.103) only: Cisco Unified MeetingPlace deployments do not support the use of the “Reserve Port on EMP for dynamic cascading” parameter on the Scheduling Settings tab of the Video Admin Configuration Tool.

Rating: 0.0/5 (0 votes cast)

Personal tools