UC Template 3.0 Features

UC Template 3.0 Features

Introduction

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 organisation. The UC Template is a rich IP-PABX solution, designed to maximize the self-management by IT administrators and end-users. This guide will help you to go through the configuration of your UC Template solution.

Intended audience

This guide is intended for certified engineers only.

Disclaimer

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 give you a description of the available features

Major changes since UC Template 2.1

This list is updated with changes up to UC Template 3.0.5. For a complete list of changes see the UC Template release notes.

indicates features that were added/changed in UC Template 3.0.4 or 3.0.5

Changes with potential impact

Asterisk-1.2 is replaced by Communication Server
- new COLP feature
  - phones will display the name of the third party and update it during the call
  - works for incoming and outgoing calls
  - a name is shown for calls towards service extensions
  - outgoing calls to the mobile or home number of an internal contact will show the name of the contact
- new CAC feature
- T.38 support for faxes
  - Fax on ATA boxes should be configured using T.38 and ATA boxes should register on the SOP where calls are coming in
  - Fax Server should be configured on the SOP where calls are coming in
Unify-* profiles are renamed to Template-*
User/Manager profiles
- Profile parameters have been slightly reorganized
- By default, users and managers will be logged in or out of their queues when changing the status
- User pincode can only be changed from the user's phone (or SMP) and not from the Voicemail menu
- The ability to change Personal Menu settings via a short code has been removed
Polycom IP331 phone displays
- status in user language (fr, nl, en)
- queue status shown on the phone
CallQueuer
- Possibility to define 10, 20, 30 minutes for the timeout (in addition to previous values)
- Possibility to have a ringtone instead of music-on-hold
- Possibility to update the display name
- Different fallback action in case no answer or no agent logged in
- Possibility to define users as dynamic members with same penalty than permanent members
Prompt recording for IVR and Group profiles messages asks now the pincode configured in profile parameters instead of pincode in Internal Directory
Call forwarding:
- External calls forwarded to external will always show the intermediate number (also for group and short number profiles)
- Internal calls forwarded to external will keep the initial callerID (as before)
Unify-Speeddial profile renamed to Template-ShortNumber
Current pincode not requested if no pincode set
Hiding the CallerID for outgoing calls can (should) be done in the profile paramters of the User (Manager)
Supported cards & Outgoing trunks:
- Only Sangoma cards & Sip trunks supported
- Sangoma cards are to be configured using Sangoma 2 module & resources
- Different settings can be defined per outgoing trunk
- More outgoing trunks can be defined
SIP reinvite activated by default
FMU: unlogged FMU phones can be called using the mobile DDI, optional but now enabled by default
DHCP Server disabled by default
Only supported versions of modules and resources can be added on the SMP and are accepted for Apply Changes

(Other) New features

HuntGroup's allows for up to 15 agents to be called one after the other in order
Manager profile
- possibility to define a specific action when Assistant calls (ring Primary & Secondary phone by default)
- possibility to forward to assistant and mobile phone as Second action
- new OutOfOffice status (skip - go to Second action by default)
User profile
- possiblity to forward to mobile phone as Second action
- possiblity to forward to alternative number as Second action
- new OutOfOffice status
New Template-IVR profile
- supports time checker and same statuses as Group profiles
- menu can contain up to 10 options (instead of 5)
- in case of wrong input a specific error message can be played
- in case of no input a specific error message can be played or fallback action
- a connection to the SMP is needed in order to configure this new version (needed to support status change)
- previous IVR profile is renamed to UC-EOL-IVR
Conferences: add possibility to announce the name of the participants when leaving or joining the conference (participant has to record his name)
Automatic login/logout from queues based on user status
Multiroute
Business code
Polycom IP331 phone shows the queue login status
Internationalization
- 3 languages supported: french, dutch and english
- status shown on phones in the language of the user (if phone permits it)
- messages played in a smart way
- profile parameters translated in net.Desktop
Support for External Contacts integration
- in Polycom's Corporate Directory
- in net.Console
- possibility to show name for imported contacts on the screen for incoming and outgoing calls
Voicemail greeting is now synchronized
Fax Server for incoming faxes
Support for Cisco ATA boxes, only FXS
DHCP Server available by default
Possiblity to have multiple receptions (main numbers)
- Configurable in the User/Manager profile
- Configurable in the Receptionist profile for the fallback
3 additional access levels for user profile parameters restrictions
ListPackages task added by default in order to permit modules installation check
Template version shown on the SMP

See below for more details.

Features

User/Manager

Profile colors

Users can manage themselves the telephony behaviour for their extension
Default parameters are configured
The access to the parameters sections by the end user can be restricted in several levels. A color is therefore added to the profile names. See table below for a rough idea of what is accessible by who
The admin can always change the parameters

	Forward settings	First action	Second action	My groups	Important numbers	Personal Menu options	Security options
Green
Blue
Purple
Red

Have a look at the features below to find out per feature who can access it.

Features

All those features can be configured per User/Manager
See the callflow possibilities in those diagrams: User callflows - Manager callflows.
Available statuses
- Office
- Teleworking
- Busy
- Holiday
- Out of the office
CFU (Green - Blue - Purple - Red)
Configurable ring time (Green - Blue - Purple)
- Up to 5 minutes (depending on operator)
- 30s by default
Different behaviour depending on status and whether internal/external call (Green - Blue - Purple)
- Options:
  - Ring Primary phone, or
  - Ring Primary and secondary phone, or
  - Ring Assistant (manager only), or
  - Ring Secondary phone, or
  - Play a "holiday" or "busy" message, or
  - Go to Second action (skip)
- Default behaviour
  - Office - Ring Primary & Secondary phone
  - Telework - Ring Secondary phone
  - Busy - Play busy message
  - Holiday - Play holiday message
  - OutOfOffice - Go to Second action (skip)
Different behaviour when assistant calls (manager only) (Green - Blue)
- Options:
  - Ring Primary phone, or
  - Ring Primary and Secondary phone, or
  - Ring Secondary phone, or
  - Forward to mobile phone of the user (no Second action will be executed), or
  - Go to Second action (skip)
- Default behaviour: Ring Primary & Secondary phone
Fallback
- Second action always executed if call not answered during First action, except for "Forward to mobile phone"
- Second action is common for every status and internal/external call
- Options for Second action (Green - Blue)
  - Voicemail, or
  - Forward to My assistant (manager only), or
  - Forward to mobile phone of the user, or
  - Forward to my team, or
  - Forward to alternative number, or
  - Forward to my reception (or general reception), or
  - Personal Assistant Menu
- Options for Personal Assistant Menu (Green - Blue)
  - Voicemail, and/or
  - Forward to Alternative number, and/or
  - Forward to mobile phone of the user, and/or
  - Callback (internal calls only), and/or
  - Forward to My reception (or general reception if not defined), and/or
  - Forward to My team, and/or
  - Forward to My assistant (manager only)
- Personal Assistant Menu
  - Options can be enabled one-by-one
  - Options are always presented to the caller as a continuous IVR starting from choice 1.
  - Options enabled by default:
    - Voicemail
    - Forward to mobile phone
    - Forward to My assistant (manager only)
CFB (Green - Blue - Purple - Red)
- Disabled by default
Call waiting (Green - Blue - Purple - Red)
- Enabled by default
- Second call send to the phone
Change important numbers (Green)
- Assistant number: extension (manager only)
- Team number: extension
- Alternative number
- My reception: extension
CLIP/CLIR (Green - Blue)
Dynamic member of up to 3 queues
- Penalties from 0 to 10
- Queue Login/logout based on status change via the phone or net.Desktop (not SMP)
  - Office: Primary phone logged in (only)
  - Telework: Secondary phone logged in (only)
  - Busy, OutOfOffice, Holiday: Primary and Secondary phones logged out
  - Can be disabled/customized in extension 8855
Call forwarding behaviour
- The admin can configure restrictions for call forwarding (CFU, CFB, forward to alternative number, mobile number):
  - Internal numbers
  - National numbers
  - National and mobile numbers
  - National, mobile and international numbers
  - National, mobile and premium numbers
  - No restriction
Pincode
- empty by default
- editable by the admin on the SMP (change only, impossible to view)
- editable by the user using the phone
- in case no pincode was set and the user tries to access authenticated services
  - on his own extension: system asks to define a new pincode (as from UC Template 3.0.5)
  - on another extension: access is refused

net.Desktop

