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.
Doug.
-----Original Message-----
From: JR Richardson [mailto:[EMAIL PROTECTED]
Sent: Fri 3/10/2006 8:55 PM
To: [EMAIL PROTECTED]; [email protected]
Cc: [EMAIL PROTECTED]
Subject: re: [Asterisk-Users] Clustering
------------------------------
Message: 6
Date: Fri, 10 Mar 2006 12:22:12 -0700
From: "Ron McCarthy" <[EMAIL PROTECTED]>
Subject: [Asterisk-Users] Clustering
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hello All,
Ive been doing more and more research on trying to setup a cluster/load
balancer for Asterisk. All the Asterisk boxes would be using a config
that
is the same between them all (via a DB), but we want one location to
point
the phones to, and from there that machine/device will send it to a
Asterisk
server so the call can be processed. I know you cant balance the whole
call,
ie: once the call is started the RTP stream has to go to the same
server,
but a new call could go to a different server if perhaps the 1st server
was
unreachable.
Has anyone tried this, or got this to work? Ive been looking at using a
Juniper Session Border Controller, but not sure if thats gonna do the
trick,
and then we also have SER..
Any comments would be great!
Thanks
Ron
-------------- next part --------------
Ron,
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.
I don’t have the load balancing session border controller function down
yet, but that is on the list of things to do.
Hope this helps.
JR
JR Richardson
Engineering for the Masses
_______________________________________________
--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
_______________________________________________
--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
