RTSP_REQUEST¶

Description¶

Triggered after a complete request has been received from either the client or the server. You can use the RTSP::msg_source command to determine if the message originated from the client or server.

Examples¶

when RTSP_REQUEST {
  # In Progress: Add Sample Code Here
}

Related Information¶

Available Commands:

clone - Causes the system to clone traffic to the specified pool or pool member regardless of monitor status.
forward - Sets the connection to forward IP packets.
IP::idle_timeout - Returns or sets the idle timeout value.
ip_ttl - Returns the TTL of the latest IP packet received.
lasthop - Sets the lasthop of an IP connection.
listen - Sets up a related ephemeral listener to allow an incoming related connection to be established.
LSN::address - Set or override translation address.
LSN::disable - Disable LSN translation.
LSN::inbound - Disable inbound connections to translation address/port.
LSN::persistence - Set translation selection mode and persistence timeout.
LSN::persistence-entry - Create or lookup translation address.
LSN::pool - Specify LSN pool for current connection.
LSN::port - Set or override translation port.
nexthop - Sets the nexthop of an IP connection.
node - Sends the packet directly to the identified server node.
peer - Causes the specified iRule commands to be evaluated under the peer’s (opposite) context.
persist - Causes the system to use the named persistence type to persist the connection.
pool - Causes the system to load balance traffic to the specified pool or pool member regardless of monitor status.
session - Utilizes the persistence table to store arbitrary information based on the same keys as persistence.

Warning

The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.

Sample Code:

Introduced: BIGIP-9.4.3 (BIGIP-9.2.0 with EA license)

The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.