Cisco Cisco IOS Software Release 12.2(2)XA
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
mgcp piggyback message
49
Cisco IOS Release 12.2(2)XA
mgcp piggyback message
To enable piggyback messages, use the mgcp piggyback message global configuration command. To
disable piggyback messages, use the no form of this command.
disable piggyback messages, use the no form of this command.
mgcp piggyback message
no mgcp piggyback message
Syntax Description
This command has no keywords or arguments.
Defaults
Piggyback messages are enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to disable piggyback messages for MGCP 1.0, NCS, and TGCP when a network
gateway cannot handle piggyback messages. Piggyback messaging is not available to SGCP and
MGCP 0.1.
gateway cannot handle piggyback messages. Piggyback messaging is not available to SGCP and
MGCP 0.1.
The term piggyback message refers to a situation in which a gateway or a call agent sends more than
one MGCP message in the same UDP packets. The recipient processes the messages individually, in the
order received. However, if a message must be retransmitted, the entire datagram is resent. The recipient
must be capable of sorting out the messages and keeping track of which messages have been handled
or acknowledged.
one MGCP message in the same UDP packets. The recipient processes the messages individually, in the
order received. However, if a message must be retransmitted, the entire datagram is resent. The recipient
must be capable of sorting out the messages and keeping track of which messages have been handled
or acknowledged.
Piggybacking is used during retransmission of a message to send previously unacknowledged messages to
the call agent. This maintains the order of events the call agent receives, and makes sure that RSIP
(RestartInProgress) messages are always received first by a call agent.
the call agent. This maintains the order of events the call agent receives, and makes sure that RSIP
(RestartInProgress) messages are always received first by a call agent.
Examples
The following example illustrates how to disable piggyback messages:
Router(config)# no mgcp piggyback message
Related Commands
Release
Modification
12.2(2)XA
This command was introduced.
Command
Description
mgcp
Starts and allocates resources for the MGCP daemon.