Help Center
All integration guides

SIP platforms

PBXs

Contact centres and UCaaS

Softswitches and SBCs

SMPP platforms

Connect Sippy Softswitch to TelecomsXchange

Guide 6 of 284-minute readUpdated 23 October 2026

In short: In Sippy, add a vendor TelecomsXchange with a connection to sip01.telecomsxchange.com port 5060 and the CLD translation rule s/^/80039#/, then add it to a routing group. Authorise Sippy's public IP on the TelecomsXchange account or fill the connection's username and password with the VoIP login. To sell, create an account with an authentication rule for remote IP 174.136.44.213.

Sippy to a purchased route
  1. Your SippyVendor connection, identified by IP
  2. then, 80039#447700900123, TelecomsXchangesip01, UDP 5060
  3. Seller's routeThe route you purchased
On this page
  1. Before you start
  2. How do I send calls to TelecomsXchange?
  3. How do I receive calls from TelecomsXchange?
  4. How do I receive calls on numbers I bought?
  5. How do I test it?
  6. What if something goes wrong?
  7. References
  8. Common questions

Sippy Softswitch models carriers as vendors with connections, and customers as accounts with authentication rules. TelecomsXchange is a vendor when you buy routes and a customer account when you sell them. For every TelecomsXchange value in one place, see Connect a SIP platform.

Warning

TelecomsXchange does not accept SIP REGISTER. There is no registration to set up on the vendor side. Sippy is recognised by its source IP or by digest authentication on the INVITE, using the connection's username and password.

Before you start#

  • A SIP account on TelecomsXchange with Sippy's public signalling IP, for example 203.0.113.10, or a VoIP login and password from Edit Account → Add SIP Digest Auth.
  • A purchased route and its tech prefix from My Interconnections, for example 80039#.
  • Admin access to the Sippy web interface.
  • To sell: a route with IP Address:Port set to Sippy, for example 203.0.113.10:5060, and the values in Interconnect Info.

How do I send calls to TelecomsXchange?#

  1. Go to Vendors → My Vendors and add a vendor, for example TelecomsXchange.
  2. Open the vendor's Connections and add a connection, one per purchased route:
    • Connection Name: for example TCXC 80039 UK.
    • Destination: sip01.telecomsxchange.com, port 5060. It currently resolves to 174.136.44.213; enter that IP if your release only accepts an address.
    • Username and Password: leave empty for IP authentication, or enter the account's VoIP Login and VoIP Password for digest authentication.
    • CLD Translation Rule: the tech prefix as a substitution, s/^/80039#/.

Sippy passes numbers to routing in E.164 format, so 447700900123 leaves as 80039#447700900123. If your customers dial with + or 00, normalise the number to E.164 in their account's CLD translation rule, for example s/^00//.

  1. Save the connection.
  2. On TelecomsXchange, open Accounts → Edit Account and download the route's rates in Sippy format from Purchased Routes. Load them into the tariff that the vendor connection uses.
  3. Add the connection to the Routing Group your customers' accounts use, so destinations covered by the tariff route to it.

Tip

One connection per tech prefix lets Sippy's routing choose between your TelecomsXchange routes by price. To let TelecomsXchange choose instead, add a single connection with a routing group prefix such as s/^/444101#/.

How do I receive calls from TelecomsXchange?#

When you sell a route, TelecomsXchange is your customer. Its calls 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 SIP and media.
  2. Create a customer, for example TelecomsXchange, and an account under it with the tariff and routing group you want to apply.
  3. On the account, open Action → Authentication Rules and click Add Authentication Rule.
  4. Enter 174.136.44.213 in Remote IP, then click Save and Close.
  5. If your TelecomsXchange route adds an Outgoing Prefix (Edit Route → Outgoing Number Translation Parameters), match it with Incoming CLD on the rule and remove it with the rule's CLD translation, for example s/^77#//.

Calls that match the rule are billed to that account and routed through its routing group. Calls from other IPs fall through to Sippy's other rules or are challenged for digest authentication.

How do I receive calls on numbers I bought?#

Set the number's SIP Endpoint (Primary) in DID Settings on TelecomsXchange to Sippy, for example sip:14165551234@203.0.113.10:5060. In Sippy, add the number under DIDs and assign it to the account or IVR that should answer it. The call arrives from 174.136.44.213; if your Sippy authenticates incoming DID calls by vendor, add that IP to the DID's authentication as well.

How do I test it?#

  1. Place a call from a test account to a number covered by the route.
  2. In Sippy, open the call's CDR to see the connection used, the translated CLD (80039#447700900123) and the result code.
  3. If you have shell access to the Sippy host, sngrep port 5060 shows the INVITE and the reply from sip01.
  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, then the call fails The connection's Username and Password are empty or wrong while your IP isn't authorised. Enter the VoIP login and password from Edit Account.
403 Forbidden Sippy's public IP isn't authorised and no valid credentials were sent. Check the IP against IP Address and Additional Allowed IPs; check the account isn't blocked or out of balance.
404 Not Found Missing or wrong tech prefix. Check the connection's CLD Translation Rule and that the number reaches it in E.164 without + or 00.
408 Request Timeout No reply from sip01. Check the connection's destination and port, and outbound UDP 5060.
503 Service Unavailable The route is blocked or failed on the seller's side. Check My Interconnections, and give the routing group a second connection to fail over to.
One-way or no audio Sippy's media relay or NAT settings advertise a private IP. Check the media IP in the SDP and open the RTP range.
No inbound calls, or calls rejected with 401 The authentication rule doesn't match. Check Remote IP is 174.136.44.213, any Incoming CLD pattern, and the firewall.
Inbound calls rejected for no route or no rate The account's tariff or routing group doesn't cover the E.164 destination.

References#

Common questions

Can Sippy register to TelecomsXchange?

No. TelecomsXchange is peering only and does not accept REGISTER. Sippy sends calls through a vendor connection, recognised by its source IP or by digest credentials on the connection.

Where do I put the tech prefix?

In the connection's CLD translation rule, as a sed-style substitution: s/^/80039#/ turns 447700900123 into 80039#447700900123. Use one connection per purchased route.

Can I import TelecomsXchange rates into Sippy?

Yes. On TelecomsXchange, Edit Account lists the account's purchased routes with a rates download in Sippy format. Load the file into the vendor tariff used by the connection.

How does TelecomsXchange appear when I sell to it?

As one customer account, authenticated by remote IP 174.136.44.213. Calls arrive in E.164 format such as 14165551234.

Can Sippy register to TelecomsXchange?
No. TelecomsXchange is peering only and does not accept REGISTER. Sippy sends calls through a vendor connection, recognised by its source IP or by digest credentials on the connection.
Where do I put the tech prefix?
In the connection's CLD translation rule, as a sed-style substitution: s/^/80039#/ turns 447700900123 into 80039#447700900123. Use one connection per purchased route.
Can I import TelecomsXchange rates into Sippy?
Yes. On TelecomsXchange, Edit Account lists the account's purchased routes with a rates download in Sippy format. Load the file into the vendor tariff used by the connection.
How does TelecomsXchange appear when I sell to it?
As one customer account, authenticated by remote IP 174.136.44.213. Calls arrive in E.164 format such as 14165551234.

Related guides

This guide matches platform build 83b4ebc9. Markdown version.