Avaya Aura ® Communication Manager Access; Security Overview - Avaya G430 Manual

®
Avaya Aura
Note:
Avaya Site Administration (ASA) supports IPv6.
Use Avaya Aura
Gateway provides. Run the Avaya Aura
might be several servers on your network that can control the Gateway. Access Avaya Aura
Communication Manager on any server that is a Media Gateway Controller (MGC) for the
Gateway. For more information, see
Access Avaya Aura
Avaya Site Administration (ASA): ASA provides wizards and other tools that help you to use
Avaya Aura
Guide for Avaya Aura
SSH to port 5023 on the MGC: For more information, see Administrator Guide for Avaya
®
Aura Communication Manager .
Gateway CLI: See

Security overview

The Gateway includes a security mechanism through which the system administrator defines
users and assigns each user a username, password, and a privilege level. The user's privilege
level determines which commands the user can perform.
In addition to its basic security mechanism, the Gateway supports secure data transfer via SSH
and SCP.
The Gateway can be configured to work with an external RADIUS server to provide user
authentication. When RADIUS authentication is enabled on the Gateway, the RADIUS server
operates in conjunction with the Gateway security mechanism. When the user enters a
username, the Gateway first searches its own database for the username. If the Gateway does
not find the username in its own database, it establishes a connection with the RADIUS server,
and the RADIUS server provides the necessary authentication services.
Related topics:
Login permissions
User account management
Administering Avaya G430 Branch Gateway
Communication Manager access
®
Communication Manager software to control telephone services that the
®
Communication Manager with any of the following tools:
®
Communication Manager effectively. For more information, see Administrator
®
Communication Manager .
Accessing the registered MGC
on page 34
on page 34
Avaya Aura
®
Communication Manager software on a server. There
Media Gateway Controller configuration
on page 72.
®
Communication Manager access
on page 67.
October 2013
®
33