asterisk users - May 2007 - asterisk auto dial does not wait for answer

Hi All,

I setup auto dial on my asterisk server. The problem
is asterisk does not wait for called party to answer
the call but proceed to process the extension specifed
in my .call file

My sample call file :

hannel: local/0124787924@outbound-reminder
MaxRetries: 5
RetryTime: 300
WaitTime: 40
Account: Reminder
context: remindem
extension: s
priority: 1
Set: MSG=0135.20070601.0124787924
Set: APPTDT=20070601
Set: APPTTIME=0135
Set: APPTPHONE=0124787924
Set: CALLATTEMPTS=5
Set: CALLDELAY=300

My outbound-reminder context:

[outbound-reminder]
exten => _01N.,1,Dial(Zap/g1/${EXTEN},20)

My remindem context :

[remindem]
exten => s,1,Answer()
exten => s,2,Wait(2)
exten => s,3,Playback(custom/reminder5)

Once asterisk start to execute .call file, my handset
rings but the console shows Playback(custom/reminder5)


Below shows some console messages :

-- Attempting call on local/0124787924@outbound-reminder for s@remindem:1
(Retry 1)
    -- Executing [0124787924@outbound-reminder:1]
Dial("Local/0124787924@outbound-reminder-5223,2",
"Zap/g1/0124787924|20") in new stack
    -- Called g1/0124787924
    -- Zap/3-1 answered Local/0124787924@outbound-reminder-5223,2
[Jun  1 02:50:09] WARNING[8651]: pbx.c:4976 ast_pbx_outgoing_exten:
Local/0124787924@outbound-reminder-5223,1 already has a call record??
       > Channel Local/0124787924@outbound-reminder-5223,1 was answered.
    -- Executing [s@remindem:1]
Answer("Local/0124787924@outbound-reminder-5223,1", "") in
new stack
    -- Executing [s@remindem:2]
Wait("Local/0124787924@outbound-reminder-5223,1", "2") in
new stack
  == Spawn extension (outbound-reminder, 0124787924, 1) exited non-zero on
'Local/0124787924@outbound-reminder-5223,2'
    -- Executing [s@remindem:3] Playback("Zap/3-1",
"custom/reminder5") in
new stack



I really appreciate if some one can help me

Regards
ASLAY

Hi:

aslay@pinwee.com.my wrote:
> Hi All,
> 
> I setup auto dial on my asterisk server. The problem
> is asterisk does not wait for called party to answer
> the call but proceed to process the extension specifed
> in my .call file
This will not work with this channel driver. Explanation follows.
> 
> My sample call file :
> 
> hannel: local/0124787924@outbound-reminder
> MaxRetries: 5
> RetryTime: 300
> WaitTime: 40
> Account: Reminder
> context: remindem
> extension: s
> priority: 1
> Set: MSG=0135.20070601.0124787924
> Set: APPTDT=20070601
> Set: APPTTIME=0135
> Set: APPTPHONE=0124787924
> Set: CALLATTEMPTS=5
> Set: CALLDELAY=300
> 
> My outbound-reminder context:
> 
> [outbound-reminder]
> exten => _01N.,1,Dial(Zap/g1/${EXTEN},20)
Zaptel considers the call answered the moment it is bridged. You need
call progress detection of some kind. Are you using an analog card?

-Stephen-

Stephen Bosch wrote:
>> [outbound-reminder]
>> exten => _01N.,1,Dial(Zap/g1/${EXTEN},20)
> 
> Zaptel considers the call answered the moment it is bridged. You need
> call progress detection of some kind. Are you using an analog card?
This is not fully correct.

Calls going out FXO signaled ports are considered answered as soon as 
dialing is finished.  This applies to analog FXO ports, as well as FXO 
signaled T-1 channels.  It is not specific to Asterisk or Zaptel. 
Sangoma cards have the same issue.  ATAs with FXO ports have the same 
issue, so do channel banks, as do most PBXs.

This issue does not apply to FXS, E&M, PRI, VoIP, or most any other port 
types.