Peers
Asterisk PBX systems that use DUNDi are peered as a cooperating system of DUNDi nodes, each having certain configuration to access a DUNDI instance on at least one other node. In the DUNDi configuration one can limit the number of consecutive lookups between peers by setting theAdvertising extensions
Each DUNDi peer can advertise its own extensions and their context. E.g. if you can connect some local E.164 number(s), you can advertise these. DUNDi configuration assigns a priority weight to each advertised extension. Low values represent a high priority and must be chosen first when more than one answer is received from a lookup.Example
In the Asterisk CLI one can do a lookup by hand to test if a DUNDi configuration works. asterisk1*CLI> dundi lookup 301@priv bypass 1. 0 IAX2/priv:ByWFbOGKgGmZbM43BJHSZw@192.168.1.2/301 (EXISTS) from 00:0c:29:d2:d8:ec, expires in 3600 s DUNDi lookup completed in 113 ms The above DUNDi lookup tells the PBX to ask the known peers if they know how to reach extension 301 in the "priv" network. The answer consists of 6 parts: * The used protocol to communicate is IAX2. * The context-name is "priv". * The secret key of the PBX, which can redirect you to extension 301 is ByW ..SZw (this changes periodically) * The address of this PBX is 192.168.1.2 (or some domainname, should be reachable by the calling party) * The extension to call is 301 (this can be different from what you asked for, e.g. when calls from the outside are not allowed directly to an internal extension) * "EXISTS" tells us the PBX is advertising this number. It is possible the PBX advertises a lot more extensions than really are connected, so it is no guarantee the extension can be reached. In order to prevent the network from overloading and at the same time keep the responses as quick as possible, the involved peers will cache the lookups they see. Because the used keys may become invalid after some period, each lookup has someExternal links