5U00120V Lab Workbookv2

®
Avaya Aura Conferencing

Implementation and
Maintainance
Course 5U00120V
Table of Contents
Accessing vLab .......................................................................................................................... 2
Shadowing ............................................................................................................................. 2
Accessing TECNet ................................................................................................................. 3
Technical Notes.....................................................................................................................12
vLab Exercises..........................................................................................................................13
Introduction ...........................................................................................................................13
Objectives .............................................................................................................................13
Lab Scenario .........................................................................................................................13
Install and configure Conferencing 7 Software ..........................................................................15
Exercise 1 - Install Conferencing 7 software ..........................................................................15
End of Exercise 1 - Install Conferencing 7 software Lab ........................................................18
Exercise 2 - Configuring Licenses and TLS ...........................................................................19
End of Exercise 2 - Configuring Licenses and TLS ................................................................26
Exercise 3 - Configuring Conferencing 7 ...............................................................................27
End of Exercise 3 - Configuring Conferencing 7 ....................................................................31
Exercise 4 - Configure SIP user for Conferencing and Make a Call .......................................32
End of Exercise 4 - Configure SIP user for Conferencing and Make a Call ............................36
Setup Web Conferencing and the Document Conversion Server ..............................................37
Exercise 5 - Configuring Web Conferencing ..........................................................................37
End of Exercise 5 - Configuring Web Conferencing ...............................................................45
Exercise 6 - Install and configure the DCS ............................................................................46
End of Exercise 6 - Install and configure the DCS .................................................................52
Exercise7 - Call into Conferencing 7 with Avaya Flare Experience ........................................53
End of Exercise 7 - Call into Conferencing 7 with Avaya Flare Experience ............................57
Enabling Video ..........................................................................................................................58
Exercise 8 - Enable Video on the endpoint ............................................................................58
End of Exercise 8 - Enable Video on the endpoint .................................................................59
Exercise 9 - Enable Video in Conferencing 7 .........................................................................60
End of Exercise 9 - Enable Video in Conferencing 7..............................................................61
Maintainance and Troubleshooting Exercises ...........................................................................62
Exercise 10 - Maintainance Exercise .....................................................................................62
End of Exercise 10 - Maintainance Exercise ..........................................................................62
Exercise 11 - Media Server Exercise .....................................................................................63
End of Exercise 11 - Media Server Exercise ..........................................................................68
Exercise 12 - Troubleshooting Exercise.................................................................................69
End of Exercise12 - Troubleshooting Exercise ......................................................................69
Bandwidth and Cascading ........................................................................................................70
Exercise 13 - Bandwidth Exercise .........................................................................................70
End of Exercise 13 - Bandwidth Exercise ..............................................................................78
Exercise 14 - Cascading Exercise .........................................................................................79
End of Exercise 14 - Cascading Exercise ..............................................................................80
Copyright © 2012 Avaya Inc. All Rights Reserved.
This document contains Avaya Inc. confidential and proprietary information.
It is not to be copied, disclosed or distributed in any manner, in whole or in part, without express
written authorization of Avaya Inc. While the information in this document is believed to be
accurate and reliable, except as otherwise expressly agreed to in writing, AVAYA PROVIDES
THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER
EXPRES OR IMPLIED. The information and/or products described in this document are subject
to change without notice.
Avaya and the Avaya Logo are trademarks of Avaya Inc. and may be registered in certain
jurisdictions. All trademarks identified by ®, TM or SM are registered marks, trademarks, and
service marks, respectively, of Avaya Inc. All other trademarks are the property of their
respective owners.
Student
Lab Workbook
Page 1
© 2012 Avaya Inc. All Rights Reserved.
Accessing vLab
All vLabs will be done in TECnet. Your instructor will provide you with the information necessary
to access the vLab and perform hands-on exercises.
If you have not performed the Pre-Check procedure prior to the class, it is a good idea to run
that now before beginning your lab exercises. Your instructor has a downloadable pdf with the
pre-check process.
Shadowing
The Class will use the concept of shadowing so that students can work together to complete the
labs. VNC allows two persons to view a desktop at the same time. Two students working
together will decide who will enter the data for each particular exercise. The other student will
read off the class spreadsheet IPs, hostnames, and other data to complete the lab. If a problem
occurs and the lab does not work properly, students can work together to try to resolve the
problem before calling on an instructor.
Shadow Design
Page 2
Lab design
Accessing TECNet
When it is time to access a lab, your instructor will and assign IDs and Passwords to the training
site called TECNet.
For remote events Students can access the labs via a web site based on the Avaya VPN
Gateway product 3050 that sits in the TECNet.
The VPN Gateway then allows specific port and client level access –using Java port forwarders
and Net direct tunneling to predefined IP address’ and Ports on the TECNet to allow the
students real-time access to the specific lab solutions being trained on.
The four Avaya SSL portals are:
https://trn-na1.avaya.com
https://trn-na2.avaya.com
https://trn-apac1.avaya.com
https://trn-emea1.avaya.com
Page 3
1. Start a browser and enter https://trn-na1.avaya.com. Your instructor may direct you to
use a different regional portal link.
Page 4
2. Enter the student login and student password provided by the instructor.
The Avaya learning Lab portal displays:
Page 5
3. Click on the PC X VNC Portforwarder where X is a number given to you by your
instructor
Page 6
4. This opens VNC forwarder
Page 7
Page 8
Log onto the PC with
User Name: PC Username (refer to class spreadsheet)
Password: PC Password (refer to class spreadsheet)
Log on to: PC Domain (refer to class spreadsheet)
5. The Primary connection for Student 1 is Pod 1A
Page 9
6. The Secondary connection for Student 1 is Pod 1B
7. This table shows the colors associated with each students primary desktop
Page 10
Student Notes
Page 11
Technical Notes
If you need technical assistance at any time, contact the Avaya University Helpdesk. Refer back
to your registration enrollment email for contact information.
Student Notes
Page 12
vLab Exercises
Introduction
In the following lab exercises you will be installing and configuring AAC, Webconfercing, File
Sharing, and enableing video.
There are many instances that ask if you want to continue to a secure
site. When prompted please choose yes, accept, or continue to
website in our lab.
Our lab uses IP adresses for usability to make the lab more user
friendly. In a production enviornment the use of DNS and FQDNs is
reccomended.
Objectives
Upon successful completion of these lab exercises, you will be able to:
 Install and Configure Conferencing 7 software

 Configure Web Conferencing and Document Conversion Server
 Configure video on Conferencing 7
 Back up Conferencing 7
 Add a Media Server to Conferencing 7
 Configure bandwidth management and cascading on Conferencing 7
Lab Scenario
Each vLab experience focuses on a different aspect of the administration
processes, just as the web-based courses do. The vLab is pre-configured
with any administration that is necessary to complete the exercises outlined in
this workbook.
Page 13
Student Notes
Page 14
Install and configure Conferencing 7 Software
Exercise 1 - Install Conferencing 7 software

In this exercise, you will use Putty to access the pre-installed Linux operating system and install
Conferencing 7 from the CDROM.
Step Action
1 Launch Putty from the remote desktop.
2 Enter the Conferencing 7 IP address (refer to class spreadsheet) in the Host

Name (or IP address) field, and click open.
3 Click Yes at the PuTTY Security Alert
Page 15
4 Login to the Conferencing 7 operating system with the user ntsysadm, when
prompted enter the Linux Remote Login Password (refer to class
spreadsheet)
5 Switch users with the command su – ntappadm , when prompted enter the
Linux App Adm Password (refer to class spreadsheet)
6 Execute the command mcpInstaller
When prompted for a password enter the Linux App Adm Password (refer to
class spreadsheet)for the user ntappadm again
7 Enter Y to continue
8 When prompted
Please enter number [1 to 5] of selection:
Enter 2 for Staging_AAC_Coresident_Simplex
9 When prompted for the following press the ENTER key to take the default
entry:
Please enter the MCP load name [MCP_15.0.10.0_2012-05-20-2013]:

EM IP Address (address of local host)[your Conferencing 7 IP]:
EM Base Port (0-65535)[12100]:
EM NE Name[EM]:
EM Instance (0 or 1)[0]:
14 When prompted for
Please select configuration to use
Enter 1 for AAC_Coresident_Dell610-24GB12Core

15 When prompted for the following press the ENTER key to take the default
entry:
Primary Database Host Address[135.122.81.100]:

Database Host Platform? [linux]:
Page 16
DB NE Name[mcpdb]:

Database Type (SINGLE/REPLICATED)?[Replicated]:
Type is SINGLE
Perform Database Backups (Y/N)?[Y]:
Press the ENTER key to take the default
20 Would you like to make any corrections? [Y/N]:
If everything looks OK enter N
21 When prompted with
Please enter the hostname of the primary Element Manager server
[UpdateMeHost]:
Enter the Element Manager Hostname (refer to class spreadsheet)
Please enter the IPv4 address of the Aura System Manager [0.0.0.1]:
Enter the System Manager IP (refer to class spreadsheet)
Please enter the FQDN of Aura System Manager [UpdateMeFQDN]:
Enter the System Manger FQDN (refer to class spreadsheet)
Please enter the IPv4 address of Aura Session Manager [0.0.0.2]:
Enter the Session Manager IP (refer to class spreadsheet)
Please enter the Service IP address of Element Manager [0.0.0.3]:
Enter the Element Manager IP (refer to class spreadsheet)
Please enter the Service IPv4 address of Accounting Manager [0.0.0.4]:
Enter the Accounting Manager IP (refer to class spreadsheet)
Please enter the Service IPv4 address of Application Server [0.0.0.5]:
Enter the Application Server IP (refer to class spreadsheet)
Please enter the Media IPv4 address of the primary Media Server [0.0.0.6]:
Enter the Media Server IP (refer to class spreadsheet)
Please enter the Service IPv4 address of the primary Web Conferencing
Server [0.0.0.7]:
Enter the Web Conference Server IP (refer to class spreadsheet)
Please enter the Site Name of this AAC installation [UpdateMeSite]:
Enter the SITENAME (refer to class spreadsheet)
Page 17
Would you like to make any corrections? [Y/N]:
Enter N to continue
Please make a selection [Y/N]:
If everything looks OK Enter Y to continue
33 The installation continues and then says Installation Successful
End of Exercise 1 - Install Conferencing 7 software Lab
Page 18
Exercise 2 - Configuring Licenses and TLS
In this exercise, you will add a license to the WebLM server that is embedded in System
Manager, and create an enrollment password in System Manager. You will then use the
Conferencing 7 Element Manager to exchange certificates, and make the certificate available in
EM and PROV. Finally you will add EM and PROV to System Manager. EM and PROV will then
be available through System Manager.
1 Open a browser on your virtual PC, and enter the URL of System Manager.
https://System Manager IP/SMGR/ (refer to class spreadsheet)
2 Enter the System Manager Username (refer to class spreadsheet)and
System Manager Password (refer to class spreadsheet)for System
Manager
3 Navigate to the Licenses hyperlink
4 Choose Install License, and browse to the desktop. Find the license file, and
install it.
5 Navigate to the Security hyperlink
6 Choose Enrollment Password
7 Set your password to avaya123, expiration in 4 weeks, and click Commit.

(Don’t click generate)
8 Open a new browser and enter the URL to Element Manager
Page 19
https:// Element Manager IP:12121/ (refer to class spreadsheet)
Click on Launch Element Manager Console
9 When prompted save the mgmtconsole.jnlp file

10 At the Element Manager Console Message Box click Connect
11 Login with User ID: admin, and Current Password: admin
If prompted for a certificate click Accept the certificate and Apply
12 Navigate to Security -> Certificate Management -> Enrollment Request
13 Enter Logical Name: EM

Common Name: Element Manager
Enrollment Password: avaya123
Click Submit
If warned about the certificate click Apply
Page 20
14 Repeat the procedure for PROV
Enter Logical Name: PROV
Common Name: Provisioning Client
Enrollment Password: avaya123
Click Submit
15 Open Feature Server Elements and click on Element Manager
16 Highlight EM in the Element Manager window, and click the -/+ button
17 For Internal OAM choose EM as the HTTPS Certificate
Page 21
18 Follow the same procedure for Provisioning Managers
19 The screen is slightly different. Choose PROV for the Internal OAM HTTPS
Certificate under Prov
Page 22
20 Stop and Start Element Manager by logging in with Putty to the Conferencing
7 operating system with the user ntsysadm, when prompted enter the Linux
Remote Login Password (refer to class spreadsheet). Then switch users
with the command su – ntappadm , when prompted enter the Linux App Adm
Password (refer to class spreadsheet).
Cd to /var/mcp/install , and issue the commands emStop.pl and emStart.pl
21 In the Home tab find and click on Inventory
22 Choose Manage Elements
Page 23
23 Add a New Managed Element
Choose Type Conferencing
24 Enter a
Name – EM
Node Element Manager IP (refer to class spreadsheet)
25 Click on New Access Point
Page 24
26 In Access Point details enter
Name - EM
Host - Element Manager IP (refer to class spreadsheet)
Port – 12121
Path - /
Order – 0
Click Save, then click Commit
27 Repeat for PROV by adding another new Managed Element of type

conferencing.
28 Name – PROV, and a Node Provisioning Manager IP (refer to class

spreadsheet)
29 In Access Point details enter

Name - PROV
Host - Provisioning Manager IP (refer to class spreadsheet)
Port – 8443
Path - prov
Page 25
Order – 0
Click Save, then click Commit
30 Go to the System Manager Home page, and click
31 There should now be entries for EM and PROV
32 Clicking on EM will open the Element Manager GUI from within System
Manager. PROV is not yet running, but after we configure it later, clicking on
PROV will open the Provisioning GUI.
End of Exercise 2 - Configuring Licenses and TLS
Page 26
Exercise 3 - Configuring Conferencing 7
In this exercise you will configure Conferencing 7. You will the add URIs so that you are able to
have a meetme and adhoc conference call
Step Action
1 Log into Element Manager through System Manager
2 Click on Servers –> EMServer1 -> Monitor, and choose Start Monitor
3 Click on Feature Server Elements -> Database -> mcpdb -> Monitor, and
choose Monitor then choose Start Monitor
4 Choose Feature Server Elements -> Element Manager -> NE Maintainance
Page 27
Element manager should already be Online, Up, and Active. No changes
need to be made, just verify the status
5 Navigate to NE Maintainance in each of Accounting Managers, Provisioning
Managers, Application Servers, Media Servers and Clusters, and web
Conferencing, and Deploy and Start each.
6 When finished all services should be green.
7 Log into System Manager in Conferencing click on PROV. Enter user admin
password admin.
Page 28
8 Navigate to System Management -> System Manager Domains
9 Add a System Manager Domain (refer to class spreadsheet field Domain 1),
and click Add.
10 Navigate to System Management -> Routing -> Service URI
11 Add a Meetme Service URI (refer to class spreadsheet)

Locale – English
Conference Type - MeetMe
12 Add an Adhoc Service URI (refer to class spreadsheet)
Page 29
Locale – English
Conference Type - Adhoc
13 Navigate to System Management -> Routing -> Locations
14 Add a Location Name called (refer to class spreadsheet field Location 1), and
Save
15 Navigate to System Management -> Routing -> Media Server Resources
16 At the Media Server Serving Locations tab
Page 30
Place a check in the newly created location
17 At the Media Server Cluster Physical Location tab
Add MediaServerCluster1 to the Selected Media Server Clusters pane, and

click Save
End of Exercise 3 - Configuring Conferencing 7
Page 31
Exercise 4 - Configure SIP user for Conferencing and Make a Call
In this exercise each student will configure their own SIP user for conferencing, and Make a call
into the Conferencing 7 server. This exercise will be done by each student on their own virtual
PC.
Step Action
1 Open a browser on your virtual PC, and enter the URL of System Manager.
https://System Manager IP/SMGR/
2 Enter the System Manager Username (refer to class spreadsheet) and
System Manager Password (refer to class spreadsheet)for System Manager
3 Navigate to User Management
4 In User Management -> Manage Users
5 Place a check in Student X User (where X is your student letter, refer to the
class spreadsheet), and click Edit
6 In the Communication Profile tab
Page 32
Place a check in Conferencing Profile
Important – when saving the conferencing profile, make sure that the check
mark is present or else the conferencing profile will not get saved
7 Remove the check from “Auto Generate Security Code, and Moderator PIN”
Use your SIP users extension for a security code
Add a 1 to the beginning of the users extension and use that for the Moderator
PIN
8 Click on Get Templates
If Get Templates does not work, check that the TLS connection between
System Manager and CONFERENCING 7.
9 Choose the desktop_user_low_priority template
Page 33
10 Click Commit
11 Double click the OneX Communicator Shortcut on your desktop and log in.
From the OneX Communicator dial the Meetme Service URI (refer to class
spreadsheet)
12 If you successfully reach Conferencing 7 a timer will count upwards from 0:01
Page 34
13 Enter your Moderator PIN and # (1 + your extension + #). If Conferencing 7
receives your Moderator PIN successfully the domain will change to the IP of
the CONFERENCING 7 Application Server.
14 Log into Element manager through System Manager. If you get Login failed,
use any of UserID/Password below, as you partner may be logged in already
admin1/admin1
admin2/admin2
admin3/admin3
Click on Monitoring and Reporting
15 Monitoring and Reporting shows Active Conferences and Sessions. Hang up

the phone. The status should change. If the screen does not show any
activity, try refreshing the browser by hitting the refresh button or
pressing F5.
Page 35
End of Exercise 4 - Configure SIP user for Conferencing and Make a
Call
Page 36
Setup Web Conferencing and the Document Conversion
Server
Exercise 5 - Configuring Web Conferencing
You will now configure web Conferencing. The goal is for the Student A virtual desktop to be
able to press the web collaboration icon in the collaboration agent, have a collaboration window
open, and share the desktop. Then have the virtual desktop for student B log in to the web
collaboration that was started on the Student A desktop and see the Student A desktop through
the web collaboration window.
Step Action
1 Log into Element manager at https:// Element Manager IP:12121
2 Click on Web Conferencing Management Servers
3 Highlight the WCMS and Choose -/+ to edit
Enter a check in Enable HTTP Port, and click Apply
Page 37
4 Click on Web Conferencing Servers
5 Highlight the WCS and Choose -/+ to edit
Enter a check in Enable HTTP Port, and click Apply
Page 38
6 Restart the WCMS
Navigate to Feature Server Elements -> Web Conferencing -> Web

Conferencing Management Servers -> WCMS1 -> NE Maintainance
Page 39
7 Restart the WCS
Navigate to Feature Server Elements -> Web Conferencing -> Web

Conferencing Servers -> WCS1 -> NE Maintainance
8 Log onto PROV through System Manager

Navigate to System Management -> Routing -> Web Conferencing Server
Resources
9 Choose Location 1 (refer to class spreadsheet), add the Primary Web

Conferencing Server, and click Save
Page 40
10 Open a Collaboration Agent by entering https://Provisioning Manager IP:8043
/aacpa/ in a browser.
11 Login with your Student A User (refer to class spreadsheet)and Student A
User Password (refer to class spreadsheet) on Desktop A.
12 Click on My Conference. Then dial into the Meetme Service URI (refer to
class spreadsheet)with your One-X phone, and enter the Moderator PIN (1 +
your phone extension) for Student A
13 Click on the Start Web Collaboration icon
Page 41
14 At this point you can share your entire screen, use the whiteboard, etc. You
cannot share documents from the library. Click on Begin Sharing -> Entire
Screen
Page 42
You now should have a web collaboration session with the moderator logged
in, and the desktop shared on the Student A desktop
15 We are now going to open a web collaboration session on the Student B
desktop, and log into it with the Participant Code associated with the
Moderator that logged into the web collaboration session on desktop A.
(For instance, if the extension is 3001, moderator code would be 13001, and
the participant code would be 3001 if the convention in the lab was followed)
On the Student B desktop log into https://Provisioning Manager IP:8043

/aacpa/ in a browser.
16 Choose the Meeting as a Guest radio Button, enter User Two for a
display name, and click Login
17 For a participant code enter the participant code associated with the
moderator that was used to start the web collaboration on Desktop A
Page 43
18 You should now see the Student A desktop through your web collaboration
session.
Page 44
End of Exercise 5 - Configuring Web Conferencing
Page 45
Exercise 6 - Install and configure the DCS
You will now install the DCS portion of web collaboration. The goal is to upload a document to
the library.
Step Action
1 From your virtual desktop Remote Desktop Connection to the DCS Server
(refer to class spreadsheet)
2 On the DCS Server open FileZilla (an SFTP client)
3 Enter the information to access Conferencing 7
Host: Conferencing 7 IP Address (refer to class spreadsheet)

Username: ntsysadm
Password: Linux Remote Login Password (refer to class spreadsheet)
Port: 22
4 Navigate to /var/mcp/loads/MCP_15.0.10.0_2012-05-20-2013/dcs in the right

pane. Drag and drop the dcs_MCP_15.0.10.0_2012-05-20-2013.zip file to the
c:/ directory. (It can be put anywhere, but we will put it in c:/)
Page 46
5 On the DCS server extract the contents of dcs_MCP_15.0.10.0_2012-05-20-
2013.zip
Page 47
6 After extracting go into the newly extracted dcs directory and double-click on
the Setup DCS batch file
7 After running the batch file Press any key to continue
8 Double-click the Start DCS batch file
Page 48
9 Open a browser to http://localhost:8080 There will be a blank page, but the
Avaya logo will be present.
10 Navigate to Feature Server Elements -> Web Conferencing -> Document

Conversion Servers and press +
Page 49
11 Add a Document Conversion Server
Short Name: DCS

Long Name : DCS_Server
FQDN: DCS Server (IP from class spreadsheet, it is OK to use an IP for lab
purposes)
Protocol: HTTP
Port: 8080
Relative URL: leave blank
Access Key: 123456
12 Log onto PROV through System Manager

Navigate to System Management -> Routing -> Web Conferencing Server
Resources
Add the newly created Document Conversion Server
Page 50
13 Go back to Web Collaboration. Notice that the Upload button in My Library is
no longer greyed out
14 Upload powerofwe.png from your desktop
Page 51
15 Preview powerofwe.png
End of Exercise 6 - Install and configure the DCS
Page 52
Exercise7 - Call into Conferencing 7 with Avaya Flare Experience
You will now use Avaya Flare Expierience to call into Conferencing 7 and use the Collaboration
Button to open a Web Collaboration session.
Step Action
1 Shut down the One-X Communicator.
2 Open Avaya Flare Experience.
3 Log in with your Student A User (refer to class spreadsheet)and Student A

User Password (refer to class spreadsheet)
4 In the top right corner change the view to conference.
Page 53
5 Make a call by clicking on the call button, entering the Meetme Service URI
(refer to class spreadsheet), and clicking on the green telephone.
6 Click on the keypad to enter digits
Page 54
7 Enter the Moderator PIN (1 + your phone extension). Notice that your
Conference info shows to the right, and that the Collaboration button is now
available.
Page 55
8 Click on the Collaboration button to start a Collaboration session.
Page 56
End of Exercise 7 - Call into Conferencing 7 with Avaya Flare
Experience
Page 57
Enabling Video
In this exercise you will enable video on the endpoint and CONFERENCING 7. Enable video on
a per user basis is only necessary if the video class of service was not set to allow video.
Exercise 8 - Enable Video on the endpoint

These are the steps to enable video on the endpoint (OneX, Flare, etc.)
Step Action
1 Log into System Manager
2 Navigate to Communication manager
3 Navigate to Endpoints -> Manage Endpoints
4 Check off your Endpoint 1 (refer to class spreadsheet) and press edit
Page 58
5 In Feature Options
Place a Check in IP Video
6 Click Commit
End of Exercise 8 - Enable Video on the endpoint
Page 59
Exercise 9 - Enable Video in Conferencing 7
These are the steps to enable video in Coferencing 7
Step Action
1 Launch Provisioning Client
2 Search for users by Status ACTIVE
3 Click on Endpoint 1 (refer to class spreadsheet)

4 Click on the Actions tab
5 Navigate to the Conferencing hyperlink
6 Place a check in the Enable Video Field
7 Note - For video to work in the conference call, it must be enabled in the
Collaboration Agent as well.
Page 60
End of Exercise 9 - Enable Video in Conferencing 7
Page 61
Maintainance and Troubleshooting Exercises
Exercise 10 - Maintainance Exercise

In this exercice we will creat a backup of the Conferencing 7 Server
Step Action
1 Use PuTTy to log into the Conferencing 7 System
2 Enter the AAC IP address (refer to class spreadsheet) in the Host Name (or
IP address) field, and click open.
3 Login to the CONFERENCING 7 operating system with the user ntsysadm,
when prompted enter the Linux Remote Login Password (refer to class
spreadsheet)
4 Execute the command mcpRelease.pl
This command displays the current Conferencing 7 version
5 Execute the command configSvrBkup
At the prompt enter Linux Remote Login Password
Choose 3 to display the current backup configuration
6 Execute the command bkupSvr –local
This will create a backup of Conferencing 7
7 Execute the command cd /var/mcp/backup/local/
Execute the command ls
Verify that the backup was created. You will see 5 files if the backup was
successfully
End of Exercise 10 - Maintainance Exercise
Page 62
Exercise 11 - Media Server Exercise
In this Exercise you will add a Media server to the Classroom location. After adding the Media
Server you will stop the first Media Server. You should still be able to make a conference call
into Conferencing 7 if the 1st media Server is down.
Step Action
1 Log in to Element Manager through System Manager
2 Add a new address by clicking +
3 Add a new Media Server

Logical Name: MedSrvAddr
IPv4 Address: MedSrvAddr IP (refer to class spreadsheet)
4 Add a new Server by clicking +
5 Server Name: MedSrv

Long Server Name: MedServer2
IPv4 Internal OAM (Default) Address: MedSrvAddr
Host Name: MedSrv
Page 63
Leave the rest of the entries at default
6 In Feature Server Elements -> Media Servers and Clusters click on Media
Servers, then click +
7 Add a Media Server
Short Name: MS2

Long Name: MediaServer2
Base Port: 49000
Page 64
8 Navigate to the newly created MediaServer2 and click on Instance, then click
+
9 For Server :choose the newly created MedServer2

For Engineering: choose AAC_Coresident_Dell610-24GB12Core
10 Click on Media Server Clusters, then +
Page 65
11 Add a new Media Server Cluster
Short Name:MSC2
Long Name: MediaServerCluster2
12 In MediaServer2 -> NE Maintainance deploy and start MediaServer2
Page 66
13 Log on to PROV through System Manager
14 Navigate to Routing -> Media Server Resources
15 At the Media Server Serving Location tab
Add MediaServerCluster2 to the classroom location, by clicking on the

checkbox, and Saving.
16 At the Media Server Cluster Physical Location tab
Add MediaServerCluster2 to the Selected Media Server Clusters
Page 67
17 Make a call into the Meetme Service URI
Stop MediaServer1 using NE Maintainance
Make a call again. It still should connect.
End of Exercise 11 - Media Server Exercise
Page 68
Exercise 12 - Troubleshooting Exercise
In this exercise the instructor has introduced a problem into the Conferencing 7 system. Use
what you learned in the courseware to try to troubleshoot the problem.
Step Action
1 Make a call to the Meetme Service URI
You should see no time counting, meaning the call did not connect.
2 Use PuTTy to log into the Conferencing 7 System
3 Enter the AAC IP address (refer to class spreadsheet) in the Host Name (or
IP address) field, and click open.
4 Login to the CONFERENCING 7 operating system with the user ntsysadm,
when prompted enter the Linux Remote Login Password (refer to class
spreadsheet)
5 Execute the command cd /var/mcp/oss/acct/AM1/All/MCPV5/AS1_0
6 Execute the command ls
We will be looking at the file AS*active.gz
7 Execute the command zcat AS*active.gz
8 Look for an error code
9 Use the courseware to troubleshoot what may be wrong, and fix the problem.
End of Exercise12 - Troubleshooting Exercise
Page 69
Bandwidth and Cascading
These exercises are meant to show the theory of how Bandwidth Management and Cascading
would be set up in a multi-location deployment
Exercise 13 - Bandwidth Exercise

The Student will add Locations with bandwidth parameters and Media Servers to different sites.
This exercise will be done by each student on their own virtual PC. You will be creating new
locations with bandwidth policies for each new location.
First we need to add an additional Media Server. This Media Server is not
real, it is just for the purposes of the exercise.
1 Log in to Element Manager through System Manager
2 Add a new address by clicking +
Page 70
3 Add a new Media Server
Logical Name: MedSrvAddr3
IPv4 Address: MedSrvAddr IP3 (refer to class spreadsheet)
4 Add a new Server by clicking +
5 Server Name: MdSrv3

Long Server Name: MedServer3
IPv4 Internal OAM (Default) Address: MedSrvAddr3
Host Name: MdSrv3
Leave the rest of the entries at default
Page 71
6 In Feature Server Elements -> Media Servers and Clusters click on Media
Servers, then click +
7 Add a Media Server
Short Name: MS3

Long Name: MediaServer3
Base Port: 49000
Page 72
8 Navigate to the newly created MediaServer2 and click on Instance, then click
+
9 For Server :choose the newly created MedServer3

For Engineering: choose AAC_Coresident_Dell610-24GB12Core
Page 73
10 Click on Media Server Clusters, then +
11 Add a new Media Server Cluster
Short Name:MSC3
Long Name: MediaServerCluster3
12 Now we can begin the exercise. The new media server is available in
provisioning managers database.
13 Log into System Manager at https://System Manager IP/SMGR/
14 Navigate to Routing
Page 74
15 Navigate to Locations
16 Create New Locations
17 Student A creates Locations A & B

Student B creates Locations C & D
Page 75
Student
A Name: Location A Name: Location B
Managed Bandwidth Units: Managed Bandwidth Units:
Mbit/sec Mbit/sec
Total Bandwidth: 5 Total Bandwidth: 5
Multimedia Bandwidth: 1 Multimedia Bandwidth: 1
Location Pattern: 135.1.* Location Pattern: 135.2.*
B Name: Location C Name: Location D
Managed Bandwidth Units: Managed Bandwidth Units:
Kbit/sec Kbit/sec
Total Bandwidth: 1500 Total Bandwidth: 1500
Multimedia Bandwidth: 750 Multimedia Bandwidth: 750
Location Pattern: 135.3.* Location Pattern: 135.4.*
Check Audio Calls can take Multimedia Bandwidth for all Locations
18 Log into PROV through System Manager

19 Navigate to Routing -> Locations
20 Student A will add locations A & B

Student B will add locations C & D
21 In Routing -> Media Server Resources
Page 76
22 Student A will add MediaServerCluster2 to locations A & B
Student B will add MediaServerCluster3 to locations C & D
23 Add the Media Server to the Physical Location
Student A adds MediaServerCluster2 to Location A

Student B adds MediaServerCluster3 to Location C
Page 77
End of Exercise 13 - Bandwidth Exercise
Page 78
Exercise 14 - Cascading Exercise
This is a shared exercise where students work together to create a cascaded configuration.
Step Action
1 Navigate to PROV through System Manager
2 In Routing - > Media Server Resources
3 Navigate to the Media Stream Cascading tab.
All locations are by default set with cascading enabled.
Page 79
Navigate to the Hosting Locations tab
Add all locations to the Hosting Location Classroom
End of Exercise 14 - Cascading Exercise
Page 80

5U00120V Lab Workbookv2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5U00120V Lab Workbookv2

Uploaded by

Copyright:

Available Formats

®

Avaya Aura Conferencing

This document contains Avaya Inc. confidential and proprietary information.

5. The Primary connection for Student 1 is Pod 1A

 Install and Configure Conferencing 7 software

Exercise 1 - Install Conferencing 7 software

2 Enter the Conferencing 7 IP address (refer to class spreadsheet) in the Host

3 Click Yes at the PuTTY Security Alert

Please enter the MCP load name [MCP_15.0.10.0_2012-05-20-2013]:

14 When prompted for

Please select configuration to use

Enter 1 for AAC_Coresident_Dell610-24GB12Core

Primary Database Host Address[135.122.81.100]:

18 When prompted for

End of Exercise 1 - Install Conferencing 7 software Lab

6 Choose Enrollment Password

7 Set your password to avaya123, expiration in 4 weeks, and click Commit.

8 Open a new browser and enter the URL to Element Manager

9 When prompted save the mgmtconsole.jnlp file

11 Login with User ID: admin, and Current Password: admin

If prompted for a certificate click Accept the certificate and Apply

12 Navigate to Security -> Certificate Management -> Enrollment Request

13 Enter Logical Name: EM

17 For Internal OAM choose EM as the HTTPS Certificate

Cd to /var/mcp/install , and issue the commands emStop.pl and emStart.pl

21 In the Home tab find and click on Inventory

22 Choose Manage Elements

25 Click on New Access Point

27 Repeat for PROV by adding another new Managed Element of type

28 Name – PROV, and a Node Provisioning Manager IP (refer to class

29 In Access Point details enter

30 Go to the System Manager Home page, and click

31 There should now be entries for EM and PROV

End of Exercise 2 - Configuring Licenses and TLS

4 Choose Feature Server Elements -> Element Manager -> NE Maintainance

10 Navigate to System Management -> Routing -> Service URI

11 Add a Meetme Service URI (refer to class spreadsheet)

12 Add an Adhoc Service URI (refer to class spreadsheet)

13 Navigate to System Management -> Routing -> Locations

15 Navigate to System Management -> Routing -> Media Server Resources

16 At the Media Server Serving Locations tab

17 At the Media Server Cluster Physical Location tab

Add MediaServerCluster1 to the Selected Media Server Clusters pane, and

End of Exercise 3 - Configuring Conferencing 7

4 In User Management -> Manage Users

6 In the Communication Profile tab

8 Click on Get Templates

9 Choose the desktop_user_low_priority template

Click on Monitoring and Reporting

15 Monitoring and Reporting shows Active Conferences and Sessions. Hang up

3 Highlight the WCMS and Choose -/+ to edit

Enter a check in Enable HTTP Port, and click Apply

5 Highlight the WCS and Choose -/+ to edit

Enter a check in Enable HTTP Port, and click Apply

Navigate to Feature Server Elements -> Web Conferencing -> Web

Navigate to Feature Server Elements -> Web Conferencing -> Web

8 Log onto PROV through System Manager

9 Choose Location 1 (refer to class spreadsheet), add the Primary Web

13 Click on the Start Web Collaboration icon

On the Student B desktop log into https://Provisioning Manager IP:8043

3 Enter the information to access Conferencing 7

Host: Conferencing 7 IP Address (refer to class spreadsheet)

4 Navigate to /var/mcp/loads/MCP_15.0.10.0_2012-05-20-2013/dcs in the right

7 After running the batch file Press any key to continue