I use DUNDi in this way, I have several remote sites and a MPLS network connecting the sites. I have each sites asterisk box looking at 2 DUNDi peers and those 2 central peers can query all sites. I don't have a lot of phones or people moving between sites, but I did not want to have to setup a IAX connection for every site on every server. I like the ability for DUNDi to determine which server to talk to and then configure the dial string for that call. This made my configuration easier to expand as I deployed new sites. I simply added the new peer to my central servers and configured the new site server and I could call between sites.
While DUNDi's original intent was more for least cost routing or zero cost routing, I think it provides an excellent means to scale a network of asterisk systems. On 5/9/07, Ronaldo <[EMAIL PROTECTED]> wrote:
Hi all, I'm planning to deploy many Asterisk servers for remote sites connected through IAX. Behind each server, there will be many sip clients connected. A sip client from one site must be able to make calls for the other sip clients connected to the other remote Asterisk servers. I've heard that DUNDi is a good option in order for each Asterisk server to locate the right (or the best) routes for the sip clients. Is DUNDi really used for that? Thanks in advance ... Ronaldo. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
-- Bruce Reeves Nortex Networks _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
