[asterisk-bugs] [Asterisk 0012694]: [patch] Bad disposition on originated IAX2 calls

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12694 
====================================================================== 
Reported By:                yraber
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   12694
Category:                   Applications/app_cdr
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.19 
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-05-21 02:43 CDT
Last Modified:              2008-11-25 15:52 CST
====================================================================== 
Summary:                    [patch] Bad disposition on originated IAX2 calls
Description: 
When using asterisk manager or a call files to originate a IAX2 call,
disposition in cdr is always FAILED on unanswered calls (BUSY, NO ANSWER or
FAILED).

* I was able to reproduce this with asterisk manager and call files, it
makes no difference.
* The problem does not appear when originating to a SIP trunk.
* The problem does not appear if the call is externally originated (a SIP
phone i.e.).

I've attached a IAX debug for the simplest case I could think about :
originating a call with a call files, and the called line was busy on
purpose. This resulted in a FAILED disposition in the CDR, who should
obviously be BUSY.
====================================================================== 

---------------------------------------------------------------------- 
 (0095514) murf (administrator) - 2008-11-25 15:52
 http://bugs.digium.com/view.php?id=12694#c95514 
---------------------------------------------------------------------- 
Laura-- it is normal for patches to have line offsets when applied to
different versions; as long as it applied, you are, in the vast majority of
cases, OK.

I usually test and apply changes to the "latest" version of a release in
SVN.

You can get that by making sure that subversion is installed on your
machine, and doing this command:

svn co http://svn.digium.com/svn/asterisk/branches/1.4

It will create a '1.4' directory and populate it with the latest version.

Over time, your copy will get outdated. You can update your copy with:

svn update   (after you cd into the 1.4 dir, of course).

It's entirely possible that problems you might want to report have already
been solved in following releases (1.4.19 isn't the latest release any
more). It's always good to verify that the problem hasn't been fixed by
checking out the release from SVN and giving it a quick spin to verify. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-25 15:52 murf           Note Added: 0095514                          
======================================================================