WebRTC TURN Preparation
Current repo truth
- durable call-session state remains in
svc-messaging
Resolving locale, route permissions, and workspace projection.
Current scope: Guest
Category: 60_technical_specs | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 60 days
Approval authority: GOVERNANCE_ADMIN, COMPLIANCE_OFFICER
Documentation portal is read-only. Editing and mutation endpoints are disabled.
Kvary platform is originally created in Georgian. Where a Georgian version exists, Georgian is authoritative for platform UI, documentation, and legal interpretation.
Translations into other languages are provided for convenience. Some records may originate in other languages and carry their own source or legal locale for a specific flow, but where a Georgian version is available, the Georgian version prevails for platform-level wording and interpretation.
Metadata incomplete: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
svc-messagingFrontend:
NEXT_PUBLIC_WEBRTC_STUN_URLSNEXT_PUBLIC_WEBRTC_TURN_URLSNEXT_PUBLIC_WEBRTC_TURN_USERNAMENEXT_PUBLIC_WEBRTC_TURN_CREDENTIALNEXT_PUBLIC_WEBRTC_ICE_TRANSPORT_POLICYBackend / deploy placeholders:
WEBRTC_STUN_URLSWEBRTC_TURN_URLSWEBRTC_TURN_USERNAMEWEBRTC_TURN_CREDENTIALWEBRTC_ICE_TRANSPORT_POLICYNEXT_PUBLIC_WEBRTC_STUN_URLS, calling should behave exactly like the current localhost flowNEXT_PUBLIC_WEBRTC_ICE_TRANSPORT_POLICY=relay can be used to smoke-test TURN-only routing