---
title: Connect a Ribbon SBC to TelecomsXchange
url: https://help.telecomsxchange.com/integrations/ribbon-sbc/
audience: Integrations
summary: On a Ribbon SBC Edge (SBC 1000/2000) or SBC SWe Lite, add a SIP Server Table
  entry for sip01.telecomsxchange.com port 5060 over UDP with Monitor set to None,
  a SIP signaling group that uses it with 174.136.44.213 as its Federated IP, a transformation
  table that turns (.*) into 80039#\1, and a call route to that signaling group. Authorise
  the SBC's public IP on the account, or add a Remote Authorization Table with the
  VoIP login.
updated: '2026-10-23'
verified_commit: 83b4ebc96d0081a25213776d5a8871bd04941125
---

# Connect a Ribbon SBC to TelecomsXchange

> On a Ribbon SBC Edge (SBC 1000/2000) or SBC SWe Lite, add a SIP Server Table entry for sip01.telecomsxchange.com port 5060 over UDP with Monitor set to None, a SIP signaling group that uses it with 174.136.44.213 as its Federated IP, a transformation table that turns (.*) into 80039#\1, and a call route to that signaling group. Authorise the SBC's public IP on the account, or add a Remote Authorization Table with the VoIP login.

## Your SBC to a purchased route

1. **PBX, Teams or Zoom**: Behind your Ribbon SBC
2. **Ribbon SBC**: Signaling group TCXC, UDP
3. **TelecomsXchange** (via `80039#447700900123`): sip01, UDP 5060
4. **Seller's route**: The route you purchased

