0703 Dpt-Igar

Avaya Solution & Interoperability Test Lab
Configuring Avaya Communication Manager Release 4.0 for

Dial Plan Transparency and Inter-Gateway Alternate
Routing – Issue 1.1
Abstract
These Application Notes illustrate the configuration and operation of the Dial Plan
Transparency (DPT) feature introduced in Avaya Communication Manager Release 4.0. The
sample configuration described in these Application Notes includes an Avaya S8720 Media
Server pair controlling two Avaya G650 Media Gateway cabinets, and an Avaya S8500 Media
Server configured as an Enterprise Survivable Server (ESS). A private IP network is used to
carry traffic between the two cabinets. Each cabinet also has access to the PSTN using ISDN-
PRI trunks. When the S8720 Media Server controls both cabinets and Call Admission Control
thresholds are met, the Inter-Gateway Alternate Routing (IGAR) feature uses the ISDN-PRI
trunks to complete inter-cabinet calls dialed by extension. When the S8720 Media Server
controls one cabinet, and the Enterprise Survivable Server controls the other cabinet, the DPT
feature uses these same ISDN-PRI trunks for inter-cabinet calls dialed by extension. These
Application Notes focus on illustrating the configuration commonalities and operational
differences between the IGAR and DPT features.
JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 41

SPOC 3/15/2007 ©2007 Avaya Inc. All Rights Reserved. DPT-IGAR.doc
1. Introduction and Scope
These Application Notes illustrate the configuration and operation of the Dial Plan Transparency
(DPT) feature introduced in Avaya Communication Manager Release 4.0. IGAR and DPT share
certain configuration parameters, but apply under different circumstances, and have operational
differences. Since both IGAR and DPT are simple to configure, these Application Notes use
detailed status and call trace verifications to reinforce the conditions under which each feature
would apply, and the expected behavior under these conditions.
As illustrated in Figure 1, the sample configuration described in these Application Notes
includes an Avaya S8720 Media Server pair controlling two Avaya G650 Media Gateway
cabinets, and an Avaya S8500 Media Server configured as an Enterprise Survivable Server
(ESS). A private IP network is used to carry traffic between the two cabinets. Each cabinet
also has access to the (simulated) PSTN using ISDN-PRI trunks. When Call Admission Control
thresholds are met, the Inter-Gateway Alternate Routing (IGAR) feature uses the ISDN-PRI
trunks to complete inter-cabinet calls dialed by extension. The DPT feature also uses these same
ISDN-PRI trunks for inter-cabinet calls dialed by extension, when the S8720 Media Server
controls one cabinet, and the Enterprise Survivable Server controls the other cabinet.
Table 1 provides a summary comparison of the IGAR and DPT features.
Characteristic IGAR DPT Section Reference
Primary server
Server control – when One server in control controls some
does the feature of gateways involved gateways, survivable Section 5.1 (IP media)
apply? in the call (e.g., one server controls others Section 5.2 (IGAR)
server controls cabinet (e.g., ESS controls Section 5.3 (DPT)
1 and cabinet 2 in cabinet 1, S8720
Figure 1) controls cabinet 2)
Typically, configured Typically, network
Trigger Call Admission fragmentation causing Section 5.2 (IGAR)
For Control thresholds survivable servers to Section 5.3 (DPT)
Feature between network assume active control
regions of some gateways
Minimum Avaya
Communication 3.0 4.0 N/A
Manager Release
One Listed Directory Yes, LDN shared by Yes, LDN shared by See configuration in
Number (LDN) per IGAR and DPT IGAR and DPT Section 4.4
network region?
IGAR trunk call may Example of IGAR call
Direction be in same direction DPT trunk call always in opposite direction
For or opposite direction in same direction as from end-user call:
Trunk Call as end-user call end-user call Section 5.2.2
Can be limited to Yes, COR/FRL of Yes, default is same

Characteristic IGAR DPT Section Reference
“privileged users”? calling station always as IGAR, but DPT Section 5.2.3 (IGAR)
compared with FRL calls can optionally be Section 5.3.3 (DPT)
on routing pattern allowed even if
COR/FRL restricted
Number of trunks Yes, directly via
used by feature can be configurable No Section 5.2.4 (IGAR)
explicitly limited? maximum
Trunk types that may TDM trunks only, TDM or IP Trunks, Section 5.2.5 (IGAR)
be used by feature IGAR skips IP trunks DPT does not skip IP Section 5.3.5 (DPT)
in route pattern trunks in route pattern
More info is end-end
Call Somewhat faster Somewhat slower signaled for a DPT
Setup than DPT call than IGAR call call, observe times in
Time Sections 5.2, 5.3
All (i.e., includes calls Direct calls (i.e.,
End-user Call Types received as members excludes calls
Eligible to Trigger of a group, bridging, received as member N/A
DPT or IGAR Trunk coverage, forwarding, of a group, bridging,
Call to remote region etc.) coverage, etc.)
New reason code
Call No different than call “SV” alerts user that
Displays whose media path feature transparency N/A
uses IP network may not apply
Internal Section 5.2: (IGAR)
or Internal call: External call: Section 5.3: (DPT)
External call at internal ring external ring Internal vs. external
destination? characteristic, internal characteristic, external can affect other
Example implications coverage criteria coverage criteria features.
Content of ISDN-PRI PSTN-formatted LDN Originating end-user’s Section 5.2: (IGAR)
Calling Party Number of originating region calling party number Section 5.3: (DPT)
Messaging: Calling party The calling party Separate companion
Call Answer extension, same as an number, if any, Application Notes in
Messages will appear internal call whose received for the Reference [3] focus
to be from the… media path uses IP incoming DPT trunk on Messaging
network call Interactions
Path Optimization
(Trunks idled when Yes No Section 5.2.6: (IGAR)
call topology allows) Section 5.3.6 (DPT)
Table 1 – IGAR and DPT Comparison

Figure 1 provides an overview of the network used to verify these Application Notes. Although
this network uses S8720 Media Servers, the approach documented in these Application Notes
could be used with other Avaya Media Servers and Media Gateways. For example, the same
procedures could be followed if the primary call server were an S8500 Media Server.
Avaya S8720 Media Servers

Primary, Cluster ID 1 Avaya S8500 Media Server
ESS, Cluster ID 2
Server 1: 2.2.87.21
Server 2: 2.2.87.22
Active: 2.2.87.23
2.2.185.88
Call Admission Control (CAC)Limits Configured Between
Network Region 1 and Network Region 3
Ethernet Ethernet
IGAR Calls Use PSTN When CAC Limits Met, and IPSI 2.2.185.9
DPT Calls use PSTN when ESS Controls Cabinet 1 C-LAN 2.2.185.2
MEDPRO 2.2.185.4
Avaya 9620
IP Telephones
X52020 and Avaya 4621
P S TN
X52050 IP Telephone
Mapped to X51003
Network ISDN-PRI ISDN-PRI Mapped to
Region 3 Trunk Group 11 Trunk Group 7 Network
Duplicated Region 1
TN2602
MEDPRO(s): Avaya G650
2.2.26.4 (Virtual) Media Gateway
2.2.26.3 (2a07) Cabinet 1
2.2.26.2 (2b07) Network Region 1
IGAR/DPT LDN x51777
IPSI 2.2.85.9 Avaya 4610
PSTN LDN: 732-851-1777
CLAN(s): Avaya 2420 IP Telephone
2.2.85.2, 6210 Analog Digital X51010
Avaya G650
2.2.85.20 Telephone, Telephone Mapped to
Media Gateways
x52001 x51002 Network
Cabinet 2
Region 1
Network Region 3
IGAR/DPT LDN x52111 Network Region 3 Network Region 1
PSTN LDN 732-852-2111
Figure 1: Network Overview

2. Equipment and Software Validated
Table 1 shows the equipment and version information used in the sample configuration. The
DPT and IGAR features are Avaya Communication Manager features that apply to all types of
stations. The station types and versions are not relevant and are therefore omitted. Note that the
Avaya Communication Manager load used was a beta version and not a generally available
software load. Therefore, minor differences in screen content may be observed.
Network Component Version Information

Avaya S8720 Media Server Avaya Communication Manager
4.0 Load 721
Avaya S8500 Media Server (ESS) Avaya Communication Manager
4.0 Load 721
Avaya TN464GP DS1s in G650 HW2 FW17
Avaya TN2312BP IPSIs in G650 Media Gateways HW07 FW 21
Avaya TN799DP C-LANs in G650 Media Gateways HW01 FW012
Avaya TN2602AP MEDPROs in G650 Media HW2 FW 24
Gateways
Table 2 – Equipment Version Information
3. Conventions, Assumptions, and Licensing

In these Application Notes, Avaya Communication Manager administration software screens are
shown with a gray shaded background. These screens are also referred to as “SAT” (System
Access Terminal) screens. In some instances, the information from the original screen has been
edited or annotated for brevity or clarity in presentation. Unless otherwise noted, each screen
capture is preceded by the text that references the screen capture.
Steps that aid in understanding the configuration, but are not central to the scope, are shown with
“display” or “list” commands, to emphasize that the screens should not be interpreted as part of a
procedurally complete configuration flow. The initial configuration of Avaya Communication
Manager to achieve a multiple cabinet system with an ESS is assumed and not illustrated. Only
aspects of the configuration related to IGAR and DPT are illustrated.
Note that the IGAR and DPT features are not separately licensed. Both features use ARS to
route the inter-region trunk call. To verify that the installed license grants permission to use the
features illustrated in these Application Notes, use the command “display system-parameters
customer-options”. Ensure that “ARS” and “ISDN-PRI” are enabled. Although ISDN-PRI
trunks are used in these Application Notes to transport the DPT and IGAR trunk calls over the
simulated PSTN, ISDN trunks are not required in general.

4. Avaya Communication Manager Configuration
This section illustrates the relevant Avaya Communication Manager configuration.
4.1. Enabling DPT and IGAR via System Features

