Signaling
Voxtronics separates its HTTP control plane from its SIP signaling plane. The Backend API manages tenant resources. SIP services handle registration, authentication, peer validation, transactions, dialogs, and call routing.
Media
The Bot runtime terminates the audio session. It validates the SDP offer, selects a compatible codec, allocates RTP and RTCP ports, and returns an SDP answer. RTP processing, jitter handling, playback, and provider audio conversion remain separate from SIP routing.
Routing
Voxtronics applies routing at three boundaries.
Functions and intents
Functions are model-facing tool definitions. Each function has a name, description, and structured parameter schema. Intents are normalized action requests produced by those tool calls or other supported runtime detection.
Adapters
Adapters execute actions after an intent has been selected. Voxtronics supports four adapter types.
AI providers
Providers hold vendor-specific model, voice, language, transcription, and audio settings. Credentials are stored in Vault and referenced by provider objects.
Transports
Transports are reusable connection definitions for AI provider APIs. They contain an optional endpoint, static headers, connection and read timeouts, and WebSocket keepalive behavior.