<div class="gmail_quote">On Wed, Jan 27, 2010 at 8:22 PM, Danny Nicholas <span dir="ltr"><<a href="mailto:danny@debsinc.com">danny@debsinc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="blue" lang="EN-US">
<div>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy;">This stands to be corrected, but as I
understand it, the queue command on it’s 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:</span></font></p>
<ol style="margin-top: 0in;" start="1" type="1">
<li class="MsoNormal" style="color: navy;"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial;">agent(s)
login to queue – this may or may not create a CDR entry</span></font></li>
<li class="MsoNormal" style="color: navy;"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial;">caller
calls asterisk – this creates a CDR for that incoming call</span></font></li>
<li class="MsoNormal" style="color: navy;"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial;">caller
is sent to queue by context or dialplan – this creates a CDR only if
forkCDR is used since the queue command isn’t a “new call”</span></font></li>
</ol>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy;">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,</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size: 10pt; font-family: Arial; color: navy;">Since my queue experience and $5 will get
you a decent starbucks in some places, take this with a grain of salt, please.</span></font></p></div></div></blockquote><div><br>Hi,<br>
<br>
I'm not sure if you understand me correctly. I'm not interested in cdrs for agent logins. For me, that is not call detail.<br>
But when you call into the pbx, thats one leg, and one cdr. And when a
queue() calls out to an agent, that is also a call. And for me, it's
logical that this would be two cdr lines. Because if this is going in
and out of a PRI/SS7 line, you would get money and pay money for these
calls. And therefore it's very important that queue() would start the
cdr duration a the exact moment the agent answers. etc.<br>
<br>
But the weirdest thing, is that the CDR for leg A is written when queue() is done, even if leg A is still active.<br>
<br>
I can't understand how people would accept this behaviour as logical? There must be a way to make queue() create valid cdrs? The one I get isn't correct for either legs.<br>
<br>Regards,<br>
Håkon<br></div></div>