This stands to be corrected, but as I understand it, the queue command on its own would not generate a second CDR any more than a transfer to an extension. The way I understand the queue/agent/call relationship is this:
1. agent(s) login to queue this may or may not create a CDR entry 2. caller calls asterisk this creates a CDR for that incoming call 3. caller is sent to queue by context or dialplan this creates a CDR only if forkCDR is used since the queue command isnt a new call It seems to me that would be desirable for queue to act as a second pbx where queue activity (login/logout/transfer etc) is logged in the CDR as new calls, Since my queue experience and $5 will get you a decent starbucks in some places, take this with a grain of salt, please. -- Danny Nicholas -- _____ From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Håkon Nessjøen Sent: Wednesday, January 27, 2010 1:07 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] CDR problems with Queue 2010/1/27 Håkon Nessjøen <haa...@avelia.no> On Wed, Jan 27, 2010 at 3:37 PM, Danny Nicholas <da...@debsinc.com> wrote: Just a shot in the dark what is the endbeforehexten value in cdr.conf? It was not defined. And the result was the same either it was set to yes or no. The cdr closing when user B hangs up, gets the full duration of call A at that point. And no more cdrs exists. Håkon Anyone? :/ Do all of you get two CDR's in calls to queues?
-- _____________________________________________________________________ -- 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