Cisco Cisco ASR 5700
ACS Configuration Mode Commands
▀ idle-timeout
▄ Command Line Interface Reference, StarOS Release 17
508
If the Flow Mapping timer is disabled, then the Mapping timeout will not get triggered for UDP/TCP idle
timed out flows. The resources such as NAT mapping will be released along with the 5-tuple flow.
timed out flows. The resources such as NAT mapping will be released along with the 5-tuple flow.
icmp
Configures the ICMP protocol for the specified flow.
tcp [ half-open ]
Configures the TCP protocol for the specified flow.
Use the
Use the
half-open
keyword to configure timeout interval for half-open TCP flows.
udp
Configures the UDP protocol for the specified flow.
idle_timeout
Specifies the timeout duration, in seconds, and must be an integer from 0 through 86400.
For
For
alg-media
specifies the media inactivity timeout. The
idle_timeout
value gets applied on RTP and
RTCP media flows that are created for SIP/H.323 calls. The timeout is applied only on those flows that
actually match the RTP and RTCP media pinholes that are created by the SIP/H.323 ALG.
A value of 0 disables the idle-timeout setting.
actually match the RTP and RTCP media pinholes that are created by the SIP/H.323 ALG.
A value of 0 disables the idle-timeout setting.
Usage
Use this command to configure the maximum duration a flow can remain idle, in seconds, after which the
system automatically terminates the flow.
Setting the value to 0 will cause the idle-timeout setting to be disabled.
For flows other than TCP, UDP and ICMP, timeout value will always be 300 seconds (unless configured in
the charging-action). Charging action’s flow idle-timeout will have precedence over ACS idle-timeout. If
charging action’s flow idle-timeout is default, then flows will have the value configured in the active
charging service.
system automatically terminates the flow.
Setting the value to 0 will cause the idle-timeout setting to be disabled.
For flows other than TCP, UDP and ICMP, timeout value will always be 300 seconds (unless configured in
the charging-action). Charging action’s flow idle-timeout will have precedence over ACS idle-timeout. If
charging action’s flow idle-timeout is default, then flows will have the value configured in the active
charging service.
Example
The following command configures the maximum duration a TCP flow can remain idle to
3000
seconds,
after which the system automatically terminates the flow:
idle-timeout tcp 3000