[asterisk-bugs] [Asterisk 0013216]: Incorrect ANSWERTIME when using M option

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13216 
====================================================================== 
Reported By:                ruddy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13216
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-31 19:10 CDT
Last Modified:              2008-10-14 12:11 CDT
====================================================================== 
Summary:                    Incorrect ANSWERTIME when using M option
Description: 
Here is the situation we have.
When somebody call extension 1000, we start AGI 'agicaller.php'
that will try to call 10 people one after another.
For each person, if the other party answer the channel, with option
M(agicallee.php),
we check if the other person accept the call and if yes, we connect both
parties.
If not, we try the next person and so on.


Now, after looking at app_dial.c, I realize that,
ANSWEREDTIME is not set to 0 when we enter dial application and is setup
only when after the BRIDGE.

So, if somebody reject the call and the agicallee.php macro setup
MACRO_RESULT to CONGESTION, the
DIALSTATUS is set to ANSWERED but ANSWEREDTIME is not reset and have the
same value as the last Dial that was made by that call.

I think :
1. Everytime, we enter dial_exec_full, we should reset ANSWEREDTIME to 0
2. Setup ANSWEREDTIME for every situation where the call was answered, not
only when it was bridge.
   Because the agicallee.php can take 5 minutes to execute and set
MACRO_RESULT to CONGESTION after all.


I hope I was enough clear in my explanations.
Thanks.

====================================================================== 

---------------------------------------------------------------------- 
 (0093619) blitzrage (administrator) - 2008-10-14 12:11
 http://bugs.digium.com/view.php?id=13216#c93619 
---------------------------------------------------------------------- 
Hrmmm... I'm not entirely sure Asterisk is doing something wrong here. It
does seem to make sense that ANSWEREDTIME is the value past the channels
being bridged, because that is technically when they are answered.

However following through your explaination I'm slightly confused as to
whether you're saying the value isn't started until the call is actually
bridged, or whether you're getting a value that is the total time from the
initial call being loaded?

I've assigned this issue to Corydon76 as maybe he has a better idea as to
what is going on here, and to determine whether Asterisk is doing the right
thing. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-14 12:11 blitzrage      Note Added: 0093619                          
======================================================================