|
|
February 2000
This document supersedes the following Cisco IP/VC 3500 Series product Release Notes:
The information from each of the documents listed has been combined and compiled with additional information to create the current document. The current document presents information specific to each Cisco IP/VC 3500 Series model and the embedded gatekeeper under the heading of the pertinent model or the gatekeeper. Information pertaining to all models is presented as separate topics.
The product family consists of the following devices:
The Cisco IP/VC 3510, Cisco IP/VC 3520, and Cisco IP/VC 3525 include an embedded gatekeeper.
The following sections provide information pertaining specifically to the
Cisco IP/VC 3510 MCU that is not included in the Cisco IP/VC 3510 MCU User Guide.
The total number of participants in all conferences that the Cisco IP/VC 3510 MCU can handling at one time depends on several factors. The factors include the video bit rate reserved by the service prefix, the number of participants reserved by the service prefix, and the amount of bandwidth the IP/VC 3510 MCU is currently using for conferences. The IP/VC 3510 MCU assumes that the parameters set in the service prefix are actually being used whether or not all of the participants specified in the service prefix participate in the conference. (For example, if the service prefix specifies five participants and only three participate, the IP/VC 3510 MCU still allocates bandwidth for five participants.) The IP/VC 3510 MCU uses this information to determine the current bandwidth usage and whether to admit a new conference or to expand a conference in progress.
In deciding whether to permit or reject a new conference, the IP/VC 3510 MCU determines how much bandwidth remains available and calculates how much the new conference will use. If the new conference uses more bandwidth than is available, the IP/VC 3510 MCU rejects the request. To ensure that you use your resources efficiently, we suggest that for each video bit rate you use you create several service prefixes representing the range of participants that are most likely to be used. For example, for the video bit rate 384, you can create service prefixes for two, three, and five participants.
We also suggest that you encourage your users to initiate conferences using the service prefix that specifies the exact number of participants expected in the conference. Users can make request for additional participants join the conference after the conference commences.
You can increase the number of participants in a conference beyond what a single IP/VC 3510 MCU allows by cascading IP/VC 3510 MCUs. Cascading is a method whereby a conference on one IP/VC 3510 MCU dials up a conference on another IP/VC 3510 MCU. The conference of the dialing IP/VC 3510 MCU becomes one of the conference participants of the receiving IP/VC 3510 MCU. In this way, conference members of the dialing IP/VC 3510 MCU can participate in the original conference without taxing IP/VC 3510 MCU resources.
The Cisco IP/VC 3510 MCU allows you to create services that have dynamic bandwidths (video bit rates). You can use the variable "~" to define the video bit rate the call will use. When the variable is used, the MCU negotiates with the conference participants to establish a common bandwidth for the conference. The IP/VC 3510 MCU does not support speed matching.
Cascading is a technique that allows an MCU to join the videoconference of another MCU. The joining MCU creates a conference that it uses to join another conference. In this way, more conferees can participate in the original conference than a single MCU can accommodate and the conference load can be better distributed. This section describes how to access MCUs in the cascaded conference and how to lock on a video participant.
To monitor the participants of a cascaded conference, you must access the monitoring utility of each cascaded MCU separately. To access the monitoring utility for the MCU, complete the following steps:
Step 2 Enter the IP address or domain name assigned to the MCU in the Location field in the browser window and click Enter. The Cisco IP/VC 3500 Series Video MCU page asking for the conference password (also referred to as the conference id) appears.
Step 3 Enter the conference id of the MCU conference that you want to monitor and click OK. The Cisco IP/VC 3500 Series Video MCU participants page appears. This page shows the participants, including other MCUs that have joined this conference. MCUs that have joined this conference are listed with the conference id that they use to join this conference.
Step 4 Repeat Steps 1 through 3 for all MCUs participating in the cascaded conference that you want to monitor.
To lock the video broadcast on a participant in a cascaded conference, complete the following steps:
Step 2 Locate the conference page of the participant whose view you want to display and click the radio button of that participant.
Step 3 In all other conference pages, click the radio button of the MCU that is linked to the MCU whose conference the selected participant belongs to. Chair Release should appear in all pages.
Step 4 In the conference page of the participant whose view you want to display, click Lock/Unlock. The view of the selected participant appears on all monitors except that of the selected participant.
You can use line commands to exercise additional control over the Cisco IP/VC 3510 MCU. Line commands let you set the video switching mode (which affects who the camera focuses on during a conference), specify the gatekeeper you want the MCU to register with, and set the debug notification level, among other functions. Line commands are described in the Cisco IP/VC 3510 MCU
User Guide in the "Advanced Commands for the MCU" section. Refer to that section for information on how to use line commands in the Cisco IPVC Configuration Utility for the MCU. Table 1 lists the line commands you can use with the MCU.
Command | Description |
|---|---|
SpeakSlct_Fast: | Voice Switch setting fast switching. |
SpeakSlct_Slow: | Voice Switch setting slow switching. |
CloseConf: <conf> | Close conference. |
CloseCall: <number> | Drop caller. |
CpUseDisp:[DIFFER, RARE, OFTEN, NONE] | Changes the CPU usage notification. |
VdoSwMode:[CUCME, ALLC1] | Changes the Video Switch Mode. |
Unregister:<none> | Unregisters the MCU. |
register: <ip> | Registers the MCU to the gatekeeper specified. |
This section lists bugs we had not resolved at the time the Cisco IP/VC 3510 MCU was released.
The following sections provide information pertaining specifically to the
Cisco IP/VC 3520 Gateway that are not included in the Cisco IP/VC 3520 Gateway User Guide.
LAN endpoints that use NetMeeting, LiveLAN, or VCON-Quick Connect v1.4 cannot initiate T.120 sessions. The endpoints can participate in T.120 sessions that are initiated on the WAN.
The number of incoming call routing methods you have enabled can affect the time required for a call to get through to the recipient.
If you are using a LiveLAN system, you may experience problems due to the inability of the LiveLAN system to tolerate opening and closing of channels.
The following sections provide information pertaining specifically to the
Cisco IP/VC 3525 Gateway that is not included in the Cisco IP/VC 3525 Gateway User Guide.
The Cisco IP/VC 3525 Gateway uses a proprietary PRI interface. Cisco ships a PRI adapter cable that allows you to connect the unit to a standard CSU-compatible interface. If you want to connect the Cisco IP/VC 3525 to a non-CSU-compatible interface, you must obtain or construct an appropriate patch cable. Table 2 shows the pinout configuration of the Cisco IP/VC 3525 Gateway PRI port.
| Pin | Line |
|---|---|
1 | --- |
2 | --- |
3 | Receive (+) Tip2 |
4 | Transmit (-) Ring1 |
5 | Transmit (+) Tip1 |
6 | Receive (-) Ring 2 |
7 | --- |
8 | --- |
Figure 1 shows the Cisco IP/VC 3525 and CSU pinout configuration of the adapter cable.
Table 3 shows the impedance of the E1/T1 interface, balanced in symmetrical pairs.
| T1 RJ-45 | E1 R-45 |
|---|---|
100 Ohms | 120 Ohms |
If you connect the Cisco IP/VC 3525 Gateway directly to the PRI line, we recommend that you insert a CSU/DSU device between the Cisco IP/VC
3525 Gateway port and the patch cable to ensure that the signal strength is at the proper level for the Cisco IP/VC 3525 Gateway.
The PRI does not support direct connections to ISDN smart jacks.
This section provides information about the limitations and restriction of the Cisco IP/VC 3525 Gateway that are not included in the Cisco IP/VC 3525 Gateway User Guide.
LAN endpoints that use NetMeeting, LiveLAN, or VCON-Quick Connect v1.4 cannot initiate T.120 sessions. The endpoints can participate in T.120 sessions that are initiated on the WAN.
The number of incoming call routing methods you have enabled can affect the time required for a call to get through to the recipient.
If you are using a LiveLAN system, you may experience problems due to the inability of the LiveLAN system to tolerate opening and closing of channels.
The following sections provide information pertaining specifically to the
Cisco IP/VC 3530 VTA that is not included in the Cisco IP/VC 3530 VTA User Guide.
The Tandberg Vision 2000 version B4.0 and Vision 800/2500/5000 version C1.1 indicate continuous incoming calls after call termination. To work around this problem, change the V.35 cable by clipping off the wire that goes into H (DTR) on the Winchester connector and short the pin H (DTR) to pin C (CTS).
This section provides information about the limitations and restriction of the Cisco IP/VC 3530 VTA that are not included in the Cisco IP/VC 3530 VTA User Guide.
Incoming restricted calls (2 x 56K, 112K, 336K) are not supported.
The following sections provide information pertaining to the Cisco IP/VC 3500 embedded gatekeeper. The embedded gatekeeper is available in the Cisco IP/VC 3510 MCU, the Cisco IP/VC 3520 Gateway, and the Cisco IP/VC 3525 Gateway. Although the gatekeeper resides within the MCU or gateway box, it is an independent entity that can be used with the resident MCU or gateway, independently of the MCU or gateway, or not used.
The information provided here is not included in the Cisco IP/VC 3510 MCU
User Guide, Cisco IP/VC 3520 Gateway User Guide, and Cisco IP/VC 3525 Gateway User Guide.
The Cisco IP/VC Configuration Utility allows you to configure the gatekeeper separately from the MCU or gateway with which it shares the box. This section describes how to save embedded gatekeeper configuration parameters.
The embedded gatekeeper configuration tables are set and saved independently of each other. To save a configuration table, complete the following steps:
Step 2 Log in to the Cisco IP/VC 3500 Series unit that has the gatekeeper parameters you want to save.
Step 3 Click Gatekeeper in the Configuration Source dialog box.
Step 4 Click the application parameter configuration you want to save.
Step 5 Set the parameters as you want to save them in the table.
Step 6 Click Save. The Save As dialog box appears.
Step 7 In the File name text box, enter a name for the file you want to save. A predefined file extension is automatically applied for the gatekeeper parameter table you are saving. The extension for each gatekeeper parameter table is as follows:
Step 8 Click Save.
The Cisco IP/VC Configuration Utility recognizes that the embedded gatekeeper shares the box with an MCU or gateway, and allows you to configure the gatekeeper separately. This section describes how to load embedded gatekeeper parameters you have saved into the Cisco IP/VC Configuration Utility to use to restore the gatekeeper parameters or to configure another embedded gatekeeper.
To load embedded gatekeeper table configuration parameters you have saved into the configuration utility, complete the following steps:
Step 2 Log in to the Cisco IP/VC 3500 Series unit that has the parameters you want to load.
Step 3 Select Gatekeeper in the Configuation Source dialog box.
Step 4 Click the application parameter into which you want to load the saved parameters.
Step 5 Click Load. The Open dialog box appears.
The Open dialog box lists files in the appropriate Cisco IP/VC directory that you can load. The file type is preselected. The file types are as follows:
Step 6 Select the file you want to load.
Step 7 Click OK. The parameters are loaded into the Cisco IP/VC Configuration Utility.
You can use the file as is or modify the parameters for the current embedded gatekeeper. The parameters can be written to Flash memory when you exit the definition table.
You must manually register endpoints that use NetMeeting version 2.x and earlier with the gatekeeper because these versions of NetMeeting do not support automatic gatekeeper registration.
NetMeeting users can only participate in conferences that use QCIF. If you anticipate NetMeeting clients to participate in conferences, be sure to create MCU services that use the QCIF format.
Endpoint phone numbers cannot start with numbers that are used as service prefixes. For example, if 61 is used as an MCU service prefix, you cannot assign endpoints phone numbers that begin with 61 such as 6111 or 6138526.
If you want to improve the audio quality of a NetMeeting endpoint, we recommend that you set the endpoint bandwidth by completing the following steps:
Step 2 Click the General tab.
Step 3 In the Network Bandwidth section, click the text box to display the drop-down list and select ISDN.
Step 4 Click OK.
This section lists bugs we had not resolved at the time your Cisco IP/VC 3500 Series product was released.
This section describes how to save the configuration parameters for Cisco IP/VC models. The procedure is the same for all four models. If you want to save parameters for the embedded gatekeeper, see the "Saving Embedded Gatekeeper Parameters" section.
You can save the configuration parameters of the Cisco IP/VC 3510, Cisco IP/VC 3520, Cisco IP/VC 3525, or Cisco IP/VC 3530 you log in to by model. You can use the configuration set you save to restore the parameters to the original unit or to configure another unit of the same model.
The configuration set you save is associated with the Cisco IP/VC Configuration Utility you use to save it. The utility writes the name of the set in the script it uses to manage units of the Cisco IP/VC model on the network. It also creates a file containing the configuration parameters in the Configuration folder in Cisco IPVC Tools. When you log in to a unit that is the same Cisco IP/VC model, the name you use to save the set appears in the Source field on the Configuration Source page.
To save the configuration parameters for any Cisco IP/VC model, complete the following steps:
Step 2 Select or enter the IP address of the Cisco IP/VC unit for which you want to save the configuration parameters.
Step 3 Enter the password (the factory default is cisco).
Step 4 In the Configuration Source dialog box, click the Source text box to display the list of configuration sets. Select the set you want to use. CURRENT loads the parameters currently in the Flash memory of the unit into the configuration utility. Plug & Play loads the factory default parameters into the configuration utility.
Step 5 Click Unit Setup.
Step 6 Review each of the configuration dialog boxes to ensure that the parameters are correct, and click Next to go to the next dialog box.
 |
