Asterisk 12 – CDR Changes

Home » Asterisk Users » Asterisk 12 – CDR Changes
Asterisk Users 2 Comments

Hello everyone, I am upgrading from release 1.8 and I have a strange behavior with CDR
generation. We are using a Redirect server for Number portability, and I see that once the call is going through the Redirect Server additional CDR records are generated – we have 3 additional records. This Behavior is different then what we had on Release 1.8.

Does anyone have a clue how to remove these CDR records?

2 thoughts on - Asterisk 12 – CDR Changes

  • Can you publish a short stub of your dial plan to see what you are doing? There are the NoCDR, ForkCDR, and ResetCDR applications that might help.

    jg

  • Due to core changes that occurred in Asterisk 12, CDRs were completely redone. There wasn’t much way around having to do that; the old CDR
    behaviour was tightly integrated with the old bridging code, and when that bridging code went, CDRs had to be get reworked as well. This was noted strongly in both the UPGRADE notice delivered with Asterisk, as well as on the Upgrading to Asterisk 12 wiki page:

    https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+12

    Depending on your dialplan – and what the channel does as it moves through the dialplan – it would not be surprising to find records you didn’t have in the past. The philosophy with CDRs in Asterisk 12 is to show you what the channel did as it moved around, rather than try to hide information. In the past, Asterisk would frequently get this
    ‘hiding’ wrong, much to many people’s consternation. This does mean you may have to post-process your records; luckily, as jg pointed out, there are still plenty of ways to manipulate CDRs through the dialplan.

    A specification for CDR behaviour in Asterisk 12 is available on the Asterisk wiki:

    https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification