James,

Yes. I have a copy of it. The author, JR Richardson, sent me a copy in 
confidence before it was released publically. If you read the doc, you will see 
that his implementation does not used a tiered approach. When a registration 
server wants to find the location of a phone, it queries the DUNDi server, who 
in turn then queries every other registration server until it finds the phone. 
This is no more efficient than the registration server querying every other 
registration server itself. I don't see the value of this approach.

Mark Spencer made a post to this list back in October 2004, where he implied 
that you could use inbound/outbound models with precache in order to get a 
central (well, you'd want two for redundancy) DUNDi server that cached 
locations of phones, so that when a registration server queried it, it didn't 
have to go and ask elsewhere, but had direct knowledge of the whereabouts of 
the phone.

Here's the post.
http://lists.digium.com/pipermail/dundi/2004-October/000189.html

Sadly, no other documentation exists in the known universe about this.

Douglas.


> -----Original Message-----
> From: James [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 29, 2006 10:01 AM
> To: Distributed Universal Number Discovery
> Subject: Re: [Dundi] DUNDi Docs
> 
> 
> Have you looked at:
> 
> http://txaug.net/storage/users/3/3/images/17/Using%20DUNDi%20w
> ith%20a%20Cluster%20of%20Asterisk%20Servers.pdf#search=%22Usin
> g%20DUNDi%20with%20a%20Cluster%20of%20Asterisk%20Servers%22
> 
> James Taylor
> www.metrotel.net
> 
> ----- Original Message ----- 
> From: "Douglas Garstang" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Friday, September 29, 2006 9:34 AM
> Subject: [Dundi] DUNDi Docs
> 
> 
> All,
> 
> I'm trying to configure DUNDi in a tiered arrangement where 3 
> servers take 
> care of registrations and then push those registrations up to 
> a pair of 
> location servers. Subsequent queries for the location of a 
> phone will be 
> direcected to the location servers. Reason for this approach 
> is that as new 
> registration servers are added, it would seem more efficient 
> not to have to 
> query every other node for every lookup, but rather query a 
> system that 
> caches all the registrations.
> 
> I think it's possible, but you do think there's actually any 
> docs on DUNDi 
> about this? A google search yields absolutely zero results, 
> except for the 
> dundi.com website which has no configuration docs.
> 
> Why can't Digium post some good docs and examples on how to 
> effectively use 
> DUNDi? What is their issue with doing this? How do they 
> expect people to 
> embrace their protocol if no one knows how to use it? I just 
> completely fail 
> to understand this.
> 
> Doug.
> _______________________________________________
> Dundi mailing list
> [email protected]
> http://lists.digium.com/mailman/listinfo/dundi
> 
> _______________________________________________
> Dundi mailing list
> [email protected]
> http://lists.digium.com/mailman/listinfo/dundi
> 
_______________________________________________
Dundi mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/dundi

Reply via email to