Yeah, meaning that when A calls B with callerID of 123 and B transfers A to C and while doing that the callerID is changed to 456 (callerID from B) then the CDR will show 456 is src. If you are trying to do billing based on this info then you are out of luck, as this is not accurate, rather look at account code as an option.
On 10/11/05, Rod Bacon <[EMAIL PROTECTED]> wrote: > I posted something on this a week ago, at which time I was told that this was > an > 'old' issue. Since then, I've spent hours looking, but can't find the answer. > > For some reason, some of my CDRs (both to CSV and MySQL) are being written > with > the wrong callerid. As best as I can determine, they are being written with > the > CLID of the _last_ caller to access the specific ZAP channel in question, not > the current one. > > Has anyone ever seen this before? > > -- > ========================================== > Rod Bacon > Empowered Communications > Ground Floor, 102 York St. South Melbourne > Victoria, Australia. 3205 > Phone: +613 99401600 Fax: +613 99401650 > FWD: 512237 ICQ: 5662270 > ========================================== > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > [email protected] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
