MOR and Trixbox

MOR and Trixbox (FreePBX) can't work nicely on the same server, because they use same Asterisk .conf files, which makes a lot of mess.

In order to integrate Trixbox with MOR you need to connect in the following way:

Connection diagram

As an example, we will configure one phone dialing. The phone is connected to Trixbox, which is connected to MOR:

Here, for simplicity, all the devices are in the same LAN:

• MOR server has IP: 10.10.1.10.
• Trixbox: 10.10.1.20.
• Phone: 10.10.1.30.

MOR and Trixbox are connected with the following settings:

• username: mor_trixbox.
• password: mor_trixbox_psw.

The phone to Trixbox is connected with:

• username: 201.
• password: 201psw.

Dialing from the phone to MOR

• Here the device makes a call to example destination 9999999999.
• When the call reaches Trixbox, the correct CallerID number for this phone is applied. In our example it is 1111111111. Then the call is forwarded to MOR.
• When MOR gets the call, it sees that the call was sent by Trixbox.
• MOR sees that Trixbox is Trunk with ANI. This means that MOR needs to check the CallerID of the call to find the real caller.
• MOR checks for the CallerID number (1111111111) and sees that this CallerID is assigned to a phone device.
• MOR retrieves all info (LCR/Tariff/Rates/Providers/etc) that is necessary to send the call further.
• When the call is finished, it is logged in MOR, not for Trixbox, but for the phone's user/device. That is what we wanted from our configuration.

Trixbox configuration for phone

Let's connect a phone to Trixbox. In FreePBX, create an extension for phone 201:

The most important details are:

Here we set the CallerID number that should be applied to the call from this device. The password and dial string are also here.

Trixbox configuration for MOR

In Trixbox we need to define MOR as a Trunk:

Define a route in Trixbox to use this Trunk (this is just an example):

Trixbox Trunk Troubleshooting

When passing multiple CallerIDs from multiple extensions in TrixBox through a single ANI-enabled trunk to MOR, be sure to define the outbound TrixBox PEER CallerID as empty, using callerid="" <>.

If you don't include this, your MOR trunk will publish whichever CallerID was last passed to it. This will not allow you to correctly track different users' CallerIDs in MOR to provide them with separate call cost tracking.

Also, be sure NOT to define the inbound USER CallerID on the same TrixBox trunk as the same empty entry. If you do, the CallerID will be stripped from all incoming calls.

MOR configuration for Trixbox

We need to create a connection between MOR and Trixbox. In this example, we will configure the MOR-Trixbox connection by using SIP.

We need to create a user for Trixbox: pbx_user. Put any details for it - it does not matter which:

Now we need to configure the device for Trixbox:

The main settings are:

• Mark this device as Trunk with ANI support.
• Username (by example): mor_trixbox.
• Password: mor_trixbox_psw.
• Host: 10.10.1.20.
• Make sure Dynamic? is unchecked and the port is 5060 (for SIP).

MOR configuration for phone

To correctly bill phone calls, you need to create a separate user and device for it on MOR.

First, create a user for the phone (phone_user):

Make sure you configure this user correctly by entering the password/LCR/Tariff and other necessary details. This user will be used for real dialing out.

Next, create a virtual device for the phone:

The settings for this device are not at all important, but you should:

1. Make sure you have marked this device as Trunk. This is important for receiving calls.
2. Make sure you have a good password for security.
3. Make sure that this device's host = dynamic (for security reasons, you cannot enter the Trixbox IP here, because 201 is not Trixbox!)

CallerID for phone in MOR

In order for MOR to recognize a device/phone, we need to assign a CallerID to our phone's device:

NOTE: currently it is not possible to enter a CallerID that is the same as the name of the device. That way, the call will fail. This happens because of the way Asterisk handles authentication.

Dialing to phone using DID

• Here a call is coming to DID 2222222222.
• When it reaches MOR, MOR knows that 2222222222 should be forwarded to device 201.
• Device 201 forwards the call to Trixbox device Dial (SIP/22222222222@mor_trixbox).
• Trixbox receives call with destination 2222222222.
• Trixbox know that this call should be forwarded to phone SIP/201.
• Phone rings.
• After the call, in the MOR log the call is in device 201's logs (CDR) - as it should be.

MOR configuration

You need to create DID 2222222222 in MOR and assign the phone's user/device to this DID:

In this device's Call Flow, you need to forward the call to Trixbox:

Trixbox configuration

Now when the call arrives in Trixbox, it should know how to route the call to phone 201.

We can configure this in two ways:

• Using Direct DID.
• Using the Inbound Route.

Direct DID configuration

Inbound Route configuration

Final notes

In the example, we used DID 2222222222 and CallerID 1111111111. In real installations, these values are the same in most cases. This means that if the user is dialing out and his CallerID is (for example) 3333333333, he can receive calls by DID 3333333333. You can configure this in the same way using this manual. Different values for DID and CallerID are chosen here to make the example easier to understand.

Configuring more phones

In order to configure more phones:

1. Connect a phone to Trixbox.
2. Configure user/device in MOR for the phone.
3. Make sure the phone's CallerID in Trixbox is the same as CallerID (CID) for the phone's device in MOR.
4. Create a DID for the phone on MOR, assign it to the phone's device, and forward calls from the device to Trixbox in MOR.
5. Make sure Trixbox knows how to route calls from DID to the phone.

Limitations

Using this configuration to connect Trixbox (actually, FreePBX) to MOR has some limitations:

1. The MOR device's CallerID can't be the same as the device's name.
2. Phones connected to Trixbox can't have similar CallerIDs. (Actually they can, but MOR will not be able to distinguish which device is making the call, so these devices with identical CallerIDs will be billed together using one account (user/device) in MOR).

Errors

chan_sip.c:8373 check_auth: username mismatch, have <201>, digest has <mor_trixbox>

This error may occur when configuring the connection between MOR and Trixbox.

--note--

This is not a connection problem. This happens when you have an incorrect (or no) outbound CallerID set within Trixbox. Thus "201" (the display name) is being passed through to MOR.

--VCCS