Bug ID 613023: Update SIP::Persist to support resetting timeout value.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(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, 11.6.1 HF2, 11.6.2, 11.6.2 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, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5

Fixed In:
13.0.0, 12.1.3.6, 11.6.3

Opened: Aug 26, 2016
Severity: 3-Major

Symptoms

SIP::persist needs improvement to support long-lived SIP sessions. Having a long timeout for persistence entries globally does not seem efficient for resource usage.

Impact

Smaller persist timeouts will result in messages being delivered to the wrong entity in the case of supporting long lived SIP sessions.

Conditions

Efficiently using long-lived SIP sessions.

Workaround

Set a higher persist timeout value globally. Note: This workaround might result in memory issues, depending on the BIG-IP system setup and traffic.

Fix Information

New SIP Persist iRule commands allow persistence key and an additional parameter to redefine lifetime of the persistence entry to any new value.

Behavior Change

In previous versions, the SIP Persist iRule command allowed only the persistence key as the parameter to store the persistence entry in the table. New SIP Persist iRule commands allows persistence key and an additional parameter to define the lifetime of persistence entry. BIG-IP systems now can have better control on the persistence entry for long lived SIP sessions.