Allied Telesis AR300 series Troubleshooting Manual
Troubleshooting isdn connections
Hide thumbs
Also See for AR300 series:
- Quick install manual (9 pages) ,
- Hardware reference manual (111 pages) ,
- Release manual (36 pages)
Advertisement
How To |
Troubleshoot ISDN Connections
Introduction
Ideally, setting up an ISDN connection is very much a straightforward process:
Connect the router to the ISDN network interface.
Configure ISDN call definitions on the router. See How To Configure ISDN Calls On Allied
Telesis Routers, available from www.alliedtelesis.com/resources/literature/howto.aspx.
Send traffic.
However, for one reason or another, there are occasions when the setup process is not as
smooth as it should be.
So if you have set up your router to communicate over ISDN, but the setup does not appear
to be working, this How To Note contains some steps you can take to try and resolve the
problem.
Which products does it apply to?
This configuration applies to the following Allied Telesis routers and switches, when a BRI or
PRI interface is installed in the base unit or through a PIC:
AR300 series routers
AR400 series routers
AR700 series routers
Rapier series switches
Rapier i series switches
Related How To Notes
You also may find the following How To Notes useful:
How To Configure ISDN Calls On Allied Telesis Routers
How To Configure Common ISDN Access Concentration With The Firewall
How To Notes are available from www.alliedtelesis.com/resources/literature/howto.aspx.
C613-16030-00 REV B
www.alliedtelesis.com
Advertisement
Table of Contents
Related Manuals for Allied Telesis AR300 series
Summary of Contents for Allied Telesis AR300 series
- Page 1 How To Note contains some steps you can take to try and resolve the problem. Which products does it apply to? This configuration applies to the following Allied Telesis routers and switches, when a BRI or PRI interface is installed in the base unit or through a PIC: AR300 series routers...
- Page 2 How to troubleshoot ISDN Step 1: Is the router communicating with the ISDN network at the signalling level? When the router is connected to the ISDN network, either by plugging it into an NT1 if the router has an S/T interface, or by plugging it directly into the ISDN network if the router has a U interface, it establishes a low-level connection to the network.
- Page 3 If the interface is not activated, the reason could be one of the following: The interface has been put into NT mode. On the AT-AR041 and AT-AR042 multi-BRI NSM modules it is possible to put the ISDN interface(s) into NT mode so that they can emulate a network switch interface. This can be useful for bench testing network configurations.
- Page 4 The cable connecting the router to the ISDN network or NTI is faulty. Try a different cable. There is a fault in the ISDN network or the NT1. If options 1, 2 and 3 do not show any faults on the router, then contact your ISDN network provider and see if they can find the fault on their network.
- Page 5 If the LAPD is not alive, the reason could be one of the following: The TEI mode has been set incorrectly. On a Basic Rate interface, the TEI mode ought to be automatic, so that the router does not mandate a TEI value to the switch, but will automatically accept whatever value is assigned by the switch.
- Page 6 If the call seems to be being disconnected for other reasons at the PPP or IP level, then it would probably be necessary for you to contact your Allied Telesis reseller or distributor for technical assistance. The Cause column The Cause column tells you why a call was disconnected.
- Page 7 For a full discussion of call identification using fields of the call setup packet, see How To Configure ISDN Calls On Allied Telesis Routers, available from literature/howto.aspx.
- Page 8 There is an ISDN call definition on the receiving router that will accept the incoming call, but there is not yet a Layer 2 interface (PPP or Frame Relay) configured to use this call definition. There is an ISDN call definition on the receiving router that will accept the incoming call, and there is a Layer 2 interface configured over the call definition, but this particular call definition is already taken by another incoming call.
Need help?
Do you have a question about the AR300 series and is the answer not in the manual?
Questions and answers