> On Jul 18, 2024, at 4:19 PM, Derrick N. Guerrero wrote:
>
> > You can see from the code that a RTSP client will use whatever
> > “client_port” value is specified by the server in a RTSP SETUP response.
I was wrong about this. Our RTSP client does, indeed parse the “client_port”
in the SET
> However, common sense suggests that the server should choose a value that was
> in the range specified by the client.
Thanks for confirming that this violates common sense. I had looked for
references to client_port and SETUP and could not find anything concrete to
suggest this was a bug in t
> On Jul 16, 2024, at 7:08 PM, Derrick N. Guerrero wrote:
>
> Hello,
>
> Could anyone answer whether the RTSP specification has requirements about the
> client_port value in a SETUP response
The RTSP specification (like all IETF protocol specifications) is online, for
free; in this case, at
Hello,
Could anyone answer whether the RTSP specification has requirements about the
client_port value in a SETUP response, and what the LIVE555 software behavior
would be if the server responds with a different value than sent in a SETUP
request?
For context, I'm investigating a video problem
