Skip to main content
POST
Create SIP Trunk
Famulor 1.0 API (legacy). This page applies only to Famulor 1.0 (app.famulor.de) and is retained for legacy compatibility. For the current platform, use the Famulor 2.0 API reference.
This endpoint creates a new SIP trunk. The platform automatically provisions inbound and outbound trunks on the voice infrastructure using the provided credentials.

Body Parameters

string
required
The type of SIP trunk: extension for a SIP extension, or number for a phone number (DID). This determines the expected format of the phone_number field.
string
required
The SIP extension (1-15 characters, e.g. 1000) when sip_trunk_type is extension, or a phone number in E.164 format (e.g. +14155551234) when sip_trunk_type is number.
string
A short, human-friendly label for the trunk (e.g. “Provider X — Main”). Maximum 50 characters.
string
required
Username for SIP authentication (3-128 characters)
string
required
Password for SIP authentication (minimum 3 characters)
string
required
The SIP server address without port (e.g. sip.provider.com)
string
required
The outbound calling number format:
  • +e164 - International with + prefix (e.g. +12025550123)
  • e164 - International without + prefix (e.g. 12025550123)
  • national - National format without country code (e.g. 0741926265)
string
required
How inbound calls are authenticated:
  • auth - Uses the same SIP username and password configured for outbound
  • ip - Whitelists specific IP addresses (requires allowed_inbound_ips)
array
Array of IP addresses allowed to send inbound calls. Required when inbound_authorization_type is ip. Must contain at least one valid IP address.
string
required
ISO 3166-2 country code where the SIP trunk is located (e.g. US, GB, DE). When sip_trunk_type is number, the country is auto-detected from the phone number if possible.
boolean
Route outbound calls through a fixed IP address. Default: false. Only enable this if your SIP provider requires IP-based authentication for outbound traffic.

Response

string
Success message
object
The created SIP trunk object (same fields as Get SIP trunk)

What happens after creation

When you create a SIP trunk, the platform automatically:
  1. Provisions an inbound trunk on the voice infrastructure - using either username/password or IP-based authentication depending on your inbound_authorization_type setting
  2. Provisions an outbound trunk - using the SIP address and credentials you provided, optionally through the outbound proxy
If provisioning fails, the SIP trunk is not saved and a 500 error is returned.

Next steps

After creating a SIP trunk, assign it to an AI assistant: