[cisco-nas] AS5300 ISDN problem

[Mark Johnson]

At 10:49 AM 7/1/2004 -0500, Jason T. Nelson wrote:
>I just configured an 8 PRI AS5300 box identically to an existing 4 PRI AS5300
>box to replace some older dual PRI equipment (non-Cisco). The version of IOS
>is identical between these two 5300's (12.2(2)XA4) yet ISDN customers who
>attempt to connect to the 8 PRI box are unable to. I have captured the Q.931
>debug output of one of these failing calls below:
>
>1d03h: ISDN Se6:23: RX <-  SETUP pd = 8  callref = 0x121F
>1d03h:         Bearer Capability i = 0x8890
>1d03h:         Channel ID i = 0xA18382
>1d03h:         Calling Party Number i = 0x2181, '7653428252', Plan:ISDN, 
>Type:National
>1d03h:         Called Party Number i = 0xC1, '3494202', Plan:ISDN, 
>Type:Subscriber(local)
>1d03h: %LINK-3-UPDOWN: Interface Serial6:1, changed state to up
>1d03h: ISDN Se6:23: TX ->  CALL_PROC pd = 8  callref = 0x921F
>1d03h:         Channel ID i = 0xA98382
>1d03h: ISDN Se6:23: TX ->  CONNECT pd = 8  callref = 0x921F
>1d03h:         Channel ID i = 0xA98382
>1d03h: ISDN Se6:23: RX <-  STATUS pd = 8  callref = 0x121F
>1d03h:         Cause i = 0x82E418 - Invalid information element contents
>1d03h:         Call State i = 0x08
>1d03h: ISDN Se6:23: RX <-  CONNECT_ACK pd = 8  callref = 0x121F
>1d03h: ISDN Se6:23: CALL_PROGRESS: CALL_CONNECTED call id 0x507F, bchan 1, 
>dsl 6
>1d03h: %ISDN-6-CONNECT: Interface Serial6:1 is now connected to 7653428252 
>username
>1d03h: ISDN Se6:23: TX ->  DISCONNECT pd = 8  callref = 0x921F
>1d03h:         Cause i = 0x8090 - Normal call clearing
>1d03h: ISDN Se6:23: RX <-  RELEASE pd = 8  callref = 0x121F
>1d03h: %LINK-3-UPDOWN: Interface Serial6:1, changed state to down
>1d03h: ISDN Se6:23: TX ->  RELEASE_COMP pd = 8  callref = 0x921F
>
>The relevant line that causes me grief is the STATUS packet I get from the
>remote ISDN device that seems to indicate error 100: "Invalid information
>element contents".

It's likely that the switch isn't happy that it specified a preferred
channel, and we specified an exclusive channel.  You can try <isdn negotiate-
bchan>, which will cause us to specify the channel as preferred.

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fdial_r/drfisl2.htm#1116673

The switch that the 4PRI connects to may be fine with the Exclusive setting.

Otherwise, msec timestamps and PPP debug (especially if the DISCONNECT is sent
out > 1 sec after the CONNECT_ACK) would be of interest.

mark