Routing

Voxtronics applies routing at three boundaries.

Tenant SIP routing

A rule in SIP → Routing maps an inbound SIP destination to one enrolled Bot. The public SIP layer resolves the tenant domain and destination, then sends the request to the Bot's registered contact.

Profile routing

The same public rule selects a profile assigned to that Bot. The control plane creates and maintains the corresponding internal profile route automatically. When the call reaches the Bot, the called destination resolves to that profile.

The profile determines whether the session uses a realtime model or an STT–LLM–TTS pipeline. It also selects the persona and policy.

Intent routing

During the session, a model tool call or detected intent can enter an intent router. The router selects an adapter permitted by the active policy. The adapter may perform a SIP action, call a webhook, publish queue work, or execute a pipeline.

The three boundaries serve different purposes: tenant routing locates the Bot, profile routing selects the call experience, and intent routing controls actions within the call.