net.Desktop has been included in the template. The version of net.Desktop supports a multi-language interface (the language is not pushed but needs to be chosen by the end-user)
outgoing fax and call recording features are not part of the default package, see options

Languages

3 supported languages for telephony default prompts and user interfaces:
- English
- French
- Dutch
Messages will be played in a smart way
- Internal calls: the language of the caller will be used
- External calls: the language of the called will be used
Phone display automatically in the language of the user (except soft buttons)
net.Desktop application and parameters are translated in user's language
Mails sent by the SOP are always in English (voicemails, incoming faxes)

Phones

Depending on the phone model, the features might be different

Polycom ip 331
- Call transfer
  - Blind
  - With consultation
- Supported for PUM without reboot
- Directory on the phone
  - Personal contact directory (limited to 99 contacts)
  - Corporate directory (live lookups on the SOP, no limit on the phone)

Users manage their own contact directory and speed dials via the phone itself so that those are kept after a reboot.

Some other phones have been tested with the template. You can find the tested features in the install guide. Keep in mind that these phones do not come with a default configuration, which means that you need to configure the phones entirely yourself (there is an example configuration however)

Voicemail

Activated by default
New voicemails shown on the phone (flashing light and informations on the screen depending on the phone)
Telephony voicemail menu with 2 folders : "new" and "old" (see short codes)
Voicemail menu protected by pincode
Access to voicemail menu via a soft button, short code and external number (if configured)
Access to someone else's voicemails via short code
Access via net.Desktop, voicemails played via PC speakers
Sent via e-mail as wav file to e-mail address of the extension
Name can be defined for the welcome message or full welcome message can be recorded through telephony voicemail menu

PUM

Call a specific number to log in (see short codes). The message is played in the language of the phone's current extension (English if no extension)
Call a specific number to log out (see short codes). The message is played in the language of the phone's current extension (English if no extension)
No reboot required (unless needed (polycom only))
Works cluster-wide, both for Polycom and Aastra phones
Extension mobility only on the same brand of phone
Personal directory and speeddials do not follow
See short codes

IVR/Groups

IVR

After an optional time check, a menu is played
In case of holiday, out of office hours or lunch, a specific action can be executed
- Forward to a number (internal or external)
- Play a message (to be recorded)
- Send the call to Voicemail
The automatic time check can be overruled by changing the status. This will force the "holiday-", "out of office hours-" or "lunch-" action, depending on the chosen status
Status can be changed using feature "Change status of another extension" (pincode protected)
The menu can contain up to 10 options (from 0 to 9)
Each option can be configured to
- Forward to another number (internal or external)
- Play a message (to be recorded)
- Send the call to Voicemail
Options can be deactivated
If a wrong option (for example: deactivated) option is chosen, a error message can be played. The menu is repeated afterwards
If no input is given by the caller within 5s the menu is played again up to 9 times (configurable), after a fallback option can be executed
The IVR extension has a dedicated pincode, requested for status change, prompt recording and Voicemail box access.
Prompts can easily be recorded via the phone (see short codes) or by uploading them to the SOP

Common group features

2 types of call groups exist. A call group is a number that allows to dispatch incoming calls over one or more agents. Note that this has nothing to do with group pickup.

After an optional time check, the call goes to the group
In case of holiday, out of office hours or lunch, a specific action can be executed
- Forward to a number (internal or external)
- Play a message (to be recorded)
- Send the call to Voicemail
The automatic time check can be overruled by changing the status. This will force the "holiday-", "out of office hours-" or "lunch-" action, depending on the chosen status
Status can be changed using feature "Change status of another extension" (pincode protected)
A welcome message can be played before ringing agents
Agents should be located on the same physical SOP
A configurable message will be displayed on the phone of the agents when a call is received
The group extension has a dedicated pincode, requested for status change, prompt recording and Voicemail box access.
Prompts can easily be recorded via the phone (see short codes) or by uploading them to the SOP

HuntGroup

