> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leamout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routing

> Understand how Leamout resolves outbound routes and inbound ownership.

Leamout keeps routing decisions in the control plane rather than delegating them to carrier or media infrastructure.

## Outbound

A call request supplies public routing intent: organization, optional application, optional explicit trunk, `from`, and `to`. The route resolver returns a concrete carrier connection, trunk, endpoint, normalized caller/destination, and carrier limits.

For BYOC, passing `trunk_id` selects the customer-owned connectivity path. Endpoint selection considers eligibility, health, priority, and weight.

## Inbound

Leamout authenticates carrier ingress before resolving customer resources. A phone number identifies carrier ownership and a voice-application binding identifies application behavior.

Carrier selection, tenant resolution, and routing policy remain control-plane decisions. The communications runtime executes the resulting signaling and media instructions.