Perform the following procedure to create a proper file structure on your local system for the zipped files:
Important:
When creating the zip file, keep these naming restrictions in mind:
The namespace and content group names cannot begin with the at (@) symbol, must be less than 128 characters, must not be case-sensitive, and must not contain spaces or any of the following symbols: { } ' * \
The media file names must be less than 128 characters, are case-sensitive, and must not contain any of the following symbols: { } ' * \
Note:
Many browsers have a 2GB limit for file uploads.
Note:
Avaya recommends that audio to be played by Avaya Aura® MSbe encoded as 16 bit, 8 kHz, single channel, PCM files. Codecs other than PCM or using higher sampling rates for higher quality recordings can be used, however, with reduced system performance. Multiple channels, like stereo, are not supported.
Before you begin
Ensure that you have already created a namespace to contain the new media files and know the name of that namespace.
Procedure
Select a target namespace already configured on Avaya Aura® MS, for example, MyNamespace.
Create a directory on your system with the same name as the target content namespace name.
The directory that you create is the root directory for your zip archive.
Create subdirectories in the namespace directory.
Subdirectories represent the content groups that the system creates in the target namespace. The file structure in the uploaded zip file must match the namespace and content group structure that you want on Avaya Aura® MS.
If the structure is not as described in the example, the upload fails.
For example, to upload media zip files to a namespace called MyNameSpace with a content group called MyContentGroup, the zip file structure must be as follows:
