Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

lcp timeout ...

Hi,

while trying to connect two routers with bri ( one b channel )

i can'`t get through the lcp negotiation..

i can`t see any authentication problem...

here is the output from various debug commands

1d02h: dchan tx start

1d02h: dchan tx intr

1d02h: ISDN BR0: received HOST_CONNECT call_id 0x80BABRI: enable channel B1

1d02h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up

1d02h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 048500073 .

1d02h: BR0:1 PPP: Treating connection as a callout

1d02h: BR0:1 PPP: Phase is ESTABLISHING, Active Open

1d02h: BR0:1 LCP: O CONFREQ [Closed] id 252 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: BRI 0 B1: Set bandwidth to 64Kb

1d02h: ISDN BR0: Event: Connected to 048500073 on B1 at 64 Kb/s

1d02h: dchan tx start

1d02h: dchan tx intr.

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 253 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2).

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 254 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: BR0:1 UNKNOWN(0x008F): LCP not open, discarding packet

1d02h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 1234567 .

Success rate is 0 percent (0/5)

Router#

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 255 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 0 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 1 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: dchan tx start

1d02h: dchan tx intr

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 2 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: BR0:1 LCP: TIMEout: State REQsent

1d02h: BR0:1 LCP: O CONFREQ [REQsent] id 3 len 10

1d02h: BR0:1 LCP: MagicNumber 0xD60A91D2 (0x0506D60A91D2)

1d02h: dchan tx start

1d02h: dchan tx intr

1d02h: ISDN BR0: received HOST_DISCONNECT call_id 0x80BA

1d02h: ISDN BR0: Event: Call to <unknown> was hung up.

1d02h: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 1234567 , call lasted 14 seconds BRI: disable channel B1

any ideas ?

3 REPLIES
Community Member

Re: lcp timeout ...

When you do your debug isdn q931 and ppp neg, look for cause code:

*May 25 22:44:36.340: BR0/0:1 LCP: I TERMREQ [Open] id 180 len 4

*May 25 22:44:36.340: BR0/0:1 LCP: O TERMACK [Open] id 180 len 4

*May 25 22:44:36.340: BR0/0:1 PPP: Phase is TERMINATING [0 sess, 1 load]

*May 25 22:44:36.476: ISDN BR0/0: RX <- DISCONNECT pd = 8 callref = 0xD5

*May 25 22:44:36.476: Cause i = 0x8090 - Normal call clearing

*May 25 22:44:36.484: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down

*May 25 22:44:36.484: BR0/0:1 LCP: State is Closed

Most likely it looks like a PPP issue. Check your commands on the bri0/0 interface and make sure you also have a dialer-list command that corresponds to the group on the bri interface.

Community Member

Re: lcp timeout ...

I am having the same problem, but only with internation isdn calls. All local calls work perfectly, but calls overseas only work 20 percent of the time. The disconnect reason is normal call clearing.

Any ideas would be much appreciated

Community Member

Re: lcp timeout ...

I am aware of similar problems. IDDD calls are compressed by the carriers to reserve bandwidth for voice calls (the carrier does not know your call is for data). Your call could be going via a compressed route between IDDD carriers. In the UK, an additional 0 (zero) prefix is required to request a full 64K channel. EG dial string is 0001 xxx yyyyyyy for calls to US.

Also you would be surprised at what bandwidth PTT/carriers have for their interconnections. If you need to bundle a few 64K channels together this could result in capacity problems, and the normal call clearing message will be seen in the Q931 debug.

343
Views
0
Helpful
3
Replies
CreatePlease to create content