[cisco-voip] Check on calls in queue for a team?

Anthony Holloway avholloway+cisco-voip at gmail.com
Fri Mar 23 10:42:59 EDT 2018


You may not like this solution, but I think you could just use a HashMap to
map your CSQs to Teams, and then another HasMap to map your Teams to Light
Directory Numbers.  Then use global sessions to track if a light is
currently being lit for a team or not.  Limit your checking to PIQ === 1
and that should be pretty efficient and easy to administer....which is
relative.

On Thu, Mar 22, 2018 at 2:53 PM Matthew Loraditch <
MLoraditch at heliontechnologies.com> wrote:

> The light needs to be on if ANY queue for the team has a call in it.
>
> We have around 40 queues. One team has 22 CSQs assigned.
>
>
>
> So my logic was call the app once we have a call form the main script,
> ring the light, hang up and then check all the queues once any queue has
> contacts waiting > 0, call and begin again. I can’t keep the call ongoing
> as I have no way to break in and terminate it.
>
>
>
> So it’s if CSQ1 has calls, call light if not check CSQ2 and so on.
>
>
>
> Am I being crazy?
>
>
>
> * Matthew Loraditch​Sr. Network Engineerp: 443.541.1518
> <443.541.1518>w: www.heliontechnologies.com
> <http://www.heliontechnologies.com/> | e: MLoraditch at heliontechnologies.com
> <MLoraditch at heliontechnologies.com>[image: Facebook]
> <https://facebook.com/heliontech>[image: Twitter]
> <https://twitter.com/heliontech>[image: LinkedIn]
> <https://www.linkedin.com/company/helion-technologies>*
>
> *From:* Anthony Holloway <avholloway+cisco-voip at gmail.com>
> *Sent:* Thursday, March 22, 2018 3:50 PM
> *To:* Matthew Loraditch <MLoraditch at heliontechnologies.com>
> *Cc:* Bill Talley <btalley at gmail.com>; cisco-voip at puck.nether.net
>
>
> *Subject:* Re: [cisco-voip] Check on calls in queue for a team?
>
>
>
> Why so many conditionals?
>
>
>
> If you're simply trying to map a CSQ name to an Extension to call, you
> could use a HashMap.
>
>
>
> Link for example usage of HashMap
>
>
>
>
> https://supportforums.cisco.com/t5/contact-center/route-customer-call-to-a-specific-agent-based-on-calling-number/td-p/2176574
>
>
>
> On Thu, Mar 22, 2018 at 1:45 PM Matthew Loraditch <
> MLoraditch at heliontechnologies.com> wrote:
>
> It’s a sip phone, it lights on a ring or on a call.
>
>
>
> I managed to program the nearly 40 nested ifs (broken up into 3 copies of
> the script) in about 30 minutes. So I guess I’m done for now in that
> respect. If I could make it more programmatic I might. I’ve done no API
> work, so not sure if that would work or not or be any easier.
>
>
>
>
>
> *Matthew Loraditch**​*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
> *From:* Bill Talley <btalley at gmail.com>
> *Sent:* Thursday, March 22, 2018 2:22 PM
>
>
> *To:* Matthew Loraditch <MLoraditch at heliontechnologies.com>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Check on calls in queue for a team?
>
>
>
> I’m behind all of the emails but am curious about how the light gets
> triggered.  Is it a SIP device registered to CUCM or how does that work?
>  What version of CCX are you running?
>
>
>
> I’m wondering if you could do a REST call to the CCX database for contacts
> waiting and parse the XML?  Might be easier to capture the data that way?
>
> Sent from a mobile device with very tiny touchscreen input keys. Please
> excude my typtos.
>
>
> On Mar 22, 2018, at 11:20 AM, Matthew Loraditch <
> MLoraditch at heliontechnologies.com> wrote:
>
> I'm setting up that light system I’ve talked about and the managers wants
> their lights to come on if any queue assigned to a team has calls waiting.
> I can't think of any way to do that but iterate through every queue in a
> very long nested if of get reporting statistics steps and anytime we add a
> queue I will have to modify the script...
>
>
>
> One team has 22 queues assigned…
>
>
>
> If anyone has a better idea, I'd love to hear it!
>
>
>
> *Matthew Loraditch**​*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
>
> <image905466.png>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> <image374618.png> <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image028123.png
Type: image/png
Size: 8404 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image559636.png
Type: image/png
Size: 96434 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image981976.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image376795.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image949743.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image981976.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180323/f06f3d56/attachment-0005.png>


More information about the cisco-voip mailing list