Accessing the Avaya G350 Media Gateway
Managing login permissions
•
Telnet to port 5023 on the media server, using the following syntax:
media server> <5023>
Communication Manager, 555-233-506.
•
Avaya G350 Media Gateway CLI. See
Managing login permissions
This section explains how to manage login permissions and contains the following topics:
•
Security overview
in conjunction with a RADIUS authentication system
•
Managing users and passwords
instructions on how to define new users
•
SSH protocol support
SSH authentication parameters
•
SCP protocol support
SCP authentication parameters
•
RADIUS authentication
RADIUS server
Security overview
The Avaya G350 Media Gateway includes a security mechanism through which the system administrator
defines users and assigns each user and username and a password. Each user is assigned a privilege level.
The user's privilege level determines which commands the user can perform.
In addition to its basic security mechanism, the G350 supports secure data transfer via SSH and SCP.
The G350 can be configured to work with an external RADIUS server to provide user authentication.
When RADIUS authentication is enabled on the G350, the RADIUS server operates in conjunction with
the G350 security mechanism. When the user enters a username, the G350 first searches its own database
for the username. If the G350 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.
Managing users and passwords
You must provide a username and password when you perform any of the following actions:
•
When you access the CLI. For more information, see
•
When you connect to the console port modem with dialup PPP. For more information, see
Accessing CLI via modem
•
When you open Avaya G350 Manager.
When you use Avaya G350 Manager or the CLI, your username determines your privilege level. The
commands that are available to you during the session depend on your privilege level.
32
. For more information, see Administrator's Guide for Avaya
Accessing the registered MGC
— overview of the G350's internal security mechanism and how it can operate
— explanation of the users, passwords, and access privileges, and
— explanation of SSH authentication and instructions on how to configure
— explanation of SCP authentication and instructions on how to configure
— instructions on how to configure the G350 to work with an external
on page 27.
Administration of the Avaya G350 Media Gateway
telnet <IP address of the
on page 44.
Accessing the CLI
on page 25.
June 2004