Administration of Dial Plan Transparency (DPT) is similar to setting up Inter-Gateway Alternate Routing (IGAR). You must first enable the DPT feature, then set up Network Regions and trunk resources for handling the DPT calls. For Survivable Core servers, you must also assign Port Networks to communities.
Procedure
Type change system-parameters features, and press Enter.
The system displays the Feature-Related System Parameters screen. Page down until you see the SYSTEM-WIDE PARAMETERS fields.
In the Enable Dial Plan Transparency in Survivable Mode field, enter y.
In the COR to Use for DPT field, enter the Class of Restriction to use for Dial Plan Transparency.
The default is station, where the FRL of the calling station determines whether that station is permitted to make a trunk call and if so, which trunk(s) it is able to access.
Type change ip-network region n, where n is the number of the Network Region to change. Press Enter.
The system displays the IP Network Region screen. Page down until you see the INTER-GATEWAY ALTERNATE ROUTING/DIAL PLAN TRANSPARENCY fields.
In the Incoming LDN Extension field, If not already done for IGAR, allocate one incoming DID/LDN extension for incoming DPT calls.
This extension can be shared by IGAR and DPT – the system will distinguish incoming IGAR calls from incoming DPT calls.
In the Dial Plan Transparency in Survivable Mode field, enter y.
Ensure that each IGAR/DPT-enabled Network Region has sufficient trunks for the expected number of outgoing and incoming DPT calls.
There is no need to set the maximum number of trunks for DPT.
Use existing routing techniques to ensure an outgoing DPT call from a given Network Region will have access to an outgoing trunk.
Unlike IGAR, the outgoing trunk need not be in the same Network Region as the calling endpoint, as long as the endpoint and trunk Network Regions are interconnected.
If you are setting up DTP for a Survivable Core Server, type change system-parameters ess. Press Enter.
The system displays the System Parameters-ESS screen. Page down to page 6.
In the Community field, enter the community assignments for each Port Network.
Assigning a Survivable Core Server to a community associates the Survivable Core Server with the IPSI(s) (IP Interface Server) in the Port Network(s) for that community. The association effects how the Survivable Core Server is prioritized for the IPSI in that community, if the Survivable Core Server is administered with a Local Preferred or Local Only preference.
Note:
For more information on Survivable Core Server, see Avaya Aura®Communication Manager Survivable Options.
