# Location Based Call Routing

## Description

With Location Based Call Routing, a call from an extension to a location based number (LBN) associated with destinations or services such as 911 (Emergency services), 411 (Directory Assistance ), or a corporate Help Desk is sent to the service situated in the same network zone (Network Zones) as the originating device. This ensures, for example, that a New York-based Hot Desk user logged into a phone in Chicago who dials 911, has the call routed to the Public Safety Answering Point (PSAP)
The party responsible for answering the 911 call and arranging the appropriate emergency response, such as sending police, fire, or ambulance teams. for Chicago, not for New York.

### Location Based Number (LBN) Call Processing

When an LBN is dialed, MiVoice Business processes it as follows:

1. Identifies that an LBN has been dialed (for example, 911), based on the Location Based Numbers form.

2. Determines the network zone of the originating device, based on the Network Zones form.

3. From the Network Zones form, retrieves the LBN Prefix for the zone identified in the previous step, for example 300.

NOTES

- In most cases, the LBN Prefix is configured with an Automatic Route Selection (ARS) digit string, but any other dialable string is valid. Configuring the LBN Prefix for each network zone is optional. Instead, a Default Prefix in the Location Based Numbers form can be configured.

- Either the LBN Prefix or the Default Prefix must be configured for the LBN processing.

If no LBN Prefix is configured for the zone, the system retrieves the Default Prefix from the Location Based Numbers form.

NOTE: If the Default Prefix is used, all LBN calls are routed to the same destination, regardless of the zone from which a call originated.

4. Combines the Prefix digit(s) with the dialed digits to form a new number; for example, prefix digits 300 combined with the dialed 911 forms a new number 300911.

5. Processes and routes the new number to the final destination, as if 300911 was dialed.

## Conditions and Feature Interactions

- LBNs are dialable numbers, but they are not associated with physical devices or users, therefore, they don't have the properties of dialable numbers, such as:

- Class of Service (COS) or Class of Restrictions (COR)

- cannot be rerouted or forwarded

- cannot be assigned a zone or tenant number

- After dialing an LBN, the user's display will be updated with the final ringing destination number.

- When a party is transferred to an LBN, the Zone of transferring party is used.

- Station Message Detail Recording (SMDR) will record and display the combined LBN Prefix and LBN as the dialed number.

## Programming

1. Identify all numbers and services considered to be location based; for example, Emergency (911), Directory Assistance (411), etc.

2. Provision the Location Based Numbers.

3. Configure the LBN Prefix in the Network Zones form.

NOTE: This step is optional. If the LBN Prefix is not configured, the system will use the Default Prefix from the Location Based Numbers form.

4. For Emergency Calls, you may also want to configure the Zone CESID field in the Network Zones form.

This field allows you to program a Customer Emergency Services ID (CESID) for each zone. If an emergency call is routed to a different zone and CESID is not assigned to the calling directory number in the CESID Assignment form ( ), the system will not be able to identify the location of the caller. However, if the Zone CESID field is configured, the system will be able to retrieve the CESID information for the zone from which the call was made because the Network Zones form is shared between all ICPs in the network. For more information on CESID, see Emergency Services - CESID Programming.

## Implementation Examples

The following examples illustrate the implementation of this feature in three different scenarios.

In each example, the following configuration values are used:

Location Based Numbers Form
Location Based Numbers | Default Prefix | Comment
911 | 9 | Emergency
411 | 4 | Information
0 |  | Operator
611 | 6 | Help Desk

Network Zones Form
Zone ID | LBN Prefix | Zone CESID
1 | 100 | 11111
2 | 200 | 22222
3 | 300 | 33333
4 |  |

###

### Example 1 - Operator

Scenario: Physical sets located in Zones 2 and 3 are registered with the MiVoice Business system located in Zone 1. Operators are located in Zones 2 and 3.

Requirement: When the user dials "0", the call is routed to the operator in the zone from which the user is dialing.

Programming required:

- Program console in Zone 2 as DN 2000, and Zone 3 console as DN 3000.

- If not already configured, add "0" to the Location Based Numbers form

- If not already configured, add LBN Prefix digits for each zone in the Network Zones form.

Call Processing: When a user in Zone 3 dials "0", MiVoice Business retrieves the digits for the zone of the originating device -- LBN Prefix for Zone 3 is 300. These digits are combined with the dialed digits to form a new number 3000 (LBN Prefix 300 + dialed digit 0 = 3000). The new digits are retranslated and the operator in Zone 3 will receive the call.

SMDR example:
01/17 22:57:37 0000:00:07 16850 *0004 3000 I