The group allows for up to 15 agents to be called one after the other. The group will always start at the first agent
Each agent will be called for a same amount of seconds. This timeout can be
- 5 seconds
- 10 seconds
- 20 seconds
- 30 seconds
- 40 seconds
- 50 seconds
When reaching the last agent, the group will restart with the first agent. The number of times that the group will be retry is between 1 and 10 (configurable)
In case all available agents are busy, a fallback action will be executed
- Forward to a number (internal or external), or
- Play a message, or
- Voicemail
In case no one has answered after the timeout (number of available agents * timeout per agent * number of retries), a fallback action (Second action) will be executed
- Forward to a number (internal or external), or
- Play a message, or
- Voicemail
Agents can be configured by entering their internal extension
The hunt group only uses the primary phone of the agent
The hunt group has no support for login/logout
Default configuration:
- Member ringing time of 10s
- Retry 10 times to reach an agent
- Voicemail as Second action

CallQueuer

Group based on a queue
The call can stay in the queue for a configurable time
- 10 seconds
- 20 seconds
- 30 seconds
- 1 minute
- 2 minutes
- 5 minutes
- 10 minutes
- 15 minutes
- 30 minutes
In case no agents are logged in, a fallback action will be executed
- Forward to a number (internal or external)
- Play a message
- Send the call to voicemail
In case no one has answered after the timeout, a fallback action will be executed
- Forward to a number (internal or external)
- Play a message
- Send the call to voicemail
Callers will hear waiting music or a ringtone (configurable)
The call can distributed between the agents by using a specific strategy
- ringall
- leastrecent
- fewestcalls
- random
Agents can be part of the callqueuer in different ways
- By changing their status (automatic log in/out)
- By calling a service number (see short codes)
- Permanent member (not possible to log in or out) * Default configuration:
- Ringtime 10s
- Play music while waiting
- Display name not updated
- Voicemail as second action
- When no members available: second action
- When group is closed: second action

CallerID manipulation for external calls

The CallerID is always set to the transferrer number in case of external calls forwarded or blind transferred to external. It is the case for:

User/Manager profiles
Short numbers
CallQueuers, HuntGroup, IVR

The CallerID is not modified for internal calls and internal calls forwarded or blind transferred to external.

CFU/CFB specific (User & Manager profiles)

UC Template 3.0.5+

forwarded to	internal	external
internal call	num: caller name: <transferrer_ext> - <caller_name>	num: caller
external call	num: caller name: <transferrer_ext> - <caller_name>	num: transferrer *

* For CFU and if the external line supports the SIP transfer method the caller number can also be shown for external calls forwarded to external. This is to be configured in the incomingCallCatcher.

UC Template 3.0.0 - 3.0.4

forwarded to	internal	external
internal call	num: caller name: <transferrer_ext> - <caller_name>	num: transferrer
external call	num: caller name: <transferrer_ext> - <caller_name>	num: transferrer

As a comparison on UC Template 2.x the original CallerID was always kept (possibly modified by the operator for external calls).

Voicemail for IVR's, and Groups

Voicemail prompts can be configured the same way as User/Manager Voicemail
Use feature "Consult voicemail of another extension" (pincode protected)
New voicemails are not shown on phones
New voicemails are sent by e-mail to the e-mail address of the group extension (only 1 e-mail address, but this can of course be one of your group mailboxes)

Opening hours

Opening hours can be defined for Groups and IVR's (HuntGroup and CallQueuers). Those are defined via separate profiles so that different opening hours can be configured and a single configuration can be used for several Groups and general numbers extensions.

5 schedules

For each opening hours configuration, up to 5 day-schedules can be defined. Those can be linked to a weekly calendar (7 days). Each schedule can be:

always open
always closed
open from A to B
open from A to B with lunch break from C to D

Holidays

Recurring holidays (every year on same date) and non-recurring holidays can be defined for each opening hours configuration.

Group pickup

There are 3 types of pickups. For all 3 types, the phone of the user who does the pickup and the picked up phone should be on the same SOP

Group pickup
- allows to pickup the phone of someone in the same group
  - maximum 31 different groups
  - defined by the administrator
- see short codes
Extension pickup
- allows to pickup a specific extension
- see short codes
Department pickup
- allows to pickup the phone of someone in the same department
  - defined by the administrator
- see short codes

Short codes

Short codes have been foreseen These short codes allow to change certain settings (not all of them) and to access service numbers
- (De-)activate call waiting
- Consult voicemail (of another extension)
- Change pincode
- Extension, group and department pickup
- Business code (in & outgoing)
- (De-)activate CFU
- (De-)activate CFB
- Log in/out to/from group(s)
- Pum log in/out
Additionally, some technical numbers have been foreseen
- Record group & IVR messages
- Play system information

The ability to change Personal Menu settings via a short code has been removed

Conferences

Up to 20 conference rooms can be created. Conference rooms are protected by a pincode. These conference rooms allow you to talk to multiple people at the same time.

It is possible to force the caller to record his name before entering the conference room. Other participants will hear 'recorded name has entered/left the conference' The announcement will be played to all participants in the language of the person who joins the conference

Receptions

It is possible to define multiple receptions (main numbers) with multiple receptionists for each receptions.

net.Console

Except for 2 features ("active-active" and "internal reception"), all features of the net.Console are supported. The net.Console can easily be configured by using the Template-Receptionist-Green profile for the receptionist itself and by using a CallQueuer for the reception number

Short Numbers

The ShortNumber profile allows you to call an internal extension, which redirects you to another (longer) number. These numbers are configured by the system administrator
Example: Call 5000 to talk to the taxi company. ShortNumbers are considered "trusted" numbers: a user who has restrictions to only be able to call internal numbers, will still be able to call the taxi company on the internal number 5000, even if it redirects to an external number When receiving a call from a number that is configured as ShortNumber, the name and number will be replaced by the one configured for the ShortNumber (configurable).
Example: When the taxi company calls, it will show "Taxi company <5000>" on the screen

FMU

Configuration to support FMU has been included by default. By selecting a restriction group which ends on "FMU" (example: NoRestrictFMU), all calls coming from this device will be rerouted to a special call catcher. When calling an external number that arrives on the SOP, the call is being redirected immediately to the extension instead of going over the external trunk

To avoid to be unable to call unlogged FMU users on their mobile number from an internal phone (the FMU device is unregistered and the call towards the mobile phone number is rerouted to the internal extension), a mechanism exists to push these calls to the FMU trunk

External connectivity (SIP, ISDN)

SOPs are supporting multiple types of interfaces for outgoing and incoming calls:

SIP trunk
PRI-ISDN trunk (EuroISDN), also known as PRA
ISDN-BRI trunk, also known as BA

ISDN trunks of the same type (PRA or BA) can be grouped together to form 1 single interface.

A Trunk Group is a set of up to 4 outgoing interfaces (not necessarily of the same type), which can be selected by a linear hunt mechanism or by a load sharing mechanism (using the CallInterface action).
Example of a Trunk Group (*):

Default outgoing interface: SIP trunk
Fallback interface 1: 1PRA
Fallback interface 2: 4BA
Fallback interface 3: none

(*) Depending on your server hardware and interface cards, this specific combination of interfaces might not be possible.

Multi route

Each user and manager can be configured to be part of a route group (no group, group 1, group 2, ... , group 9). Depending on the chosen route group, a different trunk will be used for outgoing calls.

Making an outgoing call by calling a ShortNumber does not change the route group of the user. In some cases however, no route group will exist (ex: incoming call on external number connected to a ShortNumber).

In case of internal calls forwarded to external destinations (transfer, blind transfer, CFU, CFB, "forward to cell phone", "forward to my alternative number") the route group of the transferrer is used.

This functionality is limited to single-sop only.

Business code

The ability to tag your calls with a specific code has been foreseen. This is typically used by lawyers ho want to charge the time they spent on the phone to their clients.
The code that can be used to tag calls should be 4 digits long and is not checked (free code).
For outgoing calls, a prefix which includes the code, should be dialed before the number.
For incoming calls, it is only possible to tag calls in the following circumstances

The call is an external call
The option has been activated for the called user (disables re-invite)
The call has been made directly to the users external number (the call has not been transferred before)
The call is still ongoing

Fax

Incoming faxes

3 solutions are available for incoming faxes

Fax machines connected to an FXS port on the SOP
- Although this works very well, this way of connecting fax machines is not recommended for new customers
Fax machines connected to an ATA convertor
- This is the preferred way of connecting physical fax devices
Virtual faxes

Outgoing faxes

2 solutions are available for outgoing faxes

Fax machines connected to an FXS port on the SOP
- Although this works very well, this way of connecting fax machines is not recommended for new customers
Fax machines connected to an ATA convertor
- This is the preferred way of connecting physical fax devices

Modem

It is advised to connect modems on a separate line. If really needed, they can be connected to an FXS card on the SOP (ATA boxes can not be used!)

Communication server 2

T38

T38 is supported as from version 3.0.0 of Escaux Fusion. This allows you to reliably connect fax devices on ATA boxes

CAC

Call Admission Control will allow you to limit the bandwidth between sites

Connected line Identification presentation (COLP)

As from Template 3.0, the name of the called person can be shown on the screen. The following has been implemented:

When calling a user or manager, his name will be shown
When calling a number that needs authentication (voicemail, change pincode, ...), a CallQueuer, a HuntGroup, a conference or an IVR, the name of the service will be shown in English
When calling an emergency number, SOS will be shown
When calling the system information number, the SOPkey will be shown

More information on COLP can be found here

COLP and call history

Call history is phone dependent. On both Polycom and Aastra phones, the following has been implemented:

Step 1 : A(1000) calls B(2000)
Step 2 : B(2000) calls C(3000) while A is on hold
Step 3 : B(2000) transfers the call from A(1000) to C(3000)
Step 4 : A(1000) hangs up the call and looks at the call history

The following will be shown on the screen of phone A

	Name	Number
Step 1	B	2000
Step 2	B	2000
Step 3	C	3000
Step 4	C	2000

Note that in step 4 the name does not match the number in the call history

Basic reports

Database lookups

A lookup in database can be activated in the incomingCallCatcher in order to retrieve the caller name and extension if known by the SOP: ShortNumber or user's mobile number. That way names and extensions can be showed on the phones and net.Console instead of external number.
If an integration has been done (using the Unified communication model), it is also possible to lookup the name of an imported contact. The name will be shown both for incoming and outgoing calls

SMP

Restrictions

As from template 3.0.0, all resources and modules will be unavailable, except if they have been validated by Escaux. Requests to validate new resources or modules can be sent to the service desk.

cheat mode

Under specific circumstances, it might be needed to select modules or resources that have not been validated. Example: due to a specific setup of the clients network, an application does not work. If another version of the application exists which solves the problem, Escaux might decide to activate "cheat mode". This mode will allow to select all versions of the resources and modules, without blocking the "apply changes" functionality, even if a not validated version has been detected. This mode can only be activated by Escaux employees under very specific circumstances:

High criticality
Big impact

The server will, from that moment on, stay in cheat mode until a new version is available which contains the fix. While the server is in cheat mode, everyone will be able to select any resource or module, making it prone to configuration issues. Additionally, the configuration is potentially unstable as the combination of resources and modules has not been tested extensively like in a real version

Template version

The version of the template will be visible in the web interface of the SMP

logging and snapshots

Every change that has been made on the SMP will be logged. A report is available to be able to find out who made which change. In case of problems, automatic snapshots are made at every apply changes.

Advanced reporting (needed for business code)

Filemanager

The filemanager is included in Escaux Fusion and can be used to upload prompts and music on hold. The filemanager is accessible via HTTPS or via webdav

Monitoring

The SOPs are being monitored by the SMP. Following checks are being executed:

Application management server
CPU load average
DB connections
DB consistency
Database server
Disk space
Ethernet traffic
Mail server
net.Console availability
NTP server
SIP selftest
web server

Shell

A sop shell is available. It allows to:

perform basic troubleshooting
restore SOP-SMP connectivity
restart SOP services
reboot the SOP
perform an active/standby switch

It runs in a text terminal and is accessible via local console or SSH.

Supported cards

Due to the upgrade to Communication Server 2, only sangoma cards can be used. For a general overview of supported hardware, have a look here

Zero config

The Zero config service permits to skip the provisioning tasks to be done on the SMP. The phones can simply be connected to the network and the first time those are used the extension to configure will be asked by the system.

Sysinfo

This servicec (see short codes) can be called to find out information about the SOP without needing access to the SOPshell or the SMP. Following info can be retreived:

SOPkey
ip address
date and time

This can be useful for support

Architectures

The following architectures are supported

standalone
active/standby
a cluster with an active/active SOP pair
clusters with a combination of the previous setups

Have a look at the installation guide for more info about redundant break outs

Internationalization

The UC Template only contains a Belgian routing table (ex: 0475 is mobile traffic).