You have the uniqueID, which is a pseudo timestamp. More useful to your described effort, though would be the answer and end of call fields. Your backend system is going to have the timestamp of when the order was placed, so you just need to address the calls that sandwich that timestamp.
-----Original Message----- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Mitch Claborn Sent: Thursday, October 25, 2012 11:19 AM To: asterisk-users@lists.digium.com Subject: [asterisk-users] How to tie orders taken to specific CDR records Our phone operators work off of an Asterisk queue. They take calls from customers and take orders with our back end systems. What I need to be able to do is tie the orders taken to the specific CDR record that reflects the call from which the order originated. The typical/sample CDR table doesn't have a primary key. I can add an auto-generated PK, but the CDR is not written until the call ends, when the orders have already been placed. (Even if the CDR was written earlier, could I retrieve the generated PK from it in the dialplan somehow?) Is there some combination of fields in the CDR that might uniquely identify a specific call? Open to any and all ideas. -- Mitch -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users