Manual Chapter :
The effect of message pipelining on iRule
variables
Applies To:
Show Versions
BIG-IP LTM
- 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
The effect of message pipelining on iRule
variables
SIP can pipeline messages by allowing messages that require less processing to be forwarded
without waiting for earlier messages that require more processing. For this reason, it is not
recommended to store state in tcl variables to be used by subsequent iRule events. There is no
guarantee that the next event raised after the protocol's message event will be the MR_INGRESS
for the same message. For example, saving the SIP uri in a tcl variable during a SIP_REQUEST
event to use for making a routing decision during MR_INGRESS is not recommended. The next
MR_INGRESS event may not be for the same message as the last SIP_REQUEST event.
MRF SIP implementation allows accessing the SIP iRule commands during the MR events. This is
the recommended method to make routing and delivery decisions based on attributes of a message.
For example:
when MR_INGRESS { if {[URI::host [SIP::uri]] equal "othersp.com"} { MR::message route config "/Common/othersp_tc" pool "/Common/othersp_pool" } }
