Guest

Cisco Unified Videoconferencing 3500 Series Products

Release Notes for Cisco IPVC 3511 MCU, Cisco IPVC 3511 MCU E, Cisco IPVC 3540 MCU Releases 3.5.24 and 3.5.33

 Feedback

Table Of Contents

Release Notes for Cisco IPVC 3511 MCU, Cisco IPVC 3511 MCU E, Cisco IPVC 3540 MCU
Releases 3.5.24 and 3.5.33

Contents

Documentation Roadmap

New and Changed Information

New Software Features in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

Improved Features in Cisco IPVC 35xx MCU Release 3.5.33

Changed Hardware in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

Changed Software Features in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

Important Notes

New Hardware Is Incompatible with Some Legacy Software

EMP Requirements

Cisco VT Advantage Compatibility

Open Caveats

Resolved Caveats

New Features in Releases 3.5.24 and 3.5.33

Adapting the Output Display for Different Types of Monitors

About Configuring the Cisco IPVC 35xx MCU to Use Cisco MeetingPlace

Muting Participants As They Join a Conference

Configuring Support for ICMP Error Disconnect

Configuring Participant Name Display Duration

About Configuring the Cisco IPVC 35xx MCU to Use SIP

Restricting Who Can Use the Cisco IPVC 35xx MCU Web Page to Create Conferences

Documentation Updates

About Setting the Dynamic Layout Feature

Using the Cisco IPVC 35xx MCU Configuration Wizard

Related Documentation


Release Notes for Cisco IPVC 3511 MCU, Cisco IPVC 3511 MCU E, Cisco IPVC 3540 MCU
Releases 3.5.24 and 3.5.33


March 31, 2005

These release notes describe new and changed features in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33 for the following Cisco products:

Cisco IPVC 3511 Multipoint Control Unit (MCU)

Cisco IPVC 3511 Multipoint Control Unit (MCU) E

Cisco IPVC 3540 Multipoint Control Unit (MCU) module.

Use these release notes in with the Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide for Version 3.2.


Note Throughout this document we use Cisco IPVC 35xx MCU to refer to these products unless otherwise noted.


For regulatory and compliance information about these Cisco IPVC 35xx MCUs, see Regulatory Compliance and Safety Information for Cisco IPVC 3500 Products at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/ipvc/35prcsi/rel_2/index.htm

Contents

These release notes cover the following topics:

Documentation Roadmap

New and Changed Information

Important Notes

Open Caveats

Resolved Caveats

New Features in Releases 3.5.24 and 3.5.33

Documentation Updates

Related Documentation

Documentation Roadmap

Table 1 describes related documentation for Cisco IPVC MCU Releases 3.5.24 and 3.5.33. You can find these and other Cisco IPVC documents at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/ipvc/index.htm

Table 1 Documentation Roadmap 

Document
Part Number
Description

Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide

DOC-7815962=

Describes how to install, configure and use Cisco IPVC 35xx MCU products.


New and Changed Information

New Software Features in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

The following features have been added since Cisco IPVC 35xx MCU Release 3.2.138:

Adapt screen for—Allows you to tailor the output video format for a terminal or a television monitor in the Cisco IPVC 35xx MCU service.

See the "Adapting the Output Display for Different Types of Monitors" section.

Cisco MeetingPlace support—Allows interoperation with Cisco MeetingPlace, so that the Cisco IPVC 35xx MCU can initiate video conferences and include them in the rich-media mix.

See the "About Configuring the Cisco IPVC 35xx MCU to Use Cisco MeetingPlace" section.

Conference participants initially muted—Allows you to set a service parameter that mutes participants as they join a conference.

See the "Muting Participants As They Join a Conference" section.

Disconnect participant for ICMP errors support—Allows you to disable support for Internet Control Message Protocol (ICMP) messages.

See the "Configuring Support for ICMP Error Disconnect" section.

Display participant name—Allows you to specify when participant information is displayed.

See the "Configuring Participant Name Display Duration" section.

Session Initiation Protocol (SIP) support—Allows you to configure Cisco IPVC 35xx MCUs to provide video conference in a SIP environment.

See the "About Configuring the Cisco IPVC 35xx MCU to Use SIP" section.

When using the Web, only operators or administrators can create a conference—Allows you to restrict who can use the Cisco IPVC 35xx MCU web page to create conferences to those given administrator or operator privileges.

See the "Restricting Who Can Use the Cisco IPVC 35xx MCU Web Page to Create Conferences" section.

Improved Features in Cisco IPVC 35xx MCU Release 3.5.33

The following features have been improved since Cisco IPVC MCU Release 3.5.24:

Improved H.239 stability and added support for Polycom and TANDBERG endpoints.

Improved video switch.

Changed Hardware in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

The following hardware change has occurred since Cisco IPVC 35xx MCU, Release 3.2.138.

Cisco IPVC MCU hardware module (B06)—Devices that are shipped with Releases 3.5.24 use new Cisco IPVC 35xx MCU hardware.

See the "New Hardware Is Incompatible with Some Legacy Software" section.

Changed Software Features in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

The following features have changed since Cisco IPVC 35xx MCU Release 3.2.138:

Dynamic layout—Allows you to specify how the Cisco IPVC 35xx MCU displays the images as participants join a conference.

See the "About Setting the Dynamic Layout Feature" section.

"Enable Collaboration" check box—Has been removed from the Data Settings dialog box.

Updated Cisco IPVC MCU Configuration Wizard—Configuration for SIP registration has been added.

See the "Using the Cisco IPVC 35xx MCU Configuration Wizard" section.

Important Notes

This section contains important notes about Cisco IPVC 35xx MCU products the use Release 3.5.24 or Release 3.5.33.

New Hardware Is Incompatible with Some Legacy Software

Cisco IPVC 35xx MCUs that ship from the factory with Release 3.2.224 and later releases use a new Cisco IPVC 35xx MCU hardware module. The version number of the new hardware module is B06.

Determining the Hardware Version Number of a Cisco IPVC 35xx MCU Module

From the Cisco IPVC Administrator web page, use the following procedure to determine the hardware version number of a Cisco IPVC 35xx MCU module:


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU for which you want to check the hardware version number.

Step 2 From the sidebar, click Board.

Step 3 Click the Basics tab.

Step 4 Locate the Hardware Version field.



Caution Cisco IPVC 35xx MCU hardware module version B06 supports Cisco IPVC 35xx MCU Release 3.2.138 and later releases only. The software that is installed on new modules at the factory is designed to detect attempts to install Release 2.x or earlier releases and to halt the installation. Installing Release 2.x on the new hardware can render the Cisco IPVC MCU inoperable.

EMP Requirements

To use some of the new features in Cisco IPVC 35xx MCU Release 3.5.24 or Release 3.5.33, you must use a Cisco IPVC Enhanced Media Processor (EMP) with Release 2.0.11. You can purchase Cisco IPVC EMP, Release 2.0.11 software online through Cisco Connection Online (CCO).

Cisco VT Advantage Compatibility

When end users use Cisco VT Advantage endpoints, configure the Cisco IPVC MCU to use H.263 video format only.

Open Caveats

This section lists unexpected behavior or defects in Cisco IPVC MCU Releases 3.5.24 and 3.5.33. Severity 1 caveats are the most serious; severity 2 caveats are less serious; and severity 3 caveats are not serious. Table 2 provides information about caveats in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33 that were not resolved at the time of release.

You can search for information about these and other caveats found after this release on the Cisco bug tracking tool, called Bug Toolkit. You must have a Cisco Connection Online (Cisco.com) account to access caveats. To access information about these caveats, enter the URL listed for the caveat in your browser. To access information about other caveats in the Bug Toolkit, go to the following URL:

http://www.cisco.com/support/bugtools

Table 2 Open Caveats for Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

Identifier
Headline

CSCed26771

Conference duration counter is incorrect.

http://wwwin-metrics.cisco.com/cgi-bin/ddtsdisp.cgi?id=CSCed26771

CSCed37746

Screen resolution 800x600, conf page logout button not visible.

http://wwwin-metrics.cisco.com/cgi-bin/ddtsdisp.cgi?id=CSCed37746


Resolved Caveats

Table 3 lists caveats that are resolved in Cisco IPVC MCU Releases 3.5.24 and 3.5.33.

You can search for information about these and other caveats found after this release on the Cisco bug tracking tool, called Bug Toolkit. You must have a Cisco Connection Online (Cisco.com) account to access caveats. To access information about these caveats, enter the URL listed for the caveat in your browser. To access information about other caveats in the Bug Toolkit, go to the following URL:

http://www.cisco.com/support/bugtools

Table 3 Resolved Caveats for Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33

Identifier
Headline

CSCed37750

Conf. duration counter becomes inconsistent with conf. connect time.

http://wwwin-metrics.cisco.com/cgi-bin/ddtsdisp.cgi?id=CSCed37750

CSCuk55763

G.729 audio transcoding in SCCP resolved (Cisco IPVC 35xx MCU Release 3.5.33 only).

N/A

Web browser cookie problem that could cause the web agent to crash (Cisco IPVC 35xx MCU Release 3.5.33 only).

N/A

Several XML API-related problems linked to long lists of participants in Conference Control (Cisco IPVC 35xx MCU Release 3.5.33 only).


New Features in Releases 3.5.24 and 3.5.33

The following sections describe how to configure your Cisco IPVC 35xx MCU to use the new features in Releases 3.5.24 and 3.5.33:

Adapting the Output Display for Different Types of Monitors

About Configuring the Cisco IPVC 35xx MCU to Use Cisco MeetingPlace

Muting Participants As They Join a Conference

Configuring Support for ICMP Error Disconnect

Configuring Participant Name Display Duration

About Configuring the Cisco IPVC 35xx MCU to Use SIP

Restricting Who Can Use the Cisco IPVC 35xx MCU Web Page to Create Conferences

Adapting the Output Display for Different Types of Monitors

Some monitors crop the image that the Cisco IPVC 35xx MCU distributes to conference participants. This feature allows you to configure the Cisco IPVC 35xx MCU to adapt the size of the output image to suit different types of monitors.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to configure.

Step 2 Choose MCU > Services.

Step 3 Open the profile of the service that you want to configure.

The Edit Service dialog box appears.

Step 4 Click the Edit Views icon.

The Edit Views dialog box appears.

Step 5 In the "Adapt screen for" field, click one of the following:

Terminal display—Adapts the image size to fit computer terminal displays.

TV monitor—Adapts the image size to fit TV monitors.


Note TV monitor is the default value.


Step 6 Click OK.

The Edit Service dialog box appears.

Step 7 Click OK.

Step 8 To save changes to memory, click Upload.


About Configuring the Cisco IPVC 35xx MCU to Use Cisco MeetingPlace

You can use a Cisco IPVC 35xx MCU to provide video content for Cisco MeetingPlace conferences in H.323 environments. To provide video content in Cisco MeetingPlace conferences, you must configure your Cisco MeetingPlace components and your Cisco IPVC 35xx MCU.

See the Administrator's Guide for Cisco MeetingPlace Video Integration Release 5.3 for information about configuring your Cisco MeetingPlace components.

To configure your Cisco IPVC MCU to provide video content for Cisco MeetingPlace conferences, you must do the following in this order:


Step 1 Verify that all video endpoints can connect to a conference on the Cisco IPVC MCU, and that the Cisco IPVC MCU can call out to all video endpoints.

Step 2 Create a Cisco IPVC MCU user for Cisco MeetingPlace.

Step 3 Set Cisco IPVC MCU management parameters that are required to support Cisco MeetingPlace:

Reserve ports for Cisco MeetingPlace conferences.

Specify that only authorized users can use the Cisco IPVC MCU to create video conferences. In this case, only Cisco MeetingPlace will be authorized to create video conferences.

Enable the Cisco IPVC MCU to generate an announcement for the Cisco MeetingPlace Waiting Room.

Step 4 Create a Cisco IPVC MCU service for Cisco MeetingPlace.



Note You cannot stack embedded Cisco IPVC media processors to use with Cisco MeetingPlace.


Verifying that Video Endpoints Can Connect to the Cisco IPVC MCU

Endpoints must be able to join video conferences on the Cisco IPVC MCU before Cisco MeetingPlace Video Integration can run.

If you have questions about routing calls through the gatekeeper and you use a Cisco IOS H.323 Gatekeeper, see the Cisco IOS H.323 Configuration Guide.


Step 1 Follow the instructions in the documentation for your Cisco IPVC MCU to have each video endpoint dial in to a video conference.

Step 2 Follow the instructions in the documentation for your Cisco IPVC MCU to have the Cisco IPVC MCU call each video endpoint.


Creating a Cisco IPVC MCU User for Cisco MeetingPlace

Create a username and password that Cisco MeetingPlace Video Integration will use to log in to the Cisco IPVC 35xx MCU.

After you create a Cisco IPVC 35xx MCU user name for Cisco MeetingPlace, you must make the user name available to the Cisco MeetingPlace video server through the Cisco MeetingPlace video server installation utility.

For information about installing, upgrading, and configuring the Cisco MeetingPlace video server, see the Administrator's Guide for Cisco MeetingPlace Video Integration Release 5.3.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC MCU that you want Cisco MeetingPlace to use.

Step 2 From the sidebar, click Board.

Step 3 Click the Users tab.

Step 4 Click the Add button.

The Add User dialog box appears.

Step 5 In the "User name" field, enter the name that you want the Cisco MeetingPlace Web Conferencing server to use to log in to the Cisco IPVC MCU.

Step 6 In the "Access level" field, click Administrator or Operator.

Step 7 In the Password field, enter the password that you want this user to have.

Step 8 In the "Confirm Password" field, enter the password that you want Cisco MeetingPlace to use.

Step 9 To disable the ability of this user to telnet into the Cisco IPVC MCU, uncheck Enable for Telnet / FTP.

Step 10 To save this user profile, click Upload.


Setting Cisco IPVC MCU Parameters Required to Support Cisco MeetingPlace

To use your Cisco IPVC MCU with Cisco MeetingPlace, you must configure certain Cisco IPVC MCU parameters to provide video for Cisco MeetingPlace conferences.

For more information about configuring the Cisco IPVC MCU for operation, see Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC MCU that you want the Cisco MeetingPlace server to use.

Step 2 Choose MCU > Settings > Basics.

Step 3 In the MCU field, click MCU.

Step 4 In the "Number of SCCP ports" field, select a value for the number of ports that you want Cisco CallManager to use that leaves ports available for Cisco MeetingPlace.

For example, for a 60-port Cisco IPVC MCU select 0, 15, 30, or 45.

Step 5 Click the Conference Mgmt button.

Step 6 Set the following parameters in the Conference Mgmt page:

a. In the "External conference authorization policy" field, click Authorize.

b. In the "Allow conference creation using" field, click Scheduler, Web, Control API and dial-in.

c. In the "Allow conference joining using" field, click Invite and dial-in.

d. In the "Dial-in conference terminates when" field, click Last participant leaves.

Step 7 Click the Advance button.

Step 8 We recommend that you check Disconnect participants on communications (ICMP) failure and click Audio failure in the "Disconnect on" field.

Step 9 To save these settings to memory, click Upload.


Setting the Audio Indication Interval (Optional)

