Use this Knowledge Script to create a list of unused phones. This script bases the report on the list of phones configured on Cisco Unified Communications Manager or Unified Communications Manager Express. It looks at the phones configured at the time of the most recent successful data collection, and then, using the criteria you set in the parameters, creates a list of phones that have been unused for n days.
When running this script, keep in mind how far back the data goes, including the initial data load. If you specify an initial data load of seven days, and then run this script, any phone whose last call was at least eight days ago will show up on the report as having no calls — in other words, as unused.
You can select Communications Managers or H.323 gateways as Data Sources for this report. Before using this report to identify unused Communications Manager Express phones (based on the H.323 gateways you select), run the CCME_GetConfig Knowledge Script, which provides meaningful data for all Communications Manager Express phones.
Report agent
By default, this script runs once.
Set the following parameters as needed:
Parameter |
How to Set It |
---|---|
Data Source |
|
Select data source |
Select the data for your report by View Name, Data Warehouse, or Data Source. To work with Communications Manager Express phones, select H.323 Gateways. |
Select time range |
Select a Specific or Sliding date/time range from which the report should pull data. The default is Sliding. |
Gateway name |
Use this parameter only if you selected H.323 Gateways as a data source. Specify the name of the Communications Manager Express gateway for which you want to find unused phones. Alternatively, type a partial name and the * wildcard to indicate Communications Manager Express names that match a pattern. Leave this field blank to gather statistics for all Communications Manager Express gateways known by the data source. |
Minimum days since last call |
Specify the minimum unused days filter for calls selected by the script. Phones unused for less than the minimum will not be included in the report, even if all other criteria are satisfied. Type 0 to include all unused phones in the report. |
Minimum duration when looking for calls |
Specify the minimum duration filter for calls selected by the script. Calls with a duration of less than the minimum will not be included in the report, even if all other criteria are satisfied. The default is 0 seconds. |
Direction of calls |
Specify the direction filter for calls selected by the script. You can choose to include calls that are Outbound Only, Inbound Only, or both Inbound and Outbound. |
Report Settings |
|
Order rows by? |
Select the criterion by which you want to sort the rows in the report:
All phones used on any given day are sorted by directory number. For example, the report may show 10 phones used on April 4, 7 phones used on April 3, and 12 phones used on April 2. April 4th’s 10 phones are sorted by directory number, as are the phones for April 3 and April 2. |
Include parameter help card? |
Set to y to include a table in the report that lists parameter settings for the report script. The default is y. |
Select output folder |
Set parameters for the output folder. The default folder name is UnusedPhones. |
Add job ID to output folder name? |
Set to y to append the job ID to the name of the output folder. The default is n. A job ID is helpful for making the correlation between a specific instance of a Report script and the corresponding report. |
Select properties |
Set miscellaneous report properties as desired. The default report name is Unused Phones. |
Add time stamp to title? |
Set to y to append a time stamp to the title of the report, making each title unique. The default is n. The time stamp is made up of the date and time the report was generated. Adding a time stamp is useful in order to run consecutive iterations of the same report without overwriting previous output. |
Event Notification |
|
Raise event if report succeeds? |
Set to y to raise an event when the report is successfully generated. The default is y. |
Event severity when report succeeds |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the report is successful. The default is 35. |
Event severity when report has no data |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the report contains no data. The default is 25. |
Event severity when report fails |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the report fails. The default is 5. |