Administering Call-Processing; Setting Alternate Gatekeeper List (Agl) Priorities - Avaya Communication Manager Administrator's Manual

load is unique to each interface and is the ratio of currently used sockets to the number
administered in this field. Communication Manager tries to keep the ratio used by each
interface the same. Note that this is a "target" level, and that Communication Manager
might use more sockets than specified in the field.
If there is only one ip-interface within a priority, the Target socket load or the Target
socket load and Warning level field is no longer used for load balancing. A number can be
entered in this field to receive an error or a warning alarm if the targeted value is exceeded.

Setting Alternate Gatekeeper List (AGL) priorities

The alternate gatekeeper list is used for H.323 endpoints when they cannot reach their primary
gatekeeper. The
screen determines the priority of the PE interface or the CLAN on the alternate gatekeeper list.
For more information about the Gatekeeper Priority field, see
page 586.

Administering Call-processing

The telephony features of the S8300 Media Server are administered using the same commands
and procedures as an S8700 Series Media Server or a legacy DEFINITY Enterprise
Communications System.
Accessing Avaya Communication Manager
Avaya Communication Manager resides on the media server. It can be accessed through either
Avaya Site Administration (ASA) or the System Access Terminal (SAT) program.
Avaya Site Administration
Avaya Site Administration features a graphical user interface (GUI) that provides access to SAT
commands as well as wizard-like screens that provide simplified administration for frequently
used features. You can perform most of your day-to-day administration tasks from this interface
such as adding or removing users and telephony devices. You can also schedule tasks to run at
a non-peak usage time. ASA is available in several languages.
Gatekeeper Priority field and the Network Region
Administering Call-processing
field on the IP Interfaces
Using load balancing
Issue 2.1 May 2006
on
587