A Ribbon SBC Edge (SBC 1000 or 2000) or SBC SWe Lite connects to TelecomsXchange as a SIP peer: a **SIP Server Table** that points at sip01, a **SIP signaling group** that sends and accepts calls, a **transformation table** that adds the tech prefix, and entries in a **call routing table**. For every TelecomsXchange value in one place, see [Connect a SIP platform](https://help.telecomsxchange.com/integrations/connect-sip-platforms/).

!!! warning
    TelecomsXchange does not accept SIP REGISTER, and it supports SIP over **UDP only**, with RTP (no TLS or SRTP). Use UDP toward it, don't attach a Contact Registrant Table, and set **Monitor** to **None**. The SBC is recognised by its **source IP** or by **digest authentication on the INVITE**.

## Before you start

- A [SIP account](https://help.telecomsxchange.com/buyers/create-your-first-account/) on TelecomsXchange 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#`. In this guide, `TECH_PREFIX` stands for that value, and `VOIP_LOGIN` and `VOIP_PASSWORD` for the account's **VoIP Login** and **VoIP Password**.
- The SBC's WAN port configured, DNS servers set (so it can resolve sip01), and a working signaling group toward your PBX, Teams or Zoom.
- To sell: a [route](https://help.telecomsxchange.com/sellers/add-your-first-route/) with **IP Address:Port** set to the SBC, for example `203.0.113.10:5060`, and the values in [Interconnect Info](https://help.telecomsxchange.com/sellers/interconnect-info/).

## How do I send calls to TelecomsXchange?

All tables are on the Web UI's **Settings** tab.

1. **Media List** (**Media → Media List**): make sure the list you'll use for TelecomsXchange contains the route's codecs (G.729, G.711) and no SDES-SRTP crypto profile.
2. **Remote Authorization Table** (**SIP → Remote Authorization Tables**), only for the digest variant: add a table `TCXC-Auth` with an entry **Realm** `174.136.44.213`, **Authentication ID** `VOIP_LOGIN` and **Password** `VOIP_PASSWORD`. Skip it for IP authentication.
3. **SIP Server Table** (**SIP → SIP Server Tables**): add a table `TCXC` and an entry:

| Field | Value |
|---|---|
| Server Lookup | IP/FQDN |
| Priority | 1 |
| Host FQDN/IP | `sip01.telecomsxchange.com` |
| Port | `5060` |
| Protocol | **UDP** |
| Monitor | **None** (TelecomsXchange answers OPTIONS only within a call) |
| Remote Authorization Table | `TCXC-Auth` for digest, otherwise none |
| Contact Registrant Table | none (no registration) |

4. **Signaling Group** (**Signaling Groups → Create Signaling Group → SIP Signaling Group**): add one named `TCXC`:
    - **SIP Mode**: **Basic Call**. **Agent Type**: **Back-to-Back User Agent**.
    - **SIP Server Table**: `TCXC`. **Media List ID**: the list from step 1.
    - **Signaling/Media Source IP**: the WAN interface. Behind NAT, set **Static NAT - Outbound** with your public IP.
    - **Listen Ports**: `5060`, **UDP**.
    - **Federated IP/FQDN**: `174.136.44.213`, netmask `255.255.255.255`, so the group accepts calls only from TelecomsXchange.
    - **Call Routing Table**: the table for calls coming *from* TelecomsXchange (see below).
5. **Transformation Table** (**Call Routing → Transformation**): add a table `To-TCXC-80039` with one entry:

| Field | Value |
|---|---|
| Input Field Type | Called Address/Number |
| Input Field Value | `\+?(00)?(.*)` |
| Output Field Type | Called Address/Number |
| Output Field Value | `80039#\2` |

The regular expression strips a leading `+` or `00`, then puts the tech prefix in front, so `+447700900123` leaves as `80039#447700900123`. If your numbers already arrive in E.164 without `+`, `(.*)` → `80039#\1` is enough.

6. **Call Routing Table** (**Call Routing → Call Routing Table**): in the table used by your PBX, Teams or Zoom signaling group, add an entry with **Transformation Table** `To-TCXC-80039`, **Destination Signaling Groups** `TCXC`, and a **Priority** below any more specific routes. On the SBC Edge a route entry is only used when its transformation table matches, so to send only some destinations here, narrow the input, for example `\+?(00)?(44.*)` for UK numbers.

!!! tip
    For several routes, add one transformation table and routing entry per 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 on routes you sell, and on numbers you bought, come from `174.136.44.213` over UDP, from source ports 5060 to 5072, with the number in E.164 format such as `14165551234`.

1. Allow `174.136.44.213` on your firewall for UDP 5060 and the SBC's media port range.
2. The `TCXC` signaling group's **Federated IP/FQDN** already admits `174.136.44.213`. Calls from other addresses are not accepted on it.
3. Create a call routing table `From-TCXC` and set it as the `TCXC` signaling group's **Call Routing Table**. Add entries to your PBX, carrier, Teams or Zoom signaling groups.
4. Teams expects numbers in `+E.164`; on the route to Teams, use a transformation `(.*)` → `+\1`.
5. If your TelecomsXchange route adds an **Outgoing Prefix** (**Edit Route → Outgoing Number Translation Parameters**), strip it with a transformation on the `From-TCXC` routes, for example `77#(.*)` → `\1`.

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

Set the number's **SIP Endpoint (Primary)** in **DID Settings** on TelecomsXchange to the SBC, for example `sip:14165551234@203.0.113.10:5060`. The call arrives on the `TCXC` signaling group and follows the `From-TCXC` routing table to the PBX, Teams user or Zoom user that owns the number.

## How do I use it with Microsoft Teams or Zoom Phone?

Microsoft Teams Direct Routing and Zoom Phone BYOC (Bring Your Own Carrier) only connect to a certified SBC over SIP TLS with SRTP. TelecomsXchange doesn't offer TLS or SRTP, so it can't be the TLS endpoint for Teams or Zoom. The Ribbon SBC sits in between:

- **Teams or Zoom side**: a signaling group on TLS port 5061 with a TLS Profile, an SRTP crypto profile in its media list, and a certificate for your SBC's FQDN, as in Ribbon's Teams and Zoom configuration guides.
- **TelecomsXchange side**: the UDP signaling group in this guide, with RTP. The SBC converts SRTP to RTP between the two signaling groups.

See [Connect Microsoft Teams](https://help.telecomsxchange.com/integrations/microsoft-teams/) and [Connect Zoom Phone](https://help.telecomsxchange.com/integrations/zoom-phone/) for the Teams and Zoom side.

## How do I test it?

1. Turn on SIP and call-routing logging on the SBC and send it to a syslog server; open the logs in **Ribbon LX** to see each call's ladder and routing decision.
2. Place a call to a number covered by the route.
3. In the log, look for the INVITE to `80039#447700900123` toward `174.136.44.213` and the reply. The **Monitor** tab shows the signaling group's state and active calls.
4. On TelecomsXchange, watch the call in **Live Calls** and find its SIP code in **Logs → CDR (Voice)**.

## What if something goes wrong?

| You see | What to do |
|---|---|
| 401 or 407 repeated, then the call fails | The SBC isn't answering the challenge. Attach a Remote Authorization Table with the VoIP login and password to the SIP server entry, with realm `174.136.44.213`. |
| 403 Forbidden | The SBC's public IP isn't authorised and no credentials were sent, or the account is blocked or out of balance. Behind NAT, authorise the public address. |
| 404 Not Found | Missing or wrong tech prefix, or `+`/`00` left in the number. Check the transformation table's output in Ribbon LX. |
| 408 Request Timeout | No reply from sip01. Check the SIP server entry (host, port 5060, **UDP**), DNS on the SBC and outbound UDP 5060. |
| Signaling group or server shown down | **Monitor** is set to SIP Options. Set it to **None**. |
| 503 Service Unavailable | The route is blocked or failed on the seller's side. Check **My Interconnections**; add a second route entry. |
| One-way or no audio | The SBC advertises a private IP, or RTP is blocked. Set **Static NAT - Outbound** and open the media port range. On Teams or Zoom calls, check that SRTP is only on that side. |
| Inbound calls rejected | `174.136.44.213` isn't in the signaling group's **Federated IP/FQDN**, the listen port isn't UDP 5060, or the `From-TCXC` table has no matching route. |

## References

- [Ribbon SBC Edge: Creating and modifying SIP signaling groups](https://publicdoc.rbbn.com/x/ZoVjCQ)
- [Ribbon SBC Edge: Managing SIP signaling groups](https://publicdoc.rbbn.com/display/UXDOC110/Managing+SIP+Signaling+Groups)
- [Ribbon SBC Edge: SIP server tables](https://publicdoc.rbbn.com/x/FlopFg)
- [Ribbon SBC Edge interoperability guide (table order: Remote Authorization, SIP Server, Signaling Group, Transformation, Call Routing)](https://ribboncommunications.com/sites/default/files/2023-03/Ribbon%20SBC%20Edge%20R9.0%20Interop%20with%20IP-PBX%20for%20Deutsche%20Telekom%20CompanyFlex%20SIP%20Trunk%20%20Interoperability%20Guide.pdf)
- [Ribbon SBC SWe Lite with Microsoft Teams Direct Routing (Twilio interop guide)](https://ribboncommunications.com/sites/default/files/2023-03/Ribbon%20SBC%20Edge%20SWe%20Lite%20R9.0%20on%20AWS%20Interop%20with%20Cisco%20UCM%20and%20Microsoft%20Teams%20Direct%20Routing%20for%20Twilio%20Elastic%20SIP%20Trunking%20%20I.pdf)

## Frequently asked questions

**Q: Can the Ribbon SBC register to TelecomsXchange?**

A: No. TelecomsXchange is peering only and does not accept REGISTER. Don't attach a Contact Registrant Table to the TelecomsXchange SIP server; use IP authentication or a Remote Authorization Table for digest on the INVITE.

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

A: In a transformation table on the call route to TelecomsXchange: input Called Address/Number (.*), output Called Address/Number 80039#\1. Each purchased route can have its own transformation and route entry.

**Q: Can I connect Microsoft Teams or Zoom Phone to TelecomsXchange through the SBC?**

A: Yes. Teams Direct Routing and Zoom Phone BYOC need TLS and SRTP, which TelecomsXchange doesn't offer. The Ribbon SBC terminates TLS and SRTP toward Teams or Zoom and talks to TelecomsXchange over UDP and RTP.

**Q: Does this work on Ribbon SBC Core?**

A: The same design applies on SBC Core (SBC 5400, 7000 and SWe): a zone, an IP peer for sip01 on UDP 5060, a SIP trunk group that accepts 174.136.44.213, and a number manipulation that adds the prefix. The steps below use the SBC Edge Web UI.