jsteinberg1 / cucm-phone-info Goto Github PK

Hi

I have about 12000 phones on our cluster. But currently I only see 4000 under Phone Info when I download a CSV. Is there a limitation here?

Could you add the fields ownerUserName, locationName, commonPhoneConfigName, securityProfileName, sipProfileName, phoneTemplateName, line_1_dirn, line_1_display, line_1_e164Mask?

Thanks.

Kay

Hi

Phone Scraper only shows the details of 3 phones. I have about 12000 phones.
Are there any limitations? Is there any room for improvement here?

Big Thanks.
Kay

Hello
A cool project. Could you describe exactly how to install this on Debian. That would be great.
Thanks a lot.

Might be helpful to add support for ATA devices to the tool.
I know the ATA-187 has accessible webpages you can scrape.
Their URLs are:

Device Information http://<ip_addr>/Device_Information.htm
Network Setup http://<ip_addr>/Network_Setup.htm
Network Statistics>Ethernet Information http://<ip_addr>/Ethernet_Information.htm
Network Statistics>CDP Neighbor http://<ip_addr>/CDP_Information.htm
Device Logs>Status Messages http://<ip_addr>/Status_Messages.htm
Streaming Statistics>Stream 1 http://<ip_addr>/RTP1.htm
Streaming Statistics>Stream 2 http://<ip_addr>/RTP2.htm
Note those are .htm NOT .html files

I can provide example HTML for reference if you'd like to add this support.
I don't have access to any older ATA device models and I believe the newer ones (ATA-190 and ATA191 use authentication to access their web pages by default).

In testing found that the 8821 does not pull the CUCM servers.
This is because the webpage for the 8821 is a little different than say the 8841.
8841 lists 'CUCM server1', 'CUCM server2', etc. for CUCM servers
8821 lists them as 'Server 1', 'Server 2', etc.

ITL status is populated based on the IP Phone webpage's 'status messages' page. In some circumstances the phone will not have any recently reports of ITL status and therefore the ITL status is not reported.

One way this might be addressed is to only update ITL status field in db for a given phone record if there is ITL value returned by scraper.

The 7937 Conference Phones use an entirely different webpage structure than other phones.
Their URLs are as follows:

Device http://<ip_addr>/localmenus.cgi?func=604
Network http://<ip_addr>/localmenus.cgi?func=219
Ethernet http://<ip_addr>/localmenus.cgi?func=601
Logging http://<ip_addr>/localmenus.cgi?func=603

I can provide you some HTML output from some live to help adapt the tool to pull these. LMK

Might be helpful to indicate on the phone scrape report why a given endpoint did not have any data. It could be that the phone is down or inaccessible (unpingable). It could be that the web access for that phone is disabled, in this case the phone would be pingable but would return 200 from HTTP calls.

Currently the application will only query the cucm server provided. If that server is down, it will not query another node in the cluster.

Also, if the CUCM node in the first cluster is down, logins authenticating against cucm will fail.

6901 Phones use a different URL structure than most phone models.
Their URLs are as follows:

Device Information http://<ip_addr>/Device_Information.html
Network Setup http://<ip_addr>/Network_Setup.html
Ethernet Information http://<ip_addr>/Ethernet_Information.html
Network http://<ip_addr>/Network.html
Device Logs>Status Messages http://<ip_addr>/Status_Messages.html
Streaming Statistics>Stream 1 http://<ip_addr>/Stream1.html

I can provide example HTML from some devices for reference if you'd like.

When trying to add a new cluster, anytime I try to save it I get the error "Error encountering saving cluster. Please check settings/credentials and try again"

I have validated the credentials provided work against the AXL URL provided.
How does the AXL URL need to be formatted? Like https://x.x.x.x:8443/axl/ ?????
In the certificate part of the setup, which certificate and in which format are you looking for?

Would be super helpful if you had a function that would take the Phone Info and Phone Scrape data and combines them into a single report with the data correlated by endpoint.

Maybe include a timestamp of the sync and scrape that the data comes from so the user knows how fresh the data is.