The following screen illustrates a subset of the system-parameters features form applicable to
DPT and IGAR. As shown, the IGAR and DPT features can be enabled or disabled on a system-
wide basis. The ability to disable IGAR or DPT globally allows the configuration for IGAR and
DPT to remain in the system, even though the feature will not be used to complete calls. For
IGAR or DPT to be used for a new call, the corresponding fields in the screen shown below must
be set to “y”.
The “COR to Use for DPT” field can take one of two values. With the default value of
“station”, the Class of Restriction (COR) of the call originator will be used to determine
eligibility for DPT call establishment when the ARS number associated with the DPT call is
routed. The default “station” thus allows the DPT feature to be configured as a “privilege”
available to some system users, but not to others. An example of call behavior when a call is
denied access to use DPT due to an insufficient Facility Restriction Level (FRL) is shown in
Section 5.3.3. The “COR to Use for DPT” can alternatively be set to “unrestricted”. If set to
“unrestricted”, callers whose restriction levels would otherwise block access to the trunks used
for DPT will be allowed access for DPT calls. In contrast, the IGAR feature always considers
the calling party’s restriction level. That is, IGAR restriction behavior always operates in a
manner akin to the DPT configuration of “station”. An example of call behavior when a call is
denied access to use IGAR due to an insufficient Facility Restriction Level (FRL) is shown in
Section 5.2.3.
change system-parameters features Page 5 of 17
FEATURE-RELATED SYSTEM PARAMETERS
SYSTEM PRINTER PARAMETERS

Endpoint: Lines Per Page: 60
SYSTEM-WIDE PARAMETERS
Switch Name:
Emergency Extension Forwarding (min): 10
Enable Inter-Gateway Alternate Routing? y
Enable Dial Plan Transparency in Survivable Mode? y
COR to Use for DPT: station
4.2. Assignment of Cabinets to Network Regions

The following screens illustrate the cabinet configuration. Each cabinet can be assigned to a
network region. Devices connected to the cabinet such as analog telephones, digital telephones,
and ISDN-PRI trunks derive the network region attribute from the cabinet configuration.

The following screen illustrates the configuration for cabinet 1, assigned to network region 1.
display cabinet 1
CABINET
CABINET DESCRIPTION
Cabinet: 1
Cabinet Layout: G650-rack-mount-stack
Cabinet Type: expansion-portnetwork
Location: 1 IP Network Region: 1

Rack: right Room: demo Floor: Building:
CARRIER DESCRIPTION
Carrier Carrier Type Number
E not-used PN 01
D not-used PN 01
C not-used PN 01
B not-used PN 01
A G650-port PN 01
The following screen illustrates the configuration for cabinet 2, assigned to network region 3.
display cabinet 2
CABINET
CABINET DESCRIPTION
Cabinet: 2
Cabinet Layout: G650-rack-mount-stack
Cabinet Type: expansion-portnetwork
Location: 3 IP Network Region: 3

Rack: center Room: demo Floor: Building:
CARRIER DESCRIPTION
Carrier Carrier Type Number
E not-used PN 02
D not-used PN 02
C not-used PN 02
B G650-port PN 02
A G650-port PN 02
4.3. Assignment of IP Endpoints to Network Regions

Whereas TDM devices derive a network region from the cabinet configuration, IP telephones can
be assigned a network region based on an IP address mapping, as illustrated in the example
screen below. The following screen illustrates a subset of the IP network map configuration
used to verify these Application Notes. In the sample configuration, some endpoints are mapped
to network region 1 and some are mapped to network region 3. The bolded row is relevant for
the IP Telephone verification in Section 5.3.7.

change ip-network-map Page 1 of 32
IP ADDRESS MAPPING
Emergency
Subnet Location
From IP Address (To IP Address or Mask) Region VLAN Extension
2 .2 .1 .101 2 .2 .1 .101 1 n
2 .2 .1 .102 2 .2 .1 .102 1 n
2 .2 .1 .103 2 .2 .1 .103 1 n
2 .2 .1 .104 2 .2 .1 .108 1 n
2 .2 .1 .109 2 .2 .1 .109 3 n
2 .2 .1 .110 2 .2 .1 .110 1 n
2 .2 .1 .111 2 .2 .1 .119 1 n
2 .2 .1 .120 2 .2 .1 .121 4 n
2 .2 .1 .200 2 .2 .1 .201 3 n
2 .2 .4 .100 2 .2 .4 .200 3 n
2 .2 .185.200 2 .2 .185.250 1 n
4.4. Network Region Configuration

The following screens illustrate the network region configuration for network region 1.
Although the parameters on Page 1 are not directly associated with the IGAR or DPT features,
Page 1 is illustrated below. The “Location” assigned to a network region can be relevant to
IGAR and DPT in that both IGAR and DPT use ARS for routing, and the location parameter can
be a criteria in ARS call routing. In these Application Notes, the IGAR and DPT calls are routed
using the “all locations” ARS table, but it may be necessary in more complex configurations to
route the IGAR or DPT calls using location-specific ARS tables.
change ip-network-region 1 Page 1 of 19
IP NETWORK REGION
Region: 1
Location: 1 Authoritative Domain:
Name: Home-site
MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes
Codec Set: 1 Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048 IP Audio Hairpinning? y
UDP Port Max: 4029
DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y
Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS
Audio PHB Value: 46 Use Default Server Parameters? y
Video PHB Value: 26
802.1P/Q PARAMETERS
Call Control 802.1p Priority: 6
Audio 802.1p Priority: 6
Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS
H.323 IP ENDPOINTS RSVP Enabled? n
H.323 Link Bounce Recovery? y
Idle Traffic Interval (sec): 20
Keep-Alive Interval (sec): 5
Keep-Alive Count: 5
The following screen illustrates Page 2 for network region 1. The bolded fields are directly
associated with the DPT or IGAR features. Each network region must have a unique Listed
Directory Number (LDN) extension, which is shared by the IGAR and DPT features. With the
configuration shown below, a call can be launched to the full public number 732-851-1777 for
the purposes of IGAR or DPT call establishment. The “Maximum Number of Trunks to Use for
IGAR” explicitly limits the total number of IGAR trunk calls to the specified maximum, but has

no bearing on DPT calls. The “Dial Plan Transparency in Survivable Mode?” field must be set
to “y” to enable DPT for this region.
IP NETWORK REGION
INTER-GATEWAY ALTERNATE ROUTING / DIAL PLAN TRANSPARENCY

Incoming LDN Extension: 51777
Conversion To Full Public Number - Delete: 1 Insert: 732851
Maximum Number of Trunks to Use for IGAR: 2
Dial Plan Transparency in Survivable Mode? y
BACKUP SERVERS IN PRIORITY ORDER H.323 SECURITY PROFILES

1 1 pin-eke
2 2 any-auth
3 3
4 4
5
6 Allow SIP URI Conversion? n
TCP SIGNALING LINK ESTABLISHMENT FOR AVAYA H.323 ENDPOINTS

Near End Establishes TCP Signaling Socket? y
Near End TCP Port Min: 61440
Near End TCP Port Max: 61444
The following screen illustrates the Call Admission Control rules that can trigger IGAR calls. In
the sample configuration, one call will be allowed on the IP network between network region 1
and network region 3 due to the “Total WAN-BW-limits” configuration in the bolded row
below. When one inter-region call is already using the IP network and a new connection is
attempted, the “IGAR” setting of “y” makes the call eligible for completion using the routing
defined for IGAR.
Inter Network Region Connection Management
src dst codec direct Total Video Dyn

rgn rgn set WAN WAN-BW-limits Norm Prio Shr Intervening-regions CAC IGAR
1 1 1
1 2 2 y :NoLimit y n
1 3 1 y 1:Calls 0 0 y y
The following screens illustrate the network region configuration for network region 3.

IP NETWORK REGION
Region: 3
Location: 3 Authoritative Domain:
Name: Cabinet 2
MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes
Codec Set: 1 Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048 IP Audio Hairpinning? y
UDP Port Max: 65535
DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y
Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS
Audio PHB Value: 46 Use Default Server Parameters? y
Video PHB Value: 26
802.1P/Q PARAMETERS
Call Control 802.1p Priority: 6
Audio 802.1p Priority: 6
Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS
H.323 IP ENDPOINTS RSVP Enabled? n
H.323 Link Bounce Recovery? y
Idle Traffic Interval (sec): 20
Keep-Alive Interval (sec): 5
Keep-Alive Count: 5
The following screen illustrates Page 2 for network region 3. With the configuration shown
below, other regions can launch a call to the full public number 732-852-2111 for the purposes
of IGAR or DPT call establishment.
IP NETWORK REGION
INTER-GATEWAY ALTERNATE ROUTING / DIAL PLAN TRANSPARENCY

Incoming LDN Extension: 52111
Conversion To Full Public Number - Delete: 1 Insert: 732852
Maximum Number of Trunks to Use for IGAR: 2
Dial Plan Transparency in Survivable Mode? y
BACKUP SERVERS IN PRIORITY ORDER H.323 SECURITY PROFILES

1 1 pin-eke
2 2 any-auth
3 3
4 4
5
6 Allow SIP URI Conversion? n
TCP SIGNALING LINK ESTABLISHMENT FOR AVAYA H.323 ENDPOINTS

Near End Establishes TCP Signaling Socket? y
Near End TCP Port Min: 61440
Near End TCP Port Max: 61444
The following screen illustrates the Call Admission Control rules that can trigger IGAR calls,
which matches the inter-region configuration previously described for region 1.

Inter Network Region Connection Management
src dst codec direct Total Video Dyn

rgn rgn set WAN WAN-BW-limits Norm Prio Shr Intervening-regions CAC IGAR
3 1 1 y 1:Calls 0 0 y y
3 2
3 3 1
4.5. Media Processor Configuration for Network Regions 1 and 3

