Troubleshooting

Recovering a Lost Enable Password

Troubleshooting ISDN

Debug Commands

Telephone Interfaces

Troubleshooting

This chapter describes problems that could occur with the Cisco 800 series router software, reasons for the problems, and steps to solve the problems. The problems are grouped into the following areas:

Recovering a lost enable password
ISDN
Telephone interfaces

Before troubleshooting a software problem, you must connect a terminal or PC to the router via the light-blue Console port. (For information on making this connection, see the Cisco 800 Series Routers Hardware Installation Guide or the Cisco 811 and Cisco 813 Routers Hardware Installation Guide.) With a connected terminal or PC, you can read status messages from the router and enter commands to troubleshoot a problem.

As an alternative, you can remotely access the interface (Ethernet, ISDN, or telephone) by using Telnet. The Telnet option assumes that the interface is up and running.

For information on troubleshooting hardware problems, refer to the Cisco 800 Series Routers Hardware Installation Guide or the Cisco 811 and Cisco 813 Routers Hardware Installation Guide.

Recovering a Lost Enable Password

This section describes how to recover a password that you configured with the enable command (enable password).

Note You can recover a lost enable password but not a password that you configured with the enable secret command (enable secret password). This password is encrypted and must be replaced with a new enable secret password. See the "Hot Tips" section on Cisco Connection Online (CCO) for information on replacing enable secret passwords.

Follow these steps to recover a lost enable password:

Step 1 Connect an ASCII terminal or a PC running a terminal emulation program to the Console port. For more information, see the Cisco 800 Series Routers Hardware Installation Guide.

Step 2 Configure the terminal at 9600 baud, 8 data bits, no parity, and 1 stop bit.

Step 3 Reboot the router.

Step 4 From the user EXEC mode, display the existing configuration register value:

Router> show version

Step 5 Record the setting of the configuration register.

The setting is usually 0x2102 or 0x102.

Step 6 Record the break setting.

Break enabled---bit 8 is set to 0.
Break disabled (default setting)---bit 8 is set to 1.

Note To enable break, enter the config-register 0x01 global configuration command.

Step 7 Do one of the following:

