Yep, It maps to the other node just fine.  You could have a phone on Node C that is registered to Node A (asterisk+dundi) and call a phone on Node D that is registered to Node B (asterisk+dundi).

Along with opening 5004, 5060, 10000-20000, you will also need to open 4569 on the asterisk+dundi nodes.

Here are the files.

http://downloads.openwrt.org/kamikaze/8.09.2/brcm-2.4/packages/asterisk14_1.4.23.1-1.2_mipsel.ipk

Attachments
 DUNDi.zip [5 KB] ::
 DUNDi_So_Easy.pdf.zip [55 KB] ::
 Suppliments.zip [54 KB] ::

Some reading for All on just what DUNDi is, and how it works.

http://asteriskdocs.org/en/3rd_Edition/asterisk-book-html-chunk/asterisk-CHP-5.html

I just got DUNDi working with HSMM-MESH. Let me dump what I have from the two nodes for us all to sift through.

Thats GREAT! I was a member of MARC two years ago, how ever I have moved out of the area. Im still in Mississauga twice a day tho :) The ISP Tunnel is great for remote back bones, for areas where the mesh becomes too far for practical use. I dont imagine it would be used as more then a means to connect remote mesh's together. Today Iv made some leeway in the Asterisk front.. The Phones are talking localy hopefuly this weekend I can get them talking across the mess. Even if it is direct :)

The only thing I have not done is "Study and Implement DUNDi into the HSMM-MESH on TWO Nodes." I am currently working on that now and should have something to you within a wekk.

As for the other items on your list? You shouldn't have any problem. I've sustained multiple 2+ hour calls over the mesh on the same and across different nodes (with hops in-between as well) without any hickups.

Best of luck! Keep me posted.

I've used that program for quite some time. It really saves on not having to SSH to the node every time.

When I put the files inside a /www/asterisk/ folder, but that reproduced the same error you had. Make sure you rename the style.css attached with the AsteriskGUI to something else and change the respective filename in the asterisk.html file. After you do this, put the files inside the /www/ folder and don't forget to move asterisk.sh to the cgi-bin folder and chmod it.

Just joking.  I assume the procedure works as listed.

The method is solid.  WX5U, where are you getting lost?

Iv been reading abaout it and HSMM-MESH... I am very remote from Toronto (Between Brantford and Woodstock) But I do work in Toronto Every day. Would any of the members of YRARC who are involved with HSMM-MESH be interested in trying to get a central Ontario MESH Link established?

Im only reading up on it now, so Im in the "Interest" stage right now, so I imagine there is quite a bit to do and learn yet. But Im willing to learn if others are as well. Part of this would involve my other project, the HSMM-MESH Utilizing Asterick / DUNDi for VoIP MESH.

I'm running a wrt54g v1.1 as an AP with a wrt54gs in node mode. They've run fine for a few days. Suddenly tonight I cannot create a stable connection to the AP. It shows up in the list of wifi connections available. It will connect but then begins a cycle of trying to identify the network, then disconnects, connects, then indentifying again, rinse and repeat.

During the first few moments it hands out a 172.27.0.5 address to the connected computer. Then, after a few attempts identifying the network, it hands out a 169.xxx.xxx.xxx address. When I flip to static ip and assign the 172.27.0.5 address myself, I can view the status page at 172.27.0.2 like normal. 

Is this a problem with the DHCP server? The same thing happens when I use a hardwire connection to the AP via one of the LAN ports. 

I've rebooted the router but still get the same results. Any ideas??