In Figure 1, cabinet 1 (NR1) and cabinet 2 (NR3) have IP Media Processors. There is nothing
unique about the media processor configuration owing to IGAR or DPT. The following screen is
presented because the IP addresses will appear in the verification traces shown in Section 5.
Cabinet 1 contains a TN2602 (2.2.185.4) configured for NR 1. Cabinet 2 contains a duplicated
TN2602 pair (active/standby) where the virtual IP address of the pair is 2.2.26.4 as shown below.
list ip-interface medpro

IP INTERFACES
Net
ON Slot Code Sfx IP Address/Mask Gateway Address Rgn VLAN Virtual Address
-- ---- ---- --- ------------------ --------------- --- ---- ---------------
y 01A03 TN2302 2.2.185.3 /24 2.2.185.1 1 n
y 02A03 TN2302 2.2.85.3 /24 2.2.85.1 3 n
y 02A07 TN2602 2.2.26.3 /24 2.2.26.1 3 n 2.2.26.4
y 02B07 TN2602 2.2.26.2 /24 2.2.26.1 3 n 2.2.26.4
y 01A11 TN2602 2.2.185.4 /24 2.2.185.1 1 n
4.6. Codec Set Configuration

The network region configuration allows configuration of a codec set to be used for intra-region
connections, and the option of a different codec set to be used for inter-region connections for
any given network region pair. There is nothing unique about codec set configuration owing to
DPT or IGAR, but the following screen is included because the verification traces shown in
Section 5 will include codec information. Simple G.711MU defaults were retained for the
codec configuration since this is not the focus of these Application Notes.
change ip-codec-set 1 Page 1 of 2

IP Codec Set
Codec Set: 1
Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.711MU n 2 20
2:
3:
4:
5:
6:
7:
Media Encryption
1: none
2:
3:

4.7. Routing IGAR and DPT Calls For Network Regions 1 and 3
The following screen illustrates the ARS analysis on the “full public number” for the LDN
defined on the network region screens. The LDN for region 1, 51777, converts to the full public
number 732-851-1777, and this number will route to route pattern 11. The LDN for region 3,
52111, converts to the full public number 732-852-2111, which will route to route pattern 7.
change ars analysis 732 Page 1 of 2
ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 2
Dialed Total Route Call Node ANI

String Min Max Pattern Type Num Reqd
7328511777 10 10 11 natl n
7328522111 10 10 7 natl n
The following screen illustrates route pattern 7, containing trunk group 7, an ISDN-PRI trunk
group in cabinet 1. In the example screen below, the FRL to access trunk group 7 is set to 0, the
least restrictive setting. Alternatively, to make access to the PSTN trunk for IGAR or DPT a
privileged function, the FRL on the route-pattern can be set to a higher value. Examples are
shown in the verifications in Section 5.2.3 and 5.3.3.
change route-pattern 7 Page 1 of 3
Pattern Number: 7 Pattern Name: IGAR-PN1
SCCAN? n Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 7 0 n user
2: n user
3: n user
4: n user
5: n user
6: n user
BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 M 4 W Request Dgts Format
Subaddress
1: y y y y y n n rest none
The following screen illustrates route pattern 11, containing trunk group 11, an ISDN-PRI trunk
group in cabinet 2.

Pattern Number: 11 Pattern Name: IGAR PN2
Dgts Intw
1: 11 0 n user
2: n user
3: n user
4: n user
5: n user
6: n user
BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 M 4 W Request Dgts Format
Subaddress
4.8. Trunk Groups Used by IGAR and DPT

There is nothing unique about the trunk group configuration owing to the use of the DPT or
IGAR features. The following screens illustrate aspects of ISDN-PRI trunk group 7 used in the
sample configuration. Trunk group 11 is similar, but not illustrated for brevity in presentation.
On Page 1, observe the trunk group is configured as an ISDN-PRI public network trunk group.
display trunk-group 7 Page 1 of 22
TRUNK GROUP
Group Number: 7 Group Type: isdn CDR Reports: y

Group Name: To-Sim-PSTN-PN1 COR: 1 TN: 1 TAC: 107
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
On Page 3, observe that the calling party number is sent to the network.
TRUNK FEATURES
ACA Assignment? n Measured: none Wideband Support? n
Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: n ySend Calling Number:
Used for DCS? n Send EMU Visitor CPN?
n
Suppress # Outpulsing? n Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider
Replace Restricted Numbers? n

Replace Unavailable Numbers? n
Send Connected Number: y
Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number? n

On Page 6, observe that the members of trunk group 7 are located in cabinet 1. The members of
trunk group 11 are located in cabinet 2 (not shown).
TRUNK GROUP
Administered Members (min/max): 1/4
GROUP MEMBER ASSIGNMENTS Total Administered Members: 4
Port Code Sfx Name Night Sig Grp

1: 01A0501 TN464 F 7
2: 01A0502 TN464 F 7
3: 01A0503 TN464 F 7
4: 01A0504 TN464 F 7
4.9. Incoming Number Manipulation for Calls to IGAR/DPT LDN

In the example shown in these Application Notes, an IGAR or DPT call will arrive as a 10-digit
number from the (simulated) PSTN. In general, if the number delivered by the PSTN does not
match the LDN extension assigned to the network region, the incoming call handling treatment
for the inbound trunk group may be used to perform a conversion of the delivered number to the
LDN extension.
The following screen illustrates the incoming call handling for trunk group 7. The full number
received from the PSTN is converted to the LDN extension format.
change inc-call-handling-trmt trunk-group 7 Page 1 of 30
Service/ Called Called Del Insert Per Call Night

Feature Len Number CPN/BN Serv
public-ntwrk 10 7328511777 all 51777
The following screen illustrates the incoming call handling for trunk group 11. Again, the full
number is converted to the LDN extension format.
change inc-call-handling-trmt trunk-group 11 Page 1 of 30
Service/ Called Called Del Insert Per Call Night
Feature Len Number CPN/BN Serv
public-ntwrk 10 7328522111 all 52111
4.10. Calling Party Number Formatting

The following screen illustrates a subset of the public-unknown-numbering form. This form
allows the calling party number to be formatted for outbound calls. For example, with the
configuration below, when a call from an extension 52XXX is routed to ISDN-PRI trunk group 7
or 11, the calling party number will be sent as 732-852-2XXX. For illustration only, more
specific matching numbers are shown for the LDNs assigned to the network regions and for
other specific extensions used in the verification of these Application Notes. The LDN for
network region 1, 51777, maps to the full calling party number 732-851-1777. IGAR calls will
include the calling party number mapped from the LDN extension. In contrast, DPT calls will
include the calling party number mapping applicable to the actual call originator. That is, if
extension 52001 originates a call, and DPT is required to complete the call, the calling party
number will be sent as 732-852-2001.

change public-unknown-numbering 0 Page 1 of 2
NUMBERING - PUBLIC/UNKNOWN FORMAT
Total
Ext Ext Trk CPN CPN
Len Code Grp(s) Prefix Len
5 5 5
5 5 48 732852 10
5 52 7 732852 10
5 52 11 732852 10
5 51002 7 732851 10
5 51002 11 732851 10
5 51010 732851 10
5 51777 732851 10
5 52111 732852 10
4.11. Saving Configuration Changes

The command “save translation all” can be used to save configuration changes to the main call
processing servers as well as any survivable processors, such as the ESS shown in Figure 1.

5. Verification
The illustrated configuration has been verified. The following subsections illustrate the expected
behavior using the configuration presented in these Application Notes. Three main sub-sections
follow. Section 5.1 illustrates aspects of normal operation when there is no IP network
fragmentation, one call processing server is in control of all gateways, and the IP network is used
for the bearer or media portion of the call (i.e., Call Admission Control limits have not yet been
reached). Section 5.2 illustrates the behavior when one server remains in control of all gateways,
but Call Admission Control rules dictate that the call must use Inter-Gateway Alternate Routing
to complete. Section 5.3 illustrates the behavior when cabinet 1 (network region 1) is controlled
by the ESS, while cabinet 2 (network region 3) is controlled by the S8720 Media Server. Phone
calls between network region 1 and network region 3 will use the Dial Plan Transparency feature
to complete.
The screens in this section (preceding Section 5.1) are applicable to both Section 5.1 and 5.2
(i.e., applicable when one server is controlling all gateways and regions). From the following
screen, observe the IPSI in cabinet 1 (port network 1) and the IPSI in cabinet 2 (port network 2)
are in-service and controlled by one Avaya Communication Manager server.
list ipserver-interface
IP SERVER INTERFACE INFORMATION
Port Pri/ Primary/ Primary/ Primary/ State Of
Ntwk Sec Secondary Secondary Secondary Serv Control Health
Num Bd Loc IP Address Host Name DHCP ID State State C P E G
---- ------ --------------- ---------------- --------- ----- ------- -------
1 1A01 2.2.185.9 2.2.185.9 ipsi-A01a IN actv-aa 0.0.0.0
In this case, as shown in the following screen, the server in control is the active S8720 Media
Server (cluster 1), but Section 5.1 and Section 5.2 would also apply if the S8500 ESS (cluster 2)
were controlling all gateways and regions (e.g., in the event the S8720 Media Server pair were
not in service).
status ess port-networks
Cluster ID 1 ESS PORT NETWORK INFORMATION

Port IPSI Pri/ Pri/ Cntl Connected
Com Intf Intf Ntwk Gtway Sec Sec Clus Clus(ter)
PN Num Loc Type Ste Loc Loc State ID IDs
1 1 1A01 IPSI up 1A01 1A01 actv-aa 1 1 2

2 2 2A01 IPSI up 2A01 2A01 actv-aa 1 1 2
The following screen illustrates the registered IP stations and the corresponding network regions.
The registered IP stations screen may appear differently when the system fragments due to IP
network failure. That is, when the system fragments, some telephones may remain under the
control of the main server and others may re-register with a survivable server such as the ESS in
Figure 1.

list registered-ip-stations
REGISTERED IP STATIONS
Station Ext/ Set Product Prod Station Net Gatekeeper TCP

