open source with FXO

15 views
Skip to first unread message

roadwarriorvpn.com

unread,
Dec 2, 2009, 12:25:58 PM12/2/09
to village-telco-dev
I am excited to see small and relatively cheep device that includes a
FXO. I am not sure what type of os this device will be running, but I
would really like it to be able to run OpenVPN on the device in order
to secure the SIP stream and to also make it possible to still make
calls from within countries that block SIP. So hopefully people who
are located in countries where SIP is not allowed can sill make calls
as they with wish.

I really like how SNOM introduced OpenVPN info their phone. Basically
when ever you want to load anything onto the phone you give it a URL.
In order to load the config files onto the phone you supply it a URL
to a .tar file. the phone then down loads the .tar and un tar's it on
the phone. I would be happy to help set up something similar.


I know that the board layout is pretty much set, but considering that
applications that this little device could be applied to I think it
would be a great addition if the device could accept POE. Expeshially
since yet another power brick is is no fun.

David Rowe

unread,
Dec 2, 2009, 3:29:25 PM12/2/09
to village-...@googlegroups.com
> I am excited to see small and relatively cheep device that includes a
> FXO.

Actually it's an FXS port - which you plug an analog telephone into. An
FXO port is used to connect to a PSTN telephone line.

The Mesh Potato runs Linux under OpenWRT, so there is probably some
OpenVPN support in there. CPU load may be an issue, but it would
probably be OK for light loads.

The Mesh Potato supports PoE and Power-over-telephone-Line, i.e. you
only really need to connect a 4 wire analog phone cable and supply power
over the spare pair in the phone cable. So if it's mounted on a roof
you just need one cable for the phone & power.

Re PoE in practice I don't use the Ethernet port much. Once it's mesh
networked it's much more convenient to connect via wireless.

Cheers,

David
> --
>
> You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
>

Dan Wilbanks

unread,
Dec 2, 2009, 11:58:41 PM12/2/09
to village-...@googlegroups.com
David,

Could the Ethernet port be used to acquire a simple image from a camera/other device?

Thanks,

Dan

Corinna Elektra Aichele

unread,
Dec 3, 2009, 4:35:04 AM12/3/09
to village-...@googlegroups.com
Hello Dan -

> Could the Ethernet port be used to acquire a simple image from a
> camera/other device?

Are you thinking about acquiring images from a IP camera?

The MP is capable to act as a mesh network / Internet uplink, but since our
primary aim is to provide a maximum number of VOIP calls this is not the
default setup, as more data traffic in the mesh will reduce the number of calls.

By default the Ethernet port of the MP is not configured to act as a gateway to
the mesh network / Internet, but this can be changed easily by changing the MP
Ethernet subnet address and announcing the subnet via Batman HNA messages to
the mesh.

Cheers,
Elektra


Dan Wilbanks

unread,
Dec 3, 2009, 1:15:36 PM12/3/09
to village-...@googlegroups.com
Elektra,

I realize that might be out of the scope of the initial project, but it could be an important feature for remote health care (i.e sending an image of a wound or text based medical report). We used to send digitized x-rays over 2400 baud POTS in the early years (1983) of telemedicine, this could be a very similar benchmark. Keep up the good work,

Dan

Reply all
Reply to author
Forward
0 new messages