[asterisk-bugs] [Asterisk 0012694]: Bad disposition on originated IAX2 calls
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Aug 20 04:30:57 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12694
======================================================================
Reported By: yraber
Assigned To:
======================================================================
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-08-20 04:30 CDT
======================================================================
Summary: 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.
======================================================================
----------------------------------------------------------------------
(0091573) vdyjay (reporter) - 2008-08-20 04:30
http://bugs.digium.com/view.php?id=12694#c91573
----------------------------------------------------------------------
hi i have same issue but i have issue with ZAP channels..i am using .call
file to Call out.
cli shows
CLI> Attempting call on Zap/g1/9998073470 for s at outgoing:1 (Retry 1)
-- Requested transfer capability: 0x00 - SPEECH
[Aug 20 15:06:59] NOTICE[6084]: pbx_spool.c:341 attempt_thread: Call
failed to go through, reason (3) Remote end Ringing
this should be goes in to "no answer" but it shows
"9998073470","Zap/1-1",,"Dial","0","FAILED"
in /var/log/asterisk/cdr-custom/Master.csv
it works fine on BUSY scenario.
Issue History
Date Modified Username Field Change
======================================================================
2008-08-20 04:30 vdyjay Note Added: 0091573
======================================================================
More information about the asterisk-bugs
mailing list