[Live-devel] RTSP RTP/AVP/TCP without interleaved appears to be treated as interleaved in LIVE555 2026.07.08

[曹博程]

Dear LIVE555 developers,
 
I am testing RTSP server behavior in LIVE555 and would like to confirm whether the following behavior is intended.
 
Tested target:
  LIVE555 Streaming Media version: 2026.07.08
  Target: testOnDemandRTSPServer
 
The request is:
  SETUP rtsp://127.0.0.1:8554/wavAudioTest RTSP/1.0
  CSeq: 10
  Transport: RTP/AVP/TCP;unicast
 
My understanding of RFC 7826 Appendix C.2.2 is that RTP/AVP/TCP without the interleaved parameter indicates RTP over independent TCP connections, not RTP interleaved over the RTSP control connection.
 
However, LIVE555 responds with:
  RTSP/1.0 200 OK
  CSeq: 10
  Transport: RTP/AVP/TCP;unicast;destination=127.0.0.1;source=127.0.0.1;interleaved=0-1
  Session: 06C35743;timeout=65
 
Then, without establishing any independent RTP/RTCP TCP connection, a subsequent PLAY returns:
  RTSP/1.0 200 OK
  CSeq: 11
  Range: npt=0.000-
  Session: 06C35743
  RTP-Info: url=rtsp://127.0.0.1:8554/wavAudioTest/track1;seq=0;rtptime=0
I repeated this locally 20 times, and the behavior was stable: the server always added interleaved=0-1, created asession, and accepted PLAY.
 
Could you please confirm whether this is intentional compatibility behavior, or whether RTP/AVP/TCP;unicast without interleaved should instead be handled as independent TCP transport?
From my reading, if independent TCP is accepted, the response should not add interleaved; and if the RTP/RTCP TCP connections have not been established, PLAY should receive 464 Data Transport Not Ready Yet.


Best regards,
Bocheng Cao








 曹博程
213220597 at seu.edu.cn




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20260709/dfbe260a/attachment.htm>