Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
774
Views
0
Helpful
5
Replies

Intermittent Problem in Outgoing calls using PRI lines

dileepkumar
Level 1
Level 1

‎05-06-2015 05:46 AM - edited ‎03-17-2019 02:54 AM

Hi,

I am getting below errors intermittently. This problem happens sometimes once in a day and sometime two times a day.

I have attached the voice gateways configuration, isdn debug and output of E1 card as a reference. I spoke with Telco guys but as per them there is no issue from their side.

 Cause i = 0x80E6 - Recovery on timer expiry

 Cause i = 0x80E20D - Message not compatible with call state or not implemented

 

Output of Debug ISDN Q931
======================

Bearer Capability i = 0x8090A3
  Standard = CCITT
  Transfer Capability = Speech 
  Transfer Mode = Circuit
  Transfer Rate = 64 kbit/s
 Channel ID i = 0xA98392
  Exclusive, Channel 18
 Calling Party Number i = 0x0081, '043749317'
  Plan:Unknown, Type:Unknown
 Called Party Number i = 0x80, '0079618448428'
  Plan:Unknown, Type:Unknown
000705: *May  6 08:11:29.124: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8  callref = 0x8ADF
 Channel ID i = 0xA98392
  Exclusive, Channel 18
000706: *May  6 08:11:32.072: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8AB9
000707: *May  6 08:11:32.080: ISDN Se0/0/1:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 043648682
000708: *May  6 08:11:32.084: ISDN Se0/0/1:15 Q931: Sending SETUP  callref = 0x0AE0 callID = 0x8CA9 switch = primary-net5 interface = User
000709: *May  6 08:11:32.084: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8  callref = 0x0AE0
 Bearer Capability i = 0x8090A3
  Standard = CCITT
  Transfer Capability = Speech 
  Transfer Mode = Circuit
  Transfer Rate = 64 kbit/s
 Channel ID i = 0xA98381
  Exclusive, Channel 1
 Calling Party Number i = 0x0081, '043648682'
  Plan:Unknown, Type:Unknown
 Called Party Number i = 0x80, '0077015118998'
  Plan:Unknown, Type:Unknown
000710: *May  6 08:11:32.084: ISDN Se0/0/1:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x0AE0
 Cause i = 0x80E6 - Recovery on timer expiry
000711: *May  6 08:11:32.096: ISDN Se0/0/1:15 Q931: RX <- SETUP_ACK pd = 8  callref = 0x8AE0
 Channel ID i = 0xA98381
  Exclusive, Channel 1
000712: *May  6 08:11:32.096: ISDN Se0/0/1:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 11, call id 0x8CA9, call ref 0xAE0, event 0xD
000713: *May  6 08:11:32.096: ISDN Se0/0/1:15 Q931: TX -> STATUS pd = 8  callref = 0x0AE0
 Cause i = 0x80E20D - Message not compatible with call state or not implemented
 Call State i = 0x0B
000714: *May  6 08:11:32.100: ISDN Se0/0/1:15 Q931: RX <- RELEASE pd = 8  callref = 0x8AE0
000715: *May  6 08:11:32.100: ISDN Se0/0/1:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x0AE0
000716: *May  6 08:11:32.124: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x8ADF
000717: *May  6 08:11:33.640: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x8ABB
000718: *May  6 08:11:33.648: ISDN Se0/0/1:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 044387486
000719: *May  6 08:11:33.648: ISDN Se0/0/1:15 Q931: Sending SETUP  callref = 0x0AE1 callID = 0x8CAA switch = primary-net5 interface = User
000720: *May  6 08:11:33.648: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8  callref = 0x0AE1
 Bearer Capability i = 0x8090A3
  Standard = CCITT
  Transfer Capability = Speech 
  Transfer Mode = Circuit
  Transfer Rate = 64 kbit/s
 Channel ID i = 0xA98381
  Exclusive, Channel 1
 Calling Party Number i = 0x0081, '044387486'
  Plan:Unknown, Type:Unknown
 Called Party Number i = 0x80, '0079122597976'
  Plan:Unknown, Type:Unknown
000721: *May  6 08:11:33.656: ISDN Se0/0/1:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x0AE1
 Cause i = 0x80E6 - Recovery on timer expiry
000722: *May  6 08:11:33.664: ISDN Se0/0/1:15 Q931: RX <- SETUP_ACK pd = 8  callref = 0x8AE1
 Channel ID i = 0xA98381
  Exclusive, Channel 1
000723: *May  6 08:11:33.668: ISDN Se0/0/1:15 Q931: RX <- RELEASE pd = 8  callref = 0x8AE1
000724: *May  6 08:11:33.668: ISDN Se0/0/1:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 11, call id 0x8CAA, call ref 0xAE1, event 0xD
000725: *May  6 08:11:33.668: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 044550227
000726: *May  6 08:11:33.668: ISDN Se0/0/0:15 Q931: Sending SETUP  callref = 0x0AE2 callID = 0x8CAB switch = primary-net5 interface = User
000727: *May  6 08:11:33.668: ISDN Se0/0/1:15 Q931: TX -> STATUS pd = 8  callref = 0x0AE1
 Cause i = 0x80E20D - Message not compatible with call state or not implemented
 Call State i = 0x0B
000728: *May  6 08:11:33.668: ISDN Se0/0/1:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x0AE1

 

Output of show controllers E1 
========================

voice-gateway#sh controllers e1

E1 0/0/0 is up.

  Applique type is Channelized E1 - balanced

  No alarms detected.

  alarm-trigger is not set

  Version info FPGA Rev: 08121917, FPGA Type: PRK4

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

  International Bit: 1, National Bits: 11111

  Data in current interval (554 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 18 15 minute intervals):

     179 Line Code Violations, 24 Path Code Violations,

     1 Slip Secs, 0 Fr Loss Secs, 3 Line Err Secs, 0 Degraded Mins,

     7 Errored Secs, 5 Bursty Err Secs, 0 Severely Err Secs, 100 Unavail Secs

E1 0/0/1 is up.

  Applique type is Channelized E1 - balanced

  No alarms detected.

  alarm-trigger is not set

  Version info FPGA Rev: 08121917, FPGA Type: PRK4

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

  International Bit: 1, National Bits: 11111

  Data in current interval (554 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

     12 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

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

  Total Data (last 18 15 minute intervals):

     315 Line Code Violations, 16 Path Code Violations,

     352 Slip Secs, 0 Fr Loss Secs, 5 Line Err Secs, 0 Degraded Mins,

     358 Errored Secs, 3 Bursty Err Secs, 0 Severely Err Secs, 110 Unavail Secs

E1 0/1/0 is down.

  Applique type is Channelized E1 - balanced

  Transmitter is sending remote alarm.

  Receiver has loss of signal.

  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.

  Data in current interval (554 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, 554 Unavail Secs

  Total Data (last 18 15 minute intervals):

     1541 Line Code Violations, 33 Path Code Violations,

     161 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins,

     161 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 1655 Unavail Secs

 

Labels:
Preview file
12 KB
0 Helpful
5 Replies 5

Robert Shaw
Level 3
Level 3

‎05-06-2015 05:54 AM

I see that all the errors in the above output relate to ISDN Se0/0/1:15.  Have you noticed that the errors you receive are only referring to this port alone?  If so, have you tried moving the cable from this port and putting it in a different port to see if the error follows it.  If the error follows the move to another port, it is likely a problem with the ISDN Provider.  If the errors stay on the same port then it would be a config or hardware issue.

0 Helpful

dileepkumar
Level 1
Level 1
In response to Robert Shaw

‎05-06-2015 05:59 AM

Hi Robert Shaw,

We have three PRIs and when the issue happens users wont be able to make outgoing calls, sometimes there is  a delay and sometimes it gives fast busy tone.

I have attached the sample output. I have seen the same errors on all the other PRIs and different channels.

 

0 Helpful

Robert Shaw
Level 3
Level 3
In response to dileepkumar

‎05-06-2015 06:33 AM

Hi,

Which country are these installed in?  It looks like a Line Code or framing issue, suggested by your show controllers e1 output.  Normally the default framing is CRC4, whereas you have specifically configured No CRC4.

Thanks

Rob

0 Helpful

dileepkumar
Level 1
Level 1
In response to Robert Shaw

‎05-06-2015 06:44 AM

Hi Robert,

I have confirmed with Telco they has disabled the CRC4, so it should be NO-CRC4.

We follow European standard and we are located in Dubai, United Arab Emirates.

I am still not able to understand the full meaning of the below two ISDN Errors.

 Cause i = 0x80E6 - Recovery on timer expiry

 Cause i = 0x80E20D - Message not compatible with call state or not implemented

 Its very strange that the same configuration works fine most of the time and when the issue occurs it does not work and this issue automatically get resolve.

I believe this issue is from the Telco side but Telco guys are not co-operative. I have requested them to share the output of E1 Controllers  but still no luck.

0 Helpful

Robert Shaw
Level 3
Level 3
In response to dileepkumar

‎05-06-2015 07:17 AM

Hi,

I'm more concerned by the Line Code and Path Code violations.

Line Code Violations occur with an incorrect Line Code specified in the Controller Config.  There are only two options for this and the default is HDB3 which you have set, I have never seen anyone use AMI on an E1 circuit.  You could of course try it.

The Path Code Violations are framing issues, you have confirmed with the Telco that they use NO CRC4, so your config there is also correct.

I would clear the controllers to reset the counters with "clear controllers e1 0 0" etc.  Then repeatedly run sh controllers e1 making a note each time of the Line code and Path code violations.  If they continue to increase then the problem is related to the Telco.

If one thing is standard all over the world the Telco will always tell you that the problem is not theirs.

Thanks

Rob

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents