Hello:
Has anyone got foolproof zapata.conf settings for Bell Canada ISDN service?
Here's what I have:
group = 3
context = trunk
usecallerid=yes
callerid=asreceived
switchtype=national
nsf = none
overlapdial = no
signalling = pri_cpe
resetinterval=300
priindication=inband
accountcode = outside
channel => 49-71
I am having disposition FAILED show up on my CDR. /var/log/asterisk
Messages gives me:
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Executing Dial("Zap/23-1",
"Zap/r3/xxxxxxxxxx") in new stack
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Requested transfer
capability: 0x10 - 3K1AUDIO
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Called r3/xxxxxxxxxx
Sep 29 16:00:29 VERBOSE[9220] logger.c: -- Channel 0/9, span 3 got
hangup
Sep 29 16:00:29 VERBOSE[9220] logger.c: -- Channel 0/9, span 3 received
AOC-E charging 909389878 units
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Zap/57-1 is circuit-busy
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Hungup 'Zap/57-1'
Sep 29 16:00:29 VERBOSE[10135] logger.c: == Everyone is busy/congested at
this time (1:0/1/0)
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Executing
Congestion("Zap/23-1", "") in new stack
Sep 29 16:00:29 VERBOSE[10135] logger.c: -- Hungup 'Zap/23-1'
I changed the resetinterval to 300 in an attempt to release busy circuits.
I changed the dial command to group r3 to round-robin my calls out, to avoid
circuit-busy's. For about 2 minutes today, all of my circuits reported as
congested.
I have Asterisk 1.2.7-1 with a Sangoma A104D card.
?
Regards,
Mark McQuiggan
_
This message and any attachments are intended only for the use of the addressee
and
may contain information that is privileged and confidential. If the reader of
the
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
