Bug ID 601255: RTSP response to SETUP request has incorrect client_port attribute

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, 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

Fixed In:
13.0.0, 12.1.2 HF1, 11.6.1 HF2

Opened: Jun 24, 2016
Severity: 3-Major

Symptoms

- Clientside data is sent to UDP port 0 - RTSP response to SETUP request contains incorrect 'client_port' attribute (0)

Impact

Unicast media may forwarded to incorrect UDP port (0).

Conditions

- Virtual with RTSP profile. - 200/OK is received from server in response to the initial SETUP request - SETUP request was the initial message received on a new connection

Workaround

None

Fix Information

Initialize 'client_port' attribute to value received from server when re-writing response to client.

Behavior Change