What is the AI4CALL IP2IP SIP trunk?
The AI4CALL IP2IP SIP trunk is a SIP trunk without registration: your PBX connects to AI4CALL with no username or password, because AI4CALL directly authorizes the public IP addresses your SIP traffic comes from. Setup takes two steps: add your PBX's IPs to the Authorized IPs panel in the portal, then set the listed parameters on the trunk (host sip.ai4call.com, port 5060 UDP, G.711 a-law codec, RFC 2833 DTMF tones).
In this video tutorial we walk you through the setup in the AI4CALL portal: which addresses to authorize, which ports to use, how communications are protected and which values to copy into your PBX so every call reaches the right assistant.
The trunk links your PBX to AI4CALL voice assistants, which answer the phone, understand and take action. Businesses use them without writing code; developers and system integrators get full APIs and integrations with their own software.
Authorized IPs: who can exchange SIP traffic with AI4CALL
The Authorized IPs panel lists the addresses allowed to exchange SIP traffic with AI4CALL: this is where you add the public IP addresses of the PBX you want to connect. The rule is clear-cut: any request from an address not on the list is rejected.
AI4CALL accepts SIP trunks on the default ports: 5060 for UDP and TCP, 5061 for TLS.
Account-level IPs: what happens when you change them
The portal shows a warning worth taking seriously: the IPs you enter belong to your account, not to a single assistant. Every new assistant inherits them, and every change, whether you add or remove an address, takes effect immediately on all assistants in the account.
Before removing an address, make sure no other assistant in production relies on it: deleting it cuts off that assistant's SIP traffic.
AI4CALL portal warning
SIP TLS security: how communications are protected
The SIP TLS Security section explains how communications between your PBX and AI4CALL are protected. TLS is the protocol that encrypts SIP traffic; on AI4CALL it relies on:
- X.509 version 3 digital certificates issued by Let's Encrypt
- 256-bit ECDSA public key
- TLS version 1.2 and above
- Port 5061 dedicated to SIP over TLS
SIP trunk parameters to set on your PBX
Further down, the SIP Trunk to AI4CALL panel lists every parameter to copy into your PBX:
- Type: SIP or PJSIP without registration
- Host: sip.ai4call.com on port 5060 UDP
- From domain: AI4CALL
- Codec: G.711 a-law
- DTMF tones: RFC 2833 standard
- PBX behind NAT: nat set to yes and qualify set to no
PBX NAT and firewall
If your PBX sits behind NAT, set nat to yes and qualify to no. Then allow the AI4CALL address shown in the panel on your firewall.
Request URI: the field that routes calls
The Request URI is the destination address of the SIP request and matches the trunk's TO field: it tells AI4CALL which assistant should take the call. Enter your API key or your virtual number, followed by @sip.ai4call.com:5060. Format: API key or virtual number@sip.ai4call.com:5060.
Quick setup for 3CX and Yeastar
The portal also includes two ready-to-use quick notes: on 3CX, create a SIP gateway of type no registration; on Yeastar, create a new SIP trunk with the generic provider.
Managing the allowed IPs table
At the bottom of the page you'll find the Allowed IPs table: each row shows an address and its description, and the red icon deletes it. Click Add IP to insert a new row and Save IPs to confirm. Remember: changes apply immediately to all assistants in the account.
In short: the IP2IP SIP trunk on AI4CALL
Authorize your PBX's public IPs, use port 5060 (UDP/TCP) or 5061 (TLS), set host sip.ai4call.com, G.711 a-law codec and RFC 2833 DTMF, then put your API key or virtual number in the Request URI. IPs apply to the whole account.
IP2IP SIP trunk FAQ
Do I need a username and password for the IP2IP SIP trunk?
No. The AI4CALL IP2IP SIP trunk works without registration: AI4CALL accepts SIP traffic only from the public IP addresses on the Authorized IPs list and rejects requests from any other address.
Do authorized IPs apply to a single assistant?
No. Authorized IPs are tied to the AI4CALL account: every new assistant inherits them and every change applies immediately to all assistants. Removing an IP cuts off SIP traffic for the production assistants that rely on it.
How does a call reach the right assistant?
Through the Request URI, i.e. the TO field of the SIP trunk: enter your API key or virtual number, followed by @sip.ai4call.com:5060.
Ready to connect your PBX to AI4CALL?
Tell us about your setup: we'll help you configure the IP2IP SIP trunk and get your voice assistant into production.