|
|
This chapter discusses problems that can occur configuring the Cisco IP/VC
3530 VTA, and suggests actions you can take to solve these problems. The topics include the following:
This section describes what you can do if an LED does not light.
The VTA may not be properly connected to the power source:
The LAN port is not connected to the network:
This section lists problem symptoms that can occur with the VTA and suggests actions you can take to resolve them.
The room system is unable to place a call:
Callers are not able to get through to the room system:
The VTA did not drop the session properly after the previous call:
These problems usually indicate a poor network connection:
This section describes advanced procedures you can use if VTA problems persist.
You can use the ping command to determine whether the VTA is communicating with the network and to assess network connectivity. You can issue a ping command from a Windows PC to a VTA.
To issue a ping command from a Windows PC, perform the following steps:
Step 2 At the prompt, type ping VTA IP address.
Where VTA IP address is the IP address of the VTA you want to check.
Step 3 If a series of "Reply from VTA IP address" messages appears on the screen, the VTA is connected. Type Exit and press Enter to close the window.
Step 4 If timeout messages appear on the screen, the VTA is not connected. Perform the following steps:
a. Check the physical connection between the VTA and the LAN. Make sure that the cable is securely plugged into the correct jacks and that the cable is good.
b. Verify the VTA IP address.
c. Send another ping command. If the second ping command is also unsuccessful, you must redefine the VTA IP address.
d. Type Exit and press Enter to close the window.
Step 5 If the VTA successfully responds to the ping command but the time it takes to respond greatly varies, there is likely a problem with the network. Type Exit and press Enter to close the window.
You can configure two VTA devices to communicate with each other directly to learn where there is a problem with the gatekeeper. We refer to the VTA devices as VTA 1 and VTA 2. To set up two VTA devices to directly communicate and to test whether the gatekeeper is working properly, perform the following steps:
Step 2 Configure the VTA devices to point to each other:
a. Launch the Cisco IP/VC Configuration Utility on a PC and select or specify the IP address of VTA 1 for configuration.
b. Advance to the Network Parameters dialog box and replace the Default Gatekeeper ID with the address of VTA 2.
c. Save and transfer this configuration.
Step 3 Repeat for VTA 2 Step 1 and Step 2 using the VTA 1 IP address to replace the Default Gatekeeper ID.
Step 4 Place a call from one VTA device to the other.
To further isolate whether the problem is within the VTA equipment, perform the following steps.
 |
Note We refer to the VTA devices as VTA 1 and VTA 2. |
Step 2 Configure the VTA devices to point to each other:
a. Launch the Cisco IP/VC Configuration Utility on a PC and select or specify the IP address of VTA 1 for configuration.
b. Advance to the Network Parameters dialog box and replace the Default Gatekeeper ID with the address of VTA 2.
c. Save and transfer this configuration
Step 3 Repeat for VTA 2 Step 1 and Step 2 using the VTA 1 IP address to replace the Default Gatekeeper ID.
Step 4 Place a call from one VTA device to the other.
If problems disappear on the local segment but return as soon as you involve the larger network, the problem may be in the network itself. There are several tests you can run to troubleshoot problems between remote sites, even if you are unable to test local videoconferences.
Step 2 Try the videoconference at different times of day. Because network use varies over a 24-hour period, videoconferences may work better at some times of day than others. If you find a videoconference works well during "off" hours such as early morning, but fails at busy times (typically late morning or midafternoon), the network is suspect.
Step 3 Try a network route that has fewer router hops, such as across a leased line or an alternate Internet service provider. To determine the number of router hopes, run a traceroute (tracer Ipaddr command on a PC, tr Ipaddr command on a UNIX system). If the videoconference behaves better on a connection with fewer routers, the network is at fault.
You can access the VTA through a Telnet session or through the serial port. You can use Telnet or the serial port to monitor dynamic VTA activity. You also can use the serial port to view the VTA parameters and to manipulate configuration. This section describes how you can access the VTA through Telnet and the serial port, and describes the parameters you can view and manipulate through the serial port.
You can monitor VTA activity through Telnet. Telnet sessions can be a helpful debug tool when you are working with a Cisco technician. To start a VTA Telnet session, perform the following steps:
Step 2 In the Open field, type telnet VTA IP address.
Step 3 Click OK. The Telnet window appears.
Step 4 At the login prompt, type the name required to log in to the VTA. The default name is admin.
You can use the VTA Serial Port on the front panel to monitor VTA activity, to view VTA parameters, and to manipulate VTA configuration. You can connect the VTA directly to the computer serial port or through a modem. This section describes the serial port options.
To connect the VTA Serial Port directly to a computer, perform the following steps:
Step 2 Connect the 9-pin female connector (PC) to the serial port (COM 1) on a PC.
Step 3 Start the terminal emulation software.
Step 4 Set the terminal emulator configuration parameters to the following values:
Step 5 Click OK.
To connect a remote VTA Serial Port to a computer via modem, perform the following steps:
Step 2 Make sure that the computer and modem you are using can communicate with each other. Refer to the computer and the modem documentation respectively to ensure that the parameters are correctly set to connect a call.
Step 3 Connect the Terminal/Modem cable to the VTA Serial Port and an external modem. The connector on the cable marked Unit attaches to the VTA Serial Port and the connector marked Modem connects to the modem. If your modem does not accept the cable modem connector, obtain a null cable with the connectors you need. See the "Cable Connectors and Pinouts" appendix to view the pinout of the Terminal/Modem cable, which is a null cable.
Step 4 Launch the terminal emulator utility on the computer and dial the modem number.
To monitor the VTA through the serial port, connect the VTA to a computer through the serial port as described in the "Accessing the VTA Through the Serial Port" earlier in this chapter. If the VTA is currently running, the monitoring session will begin automatically. Otherwise, the monitoring session will begin after the VTA is turned on.
Posted: Mon Jun 5 13:36:34 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.