Lucent Technologies Remote Port Security Device Users Guide

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-3 Access Failure Messages. 
5
2 No Response No response 
was returned 
from the RPSD 
Key when the 
RPSD Lock 
sent the 
challenge.Test the RPSD Lock by using 
the Self-Check test 
described in “Testing the 
RPSD Lock” on page 5-6
. If 
the Lock tests okay, 
substitute a touch-tone 
telephone for the RPSD Lock, 
and run the Last Call Status 
Test described on page 5-7
 
to obtain any status 
information the Lock may 
have generated and to 
determine if the problem is 
with the CO line. If the CO 
line is okay, escalate the 
trouble to the next level of 
service.
3 Invalid User ID The RPSD Key 
user ID is not in 
the table of 
users on the 
RPSD Lock.Add the Key user to the user 
table if it is someone you 
want to have access to the 
RMATS channel. (This 
message may indicate an 
unauthorized attempt at 
access.) Check the Test 
Responses to make sure the 
RPSD Lock and RPSD Key 
Test Responses match. If 
access for this Key is desired 
and the Test Responses do 
not match, use the Wipe Out 
command (see Chapter 4, 
“Key Administration and 
Use”) to return the Key to an 
uninitialized state. Then use 
the Key initialization 
commands, also found in 
Chapter 4.
4 Block User The 
administrator 
placed a block 
on the caller’s 
Key user ID.No action necessary. This is 
a deliberate Block command 
issued by the administrator.
Table 5-1. Access Failure Messages — Continued
Code 
No. Message Meaning Action 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-4 Access Failure Messages. 
5
5 Invalid 
ResponseThe Key 
responded to 
the Lock’s 
challenge, but 
the response 
was incorrect.Check the Test Responses to 
make sure the RPSD Lock 
and RPSD Key Test 
Responses match. If access 
for this Key is desired and 
the Test Responses do not 
match, use the Wipe Out 
command (see Chapter 4, 
“Key Administration and 
Use”) to return the Key to an 
uninitialized state. Then use 
the Key initialization 
commands, also found in 
Chapter 4.
6 Outgoing  Call An outgoing call 
is being placed 
from the Lock. 
This is not 
proper usage, 
so the Lock 
disconnects 
the call.No action necessary. This is 
not a call failure.
7Ring - No 
AnswerThe Lock rang 
the modem, but 
the modem did 
not pick up.Run the Modem Ring test, 
described on page 5-8
, and 
follow the directions for 
determining the cause of 
failure.
8 Force 
DisconnectA Force 
Disconnect 
command was 
issued to the 
Lock.No action necessary. This is 
a deliberate disconnect 
command issued by the 
administrator.
Table 5-1. Access Failure Messages — Continued
Code 
No. Message Meaning Action 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-5 Access Failure Messages. 
5
9Time 
RestrictionThe call was 
placed during 
a time of day 
when the Lock 
is restricted 
from taking any 
calls.No action necessary. This is 
a deliberate restriction 
placed on access to the Lock 
by the administrator. If you 
must have access at this 
time, contact the system 
administrator. The 
administrator may bypass 
the time restriction in one of 
the following ways: removing 
the time restriction on that 
Key user, or using the  Force 
Connect Command. See 
Chapter 3 for instructions on 
removing time restrictions or 
using the Force Connect 
command.
Table 5-1. Access Failure Messages — Continued
Code 
No. Message Meaning Action 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-6 Testing the RPSD Lock 
5
Testing the RPSD Lock
There are two ways you can test the RPSD Lock to determine the cause of 
access failures and the malfunctioning of the Lock or some associated piece of 
hardware:
nBuilt-in diagnostics
nHardware replacement
NOTE:
When a connection fails and the caller must get into the RMATS channel, 
the system administrator can permit the access by using the Force 
Connect command. See Chapter 3 for more information on the Force 
Connect command.
Both of these methods require a touch-tone telephone, the first to dial into the 
Lock and perform the diagnostics, the second to physically replace various 
pieces of hardware.
Built-in Diagnostics
The RPSD system provides three diagnostic tests which are used to determine 
the cause of access failures. These are:
nSelf-Check test
nLast Call Status test
nModem Ring test
All three tests are performed by dialing the RMATS channel from a touch-tone 
telephone and entering a code for the test you want by using the phone pad. The 
RPSD Lock responds to the code by issuing a tone or set of tones, which are 
then interpreted to determine the cause of call failure.
Self-Check Test
The Self-Check test checks the health of the RPSD Lock. Follow these steps to 
perform the Self-Check test:
1. Dial the RMATS channel from a touch-tone telephone.
When the call is answered, you hear a short tone (indicating a 
connection to the RPSD Lock).
2. Press 1 Q on the telephone pad. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-7 Testing the RPSD Lock 
5
If the response is three quick tones followed by the RPSD Lock disconnecting, 
the Lock is functioning properly. The Lock also generates a status message 
similar to the following:
999 08/14/90 16:21:34 Remote Test 1 (Self Check) Completed OK
If the response is anything but three quick tones, the Lock is not functioning 
properly.
Run the Modem Ring Test next no matter what the Lock’s response. If a Lock is 
functioning properly, the Modem Ring Test serves as a backup check on the 
Lock. If a Lock is malfunctioning, the Modem Ring Test will further diagnose the 
problem.
Last Call Status Test
The Last Call Status Test provides the call outcome for the last call attempt to the 
Lock. The test responds either with slow beeps, the number of which 
corresponds to the nine status messages explained in Table 5-1, or three fast 
beeps, which means that the last call attempt was successful.
Follow these steps to perform the Last Call Status Test:
1. Dial the RMATS channel from a touch-tone telephone.
When the call is answered, you will hear a tone indicating a connection 
to the RPSD Lock.
2. Press 2 Q on the telephone pad.
You will hear three fast beeps if the last call attempt was successful, or between 
one and nine slow beeps if the last call attempt was unsuccessful. Count the 
number of slow beeps. The number of slow beeps corresponds to the access 
failure message number. Table 5-1 explains each of the nine access failure 
messages and the appropriate action to take.
The RPSD Lock also generates a status message similar to the following:
103 08/14/90 16:21:34 Remote Test 2 (Last Call Status) Completed OK 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-8 Testing the RPSD Lock 
5
Modem Ring Test
The Modem Ring Test tells you whether the call attempts are getting through to 
the modem. If there is a problem with the Lock, the communications system 
modem, or the cabling, the call will not reach the modem. Instead you will 
probably get a Ring No Answer message.
Follow these steps to perform the Modem Ring Test:
1. Dial the RMATS channel from a touch-tone telephone.
When the call is answered, you will hear a tone indicating a connection 
to the RPSD Lock.
2. Press 3 Q on the telephone pad.
The RPSD Lock responds to the command by ringing the modem. While the Lock 
rings the modem, you hear a simulated ring on the telephone receiver. When the 
modem picks up, you hear the answer tone. The answer tone will not last long 
enough for the modem to perform handshaking. The Lock then sends three quick 
beeps to your telephone and disconnects the call.
The RPSD Lock also generates a status message similar to the following:
104 08/14/90 16:21:34 Remote Test 3 (Modem Ring) Completed OK
If you do not hear the answer tone, the problem may be the Lock, the 
communications system modem, or the cabling. Next, check the equipment by 
physically replacing the hardware. See “Hardware Replacement” on page 5-9
 for 
