I had no ideal this thread would get this big! Im going to look more
into the regcontext. I planned on using DUNDi since im going to have
lots of * servers that will be tied over a ATM backbone, so DUNDi can
then do on-net calling much easier and never have to hit the internet,
can just ride our private backbone. If anyone has more examples, please
post, im gonna to start with some mock configs this weekend I hope, and
start testing. There has be to a way to achieve N+1 redudancy, its just
a matter of getting it all to play nicely :) I will be glad to post all
steps needed to this to a wiki, so we can share this setup.<br>
<br>
Thanks!<br>
Ron<br><br><div><span class="gmail_quote">On 3/10/06, <b class="gmail_sendername">Douglas Garstang</b> <<a href="mailto:dgarstang@oneeighty.com">dgarstang@oneeighty.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi
JR. I'm dying to know... where'd you find your DUNDi documentation? Has
something new appeared since I looked at it 2-3 months ago? The
O'Reilly book's DUNDi section was impossible to follow, and the
examples in the Asterisk DUNDi config files are no better. You do a
search online and get almost no results (still wondering when Digium is
going to realease some docs for what they call their protocol). I spent
a few weeks working on it, tearing my hair out, and gave up. So did my
boss.<br><br>Doug.<br><br> -----Original Message-----<br> From: JR Richardson [mailto:<a href="mailto:jr.richardson@cox.net">jr.richardson@cox.net</a>]<br> Sent: Fri 3/10/2006 8:55 PM<br> To:
<a href="mailto:ronmccar@gmail.com">ronmccar@gmail.com</a>; <a href="mailto:asterisk-users@lists.digium.com">asterisk-users@lists.digium.com</a><br> Cc: <a href="mailto:jr.richardson@cox.net">jr.richardson@cox.net</a>
<br> Subject: re: [Asterisk-Users] Clustering<br><br><br><br> ------------------------------<br><br> Message: 6<br> Date: Fri, 10 Mar 2006 12:22:12 -0700<br> From: "Ron McCarthy" <
<a href="mailto:ronmccar@gmail.com">ronmccar@gmail.com</a>><br> Subject: [Asterisk-Users] Clustering<br> To: "Asterisk Users Mailing List - Non-Commercial Discussion"<br> <<a href="mailto:asterisk-users@lists.digium.com">
asterisk-users@lists.digium.com</a>><br> Message-ID:<br> <<a href="mailto:3885f4fe0603101122m6742410ep25276b736072618c@mail.gmail.com">3885f4fe0603101122m6742410ep25276b736072618c@mail.gmail.com
</a>><br> Content-Type: text/plain; charset="iso-8859-1"<br><br> Hello All,<br><br> Ive been doing more and more research on trying to setup a cluster/load<br> balancer for Asterisk. All the Asterisk boxes would be using a config that
<br> is the same between them all (via a DB), but we want one location to point<br> the phones to, and from there that machine/device will send it to a Asterisk<br> server so the call can be processed. I know you cant balance the whole call,
<br> ie: once the call is started the RTP stream has to go to the same server,<br> but a new call could go to a different server if perhaps the 1st server was<br> unreachable.<br><br> Has anyone tried this, or got this to work? Ive been looking at using a
<br> Juniper Session Border Controller, but not sure if thats gonna do the trick,<br> and then we also have SER..<br><br> Any comments would be great!<br><br> Thanks<br> Ron<br> -------------- next part --------------
<br><br><br> Ron,<br><br> I'm
doing something similar with clustering. I haven't gotten
the total design down yet but so far I have 1 * server holding all the
routes to several child/registration * servers where my iax and sip
clients actually register to. I'm using the 1 * server
running dundi to peer with all the registration servers and all the
registration servers only peer with the 1 * server, I call this the
Registration Presence Server or RPS. When a
child/registration server does a lookup request to the RPS, the RPS
does a lookup on all the other registration servers and knows who is
registered where and relays that info back to the original requesting
registration server. Use a dundi ttl=1 in the RPS and ttl=2
in each registration server to avoid routing loops. I'm
still in the testing phase but it's going well, but I'm running into
some cache timeout issues when a client drops off and re-registers to a
different registration server, have to flush dundi to pickup the new
location. There is a cache timeout parameter I have yet to
play with.<br><br> I
don't have the load balancing session border controller function down
yet, but that is on the list of things to do.<br><br> Hope this helps.<br><br> JR<br><br> JR Richardson<br> Engineering for the Masses<br><br> _______________________________________________
<br> --Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br> Asterisk-Users mailing list<br> To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br><br><br></blockquote></div><br>