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

Thu Mar 22 15:53:39 EDT 2018

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 Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
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<mailto: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<tel:443.541.1518>

w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>

[cid:image937678.png at 71AF2D24.FFE0460B]

[cid:image248277.png at A513F166.776FAAB5]

[Facebook]<https://facebook.com/heliontech>

[Twitter]<https://twitter.com/heliontech>

[LinkedIn]<https://www.linkedin.com/company/helion-technologies>

From: Bill Talley <btalley at gmail.com<mailto:btalley at gmail.com>>
Sent: Thursday, March 22, 2018 2:22 PM

To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Cc: cisco-voip at puck.nether.net<mailto: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<mailto: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<tel:443.541.1518>

w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>

<image905466.png>

[cid:image001.png at 01D3C1E9.BBD89370]

[Facebook]<https://facebook.com/heliontech>

<image374618.png><https://twitter.com/heliontech>

[LinkedIn]<https://www.linkedin.com/company/helion-technologies>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20180322/d7c578b2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image028123.png
Type: image/png
Size: 8404 bytes
Desc: image028123.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/d7c578b2/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image559636.png
Type: image/png
Size: 96434 bytes
Desc: image559636.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/d7c578b2/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image981976.png
Type: image/png
Size: 431 bytes
Desc: image981976.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/d7c578b2/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image376795.png
Type: image/png
Size: 561 bytes
Desc: image376795.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/d7c578b2/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image949743.png
Type: image/png
Size: 444 bytes
Desc: image949743.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/d7c578b2/attachment-0004.png>