---
title: Whitelist TelecomsXchange on your switch (Interconnect Info)
url: https://help.telecomsxchange.com/sellers/interconnect-info/
audience: For Sellers
summary: "Go to Routes \u2192 Interconnect Info. Whitelist the TelecomsXchange platform\
  \ IP, 174.136.44.213, on your firewall and switch. Voice arrives by SIP over UDP\
  \ from source ports 5060\u20135072 with all codecs passed through; SMS arrives by\
  \ an SMPP transceiver bind to your server. Each of your routes has a card with its\
  \ exact destination, tech prefix and SMPP system ID."
updated: '2026-10-21'
verified_commit: 83b4ebc96d0081a25213776d5a8871bd04941125
---

# Whitelist TelecomsXchange on your switch (Interconnect Info)

> Go to Routes → Interconnect Info. Whitelist the TelecomsXchange platform IP, 174.136.44.213, on your firewall and switch. Voice arrives by SIP over UDP from source ports 5060–5072 with all codecs passed through; SMS arrives by an SMPP transceiver bind to your server. Each of your routes has a card with its exact destination, tech prefix and SMPP system ID.

## What your network must let in

1. **TelecomsXchange**: Sends from platform IP 174.136.44.213
2. **Your firewall** (via SIP UDP `5060`–`5072`): Allows the platform IP and source ports
3. **Switch or SMSC** (via `14165551234`): Codecs pass through; SMPP binds as transceiver

Your routes only carry traffic once your switch accepts calls and messages from TelecomsXchange. **Interconnect Info** lists everything your network team needs to whitelist.

## Where do I find it?

Go to **Routes → Interconnect Info**. The page, **Whitelist Configuration**, has three parts: general SIP information, general SMPP information, and a card for each of your routes.

## What do I whitelist for voice?

| | |
|---|---|
| TCXC Platform IP | **174.136.44.213** |
| Protocol | SIP over UDP |
| Source Port Range | 5060 to 5072 |
| Codec Support | Pass-through: no transcoding |
| Number format | E.164 international, such as `14165551234` |

Allow the platform IP on your firewall and in your switch's access list, and accept SIP from source ports 5060 to 5072 to the host and port you set on the route. Media follows the SIP session; whatever codec the buyer offers is passed to you unchanged, so support the codecs you want to receive.

## What do I whitelist for SMS?

| | |
|---|---|
| TCXC Platform IP | **174.136.44.213** |
| Bind Type | Transceiver |
| SMPP Version | 3.4 or 5.0 |
| TLS Support | Optional |

TelecomsXchange connects to your SMPP server, not the other way round: it binds as a transceiver with the system ID and password you configured on the route. Allow the platform IP on the SMPP port you gave.

## What does each route's card show?

Under **Your Routes - Specific Configuration**, click a route to expand it. A **SIP** route shows the platform IP, **Your Destination** (the host and port you set), the **Source Port Range**, the route's **Tech Prefix** (or **None (default)**), the protocol and the **Route Status**, **Active** or **Blocked**.

An **SMPP** route shows **Your SMPP Server**, the **TCXC System ID** and **TCXC Password** TelecomsXchange binds with, whether **TLS Encryption** is enabled, the **SMPP Version**, and the enquire-link interval and throughput limit if you set them on the route.

![Interconnect Info with a SIP route and an SMPP route expanded, showing the platform IP, your destination or SMPP server, tech prefix, bind credentials and technical notes](https://help.telecomsxchange.com/assets/screenshots/seller-interconnect-info.jpg)

Change any of these values on the route itself: see [Add your first route](https://help.telecomsxchange.com/sellers/add-your-first-route/).

!!! warning
    The SMPP password is shown in full on this page. Treat it like any other credential and don't paste the page into tickets or chats.

## What if something goes wrong?

| Problem | What to check |
|---|---|
| No calls arrive on a new route | The platform IP is allowed on the firewall and ACL, the route's host and port match your switch, and the route isn't **Blocked**. |
| Calls arrive but fail to set up | Your switch accepts the codec the buyer sends; TelecomsXchange doesn't transcode. |
| No SMPP bind from TelecomsXchange | Your server accepts a transceiver bind from the platform IP with the system ID and password on the card, and TLS matches the route setting. |
| No routes configured yet | Click **Add Your First Route**; the cards appear once a route exists. |

## Frequently asked questions

**Q: Which IP address sends me traffic?**

A: 174.136.44.213, the TelecomsXchange platform IP, for both SIP and SMPP. Click Copy on the page to copy it.

**Q: Which codecs do I need to support?**

A: Whatever the buyer sends: TelecomsXchange passes all codecs through and doesn't transcode.

**Q: In which format do numbers arrive?**

A: E.164 international format without +, for example 14165551234, after your route's tech prefix if it has one.

**Q: How does SMS reach my SMPP server?**

A: TelecomsXchange binds to your server as a transceiver with the system ID and password shown on the route's card, using SMPP 3.4 or 5.0, with TLS if your route has it enabled.