[asterisk-bugs] [Asterisk 0014935]: Asterisk auto dial out will execute immediatetly no matter the receiver reponse for the call or not

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14935 
====================================================================== 
Reported By:                daichaoshui
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14935
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-04-19 23:36 CDT
Last Modified:              2009-04-20 08:38 CDT
====================================================================== 
Summary:                    Asterisk auto dial out will execute immediatetly no
matter the receiver reponse for the call or not
Description: 
I am using Asterisk 1.6.0 + Dahdi2.1.0.4
I want to make some auto dial out using dahdi channel.
The dial out will call some customer and play some messages.

The problem is :
The auto dial out can send the call to the user, but no matter the user
response the call or not, the messages will play immediate.It seems the
dahdi auto dial out can not get the status of (no answer, congestion,
etc...)

here is my auto dialout
Channel: DAHDI/g0/13********
MaxRetries: 0
RetryTime: 30
WaitTime: 45
Context: call-to-cust
Extension: 200
Priority: 1
Archive: Yes

Set: OrderInfo_id=1
Set: OrderInfo_PLACE=2
Set: OrderInfo_TIME=2
Set: OrderInfo_isHavePlace=1

here is the context in extensions_custom.conf
[call-to-cust] 
exten => 200,1,Ringing
exten => 200,1,Answer()
exten => 200,n,Wait(3) 
exten => 200,n(Response),Background(custom/FoodOrder-ResponseToCustNotice)

exten => 200,n,ExecIf($["${FOORODER_PLACE_${OrderInfo_PLACE}}" !=
""]?Background(${FOORODER_PLACE_${OrderInfo_PLACE}})) 
exten => 200,n,ExecIf($["${FOORODER_TIME_${OrderInfo_TIME}}" !=
""]?Background(${FOORODER_TIME_${OrderInfo_TIME}})) 
exten => 200,n,ExecIf($["${FOORODER_isHavePlace_${OrderInfo_isHavePlace}}"
!= ""]?Background(${FOORODER_isHavePlace_${OrderInfo_isHavePlace}})) 
exten => 200,n,SET(FoodOrders_updCloseToUserOrder(${OrderInfo_id}))
exten => 200,n,Playback(vm-goodbye)
exten => 200,n,Hangup()

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0014934 Asterisk auto dial context execute no m...
====================================================================== 

---------------------------------------------------------------------- 
 (0103448) file (administrator) - 2009-04-20 08:38
 http://bugs.digium.com/view.php?id=14935#c103448 
---------------------------------------------------------------------- 
This is to be expected on FXO ports. On analog signaling we are not
provided with a way to determine the progress the call is making (whether
it is ringing, etc). Instead we are simply provided with an audio stream.
That means as soon as you dial out an FXO port it will be considered
answered. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-20 08:38 file           Note Added: 0103448                          
2009-04-20 08:38 file           Status                   new => resolved     
2009-04-20 08:38 file           Resolution               open => no change
required
2009-04-20 08:38 file           Assigned To               => file            
2009-04-20 08:38 file           Status                   resolved => closed  
======================================================================