What is DUNDi - Revision history

129.125.21.153 at 13:17, 16 March 2007

2007-03-16T13:17:05Z

129.125.21.153: /* DUNDi as a routing protocol */

2007-03-16T13:16:22Z

DUNDi as a routing protocol

Gijs: /* DUNDi as a routing protocol */

2007-02-20T19:39:24Z

DUNDi as a routing protocol

Gijs: /* DUNDI lookup schema */

2007-02-17T23:53:08Z

DUNDI lookup schema

Gijs: /* DUNDI lookup schema */

2007-02-17T23:52:21Z

DUNDI lookup schema

82.161.30.84: /* How does it work? */

2007-02-17T21:56:12Z

How does it work?

Gijs: /* How does it work? */

2007-02-17T00:17:08Z

How does it work?

Gijs: /* DUNDi call flow */

2007-02-17T00:14:47Z

DUNDi call flow

Gijs: /* DUNDi call flow */

2007-02-17T00:09:30Z

DUNDi call flow

Gijs at 23:37, 16 February 2007

2007-02-16T23:37:16Z

@@ Line 47: / Line 47: @@
 *Can use the same context for both advertisements and call handling – or separate contexts (recommended)
 *Can use pattern matching to advertise “ranges”
 === Channel configuration file ===
@@ Line 54: / Line 52: @@
 *Usually via <tt>iax.conf</tt>, but not necessarily
 *Authentication using <tt>dbsecret</tt> to pull rotating key from AstDB
 == DUNDi Trust Group ==

← Older revision		Revision as of 13:16, 16 March 2007
Line 56:		Line 56:


−	~~== DUNDi as a routing protocol ==~~

← Older revision		Revision as of 19:39, 20 February 2007
Line 57:		Line 57:

	== DUNDi as a routing protocol ==		== DUNDi as a routing protocol ==
		+
		+
		+	== DUNDi Trust Group ==
		+	From [http://www.sineapps.com/news.php?rssid=240 Another DUNDi site]:
		+
		+	DUNDi is essentially a trusted, peer-to-peer system for being able to call any phone number from the Internet. DUNDi works by creating a network of nodes called the "DUNDi E.164 Trust Group" which are bound by a common peering agreement known as the General Peering Agreement or [[GPA]]. The GPA legally binds the members of the Trust Group to provide good-faith accurate information to the other nodes on the network, and provides standards by which the community can insure the integrity of the information on the nodes themselves. Unlike ENUM or similar systems, DUNDi is explicitly designed to preclude any necessity for a single centralized system which could be a source of fees, regulation, etc.
		+
		+	Much less dramatically, DUNDi can also be used within a private enterprise to share a dialplan efficiently between multiple nodes, without incuring a risk of a single point of failure. In this way, administrators can locally add extensions which become immediately available to the other nodes in the system.
		+
		+	In the DUNDi model, there is no central repository. Instead, node participate in a trust system in which each node has a trust relationship with at least one other node in the system. When the client requests a number or extension it does not know how to terminate, it queries the nodes directly connected to it. Those nodes in turn will query nodes which are directly connected to them and so on (care is taken in the protocol to minimize the actual number of transactions and nodes that are queried, while maintaining the same effective answer as querying the entire system). The resulting answers are collated, cached appropriately at each involved node, and passed along to the original requesting party.
		+
		+
		+	==[[Links#DUNDi_links\|DUNDi links]]==

@@ Line 26: / Line 26: @@
 === DUNDI lookup schema ===
-[[image:DUNDi-lookup-schema.gif|center|452px]]
+[[image:DUNDi-lookup-schema.gif|center]]
 == Basic configuration ==

@@ Line 26: / Line 26: @@
 === DUNDI lookup schema ===
-[[image:DUNDi-lookup-schema.gif|center]]
+[[image:DUNDi-lookup-schema.gif|center|452px]]
 == Basic configuration ==

@@ Line 24: / Line 24: @@
 #Incoming call setup and authentication
 #Call is controlled via dialplan logic
 == Basic configuration ==

@@ Line 9: / Line 9: @@
 == How does it work? ==
 ''Ask a friend, and they ask their friends until someone knows the answer.''
@@ Line 16: / Line 17: @@
 === DUNDi call flow ===
 For a DUNDi-lookup, followed by a call, several config-files will play a role.
 #Initial DUNDi request from end point and authentication

@@ Line 53: / Line 53: @@
 *Controls the authentication of the incoming call and delivery to incoming context (as per usual Asterisk fashion)
 *Usually via <tt>iax.conf</tt>, but not necessarily
-*Authentication using <tt>dbsecret<tt> to pull rotating key from AstDB
+*Authentication using <tt>dbsecret</tt> to pull rotating key from AstDB
 == DUNDi as a routing protocol ==