Avaya Solution & Interoperability Test Lab

Configuring PRI trunk between Avaya Aura

Communication Manager 5.2.1 and Avaya IP Office 6.0
Issue 1.0
Abstract
These Application Notes present a sample configuration for a network that uses a PRI trunk
between Avaya Aura Communication Manager 5.2.1 and Avaya IP Office.
For the sample configuration, Avaya IP Office runs on IP Office server 500 and Avaya Aura
Communication Manager runs on Avaya G650 Media Gateway and Avaya S8730 servers.
Testing was conducted via the Avaya Solution and Interoperability Test Lab.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

1 of 24
CM_IPO_PRI

1. Introduction
These Application Notes present a sample configuration for a network that uses a PRI trunk to
connect Avaya IP Office to Avaya Aura Communication Manager to simulate PSTN calls. All
calls between Avaya IP Office and Avaya Aura Communication Manager are carried over the
PRI trunk.
Avaya Aura Communication Manager supports routing calls to Avaya IP Office based on the
dialed number, ARS (Automatic Route Selection), dial pattern for the branch, and the extension
number. Avaya Aura Communication Manager 5.2.1 runs on an Avaya S8730 Server with
Avaya G650 Media Gateway. The results in these Application Notes should be applicable to
other Avaya servers and media gateways that support Avaya Aura Communication Manager
5.2.1.
For the sample configuration, Avaya IP Office runs on the 500 platform and is administered by
Avaya IP Office Manager.
As shown in Figure 1, Avaya 96xx IP Telephones (H.323) are supported by Communication
Manager. Avaya 56XX, 1608, 4621(H.323), 96XX IP Telephones (H.323 & SIP) and 24xx
Digital Telephones are used as Avaya IP Office endpoints.
Figure 1 depicts Avaya Aura Communication Manager directly connected to Avaya IP Office
using PRI over a DSI trunk to simulate outside calls from PSTN reaching stations on Avaya IP
Office.

Figure 1: Sample Configuration

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

2 of 24
CM_IPO_PRI

2. Equipment and Software Validated

The following equipment and software were used for the sample configuration provided:
Product / Hardware Platform
Avaya Aura TM Communication Manager
Avaya G650 Media Gateway
Avaya S8730 server
Avaya IP Office Server
Avaya 9640 IP Telephone (SIP)

Version
Release 5.2.1 version R015x.02.1.016.4

Avaya 1608 IP Telephone (H.323)

Firmware Version: 1.200

Avaya 4621 IP Telephone (H.323)

Avaya 5621 IP Telephone (H.323)

Firmware Version: 2.200

Firmware Version: 2.300

Avaya 2420 Digital Telephone

Firmware Version:R6.00

Release 6.0
Firmware Version:2.6.2.1

3. Configure Avaya IP Office

This section provides the procedures for configuring Avaya IP Office. The procedures include
The following areas:
Verify IP Office license
Obtain LAN IP address
Administer Codec Preference
Administer PRI trunk
Administer Short Code
Configure Incoming Call Route

From a PC running the Avaya IP Office Manager application, select Start > Programs > IP
Office > Manager to launch the Manager application. Select the proper IP Office system, and
login with the appropriate credentials. The Avaya IP Office Manager screen is displayed.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

3 of 24
CM_IPO_PRI

3.1. Verify IP Office License

From the configuration tree in the left pane, select License > IP500 Universal PRI (Additional
Channels) to display the IP500 Universal PRI (Additional Channels) screen in the right pane.
Verify that the License Status is Valid as shown below.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

4 of 24
CM_IPO_PRI

3.2. Obtain LAN IP Address

From the configuration tree in the left pane, select System to display the IPO500 screen in the
Right pane. Select the LAN2 tab, followed by the LAN Settings sub-tab in the right pane. Make

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

5 of 24
CM_IPO_PRI

3.3. Administer Codec Preference

From the configuration tree in the left pane, select System to display the IPO500 screen in the
right pane. Select the Telephony tab.
Configure Automatic Codec Preference to G.711 ULAW 64K. Click OK.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

6 of 24
CM_IPO_PRI

3.4. Administer PRI Trunk

Insert IPO 500 TRNK PRI Universal card in IPO control unit. From the configuration tree in the
left pane, right-click on Line and select PRI 24(Universal) to add a new PRI Trunk.
From PRI 24 Line tab, select Line SubType as PRI, select Switch type as 5ESS to simulate
calls from PSTN. Uncheck CRC checking field. Select option Always from drop-down menu
for Add Not end-to-end ISDN Information Element field.
Retain default values for all other fields.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

