Does anyone have any information on how to use DUNDi precaching? 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... http://lists.digium.com/pipermail/dundi/2004-October/000189.html However, it seems that no documentation exists for this in the known universe. Doug.
Doug, This may help you out a little. It's a whitepaper that JR wrote on how to get a DUNDi cluster working with two redundant primary servers that handle all the DUNDi legwork. Read through it, you might get some information you can use out of it. http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20with%20a%20Cluster%20of%20Asterisk%20Servers.pdf On Thu, 2006-11-09 at 08:36 -0700, Douglas Garstang wrote:> Does anyone have any information on how to use DUNDi precaching? > > 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... > > http://lists.digium.com/pipermail/dundi/2004-October/000189.html > > However, it seems that no documentation exists for this in the known universe. > > Doug. > _______________________________________________ > --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-- Aaron Daniel Computer Systems Technician Sam Houston State University amdtech@shsu.edu (936) 294-4198
Aaron. 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. 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. Doug.> -----Original Message----- > From: Aaron Daniel [mailto:amdtech@shsu.edu] > Sent: Thursday, November 09, 2006 9:55 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] DUNDi precache > > > Doug, > > This may help you out a little. It's a whitepaper that JR > wrote on how > to get a DUNDi cluster working with two redundant primary servers that > handle all the DUNDi legwork. Read through it, you might get some > information you can use out of it. > > http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20with%20a%20Cluster%20of%20Asterisk%20Servers.pdf On Thu, 2006-11-09 at 08:36 -0700, Douglas Garstang wrote:> Does anyone have any information on how to use DUNDi precaching? > > 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... > > http://lists.digium.com/pipermail/dundi/2004-October/000189.html > > However, it seems that no documentation exists for this in the known universe. > > Doug. > _______________________________________________ > --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-- Aaron Daniel Computer Systems Technician Sam Houston State University amdtech@shsu.edu (936) 294-4198 _______________________________________________ --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
If you have a large number of servers, a mesh relationship may not scale well, and maintaining relationships between all the servers is difficult for starters. It also cuts down on the physical distance to perform queries if you have a centralised DUNDi server, rather than having to query the peers on remote sites.> -----Original Message----- > From: Aaron Daniel [mailto:amdtech@shsu.edu] > Sent: Thursday, November 09, 2006 11:04 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] DUNDi precache > > > Why would you want to do that? Defeats the purpose of *having* the > DUNDi protocol. Why not just program the extensions in at regular > intervals or something? > > On Thu, 2006-11-09 at 10:16 -0700, Douglas Garstang wrote: > > Aaron. > > > > 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. > > > > 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. > > > > Doug. > > > > > -----Original Message----- > > > From: Aaron Daniel [mailto:amdtech@shsu.edu] > > > Sent: Thursday, November 09, 2006 9:55 AM > > > To: Asterisk Users Mailing List - Non-Commercial Discussion > > > Subject: Re: [asterisk-users] DUNDi precache > > > > > > > > > Doug, > > > > > > This may help you out a little. It's a whitepaper that JR > > > wrote on how > > > to get a DUNDi cluster working with two redundant primary > servers that > > > handle all the DUNDi legwork. Read through it, you might get some > > > information you can use out of it. > > > > > > http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w > > ith%20a%20Cluster%20of%20Asterisk%20Servers.pdf > > > > On Thu, 2006-11-09 at 08:36 -0700, Douglas Garstang wrote: > > > Does anyone have any information on how to use DUNDi precaching? > > > > > > 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... > > > > > > http://lists.digium.com/pipermail/dundi/2004-October/000189.html > > > > > > However, it seems that no documentation exists for this > in the known universe. > > > > > > Doug. > > > _______________________________________________ > > > --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 > > -- > Aaron Daniel > Computer Systems Technician > Sam Houston State University > amdtech@shsu.edu > (936) 294-4198 > > _______________________________________________ > --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, 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. Doug. -----Original Message----- From: Bruce Reeves [mailto:asterisk@nortex-networks.com] Sent: Thursday, November 09, 2006 10:56 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] DUNDi precache Doug, 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. On 11/9/06, Douglas Garstang < dgarstang@oneeighty.com> wrote: Aaron. 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. 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. Doug.> -----Original Message----- > From: Aaron Daniel [mailto: amdtech@shsu.edu] > Sent: Thursday, November 09, 2006 9:55 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] DUNDi precache > > > Doug, > > This may help you out a little. It's a whitepaper that JR > wrote on how > to get a DUNDi cluster working with two redundant primary servers that > handle all the DUNDi legwork. Read through it, you might get some > information you can use out of it. > > http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w <http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w>ith%20a%20Cluster%20of%20Asterisk%20Servers.pdf On Thu, 2006-11-09 at 08:36 -0700, Douglas Garstang wrote:> Does anyone have any information on how to use DUNDi precaching? > > 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... > > http://lists.digium.com/pipermail/dundi/2004-October/000189.html > > However, it seems that no documentation exists for this in the known universe. > > Doug. > _______________________________________________ > --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-- Aaron Daniel Computer Systems Technician Sam Houston State University amdtech@shsu.edu (936) 294-4198 _______________________________________________ --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 <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 -- Bruce Nortex Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20061109/84126ce4/attachment.htm
I also just realised a distinct advantage of the precache model. Lets say you have a central DUNDi cache server. He has in his cache the knowledge that appearance 2944093 is registered to pbx1 for the next hour. If pbx1 where to crash, then for the next hour, calls to 2944093 would fail. However, in the precache model, when the phone registers to an Asterisk box, the Asterisk box immediately precaches the information to the central DUNDi server, who maintains this information until it's updated. If pbx1 where to crash, and the phone failed over to pbx2, pbx2 would then send updated registration information to the DUNDi precache server, and thus calls would not fail for an hour. Douglas.> -----Original Message----- > From: Aaron Daniel [mailto:amdtech@shsu.edu] > Sent: Thursday, November 09, 2006 11:04 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [asterisk-users] DUNDi precache > > > Why would you want to do that? Defeats the purpose of *having* the > DUNDi protocol. Why not just program the extensions in at regular > intervals or something? > > On Thu, 2006-11-09 at 10:16 -0700, Douglas Garstang wrote: > > Aaron. > > > > 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. > > > > 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. > > > > Doug. > > > > > -----Original Message----- > > > From: Aaron Daniel [mailto:amdtech@shsu.edu] > > > Sent: Thursday, November 09, 2006 9:55 AM > > > To: Asterisk Users Mailing List - Non-Commercial Discussion > > > Subject: Re: [asterisk-users] DUNDi precache > > > > > > > > > Doug, > > > > > > This may help you out a little. It's a whitepaper that JR > > > wrote on how > > > to get a DUNDi cluster working with two redundant primary > servers that > > > handle all the DUNDi legwork. Read through it, you might get some > > > information you can use out of it. > > > > > > http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w > > ith%20a%20Cluster%20of%20Asterisk%20Servers.pdf > > > > On Thu, 2006-11-09 at 08:36 -0700, Douglas Garstang wrote: > > > Does anyone have any information on how to use DUNDi precaching? > > > > > > 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... > > > > > > http://lists.digium.com/pipermail/dundi/2004-October/000189.html > > > > > > However, it seems that no documentation exists for this > in the known universe. > > > > > > Doug. > > > _______________________________________________ > > > --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 > > -- > Aaron Daniel > Computer Systems Technician > Sam Houston State University > amdtech@shsu.edu > (936) 294-4198 > > _______________________________________________ > --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 >