Configuring LBO on an E1 PRI in India - best practices

[cstennie]

Hi,

We are having several issues with an E1 PRI configuration we have implemented in India and are looking for any recommendations on best practices

Current configuration:

interface e1 0/1

  clock source line

  no snmp trap link-status

  tdm-group 1 timeslots 1-31 speed 64

  no shutdown

!

!

interface pri 1

  description INDIA PRI

  connect e1 0/1 tdm-group 1

  role user

  no shutdown

!

!

isdn-group 1

  connect pri 1

~~~~~~~~~~~~~~~~~~~~~

voice codec-list VOICE

  default

  codec g711alaw

  codec g729

!

voice codec-list FAX

  codec g711alaw

!

!

!

voice trunk T01 type sip

  sip-server primary x.x.x.x

  codec-group VOICE

!

voice trunk T02 type isdn

  description "PRI handoff to INDIA"

  resource-selection circular descending

  connect isdn-group 1

  match dnis "01191000XXXXXXXXXX" substitute "000XXXXXXXXXX"

  match dnis "01191000XXXXXXXXX" substitute "000XXXXXXXXX"

  match dnis "011911XXXXXXXXXX" substitute "1XXXXXXXXXX"

  match dnis "011911XXXXXXXXX" substitute "1XXXXXXXXX"

  match dnis "01191XXXXXXXXXX" substitute "0XXXXXXXXXX"

  match dnis "01191XXXXXXXXX" substitute "0XXXXXXXXX"

  match dnis "01191XXXXXXXX" substitute "0XXXXXXXX"

  rtp delay-mode adaptive

!

!

voice grouped-trunk SIP

  trunk T01

  accept $ cost 0

!

!

voice grouped-trunk PRI

  trunk T02

  accept $ cost 100

!

Below are some of the errors that we have been seeing in the logs:

Physical errors in the CPE logs:

E1.e1 0/1 Remote LOF, AIS

E1.e1 0/1 Tx Remote LOF, AIS, LOF

E1.e1 0/1 SEFS 15 min threshold exceeded

E1.e1 0/1 SEFS 24 hr
threshold exceeded

E1.e1 0/1 CSS 15 min threshold exceeded

E1.e1 0/1 ES 15 min threshold exceeded

E1.e1 0/1 CSS 24 hr threshold exceeded

E1.e1 0/1 DM 15 min threshold exceeded

E1.e1 0/1 DM 24 hr threshold exceeded

E1.e1 0/1 ES 24 hr threshold exceeded

E1.e1 0/1 Tx Remote LOF, LOF

Below are detailed ISDN warnings from the Adtran logs:

INTERWORKING_UNSPEC WARNING 12

Cause No. 127 - Intel-working, unspecified.

This cause indicates that an interworking call (usually a call to 5W56 service)
has ended



NO_CIRCUIT_AVAILABLE WARNING 34
Cause No. 34 - no circuit/channel available.

This cause indicates that there is no appropriate circuit/channel presently
available to handle the call.

What it means: There is no place on the Public Telephone network to place the
call; the call never gets to its destiation. This is usually a temporary problem.

NETWORK_CONGESTION WARNING 42
Cause No. 42 - switching equipment congestion.

This cause indicates that the switching equipment generating this cause is
experiencing a period of high traffic.

What it means: Just too much going on at this point on the ISDN network to get
the call through to its destination.

My question is, is there a better way for this area of the world that we could be configuring the line buildout for the PRI handoff?  The carrier has rand head to head testing from the CO to the site and does not see any of the errors that we are seeing in the Adtran logs.  We are also not seeing the customer maxing the concurrent sessions over the PRI, as it is only used to originate and terminate in country calls (the remainder are handled via SIP). 

[Anonymous]

I moved this post to the area, as I believe this applies to a NetVanta 6310.  If that is not correct please let us know which product you are using so we can put the post in the appropriate area so someone from the community can respond.

Thanks,

Matt

[Anonymous · Accepted solution]

Hello and thank you for posting to our forum.

India is currently not a supported country for AOS Voice.  You can try one of the system countries like ETSI and see if that will work for you.  Here is a link to the AOS Voice International Configuration Guide: 

If you issue the 'show clock' command you can see what country setting the unit is currently set for.

I noticed that OOF (out of frame) outputs.  It is possible that you are seeing this because of an incompatibility but it could also be something as simple as layer 1 cabling, so make sure you check that.  LBO is sometimes a trial and error setting as you may need to try different values until you find one that works.  Again, since India is not officially supported, I do not have any suggested settings to give you.

Thanks,

Geoff

[cstennie]

Thanks for the response -

The show clock command isn't showing the system country, but a verbose sh config does show it is currently set to etsi:

interface pri 1

  description INDIA PRI

  alias

  isdn switch-type etsi

  no isdn name-delivery

  isdn ringing-signal suppress

  no calling-party override

  calling-party presentation allowed

  no area-code

  no calling-party number

  calling-party name-facility-timeout 2

  connect e1 0/1 tdm-group 1

  digits-transferred all no-prefix

  redirecting-number as-received

  role user

  no isdn alert disable pi-8

  no isdn connect enable pi-2

  no isdn setup enable pi-1

  no isdn setup enable pi-3

  isdn setup enable redirecting-number

  isdn pi-location public

  no isdn supplementary-service ect

  snmp trap link-status

  no shutdown

