ISDN Q931: Ux_DLRelInd: DL_REL_IND received from L2

Unanswered Question
Aug 25th, 2010
User Badges:

Hi All!

The problem is following:

till today we got PRI so:

(Router)---PRI---(Nortel PBX) ----PRI------(Telco)


we don't use Nortel PBX and don't want to pay a rent for it. So now we've connected:

(Router)----PRI------Telco


But now I get ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2  and have no communication


And L2 status changes periodically from TEI_ASSIGNED to AWAITING_ESTABLISHMENT


running config:


network-clock-participate wic 2

isdn switch-type primary-net5


controller E1 0/2/0
framing NO-CRC4
clock source internal
pri-group timeslots 1-31


interface Serial0/2/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn protocol-emulate network
isdn incoming-voice voice
isdn sending-complete
no cdp enable




#sh isdn status                                                               
Global ISDN Switchtype = primary-net5
ISDN Serial0/2/0:15 interface
        ******* Network side configuration *******
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED                                - L2 state changes periodically
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0xFFFF7FFF
    Number of L2 Discards = 0, L2 Session ID = 0
ISDN Serial0/2/1:15 interface
        dsl 1, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask:  0x00000000
    Number of L2 Discards = 0, L2 Session ID = 0
    Total Allocated ISDN CCBs = 0



#sh isdn status
Global ISDN Switchtype = primary-net5
ISDN Serial0/2/0:15 interface
        ******* Network side configuration *******
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = AWAITING_ESTABLISHMENT
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0xFFFF7FFF
    Number of L2 Discards = 0, L2 Session ID = 0
ISDN Serial0/2/1:15 interface
        dsl 1, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask:  0x00000000
    Number of L2 Discards = 0, L2 Session ID = 0
    Total Allocated ISDN CCBs = 0


Have somebody hint how to solve the issue?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Aaron Harrison Wed, 08/25/2010 - 11:14
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Hi


Try these commands:


network-clock-select e1 0/2/0

controller E1 0/2/0

clock source line

shut

interface Serial0/2/0:15
no isdn protocol-emulate network

shut


controller e1 0/2/0

no shut


interface Serial0/2/0:15
no shut


And see what you get... typically you don't emulate network when connecting to a telco.


Regards


Aaron


Please rate helpful posts..

paolo bevilacqua Wed, 08/25/2010 - 11:19
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

You should set clock source line, and ...


Oops, Aaron beated me to it.

paolo bevilacqua Wed, 08/25/2010 - 11:30
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Check "show controllers E1", you may have a cabling issue.

Andrey128 Wed, 08/25/2010 - 11:33
User Badges:

#sh controllers E1

