102.1.6 Avaya Media Server Installation and Commissioning

8/10/2019 102.1.6 Avaya Media Server Installation and Commissioning

1/61

1

102.1.6 AS 5300 3.0 Avaya Media ServerInstallation and CommissioningMethod of Procedure

Product Release: AS 5300 R3.0

Document Version: 1.4

Document Status: Released

Document Release Date: March 20, 2012

Security Classification: Avaya Confidential

Multimedia Communications Platform AS 5300

Copyright 2012 AvayaAll rights reserved.

Avaya CONFIDENTIAL: The information contained in this document is the property of Avaya. Except asspecifically authorized in writing by Avaya, the holder of this document shall keep the information containedherein confidential and shall protect same in whole or in part from disclosure and dissemination to third partiesand use same for evaluation, operation, and maintenance purposes only.


2/61

102.1.6 AS 5300 3.0 Avaya Media Server Installation and CommissioningDocument Version 1.4 Method of Procedure

March 20, 2012 2012 Avaya Inc. 2Avaya proprietaryuse pursuant to company instructions

Revision History

Version Date Description

1.0 November 2011 Approved.

1.1 January, 2012 wi00971894

1.2 January 26, 2012 Media Management note in Section 13

1.3 February 22,2012

wi00980271: Prop: Custom recording is lost after a patchupgrade

1.4 March 20, 2012 US12506: Added 4th step and screenshot in Section 13


3/61

102.1.6 AS 5300 3.0 Avaya Media Server Installation and CommissioningMethod of Procedure Document Version 1.4

3

Table of Contents1

Start Here ................................................................................................................ 7

2

Overview ................................................................................................................. 8

2.1

Document Conventions................................................................................................ 8

2.2 Document Overview .................................................................................................... 9

3

Work Flow ............................................................................................................. 10

4

Verify Prerequisites ............................................................................................. 11

4.1

Avaya Media Server license. ........................... ......................... .......................... ........ 11

5

Planning ................................................................................................................ 12

6

Avaya Media Server Platform Installation ........................................................ 14

6.1

Get Avaya Media Server Platform and Application Installers ...................................... 14

6.2

Install Avaya Media Server Platform ................... ......................... .......................... .... 14

7

Avaya Media Server Application Installation ................................................... 16

7.1

Install MAS Application .......................... .......................... ......................... ................. 16

7.2

Configure custom Announcements ............................................... ......................... .... 16

8

Configure additional Avaya Media Servers...................................................... 18

9

Licensing Configuration ..................................................................................... 23

10

Configuring Avaya Media Server Clustering ................................................... 25

11

Configure SIP routes for Avaya Media Server Cluster ................................... 27

12

Enable AS 5300 Avaya Media Server applications installed ......................... 29

13

Avaya Media Server maintenance ..................................................................... 31

14

Provisioning Avaya Media Server Routing ...................................................... 33

14.1

Setup Application Pools. ........................ .......................... ......................... ................. 33

14.2

Setup Adhoc Conferencing ........................ .......................... .......................... ............ 37

14.2.1 Verify Adhoc Conferencing ........................ .......................... ......................... .... 37

14.3 Setup Meet Me Conferencing .............................................. ......................... ............. 37

14.3.1

Verify Meet Me Conferencing. ............................................ .......................... .... 38

14.4

Set up Music On Hold ........................ .......................... ......................... ..................... 38

14.4.1

Verify Music On Hold. ....................... .......................... .......................... ............ 40

14.5

Set up Branding application ....................... .......................... .......................... ............ 40

14.5.1 Verify Branding service .......................... ......................... .......................... ........ 42

14.6 Set up Treatments application.................................................................................... 43

14.6.1

Verify Treatment service ....................... .......................... .......................... ........ 46


4/61



14.7

Setup Unified Communications ........................... .......................... ......................... .... 46

14.7.1

Verify Unified Communications ........................... ......................... ..................... 51

14.8 Setup IM Chat service ............................................................................................... 51

14.8.1

Verify Chat ....................................................................................................... 52

15

APPENDIX A Add Avaya Media Servers to Cluster ........................................ 53

16

APPENDIX B Create Avaya Media Server Cluster........................................... 55

17

APPENDIX C Uninstall Avaya Media Server Applications ............................. 57

17.1

Uninstall Avaya Media Server Applications ............................... ......................... ........ 57

17.1.1

Uninstalling Adhoc............................................................................................ 57

17.1.2

Uninstalling Annc ............................................................................................. 58

17.1.3

Uninstalling Chat .......................... .......................... ......................... ................. 58

17.1.4

Uninstalling Meet Me ........................ .......................... .......................... ............ 58

17.1.5

Uninstalling MOH ............................................................................................. 58

17.1.6

Uninstalling UComm ......................... .......................... .......................... ............ 58

17.2

Uninstall Avaya Media Server Platform ........................ ......................... ..................... 59

18

References ............................................................................................................ 60


5/61


5

List of FiguresFigure 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


6/61



Figure 28 Configure Treatment/Cause Group ........................................... ......................... ........ 46

Figure 29 Select Voicemail ........................... .......................... ......................... .......................... 47

Figure 30 Configure VMS Host .......................... .......................... ......................... ..................... 48

Figure 31 Configure SIP VMS.................................................................................................... 48

Figure 32 Select the Unified Communications ......................... .......................... ......................... 49

Figure 33 Configure the Routable Service .................................. ........................... .................... 49

Figure 34 Configure Voicemail Service ........................... ......................... .......................... ........ 50

Figure 35 Configure Unified Communication Service for the user ........................... .................... 51

Figure 36 Media Server Clusters ............................................................................................... 53

Figure 37 Edit Media Server Cluster .......................... .......................... .......................... ............ 54

Figure 38 Adding Avaya Media Server Cluster ........................ ......................... .......................... 55


7/61


7

1 Start HereTo immediately start executing the procedures described in this document,proceed to Section3 "Work Flow".

To first gain contextual information regarding this document, first read Section2"Overview", then proceed to Section3 "Work Flow".


8/61



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 (For example: Section1)

where "" is the number of the section. In document text where a

more complete reference facilitates the flow (such as an initial reference in anoverview section), the following form is used:

Section "" (For example: Section1 "Start Here"")

where "" is the name of the section.

References to documents listed in Section18,"References"are typically ofthe form:

[] (For example: [1])

where "" is the number of the reference from Section0.Indocument text where a more complete reference facilitates the flow (such as

an initial reference in an overview section), the following form is used:

[] ""

(For example: [1] 102.1.1. AS 5300 Server Installation)

where "" 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, orgraphical user interface, appears as follows:

Example paragraph input text


9/61


9

2.2 Document Overview

This document describes the procedures to perform the initial installation andprovisioning for the Avaya Media Server in the AS 5300 environment.

The Avaya Media Server requires the application platform software to be installed

followed by the desired set of applications.

The 102.3.6 AS 5300 3.0Avaya Media Server Installation and Commissioning

Job Aidis an Excel workbook data gathering tool which supports the AvayaMedia Server initial installation and commissioning process.


10/61



3 Work FlowThis section provides the work flow to accomplish the installation of AvayaMedia 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. Agiven step must be successfully completed prior to starting the next step.

1. Execute Section4 Verify Prerequisites

2. Execute Section5 Planning

3. Execute Section6 Avaya Media Server Platform Installation

4. Execute Section7 Avaya Media Server Application Installation

5. Execute Section8 Configure additional Avaya Media Servers

6. Execute Section9 Licensing Configuration

7. Execute Section10 Configuring Avaya Media Server Clustering

8. Execute Section11 Configure SIP routes for Avaya Media ServerCluster

9. Execute Section12 Enable AS 5300 Avaya Media Server applicationsinstalled

10.Execute Section13 Avaya Media Server maintenance

11.Execute Section14 Provisioning Avaya Media Server Routing


11/61


11

4 Verify PrerequisitesPrior to the execution of the procedures described in the remainder of thisdocument, 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.0Avaya Media Server Installation and CommissioningJob Aidis to be filled in.

The domain data with some users is provisioned into the system so that AvayaMedia Server services can be verified.

Make sure that the new license keys are requested and are available for all theAvaya Media Servers being installed.

4.1 Avaya Media Server license.

Avaya Media Server requires a new 7.5 license which is based on the MAC

address. Each license needs to be identified for each Avaya Media Server. Licensekey needs to be requested from Keycode Retrieval System (KRS).

For each Avaya Media Server, ensure that you have identified the correct Avaya

Media Server with the correct MAC address.

Log in to Media Server with SSA role. Use the command: ifconfig

The following output is produced:

bond0 Link encap:Ethernet HWaddr 00:21:5E:DC:C8:74inet addr:47.104.10.68 Bcast:47.104.10.127 Mask:255.255.255.192

UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1

RX packets:6769675 errors:0 dropped:0 overruns:0 frame:0

TX packets:4739670 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:5017303153 (4.6 GiB) TX bytes:1025713134 (978.1 MiB)

The HWaddr label in the results displays the value of the MAC address. (Do not

include colons : as part of the MAC address)


12/61



5 PlanningThis section describes how to gather the information required for performing theprocedures described in the remainder of this document.

A job aid (102.3.6 Avaya Media Server Installation and Commissioning JobAid.xlsm) is provided along with this document to capture the required

information. It has the following tabs:

MS DataThis worksheet should be used to enter information for thePrimary, Secondary and Standard Media Servers.

MiscellaneousThis worksheet should be used to enter miscellaneousinformation 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 whenperforming the provisioning of each of the individual services. Anexample could be le_domainif 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. Put the Music on Hold Media Files


13/61


13

j. Put the Branding Announcement Media Files

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 .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 orcreate a name. The items are included to point out that there will be

naming requests throughout the provisioning process.


14/61



6 Avaya Media Server PlatformInstallation

6.1 Get Avaya Media Server Platform and ApplicationInstallers

This section describes the procedure for installing the Avaya Media Server

platform and application software. Prior to installation the installers need to betransferred to the machine on which the software will be installed.

Perform the following for each Avaya Media Server:

1. Insert the Avaya Media Server DVD into the optical drive.

2. Login as a user with the SSA role.

3. Enter su -to become the root user, entering the root password whenprompted.

4. Enter the command cd /var/mcp/loads

5. Enter the commandmount /mnt/cdrom.

6. Enter the command ls /mnt/cdromto inspect the list of files on theDVD.

7. Enter the command cp /mnt/cdrom/MCP_MediaServer_*.zip

/var/mcp/loads

8. Enter the command cp /mnt/cdrom/Setup_linux_*.bin/var/mcp/loads

9. Enter the command umount /mnt/cdrom

10.Enter the command exitto logout as the root user.

11.Enter the command exitto logout as the SSA role user.

12.Remove the Avaya Media Server DVD from the optical drive.

6.2 Install Avaya Media Server Platform

Once all the installers are transferred to the target machine, the following stepsneed to be followed.

Perform the following:



15/61


15


3. Change directory by enteringcd /var/mcp/loads

4. Make the application installers executable by entering the following:chmod 755 Setup_linux*

5. Install the platform installation software by executing the following:

cd /usr/local/bin

mcpMsInstall.pl l

For example:mcpMsInstall.pl lMCP_MediaServer_7.5.0.301_2011.06.29_66

6. Accept and continue the installation. This is done by pressing to continue the installation

For example:mcpMsInstall.pl -lMCP_MediaServer_7.5.0.301_2011.06.29_66

Unpacking files...

Done

MediaServer software to be installed

MCP MS customization package: 15.0.0.66

MediaServer s/w: 7.5.0.301_2011.06.29

Continue installation? (Y/N)?: [Y]

7. Run AS 5300configinstall.pl to install AS 5300 specific parameters:

as5300configinstall.pl

Install AS5300 configuration

/var/mcp/ma/MAS/bin/chmodplat.sh

/var/mcp/ma/MAS/bin/dscpconfig.sh install

/var/mcp/ma/MAS/bin/firewallconfig.sh install

All system default iptables rules have been successfully restored.

If any of these steps fail, contact the next level of support.


16/61



7 Avaya Media Server ApplicationInstallation

7.1 Install MAS ApplicationThis section describes the steps of executing the installers. There are six Avaya

Media Server application installers. One or more may be applicable for aparticular installation. Make sure that are available and present on the Avaya Media Server prior to install.The installers should be in the /var/mcp/loads directory.

Make sure that the Avaya Media Server Application install ersare available.




3. Change to the directory loads by executingcd /var/mcp/loads

4. For each application, run the installer:For example:./SetupSetup_linux_Adhoc_7.5.0.33_2011.09.22.bin

5. Accept the license agreement and wait for the a installer to complete

Execute the installer for each application for each Avaya Media Server.

7.2 Configure custom Announcements

This section describes the steps how to configure the custom Announcements.

MAS have a special mechanism which automatically restores customAnnouncements after the installation or MAS Application upgrade.

NOTE: This feature work onlyfor following applications: DigitCollection,

MeetMe, Unified Communication.

1. Change to user with root priviledges. Execute the following:su -Password:

2. Create a directory with name AnnoucementsCustom.

mkdir /var/mcp/ma/MAS/platdata/AnnouncementsCustom


17/61


17

3. Make the directory executable by entering the following:

chmod 750 AnnouncementsCustom/

4. Change the directory to modify Annoucements:

cd/var/mcp/ma/MAS/platdata/Annoucements//default/us/en/l16

E.g. for MeetMe Application Annoucements:

cd/var/mcp/ma/MAS/platdata/Annoucements/meetme/default/us/en/l16

5. Replace records in this directory. After replacing of the records for allnecessary MAS Applications perform the next step.

6. Copy directory Announcementsto AnnouncementsCustomwith 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 AnnouncementsCustomdirectory will be

copied to Announcementsdirectory during each MAS installation or anupgrade.

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 thisfolder to an external device. Then delete this directory before MAS

installation or an upgrade.


18/61



8 Configure additional Avaya MediaServers

If the system has additional Avaya Media Servers, then execute the following foreach Avaya Media Server.

1. Launch the AS 5300 Element Manager Console.

http://:12120

2. Login to the AS 5300 Element Manager Console as an admin user

3. Navigate to IPv4 Addresses (Network Data and MtcAddresses IPv4Addresses)

4. Click on IPv4 Addresses.

Figure 1 IPv4 Addresses

5. Click on Add button.

6. Add Logical Name and IPv4 Addresses then press Apply button.


19/61


19

Figure 2 IPv4 Addresses configuration

7. Navigate to Servers.

8. Click on Servers.

Figure 3 Servers


10.Fill in all the necessary fields in the Add Server form and press Applybutton.


20/61



Figure 4 Add Server

11.Navigate to Media Servers and Clusters (Network Elements MediaServers and Clusters)

12.Click on Media Servers.

Figure 5 Media Servers


21/61


21

13.Click on Add button.

14.Fill in all the necessary fields in the Add Media Server form (use 49000 as aBase Port and 80 as a SOAP port) and press Apply button.

Figure 6 Add Media Server

15.Expand the newly created media server.

16.Click on the Instance.

17.Select the server. It is to be one created at steps 8-10.

18.Click Edit button.


22/61



Figure 7 Media Server Instance

19.Select Server, Load and Patch and Engineering.

20.Click Apply button.

Figure 8 Edit Media Server Instance


23/61


23

9 Licensing ConfigurationEach Avaya Media Server requires a license that is designated for the system torun. The license is generated based on MAC address.

1. Launch AS 5300 Element Manager Console.

http://:12120

Figure 9 Launch AS 5300 Element Manager Console

2. Log in to AS 5300 Element Manager Console.

Figure 10 Log in to AS 5300 Element Manager Console

3. From the Menu presented on the left panel, openNetwork Elements>>Media Servers and Clusters >> Media Server >> Media

Server Long Name >> License key, copy a for Avaya Media Server in the field License keythen

press theApplybutton.

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.


24/61



Figure 11 Licensing Configuration


25/61


25

10 Configuring Avaya Media ServerClustering

This section describes the procedure to configure Avaya Media Server Clusterfrom the AS 5300 Element Manager Console.

An Avaya Media Server cluster is a collection of Avaya Media Server nodes thatwork closely together and can be viewed as one node. An Avaya Media Server

cluster must contain at least one primary Media Server. Secondary Avaya MediaServer and Standard Avaya Media Servers can optionally be added, to a

maximum of eight servers in a cluster.

The figure below shows Avaya Media Server cluster with four Avaya MediaServers configured in a cluster.

Figure 12 Avaya Media Server cluster

If the system has additional Avaya Media Servers, then perform the following:

1. If the Avaya Media Servers need to be configured as Standard MediaServers in the default cluster, then following the instructions in

APPENDIX A Add Avaya Media Servers to Cluster to add the AvayaMedia Servers to the default cluster

2. If the Avaya Media Servers need to be configured in a separate cluster,

then follow the instructions inAPPENDIX B Create Avaya Media ServerCluster to configure a new cluster with the Avaya Media Servers

By default an AS5300 system includes an Avaya Media Server Cluster configuredwith two Avaya Media Servers. Perform the following to configure the replication

settings for each Avaya Media Server Cluster:


Avaya MS A

Primary

Avaya MS BSecondary

Avaya MS C

Standard

Avaya MS DStandard

Avaya MS Cluster with Four Nodes

CStoreMirroring


26/61




3. Navigate to Media Servers and Clusters (Network Elements Media Serversand Clusters)

4. Click on Media Servers and Clusters

5. Expand the Media Server Cluster and click on Replication Settings toconfigure replication settings for the cluster

6. Click on Enable Replication Account and enter User Name, Password,confirm Password and Click Applyas shown in the figure below

Figure 13 Replication Account Settings


27/61


27

11 Configure SIP routes for AvayaMedia Server Cluster

This section describes the procedure to configure Avaya Media Server SIP Routesfrom the AS 5300 Element Manager Console.

Perform the following for each Avaya Media Server Cluster:


http://:12120


3. Navigate to Media Servers and Clusters (Network Elements Media Serversand Clusters)

4. Click on Media Servers and Clusters

5. Expand the Media Server Cluster and click on SIP Routes to configure SIProuts settings for the cluster.


7. Choose SIP Node and SIP Transport.

8. Enter Served Domain (the default * means all ones), priority andweight, if necessary.

9. Click Apply as shown in the figure below.


28/61



Figure 14 SIP Routes Settings.


29/61


29

12 Enable AS 5300 Avaya Media Serverapplications installed

This section describes the procedure to enable the Avaya Media Serverapplications installed so that the application configuration can be updated from

the AS 5300 Element Manager Console.

Perform the following for each Avaya Media Server Cluster:

1. Launch the AS 5300 Element Manager Console

http://:12120

2. Login to AS 5300 Element Manager Console as an admin user

3. Navigate to Media Servers and Clusters (Network Elements MediaServers and Clusters)

4. Expand the Media Server Cluster and Click on ApplicationConfiguration

5. Enable the application installed as shown in the figure below and clickApply


30/61



Figure 15Enable AS5300 Avaya Media Server applications


31/61


31

13 Avaya Media Server maintenanceThis section describes the procedure to deploy and start Avaya Media Server NEsfrom the AS 5300 Element Manager Console.

NOTE:For the media file management to work from the Provisioning client, make sure to enableMedia Server NE:

1. Via MCP console go to Network Elements > Media Servers and Clusters > Media Servers

2. Click Edit button for intend MS NE

3. SIP TLS checkpoint must be enabled

4. Restart MS instance having SIP/TLS enabled


32/61




1. Launch the AS 5300 Element Manager Console

http://:12120

2. Login to AS 5300 Element Manager Console as an admin user

3. Navigate to Media Servers and Clusters (Network ElementsMediaServers and Clusters)

4. Expand the Media Servers and Clusters

5. Expand Media Servers

6. Expand Media Server network element and click on NE Maintenance

7. Deploy and start the Media Server NE instance

Figure 16 Deploy and start Avaya Media Server NE


33/61


33

14 Provisioning Avaya Media ServerRouting

This section describes the procedure for the minimum setup required to ensurethat calls are routed to Avaya Media Server services and that the services are

functional. This section does not cover all of the user based provisioning.

Note:All steps are done on AS5300 Provisioning Manager

14.1 Setup Application Pools.

Prior to starting this step. Identify Provisioned domain(s) that are beingprovisioned. If the domain is not provisioned, ensure that the domain level

provisioning is performed before continuing with this section. For each AvayaMedia Server application, an association to the domain needs to be created with

provisioning.

Create a Service Node.

1. Use the index on the right to select Logical Entity. (Figure 17 SelectLogical Entity)In the window created select the left most tabNode.

From the within the Node pane, perform the following:

2. Enter a name Avaya Media Server A node namein the text fieldNodename.

3. In the drop downNode typeselect Default (item 1Figure 18 AddService Node).

4. In the drop down LocationChoose the location appropriate for theProvisioned domain(item 2).

5. Select the checkbox Is Trusted(item 3).

6. Select the checkbox Enhanced IMCheck both boxes (item 4).

7. Execute Press the Save button and continue.


34/61



Figure 17 Select Logical Entity

Figure 18 Add Service Node

8. The new node should be listed in the table in the bottom half of the

pane. Select the hyper-linked fieldDomains

(item 5).

9. In the new pane presented, select the Provisioned domain, in the dropdownAvailable Domains. Use theAddbutton to add the domain.

The domain should appear in theAssigned domainsbox.

10.Then press the Savebutton to keep these settings.


35/61


35

If there are multiple Avaya Media Servers configured the Service Node for eachAvaya Media Server is to be added.

Next the logical entity needs to be set up. This logical entity is used for theservices in this Avaya Media Server cluster.

11.Start by clicking the Logical Entity Tabin the service nodewindow.

12.Provide a Logical Entityname in the text box Entity name.

13.Use the mouse and the control key to select an Avaya Media Server

service and press the Copybutton for each Avaya Media Server service

in this cluster, or use Copy allto select all services.

14.In the next pane belowAdd route(s) to logical entity,enter aroute name in the text boxName.

15.Select one of the Avaya Media Server nodes defined earlier for eachAvaya 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 thiscluster.

17.Press the Save(item2) button under the logical entityto save thelogical entity created.


36/61



Figure 19 Add Logical Entity

Next The Domain needs to be assigned to the logical entity.

18.On the pane belowAdd route(s) to logical entity, select the

hyperlinkAssign/Removeunder the Domainscolumn.

19.Select the Provisioned domainin theAvailable domainsdrop down

and press theAddbutton. Then press the Savebutton.

If a logical entity has multiple Avaya Media Server network elements

configured as service node then all the Avaya Media Server networkelements need to be in one Media Server Cluster.


37/61


37

14.2 Setup Adhoc Conferencing

This section describes the procedure for performing the provisioning required toallow calls to be made to adhoc conferencing


1. Select the Provisioned domainfrom the Domaindialog on the rightside provisioning display.

2. Select the services tab.

3. Select theAdhoc Conferencinglink

4. From Select Pool, Select the logical entitycreated in the previoussection and press the >>button next to it.

5. Check each checkbox for locations that will use Adhoc conferencing

under theAddlocationslabel. (Choose Other location if there is noothers.)

6. Press the Savebutton.

14.2.1 Verify Adhoc Conferencing

There are 3 users A, B and C with Services retrieved.

1. User A calls User B.

2. User A calls User C.

3. User A creates an Adhoc conference.

4. Users A, B and C can hear each other.

14.3 Setup Meet Me Conferencing

This section describes the procedure for performing the provisioning required toallow calls to be made to Meet Me conferencing. This does not ensure or specify

settings for specific users.


1. Select The Provisioned domainfrom the Domaindialog on the rightside provisioning display.

2. Select the services tab

3. Scroll down and click theMeet Me Conferencinghyperlink.

4. Select the ConferencesPool tab.


38/61



5. From the Select pooldrop down, select the Provisioned domainlogical entity.


14.3.1 Verify Meet Me Conferencing.

1. User A calls meetme@ProvisionedDomain. For example:[email protected]

2. User A can hear the invitation.

14.4 Set up Music On Hold

This section describes the procedure for performing the provisioning required to

allow calls to be made to Music On Hold. The Provisioning managers required.

To provision Music On Hold perform the following from the Provisioning

manager:

1. Select the Servicestab

2. Scroll down and select Announcements.

3. Scroll down and select the Music On Holdhyperlink (Figure 20 SelectMusic On Hold).

4. Select the poolin the drop down item for this cluster and press the >>button.

5. Enter a Music folder name in the Foldertextbox and press the Savebutton.

6. Click on the Media managementlink (Figure 21 Media management)

7. Click onBrowsebutton and select the media file to upload (Item 1Figure 22 Upload media file)

8. Enter the file name (Item 2, do not include the .wav as part of thename) and press Savebutton (item 3).

9. Click the tab Assign M usic Folders

10.Select the Provisioned domainin the drop down list and press the >>button.

11.Select the poolfor the Provisioned domainand press the >>button.

12.Select the desired music folder for the logical entity and press the Savebutton.


39/61


39

13.If there are multiple music files, repeat steps 6, 7 and 8 for each musicfile. Order of the upload is not important.

Figure 20 Select Music On Hold

Figure 21 Media management


40/61



Figure 22 Upload media file

14.4.1 Verify Music On Hold.

1. User A calls moh@ProvisionedDomain. For example: [email protected]

2. User A can hear music used for Music On Hold service.

14.5 Set up Branding application

To provision Branding perform the following from the provisioning manager:

1. Select the Servicestab.


3. Scroll down and select Brandinghyperlink (Figure 23 SelectBranding).

4. Select the Provisioned domainin the Select domaindrop down box

and press >>.

5. Select the poolin the Select pooldrop down box and press >>.

6. Click on Browse button and select the media file to upload

(Item 1Figure 24 Create media file)

7. Enter the file name (item 2) (do not include the .wav as part of thename.) and select a locale (item3).


41/61


41

8. Press the Savebutton (item 4).

9. Select theAssign Filestab.

10.Select the Provisioned Domainfrom the Domain dropdown box andpress the >>button.

11.Select the logical entityfor the Provisioned domainand press the >>button. The window is then updated with files added in the previousstep.

12.Select the desired file name(s) with the mouse and press the copy

button and then the Save button(Figure 25 Assign Branding media

file).

13.Repeat steps 6, 7 and 8 for each file desired.

Figure 23 Select Branding


42/61



Figure 24 Create media file

Figure 25 Assign Branding media file

14.5.1 Verify Branding service

1. Turn on Play between subscribers in the domain.

2. User 1 calls User2.

3. User1 can hear branding announcement.


43/61


43

14.6 Set up Treatments application

Make sure treatments and the files that are used to map to reason codes areavailable and understood prior to starting this section. Treatment is the

responsibility of the customer.

NOTE: MLPP announcement files can be found on the Avaya Media Server inthe directory /var/mcp/ma/MAS/platdata/Announcements/annc/mlpp/us/en.

In order to set up treatments perform the following from the provisioningmanager.

1. Select the Servicestab.


3. Scroll down and select Treatmenthyperlink (Figure 26 SelectTreatment).

4. SelectAssign Pooltab.

5. Select the Provisioned domainfrom the drop down item and press >>button.

6. Select the poolfor the domain in the Select pooldropdown and

press the Save button.

7. Select the Treatment/Cause Filetab

8. Select the Provisioned domainin the Select domain drop down andpress the >>button

9. Select the poolin the Select pooldrop down and press >> button.

10.Click on Browse button and close the media file to upload

(Item 1Figure 26 Select Treatment)

11.Enter the file name (item 2, do not include the .wav as part of thename.) and select a locale (item 3).

12.Press the Savebutton (item 4).

13.Select the Treatment/CauseGrouptab

(Figure 28 Configure Treatment/Cause Group).

14.Select Provisioned domainand press >>button.

15.Select the pooland press >>button.


44/61



16.Enter a group name for the treatment. The group name is only used asa treatment organization.

17.Highlight and select a reason such asNOT_FOUNDfrom theAvailablereasons, and press the Copybutton.

18.On the pane below highlight and select the file fromAvailable

Filesthat corresponds to the treatment file such as 404 and press

the CopyButton

19.Press the Savebutton.

20.Repeat steps 13-19 for each treatment required.

Figure 26 Select Treatment


45/61


45

Figure 27 Add media file


46/61



Figure 28 Configure Treatment/Cause Group

14.6.1 Verify Treatment service

1. User calls the number not defined in the system, for [email protected]

2. User can hear treatment announcement.

14.7 Setup Unified CommunicationsThe following instructions provide the provisioning requirements to make UnifiedCommunication calls. These instructions do not include the provisioning of

aliases to access Unified Communications since they are optional depending onthe customer site configuration.
mailto:[email protected]:[email protected]:[email protected]


47/61


47

From within the provisioning manager perform the following:

1. From the Servicemenu select the Call Terminationlabel then

select Voicemail

2. Select theVMS hosttab

3. Enter a VMShostnamein the Host nametext box.

4. Select the HostURLradio button and enter sip URL

sip:ucmsgrtv@Provisioneddomain;trusted(For example:

sip:[email protected];trusted) in the adjacent text box.


6. Select the SIP VMStab create a profile with a

Name: sip_vms_Provisioneddomain,

Client contactto voicemail.SESMdrop down select SESM1 (default),

Domainsmouse to highlight the Provisioned domain.

Voicemail hostvoicemail_hostspecified in previous step.


Figure 29 Select Voicemail


48/61



Figure 30 Configure VMS Host

Figure 31 Configure SIP VMS


49/61


49

The Unified communications service is set up next.

8. Select the Unified Communicationslink

9. Select the Routable Servicetab.

10.In the Select domain drop down, select the Provisioned domain andpress the >>button.

11.From the Select pooldrop down provide the logical enti tyand press

the Savebutton.

Figure 32 Select the Unified Communications

Figure 33 Configure the Routable Service


50/61



User data can now be provisioned.

12.Check that Unified Communications and Voicemail services are turned on inthe Service set otherwise turn them on.

13.Check that Unified Communications and Voicemail services are turned on for

the user.

14.Configure Voicemail Service for the user.

15.Configure Unified Communication Service for the user.

Figure 34 Configure Voicemail Service


51/61


51

Figure 35 Configure Unified Communication Service for the user

14.7.1 Verify Unified Communications1. Call voicemail@ProvisionedDomain. For example:[email protected]

2. Follow the menu and leave the message.

3. Stop the session.

4. Call voicemail@ProvisionedDomain. For example:[email protected]

5. Follow the menu. Read and delete the message.

6. Stop the session.

14.8 Setup IM Chat service

This section describes the procedure for performing the provisioning required toallow Chat Instant Messaging

mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


52/61



1. Select the Provisioned domainfrom the Domaindialog on the rightside provisioning display.

2. Select the services tab.

3. Select the IM Chatlink

4. From Select Pool, Select the logical entitycreated in the previoussection.


14.8.1 Verify Chat

1. There are users A and B with Services retrieved.

2. Start Chat session via UC Client.

3. Choose a room from a list and press Join chat roombutton.

4. User A and B join a Chat room.

Users A and B can send and receive messages.


53/61


53

15 APPENDIX A Add Avaya MediaServers to Cluster

This section describes the procedure to add an Avaya Media Server to the clusterfrom the AS 5300 Element Manager Console.



http://:12120


3. Click on Media Servers and Clusters.

4. Expand the Media Server and Cluster and click on Media Server Clusters.

5. Select the existing Media Server Cluster where the Avaya Media Server willbe added.

6. Click on Edit button.

Figure 36 Media Server Clusters

7. Move the Avaya Media Server from Available to Used.

8. Click on Apply button.


54/61



Figure 37 Edit Media Server Cluster


55/61


55

16 APPENDIX B Create Avaya MediaServer Cluster

This section describes the procedure to add and configure Avaya Media ServerCluster from the AS 5300 Element Manager Console.

All Avaya Media Servers that will be added into the new cluster are to be created

via AS 5300 Element Manager Console in advance (follow8Configure additionalAvaya Media Servers steps 320).



http://:12120


3. Navigate to Media Server and Clusters (Network ElementsMedia Serverand ClustersMedia Server Clusters)

4. Click on Media Server Cluster


Figure 38 Adding Avaya Media Server Cluster


56/61



6. Put the Shortand Long Name.

7. Select Primary, Secondaryand Standardservers.

8. Click on Apply button.


57/61


57

17 APPENDIX C Uninstall Avaya MediaServer Applications

17.1 Uninstall Avaya Media Server ApplicationsUninstall all of the applications that were installed during installation.

Avaya Media Server

Application

Uninstaller Name

Adhoc Conferencing Uninstall AdhocApplication/Uninstall_Adhoc_Application

Meet Me Conferencing Uninstall Meet meApplication/Uninstall_Meetme_Application

Music On Hold Uninstall Moh Application/Uninstall_Moh_Application

Announcements Uninstall Annc Application/Uninstall_Annc_Application

Unified Communications Uninstall UComm

Application/Uninstall_UComm_Application

Chat Uninstall Chat Application/Uninstall_Chat_Application

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 allapplications 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.

17.1.1 Uninstalling Adhoc

Login as a user with the SSA role.

Enter su -to become the root user, entering the root password when prompted.cd /var/mcp


58/61



For each MAS application, run the uninstaller:./For example:./Uninstall Adhoc Application/Uninstall_Adhoc_Applicationcd /var/mcp/Uninstall Adhoc Application

Run the uninstall file:./Uninstall_Adhoc_Application

17.1.2 Uninstalling Annc


Enter su -to become the root user, entering the root password when prompted.cd /var/mcp/Uninstall Annc Application

Run the uninstall file:./Uninstall_Annc_Application

17.1.3 Uninstalling Chat


Enter su -to become the root user, entering the root password when prompted.

cd /var/mcp/Uninstall ChatApplication

Run the uninstall file:./Uninstall_Chat_Application

17.1.4 Uninstalling Meet Me



cd /var/mcp/Uninstall MeetMe ApplicationRun the uninstall file:./Uninstall_MeetMe_Application

17.1.5 Uninstalling MOH



cd /var/mcp/Uninstall Moh Application

Run the uninstall file:./Uninstall_Moh_Application

17.1.6 Uninstalling UComm



cd /var/mcp/Uninstall UCommApplication

Run the uninstall file:./Uninstall_UComm_Application


59/61


59

17.2 Uninstall Avaya Media Server Platform

Note: All Avaya Media Server applications must be uninstalled before proceeding withthe platform uninstall.



cd /usr/local/bin

as5300configuninstall.pl

mcpMsUninstall.pl

Press to continue uninstall

Example:

as5300configuninstall.pl

Uninstall AS5300 configuration

/var/mcp/ma/MAS/bin/dscpconfig.sh uninstall

/var/mcp/ma/MAS/bin/firewallconfig.sh uninstall

All system default iptables rules have been successfully restored.

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]


60/61



18 References102.3.6 AS 5300 3.0Avaya Media Server Installation and Commissioning Job Aid


61/61


102.1.6 AS 5300 3.0 Avaya Media ServerInstallation and Commissioning

Method of Procedure

Copyright 2012 AvayaAll i ht d

Documents

102.1.6 Avaya Media Server Installation and Commissioning