If video participants join a conference that has not yet started, they must wait in the waiting room. To play an announcement while participants wait, set the following parameter:


Step 1 Click MCU, then click Settings.

Step 2 Click the Advanced button.

Step 3 Click the Commands button.

The Advanced Command dialog box appears.

Step 4 In the Advanced Command dialog box, do the following:

a. In the Available commands window, click Audio indication interval.

Your selection appears in the Command field.

b. In the Parameter field, enter the value in milliseconds that you want Cisco MeetingPlace to announce to video participants that they are in the waiting room and that the conference has not formally started.


Tip We recommend entering 1500 to establish an interval of 15 seconds.


c. Click Send, then click Close.


Creating a Service for Cisco MeetingPlace

You must create a Cisco IPVC MCU service for Cisco MeetingPlace. Before you create a service in the Cisco IPVC MCU make sure that the media processor (MP) that the Cisco IPVC MCU uses supports Cisco MeetingPlace.

Table 4 provides information about which Cisco IPVC media processors support Cisco MeetingPlace.

Table 4 Media Processors That Support Video in Cisco MeetingPlace, Release 5.3

Cisco IPVC Media Processor
Software Supporting Cisco MeetingPlace

Local Cisco IPVC MCU media processor

Release 3.5.24 or later releases

Cisco IPVC EMP

Release 2.0.11 or later releases

Cisco IPVC Rate Matching module

Does not support Cisco MeetingPlace

Data Conferencing Card

Does not support Cisco MeetingPlace.


You can use one of the preconfigured Cisco MeetingPlace service templates or manually create a Cisco MeetingPlace service.

Using Preconfigured Service Templates

Cisco IPVC MCU Releases 3.5.24 and 3.5.33 include three preconfigured services that are designed for Cisco MeetingPlace.


Note The Cisco MeetingPlace service prefixes appear automatically on the IPVC Administrator Services page for new Cisco IPVC 35xx MCUs. However, these services do not appear when you upgrade your Cisco IPVC 35xx MCU to Release 3.5.24 or Release 3.5.33. To display these services, you must use the restore factory defaults option. In doing so, you will lose your current configuration.


To install the Cisco MeetingPlace service templates on an existing Cisco IPVC MCU installation and erase existing services:


Step 1 Run the Cisco IPVC MCU installer.

Step 2 At the first install screen, click Customize.

Step 3 Check the MCU Config File check box.

Step 4 Continue with the installation.

Step 5 After installation, log in to the Cisco IPVC MCU as administrator.

Step 6 From the sidebar, click MCU.

Step 7 Click the Services tab.

Step 8 In the Services tab, choose the appropriate template for your needs. Voice Activated allows participants to View Active Speaker, while Continuous Presence allows participants to View Multiple People. These settings are available to participants in the web-conferencing meeting room:

Service Prefix
Supported Views
Supported Endpoints
Processors Required
Format
Allow Dynamic Scheme

887

Voice Activated and Continuous Presence

H.323

MP

H.261

Unchecked

888

Voice Activated

SCCP, H.323

MP

H.263

Checked

889

Voice Activated and Continuous Presence

SCCP, H.323

MP and EMP

H.263

Checked for both views


Step 9 Review the remaining topics in the "About Configuring the Cisco IPVC 35xx MCU to Use Cisco MeetingPlace" section and make additional configurations as required for your needs.


Creating a Service Manually

To create a Cisco IPVC MCU service for Cisco MeetingPlace, do the following tasks:

Setting the Core Service Parameters

Setting Audio Indications

Making Sure that a Conference Password Is Not Required

Setting Conference View Parameters

Setting Video Schemes Parameters

Setting the Core Service Parameters


Step 1 From the sidebar, click MCU.

Step 2 Click the Services tab.

Step 3 Click the Add button.

The Select Service dialog box appears.

Step 4 To create a new service, click OK.

The Add Service dialog box appears.

Step 5 In the "Service prefix" field, enter the value that you want to use for the Cisco MeetingPlace service.

Step 6 Uncheck the SCCP Service check box. Users of SCCP endpoints can still attend Cisco MeetingPlace conferences.

Step 7 In the "Service description," enter the description for this service that you want to appear on the Create Conference page.

Step 8 In the "Media types" section, check Video.


Note Cisco MeetingPlace provides data collaboration in conferences. Disable data collaboration in the Cisco IPVC MCU if it is currently enabled.


Step 9 Specify the number of ports that you want the Cisco IPVC MCU to reserve for each conference as follows:

a. In the "Reserved number of parties" field, enter 2.


Note One of these ports is reserved for the Cisco MeetingPlace server.



Tip You can ascertain the maximum number of ports this service can support by entering 200 in the "Maximum number of parties" field and choosing OK at the bottom of the page. The error message that appears indicates the maximum number of ports the current configuration allows based on the video bandwidth value specified in the Conference Views section.


b. In the "Maximum number of parties" field, enter the total number of Cisco IPVC MCU ports that are available for conferences.


Setting Audio Indications

We recommend that you enable all audio-indication parameters.


Step 1 Click the Indications button.

The Indications Settings dialog box appears.

Step 2 Make sure that all parameters are checked.

Step 3 Click OK.