ATT1 300

0 168

In this example, extension 16850 (Zone 3) dialed 0 and the call was routed to the operator 3000.

### Example 2 - Help Desk

Scenario: Each location (Zone 1 - Chicago, Zone 2 - New York, and Zone 3 - Atlanta) has an ICP node and a local help desk.

Requirement: All users from all zones will dial the same number (611) and be connected to the help desk located in the same zone as the call originating device (hosted by the same ICP).

Programming required:

- For each zone's ICP, configure the following values in the System Speed Calls form:

- Set the Type field to "Int" to allow SDS to distribute the speed call number to other elements in the cluster as a Remote Directory Number (RDN).

NOTE: For more information on speed call types, see System Speed Calls.

- Set the Overrides Toll Control to "No."

- Enter the following Speed Call Numbers (combined LBN Prefix+LBN DN):

- - 100611 - for Zone 1 (Chicago)

  - 200611 - for Zone 2 (New York)

  - 300611 - for Zone 3 (Atlanta)

- Enter the following Actual Numbers, which are the DNs of the help desk in each zone:

- - 1611 - Zone 1 (Chicago)

  - 2611 - Zone 2 (New York)

  - 3611 - Zone 3 (Atlanta)

Call Processing: When a Chicago-based Hot Desk user travels and logs into a device in Zone 3 - Atlanta, then dials 611, the ICP in Chicago (Zone 1) performs the following steps:

1. Verifies that the dialed digit string 611 is an LBN; using the Location Based Numbers form.

2. Identifies the zone of the originating device (Zone 3); using the Network Zones form.

3. Retrieves the LBN prefix for the zone identified in Step 2; from the Network Zones form.

4. Combines the Prefix digits (300) with the dialed digits (611) to form a new number 300611.

5. Retranslates the number to an RDN that points to Atlanta.

6. Atlanta ICP receives a request for 300611, a speed call pointing to 3611, which is the actual help desk number in Atlanta.

SMDR example:
01/18 22:57:37 0000:00:02 X99999 0002 55510510 7100300611 3611

S3611 100 10510510

A1050048 B 168

In this example, a Hot Desk user 10510 logged into a device in Zone 3 dialed 611. The SMDR from Chicago switch shows that user 10510 (Node ID 555) placed a call to 3611 through a speed dial. Digits 7100300611 were sent on the trunk, where 7100 is the Cluster Element Identifier (CEID), 300 is the LBN Prefix for Zone 3, and 611 is the LBN

### Example 3- Emergency Calls (911)

Scenario: Four nodes located in four different Network Zones are connected with IP Trunk Emergency Routes. All ICPs have routes programmed as type "Emergency" to their local PSTN. Each node has Automatic Route Selection (ARS) for its own LBN Prefix+LBN number pointing to "Emergency" routes to the local PSTN.

The following nodes are included in the cluster:

Zone 1 - Chicago 1
Zone 2 - New York
Zone 3 - Atlanta
Zone 4 - Chicago 2 has no PSTN access, will use Chicago 1's PSTN trunks for 911 calls

Requirement: 911 calls are routed to the PSAP located in the same zone as the device from which the call was made.

Programming required:

For Chicago 1:

- ARS for 100+911 points to Emergency route to local PSTN.

- Emergency IP Trunk Routes to New York and Atlanta.

- ARS 200911 pointing to Route List (New York, then Atlanta), no digit absorption.

- ARS 300911 pointing to Route List (Atlanta, then New York), no digit absorption.

For Chicago 2:

NOTE: There is no LBN Prefix configured for Zone 4 in the Network Zones form, so the Default Prefix in the Location Based Numbers form will be used. The Default Prefix for LBN 911 is 9.

- ARS for 9+911 points to Emergency IP Trunk Route to Chicago 1.

- Chicago 1 has ARS for 9+911 pointing to local Emergency PSTN routes.

For New York:

- ARS for 200+911 points to Emergency route to local PSTN.

- Emergency IP Trunk Routes to Chicago and Atlanta.

- ARS 100911 pointing to Route List (Chicago, then Atlanta), no digit absorption.

- ARS 300911 pointing to Route List (Atlanta, then Chicago), no digit absorption.

For Atlanta:

- ARS for 300+911 points to Emergency route to local PSTN.

- Emergency IP Trunk Routes to Chicago and New York.

- ARS 100911 pointing to Route List (Chicago, then New York), no digit absorption.

- ARS 200911 pointing to Route List (New York, then Chicago), no digit absorption.

## Device Support

Not applicable

## Operation

None