EasyUC
4.8.7

CUCM connection options

Prefilled phone number

Remove prefixes per CUCM connection so that the short extension is prefilled from the user's number.

EasyUC · Version 4.8.7

In EasyUC: EasyUC Cisco → Administration → CUCM & Provisioning → CUCM Connections → Actions → Prefilled phone number

What it is for

The phone number field of a user often contains the full number, for example +49 221 478 7517. The line in the CUCM, however, is meant to carry only the extension 7517. Since version 4.8.3, you enter prefixes per CUCM connection for this purpose. When EasyUC derives a line number from a user's phone number, it cuts off the matching prefix at the front.

The shortening applies wherever EasyUC prefills or newly creates a line number: creating a phone and a device profile, the setup wizard and the CSV import, Quick Tasks, Automatically User Setup and device requests in self-service. The server shortens exactly once. If several prefixes match, the longest one wins.

EasyUC does not change the phone number field in CUCM or LDAP. Lines that already exist stay as they are. Without prefixes, EasyUC behaves as before.

Prerequisites

  • License with provisioning (provisioning). Without it, the entry is missing from the Actions menu.
  • Sign-in as an administrator. In the menu definition, the Administration menu is assigned only to the role ROLE_APP_ADMIN.
  • The CUCM connection is enabled. For a disabled connection, Actions shows only Enable Connection.
  • You know the number blocks of the connection in their full notation.
  • If Check Number Range is switched on in the settings for creating devices, the number plan contains the shortened extensions. The plan is not converted.

Step by step

  1. In the header, select the EasyUC Cisco workspace.
  2. In the menu, open Administration → CUCM & Provisioning → CUCM Connections. The page is titled Manage CUCM Connections.
  3. In the row of the connection you want, click Actions. The Menu popover opens.
  4. Click Prefilled phone number. The Prefilled phone number dialog opens.
  5. In Prefixes to remove (one per line), enter one prefix per line, for example +49 221 478.
  6. If needed, enter national notations as separate lines, for example 0221 478.
  7. Under Effective prefixes, check how EasyUC interprets your lines. The prefixes are shown there cleaned up and without duplicates.
  8. Under Preview, type a real number into Sample phone number, for example +49 221 478 7517. The line below shows the result: “Prefilled: 7517 (removed: +49221478)”.
  9. Click Save. The dialog closes and the message Prefilled phone number saved. appears. Cancel discards your entries.
  10. Reload any open pages and create a phone for a test user. The number field is prefilled with the extension.

Step by step: switching the shortening off again

  1. Open the Prefilled phone number dialog as described above.
  2. Delete all lines in the Prefixes to remove (one per line) field. Effective prefixes then shows “No prefixes – the phone number is prefilled unchanged, as before.”
  3. Click Save.

Fields and options

Fields and options
Field / actionMeaning and use
Prefixes to remove (one per line)One prefix per line: an optional +, then 1 to 30 digits. At most 50 prefixes. Spaces, hyphens, brackets, dots and slashes are ignored, as is “(0)” after the country code. A leading 00 counts as +. Empty lines are skipped. Default: empty.
Effective prefixesShows the cleaned-up, unique prefixes in the order entered. This list is what gets saved.
Sample phone numberTest field of the preview. It works with the prefixes entered but not yet saved, and saves nothing itself.
RuleIf the phone number starts with one of the prefixes, that prefix is removed. If several match, the longest one wins. The extension may vary in length. If none matches, if nothing would remain or if what follows is not digits only, the number stays unchanged.
Location selectionThe shortened extension does not fit any E.164 range. “Create Device” and “Create Device Profile” therefore preselect the user's location. If you type in a different number, the number range determines the location again.

Where the shortening does not apply

  • Auto Delete Endusers and the list of deleted users still search with the unshortened number. Short extensions are not unique across locations, so deletion keeps the previous search.
  • Lines and devices created with the shortened extension must be removed by hand, for example with the Quick Task for deleting a user.
  • The Quick Task for deleting a user and the number list in the profile search with the shortened extension only in the line partitions of the templates at the user's location. A line with the same number at another location does not appear there.
  • Tasks already picked up by Automatically User Setup keep their value.
  • For locations with a number format other than NORMAL, the preview can differ from the server's result, because the server shortens the number that has already been derived according to the location format.

Checking the result and narrowing down errors

  • Success: the message Prefilled phone number saved. and a prefilled extension when creating a phone.
  • “Line 2: “…” is not a valid prefix (optional +, then 1–30 digits).”: the line contains letters or other characters.
  • “Line 3: “…” is already in line 1.”: two lines result in the same prefix after clean-up.
  • “Line 51: at most 50 prefixes.”: remove lines.
  • “Saving failed. Please check the marked entries.”: the server rejected the list. The affected lines are marked.
  • Preview “No prefix matches – prefilled unchanged”: the sample number starts with none of the prefixes. Check the country code and the national notation.
  • Preview “Nothing remains after …”: the prefix is as long as the entire number.
  • The extension is rejected on creation: with Check Number Range switched on, it is missing from the number plan.
  • Another user with the notation +49 (0)221 478 7517 is not detected as a conflict for 7517. Clean up such entries in the directory.
  • Open pages show the new value only after a reload.

Related chapters