I ran into a very reproducible interop issue between Chrome and Edge on appear.in.
This seems to be an issue with REMB.

What steps will reproduce the problem?
1. Open up https://appear.in/some-room-name-of-your-choice in Chrome
2. open same URL in Edge (which is smarter about accessing an available camera)
3. Wait until you get video in both directions. Pro-tipp: "m" mutes the microphone
4. Open a new chrome tab and go to the same URL

What is the expected result?
Things don't break ;-)

What do you see instead?
In the first tab, the video from Edge freezes.
The ice connection state changes to disconnected then failed.
If the second tab leaves soon enough (less than 10 seconds ICE timeout), video partially recovers.

What version of the product are you using? On what operating system?
chrome 55, Insider r15019 build of Edge

Please provide any additional information below.
When the third client joins, the first Chrome tab does a renegotiation (locally) which calls setRemoteDescription with a bandwidth limit of b=AS:384.

Its looks as googAvailableReceiveBandwidth drops to 0 around that time (see the attached bang.png)
But Edge doesn't respond to ICE requests anymore so this might be caused by ICE disconnecting.

When setting a fixed b=AS limit for both chrome tabs by appending '?bandwidth=512' to the URL this doesn't happen.

I'm in Stockholm on Feb 9th/10th if that makes things easier ;-)
 

Deleted: bang.png 43.0 KB

	bang.png 43.0 KB View Download