ISDN Layer 2 State = TEI_ASSIGNED

Unanswered Question
Oct 17th, 2011

Hello All,

Can anyone please help me troubleshooting below issue: I have a E1 PRI connected to voice router, show controller e1 shows

E1 0/0/0 is up.

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20100222, FPGA: 13, spm_count = 0

Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.

Framing mentioned above is confirmed by the PTT ; Isdn switch-type configured at present is:  isdn switch-type primary-net5

When I do debug isdn q921 below is what I get:

*Oct 17 14:03:35.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:36.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:37.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:40.608: ISDN Se0/0/1:15 Q921: L2_EstablishDataLink: sending SABME

*Oct 17 14:03:40.608: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:41.608: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:42.608: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:43.608: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:43.632: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

*Oct 17 14:03:43.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:44.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:45.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Oct 17 14:03:46.632: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

When I do debug isdn q931 below is the info I get:

*Oct 17 14:05:14.616: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Oct 17 14:05:17.632: ISDN Se0/0/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Oct 17 14:05:23.616: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Oct 17 14:05:26.632: ISDN Se0/0/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

show isdn status gives below message:

Global ISDN Switchtype = primary-net5

ISDN Serial0/0/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

        TEI = 255, Ces = 255, SAPI = 0, State = TEI_ASSIGNED

    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 = 10

What can be reason for this ?? And what should be the approch to fix this issues.

Many Thanks in advance for your advise !!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
kebrenna Mon, 10/17/2011 - 07:14

Hi,

The telco isn't responding to your SABME's, call telco and have them troubleshoot issue with you from their end.

Thanks,

Kevin

anil.sharma.411... Mon, 10/17/2011 - 07:18

Hello Kevin,

Many thanks for your swift response.

Do you think I need to change any config on my router as per telco advise to make it work ??

Anything like isdn switch type or something else to be changed ???

I will contact telco accordingly...

Thanks

Anil Sharma.

kebrenna Mon, 10/17/2011 - 07:24

Hi Anil,

Configs look ok, the telco should be able to confirm what switch type you need. Also, if it was a wrong switch type, I would still expect to see something come back in response. I would just call up the telco and have them check out the circuit.

Thanks,

Kevin

skarth43@ford.com Mon, 10/17/2011 - 20:41

Hello Anil,

I have encountered similar problem couple of weeks before. Before that let me know what protocol are you using ? MGCP / H323 ?

My client was using MGCP gateway and I too was getting similar SABME messages. All I have done was I removed the L3 bind and readd it, which resolved the issue.

Under the serial interface remove the isdn bind command and do a

shut/no shut.

Thanks,

Karthik

anil.sharma.411... Mon, 10/17/2011 - 22:41

Hi Kevin,

Thanks for your response I will check with Telco as well..

Hi Karthik,

Thank you... My client is using H.323 gateway .. Any ideas ??

Thanks,

Anil Sharma

learner2008 Sun, 06/03/2012 - 14:09

Hi Anil,

I am experiencing exact same issue with a newly installed ISR 2951 gateway router. Telco has performed full T1 test at their demark point but didn't find any issues. they are using esf as framing and b8zs as line code. I am wondering if your this issue has ever got fixed. if yes, could you please let me know the root cause?

thanks,

Jessica

Chris Deren Sun, 06/03/2012 - 14:16

Jessica,

Can you post "sh controller t1" and "debug isdn q921"?

Have you tried different cable?

Chris

learner2008 Sun, 06/03/2012 - 14:32

hi Chris,

Please see the output below -

"Debug ISDN q921"

May 31 18:11:25.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:26.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:27.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:28.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:34.799: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME
May 31 18:11:34.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:35.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:36.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:37.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:43.799: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME
May 31 18:11:43.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:44.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:45.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0
May 31 18:11:46.799: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

"Show Controller T1" -

T1 0/0/0 is up.

  Applique type is Channelized T1

  Cablelength is long 0db

  No alarms detected.

  alarm-trigger is not set

  Soaking time: 3, Clearance time: 10

  AIS State:Clear  LOS State:Clear  LOF State:Clear

  Version info FPGA Rev: 08121917, FPGA Type: PRK1

  Framing is ESF, Line Code is B8ZS, Clock Source is Line.

  CRC Threshold is 320. Reported from firmware  is 320.

  Data in current interval (435 seconds elapsed):

     3563085 Line Code Violations, 145448 Path Code Violations

     8 Slip Secs, 15 Fr Loss Secs, 435 Line Err Secs, 0 Degraded Mins

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 435 Unavail Secs

  Total Data (last 24 hours)

     696713734 Line Code Violations, 28206938 Path Code Violations,

     1566 Slip Secs, 377 Fr Loss Secs, 86352 Line Err Secs, 0 Degraded Mins,

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs

SEA2VGW#clear counte T1 0/0/0 is up.
  Applique type is Channelized T1
  Cablelength is long 0db
  No alarms detected.
  alarm-trigger is not set
  Soaking time: 3, Clearance time: 10
  AIS State:Clear  LOS State:Clear  LOF State:Clear
  Version info FPGA Rev: 08121917, FPGA Type: PRK1
  Framing is ESF, Line Code is B8ZS, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (435 seconds elapsed):
     3563085 Line Code Violations, 145448 Path Code Violations
     8 Slip Secs, 15 Fr Loss Secs, 435 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 435 Unavail Secs
  Total Data (last 24 hours)
     696713734 Line Code Violations, 28206938 Path Code Violations,
     1566 Slip Secs, 377 Fr Loss Secs, 86352 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs

Thanks,

Jessica Wang

Chris Deren Sun, 06/03/2012 - 16:26

telco is not responding to your TX with Rx, try different cable if that does not help contact telco provider to troubleshoot the d-channel not coming up.

Sent from Cisco Technical Support iPad App

malbaqari Sun, 06/03/2012 - 17:39

Hi Anil,

You may try different cable however I don't think that this is the problem since your L1 is Active  as per isdn status. Also, you confirmed that framing and line coding settings are confirm by teleco. Now for L2 status, 3 things you need to check with teleco:

1. isdn switch type?

2. isdn incoming-voice settings, is it voice or modem?

3. cross check that they are using isdn protocol-emulation as network?

Hi Jessica,

You may check the same thing, however, I can see lot of line code violations in your controller status. You may cross check framing and line coding settings with your teleco.

  3563085 Line Code Violations, 145448 Path Code Violations

anil.sharma.411... Mon, 06/04/2012 - 07:31

Hello Jessica,

A conference call was arrange with telco and after they confirmed.

ISDN switch type was changed from primary-net5 to primary-qsig and it fixed the issue.

Hope this helps !!

Regards,

Anil Sharma.

learner2008 Mon, 06/04/2012 - 08:43

Hi Anil,

Thanks so much for your reply.

Hi Mohammed,

To answer your questions -

1> ISDN switch type -  Per Telco, they uses NI2 as protocol and 5ESS as switch-type. I tried both 'Primary-NI' and 'Primary-5ESS" but got same issue

2> isdn incoming-voice settings, is it voice or modem? - it is set to Voice

3> cross check that they are using isdn protocol-emulation as network? - I will verify with Telco. I have tried 'isdn protocol-emulation network' under serial interface and same issue.

Per Telco (which is Century Link), they use B8ZS as linecoding and ESF for framing. They have been configured exactly same on the 2951 router. it is interesting that T1 interface does come up tremendous amount of linecode violations.

Jessica Wang

Actions

Login or Register to take actions

This Discussion

Posted October 17, 2011 at 7:08 AM
Stats:
Replies:12 Avg. Rating:
Views:5012 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard