mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-12 15:45:18 +00:00
* Move LaTeX docs into a tex/ subdirectory of the doc/ dir
* Add a Makefile in doc/tex/ for generating PDF and HTML * Add a README.txt file to doc/tex/ to document which tools are used and what web sites to visit for getting them. * Update build_tools/prep_tarball to put the proper Asterisk version string in the automatically generated PDF for release tarballs git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@72982 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
40
doc/tex/dundi.tex
Normal file
40
doc/tex/dundi.tex
Normal file
@@ -0,0 +1,40 @@
|
||||
http://www.dundi.com
|
||||
Mark Spencer, Digium, Inc.
|
||||
|
||||
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 incurring 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.
|
||||
|
||||
For more information visit http://www.dundi.com
|
||||
|
||||
\section{DUNDIQUERY and DUNDIRESULT}
|
||||
|
||||
The DUNDIQUERY and DUNDIRESULT dialplan functions will let you initiate
|
||||
a DUNDi query from the dialplan, see how many results there are, and access
|
||||
each one. Here is some example usage:
|
||||
|
||||
\begin{verbatim}
|
||||
exten => 1,1,Set(ID=${DUNDIQUERY(1|dundi_test|b)})
|
||||
exten => 1,n,Set(NUM=${DUNDIRESULT(${ID}|getnum)})
|
||||
exten => 1,n,NoOp(There are ${NUM} results)
|
||||
exten => 1,n,Set(X=1)
|
||||
exten => 1,n,While($[${X} <= ${NUM}])
|
||||
exten => 1,n,NoOp(Result ${X} is ${DUNDIRESULT(${ID}|${X})})
|
||||
exten => 1,n,Set(X=$[${X} + 1])
|
||||
exten => 1,n,EndWhile
|
||||
\end{verbatim}
|
||||
|
Reference in New Issue
Block a user