Difference between revisions of "DUNDi configuration"
(→Links) |
(→Links) |
||
| Line 14: | Line 14: | ||
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+dundi.conf Asterisk config: dundi.conf] | * [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+dundi.conf Asterisk config: dundi.conf] | ||
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+func+dundilookup Asterisk function: dundilookup] | * [http://www.voip-info.org/wiki/index.php?page=Asterisk+func+dundilookup Asterisk function: dundilookup] | ||
| + | * [http://www.voip-info.org/wiki/view/DUNDi Introduction to DUNDi] | ||
Revision as of 23:28, 2 February 2007
Alternatives to DUNDi
You can also try the TDMoE zaptel driver. This is similar to the ztdummy driver in some ways but it will link 2 or more PBX's on the same physical network with zap channels. So on a 100Mb ethernet interface you could potentially get the equivalent of about 50 PRI lines. Overkill maybe, but you can set the number of channels you want. This should be good for interconnecting a voicemail only Trixbox with another tribox handling the calls. In larger installs this would be useful as it offloads the voicemail agi scripts and transcoding to another box. TDMoE is also much simpler to configure in comparison to DUNDI.
you get many of the same features as you do with normal zap channels. It is also very efficient on bandwidth and cpu.
DUNDI is a good solution for remote PBX's. (Source)
Links
- DUNDi tutorial for Asterisk@home (Previous version of Trixbox)
- Using DUNDi with Trixbox Very short How-to to connect 3 Trixboxes together. They don't use DUNDi discovery, but just enter the neighbours' MAC-adresses. (source)
- Asterisk config: dundi.conf
- Asterisk function: dundilookup
- Introduction to DUNDi
