---
title: Connect Zoom Phone BYOC to TelecomsXchange
url: https://help.telecomsxchange.com/integrations/zoom-phone/
audience: Integrations
summary: Zoom Phone Premise Peering (BYOC-P) peers Zoom's data centres with an SBC
  you run, over TLS on port 5061 with SRTP, so TelecomsXchange can't connect to Zoom
  directly. Add the SBC, a route group and a SIP group in the Zoom web portal and
  assign BYOC numbers; on the SBC's carrier side, send SIP over UDP to sip01.telecomsxchange.com
  port 5060 with TECH_PREFIX in front of the E.164 number, authorised by IP or digest.
updated: '2026-10-23'
verified_commit: 83b4ebc96d0081a25213776d5a8871bd04941125
---

# Connect Zoom Phone BYOC to TelecomsXchange

> Zoom Phone Premise Peering (BYOC-P) peers Zoom's data centres with an SBC you run, over TLS on port 5061 with SRTP, so TelecomsXchange can't connect to Zoom directly. Add the SBC, a route group and a SIP group in the Zoom web portal and assign BYOC numbers; on the SBC's carrier side, send SIP over UDP to sip01.telecomsxchange.com port 5060 with TECH_PREFIX in front of the E.164 number, authorised by IP or digest.

## Zoom Phone to a route via your SBC

1. **Zoom Phone**: SIP group → route group
2. **Your SBC** (via TLS 5061, SRTP): AudioCodes, Ribbon or other supported SBC
3. **TelecomsXchange** (via `80039#447700900123`): sip01, UDP 5060
4. **Seller's route**: The route you purchased

This guide connects Zoom Phone to TelecomsXchange with **Bring Your Own Carrier, Premise Peering (BYOC-P)**: Zoom Phone users call out through a purchased route, and numbers bought on TelecomsXchange ring in Zoom. Zoom's data centres peer with an SBC you run, and the SBC peers with TelecomsXchange. For the full list of TelecomsXchange values, see [Connect a SIP platform](https://help.telecomsxchange.com/integrations/connect-sip-platforms/).

!!! warning
    Zoom Phone Premise Peering connects to a **supported SBC** over **TLS** (port 5061, Zoom's DigiCert certificates) with encrypted media. TelecomsXchange supports SIP over **UDP only**, with no TLS or SRTP, and does not accept REGISTER, so it **can't peer with Zoom directly**. The SBC terminates TLS towards Zoom and talks plain SIP and RTP over UDP to TelecomsXchange.

## How does the call flow?

| Leg | From → to | Transport | Number format |
|---|---|---|---|
| Zoom side | Zoom Phone data centres ↔ your SBC's public IP, for example `203.0.113.10:5061` | TLS, SRTP (as Zoom specifies at onboarding) | E.164 with `+`: `+447700900123` |
| Carrier side | Your SBC ↔ `sip01.telecomsxchange.com:5060` | UDP, RTP | Tech prefix + E.164 without `+`: `80039#447700900123` |

Premise Peering needs connectivity in both directions between the SBC and Zoom's data centres. Zoom gives you its signalling and media addresses, and the ports to open, for your region when it enables BYOC.

## Before you start

- A [SIP account](https://help.telecomsxchange.com/buyers/create-your-first-account/) with the SBC's public IP, for example `203.0.113.10`, or a VoIP login and password from **Edit Account → Add SIP Digest Auth**.
- A [purchased route](https://help.telecomsxchange.com/buyers/find-and-buy-routes/) and its tech prefix from **My Interconnections**, for example `80039#`.
- A Zoom Phone account with Premise Peering (BYOC) enabled by Zoom, and an admin role with BYOC permissions.
- An SBC that Zoom supports for Premise Peering (AudioCodes Mediant, Ribbon, Oracle and others), with a public IPv4 address and Zoom's DigiCert root and intermediate certificates installed.
- [Phone numbers](https://help.telecomsxchange.com/buyers/virtual-numbers-dids/) bought on TelecomsXchange, to use as BYOC numbers.

## How do I connect Zoom Phone to the SBC?

In the Zoom web portal, as an admin:

1. Go to **Phone System Management → Company Info**, choose the account (or a site), open **Settings → Routing**, and next to **Session Border Controllers** choose **Add**. Enter a display name and the SBC's public IPv4 address and port (TLS 5061), and save.
2. Under **Routing → Route Groups**, add a route group containing the SBC (add a second SBC for failover or load sharing).
3. Under **Routing → SIP Groups**, add a SIP group and assign the route group to it. Outbound calls from numbers in the SIP group go to its route group.
4. Under **Phone System Management → Phone Numbers → BYOC**, add the numbers you bought on TelecomsXchange (in E.164 with `+`), select the SIP group, and assign them to users, auto receptionists or call queues. If you can't add BYOC numbers yourself, Zoom support adds them.

The SBC vendor's Zoom configuration note covers the Zoom-facing side: the TLS context and certificates, Zoom's IP addresses, SRTP and codecs. The [AudioCodes](https://www.audiocodes.com/media/avbbyfws/audiocodes-sbc-with-zoom-phone-premise-peering-configuration-note.pdf) and [Oracle](https://oracle.com/webfolder/technetwork/acmepacket/Zoom/ZoomPremisePeeringwithOracleESBC.pdf) notes are linked under References.

## How do I send calls to TelecomsXchange?

On the SBC, the carrier side is an ordinary UDP peer. The [AudioCodes SBC](https://help.telecomsxchange.com/integrations/audiocodes-sbc/) and [Ribbon SBC](https://help.telecomsxchange.com/integrations/ribbon-sbc/) guides give the exact menus; the settings are:

| SBC setting | Value |
|---|---|
| Carrier peer | `sip01.telecomsxchange.com`, port `5060`, transport UDP |
| Registration | Off. TelecomsXchange is peering only |
| Keepalive (OPTIONS) | Off towards TelecomsXchange, which answers OPTIONS only within a call. Keep OPTIONS on towards Zoom if your SBC's Zoom note says so |
| Authentication | Send from the SBC's IP authorised on the account, or answer the 401/407 challenge with `VOIP_LOGIN` and `VOIP_PASSWORD` (the account's **VoIP Login** and **VoIP Password**) |
| Media | RTP, no SRTP; G.711 or G.729 as your route supports. TelecomsXchange doesn't transcode, so let the SBC transcode if Zoom and the route share no codec |
| NAT | The SBC's public IP in SIP and SDP on the carrier interface |

Add the tech prefix in the number manipulation for calls from Zoom to TelecomsXchange: remove the leading `+`, then add `TECH_PREFIX` in front, so `+447700900123` leaves the SBC as `80039#447700900123`. Then route calls from the Zoom peer to the TelecomsXchange peer.

!!! tip
    For several routes, add one manipulation and routing rule per destination prefix, each with its own tech prefix, or dial a [routing group](https://help.telecomsxchange.com/buyers/routing-groups-and-route-testing/) prefix such as `444101#` and let TelecomsXchange choose.

## How do I receive calls from TelecomsXchange?

Calls come from `174.136.44.213` over UDP, from source ports 5060 to 5072, with the number in E.164 without `+`, such as `14165551234`.

1. On the SBC, classify `174.136.44.213` as the TelecomsXchange peer, and allow it on the firewall for UDP 5060 and the RTP range.
2. Add a number manipulation for calls from TelecomsXchange to Zoom that adds `+`, so `14165551234` reaches Zoom as `+14165551234`.
3. Route those calls to the Zoom peer. Zoom rings whatever the BYOC number is assigned to.

Selling routes that terminate in Zoom Phone isn't a use case for Premise Peering: Zoom only accepts calls to BYOC numbers on your own account.

## How do I receive calls on numbers I bought?

Set each number's **SIP Endpoint (Primary)** in **DID Settings** on TelecomsXchange to the SBC's carrier side, for example `sip:14165551234@203.0.113.10:5060`, optionally with a second SBC as **SIP Endpoint (Secondary)**. Add the same number in Zoom as a BYOC number in the SIP group and assign it.

## How do I test it?

1. From the Zoom Phone app, call a number covered by the route.
2. On the SBC, follow the call in its trace tool (AudioCodes Syslog Viewer, Ribbon trace logs, or Wireshark): the TLS leg from Zoom with `+447700900123`, then the UDP INVITE to `80039#447700900123` (or `80039%23447700900123`) and TelecomsXchange's reply.
3. In the TelecomsXchange portal, watch the call in **Live Calls** and find its SIP code in **Logs → CDR (Voice)**.
4. In the Zoom web portal, check the call in **Phone System Management → Call Logs**.

## What if something goes wrong?

| You see | What to do |
|---|---|
| Zoom can't reach the SBC, or calls from Zoom never arrive | TLS or connectivity problem on the Zoom side: certificates, the SBC's public IP and port in **Session Border Controllers**, or Zoom's addresses blocked on the firewall. This is between Zoom and the SBC, not TelecomsXchange. |
| 401 or 407 repeated, then the call fails | The SBC isn't answering TelecomsXchange's challenge. Check the VoIP login and password in its authentication settings. |
| 403 Forbidden | The SBC's public IP isn't authorised and no credentials were sent. Compare with **IP Address** and **Additional Allowed IPs** on **Edit Account**; check balance. |
| 404 Not Found | Tech prefix missing or `+` still in the number. Check the outbound number manipulation in the SBC trace. |
| 408 or 503 from TelecomsXchange | The SBC can't reach sip01 on UDP 5060, or the route is blocked or failed. Check the firewall and **My Interconnections**. |
| One-way audio | The SBC advertises a private IP on the carrier side, or RTP from `174.136.44.213` is blocked. Check NAT and media settings on the carrier interface. |
| Inbound calls don't ring in Zoom | No `+` on the number, the number isn't a BYOC number in the right SIP group, or `174.136.44.213` isn't classified to the TelecomsXchange peer. |

## References

- [Zoom: Bring Your Own Carrier, Premises Peering (BYOC-P), Zoom Phone bluepaper](https://library.zoom.com/zoom-workplace/zoom-phone/zoom-phone-bluepaper/overview/bring-your-own-carrier-premises-peering-byoc-p)
- [Zoom: Integrate ZPLS with PSTN (adding a Session Border Controller in the web portal)](https://library.zoom.com/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/optional-tasks/optional-integrate-zpls-with-pstn)
- [AudioCodes: SBC with Zoom Phone Premise Peering configuration note](https://www.audiocodes.com/media/avbbyfws/audiocodes-sbc-with-zoom-phone-premise-peering-configuration-note.pdf)
- [Oracle: Zoom Premise Peering with Oracle Enterprise SBC](https://oracle.com/webfolder/technetwork/acmepacket/Zoom/ZoomPremisePeeringwithOracleESBC.pdf)
- [anynode: Zoom Phone Premise Peering, Zoom web portal configuration](https://docs.anynode.de/anynode-technote-en-zoom-phone-premise-peering/zoom-web-portal-configuration.sec6.html)

## Frequently asked questions

**Q: Can Zoom Phone register to TelecomsXchange?**

A: No. TelecomsXchange is peering only and does not accept REGISTER. Zoom Phone doesn't connect to carriers in Premise Peering anyway: it peers with your SBC, and the SBC peers with TelecomsXchange by IP or digest authentication.

**Q: Can Zoom Phone connect to TelecomsXchange without an SBC?**

A: No. Premise Peering connects Zoom's data centres to an SBC you run, over TLS with Zoom's certificates. TelecomsXchange supports only SIP over UDP and isn't a Zoom BYOC Cloud Peering partner, so the SBC is required.

**Q: Which SBC can I use?**

A: One Zoom supports for Premise Peering, such as AudioCodes Mediant, Ribbon or Oracle. Check with your Zoom account team; see the AudioCodes and Ribbon guides for the TelecomsXchange side.

**Q: Where does the tech prefix go?**

A: On the SBC, in the number manipulation for calls from Zoom to TelecomsXchange: Zoom sends +447700900123 and the SBC sends 80039#447700900123 to sip01.