Bug ID 741951: Multiple extensions in SIP NOTIFY request cause message to be dropped.

Last Modified: Oct 07, 2023

Affected Product(s):
BIG-IP PSM, SWG, TMOS, vCMP(all modules)

Known Affected Versions:
11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed In:
15.0.0, 14.1.0, 14.0.0.5, 13.1.1.4, 12.1.5.2, 11.6.5.2

Opened: Aug 28, 2018

Severity: 3-Major

Symptoms

When SIP NOTIFY messages are sent with a request URI that contains multiple client extensions, the system does not forward the message as expected.

Impact

NOTIFY message is not forwarded.

Conditions

SIP NOTIFY messages sent with a request URI that contains multiple client extensions.

Workaround

None.

Fix Information

Improved SIP URI parser now correctly handles multiple extensions in a URI.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips