-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable WebRTC connections to be made to the Domain, i.e., add Web client support. #1469
Conversation
WebRTC Signaling Channel
Conditionally include WebRTCSignalingServer.h
…annel # Conflicts: # domain-server/src/DomainServer.h
Update WebRTC Windows package
Update webapp feature branch with current master
Update WebRTC for Linux.
WebRTC revisions and updates including the addition of secure connections.
Fix SSL WebSocket Domain server crash.
The following links are available: build (macOS-10.15, client) build (ubuntu-18.04, full)
build (windows-latest, full) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Works fine to me with basic local testing between native and web on a local server.
I tested it with Kalila on Linux server and both native and web clients, and everything, including chat and messages works perfectly. |
Windows server functionality is also tested now and works correcly except for slightly choppy audio from web client. |
Enables browser clients using the Web SDK to connect to the domain server and assignment clients via WebRTC.
WebRTC connections can be enabled/disabled in the server settings. An SSL certificate is required if running a public domain - the Web client needs to be served via HTTPS in order for Web audio to work, which means that the WebSocket used to establish the WebRTC connection with the domain server also needs to be SSL. (If running on localhost or local network, the Web client can be served via HTTP and Web audio will still work, and no SSL cert is required.)