This section provides information about how the Dial Plan feature interacts with other features.

• Attendant Display and Telephone (Voice Terminal) Display

  Prefixed extensions display without the prefix. Although the telephone does not display the prefix, when you press the return call button, the telephone dials the number with the prefix.

• Integrated Services Digital Network-Basic Rate Interface (ISDN-BRI)

  When an ISDN-BRI station dials a number with additional digits, the station does not recognize the Conference or Transfer buttons. The calling party must delay dialing for 3 seconds or dial # to indicate that the call must route based on the digits already dialed. The station then recognizes the Conference or Transfer buttons and Communication Manager completes the call operation.

• Multifrequency signaling

  Countries that use R2-MFC trunk signaling without Group II tones support flexible numbering. In these countries, if extensions have different first digits, extensions with different lengths are supported.

• Property Management System (PMS)

  Property Management System (PMS) products support a maximum length of 5 digits for extensions. Extensions for PMS are administered on the Dial Plan Analysis screen. If the PMS Log Endpoint field and the Journal/Schedule Endpoint field on the Hospitality System Parameters (HSP) screen are enabled, Communication Manager supports administration of an extension with a maximum length of 7 digits. This condition on the maximum length of extensions applies even if the Special Application SA8662 is enabled.

  Note:

  If the Dial Plan Analysis screen has extension entries of more than 7 digits, you cannot enter a value in the PMS Log Endpoint field and the Journal/Schedule Endpoint field. You can administer PMS, PMS_JOURNAL, and PMS_LOG fields on the IP Services screen, but not on the Hospitality System Parameters screen.

• Uniform Dial Plan

  In a DCS environment, to assign extensions from UDP to other servers or switches, the length of extensions must be identical.

• Single-Digit Dialing

  • A prefixed extension contains 5 digits, which includes the digits of the prefix and the digits of the extension.

  • In a dial plan with mixed station numbering, extensions with different lengths can contain 1 to 16 digits.

• Multi-location Dial Plan

The following are the interactions of the Dial plan feature with the Multi-location Dial Plan feature:

• Attendant

  This feature provides a way to administer multiple attendant codes. If you have not administered Attendant Partitioning, Communication Manager supports only one attendant group for each switch. This feature supports Local Centralized Answering Points (LCAP). LCAPs do not require attendant groups to support administration of multiple attendant codes.

• Attendant Vectoring

  If you enable the attendant vectoring feature, this feature takes precedence over existing local attendant codes. Using call vectors, Communication Manager processes attendant seeking calls or Dial 0 calls. Attendant vectoring is administered by using the local attendant codes and attendant code fields on the Dial Plan screen or the attendant access code field on the Feature Access Code screen.

• Automatic Circuit Assurance

  The field ACA Referral Destination on page 1 of the System Features Parameters screen requires the administration of the attendant on the Dial Plan Analysis Table or the attendant access code on the Feature Access Code screen. This field requires that an attendant group exists.

• Automatic Wakeup

  Pending automatic wakeup settings are canceled when you run the change extension-station command.

• Call Forwarding

  Call forwarding settings are lost when you run the change extension-station command. If the changed station is a forwarded-to station, you must manually update the extension using the forwarded-to extension.

• Call Park

  Commonly shared extensions cannot park calls because these extensions are not assigned to physical stations. The range of commonly shared extensions can be shared in any location.

• Crisis Alert

  Running the change extension-station command does not update the originating extension on the Crisis Alert System Parameters screen. You have to manually update the originating extension.

• Leave Word Calling (LWC)

  The field Stations with System-wide Retrieval Permission for the Leave Word Calling Parameters on page 2 of the System Features Parameters screen requires the administration of the attendant on the Dial Plan Analysis Table screen or the Attendant Access Code on the Feature Access Code screen. This field requires that an attendant group exists.

• Survivable Remote Server

  After you perform the required administration on the main system, you must save the translations to the survivable system. If the translations on the main system and the survivable system are not synchronized, this feature might not function.

• Night Service

  This feature does not work with Location-based Night Service. A customer may want to restrict attendant-seeking calls to attendants who are local to the calling party because the local attendant most likely speaks the same language as the caller. The customer would require an attendant to place only one location in Night Service, without placing the entire switch in Night Service.

  One way to accomplish this is to use hunt groups as attendant queues. You can separately place each hunt group in Night Service and assign each hunt group with its own Night Service destination. You can administer Night Service destination by tenant, trunk group, or trunk group number.

• Station Hunting

  The station hunting chain is maintained when you run the change extension-station command.

• Survivable Remote EPN/WAN Spare Processor

  In a configuration where a survivable remote server exists, if you administer the main system without performing the same administration on the survivable processor, the changes do not reflect on the survivable server when the survivable server takes control. For example, if you run the change extension-station command only on the main server, the changed extensions on the server do not reflect on the survivable remote server when the remote processor takes control.

• Uniform dial plan (UDP)

  UDP screens are not updated if you run the change extension-station command. External system management tools supported by Avaya handle the UDP table.

The following Communication Manager features, operations, and systems require a user to dial an extension after dialing a Feature Access Code (FAC) or pressing a button. These features support the dial plan extensions of maximum 16 digits in length:

• Add/Remove Agent Skill

• Agent Login/Logout

• Attendant Call Forwarding

• Call Park

• Call Pickup, including Directed Pickup

• Code Calling/Deluxe Paging

• Controlled Restrictions

• EC500 (Extension to Cellular)

• Enhanced Call Forwarding

• Intercom Calling

• Leave Word Calling

• Malicious Call Trace

• Personal Station Access (PSA)

• Posted Messages

• Priority Calling

• Refresh Terminal Parameters

• Remote Access

• Service Observing

• Station Busy Verify

• Terminal Translation Initialization

• Whisper Paging

The following features, operations, and systems also support the dial plan expansion to 16 digits:

• Abbreviated Dialing (AD) – An extension that is stored in an AD button does not change automatically when you change the extension of that station with that extension. If you use the change extension-station command to change a short extension to a longer extension, you must re-programme an AD button programmed with an extension.

• Application Enablement Services (AES)

• ASAI and CTI API.

  Note:

  Device, Media, and Call Control (DMCC) does not support the extensions of digits in length.

• Attendant Direct Extension Selection (DXS) with Busy Lamp

• Attendant Display

• Attendant Vectoring

• Automatic Call Distribution (ACD)

  • With no reporting

  • With reporting by Basic Call Management System (BCMS)

  • With reporting by Call Management System (CMS), IQ, or Avaya Performance Center

• Automatic Customer Telephone Rearrangement (ACTR)

• Basic Call Management System (BCMS) – Non-EAS agent BCMS/VuStats login IDs can be of maximum 16 digits. Administration of the maximum length of an extension can be done through the ACD Login Identification Length field on the Feature-Related System Parameters screen and through the login IDs entered on the BCMS/VuStats Login ID screen.

  Note:

  The BCMS/VuStats login IDs are optional when Expert Agent Selection (EAS) is inactive. If EAS is active, login IDs are required.

• Best Service Routing (BSR) – The Status Poll and Interface VDN fields in the BSR application tables support 16-digit strings.

• Call Vectoring

• Direct Inward Dialing (DID)

• E911

• Expert Agent Selection (EAS): Logical Agents

• Extension Number Portability (ENP)

• External Reporting Adjunct interface – The external reporting interface messaging protocol Switch Processor Interface (SPI) is enhanced to support the expanded dial plan.

• IP Agent, Release 7

• Multi-Level Precedence and Preemption (MLPP) – The MLPP feature works with short extension dialing in Communication Manager Release 4.0 or later. For a user to be able to dial an MLPP access code followed by a short extension, you must change the Conv field on the Precedence Routing Digit Conversion screen to ytoch. The UDP table converts the short-extension-to-long-extension conversion when you enable the Conv field.

• QSIG Message Waiting Indication (MWI) – The DCS/messaging feature does not activate the MWI of stations with extensions that contain more than 7 digits.

• Session Initiation Protocol (SIP)

• Standard Local Survivability (SLS) on G250, G350, G430 and G450 Gateways, and the TGM 550 gateway module

• Meet-Me Conferencing

• VuStats – VuStats displays support longer agent, split, and VDN extensions. To support extensions that contain more than 7 digits, you must update the display formats in Communication Manager Release 3.1 with VuStats Display Formats that supports 7-digit extensions. The system does not update the formats automatically when you increase the extension length.

  Note:

  When longer extensions are used, the fixed 40-character station display cannot accommodate as much other data.

  For more information on BCMS/VuStats Login IDs, see Basic Call Management System (BCMS) earlier in this section.

The following Communication Manager features and operations do not support the dial plan expansion to support extensions with a maximum length of 16 digits:

• Administrable Attendant Access Code: The length of the access code administered through this feature is a maximum of 2 digits.

• Announcements: Recording of the Announcements is not updated to 16-digit dialing and remains at the maximum of 7 digits.

• Basic Communication Management Reporting - Desktop (BCMR-D): This product interfaces with Basic Call Management System (BCMS).

• Distributed Communications System (DCS and DCS+): DCS customers can dial extensions with a maximum of 5 digits. To maintain feature transparency with a longer dial plan, DCS customers must migrate to QSIG.

• Hospitality features, except:

  • Automatic Wakeup: A station with console permissions can enter an Automatic Wakeup request for an extension with a maximum length of 16 digits. The related station display shows only the trailing 7 digits.

    Note:

    No adjustment is made to the number formats that the system sends to the Wakeup Printer. If a Wakeup Printer is administered, extensions longer than 7 digits cannot be administered.

  • Do Not Disturb: A station with console permissions can request the Do Not Disturb feature for extensions with a maximum length of 16 digits. The related station displays shows only the trailing 7 digits.

ISDN-BRI data endpoints: When you add a BRI data endpoint, the Service Profile Identifier (SPID) field takes the new extension as the default value. The new extension must not be more than 10 digits. If the endpoint does not support SPIDs, you must disable the Endpoint Initialization feature.

The following are the interactions for the E.164 extension prefixes:

• Abbreviated Dial Button

  A call placed using an Abbreviated Dial (AD) button ignores the Call Type of enb-ext because the AD button can contain the leading digits of a long extension with the remaining digits entered using the keypad.

• Adjunct Switch Applications Interface

  Calls launched by Adjunct Switch Applications Interface (ASAI) are off-switch calls. When ASAI launches a call, the entire calling number is passed to Communication Manager. During routing, Communication Manager considers the calling number as enbloc and considers the Dial Plan enb-ext entries.

• Attendant Feature Invocation

  To invoke the following features, you must dial through UDP to enter the dial prefix before the full extension:

  • Call Forwarding

  • Call Park

  • Code Calling/Deluxe Paging

  • Controlled Restrictions

  • Leave Word Calling/Message Retrieval

  • Refresh Terminal Parameters

  • Station Busy Verify

  To invoke the following features, you can enter the full extension that matches an enb-ext entry in the dial plan, or you can include the dial prefix:

  • Automatic Wakeup

  • Do Not Disturb

  • Posted Messages

• You can dial using the keypad or enbloc method from Avaya one-X® Communicator. When you use enbloc dialing, for example, click-to-dial, transmits the digits to its Communication Manager server using Application Enablement Services (AES) or Adjunct Switch Application Interface (ASAI). In absence of AES or ASAI, Avaya one-X® Communicator uses the softphone interface to go off-hook and transmits digits. Avaya one-X® Communicator functions similarly to analog telephones, DCP telephone, and H.323-based telephones.

• Call Coverage – Remote

  If you administer a call coverage destination, the extension can be an enbloc extension, for example, Enhanced Call Forwarding. When a call covers to the call coverage path, Communication Manager considers the covered-to number as enbloc and analyzes the Dial Plan enb-ext entries to determine routing.

• Call Detail Recording

  For outgoing trunk calls:

  • Call Detail Recording (CDR) adjuncts record the originally dialed digits or the transmitted digits.

  • Calling extensions reported to CDR is the administered extension.

  For intra-switch CDR:

  • Called extensions is the administered extension.

  • The prefix digits that must be dialed from a keypad to reach the administered extensions are not supported.

