[asterisk-bugs] [Asterisk 0012318]: Originate call is already answered even if destination channel is still ringing

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12318 
====================================================================== 
Reported By:                krtorio
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   12318
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0-beta5 
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-03-28 03:26 CDT
Last Modified:              2008-09-09 12:36 CDT
====================================================================== 
Summary:                    Originate call is already answered even if
destination channel is still ringing
Description: 


All calls made through the manager command Originate call are already
answered (which in turn starts the billsec timer) even if the destination
channel is still ringing and hasn't answered the source channel. 

This of course will give out an incorrect billsec value (ex. nonzero value
even if dest. channel rejects source channel) and will affect the accuracy
of our talktime reports.

Seems that the issue exists since version 1.4.9, I reported a similar case
like this (http://bugs.digium.com/view.php?id=10444).



Problem is easily reproducible:
extensions.conf:
exten => _6XX,1,Dial(SIP/${EXTEN},60,tr)

in manager interface:
Action: Originate
Channel: SIP/660
Exten: 676
Context: outgoing
Priority: 1

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

---------------------------------------------------------------------- 
 (0092266) murf (administrator) - 2008-09-09 12:36
 http://bugs.digium.com/view.php?id=12318#c92266 
---------------------------------------------------------------------- 
OK, this bug has been in feedback since June. I'm in a CDR frame of mind,
and a lot of water has gone under the bridge since then, so to speak, so I
labbed this one up, and tested to see what the problems were.

In my case, I send a call file:

Action: Originate
Channel: Sip/snom360
Exten: 842
Priority: 1
Context: extension

which initiates a call from my snom360 to exten 842, which in AEL:

Dial(SIP/polycom430|25|Tt);

I let the first phone ring a long time. The second phone I quickly pick up
and set back down to complete the call.

I get the following cdr_custom:

"","","842","extension","SIP/snom360-0822bbc0","SIP/polycom430-08231050","Dial","SIP/polycom430|25|Tt","2008-09-09
11:22:00","2008-09-09 11:22:14","2008-09-09 11:22:15","15","1","NO
ANSWER","DOCUMENTATION","","1220980920.0","",""


The answer to end time is correct; however, the disposition is set to "NO
ANSWER", which is incorrect. The CID info is missing. I will assume that
the missing CID info is due to the fact that the manager initiating the
call interrupted the normal setting of these fields. I will investigate
these problems and see if a fix can be made. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-09 12:36 murf           Note Added: 0092266                          
======================================================================