Fusion 3.0 procedure guide
The UC Template is a modular solution for IP-telephony and Unified Communications. The solution is based on
open standards and is very efficient from an operational point of view.
The UC Template is software delivered as a service (SaaS). Updates and a water-proof disaster recovery pack
(automated and guaranteed back-up, documentation, redundancy) are included. The solution is most
scalable and allows you to effectively respond to the changing communication needs of your
The UC Template is a rich IP-PABX solution, designed to maximize the self-management by IT administrators
This guide will help you to go through the configuration of your UC Template solution.
This guide is intended for certified engineers only.
This document is confidential. It is provided for informational purposes only and is not
guaranteed to be without errors. Some of the functionalities described may be specific to a
device, to an application or to a network. Some features may only be available as optional
functionality. Escaux has a policy of continuous improvement and therefore reserves the right
to modify this document without prior notice.
Goal of this document
The goal of this document is to describe all procedures that are needed to make sure the configuration is correct.
Adding features to the template
See here how you can add features to a default Template and which restrictions apply regarding the configuration.
Profiles, callflows, extensions & parameters
You can add new profiles, custom callflows and extensions as long as you respect the reserved ranges for extensions and callflows (see below). If you create new profiles those should never start with Template nor "UC". "Template" is the prefix for default profiles that can be used for new extensions. "UC" is now the reserved prefix for technical profiles.
The prefixes "Template" and "UC" are also reserved for global parameters names and should not be used for new parameters.
Modules and resources
Some modules and resources might be available for the template (validated) but not included by default. You can choose those in the module/resources list and configure it following our documentation.
- Validated for template means available but there is no default configuration
- Template supported means included by default in the template with a default configuration (buttons for phones...).
If you want to add a new module or resource that has not been validated for that template version, contact Escaux. After validation the new module or resource will be available as an option. Note that only one module or resource version will be validated for one template version. It will not be possible to choose another version.
Changing template features
The template features have been validated as a complete system through a quality assurance process. In order to provide sufficient quality guarantees, changing the following configuration is strictly forbidden without prior written approval from Escaux:
- Extensions in the reserved ranges (see below)
- Callflows in the reserved range (see below)
- Template supported module parameters (except for parameters that are mentioned in the install guide)
- Template supported IP Phones (except MAC address, restriction group, headset settings (if applicable), codec and sip reinvite settings)
- Template supported Desktop application resources
- Template supported Probes
- Template profiles (including parameters, type,...)
- Template status names
- Template callflow assignments (Template profiles)
- Template global parameters
Changing configuration of template supported phones
The phones that are included in the template, are being pushed with a specific configuration. This includes, for example, the configuration of what is shown on the screen of the phone, the configuration of the local and corporate directory, ...
As the user guides and documentation rely on this configuration, only a very limited set of parameters are allowed to be changed. Following settings can be changed without any problem
- The description
- The MAC address
- The restriction group
- Parameters regarding re-invite and codec settings
The softkey configuration can be changed, but the user guides will not be correct (as they assume for example that the first softkey on a Polycom is used for voicemail)
See here what are the reserved ranges for extensions and callflows. Outside those ranges you can do anything you want.
Those special extensions should exist
|| General reception (default reception)
This reception extension requirement is not applicable for Fusion 4.
Following ranges have been used for technical extensions, nothing should be changed or added there:
|| Extensions for call parking (net.Console)
|| Service extensions
|| Service extensions
|| Service extensions
|| Technical service extensions *
|| Technical service extensions
|| Technical service extensions for which authentication is required
|| Technical service extensions for rerouting purposes (exception below)
* except 8855 used for dynamic queue login on status change (dbSetProfileAgentLogger): parameters can be changed
Those ranges should only contain extensions with a specific profile:
|| Service Availability profiles (Template-ServiceAvailability)
|| Conference rooms (Template-Conference)
|| Outgoing Call catcher profiles (Template-OutgoingCallcatcher)
|| "Multi routes" Call Splitter profiles (Template-CallSplitter)
Note that other extensions can be reserved for some integrations (FMU,...)
Callflow id's from *100 up to *300 are reserved and should never be used.
It is mandatory to use STARTDYNAMICAPPLICATION 7.6 for all created callflows.
In certain cases, it might be needed to be able to configure software that has not been included in the template without making it available for everyone.
In this case, Escaux employees (only) can activate a cheat mode on the SOP.
This will allow to make any changes you want. Note that changes to default configuration are completely at your own risk. Escaux is not able to guarantee the stability of a system when the cheat mode is activated.