procedures. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-9 Testing the RPSD Lock 
5
Hardware Replacement
The built-in diagnostics of the RPSD Lock may indicate that there is a hardware 
failure, but they will not necessarily determine whether that failure is in the CO 
line, RPSD Lock, communications system modem, or caller’s equipment or lines. 
To determine where the failure is occurring, replace individual components of the 
hardware with a touch-tone telephone. The following sections describe the 
procedure for such replacement in the order you should perform it.
NOTE:
The modem for the System 75 and DEFINITY Generic is internal to the 
communications system and located on the circuit board. The modem for 
the System 85 and DEFINITY Generic 2 is external to the communications 
system.
Replacing the Communications System Modem
To test whether the problem diagnosed by the Modem Ring Test is in the 
communications system modem, follow these steps:
1. Disconnect the modular telephone plug from the communications system 
modem, and connect a touch-tone telephone to the modem.
2. Call the RMATS channel from another touch-tone telephone, and perform 
the Modem Ring Test described on page 5-8
.
3. If the phone you substituted for the modem rings, have someone answer 
it. If the connection is fine, the problem is in the modem. If the system still 
malfunctions, go to Step 4.
4. Remove the touch-tone telephone and reconnect the modem, but this time 
use a different cable between the Lock and the modem. Call the modem 
again from a telephone.
5. If the system functions properly, the problem is in the cable. If the system 
still malfunctions, go to Step 6.
6. Remove the substitute cable, and put the original back. Disconnect the 
Lock from the CO line, and replace the Lock with a touch-tone telephone. 
Call the RMATS channel from a second telephone.
7. If the telephone you substituted for the Lock rings, answer it. If the  phones 
work properly, the problem is in the Lock. Replace the Lock. See 
“Replacing the RPSD Lock or Key” on page 5-10
. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-10 Replacing the RPSD Lock or Key 
5
Replacing the RPSD Lock or Key
If an RPSD Lock must be replaced, the service call is classified as the highest 
priority because a failed Lock prevents all access to or from the RMATS channel. 
You may remove the RPSD Lock from the line and, to maintain access to the 
RMATS channel,  connect the modem directly to the CO line. (Do this only if the 
Force Connect command fails as well. See Chapter 3 for further information on 
the Force Connect command.) 
!Security Alert:
Without the Lock, the line is not secure.
Lucent Technologies technicians should consider a failed Lock or Key a Severity 
4 trouble.
Customers can replace the unit themselves by contacting the National Parts 
Sales Center (NPSC). The number for the NPSC is 1 800 ATT-PART. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-11 Saving the Key Seed Value 
5
Saving the Key Seed Value
Save all of the secret information used to initialize the RPSD Lock in a secure 
location. If a Lock needs to be replaced, you will want to initialize the 
replacement Lock with the same information as the original. 
!Security Alert:
Save the secret information in a secure location to maintain the security of 
the system. If the security of the Seed Value is breached, RPSD security 
itself is lost. The RPSD Lock and Key should be reinitialized with a new 
secret key.
NOTE:
The RPSD Secret Key Seed Value must be physically protected and 
secured. Lucent Technologies makes no claim or guarantee for protection 
or security provided by the RPSD. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Troubleshooting 
Page 5-12 Saving the Key Seed Value 
5