I’ve been through every RFC I can find that seems relevant, some several times.
In particular, what I’m NOT finding is any discussion about all of the
codec-specific and so-called “out-of-band” details that these specs
DELIBERATELY avoid — which happens to be exactly what I’m having trouble with
> Regardless, my question was not about headers, but SDP data that IS being
> returned from a LIVE555 server.
>
> Being that this is a discussion group for LIVE555 server users, I figured
> it’s an appropriate question.
No, your question was a general question about RTSP server behavior; not a
My software isn’t working properly yet. These traces were intended to
illustrate the problem, not the solution, and did not come from my software,
which is an incorrect assumption on your part.
Regardless, my question was not about headers, but SDP data that IS being
returned from a LIVE555 ser
Note that this mailing list is specifically for questions about/discussion of
the "LIVE555 Streaming Media" software. It is not intended for general
questions about RTSP, RTP or RTCP. If your organization is interested in
hiring me as a consultant/technical advisor for general architectural is
I’m trying to figure out track <—> channel mappings in SDP payloads.
The DESCRIBE command to an RTSP server is giving me the following SDP data
(shortened a bit for brevity):
. . .
m=video 0 RTP/AVP 96
a=3GPP-Adaptation-Support:1
a=rtpmap:96 H264/9
a=fmtp:96 profile-level-id=42E00C;
sprop-
