Jeremy Lichfield
2005-Jan-27 13:47 UTC
[Asterisk-Users] Outgoing call on Zap channel always gives DIALSTATUS ANSWER even when BUSY?
Outgoing call on Zap channel always gives DIALSTATUS ANSWER even when
BUSY? Has anyone run into this?
Here is my conf files:
Zaptel:
span=823,1,0,d4,ami
e&m=1-24
loadzone = us
defaultzone=us
Zapata:
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
busydetect=yes
context => incoming
signalling => em
group => 2
channel => 1-24
Extensions:
[default]
exten => 1000,1,Dial(Zap/g2/14356355785,10,tT)
exten => 1000,2,NoOp(Dial Status ${DIALSTATUS})
Sip:
[101]
type=friend
context=default
username=XXXXX
fromuser=XXXXX
secret=XXXXX
host=dynamic
dtmfmode=info
nat=yes
disallow=all
allow=g729
allow=ulaw
allow=alaw
restrictcid=yes
Am I doing something wrong? Or do I need something more?
Eric Wieling
2005-Jan-27 15:28 UTC
[Asterisk-Users] Outgoing call on Zap channel always gives DIALSTATUS ANSWER even when BUSY?
Jeremy Lichfield wrote:> Outgoing call on Zap channel always gives DIALSTATUS ANSWER even when > BUSY? Has anyone run into this?If you are using ANALOG ports then this is correct. The telco does not signal the status of the call so Asterisk must assume it's always answered as soon as it's done dialing. This does not apply to VoIP or T-1/E-1 PRI ports.
Reasonably Related Threads
- Help DIALSTATUS gives ANSWER when line is BUSY?
- Manager API on gives the DIALSTATUS of the first picked up channel?
- Re: I think your problem has to do with how you set the variable.
- T100P: Can't Make/Receive Zap Calls (Long Newbie Blah)
- FAST BUSY on Back to back ZAP outgoing calls