Specifications

AT-VP504E FXS 109
13
Signalling Protocol
Configuration – MGCP
This chapter describes how to set information exclusive to the MGCP
signalling protocol. This chapter assumes that the AT-VP504E FXS
communication unit currently runs the MGCP protocol or that you will
switch the unit to this protocol. The MGCP signalling programs and
information are defined in a MGCP stack. This includes Call Agent
information and addresses, media package settings, etc.
Introduction When the AT-VP504E FXS communication unit runs the MGCP
protocol, it uses the
MGCP MIB . This MIB is located in the Allied
Telesyn MIB architecture. See “MIB Structure” on page 8 for more
details.
Your unit must run the MGCP protocol or you must switch to this
protocol.
To use the MGCP MIB
1. In the Provisioning MIB, locate the signalingProtocolsSwitch
variable under the
signalingProtocolsGroup .
This variable allows you to switch from one protocol to
another.
2. Set the signalingProtocolsSwitch variable to 0=MGCP .
The default value is 1=SIP. The AT-VP504E FXS
communication unit reboots automatically. After the unit
restarts, it will use the MGCP MIB. You will be able to set the
parameters specific to this signalling protocol.
MGCP
Information
The AT-VP504E FXS uses MGCP version draft-huitema-megaco-
mgcp-v0r1-05. MGCP is a protocol for controlling Voice over IP (VoIP)
Gateways from intelligent external call control elements. MGCP uses
the Master/Slave concept, where external call control elements are the
Masters, while the devices connected to them (such as the
AT-VP504E FXS), are the Slaves and only obey orders given by the
Master.
The AT-VP504E FXS is used with any MGCP Call Agent (also known
as Connection Manager), which manages calls from and to the
AT-VP504E FXS.