Cisco 700 Series ISDN Access Routers

This document addresses Cisco 700 connectivity problems. This document covers connection problems that relate to these questions:

A. Issue the show status command. The output looks similar to this:

cisco> show status
	Status    01/01/1995 00:00:09
	Line Status
	Line Activated
	Terminal Identifier Assigned
	Port Status                         
	Interface Connection Link
	Ch:  1      Waiting for Call
	Ch:  2      Waiting for Call

If the output shows Line Deactivated, Terminal Identifier Unassigned, or SPID Rejected, then you have an ISDN problem. Call your local ISDN provider or Telco and ask these questions:

• Do I have the correct ISDN switch type in my router?

• What are my Service Profile Identifiers (SPIDs)?

• Am I provisioned for data, voice, or both?

If you have the correct ISDN switch type and SPIDs in your router, then the switch of your ISDN provider might be malfunctioning.

A. This is probably an authentication issue. Complete these steps:

1. Make sure your router and remote router run the same type of authentication (if any).
   1. Issue a command in your Cisco 700 (most people use Challenge Handshake Authentication Protocol (CHAP) in order to check authentication. You see this output at the system/root level of your router:

      set ppp authentication in chap

   2. Then, look at the WAN user profile you created to dial out to the remote router. You see this output:

      set ppp authentication out chap

2. Make sure that the passwords on both routers match exactly, which includes upper case and lower case letters.

   Note: The password is encrypted.

   At the system level, you see this output:

   set ppp secret client

   At your WAN User Profile, you see this output:

   set ppp secret host

3. Complete these steps if your link still refuses to maintain a good connection:
   1. Go into your WAN User Profile.
   2. Issue the diag ppp on command.
   3. Enter ca 1 in order to place a call. Look at the PPP diagnostics. You should be able to follow them as your routers trade configuration information back and forth. Look for the line that shows Line Disconnected. What do the lines immediately above this line show? These lines might reveal why the line was dropped.

A. Complete these steps:

1. Look at your WAN User Profile. Do you have routing turned on? Issue the set ip routing on command. Check this on your remote router as well.
2. Answer these questions:

   1. Do you have any static routes in your WAN User Profile?

   2. Where do they direct the traffic?

   3. Do each of your routers know how and where to return a ping?

   You have a statement similar to this in your configuration:

   set ip route destination X.X.X.X /X gateway X.X.X.X

   Where destination is either 0.0.0.0 (which means anywhere), the IP address of a remote interface, or an IP address of a remote network. The information after the / denotes how many bits designate the network portion of the address (Mask Bits). Here are three examples:

   set ip route destination 0.0.0.0/0 gateway 10.1.1.1

   10.1.1.1 is the IP address of the remote router BRI.

   set ip route destination 50.125.78.2/32 gateway 10.1.1.1

   50.125.78.2/32 designates a specific IP address on a remote network.

   set ip route destination 134.56.0.0/16 gateway 10.1.1.1

   134.56.0.0/16 designates a remote network address.
3. Make sure you have some type of routing statement in your remote router, preferably in the BRI interface (or WAN User Profile if you use another Cisco 700).