OpenVox FB40 user manual
From Wiki
Contents |
Chapter 1 Overview
In most of the time, users need to reconnect the BRI line to a redundant server maintained by UPS when main PBX Server is power off. It may cause a little extra work for people who use simple and small PBX servers. But for those who run complex PBXs in server rooms, it becomes real problems.
How to eliminate this problem? The release of OpenVox FB40 failover box for BRI answers it. The FB40 can automatically switch the BRI line to the redundant server when the power of the main PBX server has been cut off and will automatically switch back to normal when the power is on again. In this way, no more worries about getting the BRI line connected to the redundant server when the main server is down.
FB40 is controlled through an Asterisk loadable module res_failover.so. This module keeps sending “running” signal to redundant server when Asterisk is running. Once Asterisk is down or system power is cut off, the module will not be able to send out the “running” signal to FB40 and thus FB40 will automatically switch to the redundant server.
FB40 provides a reliable and flexible solution to Asterisk PBX.
Chapter 2 Features
Easy installation;
Uses USB to connect computer or server;
Industry standard USB type B connector;
USB 2.0 and 1.1 compliant;
Low power consumption, takes power from USB bus;
Standard length type A to type B cable provided;
Supports software watchdog;
Supports up to 4 ISDN BRI/PRI interfaces;
Supports multiple FB40 devices in one system;
Fully supports Asterisk (Version1.2/1.4/1.6;
Supports Elastix, Trixbox;
Small plastic enclosure: 285mm x 110mm x 34mm;
4 power supply indicator LEDs;
5 year warranty;
FB40 supports all OpenVox BRI cards, Digium, Sangoma BRI cards and other compatible BRI cards;
Chapter 3 Installation Guide
Hardware Connection
A FB40 allows connecting two BRI cards simultaneously. FB40 connects to the server by a USB, BRI cards are installed in the server. Besides the USB interface, there are another four groups of ports, every group includes a OUT1, a OUT 2 and IN port. If you have two servers and two BRI cards and a FB40, you can connect lines like that all OUT1 port connect the ports of a BRI card which is set up in the main server and all OUT2 port connect to another BRI card which is set up in the redundant server, IN ports connect to BRI network.
Device Driver Detection
The device driver of FB40 has been integrated with many Linix distributions. Users can run the following command to see whether the FB40 has been recognized or detected by the system. (Please connect the FB40 to the server with attached USB cable that comes together with the product. Note: Please make sure that all the LEDs are on by switching the on-of button when the FB40 is connected to the server.)
# dmesg | grep FTDI
User can also run the lsusb command to check whether the FB40 device is connected.
# lsusb
Working Principle
When the PBX Server is ON,the BRI signal goes from: BRI network -> IN port of FB40 -> OUT port of FB40 -> the port of Openvox BRI products which are set up in the main server.
When the main PBX Server stops working (poweroff) or the FB40 stops, the
BRI/PRI signal goes from:BRI network -> IN port of FB40 -> OUT port of FB40 which connects a BRI card -> the port of Openvox BRI products which are set up in the redundant server.
Software Installation
Software Download
# wget www.openvox.cn/download/drivers/failover/failover-1.0-current.tar.gz
Software Installation
You are able to choose a asterisk version to install.
Installation with asterisk 1.2.X
1) Unzip the file
# tar -xzvf failover-1.0-current.tar.gz # cd failover
2) Copy the file to res directory under asterisk
# cp res_failover.c $asterisksource/res/
3) Copy the configuration file to /etc/asterisk directory
# cp failover.conf /etc/asterisk/
4) Compile Makefile in res directory under asterisk
# vi /usr/src/asterisk/Makefile
5) Modify Makefile
MODS=res_indications.so res_monitor.so res_adsi.so res_agi.so res_features.so To: MODS=res_indications.so res_monitor.so res_adsi.so res_agi.so res_features.so res_failover.so
6) If asterisk is installed, please compile it and re-install
# cd $asterisksource # make # make install
7) Configure the /etc/asterisk/failover.conf file on requirements.
8) Reboot asterisk.
Installation with asterisk 1.4.X
1) Unzip the file
# tar -xzvf failover-1.0-current.tar.gz # cd failover
2) Copy the file to res directory under asterisk
# cp res_failover.c $asterisksource/res/
3) Copy the configuration file to /etc/asterisk directory
# cp failover.conf /etc/asterisk/
4) If asterisk is installed, please compile it and re-install
# cd $asterisksource # make # make install
5) Configure the /etc/asterisk/failover.conf file on requirements.
6) Reboot asterisk.
Installation with asterisk 1.6.X
1) Unzip the file
# tar -xzvf failover-1.0-current.tar.gz # cd failover
2) Copy the file to res directory under asterisk
# cp res_failover.c $asterisksource/res/
3) Copy the configuration file to /etc/asterisk directory
# cp failover.conf /etc/asterisk/
4) If asterisk is installed, please compile it and re-install
# cd $asterisksource # make # make install
5) Configure the /etc/asterisk/failover.conf file on requirements.
6) Reboot asterisk.
Explanation of Configuration Files
[openvox_failover_1] device=/dev/ttyUSB0 ;kick_time_interval=4000 ;event_cmd=logger ;autorun=yes
[openvox_failover_2] device=/dev/ttyUSB1 kick_time_interval=500 event_cmd=logger autorun=no
[openvox_failover_1] ：Name of FB40 Device, to distinguish from different devices, a must to configuration;
device=/dev/ttyUSB0 ： Name of USB device that FB40 uses, a must to configuration;
kick_time_interval：the time interval of software watch dog; the default time is 4000ms, user can customize the time with 100ms for Minimum and 9000ms for Maximum;
event_cmd：event command, the default is logger, it will record the FB40 status in system log;
autorun：this decides if FB40 will start when asterisk boots; the default is yes which means the FB40 starts when asterisk boots; if no, the FB40 will not start when asterisk boots and user may need manually boot the device by running failover start command.
Steps to Use
1) Start asterisk
# asterisk –vvvgc
2) Start FB40 device
*CLI> failover start # This command can start all the FB40 devices. *CLI> failover start 1 # This command can be use to start the first FB40.A difference number means to start a specific FB40 in the server.
3) Stop FB40 device
*CLI> failover stop # This command can stop all the FB40 devices. *CLI> failover stop 1 # This command can be use to stop the first FB40.A difference number means to stop a specific FB40 in the server.
4) Show FB40 device information
*CLI> failover show # Show FB40 device information
5) Reload FB40 device configuration file
*CLI> failover stop # All the FB40 device must be stopped before reloading the configuration file *CLI> failover reload # Reload the configuration file
Software Installation by the res_failover.so
If you do not have the gcc compiler and the source code of the asterisk, you can also download the res_failover.so and use it directly as below.
1) Download res_failover.so
Check the asterisk version
# asterisk –V
Download the suitable version from
http://www.openvox.cn/download/drivers/failover/
2) Unzip the file
# tar -xzvf res_failover-1.X.X.so-for-asterisk-1.X.X.tar.gz # cd res_failover-1.X.X.so-for-asterisk-1.X.X
3) Copy the so module file to /usr/lib/asterisk/modules
# cp res_failover.so /usr/lib/asterisk/modules
4) Copy the configuration file to /etc/asterisk directory
# cp failover.conf /etc/asterisk/
5) Configure the /etc/asterisk/failover.conf file on requirements.
6) Reboot asterisk.
Chapter 4 Reference
www.openvox.cn
www.digium.com
www.asterisk.org
www.voip-info.org
www.asteriskguru.com
