Bug ID 428618: Route responses based on topmost via header port information.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.2.0, 11.3.0, 11.4.0, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:

Opened: Aug 22, 2013
Severity: 3-Major


A pool member's response back to a client via an existing connection flow (connflow) ends up using the existing client-side connflow.


Violation of the SIP RFC 3261, in routing the responses, actual client may not receive the response.


Proxying a pool member's response back to a client via an existing connflow.


Send response to the same client that initiated the request with the same port.

Fix Information

Response routing is possible now based on topmost Via header information, if the existing client-side connflow does not exist or honor-via config option is enabled in sipsession profile in MR framework.

Behavior Change