On Sat, Jan 17, 2009 at 3:08 AM, Steve Murphy <[email protected]> wrote: > Greyman-- > > I've been thinking of Benny Amorsen's comments on Simple CDRs... > > >> This is tricky... I need to create these CDR's for the billing system: >> >> src: A start: e1 ans: e2 end: e6 dst: B disp: ANSW >> src: A start: e4 ans: e5 end: e6 dst: B disp: ANSW >> >> If I do the same substitution again, I get this: >> >> A->B start: e1 ans: e2 end: e4. Whoops, end time is wrong. >> A->C start: e1 ans: e5 end: e4. Whoops, both start and end times are >> wrong. >> >> CDR2 needs to find e1 so it can replace start, while CDR3 shouldn't >> have anything replaced. I can't think of a query which will do this >> correctly. > > Do you have any ideas that might make this work for him? > I guess simple CDR's won't work for everyone, but... if they > could work in this case.... >
>From what I can gather the problem Benny has is getting the src field correct for a transfer. In the traditional Telco World the src (or A Number) field tends to be both the callerid of the customer and an identifier that ties the CDR to the customer for billing purposes. With Asterisk and a lot of other modern day softswitches there's usually a field called accountcode or similar which can be used to tie a CDR to a customer. The src field is then only fulfilling one role which is to hold the callerid that was set or recieved for the call. The trick with transfers is to forget about the src field for billing purposes and make sure the accountcode for the call is set in accordance with the business rules. For example if two customers A and B are talking to each other and A blind transfers B to a billable destination Z then who pays for the call from B to Z? There is no right answer but as far as the CDRs are concerned it's irrelvant as long as each call is recorded and the accountcode can be set within the dialplan both choices can be accomodated. With the simple CDR approach it could end up that there are multiple CDRs for a customer for the one call since they could be charged for both ends of a transfer. I don't see that as an issue. Regards, Greyman. _______________________________________________ -- 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
