We are having several issues with an E1 PRI configuration we have implemented in India and are looking for any recommendations on best practices
interface e1 0/1
clock source line
no snmp trap link-status
tdm-group 1 timeslots 1-31 speed 64
interface pri 1
description INDIA PRI
connect e1 0/1 tdm-group 1
connect pri 1
voice codec-list VOICE
voice codec-list FAX
voice trunk T01 type sip
sip-server primary x.x.x.x
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
accept $ cost 0
voice grouped-trunk PRI
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
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)
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).