|
Introduction (general & T1 specific)
The VTEL VTC may need rebooting for a variety of reasons. Before rebooting the
VTEL codec PC, try verifying that the problem is really with the codec and not
something else. The codec PC is located in the same machine room (557A) as
the Intel compute cluster along the shared wall with 551a in the VTC rack.
The console for the codec PC is in 551a. On the monitor, see if you get a
cursor when you move the mouse, and then right click to see if a menu
appears.
Right click/select the call/disconnect option and see if the codec is in
an active call. If connecting to a call fails,
go to the VTC rack in machine room. At eye level, there is a
one-rack-unit tall box that is a VX Encore T1 DSU/CSU. This is our T1
interface box and if everything is up then port 1&2 will have six LED’s
lit, and the EFS should be ~100%. If the codec is not communicating via the
DSU/CSU, then some of the LEDs on port 1 will be out. This is true both
when there may be a problem with the T1 and when connections are made via
the LAN (H.323). If all the LED’s are on and the T1 interface is active, then
it is less likely that the codec is having a problem. Often the remote sites
broadcast black.
If the call will not connect or the Galaxy interface is not responsive, try
a soft system reboot. One can use ctrl-alt-delete to kill the Galaxy
software. Two consecutive ctrl-alt-delete's will reboot the Win98 system
host. Report all abnormal issues to video@graphics.cornell.edu.
Introduction (H.323 specific)
The LAN interface uses the H.323 protocol. For H.323 calls, the DSU/CSU
will have some of the port 1 LEDs out. Trouble shooting H.323 problems is
similar to finding problems with the local hosts network connection.
The VTEL dialing interface for LAN calls is the same as for WAN connections
other than which connection tab is chosen. Note that the VTEL host PC
runs W98 1st edition.
For a soft system reboot from the console
If the system can be rebooted via software, then perform a restart from
the start menu. This assumes that the connected conference has been
terminated. Otherwise the Galaxy software will prompt the user to
disconnect the conference.
Then follow the normal start sequence.
For a hard system reboot
If the VTEL console is unresponsive, where keyboard & mouse input yields
no response, then a reboot will be necessary. Remember to use the right
mouse button in the Galaxy software.
Push the hardware reset (LHS) on the codec PC. The CDROM light should
flicker, etc and the monitor in 551a should show a normal PC reboot sequence.
Normal start/restart sequence from the console.
-
Hit ESC on the PC at the login prompt.
- The PC automatically starts up the VTEL video conferencing software.
At the magenta screen, right click and choose call/hang up.
Pick the speed dial tab and double click
an appropriate destination.
Note that the direct connect WAN connection reports an ISDN
connection, vs. a T1 connection. This can be ignored.
- The system should now be connected and running normally with either
a T1 (WAN) or H.323 (Internet/LAN) connection.
PcANYWHERE
Optionally PcANYWHERE32 server service can be launched by right clicking
and choosing the
extras menu. From the extras, choose
Utilities/WINAW32. The PcANYWHERE connection daemon is listed
as stc02 and double click it to launch the daemon. This
will allow remote access of the VTEL codec PC.
Other VTC system problems
For any required reboots or other problems send mail to
video@graphics.cornell.edu
|
