Robert Swain

Have you installed the extension and were you running the openwebrtc-daemon?

On iOS in the NativeDemo app, fixing https://github.com/EricssonResearch/openwebrtc-ios-sdk/issues/2 should help a bit. On both Android and iOS, fixing https://github.com/EricssonResearch/openwebrtc/issues/186 should help. However, it is not uncommon that the time between...

We're working on the performance issues but I'm on holiday until late next week so I don't expect much to happen before then.

We're still working on the performance issues when we get time to. Fixing https://github.com/EricssonResearch/openwebrtc/issues/240 should help a lot.

Use GTK+ and WebKitGTK+ as well, through the GObject Introspection bindings: https://wiki.gnome.org/action/show/Projects/PyGObject http://webkitgtk.org/reference/webkit2gtk/stable/WebKitWebView.html

There is an ice-connection-state property on OwrSession. It may get split into connection-state and gathering-state soon as in ORTC as that is more agnostic to the connection establishment protocols used.

Revert https://github.com/EricssonResearch/openwebrtc-examples/commit/8f7b847b5f2d0a267ef1eaea5f8b2f405af6a120 . I have not yet figured out how to get the applications working with that commit in place.

I think it will affect the Android and iOS native apps, and probably the command line test-client app, but not Bowser nor openwebrtc-daemon.

@carterbryden - By revert that commit I meant: `git revert 8f7b847` We will make the necessary changes to the SDKs as soon as we can.

The expected behaviour is that if you have two devices connected to the Internet, if they both enter the same session ID and push the join button, the call button...