Making Sure that a Conference Password Is Not Required


Step 1 Click the Management button.

The Management Settings dialog box appears.

Step 2 Make sure that password-related parameters are unchecked.

Step 3 Click OK.

The Add Services dialog box appears.


Setting Conference View Parameters

When you set view parameters, use the Cisco MeetingPlace service template as a model. The templates are described in the "Using Preconfigured Service Templates" section. A Voice Activated view allows participants to View Active Speaker, while a Continuous Presence view allows participants to View Multiple People.


Note One Voice Activated, 1-participant layout is required. A Continuous Presence view is optional, if your hardware supports it.


General Instructions for Setting View Parameters


Step 1 Click the edit view icon.

The Edit View dialog box appears.

Step 2 In the "Use Processor" field, click the type of media processor that you want this service to use.


Note The MP and RM option does not support Cisco MeetingPlace.


Click MP to specify that the service only uses the local media processor to process video conference calls.

Click EMP to specify that the service uses the Cisco IPVC Enhanced Media Processor (EMP) register with the Cisco IPVC MCU to process video conference calls.

Click Auto to allow the Cisco IPVC MCU to choose the media processor the Cisco IPVC MCU will use to process a specific video conference.


Note See Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2 for information about registering a media processor with the Cisco IPVC MCU.


Step 3 In the "Video Picture Size" field, click the video format that you anticipate most endpoints will use.

Step 4 To enable the Cisco IPVC MCU to switch the video to the speaker who is speaking the loudest, check Enable voice activate.

Step 5 In the "Voice activate method" field, we recommend that you click All see one to have all participants see the current speaker.

Step 6 To disable automatic switching of nonspeaking participants, uncheck Enable auto-switch.

Step 7 To save these conference-view parameters and to close the Edit View dialog box, click OK.


Special Instructions for Accommodating SCCP Endpoints

Because SCCP endpoints require the H.263 format, special view settings are required. To set up views, use the table in the "Using Preconfigured Service Templates" section as a model for setting parameters, or use the appropriate procedure from this section.

If your users will attend via SCCP endpoints and your Cisco IPVC MCU has only an MP card, only the Voice Activated view can be used. In this case, all participants will be able to use only the View Active Speaker option available in the Cisco MeetingPlace meeting room. They will not be able to view multiple people simultaneously.

Creating a Single Voice-Activated View


Step 1 The default view should have the correct parameter settings. Verify that the settings are as follows:

Parameter
Value

Initial Layout

1-participant layout

Max Layout

1-participant layout

Use Processor

MP

Format (in the Video Schemes Settings section)

H.263

Other parameters

As desired


Step 2 Click OK.


If your users will attend via SCCP endpoints and you have both an MP card and an EMP card, in order for participants to be able to use both the View Active Speaker and the View Multiple People options that are available in the Cisco MeetingPlace web-conferencing meeting room, both views are required. The View Active Speaker option corresponds to the Voice Activated view, and View Multiple People corresponds to the Continuous Presence view.

Creating Two Separate Views


Step 1 In the service, click the Views button to create the first view.

Step 2 Set the following parameters for this view:

Parameter
Value

Initial Layout

Desired multiple participant layout (for example, 4 participant)

Max Layout

Desired multiple participant layout (for example, 4 participant)

Use Processor

EMP

Format (in the Video Schemes Settings section)

H.263

Other parameters

As desired


Step 3 Click OK.

Step 4 Check the Display all conference views check box.

Step 5 Click Add View.

Step 6 Set the following parameters for the second view:

Parameter
Value

Initial Layout

1-participant layout

Max Layout

1-participant layout

Use Processor

MP

Format (in the Video Schemes Settings section)

H.263

Other parameters

As desired


Step 7 Click OK.


Setting Video Schemes Parameters


Step 1 Select the "Video Settings Schemes" profile that you want to edit and click the Edit button.

The Edit Video Scheme dialog box appears.

Step 2 In the "Max bit rate" field, click the maximum video bandwidth that you want this service to support. This number must be less than or equal to the bandwidth settings in Cisco MeetingPlace (and in Cisco CallManager, if your network uses Cisco CallManager.)


Note Endpoints that are not capable of supporting this bandwidth receive only the conference audio unless dynamic scheme is allowed.


Step 3 Check Allow dynamic scheme to enable the Cisco IPVC MCU to switch the conference video bandwidth to a lower value when a less capable endpoint joins the conference.

In the "Min bit rate" field, click the lowest bandwidth that you want this parameter to support.

Step 4 To save these Video Scheme changes and to close this dialog box, click OK.

Step 5 To save these conference-view parameters and to close the Edit View dialog box, click OK.


Saving Your Service

To save your service, click OK at the bottom of the Service page.

Muting Participants As They Join a Conference

This feature allows you to configure a service to automatically mute participants as they join a conference. All participants are muted when they join. The conference administrator must change the mute status of participants in the Cisco IPVC conference page for the conference.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to configure.

Step 2 From the sidebar, click MCU.

Step 3 Click the Services tab.

Step 4 Do one of the following:

To create a new service, click the Add button.

To modify that service, select a service and click the Edit button.

Step 5 Click the Voice button.

