[cisco-voip] CUCM 11.5

[Pawlowski, Adam]

Our applications folks here had initially written Perl scripts to scrape web server data from the phones.

I asked them to disable that after we started getting into problems with the 7900 series phones.. But we scraped this data and compared it with our cable and port map database, and scheduled periodic “pings” with XML to the customer to verify if their location was correct. If not, we logged a ticket for investigation. Was a good idea.

I’m not sure if we can poll that from RIS data but I know we can get some of it from registration details for directly registered endpoints.

We do use CER as well. I have an awful Perl script that takes exported ERL/Port data and compares it to port map, to update the location comment field and ensure the proper ERL is set. This is a massive annoyance for CER as we use room-level ERLs. You cannot rename ERLs in CER and the API is useless to manage the content of the application. Also last we learned “delete” doesn’t often delete anything in the database which runs up against capacity problems if you believe the datasheets.

Adam

From: Benjamin Kenneally <benjamin at kenneally.me>
Sent: Wednesday, May 30, 2018 3:16 PM
To: Anthony Holloway <avholloway+cisco-voip at gmail.com>
Cc: Hunter Fuller <hf0002 at uah.edu>; Pawlowski, Adam <ajp26 at buffalo.edu>; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 11.5


I'm a creator of gross Python scripts myself and would love to know more.

On Wed, May 30, 2018, 1
On Wed, May 30, 2018, 1:35 PM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
I'm something of a connoisseur of gross Python scripts.  Would you mind sharing what you have?

On Tue, May 29, 2018 at 7:19 PM Hunter Fuller <hf0002 at uah.edu<mailto:hf0002 at uah.edu>> wrote:
I too would love to use this, as I am currently using the world's grossest Python script to apply switch port information to phones.

On Tue, May 29, 2018 at 6:23 PM Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>> wrote:
I don't think it works yet to be honest.

The UCM has the capability to extract the information and do something with it, but only if the endpoint sends it. For whatever reason I'm not sure if that's actually supported yet in any of the endpoint firmware.

I'm waiting for this for Jabber but I think I'm going to be waiting a while.

No idea why since most of the devices already support supplying cdp/lldp port information which you can see in the registration details.

I don't think it was very well communicated that this is a bit of an orchestrated effort and the UCM side of it seems to have gotten ahead of other parts somehow.

If you do get it to work I'd be interested. If it provides a data interface for anything at all  better than CER to work properly I will be all over it.

Regards,

Adam Pawlowski
_______________________________________________
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
--

--
Hunter Fuller
Network Engineer
VBH Annex B-5
+1 256 824 5331<tel:(256)%20824-5331>

Office of Information Technology
The University of Alabama in Huntsville
Systems and Infrastructure
_______________________________________________
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
--

Best regards,

Benjamin Kenneally
+1.763.600.4147
benjamin at kenneally.me<mailto:benjamin at kenneally.me>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180530/6ccf4ecb/attachment.html>