CUCM connection options
Naming rules for devices
Templates for the device description and the names of softphones, profiles and other device types.
In EasyUC: EasyUC Cisco → Administration → CUCM & Provisioning → CUCM Connections → Actions → Device naming
Purpose
When EasyUC creates a device in the CUCM, it needs a device name and a description. Hardware phones are named after their MAC address. Softphones, device profiles, remote destinations, CTI route points and virtual devices have no MAC address. For these, EasyUC builds the name from the templates in this dialog. The Device Description template applies to the description of all devices.
A template consists of fixed text and placeholders in double curly braces. On creation, EasyUC replaces the placeholders with the data of the user and the device. For softphones, the CUCM device type requires a fixed prefix (TCT, BOT, CSF, TAB). The dialog shows it in front of the field; you enter only the part after it.
Saving does not change existing devices. The rules take effect when EasyUC creates a device. If CUCM Changes is switched on, EasyUC also sets the names again as soon as the data of a user changes in the CUCM.
Prerequisites
- License with the
cucmmodule and theprovisioningfeature. Withoutprovisioning, the entry is missing from the Actions menu. - EasyUC account with the
ROLE_APP_ADMINrole. Only administrators see the Administration menu. - The CUCM connection has been created and enabled. For a disabled connection, Actions shows only Enable Connection.
- You know the naming convention of your CUCM. Device names must be unique in the CUCM. A template without a reference to the user leads to a name conflict with the second device.
Step by step
Fields and options
| Field / action | Meaning and use |
|---|---|
| Device Description | Template for the device description. Default: {{phoneNumber}} {{firstName}} {{lastName}}. The result is shortened to 128 characters. Required. |
| iPhone | Name for Cisco Dual Mode for iPhone, prefix TCT. Default: {{userID}}. Required. |
| Android | Name for Cisco Dual Mode for Android, prefix BOT. Default: {{userID}}. Required. |
| CSF | Name for Cisco Unified Client Services Framework (Jabber/Webex on the PC), prefix CSF. Default: {{userID}}. Required. |
| Tablet | Name for Cisco Jabber for Tablet, prefix TAB. Default: {{userID}}. Required. |
| Device Profile | Name for device profiles (Extension Mobility). Default: {{location}}{{userID}}. Required. |
| Remote Destination | Name of the remote destination. Default: RD{{userID}}. Required. |
| Remote Destination Profile | Name of the remote destination profile. Default: RDP{{userID}}. Required. |
| Mobile Identity | Name of the mobile identity. Default: RDMI{{userID}}{{deviceName}}. Required. |
| CTI Route Point | Name for CTI route points. Default: MS{{userID}}. Required. |
| Virtual Device | Name for virtual devices. Default: VD{{userID}}. Required. |
| Replace Naming Values | List of replacements. Add creates a row, remove deletes it. The list applies to device names and line names alike. Both dialogs (Device Naming and Line Naming) edit the same list. |
| Text To Replace | Text that is searched for in the finished name. EasyUC replaces whole words only and ignores case. Required in every row. |
| Text To Replace With | Text that is inserted instead. Required in every row. |
Placeholders
| Field / action | Meaning and use |
|---|---|
| `{{firstName}}` | First name of the user. |
| `{{1FirstLetterFirstName}}`, `{{2FirstLetterFirstName}}`, `{{3FirstLetterFirstName}}` | The first one, two or three letters of the first name. |
| `{{lastName}}` | Last name of the user. |
| `{{userID}}` | User ID in the CUCM. |
| `{{department}}` | Department of the user. |
| `{{title}}` | Title of the user. |
| `{{displayName}}` | Display name of the user. |
| `{{deviceType}}` | Phone type, for example “Cisco 8811”. |
| `{{deviceTypeShort}}` | Short form of the phone type. “Cisco ” is cut off (8811), softphones become TCT, BOT, CSF or TAB. |
| `{{deviceName}}` | Device name in the CUCM, for example SEP… or BOT…. |
| `{{phoneNumber}}` | Phone number. Only digits and the plus sign are used. |
| `{{location}}` | Location of the user. |
| Dynamic Custom User Fields | If the CUCM has its own user attributes (Custom User Fields), the dialog lists them as well. The placeholder is the attribute name in double curly braces. |
Check the result and narrow down errors
- Success: A newly created softphone has the expected name in the CUCM, for example
CSFmmusterwith the template{{userID}}and the user IDmmuster. - Message “This value should not be blank.” under a field: All templates are required. Every row under Replace Naming Values also needs both values.
- Characters are missing from the name: In device names, EasyUC transliterates umlauts and special characters. Placeholders that EasyUC cannot resolve are removed from the description.
- Existing devices keep their previous names: This is correct. Saving does not rename anything.
- Creation fails because of a duplicate name: The template is not unique. Include
{{userID}}or{{phoneNumber}}in the template.