The Audio Settings dialog box appears.

Step 6 Check Conference participants initially muted to enable this feature.

Step 7 Click OK.

The Edit Service dialog box appears.

Step 8 Click OK.


Configuring Support for ICMP Error Disconnect

This feature allows the Cisco IPVC 35xx MCU to disconnects a participant for Internet Control Message Protocol (ICMP) errors.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want the MeetingPlace server to use.

Step 2 Choose MCU > Advanced.

Step 3 Check Disconnect participants on communications (ICMP) failure.

Step 4 In the "Disconnect on" field, click the channel that you want the Cisco IPVC MCU to monitor for ICMP errors:

To have the Cisco IPVC 35xx MCU monitor the audio-only channel, click Audio failure.

To have the Cisco IPVC 35xx MCU monitor the audio and video channels, click Audio or video failure.

Step 5 To save these changes to configuration memory, click Upload.


Configuring Participant Name Display Duration

This feature allows you to configure how the Cisco IPVC 35xx MCU displays an identifier in the frame of a participant.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to configure.

Step 2 Choose MCU > Settings > Advanced.

The Advanced page appears.

Step 3 In the "Participant name display duration" field, enter the length of time in seconds that you want to Cisco IPVC 35xx MCU to display the identifier in the frame.


Note This is a universal setting that applies to all services that are configured to display this identifier temporarily.


Step 4 To save this setting, click Upload.

Step 5 Click the Services tab and open the service profile for which you want to enable this parameter.

The Edit Service dialog box appears.

Step 6 Check the Edit Views icon.

The Edit Views dialog box appears.

Step 7 In the "Display participant name" field, click one of the following option for displaying the identifier in the frame:

Always—Constantly displays the identifier in the frame.

Never—Does not display the identifier in the frame.

On Change—Displays the identifier of the participant for the interval set in the "Participant name display duration" field when the video switches.

Step 8 Click OK.

The Edit Service dialog box appears.

Step 9 Click OK.

Step 10 To save changes to memory, click Upload.


About Configuring the Cisco IPVC 35xx MCU to Use SIP

Cisco IPVC 35xx MCUs using Release 3.5.24 or Release 3.5.33 support Session Initiation Protocol (SIP). You can configure the Cisco IPVC MCU to register with SIP proxy servers and SIP registrar servers. The Cisco IPVC 35xx MCU then allows SIP-enabled endpoints to participate in video conferences, including those that have H.323 endpoints. The Cisco IPVC 35xx MCU can register conferences with the SIP registrar server so that SIP endpoints can dial directly into established video conferences.

To configure the Cisco IPVC MCU to support SIP, do the following tasks in this order:

Specifying the Cisco IPVC 35xx MCU to Register with a Domain Name Server

Specifying the SIP Proxy Server that You Want this Cisco IPVC 35xx MCU to Use

Enabling and Configuring SIP

Specifying the Cisco IPVC 35xx MCU to Register with a Domain Name Server


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to use SIP.

Step 2 From the sidebar, click Board.

Step 3 Click the Addressing tab.

The Address page appears.

Step 4 In the "DNS suffix" field, enter the alias that you want to use for this Cisco IPVC MCU.

Step 5 In the "Preferred DNS server" field, enter the IP address of the DNS server with which you want this Cisco IPVC 35xx MCU to register.

Step 6 In the "Alternate DNS server" field, enter the IP address of the alternate DNS server with which you want this Cisco IPVC 35xx MCU to register when the preferred server is not available.

Step 7 To save your changes, click Upload.


Specifying the SIP Proxy Server that You Want this Cisco IPVC 35xx MCU to Use


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to use SIP.

Step 2 From the sidebar, click MCU.

Step 3 On the toolbar, click the Setup Wizard button.

The Cisco IPVC 35xx MCU Configuration Wizard starts.

Step 4 Click Next in until the SIP Settings page appears.

Step 5 In the "Proxy IP" field, enter the IP address of the SIP Proxy server to which you want this Cisco IPVC 35xx MCU to register.

Step 6 In the "Proxy Port" field, enter the port number that the SIP proxy server uses for communication.

Step 7 In the "Default Domain" field, enter the domain name that you want the Cisco IPVC MCU to append to the outbound dial string when the domain name is not provided.

Step 8 Check Using Microsoft RTC when the SIP proxy server that you want to use is a Microsoft RTC server.

Step 9 Click Next.

The Date and Time Settings page appears.

Step 10 To save your changes, click Finish.


Enabling and Configuring SIP


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to use SIP.

Step 2 Choose MCU > Protocols.

The SIP Protocol Configurations page appears. See Table 5 for information about the elements that appear in the SIP Protocol Configurations page.

Step 3 Select the SIP entry that you want to configure and click Edit.

The Edit SIP Protocol Configuration dialog box appears. See Table 6 for information about the elements that appear in the Edit SIP Protocol Configuration dialog box.

Step 4 To activate SIP in the Cisco IPVC 35xx MCU, check Enable.

Step 5 In the Description field, enter the description that you want to display in the SIP Protocol Configurations window for this SIP entry.

Step 6 To have the Cisco IPVC 35xx MCU register with a SIP registrar server, check Use registrar.

