Bring your own carrier - Leamout

BYOC is a first-class Leamout connectivity model. The customer owns the carrier relationship while Leamout owns routing, durable call state, controls, events, and policy. The BYOC product flow is:

Discover the built-in generic-sip carrier provider.
Create an organization carrier connection.
Configure encrypted outbound digest authentication.
Create a BYOC trunk and SIP endpoint.
Create BYOC numbers and assign their carrier ownership.
Create a voice application and bind the inbound DID.
Place an outbound call and verify carrier/trunk/endpoint attribution.
Add or remove an inbound source-IP allowlist without interrupting the runtime.
Rotate digest credentials without interrupting the runtime.

Discover the generic SIP provider

curl -sS "$LEAMOUT_API_URL/v1/carrier-providers/" \
  -H "Authorization: Bearer $LEAMOUT_TOKEN"

Use the provider whose slug is generic-sip and whose status is active.

Create a connection

{
  "provider_id": "<generic-sip provider id>",
  "name": "Primary carrier",
  "inbound_enabled": true
}

Create a BYOC trunk

{
  "type": "byoc",
  "carrier_connection_id": "<connection id>",
  "name": "Primary trunk",
  "direction": "bidirectional"
}

Then add one or more trunk endpoints and assign numbers to the same carrier connection.

A requested BYOC route does not silently fall back to managed carrier connectivity. The two connectivity modes remain separate policy choices.

⌘I