System information

Option Description
include Used to control whether this peer is included in searches for the mapping defined. Can be set to the value of
all if used for all mappings.
noinclude Used to control whether this peer is excluded from searches for the mapping defined. Can be set to all if this
peer should be excluded from all lookups.
permit Used to control whether this peer can perform lookups against a particular mapping. If the value is set to
all, this peer can search against all defined mappings.
deny Used to control which mappings this peer is restricted from searching. The value can be set to all to restrict
this peer from being able to perform any lookups against defined mappings.
model Used to control whether this peer can receive requests (inbound), transmit requests (outbound) or do both
(symmetric).
precache Typically used when we have a node with only a few routes that wants to push those values up to another node
that is providing more responses (this is known as precaching, providing an answer when no request has been
received). The values include outgoing, incoming, and symmetric. If this is set to outgoing, we push
routes to this peer. If set to incoming, we receive routes from this peer. If set to symmetric, we do both.
Configuring Asterisk for Use with DUNDi
There are three files that need to be configured for DUNDi: dundi.conf, exten-
sions.conf, and sip.conf.
*
The dundi.conf file controls the authentication of peers whom
we allow to perform lookups through our system. This file also manages the list of peers
to whom we might submit our own lookup requests. Since it is possible to run several
different networks on the same box, it is necessary to define a different section for each
peer, and then configure the networks in which those peers are allowed to perform
lookups. Additionally, we need to define which peers we wish to use to perform
lookups.
General Configuration
The [general] section of dundi.conf contains parameters relating to the overall opera-
tion of the DUNDi client and server:
; DUNDi configuration file for Toronto
;
[general]
;
department=IT
organization=toronto.example.com
locality=Toronto
stateprov=ON
* The dundi.conf and extensions.conf files must be configured. We have chosen to configure sip.conf for the
purposes of address advertisement on our network, but DUNDi is protocol-agnostic, so iax.conf,
h323.conf, or mgcp.conf could be used instead. DUNDi simply performs the lookups; the standard methods
of placing calls are still required.
Configuring Asterisk for Use with DUNDi | 507