Summary:ASTERISK-04227: fork_cdr gives wrong cdr data
Reporter:Roy Sigurd Karlsbakk (rkarlsba)Labels:
Date Opened:2005-05-19 04:44:48Date Closed:2011-06-07 14:10:24
Versions:Frequency of
Description:In case of diverts, I'm trying to use forkcdr to get sane CDR records. so A calls B and B is diverted to C, calling in I get one record saying A-B, which is ok, but then, after the ForkCDR, I get a record saying B-B instead of B-C. The following code is used for doing this (from AGI)

$AGI->exec('SetCallerID', "$extension");
$AGI->exec('ForkCDR', '');
$AGI->exec('Dial', "$current_pstngw/$divert_all_number");

Comments:By: Clod Patry (junky) 2005-05-20 15:54:50

Can ya provide more informations please? I'm not really sure to understand your point here.

Cause 1 cdr lines is created each time you make a dial.

By: Roy Sigurd Karlsbakk (rkarlsba) 2005-05-21 07:11:05

in case of diverts, I want one CDR record for incoming (xxx => mycid) and one for outgoing (mycid => yyy). My attempt at this was the following

exten => _X.,1,SetCallerID(${EXTEN})
exten => _X.,2,ForkCDR
exten => _X.,3,Dial(IAX2/blah:blah@blah/${DIVERTNUMBER})

This is how forkcdr is supposed to work, isn't it?


By: Russell Bryant (russell) 2005-05-26 18:49:20

Check out bug ASTERISK-2451.  I have a feeling this is the same issue...

By: Clod Patry (junky) 2005-06-09 18:39:08

what if you use v option?
If that doesn't work, could you try that directly in dialplan and post CLI's output?

By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-09 18:41:56

v option where?
i don't see a v option neither in forkcdr nor dial
mind, this is 1.0.7

By: Michael Jerris (mikej) 2005-06-10 06:07:43

Can you please test in head and see if this problem is reproducable in head.

By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-14 11:45:17

i have been asked to look into this to see if it's just a duplo
i'll do so as fast as possible
i meant to do this today, but was kept busy

By: Brian West (bkw918) 2005-06-15 01:15:44

ForkCDR allows you to stack/run concurrent CDR records on the same call.  Not start a new one.  If you wish to start a new one... you'll need to use ResetCDR.

Also NEVER do dial in an AGI its not the right thing to do.  Set a var .. exit the AGI then dial(${var})


By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-15 05:39:36

any particular reason why dial shouldn't be called from agi?

By: Michael Jerris (mikej) 2005-07-11 23:38:05

Suspended due to lack of response.. If we are to reopen this, we need test results from head, and to verify if this is a duplicate of another bug.