Orig Port Type ID Rel IP Address Rgn IP Address Skt
51003 4621 IP_Phone 2.600 2.2.185.200 1 2.2.185.2 y
51010 4610 IP_Phone 2.300 2.2.1.110 1 2.2.85.20 y
52020 9620# IP_Phone 1.100 2.2.1.109 3 2.2.85.2 y
5.1. IP Network Handling the Inter-Site Bearer Call

The Call Admission Control limits between NR1 and NR3 were set artificially low, allowing one
call only, to facilitate the verification of IGAR. All calls in this section are placed when there are
no calls over the IP network in progress between NR1 and NR3.
5.1.1. Extension 51002 (NR1) Dials Extension 52001 (NR3)

The following trace illustrates a call from extension 51002 to extension 52001. The bolded rows
show the inter-gateway connection (igc) using the IP Media Processors in each region.
list trace station 51002 Page 1

LIST TRACE
time data
15:18:26 tone-receiver 01AXX08 cid 0x217
15:18:26 active station 51002 cid 0x217
15:18:28 dial 52001
15:18:28 ring station 52001 cid 0x217
15:18:28 xoip: fax:Relay modem:off tty:US 2.2.185.4:2660 (igc)
15:18:28 G711MU ss:off ps:20 rn:1/3 2.2.185.4:2660 2.2.26.4:30104
The following screen shows the IP network connectivity information available from the “status
station” command. The call uses one media processing resource in each region to complete.
Observe that the media processor in cabinet 1 (1A1101) is transmitting to the virtual IP
(2.2.26.4) of the duplicated media processor pair in cabinet 2.
status station 51002 Page 3 of 4

SRC PORT TO DEST PORT TALKPATH
src port: 01A0401
01A0401:TX:tdm:a178
01A1101:RX:tdm:a178:TX:2.2.185.4:2660/g711u/20ms
02A0701:RX:2.2.26.4:30104/g711u/20ms:TX:tdm:a134
02A1001:RX:tdm:a134
dst port: 02A1001
The following screen shows a subset of the information available from the “status media
processor” command for the duplicated media processor pair. Observe the use of the virtual IP
address, 2.2.26.4. Although not the focus of these Application Notes, in the sample
configuration, if a failure were introduced, such as removing the IP network connectivity of the
active media processor in the pair, the standby media processor would automatically assume
control of the connection. The call would remain up, with a very brief interruption in the media
path that may or may not be perceptible to the users in the call.

status media-processor board 2a07 Page 1 of 2
MEDIA-PROCESSOR STATUS
Board Loc Code Vintage Serial

02A07 TN2602AP HW02 FW024 05J239703005
Ethernet Enabled? yes Node Name: tn2602-2a07
IP Address/Mask: 2.2.26.3/255.255.255.0
Gateway Address: 2.2.26.1
MAC Address: 00:04:0d:a1:1f:18
Links Alarms Duplication

Peer ETH MPCL MAJ MIN WRN State
up up up 0 0 0 active
DSP Channel Status

DSP 1: in-service/active, 1 calls DSP 3: in-service/idle
DSP 2: in-service/idle DSP 4: in-service/idle
COMMON DUPLICATED VALUES

Standby Refreshed: yes Locked: no
Network Region: 3 Shared Virt-MAC: 02:04:0d:4a:53:c0
Shared IP Address: 2.2.26.4
5.1.2. Extension 52001 (NR3) Dials Extensions 51002 (NR1)

Since the Call Admission Control configuration allows only one call, the call illustrated in
Section 5.1.1 was disconnected before the call in this section was placed. The following trace
illustrates a call from extension 52001 to extension 51002. The bolded rows show the inter-
gateway connection (igc) using the IP Media Processors in each region. This trace is very
similar to the trace shown in Section 5.1.1. The reader may observe a slight difference in that IP
station 51003 (IP address 2.2.1.110) has a bridged appearance for the called station 51002. In
this case, the call was answered at 51002.

LIST TRACE
time data

15:27:19 dial 51002
15:27:19 G711MU ss:off ps:20 rn:3/1 2.2.26.4:30224 2.2.185.4:2728
15:27:19 G711MU ss:off ps:20 rn:1/1 2.2.1.110:38878 2.2.185.4:2732
15:27:19 xoip: fax:Relay modem:off tty:US 2.2.185.4:2732 uid:0x8ca0

The following screen shows the IP network connectivity information available from the “status
station” command, which is very similar to the status and commentary in Section 5.1.1.

src port: 02A1001
02A1001:TX:tdm:a103
02A0701:RX:tdm:a103:TX:2.2.26.4:30224/g711u/20ms
01A1101:RX:2.2.185.4:2728/g711u/20ms:TX:tdm:a141
01A0401:RX:tdm:a141
dst port: 01A0401
5.2. Inter-Gateway Alternate Routing Used for Inter-Site Calls

The following subsections show screens illustrating IGAR. That is, for the call traces in the
subsections that follow, the Call Admission Control (CAC) thresholds that trigger IGAR have
already been met by prior calls, so that the new illustrated calls must use IGAR to complete. In
the illustrated configuration, the CAC threshold was set to 1 call for simplicity. The following
screen illustrates an example status of the inter-region connectivity for network region 1 at the
time the calls in this section are placed.
status ip-network-region 1
Inter Network Region Bandwidth Status

Number of # Times
Src Dst Conn Conn BW-limit BW-Used(Kbits) Connections BW-Limit IGAR
Rgn Rgn Type Stat Tx Rx Tx Rx Hit Today Now/Today
1 2 direct pass NoLimit 0 0 0 0 0 0/ 0

Video: NoLimit 0 0 0 0 0
Priority: NoLimit 0 0 0 0 0
1 3 direct pass 1 Calls 83 83 1 1 203 0/ 11
Video: 0 Calls 0 0 0 0 0
Priority: 0 Calls 0 0 0 0 0

show that the CAC limits have been met, and that an IGAR call is launched out trunk group 7
using the configured ARS routing. The call ultimately arrives to network region 3 from trunk
group 11.

LIST TRACE
time data
13:40:52 dial 52001
13:40:52 denial event 2330: No BW, prowler <--> prowl D1=0x1003c00 D2=0x195
13:40:52 IGAR starting call app A station 52001 cid 0x195
13:40:52 dial 7328522111 route:ARS
13:40:52 term trunk-group 7 cid 0x196
13:40:52 dial 7328522111 route:ARS
13:40:52 route-pattern 7 preference 1 cid 0x196
13:40:52 seize trunk-group 7 member 4 cid 0x196
13:40:52 Calling Number & Name 7328511777 NO-CPName
13:40:52 Proceed trunk-group 7 member 4 cid 0x196
13:40:52 Alert trunk-group 7 member 4 cid 0x196
13:40:52 active trunk-group 7 member 4 cid 0x196
13:40:53 IGAR active call app A trunks 7/4 & 11/4 cids 0x196 & 0x197
The following screen illustrates the outbound trunk trace for a similar (new) call from extension
51002 to extension 52001. The bolded rows show that the call is routed to the full number (732-
852-2111) for the LDN defined for IP network region 3. Observe that the calling party number
sent is the full number (732-851-1777) for the LDN defined for IP network region 1 (i.e., not the
calling party number associated with the actual call originator, extension 51002, as would be the
case for a DPT call).
list trace tac 107 Page 1

LIST TRACE
time data
13:51:56 dial 7328522111 route:ARS
13:51:56 term trunk-group 7 cid 0x19d
13:51:56 dial 7328522111 route:ARS
13:51:56 route-pattern 7 preference 1 cid 0x19d
13:51:56 seize trunk-group 7 member 2 cid 0x19d
13:51:56 Proceed trunk-group 7 member 2 cid 0x19d
13:51:56 tone-receiver 01AXX05 cid 0x19d
13:51:56 Alert trunk-group 7 member 2 cid 0x19d
13:51:56 active trunk-group 7 member 2 cid 0x19d
13:51:57 IGAR active call app A trunks 7/2 & 11/2 cids 0x19d & 0x19e

The following screen illustrates an inbound trunk trace for a similar (new) call from extension
51002 to extension 52001. The bolded rows show that the call comes in on trunk group 11 with
the calling party number of the region 1 LDN. The call is routed to extension 52111, the LDN
for region 3, and the IGAR associations are completed.

LIST TRACE
time data
13:52:51 Calling party trunk-group 11 member 3 cid 0x1a1
13:52:51 active trunk-group 11 member 3 cid 0x1a1
13:52:51 dial 52111
13:52:51 ring cid 0x1a1
13:52:51 active cid 0x1a1
13:52:51 tone-receiver 02B0107 cid 0x1a1
13:52:52 IGAR active call app A trunks 7/3 & 11/3 cids 0x1a0 & 0x1a1
The following “status station” screen illustrates connection configuration for an IGAR call.
Observe the use of the IGAR trunk in each cabinet.

src port: 01A0401
01A0401:TX:tdm:a250
01A0504:RX:tdm:a250 TX:IGAR-Trunk
02A0504:RX:IGAR-Trunk TX:tdm:a221
02A1001:RX:tdm:a221
dst port: 02A1001
The following “status trunk” screen illustrates example status for an IGAR call. Observe the
“IGAR Connection?” field is set to “y” for this trunk member.
status trunk 7/4

TRUNK STATUS
Trunk Group/Member: 0007/004 Service State: in-service/active

Port: 01A0504 Maintenance Busy? no
Signaling Group ID: 7 CA-TSC state: not allowed
IGAR Connection? yes
Connected Ports:

The following screen illustrates an example status of the inter-region connectivity for network
region 1 with an IGAR call currently active. Observe “IGAR Now” shows one IGAR call active.
Number of # Times


show that the CAC limits have been met, and that an IGAR call is launched out trunk group 7
using the configured ARS routing. Observe that the direction for the IGAR call (out trunk group
7) is the same as the direction of the IGAR call illustrated in the previous section, when
extension 51002 called 52001. That is, in the trace below, the IGAR call was in the “opposite”
direction of the end-user call, as can be the case for IGAR in general. In contrast, a DPT call is
always in the same direction as the end-user call. The call ultimately arrives to network region 3
from trunk group 11. Other differences in this trace compared to the trace for the call from
51002 to 52001 illustrated in the previous section are due to the fact that there is a bridged
appearance for called extension 51002 on extension 51003.

