Status in source: current.
Names: mgcpFwKeepAliveEnable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mgcpFwKeepAliveEnable",
"OBJECT-TYPE",
"SYNTAX",
"MxEnableState",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Enable/disable the Firewall keep-alive timeout mechanism. When Media Gateways (MGW) controlled with the MGCP protocol are deployed behind firewalls, the Media Gateway Controller (MGC) should be allowed to control the MGW. To keep the firewall and NAT connection alive, signalling packets must be exchanged between the MGW and MGC within a specified period of time called the keep-alive timeout. If no packets are exchanged for the specified period, then the connection will be closed. To keep the connection alive, the gateway uses the RSIP RM : x-keepalive command to indicate that the gateway inactivity timer has timed-out. The RSIP keep-alive command is sent from a provisionable virtual endpoint. The RSIP keep-alive command does not require any 200 OK from the Media Gateway controler (MGC). The RSIP keep-alive is launched immediately after the activation of the MGCP stack. It is then possible to see RSIP keep-alive command preceeding the initial RSIP restart if the registration initial delay period is larger than the inactivity timer. Also, the RSIP keep-alive is not submitted to the disconnection procedure. Note that voice packets cannot be used to keep the connection opened because they are transmitted on another channel.\"",
"DEFVAL",
"{",
"disable",
"}",
"::=",
"{",
"mgcpFirewall",
"5",
"}"
],
"syntax_tree": [
[
"row",
"MxEnableState"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Enable/disable the Firewall keep-alive timeout mechanism. When Media Gateways (MGW) controlled with the MGCP protocol are deployed behind firewalls, the Media Gateway Controller (MGC) should be allowed to control the MGW. To keep the firewall and NAT connection alive, signalling packets must be exchanged between the MGW and MGC within a specified period of time called the keep-alive timeout. If no packets are exchanged for the specified period, then the connection will be closed. To keep the connection alive, the gateway uses the RSIP RM : x-keepalive command to indicate that the gateway inactivity timer has timed-out. The RSIP keep-alive command is sent from a provisionable virtual endpoint. The RSIP keep-alive command does not require any 200 OK from the Media Gateway controler (MGC). The RSIP keep-alive is launched immediately after the activation of the MGCP stack. It is then possible to see RSIP keep-alive command preceeding the initial RSIP restart if the registration initial delay period is larger than the inactivity timer. Also, the RSIP keep-alive is not submitted to the disconnection procedure. Note that voice packets cannot be used to keep the connection opened because they are transmitted on another channel."
],
null,
null,
null,
[
"DEFVAL",
"disable"
]
]
}