7 of 24
CM_IPO_PRI

From Channels tab, keep Line Appearance Id field blank. Select In Service option for
Admin field. Click OK.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

8 of 24
CM_IPO_PRI

3.5. Administer Short Code

From the configuration tree in the left pane, right-click on Short Code, and select New. Enter
the dialing string that will be used to call the users on Communication Manager in the Code
field. Select Dial from the drop-down menu for Feature and enter the phone number appended
with @<ip address> in the Telephone Number. Select PRI trunk administered in Section 3.4 in
the Line Group Id field.
Shown below is the short code which was added for the sample configuration.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

9 of 24
CM_IPO_PRI

3.6. Configure Incoming Call Route

From the configuration tree in the left pane, right-click on Incoming Call Route, and select
New. Under the Standard tab, enter the PRI trunk administered in Section 3.4 in the Line
Group Id.

Under the Destination tab, enter . as the Default Value. This will enable all incoming calls to
be routed to any extension.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

10 of 24
CM_IPO_PRI

3.7. Configure SIP User Names

From the configuration tree in the left pane, right-click on User and select SIP tab. Modify the
SIP Name to be the same as the users extension number. The other fields can be left as default.
Repeat this configuration step for all users.

3.8. Save Configuration

Select File > Save Configuration to save and send the configuration to the IP Office server.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

11 of 24
CM_IPO_PRI

4. Configure Avaya Aura Communication Manager

This section covers the administrative steps to route calls between Communication Manager and
Avaya IP Office via the PRI trunk. A PRI trunk is a physical trunk between G650 & Avaya IP
Office. All configurations in this section are administered using the System Access Terminal
(SAT). These Application Notes assumed that the basic configuration has already been
administered.
This section describes configuring Communication Manager in the following areas.
Configure system parameters to enable ISDN-PRI.
Administer DS1 interface
Configure IP Node Names
Configure PRI Signaling group and Trunk group
Configure Route Pattern
Configure Public Numbering
Administer ARS Analysis

4.1. Configure system parameter customer options to enable ISDNPRI.

Use the change system-parameters customer options command to enable ISDN-PRI trunk.
On Page 4, select y for ISDN-PRI option. Submit the changes.
This change can be done only with init login. At customers environment, license file needs to be
added to enable this option. Contact an authorized Avaya sales representative to make the
appropriate changes.
change system-parameters customer-options
OPTIONAL FEATURES
Emergency Access to Attendant?
Enable 'dadmin' Login?
Enhanced Conferencing?
Enhanced EC500?
Enterprise Survivable Server?
Enterprise Wide Licensing?
ESS Administration?
Extended Cvg/Fwd Admin?
External Device Alarm Admin?
Five Port Networks Max Per MCC?
Flexible Billing?
Forced Entry of Account Codes?
Global Call Classification?
Hospitality (Basic)?
Hospitality (G3V3 Enhancements)?
IP Trunks?

y
y
n
n
n
n
n
n
n
n
n
n
n
y
n
y

Page

4 of

10

IP Stations? y
ISDN Feature Plus?
ISDN/SIP Network Call Redirection?
ISDN-BRI Trunks?
ISDN-PRI?
Local Survivable Processor?
Malicious Call Trace?
Media Encryption Over IP?
Mode Code for Centralized Voice Mail?

n
n
n
y
n
n
y
n

Multifrequency Signaling?
Multimedia Call Handling (Basic)?
Multimedia Call Handling (Enhanced)?
Multimedia IP SIP Trunking?

y
n
n
n

IP Attendant Consoles? n
(NOTE: You must logoff & login to effect the permission changes.)
AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

12 of 24
CM_IPO_PRI

4.2. Administer DS1 interface

Connect a cable from DS1 interface of G650 Media Gateway to Avaya IP Office PRI module.
Add the DS1 interface using following command add ds1 01a12 where 01a12 is slot number.
Enter any name such as To-IPO. Enter isdn-pri for Signaling Mode field and network
for Interface field.
Retain the default values for the remaining fields and submit these changes.
add ds1 01a12

Page

1 of

DS1 CIRCUIT PACK

Location:
Bit Rate:
Line Compensation:
Signaling Mode:
Connect:
TN-C7 Long Timers?
Interworking Message:
Interface Companding:
Idle Code:

01A12
Name:
1.544
Line Coding:
1
Framing Mode:
isdn-pri
pbx
Interface:
n
Country Protocol:
PROGress
Protocol Version:
mulaw
CRC?
11111111
DCP/Analog Bearer Capability:

TO-IPO
b8zs
esf
network
1
a
n
3.1kHz

T303 Timer(sec): 4

Slip Detection? n

AD; Reviewed:
SPOC 09/15/2010

Near-end CSU Type: other

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

13 of 24
CM_IPO_PRI

4.3. Configure IP Node Names

Use the change node-names ip command to add entry for the C-LAN that will be used for
connectivity to Avaya IP Office. The actual node names and IP addresses may vary.
Submit these changes.
change node-names ip

Page

1 of

IP NODE NAMES
Name
ASMA
CC-SM6.0
CLAN_1a12
Clan_1a04
G700-1
Gateway001
IPO
Medpro_1a05
default
procr

IP Address
10.0.0.247
10.0.1.187
10.0.2.128
10.0.0.234
12.0.0.4
10.0.0.1
10.0.2.222
10.0.0.235
0.0.0.0
0.0.0.0

( 10 of 10
administered node-names were displayed )
Use 'list node-names' command to see all the administered node-names
Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

14 of 24
CM_IPO_PRI

4.4. Configure PRI Signaling Group and Trunk Group

4.4.1. PRI Signaling Group
In the test configuration, trunk group 32 and signaling group 32 were used to reach Avaya
IP Office. Use the add signaling-group n command, where n is an available signaling group
number.
Enter the following values for the specified fields, and retain default values for all remaining
fields. Submit these changes.
Group Type: isdn-pri
Primary D-Channel:Location 01A1224 from Section 4.2
Trunk Group for Channel Selection:Trunk group Id
add signaling-group 32

Page

1 of

SIGNALING GROUP
Group Number: 32

Group Type: isdn-pri

Associated Signaling? y
Primary D-Channel: 01A1224

Max number of NCA TSC: 0

Max number of CA TSC: 0
Trunk Group for NCA TSC:

Trunk Group for Channel Selection: 32

TSC Supplementary Service Protocol: a

4.4.2. PRI Trunk Group

Use the add trunk-group n command, where n is an available trunk group number. Enter the
following values for the specified fields, and retain the default values for the remaining fields.
Group Type: isdn-pri
Group Name: Any group name such as Trk<->IPO
TAC:An available Trunk Access Code
Service Type: Tie
add trunk-group 32

Page

1 of

21

TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:

32
Trk <->IPO
two-way
n
0
tie

Group Type: isdn

COR: 1
Outgoing Display? y
Busy Threshold: 255

CDR Reports: y
TN: 1
TAC: #032
Carrier Medium: PRI/BRI
Night Service:

Auth Code? n
Far End Test Line No:

TestCall ITC: rest

TestCall BCC: 4

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

15 of 24
CM_IPO_PRI

On Page 5, enter port number 1A01201where 1A012 is board location assigned in Section
4.2 & numbers 01-23 are channels.
add trunk-group 32

GROUP MEMBER ASSIGNMENTS

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:

Port
01A1201
01A1202
01A1203
01A1204
01A1205
01A1206
01A1207
01A1208
01A1209
01A1210
01A1211
01A1212
01A1213
01A1214
01A1215

Code Sfx Name

TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C

add trunk-group 32

GROUP MEMBER ASSIGNMENTS

16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:

Port
01A1216
01A1217
01A1218
01A1219
01A1220
01A1221
01A1222
01A1223

AD; Reviewed:
SPOC 09/15/2010

Code Sfx Name

TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C
TN2464 C

Page
5 of 21
TRUNK GROUP
Administered Members (min/max):
1/23
Total Administered Members: 23
Night

Sig Grp
32
32
32
32
32
32
32
32
32
32
32
32
32
32
32

Page
6 of 21
TRUNK GROUP
Administered Members (min/max):
1/23
Total Administered Members: 23
Night

Sig Grp
32
32
32
32
32
32
32
32

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

16 of 24
CM_IPO_PRI

4.5. Configure Route Pattern

Configure a route pattern to correspond to the newly added PRI trunk group. Use the change
route-pattern n command, where n is an available route pattern.
Enter the following values for the specified fields, and retain the default values for the remaining
fields. Submit these changes.
Pattern Name: A descriptive name.
Grp No: The trunk group number from Section 4.4.2.
FRL: Enter a level that allows access to this trunk, with 0 being least restrictive.
No. Del Dgts: Enter 3. For the sample configuration, the user dials 233-5xxx,
However 233 will be deleted and only 5xxx will be sent to Avaya IP Office via the PRI
trunk.

change route-pattern 7
Pattern Number: 7
Grp FRL NPA Pfx Hop Toll No.
No
Mrk Lmt List Del
Dgts
1: 32
0
3
2:
3:
4:
5:
6
BCC VALUE TSC CA-TSC
0 1 2 M 4 W
Request
1:
2:
3:
4:
5:
6:

y
y
y
y
y
y

y
y
y
y
y
y

y
y
y
y
y
y

y
y
y
y
y
y

y
y
y
y
y
y

AD; Reviewed:
SPOC 09/15/2010

n
n
n
n
n
n

n
n
n
n
n
n

Pattern Name: TO IPO

Secure SIP? n
Inserted
Digits

Page

1 of

DCS/ IXC
QSIG
Intw
n
user
n
user
n
user
n
user
n
user
n
user

ITC BCIE Service/Feature PARM No. Numbering LAR

Dgts Format
Subaddress
rest
none
rest
none
rest
none
rest
none
rest
none
rest
none

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

17 of 24
CM_IPO_PRI

4.6. Configure Public Numbering

Use the change public-unknown-numbering 2 command, to define the calling party number
to be sent to Avaya IP Office. Add an entry for the trunk group defined in Section 4.4.2 to reach
Avaya IP Office endpoints. In the sample configuration, all calls originating from endpoints
connected to Communication Manager dial 233-5xxx or 233-4xxxwhere 5xxx& 4xxx is
the 4-digit extension on Avaya IP Office. The call will be routed over the PRI trunk defined in
Section 4.4.2. Submit these changes.
change public-unknown-numbering 2
Page
1 of
2
NUMBERING - PUBLIC/UNKNOWN FORMAT
Total
Ext Ext
Trk
CPN
CPN
Len Code
Grp(s)
Prefix
Len
Total Administered: 3
4 6
31
4
Maximum Entries: 9999
7 223
33
223
7
7 233
32
233
7

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

18 of 24
CM_IPO_PRI

4.7. Administer ARS Analysis

This section provides sample Alternate Route Selection (ARS) used for routing calls with
Dialed digits 9-233-5xxx or 9-233-4xxx to Avaya IP Office. Note that other methods of routing
may be used.Use change ars analysis 233 command and add an entry to specify how to route
the calls to Avaya IP Office endpoints. Enter the following values for the specified fields, and
retain the default values for the remaining fields. Submit these changes.
Dialed String: Dialed prefix digits to match on, in this case 233.
Total Min: Minimum number of digits.
Total Max: Maximum number of digits.
Route Pattern: The route pattern number from Section 4.5.
Call Type: locl

change ars analysis 233

Page
ARS DIGIT ANALYSIS TABLE
Location: all

Dialed
String

Total
Min Max
7
7
7
7
8
8
8
8
9
9
7
7
3
3
7
7
7
7
7
7
3
3
7
7
7
7
3
3
7
7

233
3
3333
3334
3335
4
411
5
555
6
611
7
8
811
9

Route
Pattern
7
2
11
11
11
2
deny
2
deny
2
1
2
2
1
2

Call
Type
locl
hnpa
locl
locl
locl
hnpa
svcl
hnpa
hnpa
hnpa
svcl
hnpa
hnpa
svcl
hnpa

Node
Num

1 of

Percent Full:

2
1

ANI
Reqd
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n

4.8. Save Translations

Configuration of Communication Manager is complete. Use the save translation command to
save these changes.

5. Verification Steps
This section provides the tests that can be performed on Avaya IP Office and Communication
Manager to verify proper configuration of these systems.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

19 of 24
CM_IPO_PRI

5.1. Verify Avaya Aura Communication Manager

Use the Communication Manager SAT interface to verify the status of the PRI trunk group.
Use the status trunk n command, where n is the trunk group number administered in Section
4.4.2. Verify that all trunks are in the in-service/idle state as shown below.
status trunk 32

Page

TRUNK GROUP STATUS

Member

Port

Service State

Mtce Connected Ports

Busy

0032/001
0032/002
0032/003
0032/004
0032/005
0032/006
0032/007
0032/008
0032/009
0032/010
0032/011
0032/012
0032/013
0032/014

01A1201
01A1202
01A1203
01A1204
01A1205
01A1206
01A1207
01A1208
01A1209
01A1210
01A1211
01A1212
01A1213
01A1214

in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle

no
no
no
no
no
no
no
no
no
no
no
no
no
no

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

20 of 24
CM_IPO_PRI

Verify the status of the PRI signaling group by using the status signaling-group n command,
where n is the signaling group number administered in Section 4.4.1. Verify the signaling group
is in-service as indicated in the Group State field shown below.
status signaling-group 32
STATUS SIGNALING GROUP
Group ID:
Group Type:
Signaling Type:
Group State:

32
isdn-pri
facility associated signaling
in-service

Active NCA-TSC Count: 0

Active CA-TSC Count: 0

Primary D-Channel

Port: 01A1224

Level 3 State: in-service

Secondary D-Channel

Port:

Level 3 State: no-link

Make a call between Avaya 9600 Series IP Telephone and Avaya IP Office IP Telephone.
Verify the status of connected PRI trunks by using the status trunk x/y, where x is the number
of the PRI trunk Group from Section 4.4.2 to reach Avaya IP Office, and y is the member
Number of a connected trunk. On Page 1 verify that the Service State is in-service/active
and Connect Ports :< port number>.
status trunk 32/1

Page

1 of

TRUNK STATUS
Trunk Group/Member: 0032/001
Port: 01A1201
Signaling Group ID: 32
IGAR Connection? no

Service State: in-service/active

Maintenance Busy? no
CA-TSC state: not allowed

Connected Ports: S01582

On Page 2 verify the status of the talk path for the call.
status trunk 32/1

Page

2 of

SRC PORT TO DEST PORT TALKPATH

src port: 01A1201
01A1201:TX:tdm:a99
01A0502:RX:tdm:a99:TX:10.0.0.235:2420/g711u/20ms
S01582:RX:10.255.255.210:2050/g711u/20ms

dst port: S01582

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

21 of 24
CM_IPO_PRI

5.2. Verify Avaya IP Office

IP Office can be debugged with the System Status Application. Log into the IP Office Manager
PC and select Start > Programs > IP Office > System Status to launch the application.
Log into the application using the appropriate credentials.
Make a call from station on Communication Manager to Avaya IP Office endpoint.
In the left panel, double-click on the Trunks entry and select PRI trunk created in Section 3.4.
Press the Trace All button. The messages on the line are displayed.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

22 of 24
CM_IPO_PRI

5.3. Verification Scenarios

Verification scenarios for the configuration described in these Application Notes included the
following:
Place a call from an extension on the Avaya IP Office to an extension on Communication
Manager. Answer the call and verify talkpath.
Repeat previous case in the opposite direction.
Verify that calls can be transferred from an extension on Avaya IP Office to an extension
on Communication Manager.
Verify that calls can be conferenced between extensions on Communication Manager to
an extension on Avaya IP Office.
Verify that extensions on Avaya IP Office can conference in extensions on
Communication Manager.
Verify that calls can be transferred from extensions on Communication Manager to an
extension on Avaya IP Office.
Proper display of the calling and called party name and number information was verified for all
calls.

6. Conclusions
These Application Notes describe how to configure a sample configuration for a network that
uses a PRI trunk between Avaya Aura Communication Manager 5.2.1 and Avaya IP Office to
simulate calls from PSTN. Interoperability testing included verification of successful calls
among several types of endpoints with various features including hold unhold, conference, Callforward, Do-Not-Disturb etc.

7. Additional References
This section references the product documentation relevant to these Application Notes.
Communication Manager:
[1] Administering Avaya Aura Communication Manager, Doc ID 03-300509, May 2009,
available at http://support.avaya.com.
IP Office:
[2] Avaya IP Office Manager, Doc ID 15-601011, available at http://support.avaya.com.

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

23 of 24
CM_IPO_PRI

2010 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

AD; Reviewed:
SPOC 09/15/2010

Solution & Interoperability Test Lab Application Notes

2010 Avaya Inc. All Rights Reserved.

24 of 24
CM_IPO_PRI