a. In the Registration name field, enter the name with which you want the Cisco IPVC MCU to register with the SIP registrar server.

b. In the "Registrar communication type" field, click the communication protocol the SIP server uses.

Click UDP for SIP servers that use UDP for communication.

Click TCP for SIP servers that use TCP for communication.

Step 7 In the "Local signaling port" field, enter the port number the Cisco IPVC 35xx MCU uses to communicate with the SIP proxy server.

Step 8 In the "Out transport connection type" field, click the transport type that you want the Cisco IPVC 35xx MCU to use for call signalling for outbound SIP calls.

Step 9 In the "Out contact header type" field, click the type of information that you want the Cisco IPVC 35xx MCU to place in the contact header for outbound calls.

Click Default SIP domain to have the Cisco IPVC 35xx MCU enter the domain name of the Cisco IPVC 35xx MCU in the contact header field.

Click Local signaling IP to have the Cisco IPVC 35xx MCU enter the IP address of the Cisco IPVC 35xx MCU in the contact header field.

Step 10 Check Enable Video Fast Update to allow the Cisco IPVC 35xx MCU to send and receive Video Fast Update (VFU) requests.

Step 11 To save your changes to configuration memory, click Upload.


Viewing the SIP Protocol Configurations Page

The SIP Protocol Configurations page provides information about connections between SIP servers and this Cisco IPVC 35xx MCU. Table 5 provides information about the elements that appear in the SIP Protocol Configurations page.

Table 5 SIP Protocol Configurations Page 

Field
Description

Enable

Check to activate SIP protocol support in the Cisco IPVC 35xx MCU.

Description

The description of the profile provided in the Description field in the profile.

Proxy Address

Lists the IP address and communication port of the SIP proxy server the Cisco IPVC 35xx MCU uses.

Status

Indicates whether the connection the Cisco IPVC  35xx MCU has with this SIP proxy server is enabled or disabled.

Servicing Registrar

Indicates the IP address, domain name, or SIP URL of the SIP registrar server to which the Cisco IPVC 35xx MCU is registered.

Total

Indicates the number of SIP proxy servers the Cisco IPVC 35xx MCU is enabled to use.

Edit

Opens the Edit SIP Protocol Configuration dialog box which allows you to enable a SIP connection and create a SIP profile.


Viewing the Edit SIP Protocol Configuration Dialog Box

The Edit SIP Protocol Configuration dialog box allows you to configure the Cisco IPVC MCU to use SIP protocol. Table 6 describes the elements that appear in the Edit SIP Protocol Configuration dialog box.

Table 6 Edit SIP Protocol Configuration Dialog Box 

Field
Description

Enable

Check to allow the Cisco IPVC 35xx MCU to communicate with a SIP proxy server.

Description

Enter a description for this SIP profile. This description appears on the SIP Protocol Configuration page.

Registration Settings

Proxy Address

Enter the IP address of the SIP proxy server that you want the Cisco IPVC 35xx MCU to use.

Proxy port

Enter the value of the listening port that the SIP proxy server uses.

User register

Check this box to enable the Cisco IPVC 35xx MCU to register with the SIP registrar server:

Registration name—Enter the name with which you want the Cisco IPVC 35xx MCU to register with the SIP registrar server.

Registration communication type—Click the transport type that you want the Cisco IPVC 35xx MCU to use to communicate with the SIP server.

UDP—Click this transport type for SIP servers that use UDP.

TCP—Click this transport type for SIP servers that use TCP.

   
   
   

General

Default Domain

You can use this field to change the domain name the Cisco IPVC 35xx MCU appends to outbound dial strings when a domain name is not otherwise provided.

Local signaling port

Enter the port number that the Cisco IPVC 35xx MCU uses to communicate with the SIP proxy server.

Out transport connection type

Click the transport type that you want the Cisco IPVC 35xx MCU to use for call signaling for outbound SIP calls.

Out contact header type

Click the type of information that you want the Cisco IPVC 35xx MCU to place in the contact header for outbound calls.

Default SIP domain—Click this to have the Cisco IPVC 35xx MCU enter the domain name of the Cisco IPVC 35xx MCU in the contact header field.

Local signaling IP—Click this to have the Cisco IPVC 35xx MCU enter the IP address of the Cisco IPVC 35xx MCU in the contact header field.

Enable Video Fast Update

Check to allow the Cisco IPVC 35xx MCU to send and receive Video Fast Update (VFU) requests.

Upload

Click this button to save your changes to configuration memory.

Cancel

Click this button to close the Edit SIP Protocol Configuration dialog box without saving your changes.


Restricting Who Can Use the Cisco IPVC 35xx MCU Web Page to Create Conferences

This feature allows you restrict who can use the Cisco IPVC 35xx MCU web page to create conferences to those with administrator and operator privilege.


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to configure.

Step 2 Choose MCU > Settings > Conference Mgmt.

The Conference Mgmt page appears.

Step 3 Check When using the Web, only operators or administrators can create a conference.

Step 4 Click Upload.


The option to create conferences does not appear in the Cisco IPVC 35xx MCU web page when users without operator or administrator privilege log on to the page.

Documentation Updates

This section contains updates to tasks described in Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2.

