Re: Issue 185: Contradictory RTP/RTCP mux settings

• From: Bernard Aboba <Bernard.Aboba@microsoft.com>
• Date: Wed, 8 Apr 2015 00:06:58 +0000
• To: "public-ortc@w3.org" <public-ortc@w3.org>
• Message-ID: <BY2PR03MB1609C9BB6F49CDE70AFD397ECFC0@BY2PR03MB160.namprd03.prod.outlook.com>

Here is a proposed fix: 

In Section 6.3.2, add: 

send
 If rtcpTransport is not set or rtcpTransport.stop() has been called and send(parameters) is called with parameters.rtcp.mux set to FALSE, throw an InvalidParameters exception.

setTransport
 If setTransport() is called with a single argument or if rtcpTransport.stop() had previously been called, and the last call to send(parameters) had parameters.rtcp.mux set to FALSE, throw an InvalidParameters exception.

In Section 7.3.2, add: 

receive
 If rtcpTransport is not set or rtcpTransport.stop() has been called and receive(parameters) is called with parameters.rtcp.mux set to FALSE, throw an InvalidParameters exception.

setTransport
 If setTransport() is called with a single argument or if rtcpTransport.stop() had previously been called, and the last call to receive(parameters) had parameters.rtcp.mux set to FALSE, throw an InvalidParameters exception.

Received on Wednesday, 8 April 2015 00:07:28 UTC