---
title: Connect Yeastar P-Series to TelecomsXchange
url: https://help.telecomsxchange.com/integrations/yeastar/
audience: Integrations
summary: On a Yeastar P-Series PBX, add a SIP trunk of type Peer Trunk (not a register
  trunk) to sip01.telecomsxchange.com port 5060 over UDP, and authorise the PBX's
  public IP on your TelecomsXchange account. Add an outbound route that strips 00
  and prepends the tech prefix, so calls leave as 80039#447700900123, and inbound
  routes for your E.164 numbers.
updated: '2026-10-23'
verified_commit: 83b4ebc96d0081a25213776d5a8871bd04941125
---

# Connect Yeastar P-Series to TelecomsXchange

> On a Yeastar P-Series PBX, add a SIP trunk of type Peer Trunk (not a register trunk) to sip01.telecomsxchange.com port 5060 over UDP, and authorise the PBX's public IP on your TelecomsXchange account. Add an outbound route that strips 00 and prepends the tech prefix, so calls leave as 80039#447700900123, and inbound routes for your E.164 numbers.

## Yeastar P-Series to a purchased route

1. **Your Yeastar PBX**: Peer trunk, identified by IP
2. **TelecomsXchange** (via `80039#447700900123`): sip01, UDP 5060
3. **Seller's route**: The route you purchased

