Install is pretty straight forward, there is (readme.txt) file.
I use winscp382 from the download section on this web site.
As I'm not big on command line any more.

There is 1 file asterisk.sh to copy to /cgi-bin/

Copy asteriskGUI to the /var/www/

I rename the asteriskGUI to asterisk as to make entering the url easier
http:\\your-meshnode:8080/asterisk/asterisk.html

That is it,

I have found another asterisk GUI which I will be testing in the next week, it has little larger footprint not much 185kb total maybe less if some doc files can be left out.
It has little better interface to just add and edit extensions and the whole system..

I will post up some time next week, If it works out ok..

I have also worked on some possible fixes for error messages. I will be posting them

[snip from Guide to Asterisk on an HSMM-Mesh]
NOTE: You may disregard this warning. It does not effect calls:
[Jan 1 01:37:18] WARNING[11607]: db.c:57 dbinit: Unable to open Asterisk
database '/var/lib/asterisk/astdb': No such file or directory

It seem to make Asterisk work better have not broke my router yet if it stays that way I will post the fix. also should hel with Voicemail.


73 Bob N7WWK
Putnam County Florida
Auxiliary Emergency Communications

BTW, there is this password reset process.  I didn't think of it at first.

http://hsmm-mesh.org/documentation/71-using-safe-mode-to-reset-a-forgotten-password.html

I picked up a directional antenna today and I now have it mounted on a pole at the peak

of my garage roof.  I have tried picking up any nodes to the north, but no luck.  I will soon try

aiming it to the south and try to pick up a node in Spanish Fork.

W7MJP

I bought two V1 WRT54G routers on Ebay.  After getting the proper current rated 5V power supply I was able to install the mesh 0.4.3 firmware on one of them.  It has a CDF1 serial number.  It did require that I install the latest greatest Linksys firmware before it would accept the Mesh firmware.  The other unit however, which has a CDF0 serial number, has consistently displayed the "Incorrect image file" error that I have read about and researched.  I attempted to upgrade the Linksys firmware on this unit as well assuming it was a similar problem but that file is rejected as well.  I have tried both the tftp an tftp2 clients with no luck.  The tftp client comes back with the same incorrect image file error.  The tftp2 client gave me a server error of some type that I neglected to write down.

Being that this is one of the first versions of this model to ship I was wondering if it maybe required a different firmware file from Linksys but I cannot find such a beast. 

It seems there is something more going on here.  I have performed the 30-30-30 reset.  The only difference I can find is that this is the first of this model, judging by the serial number.

I have seen that others have encountered this problem with the V1 routers and am hoping that a solution has been found that hasn't been documented here.

Any help for me out there?

Kirk - N6SXR

I presume you mean "Still does NOT work." 

Unplug the power for a day or so.  I suspect that won't work, but it's cheap to try.

Sorry, I should not be typing while this tired....

Try holding the reset button for 30 seconds, then power cycle and see if that takes you back to default.

KTF

There has been some recent discussion in Utah County about mesh so I'm creating a thread for those who are curious or want to connect.

I've set up a mesh node in Pleasant Grove.  N7TTP-1001.  It's currently using a directional dish facing south across Utah Valley.    I'll need to modify my current antenna situation since the current setup is mainly for testing.   Once I've verified it's working as intended, I'll make a more permanent installation.

If you're in Utah County or nearby contact me and I can swing my antenna (if needed) to your location.

-Tyler N7TTP

~

GEEZ, I hate the GUI editor this board uses.  After fighting it for a while, it ate my post. 

The best way to learn is by doing.   Have you set up a network?  Get some WRT54GLs (Check the compatible hardware list)  and put the non-HSMM OLSR on them. Set up a network and use it.

Set up your Serval network and use it.  Then connect the two. 

Then do the same with HSMM.  There's nothing sacred about HSMM.  It's probably the closet you'll get right now to "follow the instructions and you'll have a network."

The WNDW book is probably the best "Mesh for Beginners" reference right now, although it's not about HSMM in particular.

BTW, I'm not one of the developers, just a user.

I came across this now have it running on the WRT54Gv2 node with Asterisk. It is Asterisk GUI 2.3

Very easy to install, was made to run on routers. You can edit SIP.conf and extensions.conf , voicemail.conf. reload them and view logs calls.

This Screen shot from my wife node. it also has APRX running [ ki4wqf-6 ]

The asterisk GUI has install read me file in the zip and is downloadable from

http://www.fivn.com/products/asterisk.html Free Download I also attached the zip file

Hope this Helps: 1012 is my Android with 3CXPhone, 1013 is a Grandstream GPX-2000.}Next Project is getting the WRTP54g on line now that they are unlocked {see other Post}

Attachments
 asteriskGUI-2.3.zip [18 KB] ::

I have Successfully unlocked WRTP54g with CYT Device Unlock and reflashed the new firmware. Still trying to get them to connect. I'm also setting up 3CX Phone System on computer server connected to mesh node. This for testing may switch to the Asterisk directly on the mesh WRT54g v2.

Internet search for CYT Device Unlock, will yeild the turtorial and software links to get started. It will aslo unlock

 - Linksys RTP300
- Linksys WRTP54G
- Linksys PAP2 v2.0 (not original PAP2)
- Motorola vt2442 (run using cmd-line arg: MOTO )
- D-Link VTA-VR (run using cmd-line arg: DLINK )
- Vtech IP8100

Hope this helps some

73 Bob N7WWK

Well, you can debate "related," but they're not compatible in the sense that they won't connect to each other wirelessly. 

The only device an HSMM mesh node will connect to wirelessly is another HSMM mesh nodes.

Some of this is by deliberate design.  Some of this is simply that two networks have to do a LOT of configuration to mesh together.  Even if two different networks both use OLSR, there's still a lot of configuration necessary to make all the computers on the network capable of working with each other.

The biggest value add of HSMM-MESH is the configuration that goes on top of OLSR to make things work seamlessly. 

The wired ethernet ports will connect to non-HSMM devices, but it's not designed to "mesh" with other networks over these ports.

The free opinions of what's legal here are pretty worthless.  Off the cuff, I can't tell you any particular reason why it would be illegal. 

From a technical standpoint:

1) It's not going to connect wirelessly to the HSMM-MESH system.

2) If you somehow got a Serval mesh connected to a wired Ethernet plug, and connected that plug to one of the ports on a HSMM WRT54, you might be able to configure some useful connections, but it would probably take a lot of tinkering. 

If you got it connected, you would probably not have the two networks "meshed" meshed together.  You might be able to use Serval to provide an internet link to the HSMM side or vice versa.  The most likely scenario would be something like a home router setup with something like a one way NAT connection.

I know almost nothing about Serval, but I have some idea of the limitations on what HSMM can do.