Avaya G3PBX Manual Do Utilizador
Troubleshooting
Issue 1 — December 2002
DEFNETM.PDF — Avaya CT 1.2
4-4
Switch Link "Talking" But Not In Service
(Authentication Failed for ADJLK Connection)
(Authentication Failed for ADJLK Connection)
The "
Talking
" state of the link connection does not necessarily mean that the
link is in service and can accept requests.
1. To verify that the link is in service, on the DEFINITY G3PD Administrator
utility’s Link Status screen, the "Switch Version" field should have the
correct version of the switch. See the ‘‘Link Status Command’’ section in
Chapter 3.
correct version of the switch. See the ‘‘Link Status Command’’ section in
Chapter 3.
2. You can also use the DEFINITY G3PD Administrator utility’s Test
command; the "More Info" field should indicate if the heartbeat with the
switch was successful. See the ‘‘Test Command’’ section in Chapter 3.
switch was successful. See the ‘‘Test Command’’ section in Chapter 3.
3. You can also try recycling the station; busy out and release the BRI port
associated with the link.
4. If the problem persists, contact Services.
Clients Cannot See Advertised PBX Driver
(G3PD Not Visible to DEFINITY G3PD
Administrator Utility)
(G3PD Not Visible to DEFINITY G3PD
Administrator Utility)
1. From the TSM32, choose the "Driver DLL Information" option to verify
that the driver is loaded. If it is not in the list or not loaded, try to load it. If
this fails, refer to the problem description ‘‘G3PD Not Starting’’.
this fails, refer to the problem description ‘‘G3PD Not Starting’’.
2. Verify that TCP/IP is running on the client. To verify network connectivity
and ensure that you can communicate with the Tserver, use the ping
command to ping the Tserver from the client.
command to ping the Tserver from the client.
3. If you are migrating to Telephony Services for Windows NT from Telephony
Services for NetWare, check that you have the correct version of software
for the client libraries. Only the client libraries provided on the Telephony
Services for Windows CD-ROM will be able to connect to a Windows NT
Tserver.
for the client libraries. Only the client libraries provided on the Telephony
Services for Windows CD-ROM will be able to connect to a Windows NT
Tserver.
4. Check that the TSLIB.INI includes the IP address of the Tserver; refer to
Avaya Computer Telephony Installation Guide.
If your TSLIB.INI file contains host names rather than IP addresses, verify
that host name resolution is operational from the client. (Use the command
that host name resolution is operational from the client. (Use the command
ping <hostname>
to verify.)
5. If the driver is loaded, run the TSM32 and choose the "Tlink Information"
option to verify that the driver is registered with the Tserver. If the Tlink
name is not in the list or it is not registered, view the Tserver error log for
more information. If the problem still exists, check a different client to see if
the problem is with the G3PD or Tserver, or with the client itself.
name is not in the list or it is not registered, view the Tserver error log for
more information. If the problem still exists, check a different client to see if
the problem is with the G3PD or Tserver, or with the client itself.