1. Get credentials
Every SDK loads a JSON service-account file pointed at by theTELEQUICK_CREDENTIALS environment variable. The file looks like:
2. Install the SDK
Native runtimes (Python, Go, Rust, Java, .NET) load
telequick_core_ffi.so /
.dylib / .dll from disk. Either install it via the bundled package or
point TELEQUICK_LIB_PATH at a custom path.3. Dial
- The SDK opened a QUIC session with ALPN
h3to the gateway. - It serialized an
OriginateRequestenvelope and sent it on a fresh bidirectional stream prefixed with[u32 length][u32 method_id=Originate]. - The gateway replied on a server-initiated unidirectional stream with
CallEventenvelopes (CHANNEL_CREATE → CHANNEL_ANSWER → … → CHANNEL_HANGUP).
4. Receive audio
Hook the audio callback and the SDK delivers eachAudioFrame on the same
QUIC session:
Next steps
Architecture
How the gateway, the C++ core, and the SDK FFI fit together.
Authentication
Service accounts, JWT signing, and tenant scoping.
Raw RPC Format
Skip the SDK and talk to the gateway directly.
SDK Reference
Method-by-method docs for every language.