Overview
Sulus supports Bring Your Own (BYO) SIP trunk integration, allowing you to connect any SIP carrier to Sulus for both inbound and outbound calls. Here's a comprehensive overview of how it works and how to set it up.
Sulus supports Bring Your Own (BYO) SIP trunk integration, allowing you to connect any SIP carrier to Sulus for both inbound and outbound calls. Here's a comprehensive overview of how it works and how to set it up.
SIP trunking replaces traditional phone lines with a virtual connection over the internet, connecting your internal PBX or VoIP system to a SIP provider, which then routes calls to the Public Switched Telephone Network (PSTN). With Sulus's Custom "BYO" SIP Trunk option, you can integrate any SIP provider by supplying the SIP gateway address and authentication details.
Before setting up, allowlist Sulus's static IP addresses at your SIP provider based on your region:
| Region | SIP Host | Signaling IP Addresses | RTP Media |
|---|---|---|---|
| US | sip.sulus.ai | 44.229.228.186/32, 44.238.177.138/32 | Dynamic IPs; UDP ports 40000–60000 |
| EU | sip.eu.sulus.ai | 63.182.83.170/32 | Static IP 63.182.83.170; UDP ports 40000–60000 |
Important: If your organization is hosted in the EU, use https://api.eu.sulus.ai for all API calls and pair it with sip.eu.sulus.ai.
Use the Sulus API to register your SIP provider as a byo-sip-trunk credential:
curl -X POST "https://api.sulus.ai/credential" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_SULUS_API_KEY" \
-d '{
"provider": "byo-sip-trunk",
"name": "My SIP Trunk",
"gateways": [{
"ip": "sip.yourprovider.com",
"inboundEnabled": false,
"outboundEnabled": true
}],
"outboundLeadingPlusEnabled": true,
"outboundAuthenticationPlan": {
"authUsername": "YOUR_SIP_USERNAME",
"authPassword": "YOUR_SIP_PASSWORD"
}
}'Save the returned Credential ID for the next step.
Link your external phone number to the SIP trunk credential:
curl -X POST "https://api.sulus.ai/phone-number" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_SULUS_API_KEY" \
-d '{
"provider": "byo-phone-number",
"name": "My BYO Number",
"number": "15551234567",
"numberE164CheckEnabled": false,
"credentialId": "YOUR_CREDENTIAL_ID"
}'Once the number is registered, initiate outbound calls via the API:
curl -X POST "https://api.sulus.ai/call/phone" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_SULUS_API_KEY" \
-d '{
"assistantId": "YOUR_ASSISTANT_ID",
"customer": {
"number": "15557654321",
"numberE164CheckEnabled": false
},
"phoneNumberId": "YOUR_PHONE_NUMBER_ID"
}'For inbound routing, configure your SIP provider to forward calls to the Sulus SIP URI:
{phoneNumber}@<credential_id>.sip.sulus.ai{phoneNumber}@<credential_id>.sip.eu.sulus.aiEnsure you provide all signaling IP addresses when creating the SIP trunk. Missing IPs will prevent proper whitelisting and may result in 401 Unauthorized errors for inbound calls.
Each entry in the gateways array supports the following options:
| Option | Type | Default | Description |
|---|---|---|---|
ip | string | required | IPv4 address or hostname. Hostnames only work for outbound gateways. |
port | number | 5060 | SIP signaling port. |
netmask | number | 32 | Subnet mask for inbound IP matching (valid range: 24–32). |
inboundEnabled | boolean | true | Whether this gateway accepts inbound calls. |
outboundEnabled | boolean | true | Whether outbound calls route through this gateway. |
outboundProtocol | string | "udp" | Signaling protocol: udp, tcp, tls, or tls/srtp. |
optionsPingEnabled | boolean | false | Send SIP OPTIONS pings to check gateway reachability. |
transferCall tool with a sip destination type, e.g., sip:[email protected].Sulus natively documents integrations with several providers, but any SIP carrier can be used via the BYO trunk:
In summary, Sulus's BYO SIP trunk feature gives you full flexibility to bring your own carrier, configure inbound and outbound routing, and integrate with any SIP-compatible telephony provider using standard credentials and gateway configuration.
Read-only access to this documentation from your AI tools. No login, OAuth, or token required — just the endpoint below.
https://docs.sulus.ai/mcp/sulus-docs-public
Settings → Connectors.Add custom connector.Sulus Docs and paste the endpoint above as the Remote MCP server URL.Add, then enable it in your chat.Settings → Connectors.Developer mode (Settings → Connectors → Advanced) if you don't see custom connectors.Create / Add custom connector and paste the endpoint above as the MCP Server URL.No authentication and create the connector.Custom MCP connectors require a ChatGPT plan with developer mode / connectors enabled.