|
|
This chapter describes how to configure the Cisco IP/VC 3510 MCU using the Cisco IP/VC Configuration Utility software. The topics include:
Before you configure the MCU, you must consider the mode you want the Cisco IP/VC 3510 MCU to operate in and how videoconference calls are dialed in your environment. This section discusses the MCU modes of operation, MCU services, and dialing plans.
The Cisco IP/VC 3510 MCU is a full-service MCU that contains a multipoint controller (MC) and a multipoint processor (MP). The MC provides the control functions for videoconference calls. The MP processes the videoconference streams.
You can configure the Cisco IP/VC 3510 MCU in either of two operating modes: standalone or stacking. In standalone mode, the MC and MP in the unit are configured together. In stack mode, the MC and the MP are configured separately. In stack mode, up to four MPs are linked to an MC to provide processing. Stacking creates a distributed MCU, which increases the amount of processing resources while eliminating the need for duplicate services.
The MCU provides services that allow H.323 users to place multipoint videoconference calls. Services define the call parameters. The MCU administrator creates MCU services and assigns each a unique service prefix. The service prefix is associated with the MCU when it registers with the gatekeeper and is used by the end user to initiate a videoconference call.
The basic parameters in a Cisco IP/VC 3510 MCU service include the video bit rate, the frame rate, the picture format, video format, and the number of call participants. The MCU uses these parameters to create a channel for the call. The MCU also negotiates with the participating endpoints to establish the bandwidth parameters that all participants support and which will be used to process the streams for distribution. The negotiation ensures that all participants receive the same video quality. If an endpoint joining the videoconference does not have the capacity to adequately view video at the current negotiated bandwidth, the processing bandwidth can automatically be adjusted downward.
However, the MCU uses the values specified in the service to allocate resources to create the call channel. If sufficient resources are available, the call is initiated. To ensure optimum use of MCU resources, we recommend that the administrator create MCU services that support the least capable terminal in environment and that specify the smallest number of participants that are likely to participate in calls. Additional participants can be invited to the conference or can join it later.
The MCU administrator can also configure the service to support continuous presence and data sharing. These parameters affect how users use the videoconference and are discussed in the following sections.
The Cisco IP/VC 3510 MCU uses the H.263 standard to process continuous presence calls. The MCU requires that the incoming video streams it receives from videoconference participants be sent in Quarter Common Immediate Format (QCIF). The MCU multiplexes the streams and distributes them as a single stream to all of the videoconference participants. Each stream within the distributed stream appears in a quadrant on the receiving terminal. The MCU always displays four sections whether or not there are four call participants.
Three of the continuous presence quadrants are populated by the conference initiator and the first two participants to join or to be invited to the videoconference. These participants are displayed for the duration of the conference or until they drop out and are replaced by the next participant to join or be invited to the conference. The fourth quadrant is populated through voice activation by any of the remaining participants who is awarded the floor.
The Cisco IP/VC 3510 MCU supports T.120 for data sharing. T.120 support is a service option the MCU administrator can enable when creating or modifying an MCU service. The MCU provides native support for Microsoft NetMeeting.
To implement data sharing in a videoconference, the MCU web page for the conference must be opened in Microsoft Internet Explorer. The web page identifies videoconference participants who have data-sharing capability and allows the web page user to enable the T.120 session for the participant.
Before you start configuring your MCU or other videoconferencing components, we recommend that you give some thought to the kinds of calls that will be made in your environment and create a dialing plan. A dialing plan can anticipate your dialing needs and prevent potential call failures due to dialing conflicts. This section discusses key points and issues regarding videoconference dialing-plan implementation. The topics discussed include the dial-string aggregate, service prefixes, zone prefixes, and E.164 addresses.
The string a user dials to initiate a videoconference call is composed of several number clusters that provide information to various videoconference components regarding the call. This aggregate of number clusters can include a service prefix, zone prefix, conference ID, recipient phone number, dial suffix, and invitation code. Although there is a general format regarding the order of the dial string, clusters may vary in length, clusters that are not required are excluded, and component handling of the clusters can vary by manufacturer. Also, clusters that use the same set of numbers can confuse the components. For example, if an MCU service prefix is 70, E.164 addresses such as 703, 7010, or 7094585 can cause the gatekeeper to misinterpret the call request when a service prefix is not intended.
Service prefixes must be registered with the gatekeeper that the service provider (MCU or gateway) registers with. When a call request is placed, the gatekeeper checks its list of services and forwards the call to the appropriate service provider. If the service is not registered, the gatekeeper rejects the call.
We recommend that you create service prefixes that are consistent in length, cannot be confused with other number clusters, and are meaningful to users.
A gatekeeper and the H.323 endpoints that register with it compose a zone. The gatekeeper handles all access requests for calls placed by the endpoints within the zone and for all calls coming into the zone. As a means of controlling access to terminals outside the zone, zone prefixes can be assigned. A zone prefix is a zone ID that serves as a videoconferencing area code. Users outside the zone must dial the zone prefix to reach a recipient inside the zone.
We recommend that you create zone prefixes that are consistent in length, cannot be confused with other number-clusters, and are meaningful to users.
In traditional telephone networks including H.320 networks, each phone line is assigned a specific telephone number by the telephone company. The device that connects to the phone line uses the number assigned to the line. Devices that connect to several lines can have several telephone numbers.
LAN-based H.323 uses IP technology to forward information, thus requiring a gatekeeper. The H.323 endpoint registration with a gatekeeper includes the endpoint IP address, alias, and E.164 address. The gatekeeper uses this information to identify call recipients and endpoints that provide the requested service.
We recommend that you use E.164 numbers that are consistent in length and cannot be confused with other videoconference number clusters. We also recommend that you organize their distribution in a way that is meaningful to users. If you are using a telephone service that provides multiple phone numbers, make sure that each telephone company request is for numbers that have the same format (for example, all numbers have seven digits the user dials).
This section describes how to configure the MCU for standalone operation. In standalone mode, the MC and MP modules are configured at the same time.
To start the Cisco IP/VC Configuration Utility and to choose the MCU you want to configure, perform the following steps:
Step 2 To choose an MCU to configure:
 |
Caution The Cisco IP/VC Configuration Utility can assign the IP address you type into the Unit IP field to any Cisco IP/VC 3500 device residing on the network segment that does not have an IP address associated with the segment. |
Step 3 Click Next. The Enter Password window appears.
Step 4 Enter the MCU password and click Next.
The default password is cisco. The Configuration Source window appears. (See Figure 5-2.)
The Configuration Source window provides version information about the Cisco IP/VC 3510 MCU hardware and software, allows you to change the password, allows you to choose a mode of operation, and allows you to choose a configuration set to load into the configuration utility. Table 5-1 describes the version information. If you want to change the password required to access the unit, click Change Password to access the Change Password dialog box. To continue with the MCU configuration, go to the next section, "Setting the Operation Mode and Selecting a Configuration Source."
Table 5-1 and Table 5-2 define the fixed parameters that the Configuration Source window provides.
| Parameter | Description |
|---|---|
Unit Type | Model number of the selected MCU |
Version of the MCU hardware configuration | |
Allow you to view the versions of the software installed on the unit. To view the versions, click the button. |
| Software | Description |
|---|---|
Cisco IP/VC 3510 MCU software version | |
Version number of the embedded gatekeeper | |
Version number of the H.323 protocol stack the MCU uses | |
Version of the proprietary MIB for SNMP |
The Configuration Source window (see Figure 5-2) lets you specify the MCU operating mode, choose a parameter set to use to configure the unit, and access the parameters that configure the embedded gatekeeper. This section describes how to set the mode of operation and how to choose a configuration source. For instructions on how to enable and configure the embedded gatekeeper, go to the "Configuring the Embedded Gatekeeper."
There are three MCU operating modes:
MCU mode allows you to configure the unit for standalone operation. Both the MC and MP functions are configured. The MCU Distributed and MP Dedicated modes allow you to create a Cisco IP/VC 3510 MCU stack. MCU Distributed lets you configure the MC functions for the stack and specify the MPs you want the MC to use to process streams. MP Dedicated lets you specify the router the MP will use to communicate across the network.
The configuration source is the set of configuration parameters that you load into the Cisco IP/VC Configuration Utility. The parameters can be downloaded from the MCU Flash memory or taken from information stored in the Cisco IP/VC Configuration Utility directory on the computer running the utility. You must choose a configuration source to load into the configuration utility.
The MCU has the following two default configuration sources:
You can modify the parameters you load into the Configuration Utility and upload the changes to the MCU Flash memory. The utility allows you to save the changes as a set. Save the set under a unique name. The set name is added to the Configuration Utility Source drop-down menu and can be chosen to configure other Cisco IP/VC 3510 MCUs when you use the current computer.
To choose an operation mode and a configuration source, perform the following steps:
Step 2 Click the Unit Type field and choose MCU. MCU is the default mode.
Step 3 Click the Source field to display the list of available source sets.
Step 4 Choose the source set you want to load. Current is the default selection.
Step 5 Click Unit Setup.
The Unit Identification window displays information regarding the MCU. You can also specify the location where the MCU is physically placed and set a time differential for the MCU that is located in a different time zone than the computer you are using to configure the unit.
Table 5-3 shows the parameters in the Unit Identification window.
| Category | Description |
|---|---|
Unit Name | Cisco product name. |
Location | Area where the MCU is physically placed. |
Contact | Cisco URL. |
Description | MCU model number. |
Opens the Date/Time Settings dialog box, where you can view and set the time differential when the MCU is located in a different time zone. |
To enter information regarding the location of the MCU, enter the text in the Location field. To set a time differential, click the Date/Time button to display the Date/Times Settings dialog box and set the time differential parameters. Click Next. The Services Definition Table window appears.
The Services Definition Table window lists the videoconference services the MCU provides. (See Figure 5-3.) An MCU service is a set of parameters that the MCU uses to set up a multipoint call. The parameters include the frame rate, video bit rate, picture format, and number of call participants. An MCU service can provide a T.120 data channel that allows end users to share data online. Also, MCU services can be configured to provide continuous presence, a feature in which four conference participants are displayed on each participating monitor simultaneously. Each service must be assigned a unique service prefix that is associated with the MCU when the MCU registers with the gatekeeper, and that users use to initiate the multipoint videoconference call.
This section describes how to create, edit, and delete MCU services.
 |
