[cisco-voip] UCCX - Need help with SQL CLI command to gather some system info about the UCCX system.

[Nathan Reeves]

10.6 would also give you alot of the information you want via the XML
provisioning API.  Took a quick look on a box here and you'd dump the
current application list (including the script name) via '
https://x.x.x.x/adminapi/application' and triggers via '
https://x.x.x.x/adminapi/trigger'.  The XML dumped from the trigger page
includes the application name, and the XML dumped from the application page
will include the script name.  You'll still have to tie the two together
but you can use the application name as the key.

Can hit those urls via browser just fine.  You'll just be prompted for auth
(login as an administrator).

The adminapi has gotten alot better since 9 and the docs on devnet should
give you a full rundown on what can be accessed these days.

HTH

Nathan

On Wed, Jun 22, 2016 at 12:46 AM, Anthony Holloway <
avholloway+cisco-voip at gmail.com> wrote:

> Unfortunately the DB schema is such that the script name is inside of this
> long ugly BLOB column called PrivateData, and it screws up the output
> display in PuTTy.
>
> You can see the script name, but it's not very nice.  So, if you're
> willing to deal with it, then here you go:
>
> run uccx sql db_cra select applicationname, privatedata from
> crsapplication where active = 't'
>
> Then, to get the Triggers in the same query would be even more of an ugly
> mess of output, but it is doable with the following modification:
>
> run uccx sql db_cra select limit 1 a.applicationname, a.privatedata,
> t.triggername from crsapplication as a left join crstrigger as t on
> a.applicationname = t.applicationname where a.active = 't' and t.active =
> 't'
>
> I really don't recommend running that command and expecting any useful
> output.  Like I said, the PrivateData column as a BLOB of just binary bits
> ruins the output.
>
> So, to get the list of triggers and apps separate from the script name
> (the ugly bit):
>
> run uccx sql db_cra select triggername, applicationname from crstrigger
> where active = 't'
>
> Last but not least, I do have a series of python scripts which I use to
> scrape the web ui for all kinds of cool data.  I even tweeted one out once:
>
> https://twitter.com/avholloway45633/status/647450649353846784
>
> I don't like to just give away custom code, because it's kind of like
> showing someone your bedroom closet.  If you know what I mean.  So, if
> there's interest in seeing my closet, I'll clean it up first.  ;)
>
> On Tue, Jun 21, 2016 at 11:19 AM, Brian V <bvanbens at gmail.com> wrote:
>
>> All you SQL gurus out there :)
>>
>> I'm hoping there is a quick way to accomplish a task.
>>
>> I recently inherited a UCCX 10.6 install with 39 applications defined.
>>
>> I need to document the application name, the script assigned to the
>> application, and the trigger(s) assigned to the application
>>
>> I only have WebEx access to a shared desktop at the customer. That
>> desktop has a browser and Putty.
>>
>> I have HTTP and SSH access to the UCCX system via the remote desktop.
>>
>> Does anyone know how to write a quick SQL CLI statement to gather this
>> info in one go ?
>>
>>
>> Thanks !
>>
>> _______________________________________________
>> 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/20160622/6490d738/attachment.html>