Phone Scraper: Error Reporting, Phones not Scraped

[robphill]

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.

[jsteinberg1]

The phonescraper will only try to connect to phones registered within the last 24 hours (reported by CUCM Serviceability). So the assumption is the phone should be registered with that IP. If it doesn't connect, it really should only be because the phone webpage is disabled, blocked by ACL/FW, or the phone model isn't supported by PS. The phonescraper process already takes a long time on large clusters, adding ping would significantly increase the run time.

[robphill]

Understand about the added workload of adding connectivity checks, maybe not necessary.

But an aside, does the phonescraper not use the data from phone sync to poll CUCM?

[jsteinberg1]

Phonescraper does use the cucm phone sync data. When PS runs, it gets the phone IP, model, and last seen fields from the phone sync table. If the phone was registered to callmanager within the last 24 hours, it gets scraped. PS uses the model number from cucm sync to know which URLs to scrape from the phone's webserver