Messinet Secure Services currently offers direct DUNDi E.164 PSTN termination to the Chicago, IL, US metropolitan area including the following area codes:
224, 312, 630, 708, 773, 800, 847, 866, 877, 888.
I am open to peering with anyone willing to share numbers in the E.164 namespace and execute the
Digium General Peering Agreement.
If you are interested in becoming a Messinet Secure Services DUNDi peer, follow the
Asterisk DUNDi Configuration instructions below.
Current DUNDi E.164 Peer Network
I want to thank James Blackwell for helping me build, configure and advertise this DUNDi E.164 network and the related pages.
Network Maps
DUNDi E.164 US Peer Network Coverage Map (
SVG) (PNG)
DUNDi E.164 Worldwide Peer Network Google™ Map
DUNDi node details including, terminated country codes, area codes & prefixes
North America
00:08:54:E0:72:1C - Blue Ridge, GA, US
00:12:3F:2A:38:72 - Chicago, IL, US
00:C0:9F:29:EC:C9 - Elburn, IL, US
00:0E:A6:C8:B8:B4 - Hartford, CT, US
00:40:CA:4C:55:55 - Hartford, CT, US
00:30:48:52:B0:C8 - Huntsville, AL, US
00:20:ED:6F:E0:AF - Mililani, HI, US
00:17:31:DA:CE:FC - Kissimmee, FL, US
00:D0:09:60:CA:FD - Westfield, MA, US
Worldwide
00:30:1B:27:EE:8A - Bern, BE, CH
(00:80:AD:97:32:E9)
? - Coulommiers, 77, FR
(00:13:49:2B:C5:9B)
? - Cúcuta, NSA, CO
00:1B:78:E3:03:48 - Dubrovnik, HR
(00:00:CB:56:46:D3)
? - Kaiseraugst, AG, CH
(00:13:D3:A8:8E:F8)
? - Kaiseraugst, AG, CH
00:D0:B7:86:2F:F3 - Kiffis, 68, FR
00:AA:00:AD:18:49 - Lörrach, BW, DE
00:0B:6A:6C:A4:7F - Mönchengladbach, NRW, DE
00:1B:78:E1:A0:FC - Osijek, HR
00:1B:78:E2:65:F8 - Rijeka, HR
00:1B:78:E2:3B:0C - Split, HR
00:30:05:07:A8:F3 - Spreitenbach, AG, CH
00:40:B9:60:63:00 - Überlingen, BW, DE
00:10:A4:0D:24:2C - Weil am Rhein, BW, DE
00:16:3E:12:94:67 - Zagreb, HR
00:30:48:2D:ED:28 - Zuchwil, SO, CH
(00:04:75:D0:EF:24)
? - Zürich, ZH, CH
(00:01:02:07:E7:67)
? - Zürich, ZH, CH
00:0C:76:3D:6C:E2 - Zürich, ZH, CH
Legend
| Digium GPA executed | Direct connection with Messinet Secure Services |
| Digium GPA unknown | Indirect connection with Messinet Secure Services |
Asterisk DUNDi Configuration
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. For additional DUNDi configuration information, you may want to take a look at my
Local Calling Area Grabber project.
You will first need to obtain and install the public key for Messinet Secure Services in your Asterisk keys directory. The Messinet Secure Services public key is available at
http://messinet.com/~amessina/projects/dundi/messinet.com.pub.
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
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})
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>/${NUMBER}
e164 => dundi-e164-customers,100,IAX2,dundi:${SECRET}@<YOUR_EXTERNAL_HOST_NAME>/${NUMBER}
e164 => dundi-e164-via-pstn,400,IAX2,dundi:${SECRET}@<YOUR_EXTERNAL_HOST_NAME>/${NUMBER}
Enter the following information after the [mappings] section of your dundi.conf file, described above. This defines me as a peer for your DUNDi lookups.
[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
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. Then send that information along with a link to your public key to me via the Contact Form.
[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
