Supported carriers
Secrets are encrypted at rest and are never returned by the dashboard, Public API, or MCP.
Twilio voice regions
In One-click import → Twilio, choose where Twilio should process your calls from United States (US1), Ireland (IE1) or Australia (AU1). Enter the Account SID and the Auth Token for that region. To use another region with the same account, add another Twilio connection with the same Account SID and the other region’s token. Before importing an unused number, set its active Voice region in Twilio Console to the region you selected. An existing voice route or assignment to another trunk can prevent the import. The first import creates an Elastic SIP Trunk and SIP credentials in the selected region. The inbound SIP endpoint region controls where Famulor receives calls from Twilio. It defaults to Europe for IE1 and Global for US1 and AU1. You can change it when creating the connection. Check inbound and outbound calls in Twilio’s Call Logs for the selected voice region. An IE1 or AU1 connection created with only its regional token supports voice calls. Famulor SMS on eligible numbers requires a connection with a saved US1 Auth Token. You can also create the connection with the Public API, the MCP toolcreate_carrier_connection, or the CLI.
Switch the region of an imported number
Open One-click import → Twilio and select the saved connection for the target region. Next to the imported number, choose Switch region. Both connections must use the same Twilio Account SID. When automatic setup is available, confirm with Switch region. Famulor uses the saved regional Auth Token to create a dedicated secure trunk and SIP login, then switches incoming and outgoing calls for the existing number. This requires the source region to be active for the number and Famulor to be able to verify its secure incoming route. Choose Use an existing trunk if you have a compatible trunk you want to use. If the target region is already active for the number, use a compatible existing trunk.- Select an existing secure Twilio trunk whose termination domain routes outgoing calls through the target region. Once Famulor verifies that Twilio already routes incoming calls for this number to that trunk, Incoming and outgoing calls is selected by default. Choose Outgoing calls only to keep the current incoming route.
- If the trunk has a verified SIP login saved in Famulor, Famulor reuses it. Otherwise enter the existing SIP username and password for the trunk in the dialog. Confirm with Switch region.
/api/v1/carrier-connections/{id}/numbers/{numberId}/region-switch
To create a secure trunk through the API, send this POST body using the managed token from the preview for the same connection and number.
--switch-revision.
Import a number

Settings → Phone numbers → Add a number → Import from your carrier: select your carrier, then Continue to its connection details.
- Open Settings → Phone numbers → Add a number → Import from your carrier.
- Select the carrier, enter credentials, and choose the SIP region.
- Select voice-capable numbers that are not already routed elsewhere.
- Import the numbers and assign an assistant.
- Test one inbound and one outbound call before using the number in a campaign.
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.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;
- for Telnyx, that the connection still accepts the platform’s SIP credentials and allows calls to your numbers’ countries;
- that every imported number sends its SIP credentials and an international caller ID on outbound calls;
- inbound and outbound connectivity;
- number and assistant assignments.
Public API and MCP
The Public API exposes:GET/POST /api/v1/carrier-connectionsGET/PATCH/DELETE /api/v1/carrier-connections/{id}GET /api/v1/carrier-connections/{id}/available-numbersPOST /api/v1/carrier-connections/{id}/importDELETE /api/v1/carrier-connections/{id}/numbers/{numberId}POST /api/v1/carrier-connections/{id}/troubleshoot
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.
Zadarma import
Find API keys or set up Zadarma manually, including direct SIP and PBX forwarding.
POST /api/v1/carrier-connections or MCP create_carrier_connection with carrier: "zadarma", then list and import the available number. The equivalent CLI commands are: