How to Bulk Upload WAV Files to Avaya Aura Media Server (AAMS) for

use as Communication Manager 7 Announcements

The first step in the process is to discover the Namespace name Communication Manager (CM) has been assigned in the
Avaya Aura Media Server (AAMS). This Namespace name is created by AAMS when it has been associated with one or
more CMs. It is obscured by AAMS to make human management friendlier. AAMS hides the actual name and presents
the Product Name which in the case of CM is simply named “Communication Manager”. As other CMs are added, a
Content Group is created which can be seen as the “Announcement Storage Area” on the CM “display media-server <x>”
form. Both the Namespace name and the Content Group (aka Announcement Storage Area) will be required to bulk
upload announcements.

To discover the actual Namespace name usable for bulk uploading WAV files, access to the AAMS’s System Management
Interface (SMI) GUI is required.

Log in to the AAMS SMI using a web browser (via SAL): https://<localhost>:8443/emlogin. (Note: If on site use
the IP address of the AAMS in place of localhost). Navigate to Tools -> Media Management.

Notice the asterisk note at the bottom of this screen that states the UUID identifier has been translated to the product
name. In this case it has been translated to “Communication Manager”.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 1 | 8
To obtain the actual namespace UUID identifier click on the checkbox next to the “Communication Manager” Content
Namespace and click “Rename”.

AAMS then displays the actual Content Namespace UUID identifier in the Name field as shown here. This name is
needed to properly format the zip archive which will contain the WAV files and be created as part of this process.

Highlight the Name and copy it to the laptop clipboard. Be sure and click Cancel after copying.

On the laptop, in Windows File Explorer, create a directory with the Content Namespace copied from the step above.

(Note that this name will be different than the one shown in this example.)

The next item needed is the Content Group name. This can be discovered either on the AAMS SMI or from CM. To obtain
the Content Group name from AAMS click the “Communication Manager” checkbox then click “Browse”.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 2 | 8
When the next screen opens, click the “+” beside “Communication Manager” to reveal the Content Group name.

(Notice that there are already two WAV files loaded on this AAMS named “MOH” and “nonworking”.)

Since the Content Group name is actually a hyperlink it can be tricky to copy to the laptop clipboard. Right-click on the
name to open a menu.

Click “Rename”. This will open a dialog box where the name can be easily copied. Be sure and copy the entire string as
parts are hidden.

Be sure and click “Cancel” after copying to the clipboard.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 3 | 8
CM can also be used to determine the Content Group name.

In CM use the “list media-server” command to find the media-server number.

Then use the “display media-server <x>” command. In this case the media-server was number 10 in CM.

The Content Group name can be easily copied from this screen. It is the “Announcement Storage Area” field.

Next, in Windows File Explorer on the laptop, open the Namespace directory that was previously created above. In this
example its name was “379bf905-da2f-11e0-882c-e36c7400a53b”. Create a new directory of “ANNC-78bad23c-d361-
41e6-b39b-005056b73286” in that directory. (This name will be different than this example.)

It is in this directory that the WAV files to be bulk uploaded to AAMS will be placed. In this example, three WAV files
were copied to this directory using Windows File Explorer.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 4 | 8
The next step is to create the zip archive file.

Still in Windows File Explorer, right click on the Namespace directory “379bf905-da2f-11e0-882c-e36c7400a53b”.

Then choose the “Add to 379bf905-da2f-11e0-882c-e36c7400a53b.zip” selection. This will create the zip archive in the
proper format.

Open the newly created zip archive file and verify that the Path is correct. The Path should show the
“Namespace\Content Group\” as seen below for this example.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 5 | 8
If WinZip is not set to display the Path, right click on any header and click to display the Path.

Once the Path has been verified close the zip archive. The archive (zip file) is now ready to be uploaded to the AAMS.

On the AAMS SMI GUI click on Tools -> Media Management (if not already selected).

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 6 | 8
Select the “Communication Manager” Content Namespace checkbox and click “Browse”.

After the next screen opens click “Communication Manager” to highlight it then click “More Actions” from the
dropdown menu shown below.

Select “Batch File Provision” and another window will open.

Click “Browse” in that window and select the Zip archive (379bf905-da2f-11e0-882c-e36c7400a53b.zip ) and click
“Open”.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 7 | 8
Select the “Cut Extension” checkbox (this removes the “.wav” from the filename) and whichever “overwrite” option is
appropriate for the upload. Click the “Upload” button. The upload from the laptop to the AAMS will begin. There is no
status or progress indication on the AAMS web page.

The new WAV files are now uploaded to the AAMS and ready to be assigned in CM.

Announcements will need to be created in CM (or System Manager) to complete the process. The names used must
match the names assigned in the uploaded zip archive.

Once the announcements are created in CM, testing should be performed for quality and accuracy.

Avaya - Proprietary (Restricted) Solely for authorized persons having a need to know pursuant to company instructions Page 8 | 8