On 2/12/16 12:15 PM, Randell Jesup wrote:
On 2/12/2016 11:58 AM, Byron Campen wrote:
On 2/12/16 9:26 AM, Alexander Abagian wrote:
Thank you for the answer.
I've changed the order of m-sections from all-audio-first (I've done
it so because have seen this requirement it in some RFC) to
audio-video pairing with adding a new m-secions to the end of the
SDP, and it helps.
But anyway when I'm removing a participant, I'm receiving a error
"Wrong SDP: New remote description has fewer m-sections than the
previous remote description.". How should I form remote SDP in this
case ? Leaving these dead m-sections, just assigning zero tp their
ports ?
Yeah, you can either disable the extra m-sections (set a port of
0), or you can make them a=inactive. Removing m-sections is forbidden
by the rules of SDP offer/answer.
Right: You can never remove m-sections. You should not reorder them
either. You should not (though in theory I think you can) change an
m-section type (audio/video/applications); too much danger of code
getting it wrong since no one tests it - and there's very little win
to doing so.
And there's nothing that says audio should come first, though that's
generally common.
Changing the type of an m-section is forbidden by the base spec I
believe, although the JSEP draft says you should recycle disabled
m-sections even if they need to change types (I think this is likely to
break stuff).
As far as ordering of m-sections goes, the JSEP draft says to add
m-sections based on the order that MediaStreams are added, and then the
tracks are ordered alphabetically based on media type (which happens to
put audio before video).
We have not implemented either of these behaviors yet.
Best regards,
Byron Campen
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
