Is there a preferred enclosure for a tripod mounted node (WRT54GL and antennas)?  I've heard about the Wiligear WOE-001 die cast hingled unit and the Orbit 57095 sprinkler system timer cabinet.  Does anyone have an opinion about these products, or other possibility? 

The doc mentions warning that appears, and that it can be ignored:
  [Oct 19 19:17:47] WARNING[427]: db.c:57 dbinit: Unable to open Asterisk database '/var/lib/asterisk/astdb': No such file or directory

If you just do a:
   mkdir -p /var/lib/asterisk

Then that "astdb" starts getting created, and the warning goes away.   No clue what that files for (I'mbrand new to asterisk), and it's binary so nothing obvious from vi.   The code must not try to make the directory, which would yield the "unable to open" message.

73!
--david
kj4izw

Great info, guys.  Yup, you're right about the G and GL. . . not enough space.  Guess I'll have to look for a GS to play with now.  Thanks.

73, Doug, K4EK

The doc mentions that the custom /etc/config/firewall settings may disappear.
That is why I built my own firmware to include the specified open ports. By doing it this way, I am able to get two-way audio.

So you need to open ports 5060, 5004, and 10000-20000 on the asterisk node and forward those ports to the IP address of an IP phone (if it's attached to a regular HSMM-MESH node). Opening the ports as specified in the instruction guide fixes the NAT'ing issue so you can make 2+ hour-long two-way phone calls over the HSMM-MESH network.

I'm glad you got it working!

I was able to follow the instructions and install on a WRT54GS (v1.1)!

The packages (deps + asterisk) require 2M free on /jffs partition ... So this effectively requires a WRT54GS (not G or GL).

The doc mentions that the custom /etc/config/firewall settings may disappear -- I found this to be the case whenever the mesh web UI was used to update ports/services.
However, I think you can just use the web UI to setup the ports for localnode, and then they will persist (and easier to see/self-documenting from that screen).  The web UI creates "forward" entries in /etc/config/firewall, not "accept" ...  This Was the cause of my one-way-audio issue in initial test.

Here's the setup i've tested with so far:
   VOIP Phone -> Mesh Node
   <mesh>
   Mesh Node:
       Asterisk
       WAN connected to home router (DLink DI-624) LAN port.
       OBI110 (ATA) connected to home router LAN port
           home phone (POTS) connected to OBI

BUT, I do have an issue with "one-way audio", which (from a quick google) seems to be a common problem due to the NAT'ing ... So I'll have to work on that -- probably an issue with going through my home router?? (but's all on internal LAN, so i'd expect it to be open)
Resolved!! See earlier edit in this post.

Waiting on a POE injector to come in the mail, then I can try with a second VOIP phone on a second mesh node ...  I suspect (hope!) that the one-way audio issue is not present with a totally intra-mesh setup.

--david
kj4izw

Very nice!  Gonna give this a try within the next couple days.  I have Asterisk running on a Raspberry Pi device now with decent success on the mesh.  Would be awesome to have it running natively on a WRT54G.  Thanks for the info.

73, Doug, K4EK

I have four routers, two gl's, two g's. Loaded firmware, did all the things in the instructions. OLSR is grayed out. I do not see any of the routers in the list. I have had the routers up to 30 feet apart and as close as 10 feet. No Joy. Where do I start to troubleshoot this issue?

Are there any living breathing people on this forum?  Someone could at the very least flame me, that's better than claiming plug and play and then offering no support.

Are you attempting to login to a WRT with the original Linkway firmware or logging in after you've entered your callsign and changed the password?

-KY9K