If break is enabled, go to Step 8.
If break is disabled, turn the router off, wait 5 seconds, and turn it on again. Before the terminal displays Boot..., press Escape or Control-C. The terminal displays the ROM monitor prompt (boot#).
Go to Step 9.

Note Some terminal keyboards have a key labeled Break. If your keyboard does not have a Break key, refer to the documentation that came with the terminal for instructions on how to send a break.

Step 8 Send a break. The terminal displays the following prompt:

boot#

Step 9 Reset the configuration register:

boot# set ios-conf = 142

Step 10 Initialize the router:

boot# boot [flash]

The router cycles its power, and the configuration register is set to 0x142. The router uses the boot ROM system image, indicated by the system configuration dialog:

--- System Configuration Dialog ---

Step 11 Enter no in response to the prompts until the following message is displayed:

Press RETURN to get started!

Step 12 Press Return. The following prompt appears:

router>

Step 13 Enter privileged EXEC mode:

router> enable

The prompt changes to the privileged EXEC prompt:

router#

Step 14 Display the enable password in the configuration file:

router# show startup-config

Step 15 Enter configuration mode:

router# configure terminal

Step 16 Reset the configuration register:

router# config-register value

Specify the value that you recorded in Step 5 (usually 0x2102 or 0x102).

Step 17 Press Ctrl-Z to exit configuration mode.

Note To return to the configuration being used before recovering the lost enable password, do not save the configuration changes before rebooting the router.

Step 18 Reboot the router and enter the recovered password.

Troubleshooting ISDN

Table 9-1 describes symptoms that indicate problems with your ISDN line, possible problems your router might be experiencing, and solutions to solve the problems.

Table 9-1: Symptoms of ISDN Trouble

Symptom Possible Problem Solution

Your terminal or PC displays one of the following messages:

Channel Not Available Facility Not Subscribed
Wrong switch type or SPIDs. (North American telephone service providers only assign SPIDs.)

Disconnect any active ISDN calls and reset the ISDN BRI interface.

Contact your telephone service provider to verify your switch type and SPIDs.

Reconfigure the switch type and SPIDs if necessary.

Contact your telephone service provider to verify your ISDN line configuration.

Your router calls itself.

Software configuration error.

Check the settings of the dialer map dial-string and the SPIDs (North America only). The settings of these two parameters should not be the same. If the settings are the same, determine which setting is incorrect, and then reconfigure it.

Disconnect any active ISDN calls, and reset the ISDN BRI interface.

You cannot make an outgoing call.

Dialer-string configuration error.

Check the setting of the dialer map dial-string.

If the setting is incorrect, reconfigure it.

Disconnect any active ISDN calls, and reset the ISDN BRI interface.

SPID configuration error (North America only).

Check the setting of the SPIDs.

If the setting is incorrect, reconfigure it.

Disconnect any active ISDN calls, and reset the ISDN BRI interface.

The B channel is under operator control and does not respond to the router.

Contact your telephone service provider.

Your outgoing call is initially successful, but then it is rejected.

The number called is busy.

Try making the call later.

No link to the ISDN network.

A cable-related problem.

Refer to troubleshooting information in Cisco 800 Series Routers Hardware Installation Guide.

The BRI interface has shut down.

Restart the BRI interface.

Symptom	Possible Problem	Solution
Your terminal or PC displays one of the following messages: Channel Not Available Facility Not Subscribed	Wrong switch type or SPIDs. (North American telephone service providers only assign SPIDs.)	Disconnect any active ISDN calls and reset the ISDN BRI interface. Contact your telephone service provider to verify your switch type and SPIDs. Reconfigure the switch type and SPIDs if necessary. Contact your telephone service provider to verify your ISDN line configuration.
Your router calls itself.	Software configuration error.	Check the settings of the dialer map dial-string and the SPIDs (North America only). The settings of these two parameters should not be the same. If the settings are the same, determine which setting is incorrect, and then reconfigure it. Disconnect any active ISDN calls, and reset the ISDN BRI interface.
You cannot make an outgoing call.	Dialer-string configuration error.	Check the setting of the dialer map dial-string. If the setting is incorrect, reconfigure it. Disconnect any active ISDN calls, and reset the ISDN BRI interface.
	SPID configuration error (North America only).	Check the setting of the SPIDs. If the setting is incorrect, reconfigure it. Disconnect any active ISDN calls, and reset the ISDN BRI interface.
	The B channel is under operator control and does not respond to the router.	Contact your telephone service provider.
Your outgoing call is initially successful, but then it is rejected.	The number called is busy.	Try making the call later.
No link to the ISDN network.	A cable-related problem.	Refer to troubleshooting information in Cisco 800 Series Routers Hardware Installation Guide.
	The BRI interface has shut down.	Restart the BRI interface.

If the information in Table 9-1 does not help you solve your problem, you can enter several commands to further diagnose the problem. Refer to the "Debug Commands" section later in this chapter.

Debug Commands

This section discusses using debug commands to diagnose problems with your router. In general, Cisco recommends that you use these commands with the direction of your technical support representative. Using the debug commands can disrupt operation of the router when your internetwork is experiencing a high-load condition.

When you finish using a debug command, remember to disable it with the specific no debug command or with the no debug all command.

To minimize the impact of using debug commands, follow this procedure:

Step 1 Enter the following command from global configuration mode:

router (config)# no logging console

This command disables all logging to the terminal or PC that you are troubleshooting the software from. (To reenable logging, enter the global configuration mode logging console enable command.)

Step 2 To use the debug commands, do the following:

a. Access any router port remotely using Telnet, and enter the following command while in user EXEC mode:

router> enable

b. To show debug command output and error messages, enter the following command:

router> terminal monitor

: To disable logging on the virtual terminal, enter the following command:

router> terminal no monitor

c. Enter the desired debug commands.

Performing this procedure minimizes the load created because the console port no longer needs to generate character-by-character processor interrupts.

Table 9-2 describes debug commands, possible problems your router might be experiencing, and solutions to solve the problems. A output example from each command appears after the table.

Table 9-2: Troubleshooting ISDN

Command Possible Problem Solution

show isdn status
(user EXEC mode)

See output example 1, which appears after this table.

Improperly connected cable.

Refer to troubleshooting information in Cisco 800 Series Routers Hardware Installation Guide.

Damaged ISDN cable.

Order a new orange ISDN S/T cable (Cisco 801 or Cisco 803 routers) or a red ISDN U cable (Cisco 802 or Cisco 804 routers) from your Cisco reseller.

Replace the ISDN U cable that connects the NT1 to the ISDN wall jack. (You supplied this cable.)

Wrong switch type or SPID (North America only).

Contact your telephone service provider to verify your switch type and SPIDs.

Reconfigure the switch type and SPIDs if necessary.

Disconnect any active ISDN calls and reset the ISDN BRI interface.

Problem with ISDN line.

Connect an analog telephone to the ISDN jack. If you do not hear either a clicking noise, white noise, or light static, there is a problem with your ISDN line.

Contact your telephone service provider to report a problem.

If the problem continues after these steps, call your Cisco reseller.

Applies only if you have configured dial-on-demand routing (DDR).
show dialer
(user EXEC mode)

See output example 2, which appears after this table.

Software configuration error for Cisco 800 series router.

Check your router configuration, making sure there is a dialer-list, dialer-group, and dialer-map. Also, check the configuration of the destination dial-string to make sure it matches the actual dial-string. See the "Dial-on-Demand Routing Using Snapshot Routing" section in Chapter 4, "Configuring Advanced Networks," for information on configuring DDR.

Software configuration error for router connected to
Cisco 800 series router.

Check your router configuration. See the documentation that shipped with your router for more information.

Applies only if you have configured dial-on-demand routing (DDR).
debug dialer
(privileged EXEC mode)

See output example 3, which appears after this table.

Software configuration error for Cisco 800 series router.

Check your router configuration, making sure there is a dialer-map and dialer group. See the "Dial-on-Demand Routing Using Snapshot Routing" section in Chapter 4, "Configuring Advanced Networks," for information on configuring DDR.

show isdn status
(privileged EXEC mode)

See output example 4, which appears after this table.

Problem with SPIDs (North America only).

Contact your telephone service provider to verify SPIDs.

Reconfigure the SPIDs if necessary.

Disconnect any active ISDN calls and reset the ISDN BRI interface.

Terminal endpoint identifier (TEI) is not assigned.

Verify that TEI is assigned. Check the output for Layer 2 information, which will indicate if TEI is assigned.

Verify TEI assignment with telephone service provider.

debug isdn q931
(privileged EXEC mode)

See output example 5, which appears after this table.

Router connected to Cisco 800 series router does not answer call.

Contact your telephone service provider to verify your SPIDs (North America only).

Reconfigure the SPIDs, if necessary.

Disconnect any active ISDN calls, and reset the ISDN BRI interface.

Contact ISP or system administrator at the central office to verify the telephone number associated with their site.

Reconfigure the telephone number if necessary by using the dialer map command.

debug isdn q921 (privileged EXEC mode)

See output example 6, which appears after this table.

The router is sending IDREQs to the central office switch, but is not getting a response.

Contact your telephone service provider to verify your SPIDs (North America only).

Reconfigure the SPIDs if necessary.

Disconnect any active ISDN calls, and reset the ISDN BRI interface.

debug ppp negotiation, debug ppp authentication
(privileged EXEC mode)

See output example 7, which appears after this table.

PAP or CHAP authentication failed.

For PAP, check the settings of the PAP host name and password for correct spelling and use of uppercase and lowercase letters. If settings are incorrect, reconfigure them.

For CHAP, clear the existing host name and password. Reconfigure the host name and password.

Check the setting of the dialer map host name. If the setting is incorrect, reconfigure it.

debug isdn event, debug isdn q931
(privileged EXEC mode)

See output example 8, which appears after this table.

Call connected, but was later disconnected.

Enter the debug ppp negotiation and debug ppp chap commands. Check output to see if PPP negotiation and PPP authentication are successful. If PPP negotiation is unsuccessful, call your Cisco reseller. If PPP authentication is unsuccessful, do the following:

For PAP, check the settings of the PAP host name and password for correct spelling and use of uppercase and lowercase letters. If settings are incorrect, reconfigure them.

For CHAP, clear the existing host name and password. Reconfigure the host name and password.

debug isdn event, debug isdn q931
(privileged EXEC mode)

See output example 9, which appears after this table.

Wrong switch type.

Contact your telephone service provider to verify your switch type.

Reconfigure the switch type if necessary.

Disconnect any active ISDN calls and reset the ISDN BRI interface.

Command	Possible Problem	Solution
show isdn status (user EXEC mode) See output example 1, which appears after this table.	Improperly connected cable.	Refer to troubleshooting information in Cisco 800 Series Routers Hardware Installation Guide.
	Damaged ISDN cable.	Order a new orange ISDN S/T cable (Cisco 801 or Cisco 803 routers) or a red ISDN U cable (Cisco 802 or Cisco 804 routers) from your Cisco reseller. Replace the ISDN U cable that connects the NT1 to the ISDN wall jack. (You supplied this cable.)
	Wrong switch type or SPID (North America only).	Contact your telephone service provider to verify your switch type and SPIDs. Reconfigure the switch type and SPIDs if necessary. Disconnect any active ISDN calls and reset the ISDN BRI interface.
	Problem with ISDN line.	Connect an analog telephone to the ISDN jack. If you do not hear either a clicking noise, white noise, or light static, there is a problem with your ISDN line. Contact your telephone service provider to report a problem.
		If the problem continues after these steps, call your Cisco reseller.
Applies only if you have configured dial-on-demand routing (DDR). show dialer (user EXEC mode) See output example 2, which appears after this table.	Software configuration error for Cisco 800 series router.	Check your router configuration, making sure there is a dialer-list, dialer-group, and dialer-map. Also, check the configuration of the destination dial-string to make sure it matches the actual dial-string. See the "Dial-on-Demand Routing Using Snapshot Routing" section in Chapter 4, "Configuring Advanced Networks," for information on configuring DDR.
	Software configuration error for router connected to Cisco 800 series router.	Check your router configuration. See the documentation that shipped with your router for more information.
Applies only if you have configured dial-on-demand routing (DDR). debug dialer (privileged EXEC mode) See output example 3, which appears after this table.	Software configuration error for Cisco 800 series router.	Check your router configuration, making sure there is a dialer-map and dialer group. See the "Dial-on-Demand Routing Using Snapshot Routing" section in Chapter 4, "Configuring Advanced Networks," for information on configuring DDR.
show isdn status (privileged EXEC mode) See output example 4, which appears after this table.	Problem with SPIDs (North America only).	Contact your telephone service provider to verify SPIDs. Reconfigure the SPIDs if necessary. Disconnect any active ISDN calls and reset the ISDN BRI interface.
	Terminal endpoint identifier (TEI) is not assigned.	Verify that TEI is assigned. Check the output for Layer 2 information, which will indicate if TEI is assigned. Verify TEI assignment with telephone service provider.
debug isdn q931 (privileged EXEC mode) See output example 5, which appears after this table.	Router connected to Cisco 800 series router does not answer call.	Contact your telephone service provider to verify your SPIDs (North America only). Reconfigure the SPIDs, if necessary. Disconnect any active ISDN calls, and reset the ISDN BRI interface.
		Contact ISP or system administrator at the central office to verify the telephone number associated with their site. Reconfigure the telephone number if necessary by using the dialer map command.
debug isdn q921 (privileged EXEC mode) See output example 6, which appears after this table.	The router is sending IDREQs to the central office switch, but is not getting a response.	Contact your telephone service provider to verify your SPIDs (North America only). Reconfigure the SPIDs if necessary. Disconnect any active ISDN calls, and reset the ISDN BRI interface.
debug ppp negotiation, debug ppp authentication (privileged EXEC mode) See output example 7, which appears after this table.	PAP or CHAP authentication failed.	For PAP, check the settings of the PAP host name and password for correct spelling and use of uppercase and lowercase letters. If settings are incorrect, reconfigure them. For CHAP, clear the existing host name and password. Reconfigure the host name and password.
		Check the setting of the dialer map host name. If the setting is incorrect, reconfigure it.
debug isdn event, debug isdn q931 (privileged EXEC mode) See output example 8, which appears after this table.	Call connected, but was later disconnected.	Enter the debug ppp negotiation and debug ppp chap commands. Check output to see if PPP negotiation and PPP authentication are successful. If PPP negotiation is unsuccessful, call your Cisco reseller. If PPP authentication is unsuccessful, do the following: For PAP, check the settings of the PAP host name and password for correct spelling and use of uppercase and lowercase letters. If settings are incorrect, reconfigure them. For CHAP, clear the existing host name and password. Reconfigure the host name and password.
debug isdn event, debug isdn q931 (privileged EXEC mode) See output example 9, which appears after this table.	Wrong switch type.	Contact your telephone service provider to verify your switch type. Reconfigure the switch type if necessary. Disconnect any active ISDN calls and reset the ISDN BRI interface.

Output Example 1:

The current ISDN Switchtype = basic-ni1
ISDN BRI0 interface
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
Total Allocated ISDN CCBs = 0

Output Example 2:

Dial String      Successes   Failures    Last called   Last status
4155551212	0	1	00:00:00	failure
4155551213	1	0	00:00:00	successful
0 incoming call(s) have been screened.
BRI0: B-Channel 1
Idle timer (300 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
BRI0: B-Channel 2
Idle timer (300 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)

Output Example 3:

BRI0: Dialing cause: BRI0: ip PERMIT 
BRI0: No dialer string defined. Dialing cannot occur.. 
BRI0: Dialing cause: BRI0: ip PERMIT 
BRI0: No dialer string defined. Dialing cannot occur.. 
BRI0: Dialing cause: BRI0: ip PERMIT 
BRI0: No dialer string defined. Dialing cannot occur.. 
BRI0: Dialing cause: BRI0: ip PERMIT
BRI0: No dialer string defined. Dialing cannot occur.. 
BRI0: Dialing cause: BRI0: ip PERMIT 
BRI0: No dialer string defined. Dialing cannot occur..

Output Example 4:

Global ISDN Switchtype = basic-5ess
ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Spid Status:
TEI 64, ces = 1, state = 4(await init)
spid1 configured, no LDN, spid1 sent, spid1 NOT valid
TEI Not Assigned, ces = 2, state = 1(terminal down)
spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 1
CCB:callid=0x0, sapi=0, ces=1, B-chan=0, calltype = INTERNAL
Total Allocated ISDN CCBs = 1

Output Example 5:

BRI0: Dialing cause: BRI0: ip PERMIT
BRI0: Attempting to dial 6968900
TX ->  SETUP dsl = 0 pd = 8  callref = 0x01
         Bearer Capability i = 0x8890218F
         Channel ID i = 0x83
         Called Party Number i = 0x80, '6968900'
RX <-  CALL_PROC dsl = 0 pd = 8  callref = 0x81
         Channel ID i = 0x89..
RX <-  PROGRESS dsl = 0 pd = 8  callref = 0x81
         Progress Ind i = 0xC48A - Delay in response at called interface 
         Signal i = 0x01.
RX <-  DISCONNECT dsl = 0 pd = 8  callref = 0x81
         Cause i = 0x8295 - Call rejected 
         Signal i = 0x01
TX ->  RELEASE dsl = 0 pd = 8  callref = 0x01
RX <-  RELEASE_COMP dsl = 0 pd = 8  callref = 0x81
         Signal i = 0x3F..

Output Example 6:

Kisdn-SCAL#
19:27:31: TX ->  IDREQ  ri = 19354  ai = 127 dsl = 0
19:27:33: TX ->  IDREQ  ri = 1339  ai = 127 dsl = 0
19:27:35: TX ->  IDREQ  ri = 22764  ai = 127 dsl = 0
19:27:37: TX ->  IDREQ  ri = 59309  ai = 127 dsl = 0
19:27:39: TX ->  IDREQ  ri = 25214  ai = 127 dsl = 0
19:27:41: TX ->  IDREQ  ri = 35423  ai = 127 dsl = 0
19:27:43: TX ->  IDREQ  ri = 12368  ai = 127 dsl = 0
19:27:45: TX ->  IDREQ  ri = 13649  ai = 127 dsl = 0
19:27:47: TX ->  IDREQ  ri = 35426  ai = 127 dsl = 0
19:27:49: TX ->  IDREQ  ri = 12419  ai = 127 dsl = 0
19:27:51: TX ->  IDREQ  ri = 14516  ai = 127 dsl = 0
19:28:04: TX ->  IDREQ  ri = 50165  ai = 127 dsl = 0
19:28:06: TX ->  IDREQ  ri = 838  ai = 127 dsl = 0
19:28:08: TX ->  IDREQ  ri = 14247  ai = 127 dsl = 0
19:28:34: TX ->  IDREQ  ri = 45592  ai = 127 dsl = 0
19:28:36: TX ->  IDREQ  ri = 54169  ai = 127 dsl = 0
19:28:38: TX ->  IDREQ  ri = 3370  ai = 127 dsl = 0
19:29:09: TX ->  IDREQ  ri = 57291  ai = 127 dsl = 0
19:29:11: TX ->  IDREQ  ri = 56444  ai = 127 dsl = 0
19:29:13: TX ->  IDREQ  ri = 42045  ai = 127 dsl = 0
19:29:44: TX ->  IDREQ  ri = 59406  ai = 127 dsl = 0
19:29:46: TX ->  IDREQ  ri = 26863  ai = 127 dsl = 0
19:29:48: TX ->  IDREQ  ri = 63456  ai = 127 dsl = 0
19:30:19: TX ->  IDREQ  ri = 30177  ai = 127 dsl = 0
19:30:21: TX ->  IDREQ  ri = 54258  ai = 127 dsl = 0
19:30:23: TX ->  IDREQ  ri = 4883  ai = 127 dsl = 0
19:30:54: TX ->  IDREQ  ri = 17476  ai = 127 dsl = 0
19:30:56: TX ->  IDREQ  ri = 34949  ai = 127 dsl = 0
19:30:58: TX ->  IDREQ  ri = 4310  ai = 127 dsl = 0
19:31:24: TX ->  IDREQ  ri = 7735  ai = 127 dsl = 0
19:31:26: TX ->  IDREQ  ri = 424  ai = 127 dsl = 0

Output Example 7:

pico#ping 192.9.198.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.9.198.1, timeout is 2 seconds:
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up
%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up
ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEEF99
ppp: received config for type = 3 (AUTHTYPE) value = C223 value = 5 
acked
ppp: received config for type = 5 (MAGICNUMBER) value = 1E23F5C acked
PPP BRI0: B-Channel 1: state = ACKSENT fsm_rconfack(C021): rcvd id E4
ppp: config ACK received, type. = 3 (CI_AUTHTYPE), value = C223
ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 28CEEF99
BRI0: B-Channel 1: PPP AUTH CHAP input code = 1 id = 82 len = 16
BRI0: B-Channel 1: PPP AUTH CHAP input code = 2 id = 95 len = 28
BRI0: B-Channel 1: PPP AUTH CHAP input code = 4 id = 82 len = 21
BRI0: B-Channel 1: Failed CHAP authentication with remote.
Remote message is: MD compare failed
ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEEFDB
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down
%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up
%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up
ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEF76C
ppp: received config for type = 3 (AUTHTYPE) value = C223 value = 5 
acked
ppp: received conf.ig for type = 5 (MAGICNUMBER) value = 1E24718 acked
PPP BRI0: B-Channel 1: state = ACKSENT fsm_rconfack(C021): rcvd id E6
ppp: config ACK received, type = 3 (CI_AUTHTYPE), value = C223
ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 28CEF76C
BRI0: B-Channel 1: PPP AUTH CHAP input code = 1 id = 83 len = 16
BRI0: B-Channel 1: PPP AUTH CHAP input code = 2 id = 96 len = 28
BRI0: B-Channel 1: PPP AUTH CHAP input code = 4 id = 83 len = 21
BRI0: B-Channel 1: Failed CHAP authentication with remote.
Remote message is: MD compare failed

Output Example 8:

TX ->  RRp  dsl = 1 sapi = 0  tei = 96  nr = 98
RX <-  RRf  dsl = 1 sapi = 0  tei = 96  nr = 108
RX <-  UI  dsl = 1 sapi = 0  tei = 127 i =
0x08015805040288901801893401407008C135353434373336
    SETUP dsl = 1 pd = 8  callref = 0x58
        Bearer Capability i = 0x8890
        Channel ID i = 0x89
        Signal i = 0x40
        Called Party Number i = 0xC1, '5544736'
ISDN Event: incoming ces value = 1
received HOST_INCOMING_CALL
        Bearer Capability i = 0x080010
        -------------------
        Channel ID i = 0x0101
        Called Party Number i = 0x0401, '5544736'
        IE out of order or end of 'private' IEs --
        Bearer Capability i = 0x8890
        Channel ID i = 0x89
        Signal i = 0x40
        Called Party Number i = 0xC1, '5544736'
ISDN Event: Received a call from  on B1 at 64 Kb/s
ISDN Event: Accepting the call
%LINK-3-UPDOWN: Interface BRI1: B-Channel 1, changed state to up
TX ->  INFOc  dsl = 1 sapi = 0  tei = 96  ns = 108  nr = 98  i =
0x0801D807180189
    CONNECT dsl = 1 pd = 8  callref = 0xD8
        Channel ID i = 0x89
RX <-  RRr  dsl = 1 sapi = 0  tei = 96  nr = 109
RX <-  INFOc  dsl = 1 sapi = 0  tei = 96  ns = 98  nr = 109  i =
0x0801580F18018934014F
    CONNECT_ACK dsl = 1 pd = 8  callref = 0x58
        Channel ID i = 0x89
        Signal i = 0x4F
TX ->  RRr  dsl = 1 sapi = 0  tei = 96  nr = 99
ISDN Event: incoming ces value = 1
received HOST_CONNECT
        Channel ID i = 0x0101
        -------------------
        Channel ID i = 0x89
        Signal i = 0x4F
ISDN Event: Connected to  on B1 at 64 Kb/s
%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1: B-Channel 1, 
changed
state to up
TX ->  RRp  dsl = 1 sapi = 0  tei = 105  nr = 17
RX <-  RRf  dsl = 1 sapi = 0  tei = 105  nr = 1
TX ->  RRp  dsl = 1 sapi = 0  tei = 96  nr = 99
RX <-  RRf  dsl = 1 sapi = 0  tei = 96  nr = 109
%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1: B-Channel 1, 
changed
state to down
ISDN Event: Hangup call to call id 0x3C on dsl 1, ces = 1
TX ->  INFOc  dsl = 1 sapi = 0  tei = 96  ns = 109  nr = 99  i =
0x0801D84508028090
    DISCONNECT dsl = 1 pd = 8  callref = 0xD8
        Cause i = 0x8090 - Normal call clearing
RX <-  RRr  dsl = 1 sapi = 0  tei = 96  nr = 110
RX <-  INFOc  dsl = 1 sapi = 0  tei = 96  ns = 99  nr = 110  i = 
0x0801584D
    RELEASE dsl = 1 pd = 8  callref = 0x58
TX ->  RRr  dsl = 1 sapi = 0  tei = 96  nr = 100
ISDN Event: incoming ces value = 1
received HOST_DISCONNECT_ACK
%LINK-3-UPDOWN: Interface BRI1: B-Channel 1, changed state to down
TX ->  INFOc  dsl = 1 sapi = 0  tei = 96  ns = 110  nr = 100  i = 
0x0801D85A
    RELEASE_COMP dsl = 1 pd = 8  callref = 0xD8
ISDN Event: Hangup call to call id 0x3C on dsl 1, ces = 1
  CCBRI Mail NULL InPkt public is 0 ccb is 3C53E0
ISDN Event: incoming ces value = 1
received HOST_QUERY_RESPONSE
        Call State i = 0x00
        -------------------
RX <-  RRr  dsl = 1 sapi = 0  tei = 96  nr = 111
TX ->  RRp  dsl = 1 sapi = 0  tei = 105  nr = 17

Output Example 9:

0:05:44: BRI0: ISDN Event: incoming ces value = 1 
0:05:44: BRI0: received HOST_PROCEEDING
       Channel ID i = 0x0101
0:05:44:        -------------------
       Channel ID i = 0x89
0:05:44:         Locking Shift to Codeset 5
0:05:44:         Codeset 5 IE 0x2A  i = 0x80880B,'12149398003',
0x8001098001148 
00114800114
0:05:44: BRI0: RX <-  DISCONNECT pd = 8  callref = 0x89 
0:05:44:  Cause i = 0x82EF - Protocol error, unspecified 
0:05:44: BRI0: ISDN Event: incoming ces value = 1
0:05:44: BRI0: received HOST_DISCONNECT
0:05:44: BRI0: ISDN Event:  Call to 12149398003 was hung up. 
0:05:44: BRI0: TX ->  RELEASE pd = 8  callref = 0x09 
0:05:44: BRI0: RX <-  RELEASE_COMP pd = 8  callref = 0x89 
0:05:44: BRI0: ISDN Event: incoming ces value = 1
0:05:44: BRI0: received HOST_DISCONNECT_ACK
0:05:45: BRI0: ISDN Event: Call to 12149398003 at 56 Kb/s 
0:05:46: BRI0: TX ->  SETUP pd = 8  callref = 0x0A 
0:05:46:         Bearer Capability i = 0x8890218F 
0:05:46:         Channel ID i = 0x83
0:05:46:         Called Party Number i = 0x80, '12149398003'
0:05:46: BRI0: RX <-  CALL_PROC pd = 8  callref = 0x8A
0:05:46:         Channel ID i = 0x89 
0:05:46:         Locking Shift to Codeset 5
0:05:46:         Codeset 5 IE 0x2A  i = 0x80880B, '12149398003', 
0x8001098001148
00114800114
0:05:46: BRI0: ISDN Event: incoming ces value = 1 
0:05:46: BRI0: received HOST_PROCEEDING
       Channel ID i = 0x0101
0:05:46:        -------------------
       Channel ID i = 0x89
0:05:46:         Locking Shift to Codeset 5
0:05:46:         Codeset 5 IE 0x2A  i = 0x80880B, '12149398003', 
0x8001098001148
00114800114
0:05:46: BRI0: RX <-  DISCONNECT pd = 8  callref = 0x8A 
0:05:46:         Cause i = 0x82EF - Protocol error, unspecified 
0:05:46: BRI0: ISDN Event: incoming ces value = 1
0:05:46: BRI0: received HOST_DISCONNECT
0:05:46: BRI0: ISDN Event:  Call to 12149398003 was hung up. 
0:05:46: BRI0: TX ->  RELEASE pd = 8  callref = 0x0A 
0:05:46: BRI0: RX <-  RELEASE_COMP pd = 8  callref = 0x8A 
0:05:46: BRI0: ISDN Event: incoming ces value = 1
0:05:46: BRI0: received HOST_DISCONNECT_ACK 
0:05:59: BRI0: RX <-  SETUP pd = 8  callref = 0x01 
0:05:59:         Bearer Capability i = 0x8890 
0:05:59:         Channel ID i = 0x89

Telephone Interfaces

Table 9-3 describes possible problems your router might be experiencing and solutions to solve the problems. Table 9-4 describes debug commands. An output example from each command appears after the table. For important information on using debug commands, see the "Debug Commands" section earlier in this chapter.

Table 9-3: Symptoms of Telephone Trouble

Symptom Possible Problem Solution

Even though you have devices connected to ports 1 and 2, all calls are going to port 1.

You have not created dial peers.

Create dial peers. For information, refer to the "Creating Dial Peers" section in Chapter 7, "Configuring Telephone Interfaces."

You cannot make outgoing calls.

You have not specified all ISDN directory numbers with a SPID (North America only).

Check the settings of the isdn spid 1 and isdn spid 2 commands to make sure that you have specified all ISDN directory numbers for each SPID.

Even though you have created dial peers and set up distinctive ringing and ISDN voice priority, calls meant for secondary or tertiary ISDN directory numbers are routed to the primary number.

Incorrect dial peer, distinctive ringing, or ISDN voice priority configurations.

Check dial peer, distinctive ringing, or ISDN voice priority configurations by referring to Chapter 7, "Configuring Telephone Interfaces."

Use the debug q931 command.

Symptom	Possible Problem	Solution
Even though you have devices connected to ports 1 and 2, all calls are going to port 1.	You have not created dial peers.	Create dial peers. For information, refer to the "Creating Dial Peers" section in Chapter 7, "Configuring Telephone Interfaces."
You cannot make outgoing calls.	You have not specified all ISDN directory numbers with a SPID (North America only).	Check the settings of the isdn spid 1 and isdn spid 2 commands to make sure that you have specified all ISDN directory numbers for each SPID.
Even though you have created dial peers and set up distinctive ringing and ISDN voice priority, calls meant for secondary or tertiary ISDN directory numbers are routed to the primary number.	Incorrect dial peer, distinctive ringing, or ISDN voice priority configurations.	Check dial peer, distinctive ringing, or ISDN voice priority configurations by referring to Chapter 7, "Configuring Telephone Interfaces." Use the debug q931 command.

Table 9-4: Troubleshooting Telephone Interface

Command Possible Problem Solution

debug pots driver
[1 | 2]
(privileged EXEC mode)

See output examples 10 and 11, which appear after this table.

Caller ID device is not working either because you have not ordered the feature or because your device is not supported.

Contact your telephone service provider to verify that you ordered caller ID or to determine if there is a problem with the feature.

Refer to the "Caller Identification" section in Chapter 7, "Configuring Telephone Interfaces," for information on supported caller ID devices.

debug pots csm [1 | 2]
(privileged EXEC mode)

See output example 12, which appears after this table.

One of your dial peers might contain an invalid destination.

Check the settings of the destination pattern in each dial peer. If a setting is incorrect, use the destination-pattern ldn command.

Command	Possible Problem	Solution
debug pots driver [1 \| 2] (privileged EXEC mode) See output examples 10 and 11, which appear after this table.	Caller ID device is not working either because you have not ordered the feature or because your device is not supported.	Contact your telephone service provider to verify that you ordered caller ID or to determine if there is a problem with the feature. Refer to the "Caller Identification" section in Chapter 7, "Configuring Telephone Interfaces," for information on supported caller ID devices.
debug pots csm [1 \| 2] (privileged EXEC mode) See output example 12, which appears after this table.	One of your dial peers might contain an invalid destination.	Check the settings of the destination pattern in each dial peer. If a setting is incorrect, use the destination-pattern ldn command.

Output Example 10:

00:01:51:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown
00:01:51:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:01:51:POTS DRIVER port=1 enter_ringing
00:01:51:POTS DRIVER port=1 cmd=19
00:01:51:POTS DRIVER port=1 activate disconnect
00:01:51:POTS DRIVER port=1 state=Ringing drv_event=DISCONNECT_EVENT
00:01:51:POTS DRIVER port=1 cmd=1A
00:01:51:POTS DRIVER port=1 enter_idle
00:01:51:POTS DRIVER port=1 ts connect: 0 0
00:01:51:POTS DRIVER port=1 cmd=D
00:01:51:POTS DRIVER port=1 report onhook
00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:01:51:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:01:51:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:01:53:POTS DRIVER port=1 activate ringer: cadence=0 callerId=Unknown
00:01:53:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:01:53:POTS DRIVER port=1 enter_ringing
00:01:53:POTS DRIVER port=1 cmd=19
00:01:55:POTS DRIVER port=1 cmd=1A
00:02:49:POTS DRIVER port=1 state=Ringing drv_event=OFFHOOK_EVENT
00:02:49:POTS DRIVER port=1 cmd=1A
00:02:49:POTS DRIVER port=1 enter_suspend
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 report offhook
00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:02:49:POTS DRIVER port=1 state=Suspend drv_event=CONNECT_EVENT
00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 ts connect: 1 0
00:02:49:POTS DRIVER port=1 activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:02:49:POTS DRIVER port=1 state=Connect drv_event=CONNECT_EVENT
00:02:49:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:02:49:POTS DRIVER port=1 cmd=A
00:02:49:POTS DRIVER port=1 ts connect: 1 0
00:02:55:POTS DRIVER port=1 state=Connect drv_event=ONHOOK_EVENT
00:02:55:POTS DRIVER port=1 enter_idle
00:02:55:POTS DRIVER port=1 ts connect: 0 0
00:02:55:POTS DRIVER port=1 cmd=D
00:02:55:POTS DRIVER port=1 report onhook
00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:02:55:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:02:55:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT

Output Example 11:

00:09:15:POTS DRIVER port=1 activate ringer: cadence=0 callerId=4085551111
00:09:15:POTS DRIVER port=1 state=Idle drv_event=RING_EVENT
00:09:15:POTS DRIVER port=1 enter_ringing
00:09:15:POTS DRIVER port=1 callerIdStrg=030100094085551111U len=129F
00:09:15:POTS DRIVER port=1 cmd=19
00:09:17:POTS DRIVER port=1 cmd=1A
00:09:17:POTS DRIVER port=1 cmd=B
00:09:17:POTS DRIVER port=1 ts connect: 3 0
00:09:21:POTS DRIVER port=1 cmd=19
00:09:23:POTS DRIVER port=1 cmd=1A
00:09:24:POTS DRIVER port=1 state=Ringing drv_event=OFFHOOK_EVENT
00:09:24:POTS DRIVER port=1 enter_suspend
00:09:24:POTS DRIVER port=1 cmd=A
00:09:24:POTS DRIVER port=1 report offhook
00:09:24:POTS DRIVER port=1 state=activate connect: endpt=1 calltype=TWO_PARTY_CALL
00:09:24:POTS DRIVER port=1 state=suspend drv_event=CONNECT_EVENT
00:09:24:POTS DRIVER port=1 enter_connect: endpt=1 calltype=0
00:09:24:POTS DRIVER port=1 cmd=A
00:09:24:POTS DRIVER port=1 ts connect: 1 0
00:09:46:POTS DRIVER port=1 activate disconnect
00:09:46:POTS DRIVER port=1 state=Connect drv_event=DISCONNECT_EVENT
00:09:46:POTS DRIVER port=1 enter_disconnect: discon type=1
00:09:46:POTS DRIVER port=1 ts connect: 0 0
00:09:46:POTS DRIVER port=1 cmd=8
00:09:47:POTS DRIVER port=1 state=Disconnect drv_event=DISCON_SUPV_TIMER
00:09:47:POTS DRIVER port=1 cmd=A
00:09:48:POTS DRIVER port=1 activate tone=FASTBUSY_TONE
00:09:48:POTS DRIVER port=1 state=Disconnect drv_event=TONE_EVENT
00:09:48:POTS DRIVER port=1 disconnect tone
00:09:49:POTS DRIVER port=1 state=Disconnect drv_event=ONHOOK_EVENT
00:09:49:POTS DRIVER port=1 enter_idle
00:09:49:POTS DRIVER port=1 ts connect: 0 0
00:09:49:POTS DRIVER port=1 cmd=D
00:09:49:POTS DRIVER port=1 report onhook
00:09:49:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:09:49:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT
00:09:49:POTS DRIVER port=1 activate tone=SILENCE_TONE
00:09:49:POTS DRIVER port=1 state=Idle drv_event=TONE_EVENT

Output Example 12:

01:57:28:EVENT_FROM_ISDN:dchanidb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x1, cause=0x0
01:57:28:Dial peer not found, route call to port 1
01:57:28:CSM_PROC_IDLE:CSM_EVENT_ISDN_CALL, call_id=0x11, port=1
01:57:28:Calling number `5551111'
01:57:40:CSM_PROC_RINGING:CSM_EVENT_VDEV_OFFHOOK, call_id=0x11, port=1
01:57:40:EVENT_FROM_ISDN:dchan_idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0x0, event=0x4, cause=0x0
01:57:40:CSM_PROC_CONNECTING:CSM_EVENT_ISDN_CONNECTED, call_id=0x11, port=1
01:57:47:CSM_PROC_CONNECTING:CSM_EVENT_VDEV_ONHOOK, call_id=0x11, port=1
01:57:201863503872: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call lasted 5485 seconds
01:57:47: %ISDN-6-DISCONNECT:Interface BRI0:1 disconnected from unknown, call lasted 5485 seconds
01:57:47:EVENT_FROM_ISDN:dchan _idb=0x66CB38, call_id=0x11, ces=0x2 bchan=0xFFFFFFFF, event=0x0, cause=0x1
01:57:47:CSM_PROC_NEAR_END_DISCONNECT:CSM_EVENT_ISDN_DISCONNECTED, call_id=0x11, port=1

Table of Contents

Troubleshooting

Troubleshooting

Recovering a Lost Enable Password

Troubleshooting ISDN

Debug Commands

Telephone Interfaces