LIST TRACE
time data
13:47:10 tone-receiver 02B0106 cid 0x199
13:47:12 dial 51002
13:47:12 denial event 2330: No BW, prowler <--> prowl D1=0x1e00 D2=0x199
13:47:12 IGAR starting call app A station 51002 cid 0x199
13:47:12 IGAR starting call app F station 51003 cid 0x199
13:47:12 G711MU ss:off ps:20 rn:1/1 2.2.1.110:38878 2.2.185.3:2128
13:47:12 dial 7328522111 route:ARS
13:47:12 term trunk-group 7 cid 0x19a
13:47:12 dial 7328522111 route:ARS
13:47:12 route-pattern 7 preference 1 cid 0x19a
13:47:12 seize trunk-group 7 member 1 cid 0x19a
13:47:12 Proceed trunk-group 7 member 1 cid 0x19a
13:47:12 tone-receiver 01AXX04 cid 0x19a
13:47:12 Alert trunk-group 7 member 1 cid 0x19a
13:47:12 active trunk-group 7 member 1 cid 0x19a
13:47:13 IGAR active call app A trunks 7/1 & 11/1 cids 0x19a & 0x19b
13:47:13 IGAR active call app F trunks 7/1 & 11/1 cids 0x19a & 0x19b
The other status screens presented in the prior subsection would be similar for a call in this
direction, so they are omitted for brevity in presentation.

5.2.3. Restricting Access to IGAR via COR / FRL
In some instances, the use of PSTN trunks for “internal” calls to other extensions may be
considered a privilege. For example, a manager may be assigned a Class of Restriction (COR)
that has a high Facility Restriction Level (FRL) that grants the manager access to system
capabilities that other users may not be entitled to access. In the sample configuration, station
51002 was temporarily assigned a COR whose associated FRL is set below 7 for the illustration
in this section. The route pattern used by IGAR was then temporarily configured to require an
FRL of 7 to allow calls to proceed using the PSTN trunks. If 51002 calls 52001, the call will be
unable to complete to 52001 using IGAR, although other call treatments may apply. For
example, if 52001 is assigned a coverage path, the call can proceed to coverage. Other more
privileged users (whose COR has an FRL of 7) that dial the same number will be granted the
permission to overflow to the PSTN trunks as illustrated in the prior IGAR subsections.
The following (abbreviated) screen illustrates how a COR is assigned to a user. Here, station
51002 is assigned COR 2.
change station 51002 Page 1 of 5

STATION
Extension: 51002 Lock Messages? n BCC: 0
Type: 2420 Security Code: 1234 TN: 1
Port: 01A0401 Coverage Path 1: 1 COR: 2
Name: John Dewey Coverage Path 2: COS: 1
The following (abbreviated) screen illustrates COR 2. COR 2 has been assigned an FRL of 6,
which will be below the FRL assigned to trunks in the routing pattern used by IGAR.
change cor 2 Page 1 of 22

CLASS OF RESTRICTION
COR Number: 2
COR Description: Lower FRL
FRL: 6 APLT? y
Can Be Service Observed? n Calling Party Restriction: none
Can Be A Service Observer? n Called Party Restriction: none
Time of Day Chart: 1 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: none Facility Access Trunk Test? n
Restricted Call List? n Can Change Coverage? n
The following (abbreviated) screen illustrates the use of the highest FRL (7) in a routing pattern
associated with IGAR.

Dgts Intw
1: 7 7 n user
The following screen illustrates a trace for a call from station 51002 to 52001 with the
restrictions introduced in this section in place. For this particular call, extension 52001 had a

coverage path whose first point in coverage was station 51010 (same network region as the
caller). Extension 51010 rings and can answer this call. If the coverage point had been in the
same network region as the called party, then the call would not be able to alert the coverage
path, since the coverage attempt would similarly be denied access to the IGAR trunk due to the
FRL restriction.

LIST TRACE
time data
14:32:32 tone-receiver 01AXX01 cid 0x1b0

14:32:32 active station 51002 cid 0x1b0
14:32:34 dial 52001
/* Do not misinterpret the line immediately below. Station 52001 does not ring */
14:32:34 ring station 52001 cid 0x1b0
14:32:34 denial event 2330: No BW, prowler <--> prowl D1=0x1003c00 D2=0x1b0
14:32:34 IGAR starting call app A station 52001 cid 0x1b0
14:32:34 denial event 1343: Need higher FRL to route D1=0x14803d D2=0x1b1
14:32:34 dial 7328522111 route:ARS
14:32:34 route-pattern 7 preference 0 cid 0x1b1
14:32:34 term cid 0x1b1
14:32:34 station 51002 cid 0x1b1
14:32:34 station 51002 cid 0x1b1
14:32:48 station 51002 cid 0x1b1
14:32:48 station 51002 cid 0x1b1
5.2.4. Restricting Access to IGAR via Number of Trunks Used

The number of trunks used by IGAR can be restricted by the network region configuration. This
section illustrates a new call attempt that would otherwise use IGAR, if not for the configured
maximum number of trunks to use for IGAR.
The following screen illustrates the status of the interconnectivity to network region 1 at the time
the calls in this section are attempted. In particular, observe that the IP network is at the
configured CAC maximum of 1 call, and the number of IGAR calls is currently 2, the configured
maximum for IGAR trunk usage on the network region form.
Number of # Times

The following screen illustrates the status of trunk group 7, used by IGAR. The two IGAR calls
are active, but there are also in-service/idle trunks available to handle other types of calls. The
IGAR maximum trunk parameter will prevent an IGAR call from utilizing one of the available
trunks, presumably for the purpose of preserving available trunks for external callers.

status trunk 7
TRUNK GROUP STATUS
Member Port Service State Mtce Connected Ports
Busy
0007/001 01A0501 in-service/idle no
0007/003 01A0503 in-service/active no
0007/004 01A0504 in-service/active no
The following trace illustrates a call from station 51002 (NR1) to station 52020 (NR3) under
these conditions. For illustration, station 52020 was assigned a coverage path whose first and
only point in coverage was another station in its own network region (i.e., same region as called
party). As a result, the coverage call attempt is similarly denied by both CAC limits and the
IGAR maximum trunk limit. In this simple example, the caller would hear busy tone.
This trace illustrates that call coverage calls, like other types of call redirection, are eligible to
use IGAR. Recall that with DPT, the direct call to the “principal” (extension 52020) would be
eligible for DPT, but any subsequent redirections of the call would not attempt an inter-region
DPT call to complete. With DPT, redirections within the same system fragment as the caller can
occur, but redirections to other network regions controlled by other servers would not be
attempted.

LIST TRACE
time data
14:21:07 tone-receiver 01AXX01 cid 0x1ac
14:21:07 active station 51002 cid 0x1ac
14:21:10 dial 52020
14:21:10 redirect station 52020 cid 0x1ac
14:21:10 denial event 2330: No BW, prowler <--> prowl D1=0x7f00000e D2=0x1ac
14:21:10 denial event 2355: IGAR trunk limit exceeded D1=0x3 D2=0x2
14:21:14 coverage-path 52 point 1 cid 0x1ac
14:21:14 denial event 2330: No BW, prowler <--> prowl D1=0x7f000005 D2=0x1ac
14:21:14 denial event 2355: IGAR trunk limit exceeded D1=0x3 D2=0x2
14:21:16 idle station 51002 cid 0x1ac
5.2.5. IGAR Skips IP Trunks

The purpose of this section is to illustrate that IGAR will skip IP trunk groups, if present, in a
routing pattern. (In contrast, IP trunks are not skipped by DPT). The following (abbreviated)
screen shows a temporary change made to route pattern 7. Trunk group 87, an H.323 IP trunk
group, was added as the first choice in the route pattern.

Dgts Intw
1: 87 0 n user
2: 7 0 n user

The following status shows that trunk 87 is an in-service/idle IP Trunk (note the logical port IDs
indicative of an IP trunk, such as the bolded trunk member with Port T00025).
status trunk 87
TRUNK GROUP STATUS
Busy
0087/001 T00025 in-service/idle no
The next screen shows a trace for a call from extension 51002 to 52001 using IGAR, with the
above change to the route pattern in place. Observe from the trace that the routing for the IGAR
call silently skips trunk group 87, the first preference. The IGAR call completes over the second
preference, trunk group 7. The call proceeds in the same manner as the call previously illustrated
in Section 5.2.1.

LIST TRACE
time data
14:35:59 active station 51002 cid 0x1b6
14:36:01 dial 52001
14:36:01 ring station 52001 cid 0x1b6
14:36:01 denial event 2330: No BW, prowler <--> prowl D1=0x1003c00 D2=0x1b6
14:36:01 IGAR starting call app A station 52001 cid 0x1b6
14:36:01 dial 7328522111 route:ARS
14:36:01 term trunk-group 7 cid 0x1b7
14:36:01 dial 7328522111 route:ARS
14:36:01 route-pattern 7 preference 2 cid 0x1b7
14:36:01 seize trunk-group 7 member 2 cid 0x1b7
14:36:01 Proceed trunk-group 7 member 2 cid 0x1b7
5.2.6. IGAR Optimizes Paths

The purpose of this section is to illustrate that IGAR can release the IGAR PSTN trunk
connection, if the trunk connection is no longer required for the new topology of a call. For
example, if extension 51002 calls extension 52001, and a redirection feature such as call
coverage or call forwarding redirects the call to extension 51003, the IGAR trunk can be
released, since the calling and redirected-to parties are in the same network region. The single
server in control of the call has all the information required to make the determination that the
IGAR PSTN trunk call is no longer required.
The following screen shows a trace for a call from station 51002 to 52001. Station 52001 does
not answer, and the call follows the coverage path for 52001. The first point in coverage, 51003,
answers the call. Observe from the trace that after the coverage no-answer period expires, the
call is directed to 51003, and the trunk call is idled.

LIST TRACE
time data
10:26:10 tone-receiver 01AXX06 cid 0x26c
10:26:10 active station 51002 cid 0x26c
10:26:11 dial 52001
10:26:11 ring station 52001 cid 0x26c
10:26:11 denial event 2330: No BW, prowler <--> prowl D1=0x1003c00 D2=0x26c
10:26:11 IGAR starting call app A station 52001 cid 0x26c
10:26:11 dial 7328522111 route:ARS
10:26:11 term trunk-group 7 cid 0x26d
10:26:11 dial 7328522111 route:ARS
10:26:11 route-pattern 7 preference 1 cid 0x26d
10:26:11 seize trunk-group 7 member 3 cid 0x26d
10:26:11 Proceed trunk-group 7 member 3 cid 0x26d
10:26:11 tone-receiver 01AXX02 cid 0x26d
10:26:11 Alert trunk-group 7 member 3 cid 0x26d
10:26:11 active trunk-group 7 member 3 cid 0x26d
10:26:12 IGAR active call app A trunks 7/3 & 11/3 cids 0x26d & 0x26e
10:26:25 idle cid 0x26d
10:26:32 active station 51003 cid 0x26c
The following screen shows the status of trunk group 7 while station 51002 is conversing with
answering station 51003 on the call placed above. Observe that all trunks are idle. In this case,
51002 and the covered-to answering telephone 51003 are in the same network region.
status trunk 7
TRUNK GROUP STATUS

Busy

The following trace illustrates a call from 51002 to 52001 at a time when call-forwarding on no-
answer is active to destination 51003. Observe that the IGAR trunk call is established. Later,
when the call is not answered, the call forwards to extension 51003, in the same network region
as the caller, 51002. Again, the IGAR trunk is idled since it is no longer required. The final
connection is an intra-region 1 connection from 51002 to 51003.

LIST TRACE
time data
10:43:50 active station 51002 cid 0x27a
10:43:52 dial 52001
10:43:52 ring station 52001 cid 0x27a
10:43:52 denial event 2330: No BW, prowler <--> prowl D1=0x1003c00 D2=0x27a
10:43:52 IGAR starting call app A station 52001 cid 0x27a
10:43:52 dial 7328522111 route:ARS
10:43:52 term trunk-group 7 cid 0x27b
10:43:52 dial 7328522111 route:ARS
10:43:52 route-pattern 7 preference 1 cid 0x27b
10:43:52 seize trunk-group 7 member 2 cid 0x27b
10:43:52 Proceed trunk-group 7 member 2 cid 0x27b
10:43:52 tone-receiver 01AXX03 cid 0x27b
10:43:52 Alert trunk-group 7 member 2 cid 0x27b
10:43:52 active trunk-group 7 member 2 cid 0x27b
10:43:52 IGAR active call app A trunks 7/2 & 11/2 cids 0x27b & 0x27c
10:44:02 call-forwarding 51003
10:44:02 idle cid 0x27b
10:44:02 G711MU ss:off ps:20 rn:1/1 2.2.1.110:3204 2.2.185.4:2756

As another example that will be contrasted with DPT in Section 5.3, the following screens
illustrate an IGAR call from station 52001 to station 51002. The call is answered by extension
51002. Extension 51002 then initiates a transfer to extension 52050 (NR3), with this leg of the
call also being an IGAR call. When extension 52050 answers, extension 51002 completes the
transfer. Note that trunk-trunk transfer need not be permitted to complete this transfer.

LIST TRACE
time data
11:36:48 Calling party station 52001 cid 0x28b
11:36:48 Calling Number & Name 52001 John Analog
11:36:48 dial 51002
11:36:48 ring station 51002 cid 0x28b
11:36:48 denial event 2330: No BW, prowler <--> prowl D1=0x1e00 D2=0x28b
11:36:48 G711MU ss:off ps:20 rn:1/1 2.2.1.103:3198 2.2.185.4:2080
11:36:48 dial 7328522111 route:ARS
11:36:48 term trunk-group 7 cid 0x28c
11:36:48 dial 7328522111 route:ARS
11:36:48 route-pattern 7 preference 1 cid 0x28c
11:36:48 seize trunk-group 7 member 3 cid 0x28c
11:36:48 Proceed trunk-group 7 member 3 cid 0x28c
11:36:48 tone-receiver 01AXX06 cid 0x28c
11:36:48 Alert trunk-group 7 member 3 cid 0x28c
11:36:48 active trunk-group 7 member 3 cid 0x28c
11:36:49 IGAR active call app A trunks 7/3 & 11/3 cids 0x28c & 0x28d
11:36:49 IGAR active call app F trunks 7/3 & 11/3 cids 0x28c & 0x28d
11:36:51 active station 51002 cid 0x28b
11:36:59 conf/tran hold station 51002 cid 0x28b
11:36:59 active station 51002 cid 0x28e
11:37:05 dial 52050
11:37:05 ring station 52050 cid 0x28e
11:37:05 denial event 2330: No BW, prowler <--> prowl D1=0x7f000005 D2=0x28e
11:37:05 IGAR starting call app B station 52050 cid 0x28e
11:37:05 dial 7328522111 route:ARS
11:37:05 term trunk-group 7 cid 0x28f
11:37:05 dial 7328522111 route:ARS
11:37:05 route-pattern 7 preference 1 cid 0x28f
11:37:05 seize trunk-group 7 member 4 cid 0x28f
11:37:05 Proceed trunk-group 7 member 4 cid 0x28f
11:37:05 tone-receiver 01AXX07 cid 0x28f
11:37:05 Alert trunk-group 7 member 4 cid 0x28f
11:37:05 active trunk-group 7 member 4 cid 0x28f
11:37:06 IGAR active call app B trunks 7/4 & 11/4 cids 0x28f & 0x290
/* On transfer completion, the trunk connection is idled */
11:37:15 transfer station 51002 cid 0x28e
11:37:15 idle cid 0x28f
5.3. Dial Plan Transparency Used for Inter-Site Calls

The following subsections show detailed screens illustrating the use of DPT to complete calls.
For DPT to be relevant, the system must fragment so that one set of devices are controlled by
one server, and another set of devices are controlled by another. For the calls illustrated in this
section, the system is fragmented such that the ESS controls cabinet 1, and the S8720 Media
Server primary call server continues to control cabinet 2.

The following screen shows the output of “list ipserver-interface” from the active S8720 Media
Server. Observe that the IPSI in 1A01 is out of service as seen by the S8720 Media Server, and
the IPSI in 2A01 remains in-service.
---- ------ --------------- ---------------- --------- ----- ------- -------
1 1A01 2.2.185.9 2.2.185.9 ipsi-A01a OUT active 0.1.1.0
The following screen shows the output of “list ipserver-interface” from the S8500 Media Server
ESS. Observe that the IPSI in 2A01 is out of service as seen by the ESS, but the IPSI in 1A01 is
in-service. That is, the ESS has assumed control of cabinet 1. For example, this could occur if
the IPSI in 1A01 lost IP network connectivity to the S8720 Media Servers, but maintained IP
network connectivity to the ESS.
---- ------ --------------- ---------------- --------- ----- ------- -------
2 2A01 2.2.85.9 2.2.85.9 ipsi-A02a OUT active 0.1.1.0
5.3.1. Extension 51002 (NR1, ESS) Dials Extension 52001 (NR3, Main)
The following trace illustrates a call from extension 51002 to extension 52001. Extension 51002
is controlled by the ESS, and extension 52001 is controlled by the S8720 Media Server. Since
one server controls one user, and another server controls the other user, screens from the two
disparate servers are illustrated below.
The following trace is from the S8500 ESS controlling the originating station, 51002. The first
bolded row shows the DPT feature starting. The call then follows the routing defined to reach
network region 3. Observe that for DPT, the DPT trunk call must be in the same direction as the
end-user call, since the server originating the DPT call does not control the terminating gateway.
Observe also that the calling party number in the outgoing ISDN-PRI SETUP message for the
DPT trunk call represents the actual end-user originating the call, whereas the calling party
number for the corresponding IGAR call would contain the full number mapping of the LDN of
the originating region (for comparison, observe traces in Section 5.2). Although not discernible
from the trace, for a DPT call, the display includes the characters “SV”. For example, station
51002 displays “John Analog SV”, where John Analog is the name translated for station 52001.

LIST TRACE
time data
16:31:10 dial 52001
16:31:10 term station 52001 cid 0x8
16:31:10 DPT starting to NR 3 station 52001 cid 0x8
16:31:10 dial 7328522111 route:ARS
16:31:10 dial 7328522111 route:ARS
The following trace is from the S8720 main server controlling the called station, 52001. The
trace illustrates the incoming DPT trunk call to the LDN extension for network region 3,
followed by the ultimate termination of the call to the called station, extension 52001.

LIST TRACE
time data
16:06:54 Calling party trunk-group 11 member 3 cid 0x22a
16:06:54 active trunk-group 11 member 3 cid 0x22a
16:06:54 dial 52111
16:06:54 ring cid 0x22a
16:06:54 active cid 0x22a
The following screen showing trunk status is taken from the ESS, which shows the trunk
connection to the originating port.
status trunk 7/3 Page 1 of 2

TRUNK STATUS
Trunk Group/Member: 0007/003 Service State: in-service/active

Port: 01A0503 Maintenance Busy? no
Signaling Group ID: 7 CA-TSC state: not allowed
IGAR Connection? No
Connected Ports: 01A0401
5.3.2. Extension 52001 (NR3, Main) Dials Extension 51002 (NR1, ESS)
The following trace illustrates a call from extension 52001 to extension 51002, under the same
conditions illustrated in Section 5.3.1. Since one server controls one user, and another server
controls the other user, screens from the two disparate servers are illustrated below. Station
51002 will ring with the ring characteristic defined for an external trunk call (e.g., by default, a
double ring). In contrast, an IGAR call would ring with the ring characteristic for an internal

station-station call (e.g., as a single ring). Note also that call coverage for a DPT call to a
coverage point on the same server as the called party would follow the path defined for
“external” calls (since it is considered an incoming trunk call), whereas call coverage for an
IGAR call will follow “internal” paths.
The following trace is from the S8720 Media Server controlling the originating station, 52001.
The first bolded row shows the DPT feature starting. The call then follows the routing defined to
reach network region 1. Observe that for DPT, the DPT trunk call must be in the same direction
as the end-user call, since the server originating the DPT call does not control the terminating
gateway. Observe also that the calling party number in the outgoing ISDN-PRI SETUP message
for the DPT trunk call represents the actual end-user originating the call, whereas the calling
party number for the corresponding IGAR call would contain the full number mapping of the
LDN of the originating region (for comparison, observe traces in Section 5.2).

LIST TRACE
time data
16:11:56 dial 51002
16:11:56 term station 51002 cid 0x22b
16:11:56 DPT starting to NR 1 station 51002 cid 0x22b
16:11:56 dial 7328511777 route:ARS
16:11:56 dial 7328511777 route:ARS
16:11:56 tone-receiver 02B0107 cid 0x22b
The following trace is from the ESS controlling the called station, 51002. The trace illustrates
the incoming DPT trunk call to the LDN extension for network region 1, followed by the
ultimate termination of the call to the called station, extension 51002. This trace is similar to the
one in the preceding section, except that station 51003 has a bridged appearance for station
51002. Since this bridged appearance is within the same “fragment” (i.e., does not require DPT
to alert the bridged appearance), the bridged appearance does alert. Note that a DPT call can
take longer than an IGAR call to establish. This can be observed via the time stamps in the trace,
where it may take 2-3 seconds from the time the incoming DPT trunk call is answered, and the
time that the actual called station is alerted. More in-band information is exchanged over the
trunk for a DPT call compared to an IGAR call, and the incremental delay is due to this
additional end-end signaling.

LIST TRACE
time data
16:42:58 Calling party trunk-group 7 member 4 cid 0xb
16:42:58 active trunk-group 7 member 4 cid 0xb
16:42:58 dial 51777
16:42:58 ring cid 0xb
16:42:58 active cid 0xb
16:42:58 tone-receiver 01AXX01 cid 0xb
16:43:00 ring station 51002 cid 0xb
16:43:00 G711MU ss:off ps:20 rn:1/1 2.2.1.110:3204 2.2.185.4:2160
16:43:02 active station 51002 cid 0xb
5.3.3. Configuration Options for Restricting or Not Restricting DPT Calls

Section 4.1 describes how to restrict IGAR and DPT calls, and Section 5.2.3 illustrates a call
trace using FRL restrictions to restrict an IGAR call. This section illustrates the behavior of FRL
restriction for a DPT call. This section also illustrates the option of making DPT calls
“unrestricted”, thereby allowing dialing transparency for extension-dialed calls, even when the
originator would normally be restricted from accessing the trunk used for the DPT call.
The following trace shows a DPT call attempt that is denied due to FRL restrictions. The
configuration of the COR for user 51002, and the FRL assigned on the route pattern are identical
to the configuration previously shown in Section 5.2.3. Whereas the call illustrated for IGAR in
Section 5.2.3 goes to coverage, the similar DPT call illustrated below is denied with intercept
tone. Unlike IGAR, the behavior of a DPT call is akin to any other ARS routed call. As another
example, if all trunks in the DPT route pattern were in use (i.e., no trunks available), then the
caller would hear reorder tone.

LIST TRACE
time data
09:31:50 dial 52001
09:31:50 term station 52001 cid 0x1a
09:31:50 DPT starting to NR 3 station 52001 cid 0x1a
09:31:50 denial event 1343: Need higher FRL to route D1=0x8c9d D2=0x1a
09:31:50 dial 7328522111 route:ARS
09:31:50 route-pattern 7 preference 0 cid 0x1a
09:31:50 denial station 51002 cid 0x1a
With station 51002 still having a COR whose FRL is 6, and an FRL of 7 still required on the
route pattern, make the change illustrated in the following screen.
change system-parameters features Page 5 of 17

FEATURE-RELATED SYSTEM PARAMETERS
SYSTEM-WIDE PARAMETERS
Switch Name:
Emergency Extension Forwarding (min): 10
Enable Inter-Gateway Alternate Routing? y
Enable Dial Plan Transparency in Survivable Mode? y
COR to Use for DPT: unrestricted

Make a call from 51002 to 52001, and observe that the call routes successfully using DPT. A
station that would normally be restricted from accessing a route pattern preference with a higher
FRL than the FRL assigned to the station’s COR is permitted to complete a DPT call using this
same routing preference, as long as the “COR to Use for DPT” field is set to “unrestricted.”

LIST TRACE
time data
09:41:04 dial 52001
09:41:04 term station 52001 cid 0x1b
09:41:04 DPT starting to NR 3 station 52001 cid 0x1b
09:41:04 dial 7328522111 route:ARS
09:41:04 dial 7328522111 route:ARS
5.3.4. Restricting Number of Trunks Used by DPT Calls

In Section 5.2.4, the configurable maximum for IGAR trunks was configured to 2. Once two
IGAR calls were in progress, a third would not route using the trunk. Note that this maximum
does not apply to DPT calls, as illustrated in this section. The following screen, taken from the
ESS, illustrates that two calls are up. These calls are both DPT trunk calls.
status trunk 7
TRUNK GROUP STATUS
Busy
0007/001 01A0501 in-service/active no S00011

Under these conditions, if a call is attempted from 51002 to 52001, it will succeed as a DPT call,
as shown in the following trace. The trace has been abridged since it is no different than other
DPT calls presented in these Application Notes.

LIST TRACE
time data
13:56:40 tone-receiver 01AXX01 cid 0xb
13:56:40 active station 51002 cid 0xb
13:56:42 dial 52001
13:56:42 term station 52001 cid 0xb
13:56:42 DPT starting to NR 3 station 52001 cid 0xb
13:56:42 dial 7328522111 route:ARS
13:56:42 term trunk-group 7 cid 0xb
13:56:42 dial 7328522111 route:ARS
13:56:42 route-pattern 7 preference 1 cid 0xb
13:56:42 seize trunk-group 7 member 3 cid 0xb
The following screen illustrates the status of the trunk after the call, showing 3 trunks in use, all
of which are carrying DPT calls.
status trunk 7
TRUNK GROUP STATUS

Busy

0007/003 01A0503 in-service/active no 01A0401
5.3.5. DPT Calls Allowed to Use IP Trunks

In Section 5.2.5, the routing was temporarily changed such that route pattern 7 had in-service,
idle H.323 IP trunk group 87 as the first preference. The trace in Section 5.2.5 shows that IGAR
silently skips IP trunks configured in a route pattern. In contrast, the following trace is included
only to show that DPT will not skip IP trunks in a route pattern. The following trace shows the
beginning of a trace for a DPT call from 51002 to 52001. Observe that the DPT call is routed to
the IP Trunk.

LIST TRACE
time data
14:04:22 dial 52001
14:04:22 dial 7328522111 route:ARS
14:04:22 dial 7328522111 route:ARS
14:04:22 Calling Number & Name 51002 John Dewey
…………………………………

5.3.6. DPT and Path Optimization
With IGAR, one server is in control of all ports in the call. Topology changes to the call are
apparent to the server, and the server can decide to release the IGAR trunk call if the trunk is no
longer required. See Section 5.2.6 for examples. In contrast, with DPT, one server is in control
of one set of ports, and another server is control of another set of ports that are part of the same
logical call. When topology changes occur, DPT may not optimize paths.
For example, consider a call similar to the last call type in Section 5.2.6. The following screen
illustrates a trace of a DPT call from station 52001 to station 51002. The call is answered by
extension 51002. Extension 51002 then initiates a transfer to extension 52050 (NR3), with this
leg of the call also being a DPT call. When extension 52050 answers, extension 51002
completes the transfer. Note that trunk-trunk transfer must be permitted for this transfer to
complete as shown.
List trace station 51002 Page 1

LIST TRACE
time data
/* Call arrives as a DPT call from NR 3 as previously illustrated */
11:38:52 Calling party trunk-group 7 member 2 cid 0x33
11:38:57 conf/tran hold station 51002 cid 0x33
11:38:59 dial 52050
/* The transferred call is also a DPT call back to a user in NR 3 */
11:38:59 dial 7328522111 route:ARS
11:38:59 dial 7328522111 route:ARS
/* Transfer second button push, transfer completed, DPT trunks are not released */
11:39:07 transfer station 51002 cid 0x34
The following screen shows the trunk status for such a call. Note that two trunks remain in use,
one for the incoming DPT call, and one for the outgoing DPT call.
status trunk 7
TRUNK GROUP STATUS
Busy

5.3.7. Timing Considerations with DPT
A DPT call will only be attempted by the instance of Avaya Communication Manager serving
the call originator if the called party is considered to be out-of-service. Although not exhaustive,
the following two sub-sections illustrate timing considerations affecting DPT behavior.
5.3.7.1 H.323 IP Telephone Timing Considerations with DPT

When an H.323 IP Telephone is registered, and connectivity to that IP Telephone is lost, the IP
Telephone is not immediately transitioned to an out-of-service state, enabling more seamless
recovery from transient network outages. The period of time before a registered IP Telephone is
considered “not registered” is impacted by the configurable parameter shown in bold in the
following screen.
change system-parameters ip-options Page 1 of 2

IP-OPTIONS SYSTEM PARAMETERS
IP MEDIA PACKET PERFORMANCE THRESHOLDS

Roundtrip Propagation Delay (ms) High: 800 Low: 400
Packet Loss (%) High: 40 Low: 15
Ping Test Interval (sec): 20
Number of Pings Per Measurement Interval: 10
RTCP MONITOR SERVER

Default Server IP Address: 1 .1 .1 .18
Default Server Port: 5005
Default RTCP Report Period(secs): 5
AUTOMATIC TRACE ROUTE ON

