Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.3.0, 11.4.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.10, 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
Opened: Sep 20, 2013
Related AskF5 Article: K15562
RTSP established media flows will not have their public translation address and ports logged in the same way LSN translations do.
Media flows will not be able to be used to identify subscribers.
This occurs when an RTSP ALG profile is configured with an lsn-pool and there are RTSP RTP flows.
RTSP ALG when used with CGNAT, the media connections now have the data session translation address:port logged as LSN translations.
ALGs now have an option enabled by db variable to log the messages and media/data connections so that they can be traced to an LSN subscriber.