DUNDi configuration - Revision history

Gijs at 10:21, 27 February 2007

2007-02-27T10:21:15Z

Gijs: /* DUNDi CLI-checks */

2007-02-27T10:20:40Z

DUNDi CLI-checks

Gijs: /* Configuring DUNDi */

2007-02-27T10:18:35Z

Configuring DUNDi

Gijs at 09:41, 27 February 2007

2007-02-27T09:41:01Z

Gijs: /* DUNDi CLI-checks */

2007-02-27T09:27:41Z

DUNDi CLI-checks

Gijs at 10:27, 12 February 2007

2007-02-12T10:27:54Z

Gijs: /* SIP registration */

2007-02-11T02:17:54Z

SIP registration

Gijs: /* SIP registration */

2007-02-10T17:50:20Z

SIP registration

Gijs at 17:49, 10 February 2007

2007-02-10T17:49:53Z

Gijs at 11:53, 10 February 2007

2007-02-10T11:53:13Z

← Older revision		Revision as of 10:21, 27 February 2007
Line 183:		Line 183:
	* [[Asterisk DUNDi debug]] - Analysis of DUNDi traffic with Asterisk's debug.		* [[Asterisk DUNDi debug]] - Analysis of DUNDi traffic with Asterisk's debug.
	* [http://www.asteriskguru.com/tutorials/cli_cmd_14_page10.html List of Asterisk1.4 dundi-CLI-commands]		* [http://www.asteriskguru.com/tutorials/cli_cmd_14_page10.html List of Asterisk1.4 dundi-CLI-commands]
−
−	~~== Alternatives to DUNDi ==~~
−	You can also try the TDMoE zaptel driver. This is similar to the ztdummy driver in some ways but it will link 2 or more PBX's on the same physical network with zap channels. So on a 100Mb ethernet interface you could potentially get the equivalent of about 50 PRI lines. Overkill maybe, but you can set the number of channels you want. This should be good for interconnecting a voicemail only Trixbox with another tribox handling the calls. In larger installs this would be useful as it offloads the voicemail agi scripts and transcoding to another box. TDMoE is also much simpler to configure in comparison to DUNDI.
−
−	~~you get many of the same features as you do with normal zap channels. It is also very efficient on bandwidth and cpu.~~
−
−	~~DUNDI is a good solution for remote PBX's. ([http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=4361&forum=1 Source])~~

@@ Line 161: / Line 161: @@
 == DUNDi CLI-checks ==
-* '''dundi lookup''':
+===1001@priv:===
-  asterisk1*CLI> dundi lookup 301@priv bypass
+  asterisk1*CLI> dundi lookup 1001@priv
-.     0 IAX2/priv:ByWFbOGKgGmZbM43BJHSZw@2.4tw.nl/301 (EXISTS)
+.     0 IAX2/priv:ZUIkF+Wl0TuXtd13pK5UXQ@192.168.1.106/1001 (EXISTS|NOUNSLCTD|NOCOMUNSLTD)
-      from 00:0c:29:d2:d8:ec, expires in 3600 s
+     from 00:0c:29:d2:d8:ec, expires in 5 s
-  DUNDi lookup completed in 113 ms
+  DUNDi lookup completed in 89 ms
-  asterisk1*CLI> dundi lookup 202@priv
-.     0 IAX2/priv:+DmRAz4RjwF6GQMC3zopfQ@1.4tw.nl/202 (EXISTS)
+===1301@priv:===
-      from 00:0c:29:e4:14:80, expires in 3570 s
+  asterisk1*CLI> dundi lookup 1301@priv
-  DUNDi lookup completed in 13 ms
+.     0 IAX2/priv:NbJdfOHodguANV0MOKuaQg@192.168.1.101/1301 (EXISTS|NOUNSLCTD|NOCOMUNSLTD)

@@ Line 9: / Line 9: @@
 This example connects three peers, '''PBX1''' , '''PBX2''' and '''PBX3'''.
 First edit <tt>iax.conf</tt>. Add the following lines, except for any that are duplicated in the <tt>[general]</tt> section:
@@ Line 21: / Line 22: @@
   allow=gsm
 Now edit <tt>dundi.conf</tt>. The default file is well commented and has lots of examples--you'll find definitions of all the directives in there. This is where your mapping contexts are defined, which follow this format:
@@ Line 27: / Line 29: @@
 The following configuration creates two DUNDi mapping contexts:
   [general]
   port=4520
@@ Line 34: / Line 37: @@
   autokill=yes
   secretpath=dundi
+*<tt>entityid</tt> is optional. When not specified, the MAC-address of the first networkcard is used.
   department=Rubzzzz
   organization=Rubzzzz, Inc.
@@ Line 43: / Line 49: @@
   phone=+12565551212
   [mappings]
   priv => dundi-priv-local-custom,0,IAX2,koekje:${SECRET}@192.168.1.101/${NUMBER},nounsolicited,nocomunsolicit,nopartial
   [00:0C:29:A7:E0:73] ; MAC address of TrixBox2 eth0
   model = symmetric
@@ Line 66: / Line 75: @@
   ;dynamic=yes
-You need to create RSA authentication keys for your server. You may name them anything you want; a good naming convention is to use your server's fully-qualified domain name. Create keys with these commands:
+You need to create RSA authentication keys for your server. You may name them anything you want; a good naming convention is to use your server's fully-qualified domain name.
   # cd /var/lib/asterisk/keys
   # /usr/sbin/astgenkey -n myhost.mynet.com
-This creates two keys: <tt>myhost.mynet.com.pub</tt> and <tt>myhost.mynet.com.key</tt>. The public key, <tt>myhost.mynet.com.pub</tt>, must be distributed to all servers you are peering with. Post it on your Web site if you like. The ''private key'' is unencrypted, and like all private encryption keys '''must be guarded carefully'''. Then the <tt>res_crypto.so</tt> line interface:
+This creates two keys: <tt>myhost.mynet.com.pub</tt> and <tt>myhost.mynet.com.key</tt>. The public key, <tt>myhost.mynet.com.pub</tt>, must be distributed to all servers you are peering with. (in the <tt>/var/lib/asterisk/keys
   # asterisk -r
@@ Line 77: / Line 89: @@
   asterisk1*CLI># reload pbx_dundi.so
-From here you can also run the command <tt>show keys</tt> to see all of your RSA keys. Now go back to <tt>iax.conf</tt> and add the dundi user.
+From here you can also run the command <tt>show keys</tt> to see all of your RSA keys.
 <tt>dundi/secret</tt> is an encryption key automatically generated by Asterisk. You may view this key by running the <tt>database show</tt> command from the Asterisk CLI.
-Finally, edit <tt>extensions.conf</tt>; this is where you define what numbers to share and what to do with them. Telephone numbers must follow this format:
+===extensions_custom.conf===
- country_code area_code prefix number
+Finally, edit <tt>extensions_custom.conf</tt>; this is where you define what numbers to share and what to do with them. Telephone numbers must follow this format:
 == SIP registration ==

@@ Line 1: / Line 1: @@
-In order to keep our config files clean, we created 2 seperate files for resp. the extensions and the iax-config.
+In order to keep our config files clean, we edited the <tt>*_custom.conf</tt> files, where possible.
 ==Configuring DUNDi==
-([http://www.linuxplanet.com/linuxplanet/tutorials/6270/2/ Source])
+For making DUNDi work, you have to edit three Asterisk configuration files. The three files are <tt>dundi.conf</tt>, <tt>iax.conf</tt>, and <tt>extensions.conf</tt>. These are in <tt>/etc/asterisk/</tt> on the Trixbox.
+* <tt>dundi.conf</tt> controls peer authentication.
-Warm up your favorite text editor, because we're going to edit three Asterisk configuration files. The three files are <tt>dundi.conf</tt>, <tt>iax.conf</tt>, and <tt>extensions.conf</tt>. These are in <tt>/etc/asterisk/</tt> on Asterisk@Home. <tt>dundi.conf</tt> controls peer authentication, <tt>iax.conf</tt> is our transport protocol, and <tt>extensions.conf</tt> contains your dialplans.
+* <tt>iax.conf</tt> is our transport protocol.
-This example connects two peers, ''MyHost'' and ''OtherHost''.
+This example connects three peers, '''PBX1''' , '''PBX2''' and '''PBX3'''.
 First edit <tt>iax.conf</tt>. Add the following lines, except for any that are duplicated in the <tt>[general]</tt> section:
-  [dundi]
+  [koekje]
-    type=user
+ type=user
-    dbsecret=dundi/secret
+ dbsecret=dundi/secret ; the password used by others to make an IAX connection to this machine.
-    context=dundi-local
+ context=from-internal ; this context must not be changed when using Trixbox.
-    disallow=all
+ regcontext=d_adv      ; used for registration of connected phones.
-    allow=ulaw
+ disallow=all
-    allow=alaw
+ allow=ulaw
-    allow=g726
+ allow=alaw
 Now edit <tt>dundi.conf</tt>. The default file is well commented and has lots of examples--you'll find definitions of all the directives in there. This is where your mapping contexts are defined, which follow this format:
- dundi_context => local_context,weight,technology,destination,[options]
+<tt>dundi_context => local_context,weight,technology,destination,[options]</tt>
 The following configuration creates two DUNDi mapping contexts:
   [general]
   port=4520
+  entityid=00:0C:29:97:0B:98 ; This is the mac address of eth0
- ;use the server's MAC address for the entityid
+  cachetime=5
   ttl=32
   autokill=yes
   secretpath=dundi
-−
   [mappings]
-  ;copy this as shown, substituting your own server and hostname
+  priv => dundi-priv-local-custom,0,IAX2,koekje:${SECRET}@192.168.1.101/${NUMBER},nounsolicited,nocomunsolicit,nopartial
- ;this should be one long unbroken line
- dundi-peer1 => dundi-priv-local,0,IAX2,dundi:${SECRET}@myhost.mynet.com ${NUMBER},nounsolicited,nocomunsolicit,nopartial
+  [00:0C:29:A7:E0:73] ; MAC address of TrixBox2 eth0
- ;our OtherHost peer is configured here
+ model = symmetric
- ;and is allowed access only to dundi-peer1
+ host = 192.168.1.103
-  [aa:bb:cc:dd:ee:ff] ;MAC address of otherhost.elsewhere.com
+ inkey = dundi
-  model = symmetric
+ outkey = dundi
-  host = otherhost.elsewhere.com
+ include = priv
-  inkey = otherhost.elsewhere.com
+ permit = priv
-  outkey = myhost.mynet.com
+ qualify = yes
-  include = dundi-peer1
+ dynamic=yes
 You need to create RSA authentication keys for your server. You may name them anything you want; a good naming convention is to use your server's fully-qualified domain name. Create keys with these commands:

← Older revision		Revision as of 09:27, 27 February 2007
Line 144:		Line 144:
	DUNDi lookup completed in 13 ms		DUNDi lookup completed in 13 ms

		+
		+	* [[Asterisk DUNDi debug]] - Analysis of DUNDi traffic with Asterisk's debug.
	* [http://www.asteriskguru.com/tutorials/cli_cmd_14_page10.html List of Asterisk1.4 dundi-CLI-commands]		* [http://www.asteriskguru.com/tutorials/cli_cmd_14_page10.html List of Asterisk1.4 dundi-CLI-commands]

← Older revision		Revision as of 10:27, 12 February 2007
Line 1:		Line 1:
		+	In order to keep our config files clean, we created 2 seperate files for resp. the extensions and the iax-config.
		+	These files are:
		+	extensions_gijs_ruben.conf
		+	iax_gijs_ruben.conf
		+	These are included in the following files:
		+	<tt>extensions.conf:</tt>
		+	#include extensions_gijs_ruben.conf
		+	<tt>iax.conf: </tt>
		+	#include iax_gijs_ruben.conf
		+
		+
		+
	==Configuring DUNDi==		==Configuring DUNDi==
	([http://www.linuxplanet.com/linuxplanet/tutorials/6270/2/ Source])		([http://www.linuxplanet.com/linuxplanet/tutorials/6270/2/ Source])

@@ Line 118: / Line 118: @@
     '202' =>          1. Noop(202)                                  [SIP]
   -= 2 extensions (2 priorities) in 1 context. =-
 == Alternatives to DUNDi ==

← Older revision	Revision as of 17:49, 10 February 2007
Line 108:	Line 108:


	+	== SIP registration ==
	+	Add the following to <tt>sip.conf<tt>:
	+	regcontext=sipregistration
	+	Once the phones, in this example 201 and 202 register with the PBX, a context of
	+	[sipregistration] appears and can be shown in the Asterisk CLI:
	+	asterisk1*CLI> show dialplan sipregistration
	+	[ Context 'sipregistration' created by 'SIP' ]
	+	'201' => 1. Noop(201) [SIP]
	+	'202' => 1. Noop(202) [SIP]
	+	-= 2 extensions (2 priorities) in 1 context. =-