Bring your own carrier (SIP trunk)
If you already have phone numbers with a carrier or a PBX, you can connect them to VoisX over a standard SIP trunk instead of buying new numbers. Your numbers stay with your carrier. Calls travel between your carrier and our SIP gateway, and your agents answer and place calls on them just as they do on numbers bought through VoisX.
- Inbound: your carrier or PBX sends calls for your numbers to our SIP host. We match the dialed number to its agent, and the agent answers.
- Outbound: when an agent places a call, we send it to your carrier's SIP endpoint with the credentials you give us, using one of your numbers as caller ID.
This works with carriers such as Twilio Elastic SIP Trunking, Telnyx and Exotel, and with your own PBX (for example Asterisk or 3CX).
Set up a trunk
- Open your project and go to Channels & numbers.
- Click New channel and choose Bring your own carrier (SIP).
- On the trunk page, name the trunk and choose the agent that answers its calls. You can also pick a post-call workflow.
- Under Connect your carrier, copy the SIP host and the IP range to allowlist. You enter these at your carrier.
- Under Inbound authentication, choose how we recognise calls from your carrier (see Authentication).
- Under Outbound calls, enter your carrier's SIP host, port, transport and, if needed, a username and password. Add the Caller ID numbers your carrier lets you present. Leave the host empty for an inbound-only trunk.
- Click Save trunk.
- Under Numbers on this trunk, click Add numbers and enter your numbers in E.164 format, for example
+971501234567. You can paste several, one per line or separated by commas. - Point your carrier at us. The setup checklist ticks this off when the first call arrives.
Registering your own numbers is free. They count toward your project's and organization's number limits.
Our SIP hosts and IP ranges
Use the host for the region your project is in. The trunk page always shows the right values for your project, so copy them from there.
| Region | SIP host | IP range to allowlist |
|---|---|---|
| India | sip.in.voisx.ai | 20.192.2.240/29 |
| UAE | sip.uae.voisx.ai | 20.233.33.248/29 |
| Value | |
|---|---|
| Signaling | Port 5060, UDP or TCP |
| Media (RTP) | UDP ports 20000 to 29999 |
| Codecs | G.711 µ-law (PCMU) and G.711 A-law (PCMA) |
Most carriers and PBXs only accept SIP and media from known addresses. Allowlist the whole IP range, for both signaling and media. Don't allowlist the address a host name resolves to: our host can resolve to any address in the range.
Authentication
Choose how we recognise inbound calls from your carrier:
| Option | How it works | Use when |
|---|---|---|
| IP allowlist | You enter the public IP addresses or ranges your carrier sends SIP from, for example 203.0.113.0/29. Calls from those addresses are accepted. Up to 32 ranges; IPv4 ranges must be /16 or narrower, IPv6 /48 or narrower. | Your carrier publishes fixed signaling IPs (Twilio, Telnyx and most large carriers do). |
| Username and password | We generate a SIP digest username and password for the trunk. Your carrier or PBX answers our challenge with them. | Your source IP changes, or you send calls from a PBX with a dynamic IP. |
Calls that don't match any trunk are dropped without a response.
The trunk password is shown only once, right after you save. If you lose it, click Regenerate password. The old username and password stop working within about two minutes, so update your carrier straight away.
For outbound calls, we answer your carrier's digest challenge with the username and password you entered under Outbound calls.
Call features
| Feature | Support |
|---|---|
| Codecs | G.711 µ-law and A-law. Calls in other codecs are not accepted. |
| Keypad input (DTMF) | RFC 4733 (telephone-event). In-band and SIP INFO DTMF are not supported. |
| Call transfer | Blind transfer with SIP REFER. If your carrier rejects REFER, we dial the transfer number through the same trunk and connect the two calls. |
| Outbound caller ID | Any number in the trunk's Caller ID numbers list. Your carrier must allow you to present it. |
| Call settings | Transfer, end-call phrases, silence hang-up, keypad input and recording all work as on bought numbers. |
Routing numbers to agents
Each number on the trunk goes to an agent. By default that is the trunk's agent. You can choose a different agent for a single number in the numbers list. Changing the trunk's agent re-routes every number on the trunk.
To stop calls to a number reaching an agent, click Remove next to it. The number stays yours at your carrier, and you can register it again later.
Outbound calling safety
Outbound calls on your own trunk follow the same rules as any other outbound call:
- Calling hours: calls are placed only inside the legal calling hours for the callee's country, and inside your project's own calling hours if you set them. See Calling hours.
- Limits: each project has a limit on how many calls it can place per minute and how many can be in progress at once.
You are responsible for having the right to call the people you dial and for following local telemarketing rules.
Billing
On a SIP trunk you pay your carrier directly for the line and the call minutes. VoisX charges for your agent's voice minutes as usual, and there is no number rental for numbers on your own trunk. See pricing for current rates.
Current limitations
- No encryption yet. TLS signaling and SRTP media are not supported. Use UDP or TCP on port 5060.
- Static trunks only. We don't register with your carrier or PBX (no SIP REGISTER), and we don't accept registrations. Your side sends calls to our host, and we send calls to the fixed host you enter.
Setup guides
Twilio Elastic SIP Trunking
- In the Twilio Console, go to Elastic SIP Trunking > Trunks and create a trunk.
- Origination (calls into VoisX): add an origination URI with your region's host, for example
sip:sip.in.voisx.ai:5060. - In VoisX, choose IP allowlist and enter Twilio's signaling IP ranges for the edge locations you use. Twilio lists them in its Elastic SIP Trunking documentation.
- Termination (calls from VoisX):
- Choose a termination SIP URI, for example
yourcompany.pstn.twilio.com. - Under Authentication, create a Credential List with a username and password and attach it to the trunk. You can also add an IP access control list with our IP range.
- In VoisX, set the outbound host to your termination URI, port 5060, and enter the credential list's username and password.
- Choose a termination SIP URI, for example
- Numbers: attach your Twilio numbers to the trunk, then add the same numbers to your VoisX trunk and add them as caller IDs.
Telnyx
- In the Telnyx Mission Control Portal, go to Voice > SIP Trunking and create a SIP connection.
- Choose the authentication type:
- IP address: add our IP range. In VoisX, choose IP allowlist and enter Telnyx's signaling IP ranges.
- Credentials: Telnyx gives you a username and password for outbound calls. For inbound calls, choose Username and password in VoisX and enter the generated username and password in the connection's inbound settings.
- Under Inbound, set the destination to your region's host, for example
sip.uae.voisx.ai, with transport UDP or TCP, and select G.711 µ-law and/or A-law. - Under Outbound, create or choose an outbound voice profile and attach the connection. In VoisX, set the outbound host to
sip.telnyx.com, port 5060. - Assign your numbers to the connection, then add them to your VoisX trunk.
Exotel and other carriers
Any carrier that offers a standard SIP trunk with G.711 audio can be connected. Ask your carrier (for Exotel, ask Exotel support) to:
- Enable SIP trunking on your account and create a trunk.
- Send calls for your numbers to your region's host, for example
sip.in.voisx.ai, port 5060, over UDP or TCP. - Accept calls and media from our IP range.
Then in VoisX:
- Choose IP allowlist and enter the signaling IPs your carrier sends from, or choose Username and password and give your carrier the generated credentials.
- Enter the termination host and credentials your carrier gives you under Outbound calls.
- Add your numbers to the trunk.
Your own PBX
Asterisk (PJSIP)
This example pjsip.conf connects to the India region, using IP authentication in both directions. Replace <VOISX_IP_RANGE> with the IP range from your trunk page.
[voisx]
type=endpoint
transport=transport-udp
context=from-voisx
disallow=all
allow=ulaw
allow=alaw
dtmf_mode=rfc4733
direct_media=no
rtp_symmetric=yes
force_rport=yes
rewrite_contact=yes
aors=voisx
from_domain=sip.in.voisx.ai
[voisx]
type=aor
contact=sip:sip.in.voisx.ai:5060
qualify_frequency=60
[voisx]
type=identify
endpoint=voisx
match=<VOISX_IP_RANGE>
To send a call to an agent, dial the agent's number (E.164) through the endpoint, for example in extensions.conf:
exten => _+X.,1,Dial(PJSIP/${EXTEN}@voisx)
If you use Username and password instead, add an auth section with the generated credentials and reference it from the endpoint:
[voisx-auth]
type=auth
auth_type=userpass
username=<generated username>
password=<generated password>
; and in the [voisx] endpoint section:
; outbound_auth=voisx-auth
For calls from VoisX to Asterisk, set the trunk's outbound host to your Asterisk server's public address, and handle the calls in the from-voisx context.
3CX
In the 3CX Management Console, add a Generic SIP Trunk. Menu names can differ between 3CX versions.
| Setting | Value |
|---|---|
| Registrar / Server / Gateway | Your region's host, for example sip.in.voisx.ai |
| Port | 5060 |
| Transport | UDP or TCP |
| Authentication | IP based, with IP allowlist in VoisX. For Username and password, enter the generated credentials and turn registration off. |
| Codecs | G.711 U-law and G.711 A-law only |
| DTMF | RFC 2833 / RFC 4733 |
Because we don't accept SIP REGISTER, make sure 3CX does not register the trunk. Add our IP range to 3CX's allowed IPs, then route the numbers that should reach agents through this trunk.
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| The trunk page says gateway details aren't available | SIP trunks are not enabled for your region yet. | Contact us. |
| Call connects but there's no audio | Media is blocked or sent to a private address. | Allow UDP 20000 to 29999 to and from our IP range. If your PBX is behind NAT, make sure it advertises its public IP (in Asterisk: external_media_address, external_signaling_address, rtp_symmetric=yes). |
| One-way audio | NAT on your side, or a firewall that allows media in one direction only. | Turn on symmetric RTP, turn off direct media or media bypass, and allow return traffic on the media ports. |
| 403 Forbidden | Authentication failed. | On inbound calls with Username and password, the password doesn't match: copy it again, or regenerate it. On outbound calls, your carrier rejected our credentials: check the outbound username and password. |
| 404 Not Found | The dialed number isn't on this trunk. | Add the number (E.164, with + and the country code) to the trunk. Check your carrier sends the number in E.164 format. |
| No response at all | The call didn't match any trunk, so it was dropped, or port 5060 is blocked. | Check you send to your region's host, from an address in the trunk's allowed ranges (or with the trunk's username), and that port 5060 is open. |
| 480 Temporarily Unavailable | Calls can't be taken right now, for example because your organization has run out of credit. | Check your organization's credit balance. If that's fine, contact us. |