A valid authentication file must be present on every Avaya
media server, or all access to
Avaya call-processing (ACP) software from any
login is blocked. Use this screen to install a new authentication file on the Avaya media server. This file contains the logins and passwords Avaya services personnel use to access the Avaya media server. This file is updated regularly by Avaya services personnel if you have a maintenance contract.
A valid authentication file must be present on every Avaya
media server, or all access to
Avaya call-processing (ACP) software from any
login is blocked.
This topic covers:
The authentication (password) file is created on an Avaya services support system and downloaded to the Avaya media server. The file can only be changed using this support system. To change authentication information, the entire file must be replaced.
When you install a new authentication file, a new password file (file with a .pwd extension) is taken from the media server's FTP subdirectory and installed on the system. Any old authentication (password) file is overwritten and not saved. (If the installation fails, the old password file is left in the FTP subdirectory for debugging purposes.)
If the authentication file is missing or corrupted, all logins to the Avaya media server are denied. This does not prevent the Avaya call-processing software from running, but blocks further administration until a new authentication file is installed. See Solving authentication file installation problems for resolution procedures.
To install a new authentication file:
In the main menu of the media server web interface under Security, click the Install Avaya Authentication link.
The Install Avaya Authentication screen appears. Click the Install button.
The screen displays whether or not the file was installed successfully.
If an error message appears, see Solving authentication file installation problems below.
When finished, continue working with the web administration interface as needed.
The Install Avaya Authentication screen may display the following errors:
Bad product id comparison. The authentication file contains a product ID that is not the same as the product ID in the current license. To solve this:
Transfer a new authentication file to the server as described in Put new files on the server.
Run the Install Avaya Authentication screen again.
Could not check installed license. The license file is not installed. To solve this:
Install a license file using the Install License screen.
Run the Install Avaya Authentication screen again.
Current password file invalid. The currently installed authentication file is no longer valid. To solve this:
Transfer a new authentication file to the server as described in Put new files on the server.
Run the Install Avaya Authentication screen again.
Install lacfile is older than current lacfile. The authentication file to be installed has an older timestamp than the current authentication file. To solve this:
Transfer a new authentication file to the server as described in Put new files on the server.
Run the Install Avaya Authentication screen again.
Invalid version on install file <filename>. The file named <filename>is corrupted (damaged) or has a version mismatch. To solve this:
Telnet into the server and navigate to the /var/home/ftp directory.
Delete the old corrupted file named <filename>.
Transfer a new authentication file to the server as described in Put new files on the server.
Run the Install Avaya Authentication screen again.
Multiple or no .pwd files in directory /var/home/ftp. To solve this:
Telnet into the server and navigate to the /var/home/ftp directory. List the files to look for password (.pwd) files.
If no .pwd file is present, copy the current authentication file into this directory as described in Put new files on the server.
If multiple password files are present, delete those that are not needed, and keep only the one that is valid (usually the newest one).
New password invalid nnn. The content in the authentication file is corrupted (nnn is the error code). To solve this:
Transfer a new authentication file to the server as described in Put new files on the server.
Run the Install Avaya Authentication screen again.
No lacfile in <filename>. The file does not contain the correct password content. To solve this:
Transfer a new authentication file to the server as described in Put new files on the server.
Run the Install Avaya Authentication screen again.
License and authentication overview