ISDN BRI issue on Cisco 3825

Answered Question
Jun 8th, 2007

Hi,

3825 with 2 x WIC-1B-S/T-V3 in Turkey. Not able to make ISDN calls from London. Calls answered, PPP authentication Ok but calls then immediately dropped. Router running IOS 12.3(14)T7 SP Services.

BRI i/f configuration:

interface BRI0/1/0

no ip address

encapsulation ppp

dialer pool-member 50 max-link 2

isdn switch-type basic-net3

isdn point-to-point-setup

ppp authentication chap

ppp multilink

Layer 2 not MULTIFRAME_ESTABLISHED, but TEI_ASSIGNED, not necessarily a problem:

Global ISDN Switchtype = basic-net3

ISDN BRI0/1/0 interface

dsl 2, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 70, Ces = 1, SAPI = 0, State = TEI_ASSIGNED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 2 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

Q.921 debug:

istfirtc01#clear int bri 0/1/0

istfirtc01#

Jun 8 18:27:45.858 GMT+3: ISDN BR0/1/0 Q921: User TX -> IDREQ ri=19513 ai=127

Jun 8 18:27:45.878 GMT+3: ISDN BR0/1/0 Q921: User RX <- IDASSN ri=19513 ai=71

Jun 8 18:27:45.878 GMT+3: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jun 8 18:27:45.878 GMT+3: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=71

Jun 8 18:27:45.886 GMT+3: ISDN BR0/1/0 Q921: User RX <- IDCKRQ ri=0 ai=127

Jun 8 18:27:45.886 GMT+3: ISDN BR0/1/0 Q921: User TX -> IDCKRP ri=4042 ai=71

Jun 8 18:27:45.894 GMT+3: ISDN BR0/1/0 Q921: User RX <- UAf sapi=0 tei=71

Jun 8 18:27:45.894 GMT+3: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI71 changed to up

Jun 8 18:27:46.878 GMT+3: ISDN BR0/1/0 Q921: User RX <- IDCKRQ ri=0 ai=127

Jun 8 18:27:46.878 GMT+3: ISDN BR0/1/0 Q921: User TX -> IDCKRP ri=3179 ai=71

Jun 8 18:27:47.878 GMT+3: ISDN BR0/1/0 Q921: User RX <- IDREM ri=0 ai=70

Jun 8 18:27:47.890 GMT+3: ISDN BR0/1/0 Q921: User RX <- IDREM ri=0 ai=70

Jun 8 18:27:55.894 GMT+3: ISDN BR0/1/0 Q921: User TX -> RRp sapi=0 tei=71 nr=0

Jun 8 18:27:55.910 GMT+3: ISDN BR0/1/0 Q921: User RX <- RRf sapi=0 tei=71 nr=0

Jun 8 18:28:02.254 GMT+3: ISDN BR0/1/0 Q921: User RX <- DISCp sapi=0 tei=71

Jun 8 18:28:02.254 GMT+3: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 71 changed to down

Jun 8 18:28:02.254 GMT+3: ISDN BR0/1/0 Q921: User TX -> UAf sapi=0 tei=71

Jun 8 18:28:30.959 GMT+3: ISDN BR0/2/0 Q921: User RX <- IDCKRQ ri=0 ai=127

Jun 8 18:28:30.959 GMT+3: ISDN BR0/2/0 Q921: User TX -> IDCKRP ri=54044 ai=77

Jun 8 18:28:31.959 GMT+3: ISDN BR0/2/0 Q921: User RX <- IDCKRQ ri=0 ai=127

Jun 8 18:28:31.959 GMT+3: ISDN BR0/2/0 Q921: User TX -> IDCKRP ri=1245 ai=77

When line moved to a 2610XM, ISDN calls Ok.

I have this problem too.
0 votes
Correct Answer by Paolo Bevilacqua about 9 years 6 months ago

Hello,

router is disconnecting the call:

Jun 8 18:33:15.965 GMT+3: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x81

Cause i = 0x8090 - Normal call clearing

there are apparently no problem at ISDN level, please check again PPP negotiation. The only thing you can improve at ISDN layer, is "isdn tei-negotiation preserve".

Hope this helps, please rate post if it does!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
herve.durand Fri, 06/08/2007 - 07:46

Q.931 debug:

Jun 8 18:33:13.869 GMT+3: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8 callref = 0x01

Bearer Capability i = 0x8890

Standard = CCITT

Transfer Capability = Unrestricted Digital

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Calling Party Number i = 0x00C3, N/A

Plan:Unknown, Type:Unknown

Called Party Number i = 0xA1, '2123938154'

Plan:ISDN, Type:National

Low Layer Compat i = 0x8890

Sending Complete

Jun 8 18:33:13.873 GMT+3: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up

Jun 8 18:33:13.873 GMT+3: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to N/A N/A

Jun 8 18:33:13.889 GMT+3: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI71 changed to up

Jun 8 18:33:13.889 GMT+3: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8 callref =0x81

Channel ID i = 0x89

Jun 8 18:33:14.889 GMT+3: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8 callref =0x81

Channel ID i = 0x89

Jun 8 18:33:14.909 GMT+3: ISDN BR0/1/0 Q931: TX -> CONNECT pd = 8 callref = 0x81

Jun 8 18:33:15.001 GMT+3: ISDN BR0/1/0 Q931: RX <- CONNECT_ACK pd = 8 callref= 0x01

Jun 8 18:33:15.961 GMT+3: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1 disconnected from bebek, call lasted 2 seconds

Jun 8 18:33:15.965 GMT+3: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x81

Cause i = 0x8090 - Normal call clearing

Jun 8 18:33:16.053 GMT+3: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8 callref = 0x01

Cause i = 0x8090 - Normal call clearing

Jun 8 18:33:16.057 GMT+3: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down

Jun 8 18:33:16.057 GMT+3: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x81

Jun 8 18:33:32.854 GMT+3: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 71 changed to down

Jun 8 18:33:32.854 GMT+3: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Everything points to a problem on the 3825. Any known issues with the WIC-1B-S/T-V3?

Many thanks.

Correct Answer
Paolo Bevilacqua Fri, 06/08/2007 - 08:40

Hello,

router is disconnecting the call:

Jun 8 18:33:15.965 GMT+3: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8 callref = 0x81

Cause i = 0x8090 - Normal call clearing

there are apparently no problem at ISDN level, please check again PPP negotiation. The only thing you can improve at ISDN layer, is "isdn tei-negotiation preserve".

Hope this helps, please rate post if it does!

herve.durand Mon, 06/11/2007 - 09:57

Well, even though the PPP debug showed that authentication succeeded, remving CHAP config (including username) and putting it back appears to have solved the problem.

Thanks for the hint.

Actions

This Discussion