[cisco-voip] CUCM - Pulling Phone Screenshots

[Rittenhouse, Robert (LACA)]

Very cool! I will have to mess with this and see what I can come up with. All of the solutions have been very helpful.

Thank you all!

Robert Rittenhouse
Network Coordinator
Licking Area Computer Association (LACA)
(740) 345-3400 ext. 220
rrittenhouse at laca.org<mailto:rrittenhouse at laca.org>

From: Wesley Schochet [mailto:Wesley.Schochet at childrensmn.org]
Sent: Thursday, September 20, 2012 11:23 AM
To: Rittenhouse, Robert (LACA); cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM - Pulling Phone Screenshots

The best way to accomplish global authentication is to create your own Authentication service.  When a phone authenticates a user it calls a URL:

http://authURL?UserID=thisApp&Password=thisPass&devicename=SEPABCD1234FEDC

The URL returns either the word AUTHORIZED or UNAUTHORIZED.

My auth service screens out the global user/password combinations and then calls the CUCM auth URL for the others.

Wesley A. Schochet
System Architect
Children's of Minnesota
• wes.schochet at childrensmn.org
<mailto:wes.schochet at childrensmn.org>•  651-855-2081
È 651-592-5441
>>> On 9/13/2012 at 4:33 PM, "Rittenhouse, Robert (LACA)" <rrittenhouse at laca.org<mailto:rrittenhouse at laca.org>> wrote:
I am in the planning stages of writing some internal tools for CUCM/Unity 8.5(1). One of the tools will need to pull a screenshot of any phone on the cluster. I am trying to find the best way to accomplish this specific task. Do I create a single application user and keep assigning that user every device as a “controlled” device?

It seems if I add them as a controlled device I am able to authenticate at http://phoneip/CGI/Screenshot

Is there a better way to do this? One Demo utility from Uplinx tells you to enable Extension Mobility on all phones before using the tool. Is this the solution? If so, is it disruptive to do in mass?

Also, are there any other online groups/communities where we can discuss these types of topics? I can’t find much for API/AXL programming besides at Cisco Developer Network.

Thanks!
________________________________
PLEASE NOTE: This message and any response to it may constitute a public record, and therefore may be available upon request in accordance with Ohio public records law. (ORC 149.43)
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain private, confidential, and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, employee, or agent responsible for delivering this message, please contact the sender by reply e-mail and destroy all copies of the original e-mail message.


Confidentiality Statement:
This email/fax, including attachments, may include confidential
and/or proprietary information and may be used only by the
person or entity to which it is addressed. If the reader of
this email/fax is not the intended recipient or his or her
agent, the reader is hereby notified that any dissemination,
distribution or copying of this email/fax is prohibited. If you
have received this email/fax in error, please notify the sender
by replying to this message and deleting this email or
destroying this facsimile immediately.
________________________________
PLEASE NOTE: This message and any response to it may constitute a public record, and therefore may be available upon request in accordance with Ohio public records law. (ORC 149.43)

This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain private, confidential, and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, employee, or agent responsible for delivering this message, please contact the sender by reply e-mail and destroy all copies of the original e-mail message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120920/64b6576b/attachment.html>