This guide connects a Yeastar P-Series PBX (Appliance, Software or Cloud Edition) to TelecomsXchange with a peer trunk: outbound calls to a purchased route, and inbound calls on numbers you bought or routes you sell. For the full list of TelecomsXchange values, see [Connect a SIP platform](https://help.telecomsxchange.com/integrations/connect-sip-platforms/).

!!! warning
    TelecomsXchange does not accept SIP REGISTER. Create a **Peer Trunk**, not a **Register Trunk**. The PBX is recognised by its **source IP** address.

## Before you start

- A [SIP account](https://help.telecomsxchange.com/buyers/create-your-first-account/) with the PBX's public IP, for example `203.0.113.10`, in **IP Address** or **Additional Allowed IPs**. On Cloud Edition, use the static IP address the trunk page shows.
- 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.
- A Yeastar P-Series PBX with a static public IP, or a fixed NAT address with SIP and RTP ports forwarded.
- To receive calls on numbers you bought: a [phone number](https://help.telecomsxchange.com/buyers/virtual-numbers-dids/) whose SIP endpoint points at the PBX, for example `sip:14165551234@203.0.113.10:5060`.

## How do I send calls to TelecomsXchange?

1. Go to **Extension and Trunk → Trunk** and click **Add**.
2. Under **Basic**, enter a **Name** such as `TelecomsXchange`, set **Trunk Status** to **Enabled**, and set **Select ITSP Template** to **General**.
3. Under **Detailed Configuration**, enter:

| Field | Value |
|---|---|
| Trunk Type | **Peer Trunk** (Cloud Edition: **Peer Trunk (DID Based)**) |
| Transport | **UDP** |
| Hostname/IP | `sip01.telecomsxchange.com` |
| Port | `5060` |
| Domain | `sip01.telecomsxchange.com` |

4. On the **Codec** tab, keep only the codecs your route supports (G.729, u-law, a-law, as listed in the Purchased Route Confirmation email). TelecomsXchange doesn't transcode.
5. On the **Advanced** tab, leave **Qualify** off. TelecomsXchange answers SIP OPTIONS only within a call. Click **Save** and **Apply**.
6. Go to **Call Control → Outbound Route** and click **Add**. Enter a **Name**, then add one **Dial Pattern** per way users dial an international number:

| Pattern | Strip | Prepend | Dialled | Sent to TelecomsXchange |
|---|---|---|---|---|
| `00.` | `2` | `80039#` | `00447700900123` | `80039#447700900123` |
| `+.` | `1` | `80039#` | `+447700900123` | `80039#447700900123` |

7. Under **Trunk**, move `TelecomsXchange` to **Selected**. Under **Extension/Extension Group**, select who may use the route. Click **Save** and **Apply**, and move the route above any other route that matches the same numbers: Yeastar checks routes from the top.

Yeastar may send the `#` as `%23` in the Request-URI; TelecomsXchange decodes it.

!!! tip
    To pick routes per destination, add one outbound route per destination pattern (for example `0044.`) with that route's tech prefix in **Prepend**. Or prepend a [routing group](https://help.telecomsxchange.com/buyers/routing-groups-and-route-testing/) prefix such as `444101#` and let TelecomsXchange choose.

**NAT.** If the PBX is behind NAT, set its public IP and forward the SIP port and RTP range in the PBX's network settings (**System → Network → Public IP and Ports** on Appliance and Software Edition), so the SDP carries `203.0.113.10` instead of a private address.

## How do I receive calls from TelecomsXchange?

Calls on numbers you bought, and on routes you sell, 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 the firewall in front of the PBX for UDP 5060 and the RTP range, and in the PBX's own security rules if you restrict SIP by IP.
2. Yeastar matches an incoming INVITE to the peer trunk by its source IP. `sip01.telecomsxchange.com` resolves to `174.136.44.213`, so calls land on the `TelecomsXchange` trunk. If they don't, set the trunk's **Hostname/IP** to `174.136.44.213`.
3. On the trunk's **Advanced** tab, keep the DID taken from the Request-URI (the default), where TelecomsXchange puts the number.
4. Go to **Call Control → Inbound Route** and click **Add**. Set **Name**, **DID Pattern** to the number as it arrives (for example `14165551234`), select the `TelecomsXchange` trunk, and choose a **Default Destination** such as an extension, ring group or IVR. Click **Save** and **Apply**.
5. If your route has an **Outgoing Prefix** or strips digits (**Edit Route → Outgoing Number Translation Parameters**), enter the **DID Pattern** in that format.

Yeastar P-Series is a PBX. As a seller, it can terminate calls to its own extensions and numbers, but it isn't designed to carry wholesale transit traffic on to another carrier.

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

Set the number's **SIP Endpoint (Primary)** in **DID Settings** to the PBX, for example `sip:14165551234@203.0.113.10:5060`. TelecomsXchange sends the INVITE from `174.136.44.213` with `14165551234` in the Request-URI, and the inbound route for that DID sends it on.

## How do I test it?

1. Check the trunk under **Extension and Trunk → Trunk**.
2. Start a packet capture under **Maintenance → Troubleshooting**, then place a call from an extension to `00447700900123`.
3. In the capture, look for the INVITE to `80039#447700900123` (or `80039%23447700900123`) and the reply.
4. On the PBX, check the call in the call detail records. In the TelecomsXchange portal, watch it 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 from TelecomsXchange, then the call fails | The PBX's source IP isn't authorised, so TelecomsXchange asks for credentials a peer trunk can't send. Add the public IP to **IP Address** or **Additional Allowed IPs**. |
| 403 Forbidden | The source IP isn't authorised. Compare the public IP in the capture with the account; check the account isn't blocked or out of balance. |
| 404 Not Found | Missing or wrong tech prefix, or `+`/`00` left in the number. Check **Strip** and **Prepend** on the dial pattern and the Request-URI in the capture. |
| 408 Request Timeout | No reply from sip01. Check outbound UDP 5060 on your firewall and that the PBX resolves `sip01.telecomsxchange.com`. |
| 503 Service Unavailable | The route is blocked or failed on the seller's side. Check **My Interconnections**; try another route or a routing group. |
| One-way or no audio | The PBX advertises a private IP, or RTP isn't forwarded. Set the public IP in the network settings and forward the RTP range. |
| Inbound calls rejected | The call isn't matched to the peer trunk. Set **Hostname/IP** to `174.136.44.213` and check the firewall and security rules. |
| Inbound call arrives but goes nowhere | No inbound route's **DID Pattern** matches the number as it arrives; check the format and any Outgoing Prefix on your route. |

## References

- [Yeastar P-Series: Create a SIP peer trunk](https://help.yeastar.com/en/p-series-appliance-edition/administrator-guide/create-a-sip-peer-trunk.html)
- [Yeastar P-Series: SIP trunk settings](https://help.yeastar.com/en/p-series-software-edition/administrator-guide/sip-trunk-settings.html)
- [Yeastar P-Series: Set up an outbound route](https://help.yeastar.com/en/p-series-software-edition/administrator-guide/set-up-an-outbound-route.html)
- [Yeastar P-Series: Route inbound calls based on DID numbers](https://help.yeastar.com/en/p-series-software-edition/administrator-guide/route-inbound-calls-based-on-did-numbers.html)
- [Yeastar P-Series Cloud Edition: Create a SIP peer trunk](https://help.yeastar.com/en/p-series-cloud-edition/administrator-guide/create-a-sip-peer-trunk.html)

## Frequently asked questions

**Q: Can Yeastar register to TelecomsXchange?**

A: No. TelecomsXchange is peering only and does not accept REGISTER, so use a Peer Trunk, not a Register Trunk. The PBX is recognised by its public IP address.

**Q: Can a Yeastar peer trunk use the VoIP login and password?**

A: Use IP authentication. A Yeastar peer trunk is IP based and carries no credentials, and a register trunk would send REGISTER, which TelecomsXchange rejects. If your public IP changes, add the new one under Additional Allowed IPs.

**Q: Which trunk type do I pick on Yeastar P-Series Cloud Edition?**

A: Peer Trunk (DID Based). Give TelecomsXchange the static IP address shown on the trunk page: put it in the account's IP Address or Additional Allowed IPs.

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

A: In the outbound route's dial pattern, in Prepend: Pattern 00. with Strip 2 and Prepend 80039# turns 00447700900123 into 80039#447700900123.