The Communication Manager default configuration does not contain an entry for an external AAA server. All accounts are authenticated on the local host.
To activate use of an external AAA server, the /etc/pam.d/mv-auth file must be edited to incorporate the appropriate line for the server being used, and the additional configuration files edited corresponding to the needs of the AAA service. Activation of an external AAA service will be accomplished by the customer and not by Avaya Services. The customer provides and owns the AAA server on their network and they alone have the data that is necessary to set up the client on the Communication Manager server.
For information regarding configuring AAA Servers, see:
Also see documentation for: