EasyUC for Cisco
Softphone policy per location
Define per location which softphones may be created and whether they appear as Jabber or Webex App.
In EasyUC: EasyUC Cisco → Templates → IP Phones & Video → Softphones for the location / Administration → CUCM & Provisioning → Locations → Edit
What it is for
The softphone policy of a location consists of two settings. The first defines which softphone types may be newly created at this location: desktop client, iPhone, Android and tablet. The second defines the product name under which EasyUC shows these devices: Jabber or Webex App.
In CUCM, Jabber and the Webex App are the same device types: CSF for the desktop, TCT for the iPhone, BOT for Android and TAB for tablets. The choice of client therefore changes only names and icons in EasyUC, not the device in CUCM.
Releasing the types is part of Template 2.0. There you also assign to each allowed client the button template with which EasyUC creates the softphone without a reference device. In the proven template model, all four types are available, provided a matching template exists.
Prerequisites
- License module
cucmand an active CUCM connection. - For releasing the types: role
ROLE_APP_UPDATE_TEMPLATE_SETTINGSand the model Template 2.0 under Templates → Settings. - For the softphone client: access to the Administration menu. It is available only to accounts with
ROLE_APP_ADMIN. - At least one EasyUC location has been created.
- Phone button templates for the device types CSF, TCT, BOT and TAB exist in CUCM.
Step by step: Define allowed softphones (Template 2.0)
Step by step: Select Jabber or Webex App as the client
Fields and options
| Field / action | Meaning and use |
|---|---|
| Softphone client | Field at the location. Values Jabber and Webex App. Without a selection, Jabber applies. Changes only the client name and the icon when devices are created for this location. |
| Jabber Windows | Desktop client, device type CSF. The only client with several lines, up to 8. |
| Jabber iPhone | Cisco Dual Mode for iPhone, device type TCT. Exactly one line. |
| Jabber Android | Cisco Dual Mode for Android, device type BOT. Exactly one line. |
| Jabber Tablet | Tablet client, device type TAB. Exactly one line. |
| Button Template | Phone button template of the client. Mandatory as long as the client is allowed. Only templates of the matching device type are offered. |
| 1 line / N lines (optional) | Line scenarios for Jabber Windows. A template for N lines requires one for N−1. |
| N of 4 allowed | Counter of the released clients at the location. |
| Not released | Marker on a softphone tile during creation when the type is not allowed at the location. The tile cannot be selected. |
| Template 2.0 (marker) | The softphone is built from the location values of Template 2.0, without a reference template. |
| No template | For the type there is neither a button template in Template 2.0 nor a template. The softphone cannot be created. |
| Service Profile for Soft Phones | Field at the location in the UC Service Profile Settings section. Determines the service profile for users with a softphone, separately for users with and without voicemail. |
Check the result and troubleshoot
- Success: When a device is created, the Soft Phones card shows only the released types as selectable. Types that are not released carry Not released.
- “No new Jabber softphones can be created for this location.” No client is ticked at the location. Existing softphones remain untouched.
- “The button template for 1 line is mandatory.” or “The button template is mandatory as long as this client is allowed.” Select the template or untick the client.
- Note that a button template is missing for N lines and that line scenarios must be set without gaps starting from 1 line: Fill the gap in the series for Jabber Windows.
- “Template 2.0 can only be saved when every location is complete. Still missing:” The list below it names the missing details per location.
- A location without a saved Template 2.0 block does not offer new softphones in Template 2.0 mode. Open the location in the template settings, add the mandatory values and save.
- The client name has not changed: The location of the user is a different one from the location you edited. Check the location in the creation dialog.