Acme QE

Avaya Solution & Interoperability Test Lab
Application Notes for Configuring an Acme Packet Net-Net

Session Director to Support Avaya one-X Quick Edition SIP
Services - Issue 1.0
Abstract
These Application Notes provide steps to configure an Acme Packet Net-Net Session Director
(SD) to support SIP telephony services involving an Avaya one-X Quick Edition system, an
Avaya SIP Enablement Services (SES) server, and Avaya Communication Manager. In the
reference configuration, Avaya one-X Quick Edition endpoints are located at a branch site
while the Avaya SES server and Avaya Communication Manager are located at a main site.
The public Internet is used for connectivity between the sites and, consistent with a model for
a small branch, Network Address and Port Translation (NAPT) is used at the Avaya one-X
Quick Edition site. Avaya one-X Quick Edition endpoints register to the Avaya SES server
via the SD. The SD is used generally as a Session Border Controller and more specifically to
enable NAPT traversal of SIP sessions.
MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 76

SPOC 4/19/2007 2007 Avaya Inc. All Rights Reserved. acmeQE.doc
1. Introduction
The Avaya one-X Quick Edition system supports interoperability with other telephony solutions
via the Session Initiation Protocol (SIP). Opportunities to leverage this include tying Avaya one-
X Quick Edition branches to a main corporate location and tying QE branches together via
hosted telephony solutions. For example, remote Avaya one-X Quick Edition endpoints may
register with an Avaya SIP Enablement Services (SES) Server located at a main corporate
location. This in turn can enable calling to/from Avaya Communication Manager stations. Such
configurations may make use of the public Internet as opposed to VPN connections for transport
of SIP communications. When the public Internet is used, Network Address Translation (NAT)
or Network Address and Port Translation (NAPT) may be used at the branch location since
Avaya one-X Quick Edition locations are likely to be relatively small. In this event, a product
such as a Session Border Controller (SBC) can be used to allow SIP traffic to successfully
traverse the branch NAT/NAPT. The Acme Packet Net-Net Session Director (SD) is such an
SBC and is used here.
The reference configuration for these Application Notes is depicted in Figure 1.

Internet
ALM AV AYA
TST MM 711
AN ALOG
AC T
VH MPS
1 2 3 4 5 6 7 8
AL M AV AYA ALM AV AYA

TST TST MM 711
AN ALOG
ACT ICC AC T
SH UT D OW N MODULE
VH MPS
OK TO
R EMOVE
US B 1 U SB 2
SER V IC ES 1 2 3 4 5 6 7 8
AL M SO EI SM EM SI EO AV AYA
TST
AC T E1/T 1
MODU LE
SIG
COMPACT
PH ONE/ EXIT PAGE PAGE O PTIO N S

LEFT R IGH T
SPEAK ER HO LD
PHONE/EXI T PAGE PAGE OPTIO NS
LEFT RIG HT
HOLD H EADSET TR ANSFER

SPE AKER
PHONE/EXIT PAG E PAG E OPTI ONS ABC D EF

LEFT R IGHT C ONFEREN CE
M U TE
S PEAKE R H OLD
HE ADSE T TRANSFER 1 2 3
GH I JK L MNO
PH ONE/ EXIT PAGE PAGE O PTIO N S AB C DEF DR OP
HEAD SET TRANSFER

LEFT R IGH T 0SWIP MUTE
1 2 3
CONFERENCE
4 5 6
SPEAK ER HO LD P Q RS T UV W XYZ
GH I JKL MN O RED IAL
0SW IP M UTE
ABC D EF
CONFERENCE 4 5 6 D ROP 7 8 9
1 2 3 H EADSET TR ANSFER P Q RS T UV WXYZ
GH I
4
JK L
5
MNO
6 DROP
MU TE
ABC D EF
C ONFEREN CE
7 8 9
REDI AL
* 0 #
1 2 3
P QRS
7
TU V
8
W XYZ
9
RED IAL
GH I JK L MNO
DR OP
* 0 #
4 5 6
* 0 # P Q RS
7
T UV
8
W XYZ
9
RED IAL
* 0 #
Branch
Main
Figure 1 - Reference Configuration
Avaya one-X Quick Edition endpoints are located at the branch site while the Avaya SES server
and Avaya Communication Manager running on an Avaya S8300 Media Server are located at the
main site. A Juniper Networks Netscreen-25 is used as a NAPT router at the branch site and is

configured such that SIP and H.323 ALG capabilities are disabled. A pair of routers is used to
represent the public Internet.
Focusing on the path highlighted with the dashed line in Figure 1, the SD acts as a Back-to-Back
User Agent (B2BUA) for SIP sessions. SIP sessions are established from the Avaya one-X
Quick Edition stations at the branch location to the SD at the main location. The SD terminates
these SIP sessions then re-originates them as new sessions to the Avaya SES server. While
operating as a SIP B2BUA, the SD performs fix-up of SIP messages to enable NAPT traversal of
SIP sessions.
An additional aspect of the configuration is that the SD is configured to convert UDP based SIP
sessions from the Avaya one-X Quick Edition stations to TCP based SIP sessions to the Avaya
SES server. This is not required in general, however, and UDP may be used on both sides of the
SD.

2. Equipment and Software Validated
The equipment and software used for the reference configuration are listed in Table 1.
Device Description Versions Tested

Avaya S8300B Media Server CM R4.0, Load 730.5, (R014x.00.0.730.5)
Avaya G700 Media Gateway:
MGP HW 5, FW 25.33.0
VoIP FW 65
Avaya 4621SW one-X Quick Edition Telephone 3.0.5
Avaya 4610SW one-X Quick Edition Telephone 3.0.5
Avaya SES Server on S8500B R3.1.2 (SES-3.1.2.0-309.0)
Acme Packet Net-Net Session Director 4.1.0 P11
Juniper Networks Netscreen-25 ScreenOS 5.4.0r7.0
Avaya C363T-PWR Converged Stackable Switch 4.5.18
Avaya 4610SW IP Telephone R2.7 (H.323)
Avaya 4621SW IP Telephone R2.7 (H.323)
Table 1 - Equipment and Software

3. Configure Avaya Communication Manager
Avaya Communication Manager is generally configured according the procedures in Reference
[1] and Reference [2]. The following guidance from Reference [2] is worth highlighting and is
addressed in these Application Notes:
1. Be sure to disable shuffling on the Avaya Communication Manager to Avaya SES Server
SIP trunk (see Step 1, Section 3.5).
2. Be sure to add the G.729A codec to Avaya Communication Manager (see Step 1, Section
3.2).
The procedures in this section assume that the Avaya Communication Manager has already been
installed and otherwise configured for basic telephony services. The configuration of Avaya
Communication Manager is performed using the System Access Terminal (SAT). After the
completion of the configuration steps in this section, perform a save translation command to
make the changes permanent.

3.1. Configure System Parameters
The license file installed on the Avaya Communication Manager system controls the features and
capacities covered in this section. If a required feature is not enabled or there is insufficient
capacity, contact an authorized Avaya sales representative to make the appropriate changes.
Step Description
1. Use the display system-parameters customer-options command and navigate to Page 2
to verify that an adequate number of SIP trunks are licensed for the system. The number
of SIP trunks available for assignment is the difference between the value for Maximum
Administered SIP Trunks and the value for USED. One SIP trunk is consumed for
each call to an Avaya one-X Quick Edition station.
display system-parameters customer-options Page 2 of 10

OPTIONAL FEATURES
IP PORT CAPACITIES USED

Maximum Administered H.323 Trunks: 450 70
Maximum Concurrently Registered IP Stations: 450 4
Maximum Administered Remote Office Trunks: 0 0
Maximum Concurrently Registered Remote Office Stations: 0 0
Maximum Concurrently Registered IP eCons: 0 0
Max Concur Registered Unauthenticated H.323 Stations: 0 0
Maximum Video Capable H.323 Stations: 0 0
Maximum Video Capable IP Softphones: 0 0
Maximum Administered SIP Trunks: 450 50
Maximum Number of DS1 Boards with Echo Cancellation: 0 0

Maximum TN2501 VAL Boards: 0 0
Maximum Media Gateway VAL Sources: 0 0
Maximum TN2602 Boards with 80 VoIP Channels: 0 0
Maximum TN2602 Boards with 320 VoIP Channels: 0 0
Maximum Number of Expanded Meet-me Conference Ports: 0 0
(NOTE: You must logoff & login to effect the permission changes.)

2. Navigate to Page 5 verify that Private Networking and Uniform Dialing Plan are
enabled for the system. In the reference configuration, a uniform dialing plan is used
across Avaya Communication Manager and the Avaya one-X Quick Edition system but
this is not a requirement in general.
display system-parameters customer-options Page 5 of 10
OPTIONAL FEATURES
Multinational Locations? n Station and Trunk MSP? n

Multiple Level Precedence & Preemption? n Station as Virtual Extension? n
Multiple Locations? n
System Management Data Transfer? n
Personal Station Access (PSA)? n Tenant Partitioning? n
Posted Messages? n Terminal Trans. Init. (TTI)? n
PNC Duplication? n Time of Day Routing? n
Port Network Support? n Uniform Dialing Plan? y
Usage Allocation Enhancements? y
Processor and System MSP? n TN2501 VAL Maximum Capacity? y
Private Networking? y
Processor Ethernet? y Wideband Switching? n
Wireless? n
Remote Office? n
Restrict Call Forward Off Net? y
Secondary Data Module? y
(NOTE: You must logoff & login to effect the permission changes.)

3.2. Configure Codec Set
Step Description
1. Use the change ip-codec-set command to define the codec set to be used for calls to
Avaya one-X Quick Edition stations. The addition of the G729A codec is required to
ensure that calls involving recorded voice services on Avaya one-X Quick Edition
stations (e.g. voice mail) will be successful. Codec Set 1 is used in the reference
configuration.
On Page 1, leave the row for the default G.711MU codec. Edit the second row to set the
following fields:
Audio Codec: G.729A
Silence Suppression, Frames Per Pkt, and Packet Size (ms): Accept the default
values.
Default values can be used on Page 2.

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: G.729A n 2 20
3:
4:
5:
6:
7:
Media Encryption
1: none
2:
3:

3.3. Configure IP Network Region
Step Description
1. Use the change ip-network-region command to define the network region to be used for
calls to Avaya one-X Quick Edition endpoints. Region 1 is used in the reference
configuration.
On Page 1, set the following fields:

Authoritative Domain: The desired domain (e.g. companyabc.com).
Name: May be optionally set to a meaningful value (e.g. For SES).
Codec Set: The number of the codec set defined in the previous step (e.g. 1).
Default values may be used for the remaining pages.

change ip-network-region 1 Page 1 of 19
IP NETWORK REGION
Region: 1
Location: Authoritative Domain: companyabc.com
Name: For SES
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? n
UDP Port Max: 3329
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

3.4. Configure IP Node Name
Step Description
1. Use the change node-names ip command to define the IP address of the Avaya SES
server.
Edit a row setting the following fields:

Name: A desired name (e.g. sesabc)
IP Address: IP address of the Avaya SES server (e.g. 192.168.2.10).
Also make note of an IP node name to use in signaling group provisioning in the next
step. In the reference configuration, procr is used.
change node-names ip Page 1 of 2
IP NODE NAMES
Name IP Address
Ent-PBX 192.168.11.99
Ent-PBX-noSD 10.1.2.5
MAS 10.3.5.50
default 0.0.0.0
procr 192.168.1.5
sesabc 192.168.2.10
( 6 of 6 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

3.5. Configure SIP Trunk
Step Description
1. Use the add signaling-group command to add a signaling group for the SIP trunk group
to the Avaya SES server. Signaling Group 5 is used in the reference configuration.
Set the following fields:

Group Type: sip.
Near-end Node Name: The name of a local IP node to be used as the near end
for the signaling group connection (e.g. procr). In the reference configuration,
procr is used because an S8300 media is used.
Far-end Node Name: The name of the IP node provisioned in the previous step
(e.g. sesabc).
Far-end Domain: The same value as used previously for the Authoritative
Domain field entered on Page 1 of the Network Region form in Section 3.3 , Step
1 (e.g. companyabc.com).
Far-end Network Region: The number of the Network Region configured
previously in Section 3.3, Step 1 (e.g. 1).
Direct IP-IP Audio Connections: n. This will disable shuffling but is required to
prevent problems establishing full duplex audio to Avaya one-X Quick Edition
stations.
Default values may be used for the remaining fields.

add signaling-group 5 Page 1 of 1
SIGNALING GROUP
Group Number: 5 Group Type: sip
Transport Method: tls
Near-end Node Name: procr Far-end Node Name: sesabc

Near-end Listen Port: 5061 Far-end Listen Port: 5061
Far-end Network Region: 1
Far-end Domain: companyabc.com
Bypass If IP Threshold Exceeded? n

DTMF over IP: rtp-payload Direct IP-IP Audio Connections? n
IP Audio Hairpinning? n
Enable Layer 3 Test? n
Session Establishment Timer(min): 3

2. Use the add trunk-group command to add a trunk group controlled by the signaling
group created in the previous step. Trunk Group 5 is used in the reference configuration.
Set the following fields on Page 1:
Group Type: sip.
Group Name: May be optionally set to a descriptive value (e.g. SIP Trunk to
sesabc).
TAC: The desired trunk access code (e.g. *05).
Direction: two-way.
Service Type: tie.
Signaling Group: The number of the signaling group provisioned in the previous
step (e.g. 5).
Number of Members: The desired number of members (e.g. 50).
add trunk-group 5 Page 1 of 21
TRUNK GROUP
Group Number: 5 Group Type: sip CDR Reports: y
Group Name: SIP Trunk to sesabc COR: 1 TN: 1 TAC: *05
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Signaling Group: 5
Number of Members: 50
Default values can be used for Page 2. Set the following field on Page 3:
Numbering Format: public.
change trunk-group 5 Page 3 of 21
TRUNK FEATURES
ACA Assignment? n Measured: none
Maintenance Tests? y
Numbering Format: public

UUI Treatment: service-provider
Replace Unavailable Numbers? n
Show ANSWERED BY on Display? y
Subsequent pages need not be changed. The trunk members will be automatically
generated based on the value of Number of Members on Page 1.

3.6. Configure Dial Plan and Call Routing
In the reference configuration, a uniform dialing plan is used for Avaya Communication
Manager and Avaya one-X Quick Edition endpoints. The procedures here reflect this. A
uniform dialing plan is not required in general, however, and simpler configurations making use
of only AAR private networking are possible.
Step Description
1. Use the change dialplan analysis command to provision the extension range that will be
reserved for dialing to all Avaya one-X Quick Edition endpoints. In the reference
configuration, the 4xxx range is reserved for dialing to all Avaya one-X Quick Edition
endpoints in the network and the entries shown below reflect this.

Dialed String and Total Length: Values consistent with the extension range
used.
Call Type: ext.
change dialplan analysis Page 1 of 12
DIAL PLAN ANALYSIS TABLE
Percent Full: 3
Dialed Total Call Dialed Total Call Dialed Total Call

String Length Type String Length Type String Length Type
1 4 ext
2 4 ext
3 3 fac
4 4 ext
8 1 fac
9 1 fac
* 3 dac

2. Use the change uniform-dialplan command to provision entries for numbers used to dial
Avaya one-X Quick Edition endpoints. In the reference configuration, numbers of the
form 42xx are used and the entries shown below reflect this.

Matching Pattern, Len, and Del: Values consistent with the numbers used.
Net: aar.
change uniform-dialplan 0 Page 1 of 2
UNIFORM DIAL PLAN TABLE
Percent Full: 0
Matching Insert Node

Pattern Len Del Digits Net Conv Num
1999 4 0 aar n
25 4 0 aar n
42 4 0 aar n
n
n
n
n
n
n
n
n
n
n
n
n
n

3. Use the change aar analysis command to provision entries for the numbers used to dial
Avaya one-X Quick Edition endpoints at the branch. In the reference configuration, dialed
strings of the form 42xx are used. The entry shown here reflects this and specifies a match
on dialed strings beginning with 42 and of length 4.

Dialed String, Total Min, and Total Max: Values consistent with the numbers
used to dial Avaya one-X Quick Edition endpoints.
Route Pattern: The number for a pattern to be edited in Step 4 (e.g. 5).
Call Type: aar.
change aar analysis 0 Page 1 of 2
AAR DIGIT ANALYSIS TABLE
Percent Full: 3
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1999 4 4 2 aar n
2 4 4 1 aar n
3 7 7 254 aar n
4 7 7 254 aar n
42 4 4 5 aar n
5 7 7 254 aar n
6 7 7 254 aar n
7 7 7 254 aar n
8 7 7 254 aar n
9 7 7 254 aar n
n
n
n
n
n

4. Use the change route-pattern command to provision the route pattern added to the AAR
analysis table in the previous step. Route Pattern 5 is used in the reference configuration.
Edit the first route preference row setting the following fields:
Grp No: The number of the trunk group provisioned in Section 3.6, Step 2 (e.g.
5).
FRL: A desired value (e.g. 0).
Default values can be used for the remaining fields.

change route-pattern 5 Page 1 of 3
Pattern Number: 5 Pattern Name: OneX QE Branch1
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: 5 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

3.7. Configure Public Unknown Numbering
By setting the SIP trunk group Numbering Format field to public in Section 3.5, Step 2, and by
adding entries to in the Public Unknown Numbering Plan here in this step, Avaya
Communication Manager will be able to provide the proper calling number when outbound calls
are placed to Avaya one-X Quick Edition stations over the SIP trunk to the Avaya SES server.
Step Description
1. Use the change public-unknown-numbering command to provision entries for
extension numbers assigned to local stations. In the reference configuration, local Avaya
Communication Manager stations use the 1xxx and 2xxx extension ranges. The entries
shown here reflect this and specify that a 4-digit number is to be sent for calls from
stations whose 4-digit extension begins with 1 or 2.
Edit a row setting the Ext Len, Ext Code, and Total CPN Len fields to reflect the
extension ranges assigned to local stations.
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
Total Administered: 3
4 1 4 Maximum Entries: 240
4 2 4

4. Configure Avaya SES Server
The Avaya SES Server is generally configured according to the procedures in Reference [2].
Reference [3] describes how to configure the Avaya one-X Quick Edition system to interoperate
with the Avaya SES server. Procedures similar to those are provided in Section 5 of these
Application Notes. In Reference [3], several different models are presented for how to create
and make use of Avaya one-X Quick Edition SIP entities. The procedures covered in Section 4
and Section 5 of these Application Notes assume the model summarized on Page 4 of Reference
[3] under Case B: Everyone has a direct line. Hence, in the procedures presented here, an
Avaya SES User is added for each Avaya one-X Quick Edition station.
The following detailed steps assume that the Avaya SES server has already been installed and
otherwise configured for SIP services.

4.1. Log in, Verify System Properties
Step Description
1. Access the Avaya SES administration web interface by entering http://<ip-addr>/admin as the
URL in a Web browser, where <ip-addr> is the IP address of the Avaya SES Server.
Log in with the appropriate credentials and then select the Launch Administration Web
Interface link from the main page as shown below.

2. A new window presenting Avaya SES server administration options appears. In the left hand
navigation pane, expand Server Configuration and then click System Properties to present the
Edit System Properties page. Ensure that the entry for the SIP Domain field (e.g.
companyabc.com) matches the value used previously for the Authoritative Domain field
entered on Page 1 of the Network Region form (Section 3.3 , Step 1). If necessary, change the
SIP Domain field to match and click Update.

4.2. Configure Media Server
Step Description
1. In the left hand navigation pane, expand Media Servers and then click Add to present the Add
Media Server Interface page. Enter the following fields:
Media Server Interface Name: A descriptive name (e.g. S8300-HQ).
Host: Select an available Avaya SES host (e.g. 192.168.2.10). In the reference
configuration, only one Avaya SES host is used so this choice is populated appropriately
by default.
SIP Trunk Link Type: TLS.
SIP Trunk IP Address: The IP address of a signaling interface on Avaya
Communication Manager (e.g. 192.168.1.5).
Click Add. The additional Media Server fields are not required for the reference configuration
since the Avaya one-X Quick Edition endpoints are not native endpoints on Avaya
Communication Manager.

2. In the left hand navigation pane, expand Media Servers and then click List to present the List
Media Servers page. In the row associated with Media Server added in the previous step, click
Map.

3. When the List Media Server Address Map page is displayed, click Add Map in New Group.

4. When the Add Media Server Address Map page is presented, enter the following fields:
Name: A descriptive name (e.g. QE-Routing).

Pattern: A pattern matching string used to reflect the SIP Domain and to reflect the
extension numbers used for stations natively supported by Avaya Communication
Manager. In the reference configuration, extension numbers of the form 1xxx and 2xxx
are assigned to stations natively supported by Avaya Communication Manager. A
suitable pattern matching string is: ^sip:[1-2][0-9][0-9][0-9]@companyabc.com
Replace URI: Selected (i.e. checked).
Click Add.

4.3. Configure SES Users
Step Description
1. In the left hand navigation pane, expand Users and then click Add.

2. When the Add User page is presented, enter the following fields.
Primary Handle and User ID: Enter an Avaya SES server handle/user ID to associate
with an Avaya one-X Quick Edition SIP identity (e.g. 4200).
Password and Confirm Password: Enter the password assigned to the SIP identity.
Host: Select an available Avaya SES server host (e.g. 192.168.2.10). In the reference
configuration, only one Avaya SES server host is used so this choice is populated
appropriately by default.
First Name and Last Name: Descriptive names to be used for the SIP identity (e.g. QE
Branch1 User200).
The remaining fields are optional and can be used, if desired, to provide additional information
regarding the location of the Avaya one-X Quick Edition user.
Click Add.

3. Repeat Step 1 and Step 2 in this section as needed for all Avaya one-X Quick Edition SIP
identities. In the reference configuration, three Avaya one-X Quick Edition sets are used at the
branch location. Hence, Step 1 and Step 2 are performed for SES handle/user ID 4200, 4201
and 4202.
At the bottom of the left hand navigation pane, click Update to save and activate all changes.

5. Configure Avaya one-X Quick Edition System
The Avaya one-X Quick Edition system is generally configured according the procedures in
Reference [3] available at support.avaya.com. A notable exception is that, contrary to the
instructions in Step 7 on Page 6 of Reference [3], the IP address and port of the SBC were not
used for the Outbound Proxy Host and Outbound Proxy Host fields in service provider
configuration. Rather, the IP address and port information for the SBC were used for the Proxy
Host, Proxy Port, Registrar Host, Registrar Port fields in service provider configuration. In
consultation with R&D, this was confirmed to be the correct usage for the reference
configuration. The Outbound Proxy Host and Outbound Proxy Host fields in service provider
configuration should only rarely be used.
In Reference [3], several different models are presented for how to create and make use of
Avaya one-X Quick Edition SIP identities. The procedures presented here utilize the model
summarized on Page 4 of Reference [3] under Case B: Everyone has a direct line. The
following SIP identities will be created:
Incoming Outgoing
Extension Name Identity Password
Extension Extension
200 User 200 4200 ****** User 200, 200 User 200, 200
201 User 201 4201 ****** User 201, 201 User 201, 201
202 User 202 4202 ****** User 202, 202 User 202, 202
The procedures in this section assume that the Avaya one-X sets have already been installed and
otherwise initially configured to support intercom calling. The Extension and Name fields listed
above are configured during that process. The Identity, Password, Incoming Extension, and
Outgoing Extension fields are configured during the creation of SIP identities which will be
covered in this section. The Identity and Password fields are provisioned to match the Avaya
SES users created in Section 4.3.

Step Description
1. Use a web browser to access the web interface of the Avaya one-X Quick Edition system. Direct
the browser to the IP address of one of the Avaya one-X Quick Edition sets (e.g. 172.16.1.200).
Click System Options after the User Options Login page appears.

2. After the System Options Login page appears, enter the administrative password and click
Login.
3. On the System Options menu, click Service Provider.

4. The Configurations list is displayed. Initially, the list is empty because no configurations have
been created. Click Add Configuration in the upper right area of the screen.

5. When the Add Service Provider Configuration dialog box is displayed, configure the
following fields:
Domain Name and Realm: Enter the SIP domain name (e.g. companyabc.com). This
value must match the value used previously for the Authoritative Domain field entered
on Page 1 of the Network Region form (Section 3.3, Step 1).
Proxy Host and Registrar Host: The IP address of the Acme Packet SD interface which
faces the branch (e.g. 100.1.12.99).
Proxy Port and Registrar Port: 5060
Register Expiry Time: The desired amount of time (in seconds) that the Avaya one-X
Quick Edition sets will wait between sending updates to refresh registration information
(e.g. 3600).
Click Submit.

6. The Configurations list is displayed. In the Domain column, click the name of the service
provider created in the previous step (e.g. click companyabc.com).

7. The View Configuration Details dialog box is displayed. Click Identities.

8. The Identities dialog box is displayed. Initially, the list is empty because no SIP identities have
been added. Click Add Identity in the upper right side of the screen.

9. When the Add Configuration Identity dialog box is displayed, configure the following fields:
Identity: The value for a handle/user ID of a previously configured Avaya SES user (e.g.
4200). The Avaya SES user would have been configured in Section 4.3, Step 2.
Password and Verify Password: The password previously configured for the same
Avaya SES user. The password for the Avaya SES user would have been configured in
Section 4.3, Step 2.
Incoming Extension and Outgoing Extension: Select a Quick Edition user
name/extension from the drop down list (e.g. User 200, 200).
Use the default for the AA Script field.
Click Submit.
10. Repeat Step 8 and Step 9 in this section to create a SIP identity for each Avaya one-X Quick
Edition Station.

6. Configure Acme Packet Net-Net SD SBC
6.1. Overview of SD Configuration Elements
Figure 2 presents a pictorial view of the SD elements configured with the steps in this section.
Key parameters are noted for many of the elements.
General Elements
Global: Headquarters Facing

Branch Facing Elements bootparam Elements
Branch1_SIP Realm system-config HQ_SIP Realm
sip-config
media-manager
steering-pool steering-pool
100.1.12.99 local-policy 192.168.12.99
20000-21000 Source: 20000-21000
Branch1_SIP Branch1_SIP HQ_SIP
Forward to:
192.168.2.10 sip-interface
sip-interface
HQ_SIP HQ_SIP
Branch1_SIP
SIP 192.168.12.99:5060
100.1.12.99:5060
UDP TCP
realm-config realm-config
Branch1_SIP HQ_SIP
To_Branch1:12 To_HQ:12
network-interface network-interface
To_Branch1:12 To_HQ:12
100.1.12.99/24 192.168.12.99/24
GW: 100.1.12.1 GW: 192.168.12.1
phy-interface phy-interface
To Branch at To_Branch1 To_HQ
Port 1, Slot 1 Port 1, Slot 0 To SES at
10.1.3.2 192.168.2.10
Figure 2 - SD Configuration Elements

The following is a brief summary of the SD elements depicted in Figure 2:
bootparam: Used to configure boot parameters (e.g. IP address of management

interface).
system-config: Used to configure global, system-wide parameters (e.g. system default
gateway).
phy-interface: Used to configure uniquely named physical interfaces (e.g. interface
name, physical port, physical slot, speed, duplex). .
network-interface: Used to configure a logical network interfaces (e.g. IP address
information, VLAN). A network-interface is inked to a phy-interface via the name of a
phy-interface.
sip-interface: Used to configure a logical SIP interface (e.g. applicable realm, IP
address/port).
realm-config: Used to configure uniquely named realms (e.g. realm name, network
interface through which the realm can be reached). Realms represent groups of
endpoints, networks, and routes the SD may access and are used as the basis for
determining ingress and egress associations to network interfaces. Realms are linked to
network interfaces via associated phy-interface names.
steering-pool: Used to configure sets of ports that are used for steering media flows (e.g.
IP address, port range, associated realm). Use of steering pools is similar in concept to
constructing a firewall policy to permit RTP media.
media-manager: Used to configure global, system-wide parameters used in the media
steering functions of the SD.
sip-config: Used to configure global, system-wide SIP parameters.
sip-interface: Used to configure a logical SIP interface (e.g. associated realm, IP address
and port, transport protocol).
local-policy: Used to configure where session signaling messages are routed and/or
forwarded to (e.g. associated realms, next hop).
Additional details on the ACLI can be found in Reference [4] and Reference [5].

6.2. Acme Packet Command Line Interface Summary
The SD is configured using the Acme Packet Command Line Interface (ACLI). The following
are the generic ACLI steps for configuring various elements.
1. Log in to the SD with the user password.

2. Enable the Supersuser mode by entering the enable command and then the superuser
password. The command prompt will change to include a # instead of a >while in
Superuser mode. This level of system access (i.e. at the acmesystem# prompt) will be
referred to as the main level of the ACLI. Specific sub-levels of the ACLI will then be
accessed to configure specific elements and specific parameters of those elements.
3. In Superuser mode, enter the configure terminal command. The configure terminal
command is used to access the system level where all operating and system elements may
be configured. This level of system access will be referred to as the configuration level.
4. Enter the name of an element to be configured (e.g. system).
5. Enter the name of a sub-element, if any (e.g. phy-interface)
6. Enter the name of an element parameter followed by its value (e.g., name To_HQ).
7. Enter done to save changes to the element. Use of the done command causes the system
to save and display the settings for the current element.
8. Enter exit as many times as is necessary to return to the configuration level.
9. Repeat Steps 4 to 8 to configure all the elements.
10. Enter exit to return to the main level.
11. Type save-config to save the entire configuration.
12. Type activate-config to activate the entire configuration.
After accessing different levels of the ALCI to configure elements and parameters, it is necessary
to return to the main level in order to run certain tasks such as saving the configuration,
activating the configuration, and rebooting the system.
The configuration steps in subsequent sections provide details on each element and parameter to
be configured. Note that these steps specify only those elements and parameters that are changed
from system default values. Many of the default values provided for parameters can be accepted
without change and, in such cases, the parameters are not described in the instructions.
Many of the configuration steps also provide text captures of commands and responses for an
actual ACLI session. Within such text, the specific parameters that have been changed from
system default values are highlighted in bold.

6.3. Initial Connectivity, Deleting the System Configuration
Step Description
1. Access the console port of the SD using a cable, a PC, and terminal emulation program
such as HyperTerminal. Use the following settings for the serial port on the PC:
Bits per second: 115200

Data bits: 8
Parity : None
Stop bits: 1
Flow control: None
2. Log in to the console port of the SD with the user password to establish a User mode
ACLI session. Enable the Superuser mode for the ACLI session by entering the enable
command and then the superuser password. This level of system access (i.e. at the
acmesystem# prompt) will be referred to as the main level of the ACLI.
Password:
acmesystem>
acmesystem> enable
Password:
acmesystem#
3. Use the delete-config command to delete the current configuration.
Warning: Perform this step only if you wish to delete the current configuration and
create a new configuration from scratch.
acmesystem# delete-config
******************************************************
Do you really want to ERASE the current config:? [y/n]?: y
Deleting configuration
NOTE: need to reboot for changes to take effect
task done
acmesystem#
4. Use the configure terminal command to enter into the system level where all operating
and system elements may be configured. This level of system access will be referred to
as the configuration level.
acmesystem# configure terminal

acmesystem(configure)#

5. Use the bootparam command to review and/or change system boot parameters. In
particular, review and/or change the IP address information of the management interface
which, in the example, is the wancom0 interface. The bootparam command will prompt
for a line-by-line review of the system boot parameters. To accept a parameter as is,
press Enter. To change a parameter, type in a new value and press Enter.
Notes:
The IP address for the Ethernet interface is in the form <IP_address>:<netmask>
where IP_address is expressed in Binary Coded Decimal (BCD) and netmask is
expressed in hexadecimal.
These boot parameters are not cleared when the delete-config command is used.
acmesystem(configure)# bootparam
'.' = clear field; '-' = go to previous field; q = quit
boot device : wancom0
processor number : 0
host name :
file name : /tffs0/sd410p11.gz
inet on ethernet (e) : 172.16.16.56:ffffff00
inet on backplane (b) :
host inet (h) : 172.16.16.56
gateway inet (g) : 172.16.16.1
user (u) : vxftp
ftp password (pw) (blank = use rsh) : vxftp
flags (f) : 0x80008
target name (tn) :
startup script (s) :
other (o) :
NOTE: These changed parameters will not go into effect until reboot.
Also, be aware that some boot parameters may also be changed through PHY
and Network Interface Configurations.

6. Enter the exit command to exit to the main level then use the reboot command to reboot
the system.
acmesystem(configure)# exit
acmesystem#
acmesystem# reboot
-----------------------------------------
WARNING: you are about to reboot this SD!
-----------------------------------------
Reboot this SD [y/n]?: y
/code synced and unmounted
/boot synced and unmounted
7. After the SD has rebooted, log back in to the SD with the user password. Enter the
enable command again along with the superuser password to access the main level. Then
use the configure terminal command again to return to the configuration level.
Password:
acmesystem> enable
Password:

6.4. Configure System Configuration
Step Description
1. Set the system level default gateway. A system level default gateway is needed in cases
where a telnet session will be used to manage the SD and the management PC is not on
the same subnetwork as the management interface of the SD.
Use the following steps to configure the default gateway:

Navigate to the systemsystem-config element by entering the system
command and then the system-config command.
Enter the select command to instantiate the system-config element.
Enter the default-gateway command providing the IP address for the default
gateway (e.g. 172.16.16.1)
Enter the done command to save the changes to the system-config element.
Notes:
Only the default-gateway parameter is changed in this example. Other
parameters for the system-config element are left at system default values.
The IP address used for the default-gateway parameter is likely to be the same IP
address used for the gateway boot parameter (Section 6.3, Step 5).
acmesystem(configure)# system
acmesystem(system)# system-config
acmesystem(system-config)# select
acmesystem(system-config)# default-gateway 172.16.16.1
acmesystem(system-config)# done
system-config
hostname
description
location
mib-system-contact
mib-system-name
mib-system-location
snmp-enabled enabled
enable-snmp-auth-traps disabled
enable-snmp-syslog-notify disabled
enable-snmp-monitor-traps disabled
enable-env-monitor-traps disabled
snmp-syslog-his-table-length 1
snmp-syslog-level WARNING
system-log-level WARNING
process-log-level NOTICE
process-log-ip-address 0.0.0.0
process-log-port 0
call-trace disabled
internal-trace disabled
log-filter all
default-gateway 172.16.16.1
restart enabled
exceptions
telnet-timeout 0
console-timeout 0
remote-control enabled

last-modified-date 2007-02-28 18:43:09
acmesystem(system-config)#
2. Save and activate the changes to the system configuration. Enter the exit command three
times in succession to exit out to the main level. Enter the save-config command to save
the entire configuration and then enter the activate-config command to activate the
configuration.
acmesystem(system-config)# exit
acmesystem(system)# exit
acmesystem# save-config
Save-Config received, processing.
waiting 1200 for request to finish
Request to 'SAVE-CONFIG' has Finished,
Save complete
Currently active and saved configurations do not match!
To sync & activate, run 'activate-config' or 'reboot activate'.
acmesystem# activate-config
Activate-Config received, processing.
Request to 'ACTIVATE-CONFIG' has Finished,
Activate Complete
acmesystem#
Upon completion of the steps in this section, either the console port or a telnet session to the
management interface may be used to complete configuration tasks. When using a telnet
session, telnet to the IP address of the management interface as configured in boot parameters.
The same user password and superuser password as used for the console port may be used for a
telnet session.

6.5. Configure Physical Interfaces
Step Description
1. Configure the physical interface leading to the main location. Navigate to the configure
terminalsystemphy-interface element and add a physical interface by configuring
the following parameters:
name: A unique name (e.g. To_HQ)

operation-type: Media
port: An available port (e.g. 1).
slot: An available slot (e.g. 0)
Enter the done command to save the changes and use the exit command as many times as
is necessary to return to the configuration level.
acmesystem(system)# phy-interface
acmesystem(phy-interface)# name To_HQ
acmesystem(phy-interface)# operation-type Media
acmesystem(phy-interface)# port 1
acmesystem(phy-interface)# slot 0
acmesystem(phy-interface)# done
phy-interface
name To_HQ
operation-type Media
port 1
slot 0
virtual-mac
admin-state enabled
auto-negotiation enabled
duplex-mode FULL
speed 100
acmesystem(phy-interface)# exit

2. Configure the physical interface leading to the branch location. Navigate to the
configure terminalsystem phy-interface element and add a physical interface by
configuring the following parameters:
name: A unique name (e.g. To_Branch1)

operation-type: Media
port: An available port (e.g. 1).
slot: An available slot (e.g. 1)
acmesystem(system)# phy-interface
acmesystem(phy-interface)# name To_Branch1
acmesystem(phy-interface)# operation-type Media
acmesystem(phy-interface)# port 1
acmesystem(phy-interface)# slot 1
acmesystem(phy-interface)# done
phy-interface
name To_Branch1
operation-type Media
port 1
slot 1
virtual-mac
admin-state enabled
auto-negotiation enabled
duplex-mode FULL
speed 100
acmesystem(phy-interface)# exit

6.6. Configure Network Interfaces
Step Description
1. Configure the network interface leading to the main location. Navigate to the configure
terminalsystemnetwork-interface element and add a network interface by
name: The associated physical interface defined in Section 6.5, Step 1 (e.g.
To_HQ).
sub-port-id: A VLAN number (e.g. 12). Use of a VLAN is optional but is
required in cases where the same physical interface is assigned multiple IP
addresses.
ip-address: IP address for the interface (e.g. 192.168.12.99).
netmask: netmask for the interface (e.g. 255.255.255.0).
gateway: IP address for the gateway on the subnetwork (e.g. 192.168.12.1)
acmesystem(system)# network-interface
acmesystem(network-interface)# name To_HQ
acmesystem(network-interface)# sub-port-id 12
acmesystem(network-interface)# ip-address 192.168.12.99
acmesystem(network-interface)# netmask 255.255.255.0
acmesystem(network-interface)# gateway 192.168.12.1
acmesystem(network-interface)# done
network-interface
name To_HQ
sub-port-id 12
hostname
ip-address 192.168.12.99
pri-utility-addr
sec-utility-addr
netmask 255.255.255.0
gateway 192.168.12.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
dns-timeout 11
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address

acmesystem(network-interface)# exit

2. Configure the network interface leading to the branch location. Navigate to the
configure terminalsystemnetwork-interface element and add a network interface
by configuring the following parameters:
name: The associated physical interface defined in Section 6.5, Step 2 (e.g.
To_Branch1)
sub-port-id: A VLAN number (e.g. 12). Use of a VLAN is optional but will be
required in cases where the same physical interface is assigned multiple IP
addresses.
ip-address: IP address for the interface (e.g. 100.1.12.99).
netmask: netmask for the interface (e.g. 255.255.255.0).
gateway: IP address for the gateway on the subnetwork (e.g. 100.1.12.1).
acmesystem(network-interface)# name To_Branch1
acmesystem(network-interface)# sub-port-id 12
acmesystem(network-interface)# ip-address 100.1.12.99
acmesystem(network-interface)# netmask 255.255.255.0
acmesystem(network-interface)# gateway 100.1.12.1
network-interface
name To_Branch1
sub-port-id 12
hostname
ip-address 100.1.12.99
pri-utility-addr
sec-utility-addr
netmask 255.255.255.0
gateway 100.1.12.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1
dns-ip-backup2
dns-domain
dns-timeout 11
hip-ip-list
ftp-address
icmp-address
snmp-address
telnet-address

6.7. Configure Realms
Step Description
1. Configure a realm associated with the main location. Navigate to the configure
terminalmedia-managerrealm-config element and add a realm by configuring the
following parameters:
identifier: A unique name (e.g. HQ_SIP).

network-interfaces: The associated network interface defined in Section 6.6,
Step 1 (e.g. To_HQ:12). Note that the form of the referenced network interface is
<Name>:<VLAN> when VLANs are used, otherwise only the name of the
physical interface is entered.
acmesystem(configure)# media-manager
acmesystem(media-manager)# realm-config
acmesystem(realm-config)# identifier HQ_SIP
acmesystem(realm-config)# network-interfaces To_HQ:12
acmesystem(realm-config)# done
realm-config
identifier HQ_SIP
addr-prefix 0.0.0.0
network-interfaces
To_HQ:12
mm-in-realm disabled
mm-in-network enabled
mm-same-ip enabled
mm-in-system enabled
msm-release disabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
observ-window-size 0
parent-realm
dns-realm
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
average-rate-limit 0
access-control-trust-level none
invalid-signal-threshold 0
maximum-signal-threshold 0
untrusted-signal-threshold 0
deny-period 30
symmetric-latching disabled
pai-strip disabled

trunk-context
early-media-allow
additional-prefixes
restricted-latching none
restriction-mask 32
accounting-enable enabled
acmesystem(realm-config)# exit
acmesystem(media-manager)# exit
2. Configure a realm associated with the branch location. Navigate to the configure
terminalmedia-managerrealm-config element and add a realm by configuring the
following parameters:
identifier: A unique name (e.g. Branch1_SIP).

network-interfaces: The associated network interface defined in Section 6.6,
Step 2 (e.g. To_Branch1:12). Note that the form of the referenced network
interface is <Name>:<VLAN> when VLANs are used, otherwise only the name
of the physical interface is entered.
acmesystem(media-manager)# realm-config
acmesystem(realm-config)# identifier Branch1_SIP
acmesystem(realm-config)# network-interfaces To_Branch1:12
acmesystem(realm-config)# done
realm-config
identifier Branch1_SIP
addr-prefix 0.0.0.0
network-interfaces
To_Branch1:12
mm-in-realm disabled
mm-in-network enabled
mm-same-ip enabled
mm-in-system enabled
msm-release disabled
qos-enable disabled
max-bandwidth 0
ext-policy-svr
max-latency 0
max-jitter 0
max-packet-loss 0
observ-window-size 0
parent-realm
dns-realm
media-policy
in-translationid
out-translationid
in-manipulationid
out-manipulationid
class-profile
average-rate-limit 0
access-control-trust-level none
invalid-signal-threshold 0
maximum-signal-threshold 0

untrusted-signal-threshold 0
deny-period 30
symmetric-latching disabled
pai-strip disabled
trunk-context
early-media-allow
additional-prefixes
restricted-latching none
restriction-mask 32
accounting-enable enabled
acmesystem(realm-config)# exit

6.8. Configure Steering Pools
Step Description
1. Configure a steering pool associated with the service provider location. Navigate to the
configure terminalmedia-managersteering-pool element and add a steering pool
ip-address: The IP address assigned to the network interface defined in Section

6.6, Step 1 (e.g. 192.168.12.99).
start-port: The start port value that begins the range of ports available to the
steering pool (e.g. 20000).
end-port: The end port value that ends the range of ports available to the steering
pool (e.g. 21000).
realm-id: The associated realm defined in Section 6.7, Step 1 (e.g. HQ_SIP).
acmesystem(media-manager)# steering-pool
acmesystem(steering-pool)# ip-address 192.168.12.99
acmesystem(steering-pool)# start-port 20000
acmesystem(steering-pool)# end-port 21000
acmesystem(steering-pool)# realm-id HQ_SIP
acmesystem(steering-pool)# done
steering-pool
ip-address 192.168.12.99
start-port 20000
end-port 21000
realm-id HQ_SIP
network-interface
acmesystem(steering-pool)# exit

2. Configure a steering pool associated with the enterprise location. Navigate to the
configure terminalmedia-managersteering-pool element and add a steering pool
ip-address: The IP address assigned to the network interface defined in Section

6.6, Step 2 (e.g. 100.1.12.99).
start-port: The start port value that begins the range of ports available to the
steering pool (e.g. 20000).
end-port: The end port value that ends the range of ports available to the steering
pool (e.g. 21000).
realm-id: The associated realm defined in Section 6.7, Step 2 (e.g.
Branch1_SIP).
acmesystem(media-manager)# steering-pool
acmesystem(steering-pool)# ip-address 100.1.12.99
acmesystem(steering-pool)# start-port 20000
acmesystem(steering-pool)# end-port 21000
acmesystem(steering-pool)# realm-id Branch1_SIP
acmesystem(steering-pool)# done
steering-pool
start-port 20000
end-port 21000
realm-id Branch1_SIP
network-interface
acmesystem(steering-pool)# exit

6.9. Configure Media Manager
Step Description
1. Configure media-manager parameters with the following steps:
Navigate to the configure terminalmedia-managermedia-manager

element.
Enter the select command to instantiate the media-manager element.
Enter the done command to save the changes to the media-manager element.
Use the exit command as many times as is necessary to return to the configuration
level.
Notes:
No changes to default media-manager parameters are made in this example; all
default values are accepted. However, this task is required in order to create and
save an instance of media-manager parameters.
acmesystem(media-manager)# media-manager
acmesystem(media-manager-config)# select
acmesystem(media-manager-config)# done
media-manager
state enabled
latching enabled
flow-time-limit 86400
initial-guard-timer 300
subsq-guard-timer 300
tcp-flow-time-limit 86400
tcp-initial-guard-timer 300
tcp-subsq-guard-timer 300
tcp-number-of-ports-per-flow 2
hnt-rtcp disabled
algd-log-level NOTICE
mbcd-log-level NOTICE
home-realm-id
red-flow-port 1985
red-mgcp-port 1986
red-max-trans 10000
red-sync-start-time 5000
red-sync-comp-time 1000
max-signaling-bandwidth 10000000
max-untrusted-signaling 100
min-untrusted-signaling 30
app-signaling-bandwidth 0
tolerance-window 30
rtcp-rate-limit 0
min-media-allocation 32000
min-trusted-allocation 1000
deny-allocation 1000
acmesystem(media-manager-config)# exit

6.10. Configure Global SIP Parameters
Step Description
1. Configure sip-config parameters with the following steps:
Navigate to the configure terminalsession-routersip-config element.

Enter the select command to instantiate the sip-config element.
Configure the following parameters of the sip-config element:
home-realm-id: The realm associated with the main location defined in Section
6.7, Step 1 (e.g. HQ_SIP).
registrar-domain: *. Note: * is a wildcard to allow any domain.
registrar-host: *. Note: * is a wildcard to allow any host.
registrar port: 5060
options: max-udp-length=0. Note: This options forces the SD to send
fragmented UDP packets (i.e. a maximum UDP datagram size is not enforced).
Even though these Applications Notes focus on the use of TCP SIP connections,
this setting is suggested here as a good practice.
is necessary to return to the main level.
acmesystem(configure)# session-router
acmesystem(session-router)# sip-config
acmesystem(sip-config)# select
acmesystem(sip-config)# home-realm-id HQ_SIP
acmesystem(sip-config)# registrar-domain *
acmesystem(sip-config)# registrar-host *
acmesystem(sip-config)# registrar-port 5060
acmesystem(sip-config)# options max-udp-length=0
acmesystem(sip-config)# done
sip-config
state enabled
operation-mode dialog
dialog-transparency enabled
home-realm-id HQ_SIP
egress-realm-id
nat-mode None
registrar-domain *
registrar-host *
registrar-port 5060
init-timer 500
max-timer 4000
trans-expire 32
invite-expire 180
inactive-dynamic-conn 32
pac-method
pac-interval 10
pac-strategy PropDist
pac-load-weight 1

pac-session-weight 1
pac-route-weight 1
pac-callid-lifetime 600
pac-user-lifetime 3600
red-sip-port 1988
red-max-trans 10000
red-sync-start-time 5000
red-sync-comp-time 1000
add-reason-header disabled
sip-message-len 4096
options max-udp-length=0
acmesystem(sip-config)# exit
acmesystem(session-router)# exit

6.11. Configure SIP Interfaces
Step Description
1. Configure a SIP interface associated with the main location. Navigate to the configure
terminalsession-routersip-interface element and add a SIP interface by
realm-id: The name of the realm to which the SIP interface applies. In this case,
use the realm associated with the main location defined in Section 6.7, Step 1
(e.g. HQ_SIP).
sip-portsaddress: The IP address used for the network interface leading to the
main location defined in Section 6.6, Step 1 (e.g. 192.168.12.99).
sip-portstransport-protocol: TCP
Enter the done command to save the changes to the sip-port element and use the exit
command to exit out to the sip-interface element. Then enter the done command again
to save the changes to the sip-interface element. Then use the exit command as many
times as is necessary to return to the configuration level.
acmesystem(session-router)# sip-interface
acmesystem(sip-interface)# realm-id HQ_SIP
acmesystem(sip-interface)# sip-ports
acmesystem(sip-port)# address 192.168.12.99
acmesystem(sip-port)# transport-protocol TCP
acmesystem(sip-port)# done
sip-port
address 192.168.12.99
port 5060
transport-protocol TCP
tls-profile
allow-anonymous all
acmesystem(sip-port)# exit
acmesystem(sip-interface)# done
sip-interface
state enabled
realm-id HQ_SIP
sip-port
address 192.168.12.99
port 5060
transport-protocol TCP
tls-profile
allow-anonymous all
carriers
proxy-mode
redirect-action
contact-mode none
nat-traversal none
nat-interval 30
tcp-nat-interval 90
registration-caching disabled
min-reg-expire 300
registration-interval 3600

route-to-registrar disabled
secured-network disabled
teluri-scheme disabled
uri-fqdn-domain
trust-mode all
max-nat-interval 3600
nat-int-increment 10
nat-test-increment 30
sip-dynamic-hnt disabled
stop-recurse 401,407
port-map-start 0
port-map-end 0
in-manipulationid
out-manipulationid
sip-ims-feature disabled
operator-identifier
anonymous-priority none
max-incoming-conns 0
per-src-ip-max-incoming-conns 0
inactive-conn-timeout 0
network-id
ext-policy-server
default-location-string
charging-vector-mode pass
charging-function-address-mode pass
ccf-address
ecf-address
term-tgrp-mode none
implicit-service-route disabled
rfc2833-payload 101
rfc2833-mode transparent
acmesystem(sip-interface)# exit

2. Configure a SIP interface associated with the branch location. Navigate to the configure
terminalsession-routersip-interface element and add a SIP interface by
realm-id: The name of the realm to which the SIP interface applies. In this case,
use the realm associated with the branch location defined in Section 6.7, Step 2
(e.g. Branch1_SIP).
nat-traversal: always
registration-caching: enabled
route-to-registrar: enabled
sip-portsaddress: The IP address used for the network interface leading to the
branch location defined in Section 6.6, Step 2 (e.g. 100.1.12.99).
sip-portstransport-protocol: UDP
sip-portsallow-anonymous: registered
Enter the done command to save the changes to the sip-port element and use the exit
command to exit out to the sip-interface element. Then enter the done command again
to save the changes to the sip-interface element. Then use the exit command as many
times as is necessary to return to the configuration level.
acmesystem(session-router)# sip-interface
acmesystem(sip-interface)# realm-id Branch1_SIP
acmesystem(sip-interface)# nat-traversal always
acmesystem(sip-interface)# registration-caching enabled
acmesystem(sip-interface)# route-to-registrar enabled
acmesystem(sip-interface)# sip-ports
acmesystem(sip-port)# address 100.1.12.99
acmesystem(sip-port)# transport-protocol UDP
acmesystem(sip-port)# allow-anonymous registered
acmesystem(sip-port)# done
sip-port
address 100.1.12.99
port 5060
transport-protocol UDP
tls-profile
allow-anonymous registered
acmesystem(sip-port)# exit
acmesystem(sip-interface)# done
sip-interface
state enabled
realm-id Branch1_SIP
sip-port
address 100.1.12.99
port 5060
transport-protocol UDP
tls-profile
allow-anonymous registered
carriers
proxy-mode
redirect-action
contact-mode none
nat-traversal always
nat-interval 30

tcp-nat-interval 90
registration-caching enabled
min-reg-expire 300
registration-interval 3600
route-to-registrar enabled
secured-network disabled
teluri-scheme disabled
uri-fqdn-domain
trust-mode all
max-nat-interval 3600
nat-int-increment 10
nat-test-increment 30
sip-dynamic-hnt disabled
stop-recurse 401,407
port-map-start 0
port-map-end 0
in-manipulationid
out-manipulationid
sip-ims-feature disabled
operator-identifier
anonymous-priority none
max-incoming-conns 0
per-src-ip-max-incoming-conns 0
inactive-conn-timeout 0
network-id
ext-policy-server
default-location-string
charging-vector-mode pass
charging-function-address-mode pass
ccf-address
ecf-address
term-tgrp-mode none
implicit-service-route disabled
rfc2833-payload 101
rfc2833-mode transparent
acmesystem(sip-interface)# exit

6.12. Configure Local Policy
Step Description
1. Configure a local policy for routing SIP sessions to the Avaya SES server. Navigate to
the configure terminalsession-routerlocal-policy element and add a SIP interface
source-realm: The name of the realm associated with the source of ingress traffic
(i.e. realm from which SIP session traffic will be received by the SD). In this
case, use the realm associated with the branch location defined in Section 6.7,
Step 2 (e.g. Branch1_SIP).
from-address: *. Note: This parameter identifies the valid from IP addresses
that the local policy will test for. In this example, a * is used as a wildcard for
all IP addresses.
from-address: *. Note: This parameter identifies the valid to IP addresses that
the local policy will test for. In this example, a * is used as a wildcard for all IP
addresses.
policy-attributesnext-hop: The IP address of the SES server (e.g.
192.168.2.10).
policy-attributesrealm: The name of the realm associated with the destination
of egress traffic (i.e. the realm in which the Avaya SES server resides). In this
case, use the realm associated with the main location defined in Section 6.7, Step
1 (e.g. HQ_SIP)
policy-attributesapp-protocol: SIP
Enter the done command to save the changes to the policy-attributes element and use
the exit command to exit out to the local-policy element. Then enter the done command
again to save the changes to the local-policy element. Then use the exit command as
many times as is necessary to return to the main level.
acmesystem(session-router)# local-policy
acmesystem(local-policy)# source-realm Branch1_SIP
acmesystem(local-policy)# from-address *
acmesystem(local-policy)# to-address *
acmesystem(local-policy)# policy-attributes
acmesystem(local-policy-attributes)# next-hop 192.168.2.10
acmesystem(local-policy-attributes)# realm HQ_SIP
acmesystem(local-policy-attributes)# app-protocol SIP
acmesystem(local-policy-attributes)# done
policy-attribute
next-hop 192.168.2.10
realm HQ_SIP
action none
terminate-recursion disabled
carrier
start-time 0000
end-time 2400

days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
acmesystem(local-policy-attributes)# exit
acmesystem(local-policy)# done
local-policy
from-address
*
to-address
*
source-realm
Branch1_SIP
activate-time N/A
deactivate-time N/A
state enabled
policy-priority none
policy-attribute
next-hop 192.168.2.10
realm HQ_SIP
action none
terminate-recursion disabled
carrier
start-time 0000
end-time 2400
days-of-week U-S
cost 0
app-protocol SIP
state enabled
media-profiles
acmesystem(local-policy)# exit
acmesystem#

6.13. Save, Verify, Activate, and Backup Configuration
Step Description
1. From the main level, save the configuration with the save-config command.
Save complete
acmesystem#
2. Verify the configuration with the verify-config command. This command will verify that
dependencies in configuration data are satisfied (e.g. that references to realm names
exist).
acmesystem# verify-config
Verifying Configuration:
Checking realm list for each sip-interface...
OK. Each referenced realm exists.
Checking realm list for each session-agent...
Checking realm list for each sip-config home...
Checking realm list for each sip-config egress...
Checking realm list for each steering-pool...
Checking policy-attribute list for each local-policy...
Checking source-realm list for each local-policy...
OK. Each referenced source-realm exists.
Checking realm list for each local-policy...
Checking for realm-config network-interfaces...
OK. All realm-config network-interfaces exist.
Checking for physical-interface network-interfaces...
OK. All physical-interface network-interfaces exist.
Checking gateway list for each host-route...
OK. Each referenced gateway exists.
OK. The system-config default gateway (172.16.16.1) is present in
the network-interface wancom
Configuration elements checked are valid.
acmesystem#

3. Activate the configuration with the activate-config command. This command will
activate the saved configuration (i.e. it will cause the saved configuration to come into
effect).
Activate Complete
acmesystem#
4. Back up the configuration by using the backup-config command followed by a file name
(e.g. 070228-QE_sip.tar.gz). The display-backups command may be used to list the
available configuration file backups.
Notes:
These backup files are maintained on the SD itself. For off-line storage of backup
files, the backup file must be retrieved using an FTP session as covered in the next
step.
acmesystem# backup-config 070228-QE_sip.tar.gz

task done
acmesystem# display-backups
1_19_2007.acme.tar.gz
070207-baseline-sip-config.tar.gz
070208-siponly_nosipnat_tcp.tar.gz
070212-baseline-nosipnat.tar.gz
070212-siponly_appnote.tar.gz
070215-sip_tcp.tar.gz
070220-merged.tar.gz
070228-QE_sip.tar.gz
070228-merged_with_QE.tar.gz
acmesystem#

5. Retrieve the backup file using an FTP session. The example below depicts the use of the
command line FTP client available in Microsoft Windows. Log in as user along with
the user password. After logging in, navigate to the /code/bkups directory where backup
files are stored on the SD. Set the transfer mode to binary using the FTP bin command.
As a convenience, issue the FTP hash command so that the progress of the FTP
download is displayed. Then use the FTP get command to retrieve the backup file
supplying the name for the backup file that was previously created.
C:\ftp>
C:\ftp>ftp 172.16.16.56
Connected to 172.16.16.56.
220 acmesystem FTP server (Acme Packet 1.0) ready.
User (135.8.137.56:(none)): user
331 Password required for user.
Password:
230 User user logged in.
ftp> cd code
250 CWD command successful.
ftp> cd bkups
250 CWD command successful.
ftp> dir
200 PORT command successful.
150 Opening ASCII mode data connection for 'file list'.
size date time name
-------- ------ ------ --------
1024 Feb-28-2007 19:15:36 . <DIR>
1024 Feb-28-2007 19:15:36 .. <DIR>
11394 Jan-19-2007 18:52:54 1_19_2007.acme.tar.gz
11470 Feb-06-2007 17:34:44 070207-baseline-sip-config.tar.gz
5804 Feb-08-2007 12:57:56 070208-siponly_nosipnat_tcp.tar.gz
11086 Feb-08-2007 16:10:16 070212-baseline-nosipnat.tar.gz
5806 Feb-12-2007 18:32:38 070212-siponly_appnote.tar.gz
5561 Feb-15-2007 19:25:36 070215-sip_tcp.tar.gz
11141 Feb-20-2007 13:53:18 070220-merged.tar.gz
5539 Feb-28-2007 19:14:32 070228-QE_sip.tar.gz
11066 Feb-28-2007 13:19:50 070228-merged_with_QE.tar.gz
226 Transfer complete.
ftp: 811 bytes received in 0.00Seconds 811000.00Kbytes/sec.
ftp> bin
200 Type set to I.
ftp> hash
Hash mark printing On ftp: (2048 bytes/hash mark) .
ftp> get 070228-QE_sip.tar.gz
200 PORT command successful.
150 Opening BINARY mode data connection for '/code/bkups/070228-
QE_sip.tar.gz' (
5539 bytes).
##
226 Transfer complete.
ftp: 5539 bytes received in 0.18Seconds 30.60Kbytes/sec.
ftp>

7. Verification Steps
7.1. Call Flow Testing
The following call flows should be tested to verify that the configuration is operating as
expected:
1. Verify that basic, point to point calling is operating properly by placing calls from Avaya
Communication Manager stations to Avaya one-X Quick Edition stations and vice versa.
For every call, verify that audio paths are available in both directions.
2. Verify that conference calling is operating properly by establishing conference calls
where the conference host is both an Avaya Communication Manager station and an
Avaya one-X Quick Edition station. Verify that audio paths are available in both
directions to all parties on the conference call.
3. Verify that call transfer is operating properly by transferring calls from an Avaya
Communication Manager station to an Avaya one-X Quick Edition station and vice
versa. For every call, verify that audio paths are available in both directions both before
and after the call is transferred.
4. Verify that Avaya Communication Manager stations can be used to leave voice mail
messages for Avaya one-X Quick Edition stations. Verify that these messages can also
be retrieved and listened to when accessing voice mail messages from an Avaya
Communication Manager station.
All of the above call flows were tested successfully during the generation of these Application
Notes. As of the writing of these Application Notes, the Avaya one-X Quick Edition
park/retrieve feature did not operate properly in the reference configuration. In particular, full
duplex audio is not present under the following circumstances:
1. A call from an Avaya Communication Manager station to an Avaya one-X Quick Edition
station is parked and retrieved twice by Avaya one-X Quick Edition stations. The first
park/retrieve is successful but lack of audio is experienced after the second retrieve.
Automated Attendant is transferred to an Avaya one-X Quick Edition station and then
parked/retrieved by Avaya one-X Quick Edition stations. Lack of audio is experienced
after the retrieve.
Group is answered by a group member and then parked/retrieved by Avaya one-X Quick
Edition stations. Lack of audio is experienced after the retrieve.
The last two scenarios above were not utilized or configured for in these Application Notes but
are mentioned here for completeness. This issue has been captured as Avaya one-X Quick
Edition Bugzilla Bug 7285. The lack of audio can be rectified by parking and unparking the call
at the same Avaya one-X Quick Edition station where the lack of audio is experienced.

7.2. Troubleshooting
This section contains basic troubleshooting tasks that may be performed if calls cannot be
completed as expected.
Step Description
1. Verify that the SD is accessible from the branch network. Use of the ping command from
a PC on the branch network may be suitable assuming the NAPT router permits the
proper ICMP traffic.
Note: In order for the branch facing network interface on the SD to reply to ICMP traffic
(e.g. ping), additional configuration steps not shown in Section 6.6, Step 2 must be
performed on the SD. The add-hip-ip and add-icmp-ip commands must be used to
enable ICMP for the IP address of branch facing network interface. In addition, a system
level host-route for the network at the branch must be added. An example is depicted
below:
acmesystem(system)# host-route
acmesystem(host-route)# dest-network 10.1.3.0
acmesystem(host-route)# netmask 255.255.255.0
acmesystem(host-route)# gateway 100.1.12.1
acmesystem(host-route)# done
host-routes
dest-network 10.1.3.0
netmask 255.255.255.0
gateway 100.1.12.1
acmesystem(host-route)# exit
acmesystem(network-interface)# select
<name>:<sub-port-id>:
1: To_HQ:12 ip=192.168.12.99 gw=192.168.12.1

2: To_Branch1:12 ip=100.1.12.99 gw=100.1.12.1
selection: 2
acmesystem(network-interface)# add-hip-ip 100.1.12.99
acmesystem(network-interface)# add-icmp-ip 100.1.12.99
network-interface
name To_Branch1
sub-port-id 12
hostname
pri-utility-addr
sec-utility-addr
netmask 255.255.255.0
gateway 100.1.12.1
sec-gateway
gw-heartbeat
state disabled
heartbeat 0
retry-count 0
retry-timeout 1
health-score 0
dns-ip-primary
dns-ip-backup1

dns-ip-backup2
dns-domain
dns-timeout 11
hip-ip-list 100.1.12.99
ftp-address
icmp-address 100.1.12.99
snmp-address
telnet-address
Save complete
Activate Complete
acmesystem#

2. Use the show sipd endpoint-ip command to verify that the SD has SIP registrations for
all Avaya one-X Quick Edition SIP identities. Example uses of this command are shown
below. The form of the command is:
show sipd endpoint-ip <phone number>
The command uses the <phone number> argument to search for registrations by
endpoints that are registered using <phone number>. If a matching registration is found,
summary information for the registration is displayed. Note that in the examples below,
behind-nat is reported indicating that the SD determined that the SIP endpoints are
behind a NAT. The last example shown below is for a case where no matching
registration is found.
acmesystem# show sipd endpoint-ip 4200

User <sip:4200@companyabc.com>
Contact local-exp=26 exp=3074
UA-Contact: <sip:4200@172.16.1.200;behind-nat=10.1.3.2:1024> UDP
SD-Contact: <sip:4200-8k1hoamhrk4rb@192.168.12.99:5060>
Call-ID: ecd12f9ab5c5d2b937b2d22290d2dd54@companyabc.com'
SD-Contact: <sip:4201-9s1j8bqhs45vb@192.168.12.99:5060>
Call-ID: 21a55f594a8f6d844f53624c78c3855b@companyabc.com'
SD-Contact: <sip:4202-a42lobuhtk53c@192.168.12.99:5060>
Call-ID: 59245d575ff7e9040c7fa81db8c79401@companyabc.com'
Entry not found
acmesystem#

3. Verify that all Avaya one-X Quick Edition SIP identities are registered with the SES.
In the left hand navigation pane of Avaya SES server administration, expand Users and
click Registered Users. When the Search Registered Users page appears, click Search.
When the warning page appears, click OK to confirm that the search should be completed.

4. Verify that all Avaya one-X Quick Edition SIP identities are reflected in the search results.

5. Use the status signaling-group command to verify that Group State is in-service for the
signaling group between Avaya Communication Manager and the Avaya SES server.
status signaling-group 5
STATUS SIGNALING GROUP
Group ID: 5 Active NCA-TSC Count: 0

Group Type: sip Active CA-TSC Count: 0
Signaling Type: facility associated signaling
Group State: in-service
6. Use the status trunk command to verify that Service State is either in-service/idle or in-
service/active for the members of the SIP trunk group between Avaya Communication
Manager and the Avaya SES server.
status trunk 5 Page 1
TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports
Busy
0005/001 T00031 in-service/idle no
press CANCEL to quit -- press NEXT PAGE to continue

8. Conclusion
These Application Notes have provided the steps needed to configure an Acme Packet Net-Net
SD to support SIP telephony services involving an Avaya one-X Quick Edition system, an
Avaya SES server, and Avaya Communication Manager. The SD is used to enable NAPT
traversal of SIP sessions from Avaya one-X Quick Edition endpoints such that the public Internet
may be used for transport of SIP sessions. A common uniform dialing plan was successfully
implemented for Avaya Communication Manager stations and Avaya one-X Quick Edition
stations. The testing performed during the creation of these application notes demonstrated that
the reference configuration successfully supported NAPT traversal of SIP sessions and supported
conversion from UDP to TCP for SIP sessions. With the exception of the Avaya one-X Quick
Edition park/retrieve feature, all calling scenarios operated as expected.
These Application Notes have also provided a basic summary of SD configuration elements and
have provided detailed examples of ACLI interactions. This may be useful to those not familiar
with configuration of the SD.

9. References
[1] SIP Support in Avaya Communication Manager Running on the Avaya S8300, S8400,
S8500 series, and S8700 series Media Server, 555-245-206, Issue 6.1, March 2007.
Available at support.avaya.com.
[2] Application Note: Avaya one-X Quick Edition, Configuring SIP Trunking to a one-X
Quick Edition Network on CCS/SES and CM, TSS-000001_2, November 2006.
[3] Application Note: Avaya one-X Quick Edition, Configuring a one-X Quick Edition
Network to Interoperate with CCS/SES and CM, TSS-000002_2, November 2006.
[4] Net-Net Session Director Configuration Guide, Version 4.1.
[5] Net-Net ACLI Reference Guide, Version 4.1.

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


Acme QE

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Acme QE

Uploaded by

Copyright:

Available Formats

Avaya Solution & Interoperability Test Lab

Application Notes for Configuring an Acme Packet Net-Net

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 76

The reference configuration for these Application Notes is depicted in Figure 1.

AL M AV AYA ALM AV AYA

PH ONE/ EXIT PAGE PAGE O PTIO N S

HOLD H EADSET TR ANSFER

PHONE/EXIT PAG E PAG E OPTI ONS ABC D EF

HEAD SET TRANSFER

Figure 1 - Reference Configuration

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 2 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 3 of 76

Device Description Versions Tested

Table 1 - Equipment and Software

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 4 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 76

display system-parameters customer-options Page 2 of 10

IP PORT CAPACITIES USED

Maximum Number of DS1 Boards with Echo Cancellation: 0 0

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 6 of 76

Multinational Locations? n Station and Trunk MSP? n

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 76

Default values can be used on Page 2.

Audio Silence Frames Packet

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 8 of 76

On Page 1, set the following fields:

Default values may be used for the remaining pages.

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 76

Edit a row setting the following fields:

( 6 of 6 administered node-names were displayed )

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 10 of 76

Set the following fields:

Default values may be used for the remaining fields.

Near-end Node Name: procr Far-end Node Name: sesabc

Bypass If IP Threshold Exceeded? n

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 76

Numbering Format: public

Replace Unavailable Numbers? n

Show ANSWERED BY on Display? y

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 76

Edit a row setting the following fields:

Dialed Total Call Dialed Total Call Dialed Total Call

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 76

Edit a row setting the following fields:

Matching Insert Node

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 76

Edit a row setting the following fields:

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 15 of 76

Default values can be used for the remaining fields.

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 17 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 18 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 19 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 20 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 21 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 76

Name: A descriptive name (e.g. QE-Routing).

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 24 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 26 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 27 of 76

MDM; Reviewed: Solution & Interoperability Test Lab Application Notes 28 of 76