# ARS Digits Dialed

## Purpose

The Automatic Route Selection (ARS) Digits Dialed form initiates the routing of trunk calls when certain digits are dialed from a station. A number of forms can be used to arrange digit strings into groups, each group with a unique set of Leading Digits. For example, an ARS assignment for the Leading Digits 9416 (the trunk access code "9" plus the area code "416") might list in the Digits Dialed field all office codes within the 416 area code.

Use this form to perform the following tasks:

- Program Advanced Automatic Route Selection

- Program Automatic Route Selection (ARS)

- IP Networking Programming

- Program Overlap Outpulsing

- XNET Programming

- Program Account Codes - Verified and Non-verified

- Programming Kari's Law Requirements (only for Container-based MiVoice Business (cMiVB))

## Conditions

- Wildcards should be used with care. If used improperly, they can produce unforeseen results. The wildcard N covers digits 2 through 9; X covers 0 through 9; and Y covers digits 0 through 9, plus * and #. If you only have a few routes to specify, it's preferable that you specify the routes explicitly using digits.

- Given two similar rules, ARS always evaluates the most specific of the two - wildcards are considered to be less specific than explicit digit specifications. For example, if ARS is programmed with two rules: one with digits specified as "776N", and the other with digits specified as "7765", it would always select the "7765" route when a user dials "7765432".

- In order to use "range programming" to program dialed digits, the dialed digit string must contain only the digits 0 through 9 (*, #, N, X or Y cannot be used).

- Prior to the implementation of ARS dialed digit wildcards, it was valid to specify multiple identical explicit digit strings, as long as they had unique numbers of following digits.

For example, both of these were valid and unique entries: "9592 +4 Route 1" and "9592 +7 Route 2". With wildcards implemented, the system considers such entries invalid. If you have existing ARS route definitions of this nature, the system will detect them when you perform a data restore and convert them automatically to valid ARS wildcard based equivalent definitions. For example, the system would convert the above digit definition strings to: "9592YYYY +0 Route 1" and "9592YYYYYY +0 Route 2".

- When you use ARS wildcards, the first digit in the digits dialed string must be a digit, not a wildcard.

- If while adding a route to this form a "There is no more room for new records." error message is displayed, you may have exhausted the available allocation of digit or route termination blocks. To increase this allocation, increase the number of units of digit blocks in the Dimension Selection form.

- The FXS port in an EX Controller does not support leading digits.

- If a call fails because the ARS digits configured in this form match the "Local" cluster element CEID digits (configured in the Cluster Elements form). delete the appropriate ARS entry from this form. If the system displays the error message "The associated cluster element digits should be deleted first", complete the following steps to delete the ARS entry:

- In the Cluster Elements form, temporarily change the Local Cluster Element ID Digits to a different digit string.

- Delete the ARS entry from this form.

- Change the Local Cluster Element ID Digits in the Cluster Elements form back to the original value.

## Field Descriptions

Parameter | Description | Default Value
Digits Dialed | Enter the partial or complete external numbers dialed to access subsequent routing information. The Digits Dialed entries for a given Leading Digits entry must be unique, and the number resulting from the Leading Digits and Dialed Number entries must form a unique number in the digit tree. You can specify a string of dialed digits using any combination of explicitly defined digits (for example "1" or "5") or ARS wildcards (N, X, or Y). You use explicit digits to specify patterns of digits. Wildcards let you specify multiple matching digit combinations with a single entry. You can use the following wildcards: N or n specifies a digit between 2 and 9 inclusive. X or x specifies a digit between 0 and 9 inclusive. Y or y specifies a digit between 0 and # inclusive. Route selection evaluates both the Leading Digits and Dialed Number entries before selecting an appropriate termination. Leading Digit entries can be up to 25 digits in length. You can specify a string to be used to support REDIRECT/REFER to any URI with SIP. You must use the same routing prefix specified in the SIP Device Capabilities and SIP Peer Profile forms. | Blank
Number of Digits to Follow | Select the number of digits expected to follow the partial number specified under Digits Dialed. Can be from 0 to 25 (or unknown if the expected number of digits is variable). NOTE: For Forced Non-verified Account Codes, if you want the "#" character to be used to terminate dialing, set this field to "unknown". | 0
Termination Type | Select "Route" if the calls to the specified digits are to go directly to a route, "List" if the calls are to go to a route list, or "Plan" if the calls are to go to a route plan. | Route
Termination Number | Enter a Route Number, Route List Number, or Route Plan Number to link to routing information in the ARS Routes form, ARS Route Lists form, or ARS Route Plans form. | Blank

## Example

To view examples of ARS entries, refer to ARS Programming example .