WebRTC and proxy.

[Антон Мацюк]

One more question today :)

Looked at FAQ's, but found nothing about this: Do BBB client support proxy? Authentication?

Now I get error connecting WebRTC at start.

Before it just not worked (no audio returned, like mic not working) :)

http://pastebin.com/T8HePb9u

Look for this line:

POST http://demo.bigbluebutton.org/fcs/ident2 404 (Not Found) /fcs/ident2:1

And this:

WebSocket connection to 'ws://demo.bigbluebutton.org/ws' failed: Error during WebSocket handshake: Unexpected response code: 307 sip.js?v=164:7906

Maybe it is because I updated to last version of Chrome (38.0.2125.101 (64-bit))?

For xubuntu 14.04.1 and Firefox (32.0.3) I get a Flash crashed :)

Flash "About" page at Adobe site says "You have version 11,2,202,406 installed".

http://pastebin.com/qTZUZYmz

Thanks!

[Chad Pilkey]

The "fcs/ident2 404" is coming from the Flash Player. That message pops up when the client has to tunnel through port 80 I believe.

For the WebSocket error, a 307 error code stands for "Temporary Redirect" (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Ctrl+F "307). I have no idea what would be giving that response though.

If the demo server isn't working then the problem is probably a very aggressive client-side firewall. If you see the text "[Tunnelling]" in the bottom right corner then the client is being forced to go through port 80.

My only suggestion for the Flash crash would be to use Chrome/Chromium on Linux distros because Adobe has dropped support, but I think Google is still updating Pepper Flash for Linux.

[Антон Мацюк]

For the WebSocket error, a 307 error code stands for "Temporary Redirect" (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Ctrl+F "307). I have no idea what would be giving that response though.

Understood. Chad, may 307 error code be due to Chrome updated to newer stable version? (Yesterday Chrome updated.)

 

If the demo server isn't working then the problem is probably a very aggressive client-side firewall. If you see the text "[Tunnelling]" in the bottom right corner then the client is being forced to go through port 80.

Yes, if I enable "English", then it shows "Tunnelling" in bottom right corner.

Does this configuration (proxy with authentication) supported by WebRTC? Flash works. I just want to understand the abilities which BBB can provide.

Looks like WebRTC thru proxy is a problem now, so I disabled it in my pre-production instance.

Thanks.

[Chad Pilkey]

I highly doubt the 307 is coming from the browser, the more likely cause is a firewall/proxy server.

Tunneling only works for RTMP (Flash) communication and WebRTC is purely in the browser so there's no tunneling support.

[Calvin Walton]

On Tue, 2014-10-14 at 07:59 -0700, Антон Мацюк wrote:
> >
> > For the WebSocket error, a 307 error code stands for "Temporary
> > Redirect" (
> > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Ctrl+F
> > "307). I
> > have no idea what would be giving that response though.
>

> Does this configuration (proxy with authentication) supported by
> WebRTC?
> Flash works. I just want to understand the abilities which BBB can
> provide.
> Looks like WebRTC thru proxy is a problem now, so I disabled it in my
> pre-production instance.
> Thanks.
>

In theory, the WebRTC audio can be used through a proxy. In practise,
it's somewhat difficult to set up:

1. Your proxy server must support the HTTP CONNECT method to
create a tunnelled connection to port 80 on the server for the
websocket connection. (Many proxies do not allow connect to
port 80 by default)
2. You must have a TURN server configured to support TCP
connections, listening on a port which your proxy server
supports HTTP CONNECT for (e.g. port 143 is commonly allowed)

All in all, it's a fair bit of effort to set up, and I'm not sure
whether it'll actually work properly.

At some point, I expect we'll do some work to allow SSL/https
connections to a BigBlueButton server; this should improve the
websockets connection (1) because it will use port 143 instead of 80.

--
Calvin Walton <calvin...@kepstin.ca>