System Handover Document

Avaya Communication Manager

Submitted By

1
1.1 Overview
A Media Server configuration uses the MES hardware component and a software license to activate a
standby feature. This software allows the media server to communicate with a G450 Media Gateway to be
a call-processing server.

1.2 Hardware and Software Specifications

Linux 2.6.32-504.8.1.el6.AV3.x86_64 x86_64 x86_64

Operating System
CM Software Version Communication Manager R017x.00.0.441.0
Server Type Media Servers
H.248 Gateway Model G450 Media Gateways

Schematic Network Diagram

2
1.3 Network Configurations

Name IP Address IP Subnet

AVP1 Server 1 192.168.250.30 255.225.248.0
AVP2 Server 2 192.168.250.40 255.225.248.0
CM1 192.168.250.33 255.225.248.0
CM2 192.168.250.43 255.225.248.0
CM Alias 192.168.250.50 255.225.248.0
Utility Server 1 192.168.250.31 255.225.248.0
Utility Server 2 192.168.250.41 255.225.248.0
smgr1, smgr1.pk1 192.168.250.34 255.225.248.0
SMGR1 public 192.168.250.38 255.225.248.0
smgr2, smgr2.pk2 192.168.250.44 255.225.248.0
SMGR2 public 192.168.250.48 255.225.248.0
SM1 192.168.250.35 255.225.248.0
SM1-100 192.168.250.39 255.225.248.0
SM2 192.168.250.45 255.225.248.0
SM2-100 192.168.250.49 255.225.248.0
Weblm1 192.168.250.32 255.225.248.0
Weblm2 192.168.250.42 255.225.248.0
AES, aes1.pk2, public 192.168.250.36 255.225.248.0
AES, aes1.pk2, private 192.168.250.37 255.225.248.0
Gateways
IHG1G450 LAN 192.168.250.21 255.225.248.0
IHG2G450 LAN 192.168.250.22 255.225.248.0
IHG3G450 LAN 192.168.250.23 255.225.248.0
IHG4G450 LAN 192.168.250.24 255.225.248.0
IHG5G450 LAN 192.168.250.26 255.225.248.0
IHG6G450 LAN 192.168.250.53 255.225.248.0
IHG7G450 LAN 192.168.250.54 255.225.248.0
Old Gateway G450 172.16.105.22
Old Gateway G450 172.16.105.5

3
1.4 Login Accounts

ACM Login Profiles

Name Login Password

AVP1 Server 1 root P@$$w0Rd
AVP2 Server 2 root P@$$w0Rd
CM1 dadmin dadmin01
CM2 dadmin dadmin01
CM Alias dadmin dadmin01
Utility Server1 admin admin01
Utility Server2 admin admin01
Privilledge admin login for SMGR customer customer01
SMGR1 admin P@$$w0Rd
SMGR2 admin P@$$w0Rd
Smgr user password
WEBLM1 admin weblmadmin01
WEBLM2 admin weblmadmin01
Utility Enrollment pswd P@$$w0Rd
CM usr for SM
Gateways
IHG1G450 LAN root rootroot01
IHG2G450 LAN root rootroot01
IHG3G450 LAN root rootroot01
IHG4G450 LAN root rootroot01
IHG5G450 LAN root rootroot01
IHG6G450 LAN root rootroot01
IHG7G450 LAN root rootroot01
Exiting Gateway password rootROOT1
Gateway new password rootroot01
SNMP V3 user privacy Protocal Password privpassword
SMGR Enrollment password Avaya123
Customer log in cust cust01
cli log in unix pswd Session123$

4
2. Media Server
2.1 Software

Version

5
2.2 License File

6
7
2.3 CM Duplex and Configuration

8
2.3 Media gateways

2.5 Trunk Configuration

2.6 User Configuration

Avaya IP user

 To add new extension

Add station XXXX

 List of COR( Class of Restriction)

9
 1 Out dialing restricted
2 Local
3 Mobile
4 International
 List of COS( Class of Service)

1 for Hotel Rooms

2 for Back office

10
Analog Extension

SIP Extension

This section provides the procedures for configuring Session. Session Manager is comprised of two
functional components: The Session Manager server and the System Manager server. All SIP call
provisioning for Session Manager is performed through the System Manager Web interface and is
then downloaded into Session Manager.

11
This section assumes that Session Manager and System Manager have been installed, and
network connectivity exists between the two platforms.

5.1. Configure User

and provide the following information:

o Last Name – Enter last name of user.

o First Name – Enter first name of user.
o Login Name – Enter extension number@sip domain. The sip domain is defined
as Authoritative Domain in Communication Manager.
o Password – Enter password to be used to log into System Manager.

o Confirm Password – Repeat value entered above.

CRK; Reviewed: SPOC 2/15/2016

Solution & Interoperability Test Lab Application Notes

©2016 Avaya Inc. All Rights Reserved.

6 of 20
Cetis-200-SM70

o Communication Profile Password – Type Communication profile password in this field

12
o Confirm Password – Repeat value entered above.

-section
o Fully Qualified Address – Enter the extension of the user and select a domain name.

o Click the Add button

CRK; Reviewed: SPOC 2/15/2016

Solution & Interoperability Test Lab Application Notes

©2016 Avaya Inc. All Rights Reserved.

7 of 20
Cetis-200-SM70

o Primary Session Manager – Select one of the Session Managers.

o Secondary Session Manager – Select (None) from the drop-down menu.
o Survivability Server – Select (None) from the drop-down menu.
o Origination Sequence – Select Application Sequence defined for
Communication Manager.
o Termination Sequence – Select Application Sequence for Communication
Manager.
13
14
o System – Select Managed Element defined in System Manager.
o Profile Type – Select Endpoint.
o Extension - Enter same extension number used in this section.
o Template – Select template for type of SIP phone
o Security Code – Enter numeric value used to logon to SIP telephone. (Note: this
field must match the value entered for the Shared Communication Profile
Password field.

Click Commit at the bottom of the page.

Tiger Voicemail Configuration

1. Configure Numbering plans Private and Public

Ensure that the extensions used are added to the private and public numbering plans, in order to
add these type change private-numbering x. The screen below shows an Ext Code beginning
with 6 which has a Total Length of 4 is configured to both trunk groups 1 and 9.

change private-numbering 1 Page 1 of 2

NUMBERING - PRIVATE FORMAT

Ext Ext Trk Private Total

Len Code Grp(s) Prefix
Len
4 1 1 4 Total Administered: 3
4 2 1 4 Maximum Entries: 540
4 3 1 4
4 6 1 4
4 6 9 4

Type change public-unknown -numbering x. The screen below shows an Ext Code
beginning with 6 which has a Total Length of 4 is configured to both trunk groups 1
and 9
 2. Configure Dialplan

The dialplan on Communication Manager must be configured as required. Enter the command
change dialplan analysis, the screen below shows that a Dialed String beginning with 4 which
has a Total Length of 4 is configured to go to the UDP table.

3. Configure UDP Table

Enter the command change uniform-dialplan 0, the screen below shows that a Matching
Pattern beginning with 4 with a Length of 4 digits will have 0 digits Deleted and will be passed
to the aar table configured in the Net column.

4. Configure Remote Cover Path

16
A remote coverage path is configured with the pilot number of the InnLine VoIPLink voicemail
server. Enter the command change coverage remote 1 and enter the pilot number in an available
field, in this case 01 is chosen, which is denoted as r1 when referenced in a coverage path.

5. Add Coverage Path

Stations administered with voicemail should be configured with a coverage path which covers the
inbound call to the voicemail pilot number. Enter the command add coverage path next, in Point1
enter the remove coverage path administered in Section 6.4, in this case r1. Take a note of the
Coverage Path Number, in this case 2, this is configured in the station form for stations administered
with voicemail.

7. Configure Stations with Voicemail Coverage Path

Enter the command change station xxxx, where xxxx is an extension configured with
voicemail. Configure the Coverage Path 1 field with the coverage path number

17
6. Configure Avaya Aura® Session Manager
This section describes the steps for configuring the SIP trunk from Session Manager to the InnLine
VoIPLink server. The procedures include the following areas:

6.1. Log into Avaya Aura® System Manager

Access the System Manager using a Web Browser by entering http://<FQDN >/SMGR, where
<FQDN> is the fully qualified domain name of System Manager or http://<IP Adddress >/SMGR.
Log in using appropriate credentials.

Once logged ion click on Routing as highlighted

18
6.2. Administer SIP Domain
Click on Domains in the left window. If there is not a domain already configured, click
on New highlighted below

Enter the name of the domain note this will be referenced in Section 7.1. The Type
should be sip. Click on Commit once done.

6.3. Configure Location

Select Locations from the left window and select New from the main window.

19
Enter a suitable name for the location and scroll down to the bottom of the page
and enter the IP addresses associated with the location in the case there are two
ranges and click on Add. Once completed, click on Commit to continue.

20
6.4. Configure Adaptation
To configure a new Adaptation select Adaptations from the left window and click on
New from the main window.

Enter a suitable Name and select DigitConversionAdapter for the Module Name. Select Name-
Value Parameter as the Module Parameter Type. Add the following Parameters:
Name Value

Continue to add the following Parameters:

Name Value

Click on Commit once completed.

21
6.5. Configure SIP Entity for Tiger InnLine VoIPLink
Select SIP Entities from the left window and click on New in the main window.

Enter a suitable Name and ensure that the Adaptation that was created in Section
6.4 is used. Enter the Location that was configured in Section 6.2 and the correct
Time Zone.

22
6.6. Configure Entity Link for Tiger InnLine VoIPLink
Select Entity Link from the left window and click on New in the main window.

Select the correct SIP Entity that was created in Section 6.5 and ensure that UDP is
used as the Protocol. Note the Port is 5060.

23
6.7. Configure Routing Policy for Tiger InnLine VoIPLink
Select Routing Policies from the left window and click on New in the main window.

Enter a suitable Name and click on Select highlighted in order to associate this
routing policy with a SIP Entity. Select the Tiger SIP Entity created in Section 6.5 (not
shown) and click on Commit when done.

6.8. Configure Dial Pattern for Tiger InnLine VoIPLink

In order to route calls to the InnLine IP, a dial pattern is created pointing to the SIP Entity. Select Dial
Patterns from the left window and click on New in the main window.

24
Enter the number to be routed noting this will be the same number outlined in
Section 5.3. Note the SIP Domain is that configured in Section 6.2. Click on Add to
select the SIP Entity.

Tick on the Originating Location as shown below and select the Tiger Routing Policy.
Click on Select once complete.

25
6.9. Create Dial Pattern for MWI SIP Notify Messages
A dial pattern must be created in order to route the MWI SIP Notify messages to the Communication
Manager SIP Entity. Note the screen shot below highlights the Dial Pattern that was in place during
the compliance testing as all extensions on Communication Manager started with 2. If this is not in
place add the Dial Pattern as described.

2.7Avaya Media Gateway G450

 DSP daughterboard(s)  up to 2
 2 10/100 Base T WAN ports
 2 10/100/1000 Base T LAN ports
 2 USB ports
 Console and Services ports for services and maintenance access
 ETR (Emergency Transfer Relay) port
 Contact closure adjunct port
 Compact Flash Slot

26