Skip to main content

Protocol implementation quickstart

Use this path when implementing RTVBP without one of the released SDKs.

Mechanical proof, not prose alone

Treat the generated conformance vectors under conformance/ as executable acceptance. The reference pages explain the same spec, but byte and scenario proof is the compatibility authority.

Implementation order​

  1. Accept a secure WebSocket and authorize the HTTP Upgrade before returning 101.
  2. Negotiate the rtvbp.v1 profile as described in Profiles and negotiation.
  3. Decode each text message with the generated classic.v1 envelope contract.
  4. Implement the generated application or voice role.
  5. Complete session.initialize before sending binary audio.
  6. Correlate every request with exactly one response and preserve message ordering.
  7. For terminal operations, flush the successful response before starting the WebSocket close handshake.

Run the generated conformance vectors under conformance/<catalog>/ against your implementation. The generated flows are readable projections of the same typed scenarios.