1. Home
    2. /
  2. Manuals
    3. /
  3. Allied-Telesis
    4. /
  4. AT-iMG624A
    5. /
  5. 114
Page 566 / 998 Scroll up to view Page 561 - 565
VoIP MGCP
Piggyback
iMG/RG Software Reference Manual (Voice Service)
6-2
6.1.1.2 Custom endpoints syntax
iMG/RG/iBG devices allow analog endpoint MGCP identifiers to be customized to meet VoIP network configu-
ration requirements.
The syntax of each endpoint identifier can be set to any string but must include at least a local name description
in the format:
aaln/<slot>
The local and domain name part of an endpoint identifier can use also special keywords identified by the “$”
sign that are automatically replaced by the value of the attribute that they represent.
The following two special keywords are supported:
$IP - when used, this keyword is automatically replaced by the ip address value (in IPv4 dotted format) of the ip
interface where MGCP protocol has been enabled.
$MAC - when used, this keyword is automatically replaced by the MAC address of the iMG/RG/iBG device.
It’s therefore possible create complex endpoint identifiers like the following:
aaln/0@[$IP] that will be translated at runtime for example in: aaln/0@[172.30.1.1]
aaln/0@$IP that will be translated at runtime for example in: aaln/[email protected]
aaln/0@$MAC that will be translated at runtime for example in: aaln/0@00:0d:da:01:fe:ac
$MAC:aaln/0@[$IP] that will be translated at runtime for example in: 00:0d:da:01:fe:ac:aaln/0@[172.30.1.1]
aaln/0@any-string-here
To specify a new endpoint syntax for an existing voice port the following command is used:
voip mgcp protocol set endpoint-syntax <ep-syntax> port <voice-port>
where
<ep-syntax> is the endpoint identifier string as described above
<voice-port> is the name of the physical voice port (tel1, tel2,...)
6.1.2
Piggyback
iMG/RG/iBG devices support piggy-back MGCP message handling.
As reported in RFC 2705, piggy-back refers to the support for a Call Agent to send several messages at the
same time to the same gateway using the same UDP packet and separating each MGCP message by a line of
text that contain a single dot.
Support for piggy-back is enabled by default on MG/RG/iBG devices and can be disabled/enabled via the follow-
ing command:
voip mgcp protocol set piggyback disable|enable
Page 567 / 998
Wildcard
VoIP MGCP
6-3
iMG/RG Software Reference Manual (Voice Service)
6.1.3
Wildcard
MG/RG/iBG support wild card endpoint identifiers.
By default wild card support is disabled.
It can be enabled/disabled via the following CLI command:
voip mgcp protocol set wildcard enable|disable
When wild card support is enabled, MG/RG/iBG replace the local name description part of the endpoint identi-
fier with the “*” char on RSIP messages.
In this case only one RSIP message is sent in order to notify to the call agent that all the endpoints have been
taken out-of-service and are being replaced in service.
6.1.4
Heartbeat
iMG/RG/iBG support the heartbeat mechanism to detect whether User Agents are still active.
Each iMG/RG/iBG voice port has a unique User Agent permanently associated to it.
Heartbeat mechanism is typically requested on deployments that use Network Address Translation (NAT).
The reason for this requirement is that if a NAT binding expires, there is no way for a Call Agent to send an
incoming call to the User Agent as NAT bindings are generated via outgoing UDP packets.
Using a heartbeat mechanism allows the User Agent to detect loss of the NAT binding (due for example to DSL
uplink fails) and recreate it if required.
The heartbeat mechanism is implemented through the use of Audit commands as AuditConnection and Audi-
tEndpoint
iMG/RG/iBG User Agents support a configurable heartbeat timer. The User Agent then waits for either the end
of this timer, the reception of a command for the endpoint from the Call Agent, or the detection of a local user
activity for the endpoint, such as for example an off-hook transition.
If the heartbeat timer expires the User Agent enters the “disconnected” procedure.The User Agents run a fur-
ther disconnect timer and if they do not receive a command from the Call Agent or detect local activity before
the timer expires, the User Agent sends an RSIP disconnected command to the Call Agent.
If it does not receive a response it continues to periodically retry to contact the provisioned Call Agents.
If the Call Agent is using the above heartbeat mechanism, the heartbeat timer should be set to a value that
allows the Call Agent to send an audit command sufficiently often that the User Agent will see at least 3 audit
commands in the heartbeat time interval. This is to prevent a single packet loss causing the User Agent to
become “disconnected”.
By default heartbeat is disabled and can be enabled via the following command:
voip mgcp protocol set heartbeat enable|disable
Page 568 / 998
VoIP MGCP
Call Agent Failover
iMG/RG Software Reference Manual (Voice Service)
6-4
When heartbeat is enabled, each endpoint (or User Agent) supervises the operative status of Call Agent
inde-
pendently on the status of the other endpoints.
It’s possible force a specific User Agent to check for Call Agent activity and to be master also for the other
User Agents. If the specific endpoint does not receive a command from the Call Agent within the heartbeat
timer time-out it forces all the User Agents to enter into the disconnected procedure.
To activate this behavior is necessary enable the heartbeat and then enter the following command:
By default heartbeat is disabled and can be enabled via the following command:
voip mgcp protocol set heartbeat port <endpoint-name>
To return to the default behavior is necessary disable the heartbeat and then re-enabling it.
6.1.5
Call Agent Failover
iMG/RG/iBG support dual Call Agents failover mechanism to switch between inactive to active call agents in
order to support high availability services.
The failover mechanism is triggered any time a request sent by the User Agents does not get any answer from
the Call Agent within the round-trip time-out.
In this case if more than one call agent is configured, the User Agent will re-send the same command toward
the second call agent. As soon the User Agent get an answer from the second call agent, the second call agent
becomes the active call agent and will be used for all the subsequent requests.
The process repeats any time a call agent is not reachable switching in this way the communications
between
primary call agent to secondary call agent and vice versa.
It’s possible display the current active call agent checking the marker “*” character on the call agent list.
The active call agent is the call agent marked with the
“*” char.
By default the first call agent in the call agents list is the call agent that iMG/RG/iBG will attempt to contact
firstly.
It’s possible changing the call agent order of preference specifying the attribute master:
voip mgcp callagent set <call-agent-name> master
Only one call agent at time can be master.
6.1.6
Functional Differences for VoIP MGCP in Product Categories
The table below is intended to identify what is common amongst the product families - as well as where there
are differences - to highlight those differences. To determine which family your device belongs to - please refer
to the preface.
Page 569 / 998
VOIP MGCP command reference
VoIP MGCP
6-5
iMG/RG Software Reference Manual (Voice Service)
6.1.7
VOIP MGCP command reference
This section describes the commands available on iMG/RG/iBG to configure and manage the MGCP protocol
module.
6.1.7.1 VoIP MGCP CLI commands
The table below lists the
voip mgcp
commands provided by the CLI:
TABLE 6-1
Functional Mapping for VoIP MGCP
Functions
Fiber
A
Fiber
B
Fiber
C
Fiber
D
Fiber
E
Modular
ADSL
A
ADSL
B
ADSL
C
Endpoints
X
X
X
X
X
X
X
X
X
Piggyback
X
X
X
X
X
X
X
X
X
Wildcard
X
X
X
X
X
X
X
X
X
Heartbeat
X
X
X
X
X
X
X
X
X
Call Agent Failover
X
X
X
X
X
X
X
X
X
TABLE 6-2
VoIP MGCP
commands
Functions
Fiber
A
Fiber
B
Fiber
C
Fiber
D
Fiber
E
Modular
ADSL
A
ADSL
B
ADSL
C
VOIP MGCP PROTOCOL DISABLE
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL ENABLE
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL RESTART
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET DEFAULTPORT
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET HEARTBEAT
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET NAT
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET NETINTERFACE
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET PIGGYBACK
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET PROFILE
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SET REFRESH-TIME
X
X
X
X
X
X
X
X
X
Page 570 / 998
VoIP MGCP
VOIP MGCP command reference
iMG/RG Software Reference Manual (Voice Service)
6-6
6.1.7.1.1 VOIP MGCP PROTOCOL DISABLE
Syntax
VOIP MGCP PROTOCOL DISABLE
Description
This command stops the VoIP MGCP signalling protocol and releases all the resources
associated to it.
This command is typically used when it's necessary to change the VoIP signalling proto-
col, i.e. from MGCP to SIP.
To simply restart the MGCP module, use the VOIP MGCP PROTOCOL RESTART com-
mand. It doesn't remove any resources defined for the protocol.
To enable the MGCP module, use the VOIP MGCP PROTOCOL ENABLE command.
Example
--> voip mgcp protocol disable
See also
VOIP MGCP PROTOCOL RESTART
VOIP MGCP PROTOCOL ENABLE
6.1.7.1.2 VOIP MGCP PROTOCOL ENABLE
Syntax
VOIP MGCP PROTOCOL ENABLE
Description
This command turns on the MGCP signaling module.
To bind the MGCP module to a specific IP interface use the VOIP MGCP PROTOCOL
SET NETINTERFACE command.
Binding the MGCP module to a specific IP interface defines the value of the source IP
address for signalling and voice packets.
VOIP MGCP PROTOCOL SET ROUNDTRIPTIME
X
X
X
X
X
X
X
X
X
VOIP MGCP PROTOCOL SHOW
X
X
X
X
X
X
X
X
X
VOIP MGCP CALLAGENT CREATE
X
X
X
X
X
X
X
X
X
VOIP MGCP CALLAGENT SET MASTER
X
X
X
X
X
X
X
X
X
VOIP MGCP CALLAGENT DELETE
X
X
X
X
X
X
X
X
X
VOIP MGCP CALLAGENT LIST
X
X
X
X
X
X
X
X
X
TABLE 6-2
VoIP MGCP
commands
(Continued)
Functions
Fiber
A
Fiber
B
Fiber
C
Fiber
D
Fiber
E
Modular
ADSL
A
ADSL
B
ADSL
C

Rate

4 / 5 based on 3 votes.

Popular Allied-Telesis Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top