<div dir="ltr">Thanks for the link Kevin, I see the section now:<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><i>There must be 2 different Call Control Groups used for these scripts under Subsystems > CM Telephony > Call Control Group.</i></div><div><i>There must be 2 different Media Channels defined under Subsystems > Cisco Media.</i></div></blockquote><div><br></div><div>Unfortunately, they didn't expand on the topic and explain why.</div><div><br></div><div>Anyone know these two Authors on the article?</div><div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><br></div><div>Aravind Krishna Murthy</div><div>Cisco TAC Engineer</div><div><br></div><div>Arunabh Bhattacharjee</div><div>Cisco TAC Engineer</div></blockquote></div><div><br></div><div>Can you ask them to jump in here? Or maybe someone just simply knows the "why" behind this requirement?</div><div><br></div><div>I can tell you that I have deployed several callback solutions which do not use a different CCG/Media Group and it works. So, to say that it "must be 2 different" is a bit of mystery to me.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 5, 2019 at 3:41 PM Damisch, Kevin <<a href="mailto:Kevin.Damisch@oneneck.com">Kevin.Damisch@oneneck.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-3401269452352091702WordSection1">
<p class="MsoNormal">Anthony,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">/..<u></u><u></u></p>
<p class="MsoNormal"><b>"...I’ve read that the Call Control Group and Dialog Group should be different from the trigger on the originating application..."<u></u><u></u></b></p>
<p class="MsoNormal"><b><u></u> <u></u></b></p>
<p class="MsoNormal"><b>Can you link the source?<u></u><u></u></b></p>
<p class="MsoNormal">../<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I believe that is referenced here. I don’t recall the actual reasoning behind 2 separate call control groups though.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><a href="https://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-contact-center-express/200764-UCCX-Call-Back-Feature-as-seen-on-CUCM-a.html" target="_blank">https://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-contact-center-express/200764-UCCX-Call-Back-Feature-as-seen-on-CUCM-a.html</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(31,73,125)">Kevin</span></b><span style="color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b>From:</b> cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>>
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Tuesday, November 5, 2019 3:19 PM<br>
<b>To:</b> Johnson, Tim <<a href="mailto:johns10t@cmich.edu" target="_blank">johns10t@cmich.edu</a>><br>
<b>Cc:</b> voyp list, cisco-voip (<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>) <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] UCCX Callback Script<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi Tim,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I think the idea of a flawless script is in the eyes of the beholder.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I don't personally use the example script from the repo; are you talking about the one here:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<blockquote style="margin-left:30pt;margin-right:0in">
<div>
<p class="MsoNormal">script_respository_902\script_respository\release3\BaseLineAdvQueuing\BaseLineAdvQueuing.aef<u></u><u></u></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">If so, there a few things wrong with that script.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">For example, you said "...despite having Contact Inactive exception error handling..."<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Yeah, they setup an exception handler at the top for ContactInactiveException, but then they never clear it, or reset it, and so if and when the caller disconnects while recording their message or listening to the "success" prompt, the
whole thing falls a part and fails, sending script execution down to the ExceptionCIE label.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Another thing wrong with it is that the waiting mechanism for the Agent is such that it plays a relatively short prompt, waits 3 seconds for input from the Agent, then repeats.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">If you consider every application has a max 1,000 steps it can execute, and you subtract off the overhead of just getting the call to this point (say 21 steps in the most streamlined of scenarios), that leaves you with 32 minutes to queue
a call, otherwise the call will be aborted. Since most people are only interested in callback when they have queue hold time problems, this is likely to cause more issues than it solves.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">"...I’ve read that the Call Control Group and Dialog Group should be different from the trigger on the originating application..."<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Can you link the source?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Tue, Nov 5, 2019 at 10:59 AM Johnson, Tim <<a href="mailto:johns10t@cmich.edu" target="_blank">johns10t@cmich.edu</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Anyone have a callback script that is working flawlessly? We have implemented the solution in Cisco’s Advanced Queueing script and it’s seems to be working, but I’m seeing Contact
Inactive Exceptions and Contact Creation errors in syslog each time the callback is used, despite having Contact Inactive exception error handling.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">It seems that the issue may be related to the Place Call step which calls the trigger of the callback application. I’ve read that the Call Control Group and Dialog Group should
be different from the trigger on the originating application (which is what we have setup), but I’m curious if those should also be different from what’s used on the callback application. If so, can I use the same CCG and DG from the original trigger, on the
callback trigger?<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">For example, I have the following setup:
<u></u><u></u></p>
<p class="MsoNormal">App_A application has a trigger that uses CCG #8 and Dialog Group #0. In its script, it uses the Place Call step with CCG #25 and Dialog Group #3. This places the call to App_Callback
application which has a trigger that uses CCG #25 and Dialog Group #3.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Consolas">Tim Johnson</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Consolas">Voice & Video Engineer</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Consolas">Central Michigan University</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Consolas">Phone:
<a href="mailto:+19897744406@cmich.edu" target="_blank">+19897744406@cmich.edu</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Consolas">Fax: +19897795900</span><u></u><u></u></p>
<p class="MsoNormal"><a href="https://cmich.webex.com/meet/johns10t" target="_blank"><span style="font-size:10pt;font-family:Consolas;color:rgb(5,99,193);text-decoration:none"><img border="0" width="157" height="22" style="width: 1.6354in; height: 0.2291in;" id="gmail-m_-3401269452352091702gmail-m_-8154566266809588421gmail-m_-8979221485623659886Picture_x0020_1" alt="webexemailsig"></span></a><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</blockquote>
</div>
</div>
<br>
<br>
<b>Confidentiality Notice:</b> This message (including any attachments) is only for the use of the person(s) for whom it is intended. It may contain confidential, proprietary and/or trade secret information. If you are not the intended recipient, you are forbidden
to copy, distribute or use this information for any purpose, and you should inform the sender immediately and delete this e-mail.
</div>
</blockquote></div>