[Index]

Model: data/EmergencyAndCLITransformations_Settings_DAT

Emergency and CLI Settings

Full HTML Help

Overview

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.

Note

To access this feature, go to (default menus) Cisco Dial Plan Management > Advanced Configuration > Emergency and CLI Settings.

When deploying a Cisco 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 Associate a Set of E.164 Numbers to One Directory Number and Associate a Range of E.164 Numbers to a Range of 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:

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:

The following macros can be used as part of these settings:

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:

Note

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

Emergency Handling

Emergency handling is device-based. It uses the device pool local route group to handle call routing. When a phone has no Direct Inward Dial (DDI) or the phone has DDI but it is in a remote location, emergency handling uses the Site's Emergency number.

The implementation is as follows:

The image illustrates Emergency Calling.

Provisioning Emergency Calls

Additional provisioning is not required for emergency calls since VOSS Automate provisions 911 as part of the United States country scheme, and 999/112 is provisioned as part of the United Kingdom country scheme. For more information, see "Emergency Handling".

  1. When creating a site dial plan, enter the emergency number in the Emergency Number field.

    This is the Site Emergency Published Number; it is sent if the line that makes the emergency call does not have DDI. Then, if there is a callback, the Site Emergency Published Number is dialed.

  2. Ensure that a Local Route group is set up with SLRG-Emer set to the Route group. Refer to "Associate Local Route Groups to a Device Pool".

CLI Pattern settings

Model Details: data/EmergencyAndCLITransformations_Settings_DAT

Title Description Details
Hierarchy Default: {{ fn.hierarchy_friendly_path }}
  • Field Name: hn
  • Type: String
  • Default: {{ fn.hierarchy_friendly_path }}
Enable Emergency Pattern
  • Field Name: emerEnabled
  • Type: Boolean
Emergency Pattern Partition macro
  • Field Name: emerPt
  • Type: String
Emergency E164 Pattern Format macro
  • Field Name: emerFormat
  • Type: String
Enable CLI Pattern
  • Field Name: cliEnabled
  • Type: Boolean
CLI Pattern Partition macro
  • Field Name: cliPt
  • Type: String
CLI E164 Pattern Format macro
  • Field Name: cliFormat
  • Type: String
Enable Secondary CLI Pattern
  • Field Name: secondaryCliEnabled
  • Type: Boolean
Secondary CLI Pattern Partition macro
  • Field Name: secondaryCliPt
  • Type: String
Secondary E164 CLI Pattern Format macro
  • Field Name: secondaryCliFormat
  • Type: String
Emergency DN Pattern Format macro
  • Field Name: emerPatternFormat
  • Type: String
CLI DN Pattern Format macro
  • Field Name: cliPatternFormat
  • Type: String
Secondary CLI DN Pattern Format macro
  • Field Name: secondaryCliPatternFormat
  • Type: String