[asterisk-users] libpri error??
andrew.mcrory at sayso.net
Wed Mar 14 12:27:47 CDT 2012
I have a client who's taking intermittent errors on their PRI. The server is
configured with one PRI from the TELCO, and two PRI connecting to their Iwatsu
ADIX legacy system. The odd thing is, the system can run for days, weeks or
months without a reported error and then just bomb. The only thing that fixes
it is stopping and starting the services. It then runs well for a random time
period. I've upgraded and downgraded software, even tried new hardware and
CentOS 5.x. none of these changes have made a difference.
Now here's the crazy thing, this system ran fine for a couple years BEFORE a
change in the local provider(from Level 3 to CenturyLink). CL claims that they
do nothing different from Level 3 but we noticed right away that we had to
adjust the pridialplan to get outbound to work. So much for that. I figured
there was a problem with the circuit. So we worked with Sangoma and the Telco
to troubleshoot the problem. After a lot of ordeal, Sangoma cleared the Telco
and said "the problem is most likely in libpri".
I upgraded libpri to SVN release 2279 and that seemed to be the fix we needed.
We had a couple errors but figured they were in the dialplan, made some
adjustments and it ran clean. We noticed a few errors on the Telco PRI so I
upgraded to libpri 2283.
This time everything ran so clean, we thought our problems were behind us.
Unfortunately for us, this morning everything went haywire. The Iwatsu could
not make internal or outbound calls via the PRI. SIP users on the asterisk
server could not call out and I could not call in. The message was "All
circuits busy". A quick restart and everything is back.
The TELCO swears it's not their problem and upgrading libpri to SVN have
seemed to help. I'm hoping someone here can provide some insight.
I have an IDSN pcap from this morning and the relevant log file located here:
I just realized that debugging was not set in asterisk so this is probably not
enough information to get started. What should I set debug level to next time?
I will do that and turn on debugging on span 1. Anyway, if there's anything
that can be done now....
Here's my /etc/dahdi/system.conf
#autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
#autogenrated on 2012-02-29
#Dahdi Channels Configurations
#For detailed Dahdi options, view /etc/dahdi/system.conf.bak
#Sangoma A104 port 1 [slot:4 bus:9 span:1] <wanpipe1>
#Sangoma A104 port 2 [slot:4 bus:9 span:2] <wanpipe2>
#Sangoma A104 port 3 [slot:4 bus:9 span:3] <wanpipe3>
#Sangoma A104 port 4 [slot:4 bus:9 span:4] <wanpipe4>
;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
;autogenrated on 2012-02-29
;Dahdi Channels Configurations
;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak
; Required for Embarq / CenturyTel
;Sangoma A104 port 1 [slot:4 bus:9 span:1] <wanpipe1>
;Sangoma A104 port 2 [slot:4 bus:9 span:2] <wanpipe2>
;Sangoma A104 port 3 [slot:4 bus:9 span:3] <wanpipe3>
;Sangoma A104 port 4 [slot:4 bus:9 span:4] <wanpipe4>
# WANPIPE1 Configuration File
# Date: Wed Dec 6 20:29:03 UTC 2006
# Note: This file was generated automatically
# by /usr/local/sbin/setup-sangoma program.
# If you want to edit this file, it is
# recommended that you use wancfg program
# to do so.
# Sangoma Technologies Inc.
wanpipe1 = WAN_AFT_TE1, Comment
w1g1 = wanpipe1, , TDM_VOICE, Comment
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 9
FE_MEDIA = T1
FE_LCODE = B8ZS
FE_FRAME = ESF
FE_LINE = 1
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
TE_HIGHIMPEDANCE = NO
TE_RX_SLEVEL = 360
HW_RJ45_PORT_MAP = DEFAULT
LBO = 0DB
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 1
TDMV_DCHAN = 24
TE_AIS_MAINTENANCE = NO #NO: defualt YES: Start port in AIS Blue
Alarm and keep line down
#wanpipemon -i w1g1 -c Ttx_ais_off to disable
AIS maintenance mode
w1g1 -c Ttx_ais_on to enable AIS maintenance mode
TDMV_HW_DTMF = NO # YES: receive dtmf events from hardware
TDMV_HW_FAX_DETECT = NO # YES: receive fax 1100hz
events from hardware
HWEC_OPERATION_MODE = OCT_NORMAL # OCT_NORMAL: echo cancelation enabled
with nlp (default)
# OCT_SPEECH: improves software tone detection by disabling NLP (echo possible)
# OCT_NO_ECHO:disables echo cancelation but allows VQE/tone functions.
HWEC_DTMF_REMOVAL = NO # NO: default YES: remove dtmf out of
incoming media (must have hwdtmf enabled)
HWEC_NOISE_REDUCTION = NO # NO: default YES: reduces noise on the line
- could break fax
HWEC_ACUSTIC_ECHO = NO # NO: default YES: enables acustic echo
HWEC_NLP_DISABLE = NO # NO: default YES: guarantees software tone
detection (possible echo)
HWEC_TX_AUTO_GAIN = 0 # 0: disable -40-0: default tx audio level
to be maintained (-20 default)
HWEC_RX_AUTO_GAIN = 0 # 0: disable -40-0: default tx audio level
to be maintained (-20 default)
HWEC_TX_GAIN = 0 # 0: disable -24-24: db values to be
applied to tx signal
HWEC_RX_GAIN = 0 # 0: disable -24-24: db values to be
applied to tx signal
ACTIVE_CH = ALL
TDMV_HWEC = YES
MTU = 8
Sayso Communications, Inc.
2850 Industrial Plaza
Tallahassee, Florida 32301
More information about the asterisk-users