Span Clock Problems

Hello,

we have a few setups with 2/3 D410P cards per server.
Each card has similar span configuration (all are E1 PRIs):
Span 1: clock source 1, pri_cpe (connected to telco)
Span 2: clock source 0, pri_net (connected to CPE equipment)
Span 3: clock source 0, pri_net (connected to CPE equipment)
Span 4: clock source 0, pri_net (connected to CPE equipment)
Span 5: clock source 1, pri_cpe (connected to telco)
Span 6: clock source 0, pri_net (connected to CPE equipment)
Span 7: clock source 0, pri_net (connected to CPE equipment)
Span 8: clock source 0, pri_net (connected to CPE equipment)
...

Everything works fine when Span 1 is connected to a telco
and draws clock from it. All spans work fine. When telco trunk
goes down or is unplugged, spans 2-4 start to flicker up/down,
report HDLC errors and so on. It clearly seems to be a timing issue,
like spans that are clock masters to CPE equipment fail to draw
clock from the card instead of telco.
We also tried to setup clocking as 1,2,3,4 instead of 1,0,0,0,
but nothing has changed.
This causes lots of problems, because when a telco trunk goes down
all 4 ports become unusable. Strange thing is that when telco trunk
is connected to each card, eveything works perfect.

hello, zvision:
please post your zaptel.conf, zapata.conf and your logs from asterisk.
Regards!
James.zhu

I use asterisk 1.4.17/zaptel 1.4.7.1.

My zaptel.conf:

span=1,1,0,ccs,hdb3,crc4
bchan=1-15
dchan=16
bchan=17-31
span=2,2,0,ccs,hdb3,crc4
bchan=32-46
dchan=47
bchan=48-62
span=3,3,0,ccs,hdb3
bchan=63-77
dchan=78
bchan=79-93
span=4,4,0,ccs,hdb3,crc4
bchan=94-108
dchan=109
bchan=110-124
span=5,1,0,ccs,hdb3,crc4
bchan=125-139
dchan=140
bchan=141-155
span=6,2,0,ccs,hdb3,crc4
bchan=156-170
dchan=171
bchan=172-186
span=7,3,0,ccs,hdb3,crc4
bchan=187-201
dchan=202
bchan=203-217
span=8,4,0,ccs,hdb3,crc4
bchan=218-232
dchan=233
bchan=234-248
span=9,1,0,ccs,hdb3,crc4
bchan=249-263
dchan=264
bchan=265-279
span=10,2,0,ccs,hdb3,crc4
bchan=280-294
dchan=295
bchan=296-310
span=11,3,0,ccs,hdb3,crc4
bchan=311-325
dchan=326
bchan=327-341
span=12,4,0,ccs,hdb3,crc4
bchan=342-356
dchan=357
bchan=358-372

My zapata.conf:
[channels]
language=pl
switchtype=euroisdn
nsf=none
pridialplan=unknown
prilocaldialplan=unknown
overlapdial=no
priindication=outofband
facilityenable=yes
usedistinctiveringdetection=no
usecallerid=yes
hidecallerid=no
callwaiting=no
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=no
transfer=no
canpark=no
cancallforward=no
callreturn=no
echocancel=no
echocancelwhenbridged=no
rxgain=0
txgain=0
immediate=no
transfertobusy=no
usesmdi=no
busydetect=no
callprogress=no
jbenable=no

context=dgt
signalling=pri_cpe
group=1
channel=>1-15,17-31
channel=>32-46,48-62
context=ext1
signalling=pri_net
group=2,7,8
channel=>63-77,79-93
context=ext2
group=3,7,8,9,10
channel=>94-108,110-124
context=dgt
signalling=pri_cpe
group=1
channel=>125-139,141-155
context=ext3
signalling=pri_net
group=4,7,8,9,10,11,12
channel=>156-170,172-186
context=ext4
group=5,7,8,9,10,11,12,13,14
channel=>187-201,203-217
context=ext5
group=6,7,8,9,10,11,12,13,14,15,16
channel=>218-232,234-248
signalling=pri_cpe
group=1
context=dgt
channel=>249-263,265-279
channel=>280-294,296-310
signalling=pri_net
group=19,7,8,9,10,11,12,13,14,15,16,17,18
context=ext6
channel=>311-325,327-341
group=20,7,8,9,10,11,12,13,14,15,16,17,18
context=ext7
channel=>342-356,358-372

Sample asterisk log lines (after span 5 goes down). Spans go up and down,
continuosly flooding with HDLC Abort till Span 5 from telco is up again:

[May 16 11:00] NOTICE[2529] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 5
[May 16 11:00] WARNING[2529] chan_zap.c: No D-channels available! Using Primary channel 140 as D-channel anyway!
...
[May 16 11:00] NOTICE[2532] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 8
[May 16 11:00] WARNING[2532] chan_zap.c: No D-channels available! Using Primary channel 233 as D-channel anyway!
[May 16 11:00] NOTICE[2532] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 8
...
[May 16 11:00] NOTICE[2532] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 8
[May 16 11:00] WARNING[2532] chan_zap.c: No D-channels available! Using Primary channel 233 as D-channel anyway!
[May 16 11:00] NOTICE[2532] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 8
...
[May 16 11:01] NOTICE[2531] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 7
[May 16 11:01] WARNING[2531] chan_zap.c: No D-channels available! Using Primary channel 202 as D-channel anyway!
[May 16 11:01] NOTICE[2531] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 7
[May 16 11:01] NOTICE[2531] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 7
[May 16 11:01] WARNING[2531] chan_zap.c: No D-channels available! Using Primary channel 202 as D-channel anyway!
...
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 6
[May 16 11:01] WARNING[2530] chan_zap.c: No D-channels available! Using Primary channel 171 as D-channel anyway!
...
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 8
[May 16 11:01] WARNING[2532] chan_zap.c: No D-channels available! Using Primary channel 233 as D-channel anyway!
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 8
...
[May 16 11:01] NOTICE[2531] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 7
[May 16 11:01] ERROR[2531] chan_zap.c: ACK received for '1' outside of window of '0' to '0', restarting
[May 16 11:01] WARNING[2531] chan_zap.c: No D-channels available! Using Primary channel 202 as D-channel anyway!
...
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 8
[May 16 11:01] WARNING[2532] chan_zap.c: No D-channels available! Using Primary channel 233 as D-channel anyway!
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 8
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 8
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 8
[May 16 11:01] WARNING[2531] chan_zap.c: Restart requested on odd/unavailable channel number 0/0 on span 7
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
...
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
...
[May 16 11:01] NOTICE[2531] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 7
...
[May 16 11:01] NOTICE[2531] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 7
[May 16 11:01] NOTICE[2532] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 8
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] WARNING[2532] chan_zap.c: Restart requested on odd/unavailable channel number 0/0 on span 8
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6
[May 16 11:01] NOTICE[2530] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 6

Just to clarify above test scenario - the first card has two telco lines,
span 1 and 2. If I unplug one of them (but not both), there is no problem.

Also there is no problem with missed interrupts or timer inaccuracy.
Each card has its own PCI interrupt line assigned exclusively and zttest
gives 99.99% results. All works fine with 3 cards loaded with traffic till
a telco pbx line is connected to each card.

And the last (but not least), we have a few similar boxes running and each
box has the same problem.