Interoperability Application Note for Avaya Aura Session Manager

Interoperability Application Note for Avaya Aura Session Manager
Avaya Solution & Interoperability Test Lab
Interoperability Application Note for Avaya Aura® Session
Manager R6.1 and Avaya Aura® Communication Manager
R6.0.1 with Siemens HiPath 4000 IP Communication
Solution via SIP Trunk connection – Issue 1.0
Abstract
These Application Notes present a sample configuration for Siemens HiPath 4000 to
interoperate with Avaya Aura® Communication Manager and Avaya Aura® Session Manager.
The Siemens HiPath 4000 is an IP based communications solution that also supports
traditional circuit-switched communications. The Avaya Aura® Session Manager links to the
Siemens HiPath 4000 via SIP trunk. The compliance testing focused on basic call and
supplementary call feature support between Siemens and Avaya telephony environments.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
1 of 74
HiPathV5ASM61
Table of Contents
Table of Contents ............................................................................................................................ 2 1. Introduction ............................................................................................................................. 3 2. Equipment and Software Validated ........................................................................................ 4 3. Configure Avaya Aura® Communication Manager ............................................................... 5 3.1. Verify Avaya Aura® Communication Manager License................................................. 6 3.2. Administer System Parameter Features ........................................................................... 7 3.3. Administer IP Node Names.............................................................................................. 7 3.4. Administer IP Network Region and Codec Set ................................................................ 8 3.5. Create SIP Signaling Group and Trunk Group .............................................................. 10 3.6. Administer Route Pattern ............................................................................................... 13 3.7. Administer Private Numbering ...................................................................................... 13 3.8. Administer Locations ..................................................................................................... 14 3.9. Administer Dial Plan and AAR Analysis....................................................................... 14 3.10. Create Stations ............................................................................................................ 15 3.11. Save Changes.............................................................................................................. 16 4. Configure Avaya Aura® Session Manager ........................................................................... 17 4.1. Log in to Avaya Aura® Session Manager ..................................................................... 17 4.2. Administer SIP Domain ................................................................................................. 18 4.3. Administer Locations ..................................................................................................... 19 4.4. Administer Adaptations.................................................................................................. 21 4.5. Administer SIP Entities .................................................................................................. 22 4.6. Administer SIP Entity Link ............................................................................................ 26 4.7. Administer Time Ranges ................................................................................................ 28 4.8. Administer Routing Policy ............................................................................................. 29 4.9. Administer Dial Pattern.................................................................................................. 31 4.10. Administer Avaya Aura® Session Manager ............................................................... 34 4.11. Add Avaya Aura® Communication Manager as an Evolution Server ...................... 35 4.12. Administer SIP Users ................................................................................................. 40 5. Configure the Siemens HiPath 4000 ..................................................................................... 44 5.1. Client PC Preparation ..................................................................................................... 44 5.2. HiPath 4000 System Configuration................................................................................ 51 5.3. HG 3500 Gateway Configuration .................................................................................. 61 6. Verification Steps.................................................................................................................. 67 6.1. Verify Network Connectivity ......................................................................................... 67 6.2. Verify Avaya Phones ..................................................................................................... 68 6.3. Verify Siemens Phones .................................................................................................. 70 6.4. Verify SIP Trunk between Avaya Aura® Session Manager and HiPath SIP Gateway . 70 7. Conclusion ............................................................................................................................ 71 7.1. Issues detected on all Siemens Endpoints. ..................................................................... 71 7.2. Issues detected on Siemens 420S SIP Phone only ......................................................... 72 8. Additional References ........................................................................................................... 73 BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
2 of 74
HiPathV5ASM61
1. Introduction
The purpose of this interoperability Application Notes is to validate Siemens HiPath 4000 with
Avaya Aura® Communication (CM) Evolution Server which are both connected to an Avaya
Aura® Session Manager via a separate SIP trunk. A SIP trunk was configured between Avaya
Aura® System Manager and Siemens HiPath 4000, and specifically a SIP Entity Link between
Avaya Aura® Session Manager and the Siemens HG 3500 SIP Gateway. The Siemens HiPath
4000 Communications Server is the central controlling unit in the Siemens PBX environment.
Both H.323 and SIP gateways are linked to Siemens HiPath 4000 via direct ISDN lines and
LTU1 and LTU2, detailed in the diagram below. Testing was focused on basic calls and
supplementary call feature support between the Avaya and Siemens PBX environments. Testing
endpoints included H.323, SIP and TDM; however fax and EC500 test cases were not included.
Poe Switch VLAN 81
GW X.X.81.254
SIP Trunk to Avaya Aura® Session Manager
SilStack VLAN 199
X.X.9.2
UDP
Siemens HiPath 4000
Communications Server
X.X.81.2
192.168.81.2
TP-C
Avaya POE
Siemens AP 3700
HG 3500 V5
Siemens AP 3700
2 x HG 3500 V5
Avaya Aura®Communication
Manager 6.0 Access Element
Siemens 420S
SIP 810011
X.X.81.12
Avaya Aura® Session Manager
Avaya Aura®System Manager
X.X.81.112
Siemens 410
H323 810103
X.X.81.11
G650
Siemens OS20 S
SIP 810015
X.X.81.20
Avaya one-X
OK
P HONE
CONTA CTS
., @
1
GHI
MENU
AB C
2
JKL
MES S AGE
CA LL LOG
P HONE
CONTA CTS
DEF
., @
3
6
4
WX YZ
PQRS
8
9
7
SP EA KE R
CA LL LOG
DEF
2
GHI
5
T UV
7
MENU
AB C
1
MNO
4
PQRS
3
JKL
MNO
5
6
T UV
WX YZ
8
9
[
*
0
#
MUT E
VOLUME
HEA DS ET
SP EA KE R
*
0
#
MUT E
VOLUME
HEA DS ET
Avaya one-X
OK
MES S AGE
P HONE
CONTA CTS
., @
1
GHI
4
PQRS
7
MENU
AB C
2
JKL
5
T UV
8
CA LL LOG
DEF
3
MNO
6
WX YZ
9
[
Siemens 500s
TDM
810001
SP EA KE R
*
0
#
MUT E
VOLUME
HEA DS ET
Avaya h.323
Ext: 23100
X.X.99.13
Avaya SIP
Ext: 23200
X.X.99.12
Avaya one-X
Avaya TDM
Ext: 2300
OK
MES S AGE
P HONE
CONTA CTS
., @
1
GHI
4
PQRS
7
MENU
AB C
2
JKL
5
T UV
8
CA LL LOG
DEF
3
MNO
6
WX YZ
9
[
Siemens Expression
Voice Server
X.X.81.1
Avaya one-X
OK
MES S AGE
[
6 X 2-Wire conn. to
Siemens Expression
Voice Server
Siemens OS15
TDM
810002
SP EA KE R
*
0
#
MUT E
VOLUME
HEA DS ET
Avaya SIP
(Nortel)
Ext: 23300
X.X.99.34
Figure 1: Network Diagram of the Avaya Aura® Session Manager, Avaya Aura®
Communication Manager and Siemens HiPath 4000 Interoperability
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
3 of 74
HiPathV5ASM61
2. Equipment and Software Validated
The following equipment and software were used for the sample configuration provided.
Equipment
Avaya S8800 Media Server
Avaya S8800 Media Server
Avaya S8800 Media Server
Avaya G650 Media Gateway
Avaya Handset 2420
Avaya Handset 9650
Avaya Handset 9621G
Avaya 1140E (as 9630SIP)
Siemens HiPath 4000
Siemens SIP Gateway HG3500
Siemens SIP RegistrarHG3500
Siemens H.323 Gateway HG3500
Siemens OptiPoint 500
Siemens OpenStage 15T
Siemens OptiPoint 410 Std
Siemens OptiPoint 420Std
Siemens OptiPoint 420 Std S
Siemens OptiPoint OpenStage 20 S
HiPath Expressions Voicemail
BD; Reviewed:
SPOC 07/08/2011
Software
Avaya Aura® Communication Manager R6.0.1
Avaya Aura® System Manager R6.1
6.1.2.0.612004
Avaya Aura® Session Manager R6.1
6.1.2.0.612004R1.1 (1.1.6.0.113002)
TN2312BP HW15FW049
TN2602AP HW08FW049
TN799DP HW01 FW034
(Digital) :Firmware : V6.0
(H323) Firmware:V3.110b
(9620SIP)Firmware: V6.0
(9630SIP) Firmware : V04.00.04.00
Siemens HiPath 4000 V5 R0.5.28
L0-T2R.51.000-004 /
pzksti40.26.000-004
L0-T2R.51.000-004 /
pzksti40.26.000-004
L0-T2R.51.000-004 /
pzksti40.26.000-004
Firmware: MP02.04
Firmware; V1 R0.23.0
Firmware: V5 R6.1.0
Firmware: V5 R6.3.0
Firmware: V7 R5.7.0
Firmware: V2 R1.21.0
V6.01.0.4978
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
4 of 74
HiPathV5ASM61
3. Configure Avaya Aura® Communication Manager
This section provides details on the configuration of Avaya Aura® Communication Manager. All
configurations in this section are administered using the System Access Terminal (SAT). This
section provides the procedures for configuring Communication Manager on the following areas:
 Verify Avaya Aura® Communication Manager License
 Administer System Parameters Features
 Administer IP Node Names
 Administer IP Network Region and Codec Set
 Administer Signaling Group and Trunk Groups
 Administer Route Pattern
 Administer Private Numbering
 Administer Locations
 Administer Dial Plan and AAR Analysis
 Create Stations
 Saves Changes
The following assumptions have been made as part of this document:
 It is assumed that Communication Manager, System Manager and Session Manager have
been installed, configured, licensed. Refer to Section 8 for documentation regarding these
procedures
 Throughout this section, the administration of Communication Manager is performed
using a System Access Terminal (SAT). The commands are entered on the system with
the appropriate administrative permissions. Some administration screens have been
abbreviated for clarity.
 The user has experience of administering the Avaya system via both SAT and Web Based
Management systems.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
5 of 74
HiPathV5ASM61
3.1. Verify Avaya Aura® Communication Manager License
Use the display system-parameter customer options command to compare the Maximum
Administered SIP Trunks field value with the corresponding value in the USED column. The
difference between the two values needs to be greater than or equal to the desired number of
simultaneous SIP trunk connections.
Note: The license file installed on the system controls the maximum features permitted. If there
is insufficient capacity or a required feature is not enabled, contact an authorized Avaya sales
representative to make the appropriate changes.
display system-parameters customer-options
OPTIONAL FEATURES
Page
IP PORT CAPACITIES
Maximum Administered H.323 Trunks:
Maximum Concurrently Registered IP Stations:
Maximum Administered Remote Office Trunks:
Maximum Concurrently Registered Remote Office Stations:
Maximum Concurrently Registered IP eCons:
Max Concur Registered Unauthenticated H.323 Stations:
Maximum Video Capable Stations:
Maximum Video Capable IP Softphones:
Maximum Administered SIP Trunks:
Maximum Administered Ad-hoc Video Conferencing Ports:
Maximum Number of DS1 Boards with Echo Cancellation:
Maximum TN2501 VAL Boards:
Maximum Media Gateway VAL Sources:
Maximum TN2602 Boards with 80 VoIP Channels:
Maximum TN2602 Boards with 320 VoIP Channels:
Maximum Number of Expanded Meet-me Conference Ports:
BD; Reviewed:
SPOC 07/08/2011
12000
18000
12000
18000
414
100
18000
18000
24000
24000
522
128
250
128
128
300
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
2 of
11
USED
0
1
0
0
0
0
0
0
10
0
0
0
0
0
1
0
6 of 74
HiPathV5ASM61
3.2. Administer System Parameter Features
Use the change system-parameters features command to allow for trunk-to-trunk transfers.
This feature is needed to allow for transferring an incoming/outgoing call from /to a remote
switch back out to the same or different switch. For simplicity, the Trunk-to-Trunk Transfer
field was set to all to enable trunk-to-trunk transfer on a system wide basis.
change system-parameters features
Page
FEATURE-RELATED SYSTEM PARAMETERS
Self Station Display Enabled? y
Trunk-to-Trunk Transfer: all
Automatic Callback with Called Party Queuing? n
Automatic Callback - No Answer Timeout Interval (rings): 3
Call Park Timeout Interval (minutes): 10
Off-Premises Tone Detect Timeout Interval (seconds): 20
AAR/ARS Dial Tone Required? y
Music (or Silence) on Transferred Trunk Calls?
DID/Tie/ISDN/SIP Intercept Treatment:
Internal Auto-Answer of Attd-Extended/Transferred Calls:
Automatic Circuit Assurance (ACA) Enabled?
1 of
19
no
attd
transferred
n
3.3. Administer IP Node Names
Use the change node-names-ip command to add entries for Communication Manager and
Session Manager that will be used for connectivity. In the sample network, clan and
192.168.81.104 are entered as Name and IP Address for the CLAN card in Communication
Manager running on the Avaya S8800 Server. In addition, sm100b and 192.168.81.121 are
entered for Session Manager.
change node-names ip
Page
1 of
2
IP NODE NAMES
Name
clan
default
gateway
medpro
procr
procr6
sm100b
BD; Reviewed:
SPOC 07/08/2011
IP Address
192.168.81.104
0.0.0.0
192.168.81.254
192.168.81.105
192.168.81.102
::
192.168.81.121
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
7 of 74
HiPathV5ASM61
3.4. Administer IP Network Region and Codec Set
Use the change ip-network-region n command, where n is the network region number, to
configure the network region being used. In the sample network, ip-network-region 1 is used.
For the Authoritative Domain field, enter the SIP domain name configured for this enterprise
and a descriptive Name for this ip-network-region. Set the Intra-region IP-IP Direct Audio and
Inter-region IP-IP Direct Audio to yes to allow for direct media between endpoints. Set the
Codec Set to 1 to use ip-codec-set 1.
change ip-network-region 1
Page
1 of
20
IP NETWORK REGION
Region: 1
Location: 1
Authoritative Domain: mmsil.local
Name: To ASM61
MEDIA PARAMETERS
Intra-region IP-IP Direct Audio: yes
Codec Set: 1
Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048
IP Audio Hairpinning? y
UDP Port Max: 65535
DIFFSERV/TOS PARAMETERS
Call Control PHB Value: 46
Audio PHB Value: 46
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
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
8 of 74
HiPathV5ASM61
Use the change ip-codec-set n command to configure IP Codec Set paramenters where n is the
IP Codec Set number. In these Application Notes, IP Codec Set 1 was used as the main default
codec set. The standard G.711 codecs and Siemens default G729A codec were selected.
 Audio Codec
Set for G.711MU, G.711A, G729 and G.729A
 Silence Suppression: Retain the default value n
 Frames Per Pkt:
Enter 2
 Packet Size (ms):
Enter 20
Retain the default values for the remaining fields, and submit these changes.
add ip-codec-set 1
Page
1 of
2
IP Codec Set
Codec Set: 1
1:
2:
3:
4:
Audio
Codec
G.711A
G.711MU
G.729
G.729A
BD; Reviewed:
SPOC 07/08/2011
Silence
Suppression
n
n
n
n
Frames
Per Pkt
2
2
2
2
Packet
Size(ms)
20
20
20
20
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
9 of 74
HiPathV5ASM61
3.5. Create SIP Signaling Group and Trunk Group
3.5.1.
SIP Signaling Group
In the test configuration, Communications Manager acts as an Evolution Server. An IMS enabled
SIP trunk is not required. The example uses signal group 150 in conjunction with Trunk Group
150 to reach the Session Manager. Use the add signaling-group n command where n is the
signaling group number being added to the system. Use the values defined in Sections 3.3 and
3.4 for the Near-end Node name, Far-end Node name and Far-end Network Region. The
Far-end Domain is left blank so that the signaling accepts any authoritative domain. Set IMS
enabled to n and Peer Detection Enabled to y. Set Direct IP-IP Audio Connections to y so
trunk “shuffling” is on.
add signaling-group 150
Page
1 of
1
SIGNALING GROUP
Group Number: 150
Group Type: sip
IMS Enabled? n
Transport Method: tcp
Q-SIP? n
IP Video? n
Peer Detection Enabled? y Peer Server: SM
Near-end Node Name: clan
Near-end Listen Port: 5060
SIP Enabled LSP? n
Enforce SIPS URI for SRTP? y
Far-end Node Name: sm100b
Far-end Listen Port: 5060
Far-end Network Region: 1
Far-end Domain:
Incoming Dialog Loopbacks: eliminate
DTMF over IP: rtp-payload
Session Establishment Timer(min): 3
Enable Layer 3 Test? y
H.323 Station Outgoing Direct Media? n
BD; Reviewed:
SPOC 07/08/2011
Bypass If IP Threshold Exceeded?
RFC 3389 Comfort Noise?
Direct IP-IP Audio Connections?
IP Audio Hairpinning?
Initial IP-IP Direct Media?
Alternate Route Timer(sec):
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
n
n
y
n
n
6
10 of 74
HiPathV5ASM61
3.5.2.
SIP Trunk Group
Use the command add trunk-group n to add a corresponding trunk group, where n is the trunk
group number.
 Group Number
Set from the add-trunk-group n command
 Group Type
Set as sip
 COR
Set Class of Restriction (default 1)
 TN
Set Tenant Number (default 1)
 TAC
Choose integer value, usually set the same as the Trunk Group
number
 Group Name
Choose an appropriate name
 Outgoing Display
Set to y
 Service Type
Set to tie
 Signaling Group
Enter the corresponding Signaling group number
 Number of Members
Enter the number of members
add trunk-group 150
Page
1 of
21
TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:
150
sip tg 150
two-way
n
0
tie
Group Type: sip
CDR Reports: y
COR: 1
TN: 1
TAC: 150
Outgoing Display? y
Night Service:
Auth Code? n
Member Assignment Method: auto
Signaling Group: 150
Number of Members: 10
Navigate to Page 3 and set Numbering Format to private.
add trunk-group 150
TRUNK FEATURES
ACA Assignment? n
Page
3 of
21
Measured: none
Maintenance Tests? y
Numbering Format: private
UUI Treatment: service-provider
Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Modify Tandem Calling Number: no
Show ANSWERED BY on Display? y
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
11 of 74
HiPathV5ASM61
Navigate to Page 4 and enter 97 for the Telephone Event Payload Type and P-AssertedIdentity for Identity for Calling Party Display.
display trunk-group 150
Page
4 of
21
PROTOCOL VARIATIONS
Mark Users as Phone?
Prepend '+' to Calling Number?
Send Transferring Party Information?
Network Call Redirection?
Send Diversion Header?
Support Request History?
Telephone Event Payload Type:
Convert 180 to 183 for Early Media?
Always Use re-INVITE for Display Updates?
Identity for Calling Party Display:
Enable Q-SIP?
BD; Reviewed:
SPOC 07/08/2011
n
n
y
n
n
y
97
n
n
P-Asserted-Identity
n
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
12 of 74
HiPathV5ASM61
3.6. Administer Route Pattern
Configure a route pattern to correspond to the newly added SIP trunk group. Use the change
route-pattern n command, where n is the route pattern number specified in Section 3.9.
Configure this route pattern to route calls to trunk group 150, as configured in Section 3.5.2.
Assign the lowest FRL (facility restriction level) to allow all callers to use this route pattern,
Assign 0 to No. Del Digits.
change route-pattern 150
Page
Pattern Number: 150 Pattern Name: To SessMan
SCCAN? n
Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted
No
Mrk Lmt List Del Digits
Dgts
1: 150 0
0
2:
3:
4:
5:
6:
1:
2:
3:
4:
5:
6:
BCC VALUE TSC CA-TSC
0 1 2 M 4 W
Request
ITC BCIE Service/Feature PARM
y
y
y
y
y
y
unre
rest
rest
rest
rest
rest
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
y
n
n
n
n
n
n
n
n
n
n
n
n
1 of
3
DCS/
QSIG
Intw
n
n
n
n
n
n
IXC
user
user
user
user
user
user
No. Numbering LAR
Dgts Format
Subaddress
none
none
none
none
none
none
3.7. Administer Private Numbering
Use the change private-numbering command to define the calling part number to be sent out
through the SIP trunk. In the sample network configuration, all calls originating from a 5 digit
extension beginning with 23 will result in a 5-digit calling number. The calling party number will
be in the SIP “From” header.
change private-numbering 0
Page
1 of
2
NUMBERING - PRIVATE FORMAT
Ext Ext
Len Code
5 23
Trk
Grp(s)
150
Private
Prefix
Total
Len
5
Total Administered: 1
Maximum Entries: 540
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
13 of 74
HiPathV5ASM61
3.8. Administer Locations
Use the change locations command to define the proxy route to use for outgoing calls. In the
sample network, the proxy route will be the trunk group defined in Section 3.5.2.
change locations
Page
1 of
1
LOCATIONS
ARS Prefix 1 Required For 10-Digit NANP Calls? y
Loc Name
No
1: Main
Timezone Rule
Offset
+ 00:00
0
NPA
Proxy Sel
Rte Pat
150
3.9. Administer Dial Plan and AAR Analysis
Configure the dial plan for dialing 6-digit extensions beginning with 81 to stations registered
with the Siemens. Use the change dialplan analysis command to define Dialed String 81 as an
aar Call Type.
display dialplan analysis
Page
DIAL PLAN ANALYSIS TABLE
Location: all
Dialed
String
1
230
231
232
233
81
*
Total Call
Length Type
3
dac
5
ext
5
ext
5
ext
5
ext
6
aar
2
fac
Dialed
String
Total Call
Length Type
1 of
12
Percent Full: 1
Dialed
String
Total Call
Length Type
Use the change aar analysis 0 command to configure an aar entry for Dialed String 81 to use
Route Pattern 150. Add an entry for the SIP phone extensions which begin with 230 or 231.
Use unku for call type.
change aar analysis 0
Page
AAR DIGIT ANALYSIS TABLE
Location: all
Dialed
String
230
231
3
4
5
6
7
81
9
BD; Reviewed:
SPOC 07/08/2011
Total
Min Max
5
5
5
5
7
7
7
7
7
7
7
7
7
7
6
6
7
7
Route
Pattern
150
150
999
999
999
999
999
150
999
Call
Type
unku
unku
aar
aar
aar
aar
aar
unku
aar
1 of
2
Percent Full: 1
Node
Num
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
ANI
Reqd
n
n
n
n
n
n
n
n
n
14 of 74
HiPathV5ASM61
3.10. Create Stations
Create Avaya H.323, SIP and TDM Stations using the command add station n, where n is the
Station extension number.
 Type
Choose phone type e.g. 9620, 9650, 2420
 Name
Choose a suitable name
 Port
Auto assigned for IP Stations, manually set for TDM Stations
 Security Code Set Security Code
Example of Avaya H323 Station.
add station 23100
Page
1 of
5
STATION
Extension:
Type:
Port:
Name:
23100
9650
S00000
AVAYA_H323
Lock Messages? n
Security Code: 1234
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
BCC:
TN:
COR:
COS:
0
1
1
1
STATION OPTIONS
Loss Group: 19
Speakerphone:
Display Language:
Survivable GK Node Name:
Survivable COR:
Survivable Trunk Dest?
2-way
english
Time of Day Lock Table:
Personalized Ringing Pattern:
Message Lamp Ext:
Mute Button Enabled?
Button Modules:
internal
y
Media Complex Ext:
IP SoftPhone?
IP Video?
Short/Prefixed Registration Allowed:
Customizable Labels?
1
23100
y
0
n
n
default
y
Example of Avaya TDM Station.
add station 23000
Page
1 of
5
STATION
Extension:
Type:
Port:
Name:
23000
2420
01A0401
Digital Phone
Lock Messages? n
Security Code: 1234
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
BCC:
TN:
COR:
COS:
0
1
1
1
STATION OPTIONS
Loss Group:
Data Option:
Speakerphone:
Display Language:
2
none
2-way
english
Survivable COR: internal
Survivable Trunk Dest? y
BD; Reviewed:
SPOC 07/08/2011
Time of Day Lock Table:
Personalized Ringing Pattern:
Message Lamp Ext:
Mute Button Enabled?
Expansion Module?
Media Complex Ext:
IP SoftPhone?
Remote Office Phone?
IP Video?
Customizable Labels?
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
1
23000
y
n
n
n
n
y
15 of 74
HiPathV5ASM61
Example of Avaya SIP Station.
add station 23200
Page
1 of
6
STATION
Extension:
Type:
Port:
Name:
23200
9620SIP
S00001
Phone, SIP
Lock Messages? n
Security Code:
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
BCC:
TN:
COR:
COS:
0
1
1
1
STATION OPTIONS
Time of Day Lock Table:
Loss Group: 19
Message Lamp Ext: 23200
Display Language: english
Survivable COR: internal
Survivable Trunk Dest? y
IP SoftPhone? n
IP Video? n
Example of Avaya 1140E SIP Station
add station 23300
Page
1 of
6
STATION
Extension:
Type:
Port:
Name:
23300
9630SIP
S00004
NORTEL Phone
Lock Messages? n
Security Code:
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
BCC:
TN:
COR:
COS:
0
1
1
1
STATION OPTIONS
Time of Day Lock Table:
Loss Group: 19
Display Language: english
Survivable COR: internal
Survivable Trunk Dest? y
Message Lamp Ext: 23300
Button Modules: 0
IP SoftPhone? n
IP Video? n
3.11. Save Changes
Use the save translation command to save all changes.
save translation
SAVE TRANSLATION
Command Completion Status
Success
BD; Reviewed:
SPOC 07/08/2011
Error Code
0
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
16 of 74
HiPathV5ASM61
4. Configure Avaya Aura® Session Manager
This section provides the procedure for configuring Session Manager. For further reference
documents, refer to Section 8 of this document. The procedures include the following areas:
 Login to Avaya Aura® Session Manager
 Administer SIP Domain
 Administer Locations
 Administer Adaptations
 Administer SIP Entities
 Administer Entity Links
 Administer Time Ranges
 Administer Routing Policies
 Administer Dial Patterns
 Administer Avaya Aura® Session Manager
 Add Avaya Aura® Communications Manager as an Evolution Server.
 Administer SIP Users
4.1. Log in to Avaya Aura® Session Manager
Configuration is accomplished by accessing the browser-based GUI of System Manager, using
the URL http://<ip-address>/SMGR where <ip-address> is the IP address of System Manager.
The Home screen is divided into three sections with hyperlinked categories below.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
17 of 74
HiPathV5ASM61
4.2. Administer SIP Domain
SIP domains are created as part of the Avaya Aura ® System Manager (ASM) basic
configuration. There will be at least one which the ASM is the authoritative SIP controller. In
these sample notes it is mmsil.local. The ASM can also deal with traffic from other domains, so
multiple SIP domain entries may be listed.
The location of where you are currently in the system is listed at the top of the screen Underneath
will be listed the domain(s) available in the system.
To create a new SIP Domain, from the Home (first screen available upon successful logon)
select the following; Home  Elements  Routing  Domains  Domain Management
and click New.
 Name
Add a descriptive name,
 Type
Set to SIP
 Notes,
Add a brief description in the Notes field.
Click Commit to save (button not shown).
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
18 of 74
HiPathV5ASM61
4.3. Administer Locations
Session Manager uses the origination location to determine which dial patterns to look at when
routing the call if there are any dial patterns administered for specific locations. Locations are
also used to limit the number of calls coming out of or going into a physical locations. This is
useful for those locations where the network bandwidth is limited. For this sample configuration,
one Location has been created which will reference the both the ASM location and the Siemens
HiPath location. Navigate to Home  Elements  Routing  Locations. To create a new
Location, click New.
In the General section,
 Name Add a descriptive name.
 Notes add a brief description.
Leave the settings for Overall Managed Bandwidth and Pre-Call Bandwidth Parameters, as
default unless advised to do otherwise.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
19 of 74
HiPathV5ASM61
Continue scrolling down the screen until Location Pattern is displayed as shown below. In the
Location Pattern section, under IP Address Pattern enter ip addresses used to logically
identify the location(s). Under Notes add a brief description. Click Commit to save.
In the example above, ip addresses have been entered with a (*) wildcard to indicate a range.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
20 of 74
HiPathV5ASM61
4.4. Administer Adaptations
Adaptations are used to manipulate digits in the SIP URI strings of incoming and outgoing calls.
For this sample configuration, an Adaptation was created for calls to and from the Siemens
HiPath PBX. Any calls from the Siemens HiPath PBX will have the leading digit 6 removed
from the destination SIP URI, before that are routed to destination. Any calls going to Siemens
HiPath PBX, with leading digits 23, will have 6 appended to the start. This was configured to
match dial out from Siemens.
To create new Adaptation, browse to HomeElementsRoutingAdaptations. Click New.
In the General section, under Adaptation Name add a descriptive name. Select the Module
name from the drop down list, DigitConversionAdapter. Add the Digit Conversion as
required, for the incoming and outgoing calls. Click Commit to save.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
21 of 74
HiPathV5ASM61
In the example above, Siemens will dial 6-2XXXX, where 2XXXX is the extension number on
Avaya. Conversely, the identity of the Avaya extension will have 6 inserted in front of its
identity as it dials an extension on the Siemens and this will be presented on the Siemens display.
4.5. Administer SIP Entities
Each SIP device (other than Avaya SIP Phones) that communicates with the ASM requires a SIP
Entity configuration. This section details the steps to create SIP Entities for the Siemens HiPath
SIP Gateway, Session Manager and Communication Manager Evolution Server.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
22 of 74
HiPathV5ASM61
To create a SIP Entity for the Siemens HiPath, browse to Home  Elements  Routing 
SIP Entities and click New.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
23 of 74
HiPathV5ASM61
In the General section,
 Name
 FQDN or IP Address



Type,
Notes
Adaptation,

Location,


Time Zone
SIP Link Monitoring
add a descriptive name
add the IP Address of the target entity (Siemens SIP
Gateway card)
select SIP Trunk
add a brief description
click on the drop down arrow and select SiemensHiPath
(created in Section 4.4)
click on the drop down arrow select SiemensHiPath.
(created in Section 4.3)
Select the appropriate Time Zone
Set to Use Session Manager Configuration
Click Commit to save. A message will appear advising that “Entity Links can be added to the
record once the Entity has been saved”. Section 4.6 advises how to create Entity Links. To create
a SIP Entity for the Session Manager and Communications Manager, repeat the above
process. Screenshots are on the next page showing sample data for creating SIP Entities for
Session Manager and CM Evolution Server.
Screen shot for Session Manager SIP entity. Change the Type to Session Manager when
programming the SIP Entity for Session Manager.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
24 of 74
HiPathV5ASM61
Below is the screenshot for SIP Entity for CM_Evolution Server. Change the Type to CM when
programming the SIP Entity for Communications Manager.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
25 of 74
HiPathV5ASM61
4.6. Administer SIP Entity Link
A SIP Trunk between a Session Manager and a telephony system is described by an Entity Link.
The next step is to create SIP Entity Links, which included the transport parameters to be used
for communications between the ASM and external SIP devices.
Create a SIP Entity Link for Siemens HiPath. Browse to Home  Elements  Routing 
Entity Links. Click New.
 Name
Enter a suitable identifier e.g. SiemensHiPath4K
 SIP Entity 1 Drop-down and select the appropriate Session Manager
 Protocol
Drop down and select UDP
 Port
Enter 5060
 SIP Entity 2 Drop-down select the SIP Entity added previously, i.e. SiemensHipath
 Port
Enter 5060
 Trusted
Set the field as ticked
 Notes
Add a brief description
Click Commit to save.
Note: Some of the parameters are not visible in the screenshot below.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
26 of 74
HiPathV5ASM61
Create a SIP Entity Link for CM_EvolutionServer. Browse to Home  Elements  Routing
Entity Links. Click New.
 Name
Enter a suitable identifier e.g. CM-ES
 SIP Entity 1
Drop-down select the appropriate Session Manager
 Protocol
Dropdown select TCP
 Port
Enter 5060
 SIP Entity 2
Drop-down and select the SIP Entity added previously, i.e.
CM_EvolutionServer
 Port
enter 5060
 Trusted
Tick the field
 Notes
Add a brief description
Click Commit to save (not shown).
Once the Entity Links have been created, return to the SIP Entities and check to see if the Entity
Links have been assigned to the SIP Entities.
Entity Links assigned to SIP Entity Siemens HiPath.
If the Entity Links have not been added to the SIP Entity automatically, click Add and assign the
Entity Link manually.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
27 of 74
HiPathV5ASM61
Entity Links and Ports assigned to SIP Entity CM_EvolutionServer.
Entity Links and Ports assigned to SIP Entity Session Manager.
4.7. Administer Time Ranges
Create a Time Range for LCR routing which defines policies will be active. To create a Time
Range, browse to Home  Elements  Routing  Time Ranges. Click New. Under Name
enter a suitable identified. Select which Days are to be included in the Range. Set a suitable
Start Time and End Time. This will be used in configuring the Dial Plan. In Session Manager,
a default policy (24/7) is available that would allow routing to occur anytime. This was used in
the example network.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
28 of 74
HiPathV5ASM61
4.8. Administer Routing Policy
To complete the routing configuration, a Routing Policy is created. Routing policies direct how
calls will be routed to a system. Two routing policies must be created, one for the
Communications Manager and the second for the Siemens HiPath 4000. These are to be
associated with the Dial Patterns which will be created in the next step. To create a Routing
Policy to route traffic to Siemens HiPath, browse to Home  Elements  Routing  Routing
Polices. Click New. Under Name enter a suitable identifier. Under Notes enter suitable
description. Under SIP Entity as Destination click on Select. Choose the appropriate SIP Entity
that is to be the call destination. Under Time of Day, assign a suitable time range if more than
one is programmed, click on Add. Click Commit to save.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
29 of 74
HiPathV5ASM61
A Routing Policy is also created for the CM_Evolution Server.
At this stage the records are missing the Dial Pattern which will be created next.(Section 4.9).
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
30 of 74
HiPathV5ASM61
4.9. Administer Dial Pattern
As one of its main functions, ASM routes SIP traffic between connected devices. Dial Patterns
are created as part of the configuration to mange SIP traffic routing, which will direct calls based
on the number dialed to the appropriate system. In the sample network, 5 digit extensions
beginning 230 or 231 are designated as Avaya handsets (Digital and H.323), whilst 6 digit
extension starting 81 are Siemens handsets. To create a Dial Pattern for calls to the Siemens
HiPath, browse to Home  Elements  Routing  Dial Patterns. Click New. Under Pattern
enter a dial string pattern e.g. 81xxxx. (all calls with 6 digit ext beginning with 81 will be routed
to Siemens HiPath). Under SIP Domains drop-down select All. Under Notes enter a suitable
description.
To add the Originating Locations and Routing Polices, previously created, click Add.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
31 of 74
HiPathV5ASM61
In the Originating Location section (created in Section 4.3), select Apply the Selected
Routing Policies to All Originating Locations. In the Routing Policies (created in Section
4.8), select the Routing Policy to be applied. Click Commit to save.
Dial Patterns should also be created for the Avaya Digital and H.323 handsets. Screenshots for
these are on the next page.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
32 of 74
HiPathV5ASM61
Dial Patterns should also be entered for Avaya extensions beginning 230 (Digital) and 231
(H.323) and set the Originating Location and Routing Polices, choosing the relevant Routing
Policy for the CM_Evolution Server.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
33 of 74
HiPathV5ASM61
4.10. Administer Avaya Aura® Session Manager
To complete the configuration, adding the Session Manager will provide the linkage between the
System Manager and Session Manager. On the System Manager management screen, under
Elements select Session Manager or from the Home screen, browse to Home  Elements 
Session Manager Session Manager Administration. On the right hand side, under Session
Manager Instances, click on New.
Under General:
 SIP Entity name
Select the names of the SIP entity added for Session Manager
 Description
Descriptive Comment
 Management Access Point Host Name/IP
Enter the IP address of the Session Manager management
interface
Under Security Module
 Network Mask
Enter the network mask corresponding to the IP address of the
Session Manager
 Default Gateway
Enter the IP address of the default gateway for Session Manager.
Use default values for the remaining fields.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
34 of 74
HiPathV5ASM61
4.11. Add Avaya Aura® Communication Manager as an Evolution
Server
In order for Communication Manager to provide configuration and Evolution Server support to
SIP Phones when they register to Session Manager, Communication Manager must be added as
an application.
4.11.1.
Create a Avaya Aura® Communication Manager Instance
On the System Manager Managements screen under Elements, select Inventory. Alternatively,
browse to Home  Elements  Inventory  Manage Elements. Click New. Click on the
Application Tab and enter detail in the following fields.
 Name
Enter a Descriptive Name
 Type
Set to CM
 Description Free text entry
 Node
Set to IP Address for CM SAT Access
All other fields may be left with default settings.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
35 of 74
HiPathV5ASM61
Click on the Attributes Tab and enter detail in the following fields.
 Login
Login used for SAT access
 Password
Password used for SAT access
 Confirm Password Password used for SAT access
 Node
Set to IP Address for CM SAT Access
All other fields may be left with default settings.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
36 of 74
HiPathV5ASM61
4.11.2.
Create an Evolution Server Application
For Evolution Server support, further configuration of the Session Manager is required. Once
complete the Session Manager will support Avaya SIP phone registration. Users are created
through the Session Manager User Management screens. Session Manager creates
corresponding stations on the Evolution Server. Configuration of the Evolution Server
Application via Session Manager is a two stage sequence, with the Application being created
first, followed by the Application Sequence. To configure browse to: Home  Elements 
Session Manager  Application Configuration  Applications. Click New. Under Name
enter a suitable identifier. Under SIP Entity drop-down select the SIP Entity of the Feature
Server. Under Description enter a suitable description. Click Commit to save.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
37 of 74
HiPathV5ASM61
To configure the Application Sequences Configuration. Browse to: Home  -Elements  Session Manager  Application Configuration  Applications Sequences. Click New.
Under Name enter a suitable identifier. Under Description enter a suitable description. From the
Available Applications section, select the + sign beside the Application that is to be added to
this sequence. Verify that the Application in this Sequence is updated correctly Click Commit
to save.
At this point the configuration of ASM is complete. To add users for Avaya SIP endpoints refer
to Section 8 Reference [1].
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
38 of 74
HiPathV5ASM61
4.11.3.
Synchronize Avaya Aura® Communication Manager Data
On the System Manager management screen under Elements, select Inventory or browse to
Home  ElementsInventory Synchronization  Communication System. Select the
appropriate Element Name and the select Initialize data for selected devices. Then click on
Now.
Note: This Process can take some time.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
39 of 74
HiPathV5ASM61
4.12. Administer SIP Users
SIP Users must be added via Session Manager and the details will be updated on Communication
Manager. On the System Manager management screen under the Users Column, select User
Management or browse to Home  Users  User Management  Manage Users. Click
New. On the Identity tab enter the following information and use defaults for other fields.
 Last Name
Enter a last name
 First Name
Enter a first name
 Login Name
Enter the desired phone extension@domain.com where the domain was
defined in Section 4.2
 Password
Password for the user to log into System Manager (SMGR)
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
40 of 74
HiPathV5ASM61
Next click on the Communication Profile tab.
 Last Name
a desired last name
 First Name
a desired first name
 Login Name
the desired phone extension@domain.com where the domain
was defined in Section 4.2
 Password
Password for the user to log into System Manager (SMGR)
 Communication Profile Password
Password entered by user when logging into a phone
 Confirm Password
Repeat of the above password
Expand Communication Address and click New.
 Type
Set to Avaya SIP
 Fully Qualified Address Enter the extension number and set the Domain.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
41 of 74
HiPathV5ASM61
Next, navigate down the screen to Session Manage Profile and Endpoint Profile.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
42 of 74
HiPathV5ASM61
Select the appropriate Session Manager server for Primary Session Manager. For Origination
Application Sequence select the Application Sequence created in Section 4.11.3. Choose Home
Location created in Section 4.3.Click on Endpoint Profile to expand that section. Enter the
following fields and use defaults for the remaining fields.
 System
Select the CM Entity
 Extension
Enter a desired extension number
 Template
Select a telephone type template
 Port
Select IP
Click on Commit to save changes.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
43 of 74
HiPathV5ASM61
5. Configure the Siemens HiPath 4000
The Siemens HiPath configuration was verified using the web interface HiPath 4000 Assistant
V5. Before the web interface can be used, the Client PC must be prepared. To access the web
interface use internet explorer http://IPAddress_of_HiPath/.
5.1. Client PC Preparation
To access the HiPath 4000 Assistant via internet browser, the user must prepare the client
machine. Click on Client Preparation.
The following page is displayed, listing the steps to prepare the Client PC. Click on Next.
Click Next.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
44 of 74
HiPathV5ASM61
If an error is displayed for the version of Internet Browser detected, follow the steps listed under
Installation to install a correct level of Browser. Otherwise click on Next.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
45 of 74
HiPathV5ASM61
Verify that the Client PC has a suitable version of Java Runtime Environment Plug-in. In the
image below, a warning is displayed. Although you can ignore this warning if you have a newer
version of Java, should you experience problems with loading HiPath Assistant screens, please
return to this preparation process and install a recommended version of Java, having first
uninstalled any previous versions of Java, Java Plug-in v1.6.0_17 works fine. Click Next.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
46 of 74
HiPathV5ASM61
Verify Siemens I&C Security CA Certificate. If an error message is displayed, click on
Installation to install the Security Certificate. Click Next.
Notes: It is strongly recommended that you close Internet Explorer and re-open it after certificate
installation.
The next three screens are information level notices. Click Next to proceed.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
47 of 74
HiPathV5ASM61
Click Next.
Click Next.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
48 of 74
HiPathV5ASM61
The Client PC will be prompted to install InstACM.exe. This is an Applet Cache Manager plugin which is required to run HiPath 4000 Assistant web interface. Click on Run.
The browser may need to be restarted, proceed to step 6 of the web installation. Verify that the
Applet Cache Manager is installed. Click on Next.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
49 of 74
HiPathV5ASM61
Client Preparation finished. Click Logon.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
50 of 74
HiPathV5ASM61
5.2. HiPath 4000 System Configuration
Once the Client PC is prepared, access to the administration applications is available. Return to
the main login page. Click on the HiPath admin link, listed as the IP Address of the HiPath
server.
Log in to the portal using the engineering logon. (Refer to the Siemens installation engineer for
client access details).
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
51 of 74
HiPathV5ASM61
5.2.1.
Network Domain Configuration
The HiPath Assistant portal will be displayed as a tree structure on the left. Once a final option is
selected on the left, the screen will either open in new window or open on the right hand side of
the screen. To check/edit the Network Domain Configuration. Expand Configuration
Management  Network  Domain.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
52 of 74
HiPathV5ASM61
Click on the Search button to access the current configuration. This returns all programmed
records up to a limit of 1000.
The domain name is entered in the Domain field. The associated system name is listed under the
Systems tab.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
53 of 74
HiPathV5ASM61
5.2.2.
System Configuration
To check/edit the System Configuration which contains details of the version number, upload
the system number of the HiPath 4000. Expand Configuration Management  Network 
System. Wait for the System screen to display on the right hand side or in a new window.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
54 of 74
HiPathV5ASM61
Leaving all fields empty, click on the Search button to access the current configuration (button
not shown). This will return all records found in the system up to a limit of 1000 records.
Alternatively click the down arrow beside the field system to choose from a list of items. Select
the System name as recorded from the previous step and click Search. One or more fields may
be selected as Search criteria.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
55 of 74
HiPathV5ASM61
The HiPath 4000 Communication Server uses ISDN cable connection to the cabinets containing
the Siemens HG3500 IP gateways. The IP Gateways also communicate via IP network across
the LAN. This sample configuration includes a SIP Trunk Gateway (X.X.81.6), a SIP Gateway
(X.X.81.3) and a H.323 Gateway (X.X.81.4). The Gateways are collectively described by
Siemens as HG3500 or HG35XX boards and are universal card. It is during configuration of
these cards that the role is defined as to whether the board is SIP or H.323. To access the
configuration of the HG3500, expand Configuration Management  System Data  Board
 Board. Wait for the Config screen to display. Click on Search to access the current
configuration.
Each Board has a specific location code, indicated by LTG (Line Trunk Group), LTU (Line
Trunk Unit), and SLOT (Physical position with LTU where card has been inserted). In the image
below, the code is 1-1-4. This is the SIP Trunk Gateway. The board location code is important to
know when creating Stations for telephony endpoints.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
56 of 74
HiPathV5ASM61
The board list for this sample configuration are:
Board Location IP Address
/ PEN
1-1-1
X.X.81.3
1-1-4
1-1-2
1-2-1
1-2-13
1-2-2
1-1-14
1-1
1-2
5.2.3.
X.X.81.6
NA
X.X.81.4
NA
NA
NA
NA
NA
Function
SIP Gateway Phone Reg
[Siemens 420 SIP Phones]
SIP GW SIP Trunks
TDM Interface [Siemens 500 Digital Phones]
H.323 GW [Siemens 410 H.323 Phones]
8 Ch. Voice Card. Interface to Siemens Expressions Server
24 Port Analog [Fax]
Q-Sig
LTU1 ISDN Admin Link
LTU2 ISDN Admin Link
Siemens Station End-Points
The Siemens Stations can be managed from the HiPath Assistant. To check/edit the Stations,
expand Configuration Management  Station  Station. Wait for the config screen to
display. Click on Search to access the current configuration.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
57 of 74
HiPathV5ASM61
The image below illustrates the configuration of a TDM Station:
 Station No.
Selected from drop down list
 PEN.
Must match the Card location described in previous section. (1-12 is the TDM Interface Card)
 Device Combination. Select from Drop down list
 Device Family.
Selected from Drop down list
 Connection Type
Direct (TDM), IP2 (H.323) SIPSEC (SIP)
 Display Name.
Enter a suitable display name
 COS and LCRCOS. Class of Service must be assigned. Default shown
 Way to Display.
Set to yes to display Caller Name and ID
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
58 of 74
HiPathV5ASM61
The image below illustrates the configuration of a SIP Station Endpoint.
 Station No.
Selected from drop down list
 PEN.
Must match the Card location described in previous section (11-1 is the SIP Registrar Interface Card)
 Device Combination. Select from Drop down list
 Device Family.
Selected from Drop down list
 Display Name.
Enter a suitable display name
 COS and LCRCOS.
Class of Service must be assigned. Default shown
 Way to Display.
Set to yes to display Caller Name and ID
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
59 of 74
HiPathV5ASM61
The image below illustrates the configuration of a H.323 Station Endpoint.
 Station No.
Selected from drop down list
 PEN.
Must match the Card location described in previous section. (12-1 is the H.323 GW Interface Card)
 Device Combination. Select from Drop down list
 Device Family.
Selected from Drop down list
 Display Name.
Enter a suitable display name
 COS and LCRCOS.
Class of Service must be assigned. Default shown
 Way to Display.
Set to yes to display Caller Name and ID
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
60 of 74
HiPathV5ASM61
5.3. HG 3500 Gateway Configuration
To access the configuration of the HG3500 Gateway, use the Web Console interface
https://IPAddress-Of-HGGW/ and Login screen will appear.
Alternatively the configuration of a card may be reached via HiPath Assistant by accessing
Expert ModeHG35XX Web Based Management.
Once you have selected this screen, a pop up window will appear offering a list of boards
accessible via this method.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
61 of 74
HiPathV5ASM61
Click on the connect link of the board you wish to review. On initial load of the screens, Java is
used and can take some time before the screens are available to use. Main menus of use are:
 Explorers
Offers access to configure SIP parameters
 Save
Save any changes made to the board via these screens
 Reset
Some changes require the board to be restarted
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
62 of 74
HiPathV5ASM61
5.3.1.
SIP Trunk Gateway
The image below shows the SIP Trunk Gateway configuration, listing the SIP Parameters used
in these sample notes. Select Explorers  Voice Gateway  SIP Parameters. To edit any of
these settings, right click on SIP Parameters and choose Edit SIP Parameters. Not all fields
are configurable. Only the following fields are configurable via these screens:Section
SIP Server (Registrar / Redirect)
RFC 3261 Timer Values
SIP Transport Protocol
SIP Session Timer
SIP Session Timer
SIP Session Timer
DNS-SRV Records
Outgoing Call Supervision
BD; Reviewed:
SPOC 07/08/2011
Field Name
Period of registration (sec):
Transaction Timeout (msec):
SIP via UDP:
RFC 4028 support:
Session Expires (sec):
Minimal SE (sec):
Blocking time for
unreachable destination(sec):
MakeCallReq Timeout (sec):
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
63 of 74
HiPathV5ASM61
The image below shows the SIP Trunk Profile configuration created for Avaya. Select
Explorers  Voice Gateway  SIP Trunk Profiles  Avaya. Under the section Proxy,
verify that the SM100 card IP address is entered. To edit the settings, right click the folder and
select edit. Make the necessary changes and click the Apply button at the bottom of the screen
(not shown). Click the SAVE disk icon if it goes Red. The SIP Trunk Profile must then be
activated, as shown in the image below. To activate a SIP Trunk Profile, right click on the profile
and choose Activate (not shown). The folder will then go Green to indicate it is the active Trunk
Profile.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
64 of 74
HiPathV5ASM61
5.3.1.1 SIP Registrar Gateway
This is the card used by the handsets when they register. The image below shows the SIP Trunk
Gateway configuration, listing the SIP Parameters used in these sample notes. Select Explorer
 Voice Gateway  SIP Parameters.
To view registered SIP clients, select Explorers  Voice Gateway  Clients  SIP.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
65 of 74
HiPathV5ASM61
5.3.1.2 H.323 Gateway
The image below shows the H.323 GW configuration listing the H.323 Parameters used in
these sample notes. Select Explorers  Voice Gateway  H.323 Parameters.
To view registered H.323 clients, select Explorers  Voice Gateway  Clients  HFA.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
66 of 74
HiPathV5ASM61
6. Verification Steps
This section provides details on how to verify network connectivity, the main configuration setup of Avaya and Siemens phone endpoints and also the SIP Trunk between Avaya and Siemens
PBX environments.
6.1. Verify Network Connectivity
The HiPath 4000 Communications Server is the central controlling unit in the Siemens PBX setup. Connection to the HG3500 gateway chassis is via ISDN link. Check the ISDN link light on
the front panel of the HG3500 chassis to verify that it displays “green” link light. Connection to
the HG3500 IP gateways is via LAN. Verify that the link light on the front of the cards for the
LAN1 connection is a “bright green”. (Screen shot below shows lights on for LAN1, but lights
off for LAN2 as it is not in use.) Using a PC on the same network, verify ping tests to the SIP
Trunk GW, the H.323 GW and the SIP Registrar GW. Each of the Siemens gateways can be
accessed via web browser. Use the Front Panel tab to view link status and line status. The image
below shows the Front Panel status for the SIP Trunk gateway. LAN link status is displayed on
the bottom left. Channel status is listed on the right, in this example a single call from Siemens
to Avaya is active, indicated by the green indicator.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
67 of 74
HiPathV5ASM61
6.2. Verify Avaya Phones
List the Station configuration on the Access Element. In these sample notes, there are two
stations configured on the Access Element, Avaya H.323 and Avaya TDM.
list station
STATIONS
Ext/
Cable/
Hunt-to
Jack
Port/
23000
01A0401 Digital Phone
2420
S00000 AVAYA_H323
9650
S00001 Phone, SIP
9620SIP
S00004 NORTEL Phone
9630SIP
S00002 phone, nortel2
9630SIP
23100
23200
23300
23301
Type
Name/
Room/
Surv GK NN
Move
Data Ext
no
no
no
no
no
Cv1/ COR/
Cv2
COS TN
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
List the registered IP stations using the command list registered-ip-stations. The Avaya H.323
station will be listing here.
list registered-ip-stations
REGISTERED IP STATIONS
Station Ext
or Orig Port
------------23100
BD; Reviewed:
SPOC 07/08/2011
Set Type/ Prod ID/
TCP Station IP Address/
Net Rgn
Release
Skt Gatekeeper IP Address
--------- ---------- --- -------------------------------------9650
1
IP_Phone
3.110b
y
10.10.99.13
192.168.81.104
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
68 of 74
HiPathV5ASM61
The Avaya SIP station configuration is created on the Session Manager, which is then pushed
down to the Feature Server. The station will not show up on list registered-ip-stations.
Therefore a simple test call to another Avaya Station was carried out to very connectivity.
The parent configuration for station 34008 was created on the Session Manager. To verify,
browse to Home Users  User Management  Manage Users User Management.
Verify that the user is displayed with the correct User Name and Handle.
Carry out a simple test calls between the various Avaya Stations, and verify connection and
duplex audio path.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
69 of 74
HiPathV5ASM61
6.3. Verify Siemens Phones
To verify the Siemens SIP phone registration status, see Section 5.3.1.1. SIP Registrar
Gateway. To verify the Siemens H.323 phone registration status, see Section 5.3.1.2 H.323
Gateway. Carry out a simple test calls between the various Siemens stations, and verify
connection and duplex audio path.
6.4. Verify SIP Trunk between Avaya Aura® Session Manager and
HiPath SIP Gateway
Use the Session Manager SIP Entity Monitor to verify that SIP Trunk between SM and Siemens
HiPath SIP GW. Browse to Home  Elements  Session Manager System Status  SIP
Entity Monitoring. From the list of All Monitored SIP Entities (not shown), select the
SiemensHiPath entity link. Verify that Conn-Status is Up.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
70 of 74
HiPathV5ASM61
7. Conclusion
The interoperability between Siemens HiPath 4000 V5 with an IP Communications Solution and
Avaya Aura® Communication Manager with Avaya Aura® Session Manager did function.
However some issues were detected.
7.1. Issues detected on all Siemens Endpoints.
This section provides details on the issues detected during interoperability testing, which were
general to the Siemens Phone models 410s, 420s and 500 and OpenStage SIP.
7.1.1.
IP Shuffling
Intermittently one-way audio experienced when a call is put on hold from either Avaya or
Siemens devices. When the Siemens handsets (H.323 or SIP) dialed the Avaya H.323 handset
the connection would only be made between Siemens HiPath and the Avaya Media Processor
card, not using IP Shuffle. In this event the audio would function correctly until either end put
the call on hold. On retrieving the call, one way Audio would be experienced between Siemens
to Avaya, but not between Avaya to Siemens.
7.1.2.
Cross PBX transfer using Unattended or Attended Transfer
Caller Name/ID not updated on Siemens endpoint when transfer is completed by the Avaya
endpoint. When the transfer complete step is carried out, the caller display on the Siemens
endpoint retains the initial Caller Name/ID instead of updated to the “transfer-to” Caller
Name/ID.
7.1.3.
Cross PBX transfer using Unattended or Attended Transfer Fails
Transfer request is from Avaya to Siemens endpoint which then attempts to transfer the call back
to an Avaya endpoint, the feature fails consistently. The issue occurs when the Siemens endpoint
attempt an un-attended or attended transfer. Each of the endpoints reports error message:
 Siemens 410s H323 IP Phone “Not Possible”,
 Siemens 420s SIP IP Phone “488 Not Acceptable Here”,
 Siemens 500s TDM Phone “Not Possible”.
7.1.4.
Siemens SIP Devices using Call Forward Busy
When attempting to dial a Siemens SIP device which has Call Forward Busy programmed and
the device is busy, the caller receives a busy signal, rather than follow the forward busy setting.
Under tracing conditions, a busy signal is issued by the Siemens device and can be traced in
Wireshark as SIP Status Message 486 Busy Here. The tests for Call Forward No Answer and
Always were successful and the calls were forwarded to the forwarding destination successfully,
both Avaya handset and Siemens Device.
7.1.5.
Call forwarding fails when the forwarded call is picked up
Call Forwarding Always is configured on the Avaya endpoint to either Siemens or Avaya
destination. When the Siemens device rings the Avaya handset, the call is forwarded, however
call completion fails when the line is picked up at the “forwarded-to endpoint”.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
71 of 74
HiPathV5ASM61
A BYE sent from the SIP Gateway to Avaya Aura® Session Manager contains a message
“Resource unavailable, unspecified”. The Call Forward No Answer/Reply and Call Forward
Busy programmed on the Avaya device work successfully.
7.2. Issues detected on Siemens 420S SIP Phone only
This section provides details on the issues detected during interoperability testing, which are
isolated to the Siemens phone model 420S (SIP).
7.2.1.
Call Hold / Reconnect Fail on Siemens 420s SIP phone
This issue is isolated to the Siemens HiPath 420s SIP Phone. Independent of where the call is
from Avaya or Siemens. When the 420s SIP user selects “Reconnect” on a line that is in a
“Hold” state the reconnect fails to work. Wire shark trace from Siemens SIP Phone indicates 488
“Not Acceptable Here” response from SIP Gateway to Siemens SIP Endpoint, after attempting
to retrieve the call. Call is cleared. SIP Signaling and SIP Call Control logs were captured from
the Siemens 420s SIP Phone. Log message “state = ccCallHoldFeatureRejected, reason =
Unreachable : 1195” is generated. The line is then cleared.
Workaround: This issue can be resolved with the programming of a Line key on the handset,
either via accessing the Web Based Management tool for the handset, or via the Siemens DLS
(Deployment Server) Software, which may have been installed for SIP phone management. This
key allows a held call to be retrieved by the user.
7.2.2.
Blind Transfer Fail on Siemens 420s SIP Phone
The 420S SIP user selects Blind Transfer, a valid phone number of another Siemens endpoint
was entered, and Dial was selected. The attempted dial fails, Reconnect option is displayed. The
420s SIP user select Reconnect, this also fails and the line is cleared. Wire shark trace from
Siemens SIP Phone. Notify message from the SIP registration Gateway shows SIP error code
503 “Service Unavailable”. SIP Signaling and SIP Call Control logs were captured from the
Siemens 420s SIP Phone. Log message “ccFeatureFailed, feature = ccTransfer, reason =
Transfer_Rejected”. No suitable workaround has been found to resolve the issue.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
72 of 74
HiPathV5ASM61
8. Additional References
Product Documentation for Avaya Products may be found at http://support.avaya.com
[1] Administering Avaya Aura®™ Communication Manager 03-300509 Release 6.0 Issue
6.0
[2] Administering Avaya Aura® Communication Manager Server Options 03-603479
Release 6.0.1, Issue 2.2
[3] Administering Avaya Aura® Session Manager 03-603324 Release 6.1 Issue 1.0
[4] Maintaining and Troubleshooting Avaya Aura® Session Manager 03-603325 Release
6.1 Issue 4.1
Product Documentation for Siemens Products may be found the following websites and service
manuals.
[5]
[6]
[7]
[8]
Siemens Wiki Website http://wiki.siemens-enterprise.com/index.php/Main_Page
Siemens eTAC (a support website with limited information available to customer/end
user) [7] http://siemenstac.custhelp.com/app/home
HiPath 4000 V5 IP Solutions, SIP Connectivity Service Documentation ref: A31003H3150-S104-2-7620 Dec 2008.
Other Service Documentation may be obtained via your Service Suuport Provider or
Account Manager within Siemens Enterprise Communications.
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
73 of 74
HiPathV5ASM61
©2011 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
BD; Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
74 of 74
HiPathV5ASM61
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising