David Zuzga
2004-Mar-12 10:53 UTC
[Asterisk-Users] callprogress on outgoing calls placed via /var/spool/asterisk/outgoing
Hi, I am having problems with answer detection on a Wildcard X100p. Here is the issue: When placing a call by copying a sample.call file into /var/spool/asterisk/outgoing, the call is made, but execution of the context continues immediately after dialing. I would like to wait until the callee answers before proceeding in the context. If I uncomment the "callprogress=yes" in zapata.conf, the context just hangs at step 1 and never proceeds onwards. No call progress messages are output or anything. Is this due to the "experimental" nature of call progress detection, or am I doing something wrong? Thanks, Dave extensions.conf ---------------- [callme] exten => s,1,Answer exten => s,2,Playback(demo-congrats) exten => s,3,Hangup zapata.conf ------------ [channels] context=default signalling=fxs_ks ;callprogress=yes echocancel=yes echotraining=yes channel=>1 sample.call ----------- Channel: Zap/1/<phone # here> MaxRetries: 0 RetryTime: 60 WaitTime: 30 Context: callme Extension: s Priority: 1 zaptel.conf ----------- defaultzone=us loadzone=us fxsks=1
Eric Wieling
2004-Mar-12 22:13 UTC
[Asterisk-Users] callprogress on outgoing calls placed via /var/spool/asterisk/outgoing
If you want reliable progress (busy, answer, etc) you must use a digital line like a T-1 and/or PRI. It's as simple as that. There is no way for the X100P to know when the call has been answered since analog lines do not signal that. callprogress tries to fake it by listening to the audio and guessing, but it usually causes random hangups in the middle of calls instead. David Zuzga (dzuzga@isdinc.com) wrote:> > Hi, > > I am having problems with answer detection on a Wildcard X100p. Here is the > issue: > > When placing a call by copying a sample.call file into > /var/spool/asterisk/outgoing, the call is made, but execution of the context > continues immediately after dialing. I would like to wait until the callee > answers before proceeding in the context. > > If I uncomment the "callprogress=yes" in zapata.conf, the context just hangs > at step 1 and never proceeds onwards. No call progress messages are output > or anything. Is this due to the "experimental" nature of call progress > detection, or am I doing something wrong? > > Thanks, > > Dave > > extensions.conf > ---------------- > [callme] > exten => s,1,Answer > exten => s,2,Playback(demo-congrats) > exten => s,3,Hangup > > zapata.conf > ------------ > [channels] > context=default > signalling=fxs_ks > ;callprogress=yes > echocancel=yes > echotraining=yes > channel=>1 > > sample.call > ----------- > Channel: Zap/1/<phone # here> > MaxRetries: 0 > RetryTime: 60 > WaitTime: 30 > Context: callme > Extension: s > Priority: 1 > > zaptel.conf > ----------- > defaultzone=us > loadzone=us > fxsks=1 > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > >