[Live-devel] Regarding QoS and RTPTransmissionStat

[Ross Finlayson]

> On Oct 20, 2026, at 1:06 AM, MANDJUKOWSKI Esteban via live-devel <live-devel at us.live555.com> wrote:
> 
> There are several points where I am struggling to understand how I should approach my goal while using live555 latest release (2026.10.17) : 
> 
> - Iterating over the RTPTransmissionStats for each QoSRTSPClientSession gives me duplicates

I’m not sure what you mean by “duplicates”.  The “RTPTransmissionStats” database is indexed by SSRC, which (the “SSRC()” field in “RTPTransmissionStats”) should be different for each client.


> - How to correlate the RTSPClientConnection (where I can easily get the IP address) and the different RTPTransmissionStats from RTPSinks

I’m not sure what you are asking for here.  There is not a 1-to-1 mapping from “RTSPClientSession” to “RTSPClientConnection”, because it is possible for multiple RTSP TCP connections (each represented by a “RTSPClientConnection”) to be used to perform operations within a single RTP Session (“RTSPClientSession”).  What specifically do you want to do?  (Note that you can use the “RTPTransmissionStats::lastFromAddress()” method to get the most recent IP address and port used by each SSRC.)


> - How to display the correct IP address when the client is using TCP (even if frowned upon...) : since stats->lastFromAddress seems to be 0.0.0.0 (only for TCP of course)

Sorry, I don’t have a solution here.  (Once again, a reminder that RTP/RTCP-over-TCP should be used only if you have a firewall - between the server and client - that blocks UDP packets.)


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/