!

!

isdn-group 1

  call-type analog

  incoming-accept-number $

  min-channels 0

  max-channels 0

  resource pool-member

  connect pri 1

Here are the current thresholds set (they should be currently at the default):

thresholds BES 15Min 10

thresholds BES 24Hr 100

thresholds CSS 15Min 1

thresholds CSS 24Hr 4

thresholds DM 15Min 1

thresholds DM 24Hr 4

thresholds ES 15Min 65

thresholds ES 24Hr 648

thresholds LCV 15Min 13340

thresholds LCV 24Hr 133400

thresholds LES 15Min 65

thresholds LES 24Hr 648

thresholds PCV 15Min 72

thresholds PCV 24Hr 691

thresholds SES 15Min 10

thresholds SES 24Hr 100

thresholds SEFS 15Min 2

thresholds SEFS 24Hr 17

thresholds UAS 15Min 10

thresholds UAS 24Hr 10

I wonder if anyone else has gotten this working.  I understand it isn't directly supported, but India does subscribe to the ETSI standard, so I'm hoping there are some adjustments that can be made.  Any other possible suggestions on what can be toggled?

[Anonymous]

My apologies.  I said 'show clock' and I meant 'show system.'

Regards,

Geoff

[cstennie]

GENESYS-CHENNAI-ADTRAN#sh system
ADTRAN, Inc. OS version A5.02.00.E
  Checksum: 892E04B7, built on Thu Nov 17 10:59:14 2011
Hardware version AA.2
Boot ROM version A3.01.B2
  Checksum: 637C, built on: Fri Dec 17 14:11:35 2010
Copyright (c) 1999-2010, ADTRAN, Inc.
Platform: Netvanta 6310, part number 1700100G1, CLEI code is N/A
Serial number xxx
Flash: 67108864 bytes  DRAM: 134217727 bytes

CHENNAI-ADTRAN uptime is 3 days, 6 hours, 32 minutes, 26 seconds

System returned to ROM by Warm Start
Current system image file is "NONVOL:/9700100G-2A502.biz"
Boot system image file is "NONVOL:/9700100G-2A502.biz"

Country setting is ETSI (Harmonized)
  Default GUI Language is English
  Default POTS Codec Country is ETSI (Harmonized)
  Default Companding is A-Law
  Default CallerID type is UK_CCA

System clock source configuration:  e1 0/1
System current active clock source:  e1 0/1

[Anonymous]

Hello,

Please send a show int e1 0/1 and show int pri 1.

Thanks,

Geoff

[cstennie]

e1 0/1 is UP
  Receiver has no alarms
  E1 coding is HDB3, framing is E1
  Clock source is line
  No network loopbacks
  Last clearing of "show interface" counters 6d 07:27:43
    loss of frame  : 0
    loss of signal : 0
    AIS alarm      : 0
    Remote alarm   : 0

  Timeslot Status: 01234567890123456789012345678901
                   FNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN
  Status Legend: '-' = Timeslot is unallocated
                 'N' = Timeslot is dedicated (nailed)
                 'F' = Timeslot is dedicated for framing

  Line Status: -- No Alarms --

  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  Current Performance Statistics:
    0 Errored Seconds, 0 Bursty Errored Seconds
    0 Severely Errored Seconds, 0 Severely Errored Frame Seconds
    0 Unavailable Seconds, 0 Path Code Violations
    0 Line Code Violations, 0 Controlled Slip Seconds
    0 Line Errored Seconds, 0 Degraded Minutes

  TDM group 1, line protocol is not set
    Encapsulation is not set

CHENNAI-ADTRAN#sh int pri 1
pri 1 is UP
  Description: RELIANT INDIA PRI
  Switch protocol:  ETSI 300 403
  Signaling role:  user (TE)
  Calling-party override:  disabled
  Calling-party presentation:  allowed
  Calling-party number:  (no number configured)
  digits transferred all
  ISDN name-delivery:  disabled
  progress indicator #8 in alerting message:  enabled
  progress indicator #2 in connect message:  disabled
  progress indicator #1 in setup message:  disabled
  progress indicator #3 in setup message:  disabled
  progress indicator location:  public
  resource-selection: circular descending
  ECT:  disabled
  area code:
  Transmission of redirecting numbers is enabled
  Redirecting numbers: sent as received
  Connected interface: e1 0/1 tdm-group 1
  Channel status 1234567890123456789012345678901
                 ...............D...............
    Legend: - = Unallocated        . = Inactive
            A = Active B channel   B = Backup D channel
            D = Active D channel   M = Maintenance
            R = Restart
  Last clearing of "show interface" counters: never
    58937 packets input, 262787 bytes, 0 no buffer
    0 runts, 0 giants, 0 throttles
    2 input errors, 2 CRC, 0 frame
    0 abort, 0 discards, 0 overruns
    58938 packets output, 265497 bytes, 0 underruns

[Anonymous]

Hello,

From these screens the PRI looks up and the e1 is clean.  From the output shown in the first couple messages, it looked like e1 timing was an issue.  The ADTRAN is set to receive timing from e1 0/1.  Can you verify the layer 1 cabling?  Do you have any show int e1 0/1 outputs that show errors on the e1?

Regards,

Geoff

[Anonymous]

Hello,

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it and select another in its place with the applicable buttons.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

Geoff