Specifications

TROUBLESHOOTING LBI-39000B

8.2. UNABLE TO MAKE CALLS AFTER SYSTEM MANAGER CONNECTED

Problem: Unable to make inbound/outbound calls after connecting the System Manager.

Solution: Use the dbv command to ensure that the database is set up correctly. Please refer to LBI-39040 for a discussion

of the dbv command. The LID/GID must be inbound/outbound enabled and valid.

8.3. TOLL CALL RESTRICTIONS DO NOT APPEAR TO BE CORRECT

Problem: Toll call restrictions do not appear to be correct.

Solution: Use the callres command to verify that tables are set up correctly and that there are no system errors. Phone

numbers can be tested to ensure that they are allowed/disallowed in the tables. Please refer to LBI-39040 for a

discussion of the callres command.

8.4. IMC-PI TRUNK IS NOT WORKING PROPERLY

Problem: The IMC-PI trunk is not working properly.

Solution: The WAN board loopback allows the user to verify whether the PI side of the link is functioning properly.

Connect J1 to J4 (port 0 to port 3) with a cable that swaps transmit and receive signals and clocks. (See

Appendix A for cable specifications.) Use the stat command to verify that the link is up. The link should be

backed up on the order of seconds. Please refer to LBI-39040 for a discussion of the stat command. If the link

does not come up, either the loopback cable is incorrect or the WAN board needs to be swapped.

8.5. LOSE INTERCONNECT AFTER MD110-PI CABLE HAS BEEN RECONNECTED

Problem: Lose interconnect after the MD110-PI cable has been disconnected and reconnected. The PI detects no trunk

alarms. If incoming calls occur while the cable is disconnected, the MD110 will busy 1 channel for each call.

The PI disconnect reason code shown is CALLEE_BUSY_DISCONNECT. The problems presented in section

8.6 also occur.

Solution: Rebooting just the PI will not correct the problem. Restart the MD110 TLU-76/1 or TLU-77/1 using the

MD110 RFEXI command. Then, reboot the PI.

8.6. CALL NOT CONNECTING CORRECTLY AND NO TRUNK ALARMS

Problem: The call is not connecting correctly and the PI detects no trunk alarms.

Solution: Enable call logging by setting the PI CONFIG.DAT parameters DISK_LOG_CALLS and

DISK_LOG_STATES to true. Refer to the activity logging section in LBI-39040 for details on reading call

information and reason codes.

The problem discussed in section 8.5 has occurred on installations at numerous customer sites.

NOTE