Repository navigation
CalloraVoipSdk 4.11.0 #366
BechsteinDigital
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
CalloraVoipSdk 4.11.0
Media over a TCP/TLS TURN relay, and a WebRTC peer that survives an ICE restart — the two limits the 4.10 line called out. A purely additive minor: no public API was removed or changed (verified against the tracked
PublicApi.approved.txtbaseline).✨ Highlights
📡 TCP/TLS TURN relay (#240)
The relay data path is no longer UDP-only. Add a TURN server with
IceTransport.Tcp/IceTransport.Tlsand a relay candidate carries media over a persistent TCP/TLS connection to the server (RFC 8656 §12 ChannelData), as a first-class ICE candidate. Media rides the transport the winning pair selects — the model libwebrtc and pjnath use — while the UDP relay keeps its in-place whole-socket switch. TLS gives a last-resort path across firewalls that allow only outbound 443.🔄 ICE restart on a connected peer (#226)
IPeerConnection.CreateIceRestartOfferAsync(...)re-gathers and re-nominates connectivity in place — the DTLS association and SRTP contexts are preserved — instead of forcing a dispose-and-rebuild. A WLAN → mobile handover no longer drops the call.📶 Receive-side simulcast (#317)
A receive-only offerer (a conference host) can ask the peer to simulcast via
WebRtcConfiguration.SimulcastRecvLayers;IPeerConnection.NegotiatedReceiveSimulcastRidsreads back the negotiated set.📦 Also in this release
ICall(MediaFlowChanged,MediaSilenceNotifyAfter) — media silence no longer tears the call down.EncodedFrame.KeyFrameSource/SpatialId/TemporalId).ServedUserAors, §8.2.2.1).SipAccount.Register,LineState.Ready,Usernameno longer required,VoipConfiguration.LocalSipPort/LocalSipTlsPort.WebRtcConfiguration.OpaqueVideoFrames), per-track key-frame requests.🔧 Compatibility
IPeerConnection,ICall) are additive per ADR-006 §2.net8.0,net9.0,net10.0.The TCP/TLS stream relay is unit-proven; its browser / real-server data-path validation is tracked in the interop matrix (#228), and the working path is the controlling (offerer) agent. TLS certificate validation currently uses the platform default (custom-CA config is a follow-up).
🔗 Links
📄
RELEASE_NOTES_4.11.0.md·CHANGELOG.md· ADR-073 — stream relay transportThis discussion was created from the release CalloraVoipSdk 4.11.0.
All reactions