TELES ECOTEL - ISDN Port Not Loaded Correctly; Not Active

TROUBLESHOOTING
CHAPTER 15
245
ECOTEL 3G 16.1. Revised: 1 March 2011.
Solution
 In the
pabx.cfg, check the configuration of the RemoteCode parameter. If, for instance, the
configuration is
RemoteCode=BBB, BBB is defined as the dial-in prefix for ISDN remote access.
 Check the
route.cfg file for a matching mapping of an ISDN dial-in number. The mapping that matches
the above
RemoteCode parameter is MapAll<num>=BBB DATA whereby <num> is the ISDN dial-
in number.
 Ensure that you use the correct ISDN dial-in number format (i.e. trunk number plus extension or extension
only) by changing the above mapping to the following catch-all parameter:
MapAll?=BBB DATA and
by tracing the routing attempt. The trace file tells you the correct number format. Adjust the mapping
accordingly.
 Make sure that your ISDN dial-in number is not used for any other data routings by taking the same steps
as above: change the mapping to
MapAll?=BBB DATA, trace the routing attempt and adjust the
mapping according to your findings.
15.1.6 ISDN PORT NOT LOADED CORRECTLY / NOT ACTIVE
Another two issues that can inhibit ISDN remote access relate to the ISDN interface.
Reasons
 The TE or NT port configurations in the
pabx.cfg file are missing or wrong.
 The ISDN cable pin assignment is wrong.
Symptoms
 The system cannot be accessed from remote using ISDN.
 No calls are possible.
Solution
 Use GateManager to verify if the ISDN ports have been loaded correctly by going to the port status and
checking the entry in the Layer 2 column. If the entry says “MFE” (Multiframe established), this ISDN port
has been loaded correctly.
 If a port has not been loaded correctly, open
pabx.cfg and check the port entries in the Controller
/Subscriber entries. Pay particular attention to the correct connection type. A matching example is for
instance
Controller00=20 TES2M DSS1 and Controller01=21 NTS2M DSS1 with
Controller00 being the PRI TE terminal endpoint (connecting to PSTN) and Controller01 being
the matching PRI NT network termination port (connecting to the PBX). Please refer to Table 5.13,
“pabx.cfg: Controller Parameters” on page 58 and Table 5.15, “pabx.cfg: Subscriber Parameters” on
page 61 for an explanation.
 To make sure that there is no problem with the wiring, check the ISDN cable pin assignment. You can do
so by looking at the cable colors or by using a cable tester. Please refer to chapter 4.4.2 on page 26 for
the correct pin assignment.