TB2.6.1 and CDRs

Hello

I have just upgraded my 2.2 platform to a 2.6.1 release.

as part of my testing i have notice quite a few changes in respect of CDR content. i presume this is more of an Asterisk issue but i do not know

i have an issue with the content of CDRs in call transfer cases. wondering if anyone can comment.

i note -
inbound trunk (SIP or IAX) call to extension transferred to trunk (SIP or IAX) does not show the outbound called number unless one looks into the "lastdata" CDR field.

ditto for inbound trunk call to extension transferred to extension (no lastdata, internal call so less of an issue) and for extension to extension call transferred to a trunk (number is in lastdata)

for inbound trunk call to extension, extension to trunk, and an extension to trunk call transferred to another extension, the CDR data is pretty much what one would expect.

i also note that there are somewhat more CDR records now generated for a given scenario involving transfer of the call. this seems to be unnecessary and confusing (and a pain for my billing program !!!)

anyhow, wondering if anyone else has seen this and also knows whether
a) one can control where one generates CDRs
b) one can control the relevant content (i would rather retain format and content of TB2.2 !)

with the case of inbound trunk to extension being transferred externally again i have a potential fraud issue as without looking at the lastdata field (which my billing system does not today) i cannot bill the outbound call. so my final question is
c) whether anyone knows how one can block a trunk to trunk transfer if necessary to prevent the fraudulent case from occurring (prior to billing system upgrade or (a) and (b) being addressed).

thanks in advance for any suggestions

david