<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.5700.6" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=843235418-09112006><FONT face=Arial color=#0000ff
size=2>Bruce,</FONT></SPAN></DIV>
<DIV><SPAN class=843235418-09112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=843235418-09112006><FONT face=Arial color=#0000ff size=2>After
thinking about it a bit, I can see how setting the cache time to some value
higher than 0 could be effective. However, I'm trying to figure out what
benefits a 'central' DUNDi cache server provides over a completely distributed
architecture. If you have three asterisk boxes, and each peers with the other
two, AND the cache time is set, to say, an hour, when an asterisk server locates
a phone, it will store that it in it's own cache anyway. About the only
advantage I can see is is in managability. You no longer need to maintain peer
relationships between every asterisk box, only between every Asterisk box and
the central DUNDi cache server.</FONT></SPAN></DIV>
<DIV><SPAN class=843235418-09112006><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=843235418-09112006><FONT face=Arial color=#0000ff
size=2>Doug.</FONT></SPAN></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Bruce Reeves
[mailto:asterisk@nortex-networks.com]<BR><B>Sent:</B> Thursday, November 09,
2006 10:56 AM<BR><B>To:</B> Asterisk Users Mailing List - Non-Commercial
Discussion<BR><B>Subject:</B> Re: [asterisk-users] DUNDi
precache<BR><BR></FONT></DIV>Doug,<BR><BR>JR's example does cache but only for
a very short time, like 5 seconds, so that if the device registers else where
then the lookup is able to find it. You can change the cache time to the
default hour or what ever you want. As far as precahe, I know it is a dundi
cli command and you could probably script connecting to the cli and
precacheing an extension, but in my case the lookups are under 70 ms so I
don't notice a hughe hit on performance when a lookup is done. I know you are
trying to use this on a much larger scale then I do. <BR><BR>
<DIV><SPAN class=gmail_quote>On 11/9/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="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Aaron.<BR><BR>Thanks.
JR sent me that article before it was published. He's not precaching
registrations. He's doing something different. In his configuration, when a
registration server gets a request for the location of a phone, it queries
the DUNDi Lookup server, which in turn queries the other registration
servers on it's behalf. It doesn't actually cache the registrations itself.
<BR><BR>According to what Mark Spencer wrote, it should be possible for this
DUNDi Lookup server to hold, or store (ie cache) -all- phone registration
info so that it doesn't have to query the other registration
servers.<BR><BR>Doug.<BR><BR>> -----Original Message-----<BR>> From:
Aaron Daniel [mailto:<A
href="mailto:amdtech@shsu.edu">amdtech@shsu.edu</A>]<BR>> Sent: Thursday,
November 09, 2006 9:55 AM<BR>> To: Asterisk Users Mailing List -
Non-Commercial Discussion <BR>> Subject: Re: [asterisk-users] DUNDi
precache<BR>><BR>><BR>> Doug,<BR>><BR>> This may help you out
a little. It's a whitepaper that JR<BR>> wrote on how<BR>>
to get a DUNDi cluster working with two redundant primary servers that
<BR>> handle all the DUNDi legwork. Read through it, you might
get some<BR>> information you can use out of it.<BR>><BR>> <A
href="http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w">http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w
</A><BR>ith%20a%20Cluster%20of%20Asterisk%20Servers.pdf<BR><BR>On Thu,
2006-11-09 at 08:36 -0700, Douglas Garstang wrote:<BR>> Does anyone have
any information on how to use DUNDi precaching?<BR>><BR>> Mark Spencer
made a post 2 years ago where he hinted it may be possible to configure
DUNDi such that you could centralise your DUNDi registration info by using
precaching, instead of having each DUNDi peer meshed with every other one...
<BR>><BR>> <A
href="http://lists.digium.com/pipermail/dundi/2004-October/000189.html">http://lists.digium.com/pipermail/dundi/2004-October/000189.html</A><BR>><BR>>
However, it seems that no documentation exists for this in the known
universe. <BR>><BR>> Doug.<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>Aaron
Daniel<BR>Computer Systems Technician <BR>Sam Houston State University<BR><A
href="mailto:amdtech@shsu.edu">amdtech@shsu.edu</A><BR>(936)
294-4198<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>--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></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>Bruce<BR>Nortex Networks </BLOCKQUOTE></BODY></HTML>