• Call Forwarding

  When a Call Forward destination is entered from a keypad, Communication Manager analyzes the digits to determine the last digit of the dialed number. You must dial through UDP to reach the Call Type enb-ext extension.

  If a Call Forward destination is administered, the extension can be an enbloc extension. When a call is forwarded, Communication Manager processes the forwarded-to number as enbloc and analyzes the Dial Plan enb-ext entries to determine routing.

• Call Management System and Call Center Reporting

  Call Management System and Call Center Reporting provide limited support for extensions that contain more than 7 digits.

• Call Vectors

  A Call Vector Route-To destination can be an enbloc extension. When a vector step is executed, Communication Manager considers the route-to number as enbloc and analyzes the Dial Plan enb-ext entries to determine routing.

• Dial Plan Transparency during a Data Network Outage

  Using Dial Plan Transparency, you can dial inter-branch calls during a WAN failure.

• Directed Call Pickup

  When a Directed Call Pickup destination is entered from the keypad, Communication Manager analyzes the digits to determine the last digit of the dialed number. You must dial through UDP to reach the Call Type enb-ext extension.

• Displays

  The E.164 extension prefixes feature has no impact on station displays. In the dial plan, the Call Type enb-ext extension is displayed without any prefix.

• EC500

  Calls launched using the EC500 feature are generally off-switch calls. When EC500 launches a call, the entire calling number is passed to Communication Manager. During routing, Communication Manager considers the calling number as enbloc and considers the Dial Plan enb-ext entries.

• Emergency Calling

  Emergency calling does not function with the Call Type enb-ext extension. In a multinational Communication Manager network, the local ARS and AAR numbering plans are set up to let callers reach an emergency number according to their national routing policy.

• Enbloc DID Trunk Calls

  Trunks that contain the full digit string, do not need to go through the UDP to match on an enb-ext entry in the dial plan. An incoming ISDN SETUP or a SIP INVITE message establishes the calls by using any of the following digit strings:

  • 33-299-31-xx-xx <the actual extension>

  • 0299-31-xx-xx <the UDP version of the extension>

• H.323 Station Registration

  An H.323 station can register in any of the following ways,

  • Short extension

  • Full extension

  • Prefixed extension

  Avaya recommends that you use the short extension method or full extension method consistently because the backup file with the station settings is stored in a file-based number used during registration. If you use different numbers to log in, the station does not save multiple backup files, which can lead to confusion and inconsistent results.

• Integrated Directory

  You can view the administered extension number when you browse the Integrated Directory. Calls launched from the Integrated Directory are processed as enbloc. Communication Manager analyzes the Dial Plan enb-ext entries to determine routing.

• Leave Word Calling

  When a Leave Word Calling destination is entered from a keypad, Communication Manager analyzes the digits to determine the last digit of the dialed number. You must dial through UDP to reach the Call Type enb-ext extension.

• Call Type Digit Analysis

  When a call initiated using the Call Type Digit Analysis feature is considered enbloc. During routing, the Communication Manager server analyzes the Dial Plan enb-ext entries.

• Malicious Call Trace

  When a Malicious Call Trace is activated on behalf of another station from a keypad, Communication Manager analyzes the digits to determine the last digit of the dialed number. To reach the Call Type enb-ext extension, you must dial through UDP.

• Priority Calling

  When a Priority Calling destination is entered from a keypad, the digits are analyzed to determine the last digit of the dialed number. You must dial through UDP to reach the Call Type enb-ext extension.

• Property Management System

  Most Property Management System (PMS) products use the adjunct protocol with extensions not longer than 5 digits. The E.164 feature does not apply to Communication Manager with PMS adjuncts.

• Remote Access

  When a Remote Access FAC is entered from a keypad, Communication Manager checks the digits to determine the last digit of the dialed number. To reach the Call Type enb-ext extension, you must dial through UDP.

• Service Observing

  When an agent extension is entered from a keypad while invoking Service Observing, Communication Manager analyzes the extension to determine the last digit of the dialed number. To reach the Call Type enb-ext extension, you must dial through UDP.