Re: connect a PC via modem to a Cisco 801

s.tecnico · ‎01-28-2002

I want to configure a connection between a remote Pc (with a modem) and a Cisco router 801 with a bri interface. I have configured the option "dialer incoming-calls data" on the bri0 interface to treat allways all calls as a data. When the PC rangs, the router detects the incoming call as a DATA type, brings up one of the two isdn channels and starts to negotiate the LCP but at last of some chances disconnects because of time out.

There's somebody who knows what on earth could be happenning?

Below you can see the "sh debug" of the cisco 801 when the incoming call is produced. Thanks in advanced.

00:02:39: ISDN BR0: RX <- SETUP pd = 8 callref = 0x63

00:02:39: Sending Complete

00:02:39: Bearer Capability i = 0x9090A3

00:02:39: Channel ID i = 0x89

00:02:39: Progress Ind i = 0x8A83 - Origination address is non-ISDN

00:02:39: Calling Party Number i = 0x0183, '932035295', Plan:ISDN, Type:

Unknown

00:02:39: Called Party Number i = 0xA1, '932066084', Plan:ISDN, Type:Nat

ional

00:02:167503724544: ISDN BR0: Incoming call id = 0x0002, dsl 0

00:02:167503724544: ISDN BR0: LIF_EVENT: ces/callid 1/0x2 HOST_INCOMING_CALL

00:02:167503724544: ISDN BR0: HOST_INCOMING_CALL: voice_answer_data = TRUE call

type is VOICE ALAW

00:02:167503765504: ISDN BR0: Event: Received a DATA call from 932035295 on B1 a

t 64 Kb/s

00:02:167503765504: ISDN BR0: Event: Accepting the call id 0x2

*Mar 1 00:02:39.517: %DIALER-6-BIND: Interface BR0:1 bound to profile Di2

00:02:167510574276: ISDN BR0: RM returned call_type 0 resource type 0

00:02:39: ISDN BR0: isdn_send_connect(): msg 4, call id 0x2, ces 1 bchan 0, call

type DATA

*Mar 1 00:02:39.589: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up

00:02:39: BR0:1 PPP: Treating connection as a callin

00:02:39: BR0:1 PPP: Phase is ESTABLISHING, Passive Open [0 sess, 0 load]

00:02:39: BR0:1 LCP: State is Listen

00:02:39: ISDN BR0: TX -> CALL_PROC pd = 8 callref = 0xE3

00:02:39: Channel ID i = 0x89

00:02:39: ISDN BR0: TX -> ALERTING pd = 8 callref = 0xE3

00:02:39: ISDN BR0: TX -> CONNECT pd = 8 callref = 0xE3

00:02:39: ISDN BR0: RX <- CONNECT_ACK pd = 8 callref = 0x63

00:02:167503724544: ISDN BR0: LIF_EVENT: ces/callid 1/0x2 HOST_CONNECT

00:02:167503724544: ISDN BR0: Event: Connected to 932035295 on B1 at 64 Kb/s

00:02:41: BR0:1 LCP: TIMEout: State Listen

00:02:41: BR0:1 LCP: O CONFREQ [Listen] id 1 len 10

00:02:41: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:43: BR0:1 LCP: TIMEout: State REQsent

00:02:43: BR0:1 LCP: O CONFREQ [REQsent] id 2 len 10

00:02:43: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

*Mar 1 00:02:45.637: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 9320

35295

00:02:45: BR0:1 LCP: TIMEout: State REQsent

00:02:45: BR0:1 LCP: O CONFREQ [REQsent] id 3 len 10

00:02:45: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:47: BR0:1 LCP: TIMEout: State REQsent

00:02:47: BR0:1 LCP: O CONFREQ [REQsent] id 4 len 10

00:02:47: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:49: BR0:1 LCP: TIMEout: State REQsent

00:02:49: BR0:1 LCP: O CONFREQ [REQsent] id 5 len 10

