[asterisk-bugs] [Asterisk 0014844]: Asterisk call file has CDR always set to NO ANSWER

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14844 
====================================================================== 
Reported By:                ruddy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14844
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-07 09:48 CDT
Last Modified:              2009-04-09 10:52 CDT
====================================================================== 
Summary:                    Asterisk call file has CDR always set to NO ANSWER
Description: 
I'm having a weird behaviour with outgoing calls generated by call file
into /var/spool/asterisk/outgoing

When the callee answers the call, and the call is forward to an extension
where we answer it, we still have 'NO ANSWER' as CDR disposition
====================================================================== 

---------------------------------------------------------------------- 
 (0103005) ruddy (reporter) - 2009-04-09 10:52
 http://bugs.digium.com/view.php?id=14844#c103005 
---------------------------------------------------------------------- 
Here is the dialplan 

exten => 102,1,Noop(" XXXXXXXX " ${UNIQUEID} ${CDR(disposition)})
exten => 102,n,Ringing
exten => 102,n,Answer
exten => 102,n,Noop(YYYYYYYYYY ${CDR(disposition)})
exten => 102,n,Playback(tt-weasels)
exten => 102,n,Hangup


And here is the output


[Apr  9 11:40:27] VERBOSE[21844] logger.c:        > Channel DAHDI/189-1
was answered.
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing
[102 at testcontext:1] NoOp("DAHDI/189-1", "" XXXXXXXX " 1239291619.78485 NO
ANSWER") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing
[102 at testcontext:2] Ringing("DAHDI/189-1", "") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing
[102 at testcontext:3] Answer("DAHDI/189-1", "") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing
[102 at testcontext:4] NoOp("DAHDI/189-1", "YYYYYYYYYY NO ANSWER") in new
stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing
[102 at testcontext:5] Playback("DAHDI/189-1", "tt-weasels") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- <DAHDI/189-1> Playing
'tt-weasels' (language 'en')
[Apr  9 11:40:30] VERBOSE[21844] logger.c:     -- Executing
[102 at testcontext:6] Hangup("DAHDI/189-1", "") in new stack
[Apr  9 11:40:30] VERBOSE[21844] logger.c:   == Spawn extension
(testcontext, 102, 6) exited non-zero on 'DAHDI/189-1'
[Apr  9 11:40:30] DEBUG[21844] chan_dahdi.c: Set option AUDIO MODE, value:
ON(1) on DAHDI/189-1
[Apr  9 11:40:30] DEBUG[21844] chan_dahdi.c: Not yet hungup...  Calling
hangup once with icause, and clearing call
[Apr  9 11:40:30] DEBUG[21844] chan_dahdi.c: Set option AUDIO MODE, value:
OFF(0) on DAHDI/189-1


And we have a NO ANSWER in the CDR as well 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-09 10:52 ruddy          Note Added: 0103005                          
======================================================================