Cisco Systems OL-15491-01 appendix Idle CSG2 content, Idle duration no idle duration

Appendix A CSG2 Command Reference

idle (CSG2 content)

idle (CSG2 content)

To specify the minimum amount of time that the CSG2 maintains an idle content connection, use the idle command in CSG2 content configuration mode. To restore the default idle duration value, use the no form of this command.

idle duration no idle duration

Syntax Description	duration	Content idle timer duration in seconds. If no packets are received on a content
		connection for more than duration seconds, the CSG2 assumes the connection is idle
		and ends the connection.
		The range is from 4 to 65535. The default is 300.
Defaults	The default idle duration is 300 seconds (5 minutes).
Command Modes	CSG2 content configuration
Command History	Release	Modification
	12.4(11)MD	This command was migrated from CSG1.
		Changes from CSG1: The default setting for the duration argument changed from
		3600 seconds to 300 seconds.
Usage Guidelines	Real Time Streaming Protocol (RTSP) billing in the CSG2 is based on inspection of the RTSP SETUP
	and TEARDOWN messages that are exchanged between the subscriber and network. The CSG2 builds

the RTSP call detail record (CDR) immediately after the RTSP TEARDOWN signal if the URL exactly matches that from the RTSP SETUP signal. Otherwise, the CSG2 builds the CDR after any condition that causes the flows to be terminated, as when a service_stop is triggered (for example, when the access network sends a RADIUS Accounting Stop for the subscriber).

For RTSP, do not set the idle timer duration to less than 60 seconds.

When using HTTP as the transport for RTSP, the control connection is used sparingly and might time out, causing the stream to become unresponsive. This occurs because the subscriber opens two TCP connections, one for the main content and one for control. The subscriber uses the control connection sparingly, which can cause the connection to time out. To prevent this problem, ensure that the content idle timer has a duration of at least 60 seconds (the default setting is 300 seconds). This is not an issue when using UDP or TCP as the transport.

The CSG2 tracks usage on a per-session basis. User Datagram Protocol (UDP) does not have an end-of-session indicator and simply idles out. For that reason, for UDP and wireless application protocol 1.x (WAP 1.x), setting the content idle timer to a low value (for example, 30) allows the CSG2

	Cisco Content Services Gateway - 2nd Generation Release 2.0 Installation and Configuration Guide
A-36	OL-15491-01