Link Failure? y
H.248 MEDIA GATEWAY H.323 IP ENDPOINT

Link Loss Delay Timer (min): 5 Link Loss Delay Timer (min): 5
Primary Search Time (sec): 75
Periodic Registration Timer (min): 20
When calls are placed to an IP Telephone that has previously registered, but is currently not
reachable due to a network outage, the DPT feature will not be invoked for such calls until the
timers associated with H.323 IP endpoint recovery have expired for the called telephone. An
example is provided below to reinforce the behavior.
In Figure 1, assume that the network is healthy, and extension 51003 is registered to the primary
S8720 Media Servers. The following abridged screen illustrates this starting state, highlighting
extension 51003 only.

51003 4621 IP_Phone 2.600 2.2.185.200 1 2.2.185.2 y
Now assume that a network outage is introduced at 12:00 that isolates the 2.2.185.0/24 subnet
from the rest of the network. The following screen illustrates the registration status after the

failure is introduced, but prior to the expiration of the associated timers (e.g., at 12:03). Observe
that extension 51003 still appears in the list of registered IP stations, but observe that the TCP
socket field is “n”.

51003 4621 IP_Phone 2.600 2.2.185.200 1 2.2.185.2 n
The following screen illustrates the status of the station at this time. Observe that the service
state of the telephone is in-service.

GENERAL STATUS
Administered Type: 4621 Service State: in-service/on-hook
Connected Type: N/A TCP Signal Status: on-demand
Extension: 51003
Port: S00000 Parameter Download: complete
Call Parked? no SAC Activated? no
Ring Cut Off Act? no
Active Coverage Option: 1
EC500 Status: disabled Off-PBX Service State: N/A

Message Waiting:
Connected Ports:
If a call is attempted from a phone in network region 3 to station 51003 while it is considered to
be in-service (i.e., before the link loss delay timer has expired), a DPT call will not be invoked.
More generally, under these conditions, a caller may hear ringback, but the called telephone will
not ring, and the call will attempt to follow coverage for the called party.
Once the H.323 recovery timers fully expire (e.g., must be after 12:05 in this example), station
51003 will no longer appear in the list of registered stations, and the status of the station will
transition to out-of-service. At this point, calls made to station 51003 from phones in network
region 3 will be eligible for DPT and will complete as shown previously.
Depending on the nature of the outage and the configurable timer values, it may be possible that
an IP station such as 51003 has registered with a survivable server such as an Enterprise
Survivable Server or Local Survivable Processor. For example, in the sample network, assume
the Link Loss Delay Timer applicable to H.323 telephones was configured for 10 minutes, and
the IPSI no-service timer associated with ESS recovery was set to 3 minutes. If the same
network outage were introduced at 12:00, the primary S8720 Media Server would not consider
extension 51003 out-of-service until at least 12:10. By that time, the IPSI in cabinet 1 would be
under the control of the S8500 ESS, and IP Telephone 51003 would have re-registered with a C-
LAN in cabinet 1. After extension 51003 is registered with the ESS, if extension 51003 calls a
phone such as extension 52001 in region 3, the call will complete using DPT, since the ESS
controlling extension 51003 considers the telephones in region 3 to be out-of-service. In other
words, this example presents a condition where 51003 can successfully ring 52001 using DPT,

while extension 52001 can not ring 51003, since the originating server processing the call does
not yet consider the called station to be out-of-service.
5.3.7.2 DPT Timing Considerations for IPSI-Connected Port Networks

When connectivity to an IPSI is lost, the telephones connected to the cabinet housing the IPSI
are not immediately transitioned to an out-of-service state, enabling more seamless recovery
from transient network outages. Continuing with the example presented in the previous section,
assume a network outage is introduced at 12:00 that isolates the 2.2.185.0/24 subnet from the rest
of the network. The primary S8720 Media Servers quickly detect the IPSI in cabinet 1 is
unreachable and begin recovery procedures. Telephones in cabinet 1 are considered to be in the
in-service state for approximately one minute. After introducing the failure, and prior to one
minute’s elapsed time, a call from a phone in network region 3 to digital station 51002 will not
attempt to use DPT to complete, since the called station 51002 is considered to be in-service.
Once the stations in an IPSI connected port network are marked out-of-service, calls to those
stations can attempt to complete using DPT. However, these DPT calls may not be successful
until the unreachable IPSI has re-registered with a reachable ESS. That is, a trunk group must
be in-service to receive the incoming DPT calls arriving from other network regions. Until the
IPSI has failed over to an ESS, the trunk group handling the incoming DPT calls will be out-of-
service, and therefore DPT call attempts from other network regions will fail to complete. In the
example, if a call is made from station 52001 to station 51002 more than 1 minute after the
network failure is introduced, but before the IPSI in cabinet 1 has registered with the ESS and
brought trunk group 7 in-service, the DPT call will fail. The caller may hear reorder tone or a
network announcement.

6. Conclusion
As illustrated in these Application Notes, users can have “dialing transparency” allowing calls to
be dialed by extension, whether the call is carried over the IP network, completed using Inter-
Gateway Alternate Routing due to Call Admission Control limits, or completed with the Dial
Plan Transparency feature introduced in Avaya Communication Manager Release 4.
7. References
The following references are among the Application Notes available at http://www.avaya.com.
The documents listed below are related, in the sense that they provide alternate means to achieve
dialing transparency before Avaya Communication Manager Release 4.
Reference [1] was written based on Avaya Communication Manager 3.0.1 load 346, which
allowed dialing transparency from a branch controlled by a Local Survivable Processor to users
at the main site, using the “coverage remote” enhancements that enable access to messaging
from the survivable branch office.
[1] “Configuring Avaya Communication Manager for Voice Mail Service and Dialing
Transparency for Sites Using Avaya Media Gateways with Local Survivable Processors, Issue
1.0”
Reference [2] was written based on Avaya Communication Manager 3.1, which allowed dialing
transparency from a site controlled by an Enterprise Survivable Server to users at the main site,
using the “coverage remote” enhancements that enable access to messaging from the ESS site.
[2] “Configuring Avaya Communication Manager for Voice Mail Service and Dialing
Transparency for Sites Using an Enterprise Survivable Server, Issue 1.0”
Reference [3] (to be written) uses the DPT feature in Avaya Communication Manager Release
4.0 together with the “coverage remote” enhancements used in References [1] and [2]. The
Application Notes in Reference [3] focus on the messaging interactions with DPT, and are a
companion to the configuration described herein.
[3] “Configuring Avaya Communication Manager Release 4.0 for Dialing Transparency and
Voice Mail Service for Sites with Survivable Processors, Issue 1.0”

©2007 Avaya Inc. All Rights Reserved.
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™
are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the
property of their respective owners. The information provided in these Application Notes is
subject to change without notice. The configurations, technical data, and recommendations
provided in these Application Notes are believed to be accurate and dependable, but are
presented without express or implied warranty. Users are responsible for their application of any
products specified in these Application Notes.
Please e-mail any questions or comments pertaining to these Application Notes along with the
full title name and filename, located in the lower right corner, directly to the Avaya Solution &
Interoperability Test Lab at interoplabnotes@list.avaya.com


0703 Dpt-Igar

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

0703 Dpt-Igar

Caricato da

Copyright:

Formati disponibili

Avaya Solution & Interoperability Test Lab

Configuring Avaya Communication Manager Release 4.0 for

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 41

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 2 of 41

Table 1 – IGAR and DPT Comparison

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 3 of 41

Avaya S8720 Media Servers

Figure 1: Network Overview

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 4 of 41

Network Component Version Information

Table 2 – Equipment Version Information

3. Conventions, Assumptions, and Licensing

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 41

4.1. Enabling DPT and IGAR via System Features

SYSTEM PRINTER PARAMETERS

4.2. Assignment of Cabinets to Network Regions

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 6 of 41

Location: 1 IP Network Region: 1

Location: 3 IP Network Region: 3

4.3. Assignment of IP Endpoints to Network Regions

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 41

4.4. Network Region Configuration

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 8 of 41

INTER-GATEWAY ALTERNATE ROUTING / DIAL PLAN TRANSPARENCY

BACKUP SERVERS IN PRIORITY ORDER H.323 SECURITY PROFILES

TCP SIGNALING LINK ESTABLISHMENT FOR AVAYA H.323 ENDPOINTS

Inter Network Region Connection Management

src dst codec direct Total Video Dyn

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 41

INTER-GATEWAY ALTERNATE ROUTING / DIAL PLAN TRANSPARENCY

BACKUP SERVERS IN PRIORITY ORDER H.323 SECURITY PROFILES

TCP SIGNALING LINK ESTABLISHMENT FOR AVAYA H.323 ENDPOINTS

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 10 of 41

src dst codec direct Total Video Dyn

4.5. Media Processor Configuration for Network Regions 1 and 3

list ip-interface medpro

4.6. Codec Set Configuration

change ip-codec-set 1 Page 1 of 2

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 41

Dialed Total Route Call Node ANI

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 41

4.8. Trunk Groups Used by IGAR and DPT

Group Number: 7 Group Type: isdn CDR Reports: y

Replace Restricted Numbers? n

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 41

Port Code Sfx Name Night Sig Grp

4.9. Incoming Number Manipulation for Calls to IGAR/DPT LDN

Service/ Called Called Del Insert Per Call Night

4.10. Calling Party Number Formatting

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 41

4.11. Saving Configuration Changes

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 15 of 41

2 2A01 2.2.85.9 2.2.85.9 ipsi-A02a IN actv-aa 0.0.0.0

status ess port-networks

Cluster ID 1 ESS PORT NETWORK INFORMATION

1 1 1A01 IPSI up 1A01 1A01 actv-aa 1 1 2

JRR; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 41

Station Ext/ Set Product Prod Station Net Gatekeeper TCP

5.1. IP Network Handling the Inter-Site Bearer Call

5.1.1. Extension 51002 (NR1) Dials Extension 52001 (NR3)

list trace station 51002 Page 1

status station 51002 Page 3 of 4