Skip to main content
Carrier import connects your own carrier account, discovers its existing phone numbers, and creates the matching inbound and outbound SIP configuration automatically. The carrier continues to bill number rental and call termination.

​
Supported carriers

Secrets are encrypted at rest and are never returned by the dashboard, Public API, or MCP.
Vonage is initially available in preview/staging environments for live validation. Enable both VONAGE_CARRIER_IMPORT_ENABLED=true and NEXT_PUBLIC_VONAGE_CARRIER_IMPORT_ENABLED=true; keep them unset in production until the smoke test is complete.

​
Import a number

  1. Open Settings → Phone numbers → Add SIP integration → Import from carrier.
  2. Select the carrier, enter credentials, and choose the SIP region.
  3. Select voice-capable numbers that are not already routed elsewhere.
  4. Import the numbers and assign an assistant.
  5. Test one inbound and one outbound call before using the number in a campaign.
The platform re-reads each selected number from the carrier before importing it. A client-supplied number can therefore never be paired with a different carrier resource.

​
Vonage routing protection

Vonage numbers with an existing app, telephone, or unrelated SIP callback are marked as unavailable. Carrier import never overwrites that routing. When a Vonage number is removed, its callback is cleared only if it still points to the exact regional SIP endpoint configured by this connection. A callback changed later in Vonage is preserved.
Do not remove or replace the carrier-side trunk, connection, or callback while a number is active. Use Troubleshoot to detect and safely repair supported drift.

​
SIP regions and troubleshooting

The selected region determines the SIP endpoint used for inbound signaling. Changing it runs provider diagnostics and repairs imported-number routing. Troubleshoot verifies:
  • carrier credentials and account balance;
  • provider trunk/connection or direct number routing;
  • the platform inbound/outbound trunk pair;
  • assistant dispatch rules.
Repairs are limited to resources owned by the selected connection. Provider errors remain visible on the connection.

​
Public API and MCP

The Public API exposes:
  • GET/POST /carrier-connections
  • GET/PATCH/DELETE /carrier-connections/{id}
  • GET /carrier-connections/{id}/available-numbers
  • POST /carrier-connections/{id}/import
  • DELETE /carrier-connections/{id}/numbers/{numberId}
  • POST /carrier-connections/{id}/troubleshoot
Use the sip_trunks:read or sip_trunks:write scope. Equivalent MCP tools are list_carrier_connections, create_carrier_connection, get_carrier_connection, update_carrier_connection, list_carrier_available_numbers, import_carrier_numbers, remove_carrier_number, delete_carrier_connection, and troubleshoot_carrier_connection.
Carrier import is the fastest option for Twilio, Telnyx, and Vonage. For another SIP provider, use BYO SIP trunk.