I have been able to successfully get Asterisk to run self-contained on an HSMM-MESH node.  I am now able to plug VoIP phones into wirelessly connected nodes and make phone calls to them through the NAT.  Instructions are attached.  It only takes 30 minutes for the initial setup.

NOTE:  This guide was written with the idea that the user is running Linux to complete the steps.  Instructions may vary slightly for windows users.

EDIT:  Windows version on page 2.

Attachments
 AsteriskDependents.zip [660 KB] ::
 Asterisk Installiation Guide Rev1.2.pdf.zip [784 KB] ::
 Asterisk.zip [785 KB] ::

I am looking for anyone in the Tampa area that may be interested in experimenting with HSMM-MESH. 

I live in north Pinellas county and would like to hear from hams that would like to work with this mode.

73 

Joel WM4P

WM4P@arrl.net

Brnad new to meshing ... have a node (setup was simple with the guide!) here (near Augusta,GA), and looking for local interest, but not sure if any will turn up ...

What's the current status on the tunnelling? Saw some references to it, but not a specific how-to .. Would like to give that a try to be able to play around on a mesh, since i'm currently an "island" here.

thanks!
--david
KJ4IZW
Aiken, SC

Well, I tried editing my post and it didn't update it, and when I pressed back, I lost what I wrote. With that said........

I have been able to install Asterisk to both an HSMM-MESH node and have it up in running right now (not from node-to-node yet) and also on the Raspberry Pi. The Raspberry Pi method is a lot more user friendly than editing configuration files on the HSMM-MESH node. Also, I have installed an email server to the Raspberry Pi as well.

My first finding: Asterisk on the Raspberry Pi works.   However, by using the Raspberry Pi with Asterisk + FreePBX, my calls are currently getting dropped after 10 minutes of operation. I am looking into this issue and have a solution that I will be trying out later today. When I am dialing an extension number, it does take a couple seconds to process and connect. The delay between when the person speaks and the other phone outputting the audio is about 0.5 seconds. Also, with this setup, the Raspberry Pi at max is only using at max ~60% of it's processing power. I have noticed that the WebGUI shows the Raspberry Pi idling most of the time, but that's not a problem.  I would much prefer taking the Pi out of the picture, but if you would like a webGUI interface, than that is the way to go.

As for an e-mail server, it is easy to setup on the Raspberry Pi and works just fine. I used SquirrelMail. When you access the e-mail server, it will appear to not be doing anything when you click on any link, but if you wait, it takes you to that page and functions just fine.  Typical delay is about a second.

I had a friend setup their computer as a TeamSpeak server (Computer-to-Computer VoIP), and that works perfectly fine over the HSMM-MESH network. You might want to check into that too.

Anything else that you would like to know about?

Welcome from the land down under.  I hope you find the mesh as useful as we do.

1. Security at this point is through obscurity.  The olsrd_secure plugin is used for OLSR communications and only those with the proper key can fully participate in the mesh.  Outside of that, it would take specialized knowledge to gain network access, and only a small percentage of the public would have it.  It would be far easier for a local yahoo to get a 2 meter FM radio and cause trouble on the repeaters than it would be to fiddle with the mesh.

2. The domain name problem was as yet unsolved when the firmware was released to the public, and it remains unsolved.  I know it may be annoying to those of you not in Austin, but since austin.tx.us.mesh is hardcoded into several places in the firmware you can expect the mesh to break if the domain name is changed.  I have some ideas about how to properly handle domains in the absence of centralized administration, but for now and the near future we have to deal with the domain as it exists in the current firmware.

73
ad5oo

Just a note to anyone else playing with these - I was able to get OLSRD working and talking to my WRT54G nodes, using the development HSMM-MESH firmware on the WRT's.  I compiled the 0.6.3 version but there is a 0.6.2 package that may work as well.  I'm using a realtek based wifi dongle and it is running okay (so far) from the USB on board, not running a powered hub.  I don;t have a keyboard or mosue hooked up, either, though, coming in via ethernet, so that may help the power equation.

Howdy stranger, you might want to consider joining the developers Yahoo! Group.

I have two Linysys WRT54G3G-ST routers with firmware changed to hsmm-mesh.

Both have been previously tested and worked fine and saw each other.

I changed the login & password on each and that info was duly stored on the two laptops.

I was trying to connect a TRENDnet IP camera so I fired them up but cannot get into Setup.

Neither router remembers the new login & password nor do they recognize the default open-wrt login & password.

I was planning to use these for a project that starts tomorrow.

What do I do, please?

Thanks!

PLEASE DISREGARD:  Found this:

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

Hi All,

Newbie to HSMM-Mesh from Australia (looks like that makes two of us now!). I've managed to flash a WRT54GL (waiting on a 2nd to start a mesh). Was wondering:

1. If there is no security then how is the network secured from unauthorised access? (Australian regs are different (however there are similarities) but it would appear from my reading that FCC Part 97 requirements dictate that Part 15 users can't get into the system).

2. The default domain appears to be austin.tx.us.mesh.  How do we change that (say to sydney.nsw.au.mesh) for consistency with the nominal naming convention? Would this 'break' anything in the mesh? (keeping the SSID as HSMM-MESH).

73,

Cameron

I'm looking to set a node up -- I could set one up in San Jose and perhaps in Cupertino.  Is there much of a point?  Would I be able to reach anyone else in the area, or would I just be placing my dots on the map in the hopes of enticing someone to fill in some of the open spaces? :)

Is this project in active development?  Is there some place where people discuss patches, bugs, wanted features, etc?

If I wanted to take a stab at helping, where would it be most useful?  Implementing new features, fixing old bugs?  Porting to new hardware (maybe Atheros-based devices), or moving files to USB storage to better support newer, more easily available 2MB devices?

There are plenty of newer routers that can be used for this, if the firmware could be made to work on them; I really don't want to have to resort to using DD-WRT mesh firmware (and having to hack it up if it's not compatible with HSMM-Mesh) to use this particular router for experimentation. I will use it (DD-WRT) for the wireless bridging capabilities it provides, though.

The WRT54GL is still for sale, new, on ebay.  So they are not hard to find.  You could save your self a huge amount of time starting with supported hardware.  Working with a WRT54G v8 would be a challenging project for someone with expert hardware and software skills.  If you get it working, let is know how you did it. 

The HSMM-MESH firmware will not fit in the native memory of a WRT54 v8.  There is no easy way to "leave stuff out" to try to make it fit.  If you can't get the firmware image loaded, you can't boot it.

If you want to try get a taste of trying to work with minimal foot print 3rd party firmware in newer Linksys routers, check out dd-wrt for ideas on how one might try.  We do not have a method for loading working HSMM-MESH firmware into a WRT54G v8.

-Glenn

KD5MFW