On Sat, 10 Jan 2004, Steven Critchfield waxed:
On Sat, 2004-01-10 at 15:19, John Brown (CV) wrote:
busydetect=yes
callprogress=yes
musiconhold=default
signalling=pri_cpe
group=1
channel= 1-4
Well seems you haven't been on the list, or maybe you haven't been
paying attention since we have been covering that problem for a while
lately. PRI has busydetect and callprogress built into the D channel and
is absolutely known. Those 2 options are for analog links where the
signaling is not always accurate.
Easy, now. I just added another T1, and I have noticed the
D-Channel dropping for a few seconds then coming right back,
fortunately in the wee hours when no one's on the lines.
But I have both busydetect and callprogress off, with a T400
tho not a T100.
Here's some zaptel.conf:
span=1,0,0,esf,b8zs
span=2,0,0,esf,b8zs
span=3,1,0,esf,b8zs
span=4,0,0,esf,b8zs
First 2 spans are channel banks, span 3 is local T1, and
span 4 is long distance T1. The D-Channel only appears to
drop on span 4, although I can't yet get the time to play
wire/card-swap much due to the machine being in production.
Both T1's are from the same switch, so I'm told, so it
should be the same clock.
Here's some log:
Jan 9 04:22:05 WARNING[5126]: File chan_zap.c, Line 5759 (zt_pri_error): PRI: Read on
106 failed: Unknown error 500
Jan 9 04:22:05 WARNING[6151]: File chan_zap.c, Line 4708 (handle_init_event):
Detected alarm on channel 73: Red Alarm
Jan 9 04:22:05 WARNING[6151]: File chan_zap.c, Line 1101 (zt_disable_ec): Unable to
disable echo cancellation on channel 73
Jan 9 04:22:05 WARNING[6151]: File chan_zap.c, Line 4708 (handle_init_event):
Detected alarm on channel 74: Red Alarm
Jan 9 04:22:05 WARNING[6151]: File chan_zap.c, Line 1101 (zt_disable_ec): Unable to
disable echo cancellation on channel 74
...last 2 lines repeated for each channel on span 4 (up to channel 95) all at the
same time
Jan 9 04:22:11 NOTICE[6151]: File chan_zap.c, Line 4703 (handle_init_event): Alarm
cleared on channel 73
Jan 9 04:22:11 NOTICE[6151]: File chan_zap.c, Line 4703 (handle_init_event): Alarm
cleared on channel 74
...again repeated at the same time for every channel on span 4
Jan 9 04:22:11 WARNING[5126]: File chan_zap.c, Line 5759 (zt_pri_error): PRI: Read on
106 failed: Unknown error 500
Jan 9 04:22:14 VERBOSE[5126]: == D-Channel on span 4 down
Jan 9 04:22:20 VERBOSE[5126]: == D-Channel on span 4 up
...and then the B-Channels start coming back up
I'm trying to blame it on the mobo and the telco, but now
that someone else is seeing it, maybe it's * ? It wasn't a
problem when I had one T1, and span 3 doesn't seem to ever
drop, so maybe it's something with the span 4 port on the
T400 card ? Or is this some side-effect of the known
buffering problem ?
--Chris
--
Chris Maj cmaj_hat_freedomcorpse_hot_info
Pronunciation Guide: Maj == May
Fingerprint: 43D6 799C F6CF F920 6623 DC85 C8A3 CFFE F0DE C146
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
