Bug ID 782353: SIP MRF via header shows TCP Transport when TLS is enabled

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,, 15.0.0, 15.0.1,,,,

Fixed In:

Opened: May 15, 2019

Severity: 3-Major


When an SSL Client Profile (TLS) is enabled on a SIP Message-Routing Virtual Server, the via header shows an incorrect transport protocol when SIP messages are sent out the client side of MRF. For example, the via header contains 'SIP/2.0/TCP' or 'SIP/2.0/UDP', when it should read 'SIP/2.0/TLS'.


The via header is not correct and violates the SIP RFC.


Sending SIP messages from the client side of the SIP MRF when an SSL client profile is enabled on the SIP Message-Routing virtual server.


Create an iRule that replaces the incorrect via header with a correct one, for example: when SIP_REQUEST_SEND { if { [clientside] } { SIP::header replace Via [string map [list "SIP/2.0/TCP " "SIP/2.0/TLS " "SIP/2.0/UDP " "SIP/2.0/TLS "] [SIP::header Via 0]] 0 } }

Fix Information

The via headers show the correct text (e.g., SIP/2.0/TLS) when an SSL Client Profile is enabled on a SIP Message-Routing virtual server.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips