From: Ufo <ufo@rund.freifunk.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Mobile voice communication over mesh networks
Date: Tue, 14 Oct 2014 14:39:53 +0200 [thread overview]
Message-ID: <543D1999.4050601@rund.freifunk.net> (raw)
In-Reply-To: <D05D5F01.15409%david.moffatt@nokia.com>
thank you. nice list, but mostly the details about used techniques are
not mentioned. most of the systems are using central servers and have
commercial business plans. so that was not the task on this thread.
with *mumble* you can at least install your own server, even on openwrt,
and its open source..
but, best app on your list might be the *pttdroid*
https://play.google.com/store/apps/details?id=ro.ui.pttdroid
its a very simple app which needs NO server! so within our batman-adv
networks its running nice, without any configuration needed :-o
p.s. even when you are alone on your mesh it seems to be a nice app for
debugging purposes, because you can create broadcast- and multicast
usertraffic very easy..
Am 10.10.14 19:02, schrieb david.moffatt@nokia.com:
>
> http://lmgtfy.com/?q=push+to+talk+androidOn
>
> :-)
>
> 10/9/14, 10:12 PM, "ext tjhowse" <tjhowse@gmail.com> wrote:
>
>> Has anyone looked into either a piece of hardware or a smarphone app
>> that would allow for functionality similar to CB radios but over a
>> wifi mesh fabric?
>
--
---
Freifunk Leipzig http://leipzig.freifunk.net
prev parent reply other threads:[~2014-10-14 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 5:12 [B.A.T.M.A.N.] Mobile voice communication over mesh networks tjhowse
2014-10-10 8:36 ` Ufo
2014-10-10 17:02 ` david.moffatt
2014-10-14 12:39 ` Ufo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543D1999.4050601@rund.freifunk.net \
--to=ufo@rund.freifunk.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox