Prior to an application discovering any assigned Media Server, a special administrator account in System Manager must be prepared to allow the application access. Not all applications perform this discovery step, so this procedure may not be needed. See adopting solution documentation for details.
Procedure
Sign into System Manager Web UI.
Navigate to Users > Administrators > Security > Roles.
On the Roles page, highlight the role System Administrator, and click New to create a new role.
On the Add New Role page, set the role name and description.
Click Commit and click Continue.
On the Role Details page, click Add Mapping….
On the Select Element and/or Network Service to Map to Role page, select Avaya Aura Media Server as Element or Resource Type and All as Element or Resource Instance.
Click Next.
Click Commit.
To complete the creation of the new role with the permissions of Media Server element, on the Role Details page, click Commit.
To assign the new role to an administrative account, sign into System Manager Web UI.
Navigate to Users > Administrators > User Services > Administrative Users.
On the Administrative Users page, click Add…
On the Add New Administrative User Step 1 page, fill in the required field.
Click Commit. Click Continue.
On the Add New Administrative User Step 2 page, select and assign the role that has the permissions of AAMS element as Avaya Aura Media Server Administrator.
Click Commit.
Sign out of System Manager.
Sign into System Manager again using the new administrative user and change the password at the first login.
Note:
The new administrative user and password are required by the Media Server controlling application, see the applications documentation to determine where to configure this information.
