▀ ICAP Interface Support Overview
Content Insert: Retransmitted packets are dropped and not charged.
Redirect: Retransmitted packets are dropped and not charged.
Discard: The uplink packet is sent for ICAP rating and depending on the ICAP response the WTP
Terminate flow: Retransmitted packets are dropped and not charged.
RTSP:
The following scenarios describe the failure actions where an RTSP request is received from the client. If
ICAP is enabled, then the request goes to the ICAP server for content filtering.
Allow: If the failure action configured is "allow", the RTSP request packet is sent out after applying the
Content Insert: If the failure action configured is "content-insertion <string of size 1 to 128>", then this
Redirect-URL: If the failure action configured is "redirect-url <string of size 1 to 128>", then a TCP
Discard: If the failure action configured is "discard", then the RTSP request packet received from the
Terminate flow: If the failure action configured is "terminate-flow", then the TCP connection is torn
Supported Networks and Platforms
This feature supports ST16 and Cisco Chassis for the core network services configured on the system.
License Requirements
External Content Filtering Server support through Internet Content Adaptation Protocol (ICAP) interface is a licensed
Cisco feature. A separate feature license may be required. Contact your Cisco account representative for detailed
information on specific licensing requirements.
For information on installing and verifying licenses, refer to the Managing License Keys section of the Software
Management Operations chapter in the System Administration Guide.
▄ Cisco ASR 5000 IP Services Gateway Administration Guide
142
transaction allowed/blocked.
appropriate disposition action. Here, the flow remains the same as in the case if the ICAP response
received is 200 OK.
failure action for RTSP request will not be supported. Instead the failure action "Discard" for such an
RTSP request will be supported.
FIN_ACK packet with an RTSP "302 Moved Temporarily" response header is inserted towards the
client containing the said URL for redirection. A TCP RST packet is inserted towards the server. The
underlying TCP connection is thus closed. If the RTSP client wants to retry to the redirected URL, the
opening of a new TCP connection must be initiated.
client is quietly discarded and no notification is sent to the client.
down by injecting a TCP FIN-ACK towards the client and a RST packet towards the server. However,
no notification will be sent to the RTSP client and the server regarding this flow termination.
ICAP Interface Support
OL-27210-02