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

[noreply at bugs.digium.com]

The following issue requires your FEEDBACK. 
====================================================================== 
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:             03-28-2008 03:26 CDT
Last Modified:              06-23-2008 10:53 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

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

---------------------------------------------------------------------- 
 murf - 06-23-08 10:53  
---------------------------------------------------------------------- 
Interesting. I read 10444 (it's been a while!), and noted that I mentioned
better behavior in CDRfix5... so, since you are reporting this against
1.6.0,
I suggest you check out:

http://svn.digium.com/svn/asterisk/team/murf/CDRfix6

and see if your problem is solved without the resetCDR call.

Since I fully intend to merge the CDRfix6 and CDRfix4 branches soon, it
would be good to have feedback against these branches!
 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-23-08 10:53  murf           Note Added: 0089093                          
06-23-08 10:53  murf           Status                   assigned => feedback
======================================================================