Cisco Cisco IOS Software Release 12.2(2)XA
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
mgcp quarantine mode
53
Cisco IOS Release 12.2(2)XA
mgcp quarantine mode
To configure event quarantine buffer handling mode, use the mgcp quarantine mode global
configuration command. To restore the default value, use the no form of the command.
configuration command. To restore the default value, use the no form of the command.
mgcp quarantine mode {discard [loop | step] | process [loop | step] | loop | step}
no mgcp quarantine mode {discard [loop | step] | process [loop | step] | loop | step}
Syntax Description
Defaults
discard and step
Command Modes
Global configuration
Command History
Usage Guidelines
Quarantine events are defined as events that have been detected by the gateway before the arrival of the
MGCP NotificationRequest command, but that have not yet been notified to the call agent. They are
held in the quarantine buffer until receipt of the MGCP NotificationRequest command, when the
gateway is expected to generate either one notification (step by step), or multiple notifications (loop),
in response to this request (the default is exactly one), based on the configuration of mgcp quarantine
mode.
MGCP NotificationRequest command, but that have not yet been notified to the call agent. They are
held in the quarantine buffer until receipt of the MGCP NotificationRequest command, when the
gateway is expected to generate either one notification (step by step), or multiple notifications (loop),
in response to this request (the default is exactly one), based on the configuration of mgcp quarantine
mode.
This command supports backward compatibility with SGCP implementations running under the MGCP
application. SGCP does not have a way to allow the call agent to control the quarantine mode. MGCP
has this functionality.
application. SGCP does not have a way to allow the call agent to control the quarantine mode. MGCP
has this functionality.
When the gateway is in the notification state, the interdigit timer (Tcrit) is not started.
discard
Enables discarding of quarantined events instead of processing: observed
events are not reported to the call agent, even if the call agent is ready to
receive them.
events are not reported to the call agent, even if the call agent is ready to
receive them.
loop
Enables loop mode for quarantined events instead of stepping: after
receiving a request from the call agent, the gateway reports the observed
events to the call agent in multiples without waiting for subsequent
requests.
receiving a request from the call agent, the gateway reports the observed
events to the call agent in multiples without waiting for subsequent
requests.
process
Enables processing of quarantined events instead of discarding: observed
events are reported to the call agent when the call agent is ready to receive
them.
events are reported to the call agent when the call agent is ready to receive
them.
step
Enables step mode for quarantined events instead of looping: after receiving
a request from the call agent, the gateway reports observed events
individually to the call agent, one for each request.
a request from the call agent, the gateway reports observed events
individually to the call agent, one for each request.
Release
Modification
12.1(5)XM
This command was introduced.
12.2(2)XA
Support for MGCP was added.