00:02:49: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:51: BR0:1 LCP: TIMEout: State REQsent

00:02:51: BR0:1 LCP: O CONFREQ [REQsent] id 6 len 10

00:02:51: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:53: BR0:1 LCP: TIMEout: State REQsent

00:02:53: BR0:1 LCP: O CONFREQ [REQsent] id 7 len 10

00:02:53: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:55: BR0:1 LCP: TIMEout: State REQsent

00:02:55: BR0:1 LCP: O CONFREQ [REQsent] id 8 len 10

00:02:55: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:57: BR0:1 LCP: TIMEout: State REQsent

00:02:57: BR0:1 LCP: O CONFREQ [REQsent] id 9 len 10

00:02:57: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:02:59: BR0:1 LCP: TIMEout: State REQsent

00:02:59: BR0:1 LCP: O CONFREQ [REQsent] id 10 len 10

00:02:59: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:03:01: BR0:1 LCP: TIMEout: State REQsent

00:03:01: BR0:1 LCP: O CONFREQ [REQsent] id 11 len 10

00:03:01: BR0:1 LCP: MagicNumber 0x0219DA62 (0x05060219DA62)

00:03:03: BR0:1 LCP: TIMEout: State REQsent

00:03:03: BR0:1 PPP: Treating connection as a callin

*Mar 1 00:03:03.761: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di2

00:03:03: BR0:1 LCP: State is Listen

00:03:03: ISDN BR0: Event: Hangup call to call id 0x2

00:03:03: ISDN BR0: process_disconnect(): call id 0x2, call type is DATA, b_idb

0x276F0A4, ces 1, cause Normal call clearing(0x10)

*Mar 1 00:03:03.813: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 93

2035295 , call lasted 24 seconds

00:03:03: ISDN BR0: TX -> DISCONNECT pd = 8 callref = 0xE3

00:03:03: Cause i = 0x8090 - Normal call clearing

00:03:04: ISDN BR0: RX <- RELEASE pd = 8 callref = 0x63

00:03:04: Cause i = 0x8090 - Normal call clearing

00:03:17186718972: ISDN BR0: LIF_EVENT: ces/callid 1/0x2 HOST_DISCONNECT_ACK

00:03:17179869184: ISDN BR0: HOST_DISCONNECT_ACK: call type is DATA

*Mar 1 00:03:04.285: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down

00:03:17179869184: BR0:1 LCP: State is Closed

00:03:17186718772: BR0:1 PPP: Phase is DOWN [0 sess, 0 load]

00:03:04: ISDN BR0: TX -> RELEASE_COMP pd = 8 callref = 0xE3

*Mar 1 00:03:14.345: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 80 chan

ged to down

00:03:60129542144: L3: NLCB watch! cid 0x4BC628 cr 0x0 ev 0x211 ces 222 dsl 0

empulse · ‎01-28-2002

I do not believe that you can dial an ISDN modem directly using a standard analog modem. It appears from your message that this is what you are doing. I think you need to use an ISDDN modem, using an ISDN line on the computer you are dialing from.

s.tecnico · ‎02-03-2002

Are you sure there's no way to dial from an analog modem to an ISDN line connected to a Cisco 801?

If you connnect the ISDN line to a server and you use an analog modem to dial in and to connect to the server it funcitons OK, so why you can´t do it with the router? If you look through the debug you can see a problem of time out during de LCP phase, might it be a problem of sincronization?

mitchellp · ‎02-04-2002

Seems to me as if the LCP negotiation is one sided, no input packets received from the PC. One of the first negotiations should be the authorisation protocol (PAP, CHAP). Might be worth checking the PC's config. and also the authorisation protocol in use. If you do not want to use a particular one, it is best to specifically refuse it in the interface config. on the router, otherwise the two ends may never agree. Also sometimes it is best to use a one way authentication, so that the PC is authenticated, but it doesn't try to authenticate the router.