---
title: Connect MOR (Kolmisoft) to TelecomsXchange
url: https://help.telecomsxchange.com/integrations/mor-kolmisoft/
audience: Integrations
summary: In MOR, add a SIP provider with Hostname sip01.telecomsxchange.com, Server
  IP 174.136.44.213, Port 5060, Authenticate by IP on and Register off, then add a
  provider rule that adds the tech prefix (80039#) and put the provider in an LCR.
  To sell, accept 174.136.44.213 as an IP-authenticated device for a user with your
  tariff, or assign the TelecomsXchange provider to that user if you also buy.
updated: '2026-10-23'
verified_commit: 83b4ebc96d0081a25213776d5a8871bd04941125
---

# Connect MOR (Kolmisoft) to TelecomsXchange

> In MOR, add a SIP provider with Hostname sip01.telecomsxchange.com, Server IP 174.136.44.213, Port 5060, Authenticate by IP on and Register off, then add a provider rule that adds the tech prefix (80039#) and put the provider in an LCR. To sell, accept 174.136.44.213 as an IP-authenticated device for a user with your tariff, or assign the TelecomsXchange provider to that user if you also buy.

## MOR to a purchased route

1. **Your MOR**: SIP provider, Register off
2. **TelecomsXchange** (via `80039#447700900123`): sip01, UDP 5060
3. **Seller's route**: The route you purchased

MOR (Kolmisoft's softswitch and billing platform) sends calls through **providers**, chosen by an **LCR**, and accepts calls from **devices** that belong to **users**. TelecomsXchange is a provider when you buy routes and a user's device (or a provider assigned to a user) when you sell them. 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. Leave **Register** unticked on the provider. MOR is recognised by its **source IP** or by **digest authentication on the INVITE**, using the provider's **Login** and **Password**.

## Before you start

- A [SIP account](https://help.telecomsxchange.com/buyers/create-your-first-account/) on TelecomsXchange with MOR's public signalling IP (each Asterisk server that sends calls), 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**.
- An admin login to MOR, and a provider tariff (MOR won't create a provider without one).
- To sell: a [route](https://help.telecomsxchange.com/sellers/add-your-first-route/) with **IP Address:Port** set to MOR, 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?

1. Create a provider tariff for the route. On TelecomsXchange, download the route's rates from **Accounts → Edit Account → Purchased Routes** in **Default** format and import them into it.
2. Go to **SETTINGS → Billing → Providers** and click **New Provider**. Enter a **Name** such as `TCXC 80039 UK`, choose **Technology: SIP**, the tariff, and the Asterisk server, then click **Create**.
3. Edit the provider and set:
    - **Authentication**: tick **Authenticate by IP**; leave **Register** unticked. For digest authentication, untick **Authenticate by IP** and enter `VOIP_LOGIN` in **Login** and `VOIP_PASSWORD` in **Password** (MOR can't combine IP and login authentication on one provider).
    - **Network related**: **Hostname** `sip01.telecomsxchange.com`, **Server IP** `174.136.44.213`, **Port** `5060`, **Qualify** off. TelecomsXchange answers OPTIONS only within a call.
    - **Codecs**: the codecs the route supports, for example G.729 and G.711. TelecomsXchange doesn't transcode.
    - **Advanced → Transport**: UDP.
4. Click the **Provider Rules** icon next to the provider and add a **Destination Rule** that adds the tech prefix:

| Name | Cut | Add | Min len | Max len |
|---|---|---|---|---|
| TCXC prefix | *(empty)* | `80039#` | 1 | 100 |

MOR works in E.164, so `447700900123` leaves as `80039#447700900123`. Check that your users' **Localization** turns what they dial into E.164 (for example, cut `00`) before this rule runs.

5. Go to **SETTINGS → Billing → LCR**, open your LCR (or create one **By Price** or **By priority**), click the number in the **Providers** column and add the TelecomsXchange provider.
6. Make sure the users who should reach TelecomsXchange use that LCR, and that their tariff has rates for the destinations.

!!! tip
    One provider per tech prefix lets MOR's LCR choose between your TelecomsXchange routes by price. To let TelecomsXchange choose instead, add a single provider whose rule adds a [routing group](https://help.telecomsxchange.com/buyers/routing-groups-and-route-testing/) prefix such as `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 (UDP) and the Asterisk RTP range.
2. Create a user for TelecomsXchange in **SETTINGS → Users**, with the tariff you sell at and the LCR that routes to your own carriers. Make it postpaid with a credit limit, or keep its balance funded.
3. Choose how MOR recognises the calls:
    - **If you only sell to TelecomsXchange**: add a SIP device to that user (**SETTINGS → Users → Devices**). Under **IP Authentication**, set **IP Address** to `174.136.44.213`. Keep **Insecure** at **port, invite** (the default for IP-authenticated devices), because TelecomsXchange sends from several source ports.
    - **If you also buy from TelecomsXchange**: don't create a second entry for the same IP. Assign the TelecomsXchange provider from the previous section to the user, as Kolmisoft recommends for a carrier that sends and receives from one IP.
4. If your TelecomsXchange route adds an **Outgoing Prefix** (**Edit Route → Outgoing Number Translation Parameters**), cut it with a **Localization** rule on the device's or provider's Location, for example **Cut** `77#`.

!!! warning
    If you also buy from TelecomsXchange, make sure the LCR used for calls from TelecomsXchange doesn't include the TelecomsXchange provider, or a misrouted call can loop.

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

Set the number's **SIP Endpoint (Primary)** in **DID Settings** on TelecomsXchange to MOR, for example `sip:14165551234@203.0.113.10:5060`. In MOR, add the number under DIDs in E.164 format with TelecomsXchange as its provider, and assign it to the device that should answer. The call arrives from `174.136.44.213`; MOR localizes the number with the provider's Location to find the DID, and TelecomsXchange already sends it in E.164.

## How do I test it?

1. Open **SETTINGS → Billing → Functions → Call Tracing**, pick a test user and device, and trace a call to `447700900123`. It flags missing rates, LCR entries and devices, and shows the number after Provider Rules.
2. Place the call. On the Asterisk server, `asterisk -rx "sip set debug on"` (or `pjsip set logger on`, depending on your MOR version) or `sngrep port 5060` shows the INVITE to `80039#447700900123` and the reply.
3. In MOR, check the call in the calls statistics with its hangup cause.
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 | MOR's IP isn't authorised and no login was sent. Add the IP, or untick **Authenticate by IP** and enter the VoIP login and password. |
| 403 Forbidden | MOR's public IP isn't authorised and no valid credentials were sent, or the account is blocked or out of balance. With several Asterisk servers, authorise each one. |
| 404 Not Found | Missing or wrong tech prefix, or the number wasn't E.164. Check the **Provider Rules** and the user's **Localization** in Call Tracing. |
| 408 Request Timeout | No reply from sip01. Check **Server IP**, **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 LCR a second provider. |
| Provider marked unreachable | **Qualify** is on. Turn it off. |
| One-way or no audio | MOR advertises a private IP, or RTP is blocked. Check the Asterisk external IP settings and open the RTP range. |
| Inbound calls rejected | No device or assigned provider matches `174.136.44.213`, or two entries share it. Keep one, and check the firewall. |
| Inbound call rejected for no rate | The TelecomsXchange user's tariff or LCR doesn't cover the E.164 destination. Trace it with Call Tracing. |

## References

- [Kolmisoft: Providers](https://wiki.kolmisoft.com/index.php/Providers)
- [Kolmisoft: MOR Provider Rules](https://wiki.kolmisoft.com/index.php/MOR_Provider_Rules)
- [Kolmisoft: MOR Number Manipulation](https://wiki.kolmisoft.com/index.php/MOR_Number_Manipulation)
- [Kolmisoft: LCR](https://wiki.kolmisoft.com/index.php/LCR)
- [Kolmisoft: Device settings](https://wiki.kolmisoft.com/index.php/Device_settings)
- [Kolmisoft: Authentication](https://wiki.kolmisoft.com/index.php/Authentication)
- [Kolmisoft: Configure Provider which can make calls](https://wiki.kolmisoft.com/index.php/Configure_Provider_which_can_make_calls)
- [Kolmisoft: DID handling by Localization](https://wiki.kolmisoft.com/index.php/DID_handling_by_Localization)
- [Kolmisoft: Call Tracing](https://wiki.kolmisoft.com/index.php/Call_Tracing)

## Frequently asked questions

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

A: No. TelecomsXchange is peering only and does not accept REGISTER. Leave Register unticked on the provider and use Authenticate by IP, or Login and Password for digest authentication on the INVITE.

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

A: In a Provider Rule (destination rule) that adds the prefix, for example Add 80039#. MOR keeps numbers in E.164 internally and Provider Rules convert them to the provider's format, so 447700900123 leaves as 80039#447700900123.

**Q: I buy and sell with TelecomsXchange. Do I need two entries for 174.136.44.213?**

A: Kolmisoft recommends one provider for both directions when a carrier uses the same IP. Assign the TelecomsXchange provider to a user, and calls it sends are billed to that user.

**Q: How do I check why a call fails before it reaches TelecomsXchange?**

A: Use Call Tracing in SETTINGS, Billing, Functions. It shows missing tariffs, rates, LCR entries and whether Provider Rules turned the number into 80039#447700900123.