Bug ID 599521: Persistence entries not added if message is routed via an iRule

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2, 11.6.1 HF2

Opened: Jun 15, 2016
Severity: 3-Major


MRF SIP route table implementation does not add a persistence entry if the message was routed via an iRule.


Since MRF SIP persistence may be bidirectional, not having the persistence entry will keep message flowing in the opposite direction from being automatically routed via persistence.


If the message is routed via an iRule, a SIP persistence entry will not be created.


An iRule could be used to route messages directed towards the original client.

Fix Information

MRF SIP will add a persistence entry for message routed via an iRule.

Behavior Change