System information

by requesting the extension numbers from the remote location when your local box
doesn’t know how to reach them.
Additionally, if one of the locations had a cheaper route to a PSTN number you wanted
to dial, you could request that route in your DUNDi cloud. For example, if one box
was located in Vancouver and the other in Toronto, the Vancouver office could send
calls destined for the Toronto area across the network using VoIP and out the PRI in
Toronto, so they can be placed locally on the PSTN. Likewise, the Toronto office could
place calls destined for Vancouver out of the PRI at the Vancouver office.
The dundi.conf File
It is often useful to be aware of the options available to us prior to delving into the
configuration file, but feel free to skip this section for now and come back to reference
particular options after you’ve got your initial configuration up and working.
There are three sections in the dundi.conf file: the [general] section, the [mappings]
section, and the peer definitions, such as [FF:FF:FF:FF:FF:FF]. We’ll show the options
available for each section in separate tables.
Table 23-1 lists the options available in the [general] section of dundi.conf.
Table 23-1. Options available in the [general] section
Option Description
department Used when querying a remote system’s contact information. An example might be: Communications.
organization Used when querying a remote system’s contact information. An example might be: ShiftEight.org.
locality Used when querying a remote system’s contact information. An example might be: Toronto.
stateprov Used when querying a remote system’s contact information. An example might be: Ontario.
country Used when querying a remote system’s contact information. An example might be: Canada.
email Used when querying a remote system’s contact information. An example might be:
[e-mail]
phone Used when querying a remote system’s contact information. An example might be: [phone]
bindaddr Used to control which IP address the system will bind to. This can only be an IPv4 address. The default is
0.0.0.0, meaning the system will listen (and respond) on all available interfaces.
port The port to listen for requests on. The default is 4520.
tos The Terms of Service or Quality of Service (ToS/QoS) value to be used for requests. See https://wiki.asterisk
.org/wiki/display/AST/IP+Quality+of+Service for more information about the values available and how
to use them.
entityid The entity ID of the system. Should be an externally (network) facing MAC address. The format is
00:00:00:00:00:00.
cachetime How long peers should cache our responses for, in seconds. The default is 3600.
ttl The time-to-live, or, maximum depth to search the network for a response. The maximum wait time for a
response is calculated using (2000 + 200 * ttl) ms.
The dundi.conf File | 505