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

[Anthony Holloway]

Yes, it's a third party SIP phone and when it's called it lights up.  Hence
the Place Call step solution in UCCX.

Other thread talking about the device.
https://cisco-voip.markmail.org/thread/56k3exldkrtz5e2r

On Thu, Mar 22, 2018 at 1:23 PM Bill Talley <btalley at gmail.com> wrote:

> 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/20180322/a4be9d4f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image505954.png
Type: image/png
Size: 96434 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/a4be9d4f/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image876780.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/a4be9d4f/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image412570.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/a4be9d4f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image505954.png
Type: image/png
Size: 96434 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/a4be9d4f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image412570.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/a4be9d4f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image876780.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180322/a4be9d4f/attachment-0005.png>