Difference between revisions of "Trunks"
| Line 21: | Line 21: | ||
In order to do this, you should mark some device as Trunk with ANI.<br> | In order to do this, you should mark some device as Trunk with ANI.<br> | ||
Now when some other device connected to that Trunk dials through MOR, MOR check this device's CallerID and if it's present for some device in the MOR – then MOR recognizes the device as valid device on the MOR and assigns call to him instead of Trunk. | Now when some other device connected to that Trunk dials through MOR, MOR check this device's CallerID and if it's present for some device in the MOR – then MOR recognizes the device as valid device on the MOR and assigns call to him instead of Trunk. | ||
<br><br> | |||
---- | |||
See also: | |||
* [[PBX connection to MOR]] | |||
** [[MOR and Trixbox]] | |||
Revision as of 07:38, 20 August 2009
Under Trunk we have in mind other server/PBX which can be connected to the MOR system.
When we are calling to such device, we send full number which was dialed before.
Example: when dialing simple device, we would use:
Dial(SIP/some_device)
and if this device is Trunk we use:
Dial(SIP/some_device/${EXTEN}).
This lets Trunk to decide to which device (connected to the Trunk) to route the call.
If you want to make device Trunk, just mark is at Trunk in device details: 
No/Yes/Yes with ANI
Trunk with ANI
It is sometimes necessary not to bill whole trunk as one client but to be able to bill separate clients connected to the server/pbx (trunk) separately.
In order to do this, you should mark some device as Trunk with ANI.
Now when some other device connected to that Trunk dials through MOR, MOR check this device's CallerID and if it's present for some device in the MOR – then MOR recognizes the device as valid device on the MOR and assigns call to him instead of Trunk.
See also:
