Difference between revisions of "MOR and Trixbox"
Line 116: | Line 116: | ||
[[Image:trixbox7.png]] | [[Image:trixbox7.png]] | ||
All settings for this device are not important at all | All settings for this device are not important at all except: | ||
# Make sure you marked this device as '''Trunk''' - important for receiving calls | |||
# Make sure you have good password for security | |||
<br> | <br> | ||
==CallerID for phone in MOR== | ==CallerID for phone in MOR== | ||
Revision as of 08:00, 19 December 2007
As MOR and Trixbox (FreePBX) both use Asterisk Realtime and custom extensions - they can't work nicely on the same server.
In order to integrate Trixbox with MOR you need to connect in following way:
Connection diagram
As an example we will configure one phone dialing. Phone is connected to Trixbox which is connected to MOR:
Here for simplicity all devices are in 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 following settings:
- username: mor_trixbox
- password: mor_trixbox_psw
And phone to Trixbox is connected with:
- username: 201
- password: 201psw
Dialing diagram from phone to MOR
- Here device makes call to example destination 9999999999.
- When call reaches Trixbox correct CallerID number for this phone is applied. In our example it is 1111111111. Then call is forwarded to MOR.
- When MOR gets a call it sees that call is sent by Trixbox.
- Also it sees that Trixbox is Trunk with ANI - that means MOR needs to chech CallerID of the call to find real caller.
- MOR checks for CallerID number (1111111111) and sees that this CallerID is assigned to phone device.
- The MOR retrieves all info necessary to send call further (LCR/Tariff/Rates/Providers/etc).
- When call is finished - it is logged in MOR not for Trixbox, but for phone's user/device. That is what we wanted from our configuration.
Trixbox configuration for phone
Lets connect phone to Trixbox. In FreePBX create Extension for 201 phone:
Most important details:
Here we set CallerID number which should be applied to the call from this device. Password and dial string also here.
Trixbox configuration for MOR
In Trixbox we need to define MOR as a Trunk:
Define some route in Trixbox to use this Trunk (here is just an example):
MOR configuration for Trixbox
We need to create connection between MOR and Trixbox. In this example we will configure MOR-Trixbox connection using SIP.
We need to create user for Trixbox - pbx_user, put any details for it - it does not matter:
Now we need to configure device for Trixbox:
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 port is 5060 (for SIP)
MOR configuration for phone
To correctly bill phone calls you need to create separate user and device for it on MOR.
First let's create user for phone (phone_user):
Make sure you configure this user correctly - e.g. enter password/LCR/Tariff and other necessary details - this user will be used for real dialing out.
Then we need to create virtual device for our phone:
All settings for this device are not important at all except:
- Make sure you marked this device as Trunk - important for receiving calls
- Make sure you have good password for security
CallerID for phone in MOR
In order MOR to recognize device/phone we need to assign CalledID to our phone's device:
NOTE: currently it is not possible to enter same CallerID as device's name. That way call will fail. It is due to the way Asterisk handles authentication.
Configuring more phones
In order to configure more phones:
- Connect phone to Trixbox
- Configure user/device in MOR for phone
- Make sure CallerID for phone in Trixbox is the same as CallerID (CID) for phone's device in MOR
Dialing to phone using DID
- Here call is coming to DID: 2222222222
- When it reaches MOR - MOR knows that 2222222222 should be forwarded to device 201