[cisco-voip] ISDN Bad Frame

Mark Holloway mh at markholloway.com
Fri Dec 4 17:43:06 EST 2009


Thanks everyone, but after adding 'isdn protocol emulate network' on the PSTN router the debug on the HQ router has a different output.  This is one I haven't encountered before.

r1-hq#
Dec  4 22:08:58.358: ISDN Se0/0/0:23 Q921: User RX <- SABMEp sapi=0 tei=0
Dec  4 22:08:58.358: ISDN Se0/0/0:23 Q921: S4_SABME: BACKHAULED & vsc_wants_L2_up = FALSE
Dec  4 22:08:59.358: ISDN Se0/0/0:23 Q921: User RX <- SABMEp sapi=0 tei=0
Dec  4 22:08:59.358: ISDN Se0/0/0:23 Q921: S4_SABME: BACKHAULED & vsc_wants_L2_up = FALSE
Dec  4 22:09:05.358: ISDN Se0/0/0:23 Q921: User RX <- SABMEp sapi=0 tei=0
Dec  4 22:09:05.358: ISDN Se0/0/0:23 Q921: S4_SABME: BACKHAULED & vsc_wants_L2_up = FALSE
Dec  4 22:09:06.358: ISDN Se0/0/0:23 Q921: User RX <- SABMEp sapi=0 tei=0
Dec  4 22:09:06.358: ISDN Se0/0/0:23 Q921: S4_SABME: BACKHAULED & vsc_wants_L2_up = FALSE






On Dec 4, 2009, at 2:55 PM, Joe Martini (joemar2) wrote:

> Check your “isdn protocol emulate {network | user}”
>  
> Joe
>  
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mark Holloway
> Sent: Friday, December 04, 2009 4:46 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] ISDN Bad Frame
>  
> I'm trying to get this lab ISDN configuration up and running but I am having ISDN problems.  I have two 2811 routers each with a VWIC 2MFT-T1 and a T1 crossover cable connecting them.  They won't move from TEI_ASSIGNED to MULTIPLE_FRAME_ESTABLISHED.  I know my T1 cable is good. 
>  
> # debug isdn q921
>  
> Dec  4 20:57:58.250: ISDN Se0/0/0:23 Q921: User RX <- BAD FRAME(0x00017F)
> Dec  4 20:57:59.250: ISDN Se0/0/0:23 Q921: User RX <- BAD FRAME(0x00017F)
> Dec  4 20:58:00.250: ISDN Se0/0/0:23 Q921: User RX <- BAD FRAME(0x00017F)
>  
>  
> # show isdn status
>  
> Global ISDN Switchtype = primary-ni
>  
> %Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply
>  
> ISDN Serial0/0/0:23 interface
>             dsl 0, interface ISDN Switchtype = primary-ni
>             L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER 0x0003 
>     Layer 1 Status:
>             ACTIVE
>     Layer 2 Status:
>             TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
>  
>  
> # show run | sec controller
> controller T1 0/0/0
>  framing esf
>  linecode b8zs
>  cablelength short 133
>  pri-group timeslots 1-3,24 service mgcp
>  description PRI
>  
> # show run | sec Serial
> interface Serial0/0/0:23
>  description PRI
>  no ip address
>  encapsulation hdlc
>  isdn switch-type primary-ni
>  isdn incoming-voice voice
>  isdn bind-l3 ccm-manager
>  no cdp enable
>  
>  
> The "PSTN" router
>  
> controller T1 0/0/0
>  clock source internal
>  cablelength short 133
>  pri-group timeslots 1-3,24
>  description PRI
>  
> interface Serial0/2/0:23
>  description PRI
>  no ip address
>  encapsulation hdlc
>  isdn switch-type primary-ni
>  isdn incoming-voice voice
>  isdn bchan-number-order ascending 
>  no cdp enable
>  
> PSTN#deb isdn q921
> debug isdn q921 is                  ON.
> PSTN#term mon
> PSTN#
> Dec  4 21:54:51.090: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0
> Dec  4 21:54:55.590: ISDN Se0/2/0:23 Q921: L2_EstablishDataLink: sending SABME
> Dec  4 21:54:55.590: ISDN Se0/2/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
> Dec  4 21:54:56.590: ISDN Se0/2/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
> Dec  4 21:54:57.090: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME
> Dec  4 21:54:57.090: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0
> Dec  4 21:54:57.590: ISDN Se0/2/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
> Dec  4 21:54:58.090: ISDN Se0/0/0:23 Q921: Net TX -> SABMEp sapi=0 tei=0
>  
>  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091204/a3e007fc/attachment.html>


More information about the cisco-voip mailing list