E1 0/2/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info Firmware: 20051006, FPGA: 20, spm_count = 0
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (605 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     11 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     11 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 66 Unavail Secs
  Total Data (last 9 15 minute intervals):
     113368 Line Code Violations, 16286 Path Code Violations,
     30 Slip Secs, 13 Fr Loss Secs, 8 Line Err Secs, 0 Degraded Mins,
     36 Errored Secs, 1 Bursty Err Secs, 13 Severely Err Secs, 391 Unavail Secs

paolo bevilacqua Wed, 08/25/2010 - 16:29
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Configure "network-clock-select 1 e1 0/2/0".


If still trouble, post config and outoput of "debug isdn q921" taken with "term mon".

Aaron Harrison Wed, 08/25/2010 - 11:31
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Hi


What country are you based in?


Other things that may want changing are the crc4 setting, or possibly the net5 isdn type for another one if that was configured specifically for the Nortel...


Aaron

Andrey128 Wed, 08/25/2010 - 11:37
User Badges:

Aaron,

Russia


I tried to change from no-crc to crc - controller didn't change to state up, isdn switch-type I did't change

Aaron Harrison Wed, 08/25/2010 - 11:46
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Can you post your current config again?

Steven Holl Thu, 08/26/2010 - 06:46
User Badges:
  • Cisco Employee,

L1 config shouldn't matter here if L1 is negotiating at all.  If the system logs don't report L1 flapping when L2 goes down, then lincoding, clocking, and framing should be fine.  As long as the controller runs clean with 'sh controller [t1|e1]' then that part is fine.


You mention you used to have this connected to a PBX, and are now going to the provider.  That's your issue: yoiu are still configured as network side on the PRI, which means the gateway is going to expect to receive SABMEs.  You need to be set to user side on this when interfacing with the provider:


interface Serial0/2/0:15

isdn protocol-emulate user

shut

no shut



If you still have issues after this, post a current:

sh ver

sh run

sh controller e1

sh isdn st

sh log | i %


Along with the output of 'debug isdn q921'.



-Steve

Andrey128 Sat, 08/28/2010 - 02:27
User Badges:

Hi All!

I changed:


controller E1 0/2/0

isdn protocol-emulate user

shut

no shut


but it didn't help.

Telco support tells that "we must change mode from 'master' to 'slave' ", are the commands above make this?


Here are needed diagnostic data:

-------------------------------------------------------------------------------

#sh ver


Cisco IOS Software, 3800 Software (C3825-SPSERVICESK9-M), Version 12.4(6)T3, REL                                                                             EASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Fri 21-Jul-06 17:43 by kellythw


ROM: System Bootstrap, Version 12.3(11r)T2, RELEASE SOFTWARE (fc1)


gw2  uptime is 2 days, 14 hours, 19 minutes
System returned to ROM by reload at 21:40:08 EEST Wed Aug 25 2010
System restarted at 21:41:27 EEST Wed Aug 25 2010
System image file is "flash:c3825-spservicesk9-mz.124-6.T3.bin"




Cisco 3825 (revision 1.0) with 184320K/77824K bytes of memory.


2 Gigabit Ethernet interfaces
26 Serial interfaces
1 terminal line
2 Channelized E1/PRI ports
8 Voice FXS interfaces
1 cisco service engine(s)
DRAM configuration is 64 bits wide with parity enabled.
479K bytes of NVRAM.
62720K bytes of ATA System CompactFlash (Read/Write)


Configuration register is 0x2102





-------------------------------------
#sh run


network-clock-participate wic 2
network-clock-select 1 E1 0/2/0


isdn switch-type primary-net5


controller E1 0/2/0
framing NO-CRC4
pri-group timeslots 1-12,16


interface Serial0/2/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
isdn sending-complete
no cdp enable
-------------------------------------


#sh controllers E1
E1 0/2/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info Firmware: 20051006, FPGA: 20, spm_count = 0
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (491 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Total Data (last 24 hours)
     2132 Line Code Violations, 421 Path Code Violations,
     2 Slip Secs, 3 Fr Loss Secs, 3 Line Err Secs, 0 Degraded Mins,
     2 Errored Secs, 0 Bursty Err Secs, 3 Severely Err Secs, 20 Unavail Secs


---------------------------------------


#sh isdn status
Global ISDN Switchtype = primary-net5
ISDN Serial0/2/0:15 interface
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0x80000FFF
    Number of L2 Discards = 0, L2 Session ID = 0
ISDN Serial0/2/1:15 interface
        dsl 1, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask:  0x00000000
    Number of L2 Discards = 0, L2 Session ID = 0
    Total Allocated ISDN CCBs = 0
------


#sh isdn status
Global ISDN Switchtype = primary-net5
ISDN Serial0/2/0:15 interface
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = AWAITING_ESTABLISHMENT
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0x80000FFF
    Number of L2 Discards = 0, L2 Session ID = 0
ISDN Serial0/2/1:15 interface
        dsl 1, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask:  0x00000000
    Number of L2 Discards = 0, L2 Session ID = 0
    Total Allocated ISDN CCBs = 0




----------------------------------------


#debug isdn q921 detail



Aug 28 09:11:28.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:28.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=1
Aug 28 09:11:28.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:28.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:29.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:29.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=2
Aug 28 09:11:29.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:29.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:30.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=3
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = ME 0x0700, prim = MDL_ERR_IND 0x0691
        priv_len = 4 int_id = 0x66DBA0C0 datasize = 17
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: data =
Aug 28 09:11:30.948:    66DBA0C0070000000691041400010000
Aug 28 09:11:30.948:    47
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = Q.931 0x0000, prim = DL_REL_IND 0x0211
        priv_len = 4 int_id = 0x66DBA0C0 datasize = 16
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: data =
Aug 28 09:11:30.948:    66DBA0C0000000000211044300010000
Aug 28 09:11:30.948:
Aug 28 09:11:35.948: ISDN Se0/2/0:15 Q921d: handle_mail: setting pkt to NULL
Aug 28 09:11:35.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:35.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:36.572: ISDN  Q921d: isdn_from_driver_process: QUEUE_EVENT
Aug 28 09:11:36.572: ISDN Se0/2/0:15 Q921d: process_rxdata: Frame sent to L2
Aug 28 09:11:36.572: ISDN  Q921d: isdn_from_driver_process: event_count 1
Aug 28 09:11:36.572: ISDN Se0/2/0:15 Q921d: NOP: DLCB state 5 EventIndex 3 L2_Event 1 Tei 0 DSL_Chan 0 ces 1 SAPI 0
Aug 28 09:11:36.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:36.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:36.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:37.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:37.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=1
Aug 28 09:11:37.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:37.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:38.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:38.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=2
Aug 28 09:11:38.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:38.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:39.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=3
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = ME 0x0700, prim = MDL_ERR_IND 0x0691
        priv_len = 4 int_id = 0x66DBA0C0 datasize = 17
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: data =
Aug 28 09:11:39.948:    66DBA0C0070000000691040000010006
Aug 28 09:11:39.948:    47
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = Q.931 0x0000, prim = DL_REL_IND 0x0211
        priv_len = 4 int_id = 0x66DBA0C0 datasize = 16
----------------------------------------------


#sh log | i ISDN


28 09:10:27.949: ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 28 09:10:36.949: ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 28 09:10:45.949: ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 28 09:10:54.949: ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 28 09:11:03.948: ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 28 09:11:12.948: ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Aug 28 09:11:28.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:28.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=1
Aug 28 09:11:28.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:28.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:29.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:29.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=2
Aug 28 09:11:29.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:29.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:30.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=3
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: data =
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
Aug 28 09:11:30.948: ISDN Se0/2/0:15 Q921d: data =
Aug 28 09:11:35.948: ISDN Se0/2/0:15 Q921d: handle_mail: setting pkt to NULL
Aug 28 09:11:35.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:35.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:36.572: ISDN  Q921d: isdn_from_driver_process: QUEUE_EVENT
Aug 28 09:11:36.572: ISDN Se0/2/0:15 Q921d: process_rxdata: Frame sent to L2
Aug 28 09:11:36.572: ISDN  Q921d: isdn_from_driver_process: event_count 1
Aug 28 09:11:36.572: ISDN Se0/2/0:15 Q921d: NOP: DLCB state 5 EventIndex 3 L2_Event 1 Tei 0 DSL_Chan 0 ces 1 SAPI 0
Aug 28 09:11:36.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:36.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:36.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:37.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:37.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=1
Aug 28 09:11:37.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:37.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:38.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:38.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=2
Aug 28 09:11:38.948: ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
Aug 28 09:11:38.948: ISDN  Q921d: isdn_l2d_srq_process: event_count 1
Aug 28 09:11:39.948: ISDN  Q921d: l2_timer: timer (0x6752A7F0), timer_type (0x1240)
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=3
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: data =
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
Aug 28 09:11:39.948: ISDN Se0/2/0:15 Q921d: data =
------------------------------------------------

Steven Holl Sat, 08/28/2010 - 05:18
User Badges:
  • Cisco Employee,

I can only assume that 'Master/slave' is referring to either network/user side (which we've discussed already) or in regards to clocking (which you are set to receive clock).


Can you run just 'debug isdn q921' instead of 'debug isdn q921 detail'?  The latter doesn't decode what the outbound messages are.  I want to make sure that the SABME messages are being sent to the provider.  It looks like they are, and the T200 timer is the one that will pop, but I want to see the normal q921 debugs to be sure.


If 'debug isdn q921 shows us transmitting a SABME out the circuit, you need to get with your provider and have them tell you why they aren't responding with a UA.

http://www.freesoft.org/CIE/Topics/125.htm


Also, I see that the circuit has taken L1 errors.  Issue 'clear counters' and make sure those counters stay at 0 during times where you know L1 isn't flapping.


-Steve

Andrey128 Sat, 08/28/2010 - 05:48
User Badges:

Hi, Steve,

yes, SABME are sended to provider:


debug isdn q921


Aug 28 12:38:55.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:38:55.961: ISDN Se0/2/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=12
Aug 28 12:38:56.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:38:57.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:03.441: ISDN Se0/2/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 28 12:39:03.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:04.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:05.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:05.969: ISDN Se0/2/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=12
Aug 28 12:39:06.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:12.441: ISDN Se0/2/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 28 12:39:12.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:13.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:14.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:15.441: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:15.976: ISDN Se0/2/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=12
Aug 28 12:39:21.440: ISDN Se0/2/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 28 12:39:21.440: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:22.440: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:23.440: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:24.440: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:25.980: ISDN Se0/2/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=12
Aug 28 12:39:30.440: ISDN Se0/2/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 28 12:39:30.440: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 12:39:31.440: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0


I also cleared counters and during ~10 minutes have no errors:


sh controllers E1 0/2/0
E1 0/2/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info Firmware: 20051006, FPGA: 20, spm_count = 0
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (551 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Andrey128 Sat, 08/28/2010 - 06:37
User Badges:

for ex. here is q921 dialog when I pluged router back to PBX:


Aug 28 13:29:06.386: %LINK-3-UPDOWN: Interface Serial0/2/0:15, changed state to down
Aug 28 13:29:07.406: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/2/0
Aug 28 13:29:08.386: %CONTROLLER-5-UPDOWN: Controller E1 0/2/0, changed state to up
Aug 28 13:29:08.386: ISDN Se0/2/0:15 Q921: L2_EstablishDataLink: sending SABME
Aug 28 13:29:08.386: ISDN Se0/2/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0
Aug 28 13:29:08.390: ISDN Se0/2/0:15 Q921: Net RX <- UAf sapi=0 tei=0                                       
Aug 28 13:29:08.390: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/2/0:15, TEI 0 changed to up
Aug 28 13:29:09.418: ISDN Se0/2/0:15 Q921: Net RX <- SABMEp sapi=0 tei=0
Aug 28 13:29:09.418: ISDN Se0/2/0:15 Q921: Net TX -> UAf sapi=0 tei=0
Aug 28 13:29:10.386: %LINK-3-UPDOWN: Interface Serial0/2/0:15, changed state to up
Aug 28 13:29:19.418: ISDN Se0/2/0:15 Q921: Net TX -> RRp sapi=0 tei=0 nr=0
Aug 28 13:29:19.422: ISDN Se0/2/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=0
Aug 28 13:29:29.421: ISDN Se0/2/0:15 Q921: Net TX -> RRp sapi=0 tei=0 nr=0
Aug 28 13:29:29.425: ISDN Se0/2/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=0


Router got UA and connection established.

Steven Holl Sat, 08/28/2010 - 06:42
User Badges:
  • Cisco Employee,

Your provider isn't responding to the SABME with a UA.  This is a provider issue.  Perhaps they don't have the circuit turned up completely.  If they push back, you will need to have them get a q.921 trap on their side and see if they see the SABME coming in, and if they show a UA in response.

Actions

This Discussion