<span class="Apple-style-span" style="border-collapse: collapse; ">Dear members of the list;<br><br>I am writing in the hope to get some help with a very peculiar problem with my new asterisk <a href="http://1.6.0.1" target="_blank" style="color: rgb(92, 69, 32); ">1.6.0.1</a> installation. The same code runs on version 1.2 without problems, but it seems the behaviour has changed (also on 1.4.7, which I tried).<br>
<br>Please consider the following extension:<br><br>exten => 1213,1,Answer<br>exten => 1213,n,Set(counter=X)<br>exten => 1213,n(again),Set(CDR(accountcode)=forkcdr-test)<br>exten => 1213,n,Set(CDR(userfield)= ${counter})<br>
exten => 1213,n,ForkCDR()<br>exten => 1213,n,Playback(one-moment-please)<br>exten => 1213,n,Wait(3)<br>exten => 1213,n,Set(counter=X${counter})<br>exten => 1213,n,Goto(again)<br>exten => 1213,n,Hangup<br>
<br>If left running, the above code should produce multiple Call Data Records, each with a longer sting of "X"s in the userfield. This is indeed also the case on my 1.2 installation, but on 1.4.7 and <a href="http://1.6.0.1" target="_blank" style="color: rgb(92, 69, 32); ">1.6.0.1</a>, only one record (the first) is written.<br>
<br>After a lot of testing, I discovered that if I add the "R" option to the ForkCDR command (to prevent it from resetting the new CDR), multiple records are in fact written, but they all contain the same call-info:<br>
<br>"fork-cdr-test",,,,,"ForkCDR","R","2008-11-20 09:00:28","2008-11-20 09:00:28","2008-11-20 09:00:40",12,12,,,"1227171628.5","I"<br>"fork-cdr-test",,,,,"ForkCDR","R","2008-11-20 09:00:28","2008-11-20 09:00:28","2008-11-20 09:00:40",12,12,,,"1227171628.5","II"<br>
"fork-cdr-test",,,,,"ForkCDR","R","2008-11-20 09:00:28","2008-11-20 09:00:28","2008-11-20 09:00:40",12,12,,,"1227171628.5","III"<br>"fork-cdr-test",,,,,"","Wait","3","2008-11-20 09:00:28","2008-11-20 09:00:28","2008-11-20 09:00:40",12,12,,,"1227171628.5","III"<br>
<br>This suggests to me, that the broken (?) behaviour may be in the reset function rather than in the ForkCDR itself.<br><br>I have also noticed that the unique-id column now contains the UNIX timestamp. Since the timestamp is the same for all the records, it's hardly "unique". I tried changing the "loguniqueid" parameter in cdr.conf, but with no effect.<br>
<br>Any help or suggestions on the above issues would be greatly appreciated.<br>Thank you very much in advance.<div><p><span style="font-size: 10pt; color: black; "><br>Best Regards</span></p><p>Torben</p></div></span>