EasyRTC in Bowser browser on iOS

[Zoran Krnetic]

Hello!

Last week first-ever WebRTC capable iOS browser was released: http://getbowser.appspot.com https://github.com/EricssonResearch/Bowser

I've tried to use Bowser to run your simple audio/video demo to connect with Chrome on Mac. Here are results:

1. when I open your demo in Bowser, local cam video is displayed and it gets connected to easyrtc server - I see other party ID and on other party's page my ID appears

2. when I try to initialize connection from Bowser to Chrome nothing happens - no connection is made

3. when I try calling from Bowser to Chrome, I get following error message in Chrome:

"set-remote-description: Failed to set remote offer sdp: Called with SDP without DTLS fingerprint."

Can somebody help? At least give me idea where to look for solution of issue 3. maybe?

Thanks,

Zoran

[Eric Davies]

Try point your bowser browser at google's apprtc.appspot.com site. From what I understand, it claims to work there. If it doesn't,  you need to get the latest version of bowser because the blog indicates they had some versions that didn't interoperate. If it does work on apprtc but doesn't on easyrtc, then I'll be curious to check it out when time permits.

[Zoran Krnetic]

Eric,

I definitely have latest version of Bowser (0.2.3), it was updated couple of days ago. apprtc.appspot.com doesn't work at all in Bowser! Just a black screen. Your simple audio/video demo works much better - at least I have local video and connection to signaling server.

Thanks,

Zoran

[Eric Davies]

Are there any demos of the bowser browser interoperating with other browsers?

[Zoran Krnetic]

Yes - their own demo http://demo.openwebrtc.io I tried and worked between Bowser on iPhone and Chrome 38 on Mac.

Zoran

[Eric Davies]

I'll look into it on Saturday night.

[Eric Davies]

In your  easyrtc.js file, there is a function called buldPeerConstraints. It has the line:

           options.push({'DtlsSrtpKeyAgreement': 'true'}); // for interoperability

Try deleting that line.

Tomorrow, I'll try making sure the demos still work without it between chrome and firefox. I don't have the bowser browser downloaded to an ipad because I'm not willing to give Apple my credit card number to hold onto just to install one free app.  That just strikes me as dangerous.

[Eric Davies]

Commenting out that line doesn't seem to interfere with chrome/firefox interop. I think we safely delete it if it proves to enable iOS-bowser connections.

[Zoran Krnetic]

Eric,

I have commented out that line (and updated Bowser to latest version) and I'm still getting "set-remote-description: Failed to set remote offer sdp: Called with SDP without DTLS fingerprint.  in Chrome when I try to call from Bowser to Chrome. When I try to call from Chrome to Bowser I get "Miscellaneous error from signaling server. It might be ignorable" in Bowser. Do you have some other suggestion for me to try?

Thanks,

Zoran

[Eric Davies]

Hi Zoran, 

I was at the WebRTC expo last week, and Bowser came up. The general perception by people in the know there was that Bowser is a brilliant hack, but not something you should use for production use.

That said, what I would suggest doing:

   use Chrome and bowser in a chat using the Bowser example. Make sure you start with the Chrome inspector window up so you can see the SDP offer and answer messages in the websocket stream (it will have a status of 101, pending).

   then do the same thing in a chat using an easyrtc example.

If you compare the two sets of messages, there should be something different. It's then a matter of figuring out what causes that difference.

[gianni]

Any progress on bowser compatibility with easyrtc ?

[Priologic Victoria]

This isn't something we're working on. It would be up to you.