The Dial Plan Analysis Table is the guide that the software uses to translate the digits dialed by users. This screen enables you to determine the beginning digits and total length for each type of call that Communication Manager needs to interpret.

Use the Dial Plan Analysis Table screen to define the dial plan for your system.

• Call Type - Indicates what the system does when a user dials the digit or digits indicated in the Dialed String column. The Dial Plan Analysis Table screen contains the following call types:

  • Attendant (attd) - Defines how users call an attendant. Attendant access numbers can be any number from 0 to 9 and contain 1 or 2 digits.

  • Dial access code (dac) - You can use trunk access codes (TAC) and Feature Access Codes (FACs) in the same range. For example, you could define the group 100 -199, which would allow both FAC and TAC in that range. Dial access codes can start with any number from 1 to 9, * and #, and contain up to 4 digits.

    Note:

    You cannot enter a range specifically for trunk access codes on the Dial Plan Analysis Table screen. However, with the Trunk Group screen you can assign a TAC to a trunk group. The TAC you enter on the Trunk Group screen must match the format you have administered for a DAC on the Dial Plan Analysis Table screen.

  • Enbloc extensions (enb-ext) - Defines a block of extensions that must be dialed using a prefix when the caller dials from a keypad. These extensions can be dialed without a prefix if the caller dials enbloc, for example, from a station call log.

    Important:

    To avoid dial plan conflicts, Avaya recommends you to put all extensions under the same first digit or group of digits, leaving the other leading digits free for short dialing within a branch.

  • Extensions (ext) - Defines extension ranges that can be used on your system.

  • Feature access codes (fac) - FAC can be any number from 1 to 9 and contain up to 4 digits. You can use * or #, but only as a first digit.

  • Uniform Dial Plan (udp) - The udp call type works identically with the ext call type, with this exception:

    • If dialed digits match the call type of udp, Communication Manager automatically checks the UDP Table first to see if there is a match, regardless of the value in the UDP Extension Search Order field on the Dial Plan Parameters screen. If there is no match, Communication Manager then checks the local server.

    • If dialed digits match the call type of ext, Communication Manager checks the value in the UDP Extension Search Order field on the Dial Plan Parameters screen.

      • If the value in the UDP Extension Search Order field on the Dial Plan Parameters screen is udp-table-first, Communication Manager checks the UDP Table first to see if there is a match. If there is no match, Communication Manager then checks the local server.

      • If the value in the UDP Extension Search Order field on the Dial Plan Parameters screen is local-extensions-first, Communication Manager checks the local server first to see if there is a match. If there is no match, Communication Manager then checks the UDP Table.

      With the udp call type, Communication Manager can recognize strings of 14 and 15 digits, which are shorter than the maximum extension length of 18 digits. However, the udp call type can be used with any length in case this provides a useful new capability to customers.

    Note:

    If you are administering a Per-Location Dial Plan, you must use the Uniform Dial Plan feature.

• Total Length - Indicates how long the dialed string will be for each type of call.