.. _emergency-and-cli-settings:


Emergency and CLI Settings
--------------------------

.. _19.2.1|VOSS-611:


This feature, accessed from the default menu **Dial Plan Management > Advanced
Configuration > Emergency and CLI Settings** provides a facility for mapping a site
specific CLI (Calling Line Identity) for emergency and non-emergency calls. This
allows users to roam using extension mobility and still provide a site specific
emergency number appropriate to the site they have visited.

When deploying an HCS site dialplan, a site specific emergency number is configured
as a default emergency number for all devices at that site. This feature allows
users making an emergency call from within their own site to present a CLI of their
own individual DDI (Direct Dial In) instead of the site wide emergency CLI.

A CLI mapping and secondary CLI mapping can also be created using this feature.
The behavior is controlled through settings that can exist at any hierarchy.

This feature allows a Provider administrator (or higher) to add up to three (3)
new calling party transformation patterns to provide specific translation to a DDI
for those DNs having a DDI mapping. The transformations are created and deleted
when either '1 to 1' or '1 to N' number associations are created and deleted. See
:ref:`associate_set_e164_numbers_to_one_directory_number` and :ref:`associate_range_e164_numbers_to_range_directory_numbers`   

Using the HCS dialplan schema, site wide mapping is provided using a wildcard match
to a site specific prefix used only for emergency calls. An example is '**\*156*!**'.
This feature may be used to add more specific patterns such as '**\*156*81214000**'
in order that transformations to the E164 can take place. DNs that do not have a
mode specific match fall back to the wildcard match as previously set, and therefore
use the site wide emergency CLI.

.. note::

   There is no requirement to use any schema. This feature can be used wherever
   transformations are required as part of DN association.
	
The supported transformation patterns are:

* **Emergency CLI** transformation
* **CLI** transformation
* **Secondary CLI** transformation

A data model contains settings for this feature. A default set of settings is
created at the ``sys.hcs`` hierarchy, which disables all 3 patterns. These settings
must be cloned and used at a lower hierarchy to provide the settings required
for each hierarchy, that is clone them to the provider level for platform wide
settings, or customer level for customer specific settings.

Each of the 3 patterns can be enabled or disabled independently. The following
additional controls are available:

* Macro for defining the partition
* Macro for defining the E164 number format
* Macro for defining the DN (pattern) format

There are 3 new macros that can be used as part of these settings:

* EmergencyAndCLITransformations_SiteCountryCode - returns the country code, e.g. 44
* EmergencyAndCLITransformations_SiteCountryCodeWithPlus - returns the country code
  with a plus, e.g. +44
* EmergencyAndCLITransformations_NationalTrunkPrefix - returns the trunk prefix,
  e.g. 0

Each of these macros is country aware and returns the settings appropriate to the
site where the DN association is performed.

In addition to these macros, there is a set of pwf context variables that can be
used in the settings macros:

* pwf.e164_number - the E164 number from the mapping transaction
* pwf.dn_number - the directory number from the transaction
* pwf.sitePrefix - the site prefix number as used for HCS emergency calling

.. note::

   Only site level associations are supported, no support is provided for linked
   sites.