Jump to: navigation, search

Terry G

Introduction

Welcome to the VillageTelco Wiki. This site contains documentation on various aspects of Village Telco technology and operation.


The original VillageTelco work was to develop and deliver economical community telephony systems based on readily available WiFi technology.

This work resulted in the development of the Mesh Potato hardware device, a WiFi router that includes an Analogue Telephone Adapter circuit, and the VT series firmware based on Open Source software including OpenWrt (router and WiFi), Asterisk (telephony) and Batman (mesh networking protocol).

A number of relatively large scale VT network implementations have been undertaken in various places, notably Dili in East Timor and Bo-kaap and Kranshoek in South Africa.

For information on the original Village Telco work see the following document: Background


Later work has resulted in the development of the Small Enterprise Campus Network (SECN) firmware which runs on the Mesh Potato and various commercially available WiFi router devices from TP Link and Ubiquity.

This system is intended to provide both voice and data networking for smaller scale networks. The SECN firmware is also based on OpenWrt and Asterisk, but uses a later version of the mesh networking protocol known as Batman-adv.


The Batman software is no longer under active development and similarly the VT firmware is now deprecated and also not under active development. The replacement Batman-adv software is under very active development with a large project team. See http://open-mesh.org for details.


If you're interested in learning more about actual Village Telco deployments, have a look at the Deployments section of the Village Telco website.

Mesh Node Hardware

There's no vendor lock-in with Village Telco. While we do manufacture the Mesh Potato, we recognise that there are many excellent WiFi manufacturers and for some scenarios, other hardware may be desirable. Accordingly we produce a Village Telco firmware for Ubiquiti and TP-Link hardware. If you have another OpenWRT-compatible device that you would like to see the Village Telco firmware running, please get in touch

Mesh Potato

Mesh_Potato_(MP01)

MP02 (in development)

Ubiquity Devices

Ubiquity

Long Range Devices

TP Link Devices

TP Link

Mesh Node Firmware

Firmware Versions

Firmware Roadmap

VT Firmware

SECN 1.0 Firmware

SECN 1.1 Firmware

SECN 2.0 Firmware

SECN 2.1 Firmware

Build Environment

How To Set Up a SECN Build Environment

Server Options for Village Telco

In the past, Village Telco developed its own server solution which comprised Asterisk and A2Billing with a simplified UI for A2Billing as well as an installation wizard. We haven't been able to continuously update this software combination and it has to some degree now been eclipsed by other options. You can read more about it Archives/Village_Telco_Server of this wiki.

Voice Billing

Standalone

Cloud

Data Billing

Standalone

Mesh Network Monitoring

Not to be confused with standard networking monitoring tools like Munin, Nagios, Zabbix, and others, mesh monitoring tools measure the health of the mesh routes on the network. Some of them can do some of the monitoring that standard networking monitoring tools can do but the reverse is not true.

HowTo Guides

General

Classroom Router

Networking

Monitoring your Mesh Potato Network with Munin

Mesh_Gateway_Settings_and_Bridge_Loop_Avoidance

Optimizing dense meshes for call capacity and bandwidth

Testing Data Transfer Rates on a Mesh

SECN 1.1 Bridged Client Mode Operation

Hardware

Adding an external antenna

Adding a Reflector to the MP-01

Building a Serial Port for TL-WR703N

Using a 3G USB Modem with the TL WR703n

Installation

Installing VT SECN Firmware

Flashing a Ubiquiti Bullet M2HP with SECN

OpenWrt Failsafe Mode and Flash Recovery

Flashing the TL WR703n for the first time

Legal

G.729

Deployments

Other

How to contribute
Resources
Village Telco Documentation
Wireless Networks in the South

Archives

Other Projects

OpenBts

WIP Updates to this page - work in progress