|
|
This chapter covers problems you may encounter when configuring, operating, and managing the Cisco IP/VC 3510 MCU and the embedded gatekeeper. Suggested actions you can use to solve the problems are provided. The topics include:
This section identifies problems that the LEDs can indicate and suggests possible solutions.
Power LED does not light
This indicates that the Cisco IP/VC 3510 MCU is not properly connected to the power source.
Link LED does not light
This indicates that the LAN port is not connected to the network.
This section identifies problems that can encounter using configuration utility and suggests possible solutions.
MCU IP address does not appear in the Select Unit list box
The MCU may be on a different network segment than the computer you are using to view or set the MCU parameters.
Exception error appears when you try to access the MCU
The MCU may be disconnected from the network.
Reply from
Request timeout You cannot upload a file to the MCU using the Cisco IP/VC Software Upload Utility
The computer you are using to upload may not be able to contact the MCU.
This section discusses issues that may occur when a connection is made to the MCU through the serial port for configuration and diagnostics.
You cannot access the MCU through the serial port
Information from the MCU does not appear on the terminal emulator screen.
To verify communication, perform the following steps:
Step 2 Press Enter.
If the prompt moves, the terminal emulator is communicating with the MCU.
Step 3 Restart the MCU. A log of the startup events appears on the computer monitor.
Step 4 If nothing appears, check the cable connection between the MCU and the computer.
You must use the terminal/modem cable or a null cable. Contact Cisco Technical Support for assistance.
You cannot access a remote MCU through a modem for a terminal emulator session
Information from the MCU does not appear on the terminal emulator screen after you have dialed the modem number.
This section identifies problems that users can have making calls through the MCU and suggests possible solutions.
Users are unable to share data
User data-sharing applications do not open on a videoconference call.
To verify that the service is configured to use T.120, perform the following steps:
Step 2 In the Select Unit dialog box, enter the IP address of the MCU that is being used to place the call.
Step 3 Click Next.
Step 4 Go to the Configuration Source window and select Current in the Source field.
Step 5 Click Unit Setup and Next.
Step 6 Go to the Services Definition Table and make sure that the T.120 parameter for the service that is being used is set to Yes.
If you want to modify the parameter, select the service and click Edit.
Step 7 Click Abort to exit the configuration utility unless you want to edit the service.
This section identifies problems users can have receiving calls through the MCU and suggests possible solutions.
If you are using the embedded gatekeeper, try refreshing the registration database. Click Unregister All in the Network Control window. All dynamically registered endpoints unregister and reregister with the embedded gatekeeper.
 |
Caution Unregister All terminates all ongoing calls. |
This section identifies problems that can occur while using the embedded gatekeeper and suggests solutions.
User is not able to use a call service
The call service may not be registered with the embedded gatekeeper.
The service that the user wants to use must be registered with the embedded gatekeeper. Verify that the service is listed in the gatekeeper's Services Definition Table in the Cisco IP/VC Configuration Utility. If the service is not listed, you can add it. See the "Registering Services Provided by Endpoints" section for instruction on how to register a service with the embedded gatekeeper.
Users are unable to make LAN-to-LAN calls
Endpoints may not be registered with the gatekeeper.
Make sure that the endpoints have an online registration with the gatekeeper. Endpoints that are currently registered with the gatekeeper appear in the Zone Definition Table.
If an endpoint disconnects from the network inappropriately, its registration may appear until the gatekeeper issues a timeout. The MCU reregisters when it logs back onto the network.
 |
Note Some endpoints such as Microsoft NetMeeting version 2.x do not support the RAS protocol and cannot register dynamically with the embedded gatekeeper. In this case you have to predefine the endpoint in the embedded gatekeeper Zone DefinitionTtable and define it as "Online Always." |
Users from other zones cannot contact users registered with the embedded gatekeeper
The embedded gatekeeper may not have a zone prefix defined.
If your network is using zone prefixes, you must assign the embedded gatekeeper a zone prefix for users registered in other zones to dial local users.
To assign a zone prefix, perform the following steps:
Step 2 In the Select Unit dialog box, enter the IP address of the MCU that is being used to place the call.
Step 3 Click Next.
Step 4 Go to the Configuration Source window and select Gatekeeper.
Step 5 Click Service Definition.
Step 6 Select Zone prefix 1.
This predefined service allows you to assign the embedded gatekeeper a zone prefix.
Step 7 Click Edit. The Services Definitions window appears.
Step 8 In the Prefix field, enter the dialing prefix you want to assign to the embedded gatekeeper.
Step 9 Set the zone access parameter as follows:
Step 10 Click OK.
Posted: Wed Sep 20 09:14:07 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.