Toshiba Strata AirLink, Installation Manual

Page: 94 / 117

Maintenance and Troubleshooting
Troubleshooting
84
Strata AirLink Installation Guide 5/00
Handset
Table 25 lists handset symptoms and possible solutions.
Table 25 Handset Troubleshooting
Symptoms Possible Solution
Called party can hear but
cannot be heard.
Conversation broken up.
Handoff clicks occur during
conversation.
The handset signal strength is inadequate. Try moving closer to a Base
Station. If the problem is reported by many users, try moving the Base
Station to a location that provides better coverage.
For best results the signal strength icon should show three to five bars.
The (BER) test should report Good or Max results. See BER testing on
Page 16 for instructions on how to perform this test.
Display does not contain date,
time and signal strength.
The handset is not locked onto a Base Station. Try powering off and on
or moving to another location closer to a Base Station.
Note It may take up to a minute for the full display to appear.
If the problem persists, check system and handset ID configuration.
These symptoms could also occur if the BSIA, RWIU, or Base Station is
being reset.
Off-hook icon ( ) flashes
when
&$//
is pressed;
Handset operated correctly and
now cannot make calls.
The handset ESN is improperly configured. Fix this problem by:
1. Reprogramming the handset with proper system and handset IDs.
2. Changing the handset ID configured for the handset to any valid ID
not already in use.
3. Changing the handset ID in the User Database to match the ID
programmed in the handset.
4. Making a call on the handset to store its ESN in the BSIA or RWIU.
5. Installing the ALM.
6. Performing a maintenance check (system maintenance busy) and
loop start line status is activated.
Invalid ESN reported for
handset (alarm).
The same handset ID and system ID were programmed into two
telephones and databases, and the handset ESNs were associated with
the wrong analog line when the first telephone call was made. Fix this
problem by:
1. Locating both handsets and correcting the databases.
2. Checking the handset ID configuration in both handsets to make
sure they are correct.
3. Changing the ID in the handset and making another call (corrects
the ESN configuration for that handset).
4. Correcting the configuration for the handset that reported the invalid
ESN. Follow these steps:
●
Open the User Database and change the handset ID configured
for the handset to any valid ID not already in use.
●
Change the handset ID in the User Database to match the ID
programmed in the handset.
●
Make a call on the handset to store its ESN.