Homemade VoIP Network Over Wi-Fi Routers
AnInkle writes "A blogger on The Tech Report details his research and testing of wireless voice communication options for remote mountainous villages in rural undeveloped areas. The home-built project involves open-source software, low-cost wireless routers, solar power, mesh networking, unlicensed radio frequencies and VoIP technology. Although his research began several months ago, he has concluded the first stage of testing and is preparing to move near one of the sites where he hopes to eventually install the final functional network. Anyone with experience or ideas on the subject is invited to offer input and advice."
Wouldn't this be great! You could use your networking skills to setup a private, free telephone system. And, if it was encrypted, no one could snoop in on it... and if it was in an urban environment... Hmmm....
Read this yesterday, still don't get it. Can omni directional wifi ever compete with a cell tower's coverage range? Cellular has the advantage of insanely cheap commoditized phones.
Seems a bit like trying to use bluetooth to connect two buildings in a campus together - nominally cheap hardware, but probably cannot be coerced into doing what you seek.
David Rowe has been quite busy working on cool, low-cost telcomm stuff. His site also has links and comments and so forth from others interested in the subject, including people doing actual, in the field, deployments in fairly poor and hostile(to the tech) environments.
I've had a radio phone in a remote, mountainous region since the early 70's. Uptime is 100%. What goal must be achieved that can't be accomplished with older tech?
the two do not mix well, mountains will severely block radio waves from any part of the spectrum...
Politics is Treachery, Religion is Brainwashing
...when strategically placed can deal with that.
http://michaelsmith.id.au
I experimented with 5 units of WRT54G wireless routers running Freifunk firmware and I tried saturating the link with several G.729 VoIP calls. The system doesn't scale well. Over 3 hops, the number of calls greatly reduces as there is just too much random delay. In order for voice communication to be worthwhile, the latency cannot be more than 200ms although there are good forward error correction schemes and huge buffers.
Latency is a real problem especially when you are doing it over several hops. The "lag" isn't consistent. It will hit you at random interval, and that can be extremely irritating. This may be due to the use of CSMA/CA and RTS/CTS (depending on configuration). I haven't found a way to improve it though...
w00t
Anyone know what he's using for routing?
the option was this coop formed by advanced users.
The results on the shared T4, (yes, as in tee-four), are amazing and it's the fastest and most inexpensive, -at $30/month- internet access in town.
You just need to provide your own hardware,
The electric company down here had a wireless option a while ago (don't know if it still exists), where you got cellphone coverage plus normal licensed band 2-way radio in the same unit, meaning you could talk either with normal cellphone *or* push to talk direct to other subscribers and across their multi state network of repeaters.
OK- checked, still exists http://www.southernlinc.com/index.asp
ALOHA!
And now for some filler to get the filter to let me post.
-- What you do today will cost you a day of your life.
This brings me to a thought I have every time someone wants to know if they have enough bandwidth for voip. How much of h323, voip, etc.. is consumed to keep the whole accounting; pay per call, distance of call, who is calling, etc.. type stuff together? It seems to me a constant open stream where audio could traverse in any direction and any distance would not be that bandwidth intensive. Maybe I just don't understand everything involved.
Having to work for a living is the root of all evil.