> Unfortunately, we are reluctant to change this on our side because we
> deliberately moved the "t=0,0" line in our newer H.264 appliances (as
> compared to our older MPEG-2 appliances) to achieve better alignment with
> Section 5 of RFC 4566
I'm puzzled by this, because Section 5 of RFC 4566 (the section that you
quoted) says that
> One or more time descriptions ("t=" and "r=" lines; see below)
must appear before:
> a=* (zero or more session attribute lines)
Therefore, putting the "t=0,0" line above the attributes line is *correct*, and
so it's what you should be doing in the SDP descriptions that you generate.
(Also, although not directly relevant to this email, another thing that's wrong
with your SDP description is your use of the static payload type 36, which
isn't defined anywhere.)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
ps. If you haven't already done so, you should consider using the "LIVE555
Streaming Media" software in your own server products; it would likely save you
a lot of work.
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
