Well, I think this should be a critical feature to implement for the next releases of Asterisk (hopefully * 1.6), I've read a lot of this matter in the list and in the bug tracker. I think the more insightful reading about this topic can be found in this link: http://www.asterisk.org/node/48358
I know Murf that you are working hard on this, I'm sure all of us on the list encourage you to keep doing your great work... Since the billable time of a call composed of several transfers depends on the policy established for it (by this I mean to whom charge for the whole call), may I suggest that the "Future Wonderful CDR" needs to include a "Policy Manager" (the first term that comes to my mind) that allows you to sets how to account for it??? Maybe just a new parameter in cdr*.conf named "whotobill" or some similar with values that describe the initiator of the call, the person who gets the transfer (in case of a requested call to the operator) and so on... Thanks Greyman for your response, best regards... -- Raul Gomez Linux Counter #156439 On Thu, Apr 17, 2008 at 9:35 AM, Grey Man <[EMAIL PROTECTED]> wrote: > Hi Raul, > > CDR's for transfers are beyond the ability of Asterisk. > > http://lists.digium.com/pipermail/asterisk-users/2008-January/204856.html > http://bugs.digium.com/view.php?id=11093 > > It's not something the powers that be want to think about a design for > and the solution that's been suggested is to date it to use a > different type of server software, such as a SIP Proxy, to generate > the CDR's (something easy to suggest and complicated to do). > > You're not the only one affected by this and there is no fix. > > Regards, > > Greyman. > -users <http://lists.digium.com/mailman/listinfo/asterisk-users> >
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users