DUNDi E.164 Configuration for Messinet Secure Services Peering

Here is the information you will need if you would like to add the Messinet Secure Services Asterisk PBX as a DUNDi E.164 peer.

You will first need to obtain and install the public keys for Messinet Secure Services in your Asterisk keys directory. The public keys for the primary Messinet Secure Services DUNDi E.164 node is listed below.

iax.conf

Enter the following information in your iax.conf file. This defines the user for incoming calls using the DUNDi "e164" context defined below. 

[dundi]
type=user
accountcode=dundi
dbsecret=dundi/secret
context=dundi-e164-local
; Please see Asterisk Project Security Advisory - AST-2009-006
; http://downloads.asterisk.org/pub/security/AST-2009-006.html
; before using the following "requirecalltoken" variable.
;requirecalltoken=no

extensions.conf

The following is an example of the DUNDi-related contexts in your extensions.conf file. These contexts define the extensions that you share via the "e164" DUNDi context. These are only examples. You should replace the extension matches with numbers that you will terminate for other DUNDi peers. 

[dundi-e164-canonical]
; List canonical entries here
;exten => 12564286000,1,Macro(std-exten,6000,IAX2/foo)
;exten => _125642860XX,1,Dial(IAX2/otherbox/${EXTEN:7})

[dundi-e164-customers]
; If you are an ITSP or Reseller, list your customers here.
;exten => _12564286000,1,Dial(SIP/customer1)
;exten => _12564286001,1,Dial(IAX2/customer2)

[dundi-e164-via-pstn]
; If you are freely delivering calls to the PSTN, list them here
;exten => _1256428XXXX,1,Dial(Zap/g2/${EXTEN:7}) ; Expose all of 256-428
;exten => _1256325XXXX,1,Dial(Zap/g2/${EXTEN:7}) ; Ditto for 256-325

[dundi-e164-local]
include => dundi-e164-canonical
include => dundi-e164-customers
include => dundi-e164-via-pstn

[dundi-e164-switch]
switch => DUNDi/e164

[dundi-e164-lookup]
; Locally to lookup, try looking for a local E.164 solution
; then try DUNDi if we don't have one.
include => dundi-e164-local
include => dundi-e164-switch

[macro-dundi-e164]
exten => s,1,Goto(${ARG1},1)
include => dundi-e164-lookup

[some-outbound-context]
exten => _1NXXNXXXXXX,1,Macro(dundi-e164,${EXTEN})

dundi.conf

Enter the following information in the [mappings] section of your dundi.conf file. This portion of the configuration states that DUNDi queries for the DUNDi "e164" context are mapped to the [dundi-e164-canonical], [dundi-e164-customers] and [dundi-e164-via-pstn] contexts of your extensions.conf file. 

[mappings]
e164 => dundi-e164-canonical,0,IAX2,dundi:${SECRET}@<YOUR_EXTERNAL_HOST_NAME_OR_IP>/${NUMBER}
e164 => dundi-e164-customers,100,IAX2,dundi:${SECRET}@<YOUR_EXTERNAL_HOST_NAME_OR_IP>/${NUMBER}
e164 => dundi-e164-via-pstn,400,IAX2,dundi:${SECRET}@<YOUR_EXTERNAL_HOST_NAME_OR_IP>/${NUMBER}

Enter the following information after the [mappings] section of your dundi.conf file, described above. This defines my Asterisk servers as primary and secondary peers for your DUNDi lookups. The connection to my secondary node will allow you to main maximum connectivity to my portion of the DUNDi E.164 cloud in the even that my primary node becomes unavailable. 

; Messinet Secure Services primary peer
[00:12:3F:2A:38:72]
model=symmetric
host=messinet.com
inkey=messinet.com
outkey=<YOUR_KEY_NAME>
include=e164
permit=e164
qualify=no
order=primary

Submit Your DUNDi E.164 Node Configuration

Finally, you will need to provide your DUNDi information to me so I can include it in my dundi.conf file.

  • Copy the following block and enter your peering information. 
    [00:00:00:00:00:00] ; The MAC address of an interface you own.
model=symmetric
host=<YOUR_EXTERNAL_HOST_NAME>
inkey=<YOUR_KEY_NAME>
outkey=messinet.com
include=e164
permit=e164
qualify=no
order=primary
  • Send an e-mail to amessina AT messinet DOT com and paste the information into the body of the e-mail.
    • Include a link to your public key or attach the key to the e-mail.
    • Please include a "test" phone number your terminate via DUNDi E.164 that I can dial to test the configuration.
  • I will configure your node on my server(s) and respond with additional information.