Note The MCU is shipped with preconfigured services. You can use the default services or delete them. |
This section describes how to create new MCU services. Services that feature continuous presence use a modified set of parameters. See the "Adding a Service with Continuous Presence" section later in this chapter for instructions on how to create a service that provides continuous presence.
You can create up to 20 MCU services. Each service is assigned an entry number and listed in the Services Definition Table.
To create an MCU service, perform the following steps:
Step 2 In the Description field, enter a description for this service.
The description can be up to 31 characters long. You can use the numbers 0 through 9 and the characters pound (#), asterisk (*), and comma (,).
Step 3 In the Prefix field, enter a value for the prefix that users will dial to use this service.
The prefix can have up to 31 characters, including the numbers 0 through 9 and the characters pound (#), asterisk (*), and comma (,).
Step 4 Click the Video Format field and choose the format you want the service to use. H.261 is the default.
Step 5 In the Number of Parties field, enter a value for the number of videoconference participants the MCU will allocate for the call.
For this service, the MCU will always allocate ports for the number of participants you specify, whether or not the specified number of participants actually participate in the call. The number of participants a call can have is also affected by the video bit rate value. Table 5-4 shows the maximum number of participants you can assign per video bit rate. When a user uses a service with maximum values to initiate a videoconference call, the MCU cannot process other calls concurrently.
| Video Bit Rate (K) | Maximum Number of Participants |
|---|---|
0 (audio only) | 24 |
64 | 16 |
110 | 15 |
192 | 11 |
320 | 9 |
448 | 7 |
720 | 5 |
800 | 4 |
1500 | 3 |
~ | 3-9 |
Step 6 In the Video Bit Rate field, enter a value for the maximum video bit rate that the service will allow.
You can enter a value up to 1500 or enter the character for the dynamic rate ~ (tilde). Table 5-4 shows the maximum number of participants you can assign per video bit rate. The video bit rate and number of participants values you use directly affect the available resources the MCU will have for placing videoconference calls. "Calculating MCU Admission Control," describes how you can determine the amount of resources a service will use.
|
Note The MCU uses an algorithm to calculate the available bandwidth for videoconference calls. Of the total videoconference bandwidth, 64 kbps are allocated to audio. To ensure optimum availability, deduct the 64 kbps for audio from the total videoconference bandwidth to derive the video bit rate. For example, for 384-kbps videoconference calls, set the video bit rate value to 320. |
The dynamic rate allows the MCU to set the video bit rate to that of the endpoint initiating the conference. We recommend that you create a service using the dynamic rate for videoconference calls using endpoints with different capabilities. This ensures that all participants receive good picture quality when the endpoint with the lowest capacity initiates the call. (The default maximum video bit rate the dynamic rate will set is 320 kbps. You can change the maximum dynamic rate using the Advanced commands. See the "MCU Advanced Commands" section later in this chapter for instructions on how to use Advanced commands.)
Step 7 If you want the service to provide T.120 support, check the T.120 check box.
Step 8 Click the Frame Rate field and choose the frame rate you want the service to use.
Step 9 Click the Picture Format field and choose the picture format you want the service to use.
Step 10 Click OK. The Services Definition Table window appears.
Step 11 To exit the Services Definition Table window, perform any of the following operations:
To create a service with continuous presence, perform the following steps:
Step 2 Choose an option:
Step 3 In the Description field, enter a description of the service.
The description can be up to 31 characters long. You can use the numbers
0 through 9 and the characters pound (#), asterisk (*), and comma (,). We recommend that you indicate that continuous presence is enabled in the Description field, because there is no listing for continuous presence in the Services Definition Table.
Step 4 In the Prefix field, enter a value for the prefix that users will dial to use this service.
The prefix can have up to 31 characters, including the numbers 0 through 9 and the characters pound (#), asterisk (*), and comma (,).
Step 5 In the Number of Parties field, enter a value for the number of videoconference participants the MCU will allocate for the call for this service.
The MCU will always allocate ports for the number of participants you specify, whether or not the specified number of participants actually participate in the call. The number of participants a call can have is also affected by the video bit rate value. Table 5-5 shows the maximum number of participants you can assign per video bit rate. When a user uses a service with maximized values to initiate a videoconference call, the MCU cannot process other calls concurrently.
| Video Bit Rate (K) | Maximum Number of Participants |
|---|---|
112 | 11 |
128 | 10 |
192 | 7 |
224 | 7 |
256 | 6 |
320 | 4 |
336 | 4 |
384 | 3 |
Step 6 Set the video bit rate value in the Video Bit Rate In field.
The Video Bit Rate In value represents the video bit rate that the MCU will receive from endpoints contributing to the output stream that the MCU distributes to the videoconference endpoints. Continuous presence allocates four endpoints to contribute to the output stream at all times. Consequently, the Video Bit Rate In value must be one-fourth that of the video bit rate output. The Video Bit Rate Out field automatically calculates the video bit rate bandwidth that the service will output from the value you enter into the Video Bit Rate In field. Make sure that the output value is in accordance with the maximum number of participants to video bit rate values shown in Table 5-5. "Calculating MCU Admission Control," describes how you can determine the amount of resources a service will use.
Step 7 Set the Frame Rate value to the rate you want frames sent to the MCU.
Step 8 Click OK. The Services Definition Table window with the continuous presence parameters appears. (See Figure 5-6.)
Step 9 To exit the Services Definition Table window, perform any of the following operations:
The Services Definition Table allows you to edit an existing service. To edit an existing service, perform the following steps:
Step 2 Make the necessary changes and click OK to confirm. The Services Definition Window appears.
Step 3 The edits you make to the service appear in the configuration utility only. They do not take effect until the configuration set is saved to MCU Flash memory. The configuration utility retains the changes until the configuration set is saved or the utility is closed. To continue, do either of the following:
You can delete services that you no longer want to offer. To delete a service, select the service and click Delete.
The Miscellaneous Settings window allows you to identify the gatekeeper and the router you want the MCU to use. (See Figure 5-7.)
To set the parameters in the Miscellaneous Settings window, perform the following steps:
If you want to use the embedded gatekeeper, you must enable the embedded gatekeeper and manually register the MCU. See "Configuring the Embedded Gatekeeper" for instructions on how to configure the embedded gatekeeper. The IP address is same as the MCU IP address.
Step 2 In the Default Router IP field, enter the IP address of the router you want the MCU to use.
Step 3 If you want the MCU to use an external T.120 server to process data streams for videoconference calls, perform the following:
a. Check the External T120 Server check box.
b. In the T120 Server IP field, enter the IP address of the computer on which the T.120 server you want to use is installed.
c. In the T120 Server Port field, enter the number of the listening port that the T.120 server is configured to use.
|
Note For a listing of the external T.120 servers that the MCU supports, refer to the August 2000 or later Release Notes for the Cisco IP/VC 3500 Series Product Family. |
Step 4 Click Next. The LAN Ports Setting window appears.
The LAN Port Settings window allows you to change the MCU port status and IP address information. You can also enter a comment. To change the port status and IP address information, perform the following steps:
If the check mark does not appear in the check box, the port is disabled and the MCU will not send or receive call information.
Step 2 To change the IP address, enter the new IP address in the IP address field.
Step 3 To change the subnet mask, enter the new subnet mask in the IP Mask field.
Step 4 To enter a comment, type the comment in the Description field. You can use up to 31 characters, including spaces.
Step 5 Click Next. The LAN Parameters window appears.
Step 6 Verify that the status and IP address information are correct.
|
Note An asterisk (*) next to the port number indicates that the port parameters have been edited. |
Step 7 Click Next. The Save Settings window appears.
The Save Settings window allows you to save the parameters you have configured as a set and to upload the parameters to the MCU Flash memory. The set is saved in the Cisco IP/VC Configuration Utility directory on the current computer and can be used to restore the parameters to the current MCU or to configure other Cisco IP/VC 3510 MCUs. The name you assign to the set appears in the Source field in the Configuration Source window.
To save and upload the configuration parameters, perform the following steps:
a. Enter the name you want to use for the new configuration parameter set. If you want to update an existing set, click the arrow and select the set you want to update.
b. Click Yes. The Confirm window appears.
Step 2 If you want to upload the parameters to MCU Flash memory whether or not you have saved them, click Yes. The file uploads.
Step 3 The Information message box appears when the upload is completed. Click OK. The Confirm window appears.
Step 4 The Confirm window asks if you want to exit the configuration program. Click Yes to exit.
This section describes how to configure the Cisco IP/VC 3510 MCU for stacked operation. Stacking allows you to configure the MCU to perform the MP function only, and to link those MCUs with MCUs that can perform MC functions. A single Cisco IP/VC 3510 MCU with MC capability can manage up to four Cisco IP/VC 3510 MCUs configured to perform only MP functions. The technique can reduce the number of service prefixes you must create and increase the number of simultaneous calls an MC can manage.
For stacking, the MC and the MP functions are configured separately. The MC configuration includes creating the MCU services and identifying the MP modules you want the MC to use. The MP configuration include specifying the router the MP will use to communicate over the network. An MP can be linked to one MC only.
This section describes how to configure the MC function in the MCU for stacking.
To start the configuration utility and select the MC operation mode for stacking, perform the following steps:
Step 2 Choose the MCU on which you want to configure the MC for stacking:
|
Caution The Cisco IP/VC Configuration Utility can assign the IP address you enter in the Unit ID field to any Cisco IP/VC device residing on the network segment that does not have an IP address associated with the segment. |
Step 3 Click Next. The Enter Password window appears.
Step 4 Enter the MCU password and click Next. The default password is cisco. The Configuration Source window appears. (See Figure 5-9.)
The Configuration Source window provides version information about the Cisco IP/VC 3510 MCU hardware and software, allows you to change the password, allows you to choose the mode of operation you want to use to configure the MCU, and allows you to choose a configuration set to load into the configuration utility. Information about the version information is provided in the section "Starting the Cisco IP/VC Configuration Utility" earlier in this chapter. If you want to change the MCU password, click Change Password to access the Change Password dialog box.
Step 5 Click the Unit Type field and select MC Distributed.
Step 6 Click the field in the Source area and choose a configuration set from the drop-down menu.
A configuration set is the set of parameters that will load into the Configuration Utility. You can alter any of the parameters and upload the set to the MCU Flash memory. Plug & Play and Current are permanent options. Plug & Play loads the MCU default parameters. Current loads the parameters currently saved in the MCU Flash memory. Configuration sets that are saved will also appear. Current is the default set.
Step 7 Click Unit Setup.
The Unit Identification window provides information about the MCU and allows you to configure a clock showing a time differential if the MCU that you are configuring is in a different time zone than the computer you are using to configure the unit. For more information about the Unit Identification window, see the "Setting Unit Identification Parameters" section .
Step 8 In the Unit Identification window, click Next. The MP Definition Table window appears.
The MP Definition Table allows you to register and enable MPs the MC can use to process videoconference streams. (See Figure 5-10.) To register an MP, you must specify the IP address of the Cisco IP/VC 3510 MCU. Up to four MPs can be enabled to use with the MC at one time, including the embedded MP and three MPs from other Cisco IP/VC 3510 MCUs. This section describes how to specify the MPs you want to use with the MC.
To add an MP to the table, perform the following steps:
|
Note You can arrange a for new MP to appear on the list after an existing MP by selecting the MP you want the new MP to follow before you click Add. After you set the parameters for the new MP, it will appear in the MP Settings window after the MP you selected. |
Step 2 In the IP address field, enter the IP address of the MP you want the MC to use.
Step 3 In the Description field, enter a description for this entry.
The description can be up to 31 characters, including spaces.
Step 4 To enable the MC to use this MP, check the Status (Enable/Disable) check box.
The MC can only support four enabled MPs.
Step 5 Click OK. The entry appears in the MP Definition Table.
Step 6 Click Next. The Services Definition Table window appears.
|
Note If you are modifying an existing MC configuration by adding, editing, or deleting an MP and you do not want to make further changes to the MC configuration, you can click Finish to proceed directly to the Save window. No other parameters will be modified. |
The Services Definition Table window for MCU Distributed lists the videoconference services the MC provides. (See Figure 5-12.) An MCU service is a set of parameters that the MC uses to set up a multipoint call. The parameters include the frame rate, video bit rate, picture format, and number of call participants. A service can provide a T.120 data channel that allows end users to share data online. Also, MCU services can be configured to provide continuous presence, a feature in which four conference participants are displayed on participating monitors simultaneously. Each service must be assigned a unique service prefix that is associated with the MCU when the MCU registers with the gatekeeper, and that users use to initiate the multipoint videoconference call.
This section describes how to create, edit, and delete MCU services.
To create a service you want the MC to provide, perform the following steps:
Step 2 In the Description field, enter a description for the service.
The description can be up to 31 characters long. You can use the letters, numbers, and the characters pound (#), asterisk (*), and comma (,).
Step 3 In the Prefix field, enter a value for the service prefix that users will dial to use this service. The prefix can have up to 31 characters, including the numbers 0 through 9 and the characters pound (#), asterisk (*), and comma (,).
Step 4 Click the Video Format field and choose the format you want the service to use. H.261 is the default.
Step 5 In the Number of Parties field, enter a value for the number of videoconference participants the MC will allocate for the videoconference.
For this service, the MC always allocates ports for the number of participants you specify whether or not that number of participants actually participate in the call. The number of participants a call can have also depends on the video bit rate the call uses. Table 5-6 shows the maximum number of participants you can assign per video bit rate. The number you enter can affect whether the MC accepts or rejects a call.
When a user chooses a service and initiates a call, the resources for the call are automatically established. In placing the call, the MC examines the available resources of each linked MP in sequence. It directs the call to the first MP with enough resources available to process the call request. If no MP has enough available resources, the call is rejected. "Calculating MCU Admission Control," describes how you can determine the amount of resources a service allocates.
| Video Bit Rate (K) | Maximum Number of Participants |
0 (audio only) | 24 |
64 | 16 |
110 | 15 |
192 | 11 |
320 | 9 |
448 | 7 |
720 | 5 |
800 | 4 |
1500 | 3 |
~ | 3-9 |
Step 6 In the Video Bit Rate field, enter a value for the maximum video bit rate that the service will allow.
You can enter a value up to 1500 or enter the character for the dynamic rate ~ (tilde). Table 5-6 shows the maximum number of participants you can assign per video bit rate. The value you enter can affect whether the MC processes additional videoconference calls on the next available MP. "Calculating MCU Admission Control," describes how you can determine the amount of resources a service will use.
|
Note The MC uses an algorithm to calculate the available bandwidth for videoconference calls. Of the total videoconference bandwidth, 64 kbps are allocated to audio. To ensure optimum availability, deduct the 64 kbps for audio from the total videoconference bandwidth to derive the video bit rate. For example, for 384-kbps videoconference calls, set the video bit rate value to 320. |
The dynamic rate allows the MC to set the video bit rate to that of the endpoint initiating the conference. We recommend that you create a service using the dynamic rate for videoconference calls using endpoints with different capabilities. This ensures that all participants receive good picture quality when the endpoint with the lowest capacity initiates the call. (The default maximum video bit rate the dynamic rate will set is 320 kbps. You can change the default rate using the Advanced commands. See the "MCU Advanced Commands" section later in this chapter for instructions on how to use Advance commands.)
Step 7 If you want the service to provide T.120 support, check the T.120 Enabled check box.
Step 8 Click the Frame Rate field and choose the frame rate you want the service to use.
Step 9 Click the Picture Format field and choose the picture format you want the service to use.
Step 10 If you want a specific MP to process this service, click the MP Link field and choose the IP address of the MP.
The link feature assigns process priority for the service to the MP you specify. Requests for the service are directed by the MC to this MP first. If the MP is busy, the call is directed to the next available MP for processing. If the link is not set, the MC uses the first available MP.
Step 11 Click OK. The Services Definition Table window appears.
Step 12 To exit the Services Definition Table window, perform any of the following operations:
To create an MCU service that enables the continuous presence feature, perform the following steps:
Step 2 Choose an option:
Step 3 In the Description field, enter a description of the service.
The description can be up to 31 characters long. You can use letters, numbers, and the characters pound (#), asterisk (*), and comma (,). We recommend that you indicate that continuous presence is enabled in the description, because there is no listing for continuous presence in the Services Definition Table.
Step 4 In the Prefix field, enter a value for the service prefix users will dial to use this service.
The prefix can have up to 31 characters, including the numbers 0 through 9 and the characters pound (#), asterisk (*), and comma (,).
For this service, the MC always allocates ports for the number of participants you specify whether or not that number of participants actually participate in the call. The number of participants a call can have also depends on the video bit rate the call uses. Table 5-7 shows the maximum number of participants you can assign per video bit rate. The number you enter can affect whether the MC accepts or rejects a call.
When a user chooses a service and initiates a call, the resources for the call are automatically established. In placing the call, the MC examines the available resources of each linked MP in sequence. It directs the call to the first MP with enough resources available to process the call request. If no MP has enough available resources, the call is rejected. "Calculating MCU Admission Control," describes how you can determine the amount of resources a service allocates.
| Video Bit Rate (K) | Maximum Number of Participants |
|---|---|
112 | 11 |
128 | 10 |
192 | 7 |
224 | 7 |
256 | 6 |
320 | 4 |
336 | 4 |
384 | 3 |
Step 6 Set the video bit rate value in the Video Bit Rate In field.
The Video Bit Rate In value represents the video bit rate the MP will receive from endpoints contributing to the output stream that the MP distributes to the videoconference endpoints. Continuous presence allocates four endpoints to contribute to the output stream at all times. Consequently, the Video Bit Rate In value must be one-fourth that of the video bit rate output. The Video Bit Rate Out field automatically calculates the video bit rate bandwidth that the service will output from the value you enter in the Video Bit Rate In field. Make sure that the output value is in accordance with the maximum number of participants to video bit rate values shown in Table 5-7. "Calculating MCU Admission Control," describes how you can determine the amount of resources a service will use.
Step 7 If you want the service to provide T.120 support, check the T.120 Enabled check box.
Step 8 Set the Frame Rate value to the rate you want frames sent to the MCU.
Step 9 If you want a specific MP to process this service, click the MP Link field and choose the IP address of the MP.
The link feature assigns process priority for the service to the MP you specify. Requests for the service are directed by the MC to this MP first. If the MP is busy, the call is directed to the next available MP for processing. If the link is not set, the MC uses the first available MP.
Step 10 Click OK. The Services Definition Table window with the continuous presence parameters appears. (See Figure 5-15.)
Step 11 To exit the Services Definition Table window, perform any of the following operations:
The Services Definition Table allows you to edit existing services. To edit an existing service, perform the following steps:
The Service Settings dialog box appears, displaying the service parameters.
Step 2 Make the necessary changes and click OK to confirm. The Services Definition Window appears.
The edits you make to the service appear in the configuration utility only. They do not take effect until the configuration set is saved to MCU Flash memory. The configuration utility retains the changes until the configuration set is saved or the utility is closed. To continue, do either of the following:
You can delete services that you no longer want to offer. To delete a service, select the service and click Delete.
The Miscellaneous Settings window allows you to specify the gatekeeper and the router you want the MC to use. (See Figure 5-16.) It also provides a mechanism for you to enter MCU line commands.
To set the parameters in the Miscellaneous Settings window, perform the following steps:
|
Note You cannot enable the embedded gatekeeper when the MCU is configured for a stacked operations mode. |
Step 2 In the Default Router IP field, enter the IP address of the router you want the MC to use.
Step 3 If you want the MCU to use an external T.120 server to process data streams for videoconference calls, perform the following:
a. Check the External T120 Server check box.
b. In the T120 Server IP field, enter the IP address of the computer on which the T.120 server you want to use is installed.
c. In the T120 Server Port field, enter the number of the listening port the T.120 server is configured to use.
|
Note For a listing of the external T.120 servers that the MCU supports, refer to the August 2000 or later Release Notes for the Cisco IP/VC 3500 Series Product Family. |
Step 4 Click Next. The LAN Ports Setting window appears.
The Cisco IP/VC 3510 MCU LAN port settings are the same for all operation modes. The LAN Port Settings window allows you to change the port status and IP address information of the unit, and to enter a comment. To change the port status and IP address information and enter a comment, perform the following steps:
Step 2 To change the IP address, enter the new IP address in the IP Address field.
Step 3 To change the subnet mask, enter the new subnet mask in the IP Mask field.
Step 4 To enter a comment, type the comment in the Description field. You can use up to 31 characters, including spaces.
Step 5 Click Next. The LAN Parameters window appears.
Step 6 Verify that the status and IP address information are correct.
|
Note An asterisk (*) next to the port number indicates that the port parameters have been edited. |
Step 7 Click Next. The Save Settings window appears.
The Save Settings window allows you to save the parameters you have configured for the MC as a set and to upload the parameters to the unit Flash memory. The set is saved in the Cisco IP/VC Configuration Utility directory on the current computer and can be used to restore the parameters to the current MC or to configure other Cisco IP/VC 3510 MCUs for MC mode. The name you assign to the set appears in the Source field in the Configuration Source window.
To save and upload the configuration parameters, perform the following steps:
a. Enter the name you want to use for the new configuration parameter set. If you want to update an existing set, click the arrow and choose the set you want to update.
b. Click Yes. The Confirm window appears.
Step 2 If you want to upload the parameters to the unit Flash memory whether or not you have saved them, click Yes. The file uploads.
Step 3 The Information message box appears when the upload has completed. Click OK. The Confirm window appears.
Step 4 The Confirm window asks if you want to exit the configuration program. Click Yes to exit.
You can configure the Cisco IP/VC 3510 MCU to be used in MP-only mode. In this mode, the unit only processes and distributes the videoconference streams for calls the MC directs to it. You must register the MP with the MC that it is to serve. The registration is described in the "Specifying MPs the MC Is to Use" section. This section describes how to configure the MCU for MP mode.
To set the unit to function as an MP only, perform the following steps:
Step 2 Choose the MCU on which you want to configure the MP for stacking:
|
Caution The Cisco IP/VC Configuration Utility can assign the IP address you enter in the Unit ID field to any Cisco IP/VC device residing on the network segment that does not have an IP address associated with the segment. |
Step 3 Enter the MCU password and click Next. The default password is cisco. The Configuration Source window appears. (See Figure 5-17.)
Step 4 Click the Unit Type field and choose MP Dedicated.
Step 5 Click the field in the Source area and choose a configuration set to load into the configuration utility.
The default set is Current, which loads the parameter set currently on the MCU into the utility.
|
Note A warning prompt appears, stating that the built-in gatekeeper is not available for this unit type. Configuration changes will take effect after restarting the unit. Click OK. The Configuration Source window reappears. |
Step 6 Click Unit Setup. The Unit Identification window appears.
Step 7 The Unit Identification window provides information about the unit, and allows you to enter a comment and set a time differential for units that are located in different time zones. See the "Starting the Cisco IP/VC Configuration Utility" section earlier in this chapter for more information regarding the Unit Identification window. Click Next. The Miscellaneous Settings window appears.
The Miscellaneous Settings window (see Figure 5-18) allows you to specify the router you want the MP to use to communicate over the network and to use advanced commands. This section describes how to specify the router you want the MP to use. For more information about the advanced commands, see the "Advanced Commands Reference" section.
To specify the router you want the MP to use, perform the following steps in the Miscellaneous Settings window:
Step 2 Click Next. The LAN Ports Settings window appears.
The Cisco IP/VC 3510 MCU LAN port settings are the same for all operation modes. The LAN Port Settings window allows you to change the port status and IP address information of the unit, and to enter a comment. To change the port status and IP address information and enter a comment, perform the following steps:
The LAN port is enabled by default. The MP will not send or receive call information.
Step 2 To change the IP address, enter the new IP address in the IP Address field.
Step 3 To change the subnet mask, enter the new subnet mask in the IP Mask field.
Step 4 To enter a comment, type the comment in the Description field. You can use up to 31 characters, including spaces.
Step 5 Click Next. The LAN Parameters window appears.
Step 6 Verify that the status and IP address information are correct.
|
Note An asterisk (*) next to the port number indicates that the port parameters have been edited. |
Step 7 Click Next. The Save Settings window appears.
The Save Settings window allows you to save the parameters you have configured for the MP as a set and to upload the parameters to the unit Flash memory. The set is saved in the Cisco IP/VC Configuration Utility directory on the current computer and can be used to restore the parameters to the current MP or to configure other Cisco IP/VC 3510 MCUs for MP mode. The name you assign to the set appears in the Source field in the Configuration Source window.
To save and upload the configuration parameters, perform the following steps:
a. Enter the name you want to use for the new configuration parameter set.
b. Click Yes. The Confirm window appears.
Step 2 If you want to upload the parameters to the unit Flash memory whether or not you have saved them, click Yes. The file uploads.
Step 3 The Information message box appears when the upload has completed.
Click OK. The Confirm window appears.
Step 4 The Confirm window asks if you want to exit the configuration program. Click Yes to exit.
The MCU advanced commands are line commands that set MCU parameters that are not available in the configuration utility. These commands allow you set such parameters as the debug notification level, voice switching level, video switching mode, and the dynamic bit rate. Advanced commands are set through the configuration utility. This section describes how to access the dialog box for advanced commands, enter the commands, and list the commands you can use.
To access the dialog box for advanced commands, perform the following steps:
Step 2 Select the IP address of the MCU you want to configure or enter the IP address in the Unit IP field and click Next. The Enter Password window appears.
Step 3 Enter the MCU password and click Next. The default password is cisco. The Configuration Source window appears.
Step 4 Click the Unit Type field and select the operation modes.
Step 5 Click the Source field and choose a source set.
Step 6 Click Unit Setup.
Step 7 Click Next in the subsequent windows until the Miscellaneous Settings window appears.
Step 8 Click Advanced. The Advanced dialog box appears. (See Figure 5-19.)
To enter an advanced command, perform the following steps:
Advanced commands are not case sensitive.
Step 2 Click Send.
The command is relayed to the MCU. The MCU sends a response to verify that a valid command was entered. The response is displayed in the Response field. The following response is displayed for an invalid command:
Unknown Command
Step 3 Repeat Step 1 and Step 2 for each command you want to enter.
Step 4 Click Cancel when you are finished.
This section provides information about the available advanced commands.
Function
Displays or sets the frequency of the CPU usage load displays.
Parameters
No parameter—Displays the current CPU usage load.
None—No CPU usage information is displayed.
Rare—Rarely displays CPU usage information.
Often—Displays CPU usage often.
Differ—Displays CPU usage information only if the usage changes by more
than 1%.
Function
Sets the default maximum dynamic bit rate.
Parameters
Enter the required rate in bits-per-second up to 1500000.
Function
Changes the type and number of debug messages that are generated.
Parameters
10—Default value
35—Enhanced level
|
Note We do not recommend exceeding NotifyLevel 25. Doing so can overload the system with very large debug messages. |
Function
Displays the IP address of the gatekeeper the MCU is registered with or registers the MCU with another gatekeeper.
Before you register the MCU with another gatekeeper you must unregister it from its current gatekeeper first.
Parameters
No parameter—Displays the IP address of the gatekeeper to which the MCU is registered.
IP address of a gatekeeper—MCU registers with this gatekeeper. You do not have to enter the entire IP address. When the gatekeeper is on the same network segment as the MCU, the host portion of the IP address is sufficient.
Function
Allows you to change the color scheme of the HTTP-based monitoring pages. Currently there are three defined color scheme options. A number from 0 to 2 identifies each color scheme option. The color scheme change takes effect only after you restart the MCU unit.
Parameters
No parameters—Displays the number of the current color scheme option.
0 to 2—Changes the color scheme according to the option you specify.
Additional advanced commands may be available for different versions of the MCU.
Function
Selects fast video-switching mode. This mode is useful when fast and interactive video switching is required. This is the default mode for the MCU.
Parameters
None.
Function
Selects slow video-switching mode. This mode is useful for cases in which background noise causes a high level of false video switching sequences. This mode will decrease the number of false switching events causing the switch to be less sensitive.
Parameters
None.
Function
Unregisters the MCU from the gatekeeper. You can then register the MCU to another gatekeeper.
Parameters
None.
Function
Displays or sets the video-switching mode for the MCU.
The default mode is CUCME
Parameters
No Parameter—Displays the current video-switching mode.
ALLC1—All participants see the participant that is talking the loudest, and the participant talking the loudest, sees himself/herself.
CUCME—All participants see the participant that is talking the loudest, and the participant currently talking sees the previous participant that spoke.
Posted: Wed Sep 20 09:13:19 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.