[Home]

Summary:ASTERISK-13910: Asterisk call file has CDR always set to NO ANSWER
Reporter:Ruddy G (ruddy)Labels:
Date Opened:2009-04-07 09:48:18Date Closed:2009-08-05 12:28:24
Priority:MajorRegression?No
Status:Closed/CompleteComponents:CDR/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) p.call
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
Comments:By: Mark Michelson (mmichelson) 2009-04-07 19:11:29

Could you upload the call file you are using? Thanks!
By: Ruddy G (ruddy) 2009-04-09 10:52:23

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@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@testcontext:2] Ringing("DAHDI/189-1", "") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing [102@testcontext:3] Answer("DAHDI/189-1", "") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing [102@testcontext:4] NoOp("DAHDI/189-1", "YYYYYYYYYY NO ANSWER") in new stack
[Apr  9 11:40:27] VERBOSE[21844] logger.c:     -- Executing [102@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@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
By: rmartinez (rmartinez) 2009-04-29 11:15:10

Hello.
I'm having the exact same problem.  I'm using Asterisk version 1.4.24.1 with manager running from another machine.  The manager try to make a call as follows

Action: Originate\r\nChannel: SIP/PRUEBA/0056233418\r\nContext: context-PRUEBA\r\nTimeout: 10000\r\nexten: s\r\nPriority: 1\r\n\r\n

the debug from the console is as follows :

== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'admin' logged on from 10.0.0.207
    > Channel SIP/PRUEBA-09d5c090 was answered.
-- Executing [s@context-PRUEBA:1] Set("SIP/PRUEBA-09d5c090", "CALLERID(name=PRUEBA") in new stack
-- Executing [s@context-PRUEBA:2] Set("SIP/PRUEBA-09d5c090", "CALLERID(num)=") in new stack
-- Executing [s@context-PRUEBA:3] Set("SIP/PRUEBA-09d5c090", "IND=1") in new stack
-- Executing [s@context-PRUEBA:4] Answer("SIP/PRUEBA-09d5c090", "") in new stack
-- Executing [s@context-PRUEBA:5] SetMusicOnHold("SIP/PRUEBA-09d5c090", "default") in new stack
-- Executing [s@context-PRUEBA:6] BackGround("SIP/PRUEBA-09d5c090", "oruxintro") in new stack
-- <SIP/PRUEBA-09d5c090> Playing 'oruxintro' (language 'en')
== Spawn extension (context-PRUEBA, s, 6) exited non-zero on 'SIP/PRUEBA-09d5c090'
== Manager 'admin' logged off from 10.0.0.207

I'm pretty sure that the call was answered (in fact i'm answering the call).  But there is no trace from the call in the CDR, if i set to "yes" the "unanswered" field in the cdr.conf i have the CDR but with "NO ANSWER".

+---------------------+-------------------------+--------------+-----+----------------+--------------------------+------------+------------+------------------------------+----------+---------+-------------+----------+-------------+--------------+-----------+
| calldate            | clid                    | src          | dst | dcontext       | channel                  | dstchannel | lastapp    | lastdata                     | duration | billsec | disposition | amaflags | accountcode | uniqueid     | userfield |
+---------------------+-------------------------+--------------+-----+----------------+--------------------------+------------+------------+------------------------------+----------+---------+-------------+----------+-------------+--------------+-----------+
| 2009-04-29 10:01:48 | PRUEBA                  |              | s   | context-PRUEBA | SIP/PRUEBA-09d5c090      |            | BackGround | oruxintro                    |       14 |       0 | NO ANSWER   |        3 |             | 1241013708.3 |           |
+---------------------+-------------------------+--------------+-----+----------------+--------------------------+------------+------------+------------------------------+----------+---------+-------------+----------+-------------+--------------+-----------+


Any ideas?
Ricardo.-


I forgot to add the dialplan :

[ Context 'context-PRUEBA' created by 'pbx_config' ]
 's' =>            1. Set(CALLERID(name)=PRUEBA)                 [pbx_config]
                   2. Set(CALLERID(num)=${DEST})                 [pbx_config]
                   3. Set(IND=1)                                 [pbx_config]
                   4. Answer()                                   [pbx_config]
                   5. SetMusicOnHold(default)                    [pbx_config]
                   6. Background(oruxintro)                      [pbx_config]
                   7. Hangup()                                   [pbx_config]


By: Alex Fishlock (fishloa) 2009-05-26 18:40:54

I see exactly this issue with this version of asterisk
Asterisk 1.6.0.5
Built from source myself
By: Vadim Mikhnevych (vmikhnevych) 2009-06-30 03:46:44

We had the same issue on 1.6.1.1. Main problem was billsec=0.
The solution/workaround looks a bit magical, but it worked for us. In cdr.conf there is a "unanswered=no" default value. We changed it to "yes", but it didn't help. BUT, then we changed it back to "no", and after that billsec was correct and calls were marked ANSWERED.
By: Leif Madsen (lmadsen) 2009-07-13 10:35:01

Assigned to mnicholson to take a look to determine if there is anything to be done here. Thanks!
By: Matthew Nicholson (mnicholson) 2009-07-13 17:31:01

Is this still a problem with the svn branch of 1.4?
By: Matthew Nicholson (mnicholson) 2009-07-20 12:32:20

Please test with the SVN branch of asterisk 1.4 and report your results here.


By: Abhishek Singh (bailoo) 2009-07-24 13:50:01

I see the same behavior when initiating calls with .call files on asterisk 1.4.24. disposition is "no answer" and billsec = 0 even when the outgoing calls are answered.
By: Matthew Nicholson (mnicholson) 2009-07-28 17:08:24

Again, please test with the SVN branch of asterisk 1.4.
By: Matthew Nicholson (mnicholson) 2009-07-29 15:17:21

I cannot reproduce this with asterisk 1.4 SVN r208377.
By: Leif Madsen (lmadsen) 2009-08-05 12:28:23

As mnicholson has tried several times to reproduce this issue and cannot, I'm closing this as "unable to reproduce". If the reporter can find myself or mnicholson on IRC in #asterisk-bugs (irc.freenode.net), then we can perhaps figure out why you're seeing this issue, but he cannot.

Thanks!