TELES ECOTEL - ISDN Access: Dial-In Number Missing or Wrong

TROUBLESHOOTING
CHAPTER 15
244
ECOTEL 3G 16.1. Revised: 1 March 2011.
Symptoms
 The gateway cannot be accessed from remote.
 There is ethernet activity on the gateway.
 Ping works if you connect directly to the gateway.
 The gateway can be accessed via GateManager if you connect directly to the gateway.
Solution
 Make sure there is ethernet activity by checking the ethernet port LEDs (please see Chapter 4.7 on
page 27  . If the LED that indicates data traffic is not blinking, the ethernet cable is probably defect.
Please replace the cable and check whether this solves your problem.
 If the problem persists, connect your computer directly to the gateway using a crossover cable. Make sure
your computer uses the same IP range as your gateway.
 Send a Ping from your computer to the gateway and wait for the corresponding ICMP echo to make sure
that the system can be accessed using ICMP.
 From the connected computer, use GateManager to access the system and make sure that this access is
working as well.
 If steps 1 to 4 are working, most likely a firewall or NAT / PAT issue is causing the connection problem.
Check your firewall or NAT / PAT settings and adjust them to let traffic pass through to your system.
15.1.5 ISDN ACCESS: DIAL-IN NUMBER MISSING OR WRONG
In systems with a BRI / PRI interface, ISDN access can be impaired due to faulty or missing configurations of dial-
in numbers.
Reasons
 The configuration of the
RemoteCode parameter in the pabx.cfg is missing or does not match the
corresponding dial-in number mapping in the
route.cfg.
 There is no route configured for the ISDN dial-in number in the
route.cfg .
 The ISDN dial-in number was configured in the
route.cfg using the wrong number format (i.e. the
trunk number or extension are missing).
 The ISDN dial-in number that has been configured in the
route.cfg is used for other data routings as
well.
Symptoms
 The system cannot be accessed from remote using ISDN.