Authorization Check Of Call Manager Ip Addresses; Support Of Diffserv Capabilities; Handling Events; Playing Signals - AudioCodes Mediant 1000 User Manual

User's Manual
7.2.2.4

Authorization Check of Call Manager IP Addresses

While the MEGACO specification specifies that only one Call Manager can send
commands to the gateway at a time, AudioCodes gateways handle the Authorization
Check in either of these modes:
No authorization check is performed. This mode specifies that every command is
1.
accepted and executed.
The IP address of the Call Manager sending the incoming command is checked
2.
against the list of provisioned Call Managers. If it matches one on the list, the
command is executed. If The Call Manager' IP Address is not found on the list, an
error message is sent. This mode is set as the default.
These two modes are controlled by the ini file parameter 'MEGACOCheckLegalityOfMGC',
for which the default value is 1.
7.2.2.5

Support of DiffServ Capabilities

The DiffServ value of the IP header can be set for both the control path and the media
path. The range of the DiffServ parameter is between 0 and 63. It enables routers to
differentiate between different streams. The values are set via SNMP, Web or ini file
parameter. Note, that changing the value of the control path requires the Gateway to be
reset.
The value of the control path is set via the ini file parameter 'ControlDiffServ', and the value
for the media path is set via the ini file parameter 'IPDiffServ'.
7.2.2.6

Handling Events

Events are declared in an EventsDescriptor that has an ID and a list of events on which the
Call Agent requires notification. Up to 16 events can be defined in the descriptor. Wildcards
are permitted in the events names. For example, if the list includes dd/*, and the user
presses the number 1, the Call Agent receives notification when the digit starts
(dd/std{tl=d1}) and when it ends (dd/etd{tl=d1}). The event dd/d1 is not sent, as it is
included in the other two. An event can have parameters, for example, the KeepActive flag.
When the event having the KeepActive flag is received, it does not stop the currently
played signals.
An event can have an embedded descriptor in it. It can be a SignalsDescriptor (refer to
"Playing Signals" below), a new EventDescriptor, or both. The embedded descriptor
replaces the current descriptor.
7.2.2.7

Playing Signals

Signals in MEGACO reside in a SignalsDescriptor. Only one signal is allowed in the
descriptor as the Mediant 1000s cannot play more than one signal at a time. However, this
one signal can be of the SignalList type. In which case, there can be up to 30 signals in the
list, and they are played sequentially until the list ends or the execution is interrupted.
Interrupting the execution can be one of the following:
Event - Only events required by the Call Agent stop the execution, and only if they do
not have the KeepActive flag.
New Signals Descriptor - Stops the execution, unless the same signal is received, and
it has a KeepActive flag. If the old signal and the new signal are both signal lists and
Version 4.6 81
7. Standard Control Protocols
August 2005