Académique Documents
Professionnel Documents
Culture Documents
R3.0
102.1.6 AS 5300 3.0 Avaya Media Server
Installation and Commissioning
Method of Procedure
Product Release:
AS 5300 R3.0
Document Version:
1.4
Document Status:
Released
Security Classification:
Avaya Confidential
Revision History
Version
Date
Description
1.0
November 2011
Approved.
1.1
January, 2012
wi00971894
1.2
1.3
February 22,
2012
1.4
Table of Contents
1 Start Here ................................................................................................................ 7
2 Overview ................................................................................................................. 8
2.1
Document Conventions................................................................................................ 8
2.2
5 Planning ................................................................................................................12
6 Avaya Media Server Platform Installation ........................................................14
6.1
6.2
7.2
Uninstalling Adhoc............................................................................................ 57
17.1.2
17.1.3
17.1.4
17.1.5
17.1.6
18 References ............................................................................................................60
List of Figures
Figure 1 IPv4 Addresses ......................................................................................................... 18
Figure 2 IPv4 Addresses configuration .................................................................................. 19
Figure 3 Servers ...................................................................................................................... 19
Figure 4 Add Server ................................................................................................................ 20
Figure 5 Media Servers ........................................................................................................... 20
Figure 6 Add Media Server ..................................................................................................... 21
Figure 7 Media Server Instance .............................................................................................. 22
Figure 8 Edit Media Server Instance....................................................................................... 22
Figure 9 Launch AS 5300 Element Manager Console ................................................................ 23
Figure 10 Log in to AS 5300 Element Manager Console ............................................................ 23
Figure 11 Licensing Configuration ............................................................................................ 24
Figure 12 Avaya Media Server cluster ....................................................................................... 25
Figure 13 Replication Account Settings ..................................................................................... 26
Figure 14 SIP Routes Settings. .................................................................................................. 28
Figure 15 Enable AS5300 Avaya Media Server applications ...................................................... 30
Figure 16 Deploy and start Avaya Media Server NE .................................................................. 32
Figure 17 Select Logical Entity .................................................................................................. 34
Figure 18 Add Service Node ..................................................................................................... 34
Figure 19 Add Logical Entity ..................................................................................................... 36
Figure 20 Select Music On Hold ................................................................................................ 39
Figure 21 Media management ................................................................................................... 39
Figure 22 Upload media file ....................................................................................................... 40
Figure 23 Select Branding ......................................................................................................... 41
Figure 24 Create media file ....................................................................................................... 42
Figure 25 Assign Branding media file......................................................................................... 42
Figure 26 Select Treatment ....................................................................................................... 44
Figure 27 Add media file............................................................................................................ 45
1 Start Here
To immediately start executing the procedures described in this document,
proceed to Section 3 "Work Flow".
To first gain contextual information regarding this document, first read Section 2
"Overview", then proceed to Section 3 "Work Flow".
2 Overview
2.1 Document Conventions
The following conventions are used throughout this document.
References to sections in this document are typically of the form:
Section <number> (For example: Section 1)
where "<number>" is the number of the section. In document text where a
more complete reference facilitates the flow (such as an initial reference in an
overview section), the following form is used:
Section <number> "<name>" (For example: Section 1 "Start Here"")
where "<name>" is the name of the section.
References to documents listed in Section 18, "References" are typically of
the form:
[<number>] (For example: [1])
where "<number>" is the number of the reference from Section 0. In
document text where a more complete reference facilitates the flow (such as
an initial reference in an overview section), the following form is used:
[<number>] "<title>"
(For example: [1] 102.1.1. AS 5300 Server Installation)
where "<title>" is the title of the referenced document.
In-line text describing output displayed on a login window, console, or
graphical user interface, appears as follows: Example in-line output
text.
In-line text describing data entered into the terminal or console window, or
graphical user interface, appears as follows: Example in-line input text.
Paragraph text describing output displayed on a login window, console, or
graphical user interface, appears as follows:
Example paragraph output text
Paragraph text describing data entered into a terminal or console window, or
graphical user interface, appears as follows:
Example paragraph input text
March 20, 2012
3 Work Flow
This section provides the work flow to accomplish the installation of Avaya
Media Server in AS 5300 3.0 system. Each step in this procedure refers to a
section which provides the specific work instructions to accomplish that task. A
given step must be successfully completed prior to starting the next step.
1. Execute Section 4 Verify Prerequisites
2. Execute Section 5 Planning
3. Execute Section 6 Avaya Media Server Platform Installation
4. Execute Section 7 Avaya Media Server Application Installation
5. Execute Section 8 Configure additional Avaya Media Servers
6. Execute Section 9 Licensing Configuration
7. Execute Section 10 Configuring Avaya Media Server Clustering
8. Execute Section 11 Configure SIP routes for Avaya Media Server
Cluster
9. Execute Section 12 Enable AS 5300 Avaya Media Server applications
installed
10. Execute Section 13 Avaya Media Server maintenance
11. Execute Section 14 Provisioning Avaya Media Server Routing
10
4 Verify Prerequisites
Prior to the execution of the procedures described in the remainder of this
document, it is assumed that all of the prerequisites described in this section have
been met.
The following media must be available:
AS 5300 3.0 Linux platform
Avaya Media Server Platform installers
Avaya Media Server Application installers
Customer supplied music to be used for Music on Hold
Announcements to be used for Branding
Announcements to be used for Treatments, such as declined call.
The 102.3.6 AS 5300 3.0 Avaya Media Server Installation and Commissioning
Job Aid is to be filled in.
The domain data with some users is provisioned into the system so that Avaya
Media Server services can be verified.
Make sure that the new license keys are requested and are available for all the
Avaya Media Servers being installed.
The HWaddr label in the results displays the value of the MAC address. (Do not
include colons : as part of the MAC address)
11
5 Planning
This section describes how to gather the information required for performing the
procedures described in the remainder of this document.
A job aid (102.3.6 Avaya Media Server Installation and Commissioning Job
Aid.xlsm) is provided along with this document to capture the required
information. It has the following tabs:
MS Data This worksheet should be used to enter information for the
Primary, Secondary and Standard Media Servers.
Miscellaneous This worksheet should be used to enter miscellaneous
information related to the installation and commissioning procedure.
To collect the required data, open the job aid and enter the following information
1. MS Data
a. Put the Primary Avaya Media Server data
b. Put the Secondary Avaya Media server data
c. Put the additional Avaya Media server data, if necessary
The information can be determined by the network administrator.
2. Miscellaneous
a. Put the Element Manager Console data
b. Put the Provisioning Client data
c. Put the FTP server data
d. Put vmhostname
e. Put the Logical Entity. The logical entity name is created for use when
performing the provisioning of each of the individual services. An
example could be le_domain if the logical domain is used for all
services.
f. Put the Provisioned Domain
g. Put Avaya Media Server Installers names.
h. Put the Treatment Media Files
i.
March 20, 2012
12
j.
Note: Media files are to be .wav of the form 16 bit pcm mono 8Khz. The
job aid references several items that are indicated as <customer defined>.
For these items it is expected to have a unique name that is meaningful to
the customer. There are no rules specifying how a customer must select or
create a name. The items are included to point out that there will be
naming requests throughout the provisioning process.
13
14
2. Enter su - to become the root user, entering the root password when
prompted.
3. Change directory by entering
cd /var/mcp/loads
15
5. Accept the license agreement and wait for the a installer to complete
Execute the installer for each application for each Avaya Media Server.
16
5. Replace records in this directory. After replacing of the records for all
necessary MAS Applications perform the next step.
6. Copy directory Announcements to AnnouncementsCustom with saving the
ways by executing
cp -f -R
/var/mcp/ma/MAS/platdata/Announcements/*
/var/mcp/ma/MAS/platdata/AnnouncementsCustom
As result the records from AnnouncementsCustom directory will be
copied to Announcements directory during each MAS installation or an
upgrade.
The backup of custom records will be saved in AnnouncementsCustom
folder and will be automatically restored after upgrade or re-install.
To restore default Announcements rename the folder
AnnouncementsCustom (E.g. OldAnnouncementsCustom) or move this
folder to an external device. Then delete this directory before MAS
installation or an upgrade.
17
18
7. Navigate to Servers.
8. Click on Servers.
Figure 3 Servers
19
20
21
22
9 Licensing Configuration
Each Avaya Media Server requires a license that is designated for the system to
run. The license is generated based on MAC address.
1. Launch AS 5300 Element Manager Console.
http://<EM Service IP>:12120
Figure 9 Launch AS 5300 Element Manager Console
3. From the Menu presented on the left panel, open Network Elements
>> Media Servers and Clusters >> Media Server >> Media
Server Long Name >> License key, copy a <Avaya Media Server
License Key > for Avaya Media Server in the field License key then
press the Apply button.
Important: The comment line should not be copied when copying a license
key.
Note: Step 3 needs to be repeated for each Media Server in the system.
23
24
Avaya MS A
Primary
Avaya MS C
Standard
CStore
Mirroring
Avaya MS B
Secondary
Avaya MS D
Standard
If the system has additional Avaya Media Servers, then perform the following:
1. If the Avaya Media Servers need to be configured as Standard Media
Servers in the default cluster, then following the instructions in
APPENDIX A Add Avaya Media Servers to Cluster to add the Avaya
Media Servers to the default cluster
2. If the Avaya Media Servers need to be configured in a separate cluster,
then follow the instructions in APPENDIX B Create Avaya Media Server
Cluster to configure a new cluster with the Avaya Media Servers
By default an AS5300 system includes an Avaya Media Server Cluster configured
with two Avaya Media Servers. Perform the following to configure the replication
settings for each Avaya Media Server Cluster:
1. Launch the AS 5300 Element Manager Console.
25
26
27
28
29
30
Via MCP console go to Network Elements > Media Servers and Clusters > Media Servers
2.
3.
4.
31
32
3. In the drop down Node type select Default (item 1Figure 18 Add
Service Node).
4. In the drop down Location Choose the location appropriate for the
Provisioned domain (item 2).
5. Select the checkbox Is Trusted (item 3).
6. Select the checkbox Enhanced IM Check both boxes (item 4).
7. Execute Press the Save button and continue.
33
8. The new node should be listed in the table in the bottom half of the
pane. Select the hyper-linked field Domains (item 5).
9. In the new pane presented, select the Provisioned domain, in the drop
down Available Domains. Use the Add button to add the domain.
The domain should appear in the Assigned domains box.
10. Then press the Save button to keep these settings.
34
If there are multiple Avaya Media Servers configured the Service Node for each
Avaya Media Server is to be added.
Next the logical entity needs to be set up. This logical entity is used for the
services in this Avaya Media Server cluster.
11. Start by clicking the Logical Entity Tab in the service node
window.
12. Provide a Logical Entity name in the text box Entity name.
13. Use the mouse and the control key to select an Avaya Media Server
service and press the Copy button for each Avaya Media Server service
in this cluster, or use Copy all to select all services.
14. In the next pane below Add route(s) to logical entity, enter a
route name in the text box Name.
15. Select one of the Avaya Media Server nodes defined earlier for each
Avaya Media Server in this cluster (creating one route for each service
node). Then press Save (item 1 Entity Figure).
16. Repeat steps 13 and 14 for each Avaya Media Server Node in this
cluster.
17. Press the Save (item2) button under the logical entity to save the
logical entity created.
35
36
5. From the Select pool drop down, select the Provisioned domain
logical entity.
6. Press the Save button.
38
13. If there are multiple music files, repeat steps 6, 7 and 8 for each music
file. Order of the upload is not important.
Figure 20 Select Music On Hold
39
Select the pool in the Select pool drop down box and press >>.
40
41
42
16. Enter a group name for the treatment. The group name is only used as
a treatment organization.
17. Highlight and select a reason such as NOT_FOUND from the Available
reasons, and press the Copy button.
18. On the pane below highlight and select the file from Available
Files that corresponds to the treatment file such as 404 and press
the Copy Button
19. Press the Save button.
20. Repeat steps 13-19 for each treatment required.
Figure 26 Select Treatment
44
45
46
47
48
49
50
51
1. Select the Provisioned domain from the Domain dialog on the right
side provisioning display.
2. Select the services tab.
3. Select the IM Chat link
4. From Select Pool, Select the logical entity created in the previous
section.
52
54
55
56
Uninstaller Name
Adhoc Conferencing
Uninstall Adhoc
Application/Uninstall_Adhoc_Application
Meet Me Conferencing
Uninstall Meet me
Application/Uninstall_Meetme_Application
Music On Hold
Announcements
Unified Communications
Uninstall UComm
Application/Uninstall_UComm_Application
Chat
Note: Upon execution of each application installer the following prompts are seen.
Answer each prompts as given below.
1. Do not remove the Avaya Media Server Platform as this must be done after all
applications have been uninstalled.
2. Do you want to uninstall Moh Application 7.5.0.xx? (y/n) (DEFAULT: yes)
At the prompt enter yes.
3. Do you want to preserve configuration data? (y/n) (DEFAULT: yes)
At the prompt enter no.
Repeat the above steps for each application.
57
58
Example:
as5300configuninstall.pl
Uninstall AS5300 configuration
/var/mcp/ma/MAS/bin/dscpconfig.sh uninstall
/var/mcp/ma/MAS/bin/firewallconfig.sh uninstall
mcpMsUninstall.pl
Uninstall MediaServer software
MCP MS customization package: 15.0.0.66
MediaServer s/w: 7.5.0.301_2011.06.29
Continue uninstall? (Y/N)?: [Y]
59
18 References
102.3.6 AS 5300 3.0 Avaya Media Server Installation and Commissioning Job Aid
60
61