[asterisk-users] yellow alarm after weeks without trouble

[Jean-Denis Girard]

Hi list,

I'm getting an error on a E1 link to the telco, after some weeks of
operation without trouble.

I have an asterisk with a TE405 in passtrough mode: two E1 are connected
to the Telco, two E1 are connected to 2 Siemens PaBX. Only 15 channels
are used on each E1 (conf is attached).The system has been in production
for nearly a year, and does work flawlessly for weeks, then I
mysteriously get errors on the first PRI span, which is used as primary
clocking source. It happened again this Sunday (while the system was
idle), after six weeks of operation without trouble. Call are dropped, 
and users are angry. It has happened  4-5 times during one year. 
Reloading zaptel modules and restarting asterisk does bring the system 
back to normal.
As far as I can tell, pri debug span 1 shows nothing special (see
attached log).
The Telco says that there is "drift in the synchronization".
System load as shown by top is very low, vmstat shows no CPU spikes,
TE405P has its on interrupt. I already changed the TE405P.
I have other similar systems running without any trouble, so any idea
about improving this installation would be welcome. I can provide more
info if needed. Main differences with my other similar installations 
are: two E1 are used, and system is 64 bit (Asus MB with Opteron).


Thanks,
-- 
Jean-Denis Girard

SysNux                  Systèmes Linux en Polynésie française
http://www.sysnux.pf/   Tél: +689 483 527 / GSM: +689 797 527
-------------- next part --------------
# Zaptel.conf: fichier de configuration bas niveau de zaptel
# SysNux 07/12/2005
# Jean-Denis Girard <jd.girard at sysnux.pf>

loadzone=fr
defaultzone=fr

# 4 canaux T2 (2 sur OPT, 2 sur PaBX). Chaque T2 utilise seulement 
# les 15 premiers canaux B

span=1,1,0,ccs,hdb3
bchan=1-15
dchan=16
#bchan=17-31

span=2,2,0,ccs,hdb3
bchan=32-46
dchan=47
#bchan=48-62

span=3,0,0,ccs,hdb3
bchan=63-77
dchan=78
#bchan=79-93

span=4,0,0,ccs,hdb3
bchan=94-108
dchan=109
#bchan=110-124


-------------- next part --------------
; Zaptata.conf: fichier de configuration des interfaces zap
; 4 T2: 2 connectés à l'OPT, 2 connectés au PaBX
; sur chaque T2 seulement 15 canaux B utilisés
; SysNux 07/12/2005
; Jean-Denis Girard <jd.girard at sysnux.pf>

[channels]
language=fr
switchtype=EuroISDN
usecallerid=yes
callwaiting=no
callwaitingcallerid=no
threewaycalling=no
transfer=no
cancallforward=no
callreturn=no
echocancel=yes
echocancelwhenbridged=yes

pridialplan=national
prilocaldialplan=national
internationalprefix=00
nationalprefix=0689

overlapdial=yes
callerid=asreceived
immediate=no ; XXX

; 2 premiers T2 connectés à l'OPT
context=entrant
signalling=pri_cpe
group=1
channel => 1-15
;channel => 17-31
channel => 32-46
;channel => 48-62

; 2 derniers T2 connectés au PaBX
context=sortant
signalling=pri_net
immediate=no
group=2
channel => 63-77
;channel => 79-93
channel => 94-108
;channel => 110-124


-------------- next part --------------
A non-text attachment was scrubbed...
Name: debug.bz2
Type: application/x-bzip2
Size: 5724 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20070206/d86518da/debug.bin