EasyUC Engineer
Maintain locations, packages and Template 2.0 in Engineer
Edit locally or on the server, check CUCM references and exchange configurations between customer projects.
In EasyUC: Standorte; Pakete; Template 2.0
What it is for
Locations, packages and Template 2.0 define how Engineer creates devices and lines. They use the same field names and groups as the server version, so configurations can be taken over without rework.
Prerequisites
- A customer project with a verified CUCM connection so that selection lists can be loaded.
- For the server configuration: a connected EasyUC server with the corresponding permissions.
Step by step
Fields and options
| Field / action | Meaning and use |
|---|---|
| Device settings | Device description with variables, device pool, common device configuration, region, CUCM location and device CSS. |
| Line settings | Line naming, partition, line and forwarding CSS, busy trigger and no-answer timer. |
| Phone models and scenarios | One line scenario is mandatory per model; further scenarios up to five lines are optional and without gaps. Jabber desktop supports up to eight scenarios. |
| Import / export | Export locally stored locations and templates as JSON and import them into another customer project; on the server, CSV import/export with preserved IDs. |
Check the result and narrow down errors
- Saving fails: mandatory fields of all location and package profiles are checked when saving Template 2.0; locations and packages can be saved independently.
- Saving a configuration does not change existing CUCM objects; only a creation or action writes to CUCM.