Orbitali Docs

Inbound SIP

Connect a SIP provider to a self-hosted Orbitali gateway.

Inbound SIP is available when your Orbitali operator enables its Asterisk gateway. Use Phone numbers → SIP connections to create a connection, add an E.164 number and assign an existing agent.

Configure the provider to send calls to sip:+<called-number>@<gateway-address>:25483, using TCP or UDP and G.711 PCMU/PCMA. Authentication uses the generated username/password or a provider IPv4 source allowlist. Keep the authentication username separate from the caller ID. REGISTER and standalone outbound SIP calls are not supported. Direct transfers require an outbound route on the SIP connection.

IP allowlists cannot overlap another connection, including a disabled connection. Providers sharing IP ranges across tenants should use credential authentication. A source allowlist authorizes every call from that range, so use only the provider ranges assigned to your connection. IPv6 allowlists are currently unsupported.

Passwords are returned only when created or rotated. After rotation, update the provider and wait for Configuration applied. That status confirms loading the configuration; Verified by a successful call requires a completed call with media in both directions on the same revision. Perform a real speech and interruption test as well.

Public API

See Inbound SIP API for authentication, connection and number requests, responses, and error recovery. After adding a number, assign it to an active agent using the Phone Numbers API.

Use the dashboard or SIP API to configure the connection. The MCP assign_phone_number tool can assign an existing SIP number to an agent and set its E.164 handoffPhoneNumber.

KrosAI is the first planned interoperability target. Compatibility remains unverified until an actual inbound call succeeds, including speech, interruption, hangup and accounting.

Transfer to a person

In Phone numbers → SIP connections → Edit, enable the outbound route and enter the PBX/trunk server, port, TCP/UDP transport, optional outbound credentials, and authorized E.164 caller ID. Ask the PBX administrator for these settings and outbound calling permission. Save, wait for configuration to apply, and configure the destination E.164 handoff number in the agent's phone-number assignment.

When the agent invokes transfer_call, Asterisk dials the configured handoff number. Until the destination answers, the caller remains with the agent. Busy, rejection, timeout (30 seconds), or connection errors return a failure so the agent can offer another option. Once answered, the agent session ends and Asterisk connects the two people. Asterisk remains in the audio path; either person hanging up releases the other leg. Usage and call completion reflect the AI session ending at transfer, not the subsequent human conversation.

The caller ID is the configured authorized number. Preserving the original number is not promised. Extensions, SIP URIs, attended transfers, REFER, TLS, and outbound REGISTER are outside this first version. See SIP API transfer configuration.

Before production, test a successful transfer with two-way audio, busy/rejected destination, no answer, connection failure, hangup during ringing, hangup by either party after answer, caller ID, and agent session/usage closure. Confirm that failed transfers return to the agent and that no channels or bridges remain after hangup.

On this page