Bring Your Own Carrier (BYOC)

Bring Your Own Carrier (BYOC) lets you keep your existing carrier relationship, SBC, or on-premise PBX and route that traffic through Vobiz. Your numbers stay where they are — Vobiz becomes the platform layer on top.

Where do the IPs and numbers come from?Both come from your existing telephony provider, not from Vobiz.

What we need	Where you get it
SIP signalling IPs / CIDR blocks	Your carrier or SBC provider publishes these. If you run your own SBC or PBX, it is that server’s public IP.
Phone numbers (DIDs)	You already own them at your provider. They stay there — you tell us which ones to expect.

Finding your carrier’s IPs

If you use a hosted provider, the signalling IPs are in their public documentation:

Provider	Where to look
Plivo	”SIP signaling” page — lists `phone.plivo.com` / `app.plivo.com` and the external SIP endpoint IPs
Twilio	”Elastic SIP Trunking IP addresses” — published as CIDR blocks
Telnyx	”SIP connection IPs”
Exotel / Ozonetel / Knowlarity	Supplied by your account manager on request

If you run your own SBC — FreeSWITCH, Asterisk, Kamailio, OpenSIPS, Avaya, or Cisco CUBE — there is nothing to look up. It is the public IP of that machine, or the NAT address it presents.

The exact phrasing to send your provider: “Please send me the source IP addresses your platform uses for outbound SIP signalling.” That is the list we need.

1. What you send us

1.1 Your SIP signalling IPs

Individual IPs or CIDR blocks. All of these are valid:

0.113.45              single host
0.113.0/27            a block
1f1c:...:3891/128    IPv6, if your provider uses it

Every IP that may originate a call must be listed. Traffic from an address that is not on the list is rejected with 403 Forbidden — this is the single most common cause of a failed BYOC launch.

1.2 Transport and port

UDP or TCP  →  port 5060
TLS         →  port 5061

If you use TLS, state the port explicitly. A TLS trunk submitted without a port falls back to 5060, and calls then ring for roughly 10 seconds before failing without a clear error. Confirm the port before you go live.

1.3 Your phone numbers

The E.164 numbers you are bringing, for example +919876543210. They remain owned by and billed through your provider. We map them to your trunk so inbound calls route to the right place.

1.4 Where we deliver calls to you (origination URI)

The hostname or IP your equipment listens on:

sip:sbc.yourcompany.com          or       sip:203.0.113.45:5060

You can supply a second URI as failover, with its own priority and weight. See Origination URIs for how priority and weight are applied.

1.5 Choose an authentication method

Method	How it works	Best when
IP-based (recommended)	We whitelist your IPs. No password, no registration.	Your IPs are static
SIP digest	Username and password we issue	Your IPs are dynamic

You can use both across different trunks. See IP ACLs and Credentials.

2. What you whitelist on your side

IP Address Whitelisting is the authoritative, always-current list of every Vobiz IP address and port. Whitelist the SIP signalling and RTP media entries from that page on your firewall or SBC — those are the ranges a BYOC trunk uses.

IP Address Whitelisting

All Vobiz SIP signalling, RTP media, and callback IPs with ports and directions.

Two BYOC-specific points on top of that list:

Point your trunk at sip.vobiz.ai. It resolves round-robin across the Vobiz signalling SBCs, so use the hostname rather than pinning a single IP.
Media is direct, signalling is proxied. RTP flows between your equipment and our media layer, not through the signalling SBCs — so the RTP media entries have to be open independently of the SIP ports. Whitelist the CIDR blocks rather than individual hosts; the media fleet scales with load and new hosts appear inside those blocks.

Whitelisting is mutual. Allowing our IPs on your side is separate from us whitelisting yours. Both are required before calls will complete. Re-confirm the current list with us at provisioning time.

3. Provisioning process

You send us your details

Everything in section 1: signalling IPs, transport and port, numbers, origination URI, and authentication method.

We create the carrier record

Vobiz whitelists your IPs on our SBCs.

We create the trunk

Vobiz provisions the trunk and registers your numbers against it.

You whitelist our ranges

Allow the signalling and media ranges from section 2 through your firewall.

You point your SBC at Vobiz

Direct your SBC or carrier at sip.vobiz.ai.

Test both directions

Place a test call each way. We confirm that signalling and media are both established.

Typical turnaround once we have your details: same business day.

4. Worth knowing before you start

Concurrency and CPS are enforced per account

Limits apply to your account as a whole, not per trunk — your base account limit plus any purchased channel capacity. If you need a specific ceiling, tell us up front so we can set it during provisioning.

Caller ID must be a number you own on the account

Presenting a CLI that is not registered to you is rejected with 403. If you release a number, update your dialler’s outbound caller ID at the same time — calls presenting the released number will fail.

Media is direct, signalling is proxied

A firewall that allows 5060/5061 but not the RTP range produces a call that connects with no audio. If you get one-way or no audio, check the UDP media range first.

Codec support

We support G.711 (PCMU/PCMA), G.729, and Opus. Send us your preference order and we will configure the trunk to match.

5. Ready-to-send checklist

Copy this, fill it in, and send it to support@vobiz.ai.

BYOC onboarding checklist

Company:
Provider (or "own SBC"):

SIP signalling IPs / CIDR:
Transport:                        UDP / TCP / TLS
Port:                             5060 / 5061 / other
Auth method:                      IP-based / SIP digest

Numbers (E.164):

Origination URI (where we send calls to you):
Failover URI (optional):

Codec preference:
Expected concurrent calls:
Expected calls per second:
Technical contact (name / email / phone):

Next steps

SIP Trunking

How SIP signalling and RTP media work, and where trunks fit.

Create a Trunk

Provision a trunk over the API once your carrier record exists.

IP Access Control Lists

Manage the IP addresses authorised to use your trunk.

IP Address Whitelisting

The full platform IP list, including callback delivery.

Getting Started

Using Vobiz Platform

Compliance (India)

Tools

Bring Your Own Carrier (BYOC)

Finding your carrier’s IPs

1. What you send us

1.1 Your SIP signalling IPs

1.2 Transport and port

1.3 Your phone numbers

1.4 Where we deliver calls to you (origination URI)

1.5 Choose an authentication method

2. What you whitelist on your side

IP Address Whitelisting

3. Provisioning process

4. Worth knowing before you start

5. Ready-to-send checklist

Next steps

SIP Trunking

Create a Trunk

IP Access Control Lists

IP Address Whitelisting

​Finding your carrier’s IPs

​1. What you send us

​1.1 Your SIP signalling IPs

​1.2 Transport and port

​1.3 Your phone numbers

​1.4 Where we deliver calls to you (origination URI)

​1.5 Choose an authentication method

​2. What you whitelist on your side

IP Address Whitelisting

​3. Provisioning process

​4. Worth knowing before you start

​5. Ready-to-send checklist

​Next steps

SIP Trunking

Create a Trunk

IP Access Control Lists

IP Address Whitelisting

Finding your carrier’s IPs

1. What you send us

1.1 Your SIP signalling IPs

1.2 Transport and port

1.3 Your phone numbers

1.4 Where we deliver calls to you (origination URI)

1.5 Choose an authentication method

2. What you whitelist on your side

3. Provisioning process

4. Worth knowing before you start

5. Ready-to-send checklist

Next steps