<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE-AT link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>some questions regarding design decisions in mod_callcenter,primary adressed to moc.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1) why did you put the queues in a hash table rather than in db tables ?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2) what do you recommend for the following scenario:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>when an agent call ends, there should be an event for the wrap-up-time start and one for wrap-up-time end.<o:p></o:p></p><p class=MsoNormal>i implemented sending end of the event using switch_scheduler_add_task, so a new task is started with the given wrap-up-time<o:p></o:p></p><p class=MsoNormal>when the call ends. this works, but has 2 disadvantages: <o:p></o:p></p><p class=MsoNormal>- if the agent ends the wrapuptime by hand, the scheduler task keeps running.-<o:p></o:p></p><p class=MsoNormal>- i cannot extend the wrapuptime on the fly if needed (or is there a fs api call to extend the time ? )<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>so my next idea is to put an additional sql query into cc_agent_dispatch_thread_run and do the time calculations in the callback (also for onbreak)<o:p></o:p></p><p class=MsoNormal>do you think this is a better approach ?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3) did you consider setting the agentstate for outbound / inbound calls from / to the agent contact(phone) ?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>thanks&regards<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>gw<o:p></o:p></p></div></body></html>