The following sections describes the updated tasks for Cisco IPVC 35xx MCU, Releases 3.5.24 and 3.5.33.

About Setting the Dynamic Layout Feature

Using the Cisco IPVC 35xx MCU Configuration Wizard

About Setting the Dynamic Layout Feature

The dynamic layout feature has expanded in Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33. The information in this section supersedes that in the "Create a Basic View" and "Viewing the Edit View Dialog Box" in Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2.

The dynamic layout feature allows you to use multiple layouts to display participants in a video conference. The type of media processor that the service uses determines the number of layouts that are available and the maximum number of frames that can appear. Table 7 provides layout information for Cisco IPVC media processors.

Table 7 Cisco IPVC Media Processors Layout Information 

Cisco Media Processor
Number of Layouts
Maximum number of Frames

Embedded media processor

2

4

Rate Matching module

13

16

Enhanced Media Processor

27

16


You choose whether to use multiple layouts when you configure a service. You specify an initial layout and a maximum layout. In the initial layout, you specify the display capacity and pattern of the first participants to join the conference. In the maximum layout, you specify the total number of participants that you want to display and the pattern in which you want to display them.

Services that use a Cisco IPVC EMP, Release 2.0.11 or later releases can use additional layouts representing capacities between the initial and maximum layouts. These layout choices apply to all relevant services.

To set dynamic layouts, see the following:

Activating Dynamic Layouts

Setting Universal Layouts

Activating Dynamic Layouts


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to configure.

Step 2 Choose MCU > Services.

Step 3 To open a service profile, do one of the following:

Click the Add button to create a new service profile.

Select a service prefix and click the Edit button to modify an existing service profile.

The Edit Service dialog box appears.

Step 4 Check the Edit Views icon.

The Edit Views dialog box appears.

Step 5 To set the maximum layout parameter:

a. Click the Max. Layout Change button.

The Set Max Layout dialog box appears.

b. Click the layout for the maximum number of participants that you want this service to display simultaneously.

c. Click OK.

Step 6 To set the initial layout parameter:

a. Click the Initial Layout Change button.

The Set Initial Layout dialog box appears.

b. Click the layout for the number of participants that you want this service to display when the conference is initiated.

c. Click OK.

Step 7 Check Use dynamic layout.

Step 8 Click OK.

The Edit Services dialog box appears.

Step 9 Click OK.


Setting Universal Layouts


Step 1 Log in to the Cisco IPVC Administrator of the Cisco IPVC 35xx MCU that you want to configure.

Step 2 Choose MCU > Settings > Display layout.

The Dynamic Layouts page appears.

Step 3 For each quantity-of-participant listing, click the layout that you want the Cisco IPVC MCU to use when that number of participants joins the conference and the service is configured to display more participants.


Note When you do not specify a pattern for a quantity-of-participant listing, the Cisco IPVC 35xx MCU uses the next pattern that you specify.


Step 4 Click Upload.


Using the Cisco IPVC 35xx MCU Configuration Wizard

Cisco IPVC 35xx MCU Releases 3.5.24 and 3.5.33 now allow you to input registration information for SIP in the Setup Wizard.

The following information supersedes the information in the "Using the IP/VC MCU Configuration Wizard" in Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2.


Step 1 If the wizard starts automatically after you log in to the Cisco IPVC Administrator go to Step 2, otherwise click Setup Wizard on the toolbar.

The Board Settings dialog box appears.

Step 2 To change the IP address information with which the Cisco IPVC 35xx MCU is currently configured:

a. In the IP address field, enter the IP address that you want to the Cisco IPVC MCU to use.

b. In the Subnet mask field, enter the subnet mask that you want to assign to the Cisco IPVC 35xx MCU.

c. In the router IP address field, enter the IP address of the router that you want the Cisco IPVC 35xx MCU to use.

d. Click Next.

The H.323 Settings dialog box appears.

Step 3 To specify the H.323 gatekeeper that you want the Cisco IPVC 35xx MCU to use:

a. In the Gatekeeper IP field, enter the IP address of the gatekeeper that you want the Cisco IPVC 35xx MCU to use.

b. In the Gatekeeper Port field, enter the port number that the Cisco IPVC 35xx MCU can use to communicate with the gatekeeper.

c. Click Next.

The SIP Settings page appears.

Step 4 To specify the SIP proxy server and domain information that you want the Cisco IPVC MCU to use:

a. In the Proxy IP field, enter the IP address of the SIP proxy server that you want the Cisco IPVC 35xx MCU to use.

b. In the Proxy Port field, enter the port number that the SIP proxy server uses for communication.

c. In the Default Domain field, enter the domain name that you want the Cisco IPVC MCU to append to the dial string of outbound calls when the domain suffix is not provided.

d. Check Using Microsoft RTC to have the Cisco IPVC 35xx MCU register with the Microsoft RTC server in your environment.

e. Click Next.

The Date and Time Settings page appears.

Step 5 To synchronize the Cisco IPVC 35xx MCU clock with the clock on the current computer, click Update to local time.

Step 6 To save the changes, click Finish.


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:

http://www.cisco.com/univercd/cc/td/doc/product/conf/mtgplace/roadmap.htm