Avaya Media Gateway G250, Administration Manual

Page: 49 / 840

Accessing Avaya Communication Manager
Issue 5 June 2008 49
Accessing Avaya Communication Manager
Use Avaya Communication Manager software to control telephone services that the Avaya
G250/G350 Media Gateway provides. Run the Avaya Communication Manager software on a
server. There might be several servers on your network that can control the Avaya G250/G350
Media Gateway. Access Avaya Communication Manager on any server that is a Media
Gateway Controller (MGC) for the Avaya G250/G350 Media Gateway. For more information,
see
Configuring the Media Gateway Controller (MGC) on page 92.
Access Avaya Communication Manager with any of the following:
●
Avaya Site Administration (ASA) . ASA provides wizards and other tools that help you to
use Avaya Communication Manager effectively. For more information, see Administrator
Guide for Avaya Communication Manager , 03-300509.
●
SSH to port 5023 on the MGC . For more information, see Administrator Guide for Avaya
Communication Manager , 03-300509.
●
Avaya G250/G350 Media Gateway CLI . See Accessing the registered MGC on page 97.
Managing login permissions
You can manage login permissions to enable different privilege levels for each user and to
operate the security mechanism.
Security overview
The Avaya G250/G350 Media 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 G250/G350 supports secure data transfer via
SSH and SCP.
The G250/G350 can be configured to work with an external RADIUS server to provide user
authentication. When RADIUS authentication is enabled on the G250/G350, the RADIUS server
operates in conjunction with the G250/G350 security mechanism. When the user enters a
username, the G250/G350 first searches its own database for the username. If the G250/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.