Skip to main content
LLM ReadyRaw Markdown for AI agents:sip-trunking-byoc.mdFull index:llms.txtllms-full.txt

SIP Trunking (BYOC)

Firetell SIP Trunking (Bring Your Own Carrier — BYOC) lets you connect phone numbers from any telecom carrier or SIP Trunking service provider—as well as existing IP-PBX and enterprise SBC systems (3CX, Cisco CUCM, Avaya, Grandstream, Genesys)—directly into your Firetell workspace for Voice AI, IVR Call Flows, and Call Center routing.


1. Inbound SIP Traffic (IP Access Control Lists)​

To send SIP calls from your PBX or carrier into Firetell:

  1. Navigate to Console → SIP Trunks → Inbound IP ACLs.
  2. Create an ACL and add the static IPv4 CIDR blocks of your SBC/PBX (e.g., 203.0.113.10/32).
  3. Bind the Inbound ACL to your Phone Numbers so inbound INVITE requests from your trusted IP addresses are authenticated automatically.

2. Outbound SIP Gateways​

To route calls from Firetell to your external PBX or carrier gateway:

  1. Go to Console → SIP Trunks → Outbound Gateways and click Add Gateway.
  2. Configure:
    • Gateway Host / IP: e.g., sbc.yourcompany.com:5060
    • Authentication: IP Authentication or Digest Username/Password registration.
    • Transport: UDP, TCP, or TLS.
  3. Assign the Outbound Gateway to your desired DID numbers or call flows.

Firewall & IP Whitelisting​

When you create a workspace in Firetell, you select a primary deployment region. Each region operates an isolated cluster of dedicated SIP signaling proxies and RTP media relays to ensure low-latency voice routing and regional data locality.

To prevent rejected INVITE requests, dropped calls, or one-way audio, configure your carrier trunk, enterprise SBC, or PBX firewall to allow both SIP signaling and all RTP media IP addresses for your workspace's assigned region (you can check your workspace region anytime under Console → Settings → General).

Regional Signaling & Media IP Addresses​

RegionSIP Signaling (IP & Ports)RTP / SRTP Media (IPs & Port Range)
asia-vn-1
Asia Pacific (Vietnam)
IP: 45.115.16.84
• 5060 (UDP / TCP)
• 5061 (TLS)
IPs: 45.115.16.247, 45.115.16.249, 45.115.16.146, 45.115.16.178
• Ports: 16384–32768 (UDP)
us-east-1
North America (US East)
Coming Soon — We’re putting the finishing touches on our cloud voice infrastructure in the us-east-1 region.Coming Soon — We’re putting the finishing touches on our cloud voice infrastructure in the us-east-1 region.
asia-sg-1
Asia Pacific (Singapore)
Coming Soon — We’re putting the finishing touches on our cloud voice infrastructure in the asia-sg-1 region.Coming Soon — We’re putting the finishing touches on our cloud voice infrastructure in the asia-sg-1 region.
eu-west-1
Europe (EU West)
Coming Soon — We’re putting the finishing touches on our cloud voice infrastructure in the eu-west-1 region.Coming Soon — We’re putting the finishing touches on our cloud voice infrastructure in the eu-west-1 region.
Whitelist Every Media IP in Your Region

Firetell dynamically distributes call audio across all RTP media servers within your workspace's region for high availability and load balancing. Do not whitelist only a single RTP IP observed during a test call—allow the entire regional RTP IP pool and full UDP port range (16384–32768) to avoid intermittent one-way or silent audio.

Firewall & SBC Configuration Checklist​

  • Allow Bidirectional Signaling & Media: Permit traffic to and from Firetell's signaling IP (5060 UDP/TCP or 5061 TLS) and RTP media IPs (16384–32768 UDP) on both your perimeter firewall and your carrier trunk, enterprise SBC, or IP-PBX IP trust list.
  • Disable SIP ALG: Turn off SIP ALG (Application Layer Gateway) / SIP inspection helpers on edge routers and firewalls (FortiGate, Palo Alto, SonicWall, pfSense, MikroTik, Ubiquiti). SIP ALG frequently rewrites Via, Contact, and SDP headers incorrectly, causing one-way audio or calls dropping at ~30 seconds.
  • Verify NAT External Addresses: If your PBX or SBC sits behind 1:1 NAT, configure its external signaling IP and external RTP address explicitly so SDP c= connection lines advertise your public IPv4 address rather than a private RFC1918 address (10.x.x.x / 192.168.x.x).
  • Keep UDP NAT Bindings Alive: Set firewall UDP state timeouts to at least 120 seconds or enable periodic SIP OPTIONS keep-alives (60s interval) on your trunk so inbound calls from Firetell can always reach your gateway.
Automate Trunk Provisioning

You can also manage Inbound IP ACLs and Outbound Gateways via the SIP Trunks REST API.