System information

Since we only have a single mapping defined (extensions), we’re going to permit and
include extensions within our peer definitions on both the Toronto and Vancouver
systems.
On Toronto, we’ll permit Vancouver to search the extensions mapping, and use Van-
couver whenever we’re performing a lookup within the extensions mapping:
[00:00:00:00:00:00] ; Vancouver Remote Office
model = symmetric
host = vancouver.example.com
inkey = vancouver
outkey = toronto
qualify = yes
dynamic=yes
permit=extensions
include=extensions
Similarly, we’ll permit and include the extensions mapping for the Toronto office on
the Vancouver system:
[FF:FF:FF:FF:FF:FF] ; Toronto Remote Office
model = symmetric
host = toronto.example.com
inkey = toronto
outkey = vancouver
qualify = yes
dynamic=yes
permit=extensions
include=extensions
After modifying the peers, we reload the pbx_dundi.so module to have the changes take
effect:
*CLI> module reload pbx_dundi.so
The include and permit configuration can be verified via the dundi show peer command
on the Asterisk CLI:
*CLI> dundi show peer 00:00:00:00:00:00
Peer: 00:00:00:00:00:00
Model: Symmetric
Host: 172.16.0.104
Port: 4520
Dynamic: no
Reg: No
In Key: vancouver
Out Key: toronto
Include logic:
-- include extensions
Query logic:
-- permit extensions
Now we can test our lookups. We can do this easily from the Asterisk CLI using the
dundi lookup command. If we perform a lookup from the Vancouver system, we’ll
receive a response from the Toronto system with an address we can use to place a call.
Configuring Asterisk for Use with DUNDi | 513