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

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12318 
====================================================================== 
Reported By:                krtorio
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12318
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
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:             03-28-2008 03:26 CDT
Last Modified:              03-28-2008 06:31 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

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

---------------------------------------------------------------------- 
 davidw - 03-28-08 06:31  
---------------------------------------------------------------------- 
I suspect you may need more than one option.  I assume that the original
intended use of Originate was for achieving something like predictive
dialling, or for completely automated messages.  In that case, the first
party is likely to be a toll number in most parts of the world, and one may
want the billing information to reconcile toll costs.

Are you trying to bill for the agent's time, or are you making the local
party the first party? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-28-08 06:31  davidw         Note Added: 0084687                          
======================================================================