There was an error while loading. Please reload this page.
Add 26.9.18 to Releases and bump the current version One bug across three platforms, filed as several issues: peer connection awaits resumed on libwebrtc own signalling thread, so a Dispose after an await ran inside libwebrtc callback and closed the connection a few lines before libwebrtc used what the close destroyed. EXC_BAD_ACCESS at 0x30 on Apple, a destroyed-mutex abort on Android, and asynchronous either way so it killed unrelated work. Also records OnTrack finally firing on Apple, and the -NativeLog switch. Connection-Signaling said "the release following 26.9.16" in three places for things that have now shipped; they name 26.9.18.
Correct the TURN proxy table: three of the five are stubs The table listed all five proxies as though they were choices. Three of them - Twilio, Coturn and AppRtc - have a GetIceServersAsync that throws NotImplementedException, so picking one gets an exception at the first client to join a room rather than a working call. The page also said "the two proxies for hosted ones are already written", which is half true: Xirsys is, Twilio is not. That misinformation had a cost. Someone deploying the server and asking why calls worked on a LAN and not the internet (issue #42) was told, on the issue, to switch to Coturn or Twilio. Neither could ever have worked. Records the third gate as well, which nobody had noticed: IHttpClientFactory was never registered, so XirsysProxy - the one hosted proxy that is implemented - could not be resolved even after the two source edits this page described. Documents the single configuration key that replaces all three edits, marked as arriving in the release after 26.9.16 since the server is run from source and master does not have it yet. The old three-edit procedure is kept for anyone on an older checkout. Also documents ISignalingServerUrlProvider for setting the client's signalling address at runtime, same release, since this page is where the client BaseUrl is documented.
Connection-Signaling: switching TURN provider takes two edits, not one The page said uncomment the proxy you want in Startup.cs. That is necessary and not sufficient: RoomHub hardcodes Create(TurnServer.StunOnly) rather than reading it from configuration, so uncommenting alone changes nothing and the reader would conclude the provider is broken. Written from Startup.cs without following the call through to the hub. Found by tracing what actually reads the TURN settings - the answer being nothing, in the default build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Wiki: the seven stack pages One page per layer, bottom to top, each ending in a pointer to the next: WebRTCnative, Bindings, The unified API, Middleware, Connection and its two implementations, and the demo apps. The unified API page is named for what it is rather than for the package, because a sidebar with WebRTCme nested under WebRTCme reads as a mistake. Connection is split three ways. One page covering two topologies, two server deployments and two sequence diagrams would have been six hundred lines, and the two implementations have almost nothing in common below IConnection. Twelve mermaid diagrams, all parsed and rendered under the strict security level GitHub uses before being committed. Mermaid rather than SVG pairs: it themes itself for dark mode and stays editable in place. Connection-Signaling records that the server's tracked appsettings.json carries a real Xirsys credential, because a reader who forks this needs to know not to rely on it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>