EasyUC
4.8.7

CUCM connection options

Registration history

Set the polling interval and retention of the registration status and read the related report.

EasyUC · Version 4.8.7

In EasyUC: Administration → CUCM & Provisioning → CUCM Connections → Actions → Device registration

What it is for

EasyUC asks the CUCM at fixed intervals which phones are registered and stores the result as a history. This shows you not only the current state but also since when a phone has no longer been registered.

This is useful for diagnosis in two cases: a user reports a dead phone and you want to know since when it has been missing. Or you are looking for devices that have not been registered for weeks because they were removed or connected wrongly.

At the CUCM connection you define how often EasyUC queries the status and for how many months the history is kept. The evaluation is in the Device Registrations report.

Prerequisites

  • A licence with provisioning. The Device Registration entry appears in the action menu of the connection only then.
  • Access to the CUCM connections in the administration to change the setting.
  • For the report: page role ROLE_APP_VIEW_DEVICE_REGISTRATION_PAGE and ROLE_APP_LIST_DEVICE_REGISTRATION.
  • A working CUCM connection. The background services of EasyUC are running.

Step by step: set the query

  1. Open Administration → CUCM & Provisioning → CUCM Connections.
  2. In the row of the connection, click Actions → Device registration. The Device registration dialog opens.
  3. Choose the polling interval under Interval EasyUC should ask for status.
  4. Choose the retention of the history under How many months to keep the registration history (last months).
  5. Click Save.

Step by step: evaluate the registration status

  1. Open Reporting → Bestand & Systemzustand → Device Registrations.
  2. Enter the device name under Device Name to check a single phone.
  3. Under Status, choose Registered or Unregistered.
  4. Under Unregistered for x Days, choose for at least how many days a device should have been unregistered, to find old devices.
  5. If required, narrow down by Models or by searching for the firmware (Search by Load Id).
  6. Per device, read status, details and Verified At.

Fields and options

Fields and options
Field / actionMeaning and use
Interval EasyUC should ask for statusGap between status queries: every 15 minutes, every 30 minutes, every hour, every 2 hours or every 4 hours.
How many months to keep the registration history (last months)Retention of the history: 3, 6, 12, 18 or 24 months.
Status (report)Registered or Unregistered.
Unregistered for x Days1, 5, 10, 15, 20, 25 or 30 days.
Rows per page25, 50 or 100 rows.
Delete All RegistrationsRemoves the stored registration history. The operation runs in the background.
Delete DevicesDeletes the selected devices from the CUCM. The operation runs in the background.

How to read the report

How to read the report
Field / actionMeaning and use
DeviceDevice name. Below it, where applicable, "Device Deleted", "Delete Pending" or "Restore Pending" if a delete operation is running or has finished for the device.
ModelPhone model according to the CUCM.
StatusRegistration status at the last query.
DetailsFor registered devices only: IP address, Load Id (firmware) and directory number (Dir). Otherwise a dash.
Verified AtTime of the last query at which this status was found.

Check the result and narrow down errors

  • You recognise success when a known, connected phone appears as registered with a current time under Verified At after the next polling interval.
  • The report shows the state of the last query, not the state of this second. Take the interval into account. You see the current state on the phone itself in EasyUC.
  • If Verified At stays old, the query is not running. Check the background jobs and the CUCM connection.
  • A shorter interval increases the number of queries to the CUCM and the amount of data. Choose it only as short as necessary.
  • An unregistered device is not automatically defective. Softphones are registered only while the client is running.
  • The dialog contains two settings. A former third value for keeping the status in days is hidden in the interface.

Related chapters