Note Some configuration dialog boxes have a Finish button. Finish allows you to skip the remaining configuration dialog boxes and go directly to the Save Setup dialog box. All parameters, including those you do not review, are saved when you save the set. |
Step 7 In the Save Setup dialog box, complete the following steps:
a. In the Save as text box, enter a name for the configuration set you want to create. If you want to save the parameters as an existing set, click the arrow to display the list of available sets for this model and select the set you want.
|
Note We recommend that you do not use Current or Plug & Play as names for the new file. |
b. Click Yes. The set is saved in the Cisco IPVC Tools/Configuration folder on the configuring computer. The Confirm dialog box appears.
Step 8 The Confirm dialog box lets you upload the configuration file you have just saved to the Flash memory of the unit. If you do not want to save the parameters to the unit, click No. If you want to upload the parameters to the unit, click Yes.
Step 9 Complete the remaining dialog boxes.
The configuration set name will appear on the Source drop-down list in the Configuration Source dialog box whenever you access this Cisco IP/VC model on this computer.
You can load a saved configuration parameter set into the Cisco IP/VC Configuration Utility for any Cisco IP/VC unit of the appropriate model. After you load the set into the Utility, you can save the parameters to the unit or modify the parameters and save them to the unit or as another configuration set.
This section describes how to load the configuration parameters you have saved to Cisco IP/VC 3500 models. The procedure is the same for all four models (the process only allows you to load parameters appropriate to the version of the IP/VC Configuration Utility that you open). If you want to load parameters for the embedded gatekeeper, see the "Loading Saved Embedded Gatekeeper Parameters" section.
To load a configuration set into the Cisco IP/VC Configuration Utility, complete the following steps:
Step 2 Log in to the Cisco IP/VC unit you want to configure or of the same model as the configuration set you want to load.
Step 3 Continue to the Configuration Source dialog box and click the Source arrow. A drop-down list appears containing the names of all of the configuration sets associated with this model on the current computer.
Step 4 Select the file you want to use.
Step 5 Click Unit Setup. The configuration parameters are loaded into the configuration utility.
This section describes LAN configuration issues that can affect the performance of your IP/VC 3500 Series unit.
Cisco IP/VC 3510 MCU, Cisco IP/VC 3520 Gateway, and Cisco IP/VC 3525 Gateway are equipped with 10/100BaseT, half-duplex Ethernet interfaces. The Cisco IP/VC 3530 VTA is equipped with a 10BaseT, half-duplex Ethernet interface. To ensure best performance, be sure that the switch you connect the Cisco IP/VC unit to automatically sets to or is manually set to half-duplex operation.
If your network is subjected to heavy multicast traffic, you may experience degradation in videoconference quality. The MCU may not be able to handle all of the information the switch sends. Try disabling the multicast feature on the switch. (Multicast can be disabled on some Cisco Catalyst switches such as the Catalyst 5000 by accessing Interface/Port and applying Block.)
Before you start configuring your videoconferencing components, we recommend that you think about the kinds of calls that will be made in your environment and create a dial plan. A dial plan can anticipate your dialing needs and prevent potential call failures that occur because of dialing conflicts. This section discusses key points and issues regarding dial-plan implementation. The topics discussed are: the dial-string aggregate, service prefixes, zone prefixes, phone numbers, and routing.
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, and recipient phone number. Although there is a general format regarding the order of the dial string, several factors can affect how the dial string is read: cluster lengths may vary, 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.
A service prefix (referred to as a technology or tech prefix in the Cisco MCM documentation) is an identifier assigned to a service provided by an MCU or gateway. A service is the set of parameters that define a videoconference call. Services can specify the conference bandwidth, format, and the number of call participants. The call initiator uses the service prefix to specify the type of call when setting up the conference.
Service prefixes must be registered with the gatekeeper 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, that cannot be confused with other number-clusters, and that are meaningful to users.
A gatekeeper and the H.323 endpoints that register with it comprise 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, you can assign zone prefixes. 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, that cannot be confused with other number-clusters, and that 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 the need for a gatekeeper. The gatekeeper registration of H.323 endpoint includes these endpoint attributes: IP address, alias, and E.164 address. The gatekeeper uses this information to identify call recipients and endpoints that provide the requested service.
An E.164 address is a phone number that is assigned to the computer. It can be a regular phone number associated with a telephone line connected to a gateway or a number the user creates while setting up the H.323 utility.
We recommend that you use E.164 addresses that are consistent in length, that cannot be confused with other videoconference number-clusters, and that you organize their distribution is such a way that is meaningful to users. If you are using a telephone service that provides multiple phone numbers, make sure that each telco request is for numbers that have the same amount of passable digits. For example, each telco request would ask for numbers that require the users to dial seven digits.
Videoconference calls can be placed through a gateway to H.323 terminals on the LAN. Depending on how your system is set up, calls can be routed directly or indirectly to the LAN recipient. Incoming calls are routed through the gateway. Cisco IP/VC 3500 Series gateways provide the following four methods of routing incoming calls:
To use the Cisco MCM gatekeeper with proxy enabled with a Cisco IP/VC
3500 Series product, you must install Cisco IOS Release 12.0(7)T or later.
Use this release note in conjunction with the following documents:
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
.
Posted: Mon Mar 6 07:52:08 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.