Bug ID 747187: SIP falsely detects media flow collision when SDP is in both 183 and 200 response

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,, 14.0.0,,,,,, 14.0.1, 14.1.0,

Fixed In:

Opened: Oct 18, 2018

Severity: 3-Major


A spurious error message is logged ("MR SIP: Media flow creation (...) failed due to collision") and media does not flow.


Media does not flow on pinholes for which a collision was detected and reported.


A SIP server responds to an INVITE with both a 183 "Session Progress" and later a "200 OK" for a single SIP call, and both responses contain an SDP with the same media info.



Fix Information

No collision is detected or logged when multiple messages with SDP recreate the same flows in the same call.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips