Install A1200P With Trixbox-2.2

A1200P-Trixbox-2.2 Installation Guideline
Written By James.Zhu
Version 0.1
Date:04/08/2007

This instruction is to provide a step-by-step guideline to users who want to install OpenVox ( www.openvox.com.cn ) A1200P into Trixbox-2.2. There are few steps, which users must follow:

1. Preparing the installation
1) About A1200P
A1200P is a modular analog telephony interface product. It is designed to be the small to middle business PBX usage. Each A1200P can have up to 12 ports per card, and user can install 4 pcs of A1200P in one PC to get 48 ports.

A1200P must be used with FXO-100 or FXS-100 together to build a workable system. The FXO-100 and FXS-100 module are also pin to pin compatible with X100M and S100M. The A1200P has 3 RJ45 sockets on the bracket. Each jack has 4 corresponding module installation positions on the motherboard.

Each RJ45 socket has 8 pins. A1200P uses the 2 pins of it as a pair to connect to you 2-wire telephone line, so Each RJ45 socket can connect 4 telephone lines.

2) Stop Asterisk and zaptel in Trixbox
Before installing new zaptel and Asterisk, user must stop Asterisk and zaptel in Trixbox.

3) Choose right versions of kernel-devel, Asterisk and zaptel
User must make sure that you have installed kernel-devel in the system. To check the kernel-devel, user can run the command: rpm –q kernel-devel.
If there is no kernel-devel, please run this command: yum install kernel-devel.

In this test environment, I try to use the version of Asterisk and zaptel same as Trixbox-2.2 has. Here, I use asterisk-1.2.18 and zaptel-1.2.18：

2. Downloading new A1200P driver, zaptel and Asterisk packages
To run A1200P in Trixbox, please download the a1200p driver, zaptel-1.2.18 and Asterisk-1.2.18. User can go to these websitesto download
2.1) www.openvox.com.cn/members_downloads.php
2.2) downloads.digium.com/pub/asterisk/releases/
2.3) downloads.digium.com/pub/zaptel/releases/
After downloading, copy the three packages into /usr/src directrory.

3. Unzip and installing zaptel and Asterisk packages.
3.1) In the directory /usr/src, run the command to unzip the files
tar –zxvf zaptel-1.2.18.tar.gz and tar –zxvf asterisk-1.2.18.tar.gz

3.2) Copy opvxa1200.c source file into /usr/src/zaptel-1.2.18。

3.3) Modify /usr/src/zaptel-12.1.8/Makefile:
a) Find the line start with Modules=
b) Add opvxa1200 in it. Makefile likes this
Before modify:
MODULES=zaptel tor2 torisa wcusb wcfxo wctdm wctdm24xxp \
ztdynamic ztd-eth wct1xxp wct4xxp wcte11xp pciradio \
ztd-loc # ztdummy



After modified
MODULES=zaptel tor2 torisa wcusb wcfxo wctdm wctdm24xxp \
ztdynamic ztd-eth wct1xxp wct4xxp wcte11xp pciradio \
opvxa1200 \
ztd-loc # ztdummy
c) Find the line: wctdm.o: zaptel.h wctdm.h
d) After this line, add another new line: opvxa1200.o : zaptel.h wctdm.h
e) Save the changes and compile the zaptel driver:
make clean, make and make install. If errors occurred during compiling zaptel such as lock error in zaptel-base.c and torisa.c, please edit the two files by follow steps.

Using vi to open zaptel-base.c and go to line around 307, comment the lines like this:

/* #ifdef DEFINE_RWLOCK
static DEFINE_RWLOCK(zone_lock);
static DEFINE_RWLOCK(chan_lock);
#else */
static rwlock_t zone_lock = RW_LOCK_UNLOCKED;
static rwlock_t chan_lock = RW_LOCK_UNLOCKED;
/* #endif */



Using vi to open file torisa.c, go to line 306, edit the line like this:

/*#ifdef DEFINE_RWLOCK
static DEFINE_RWLOCK(torisa);
#else */
static rwlock_t torisa = RW_LOCK_UNLOCKED;
/* #endif */



After changing the files, use should compile the zaptel without errors.
After compiling zaptel, user can compile asterisk.

Under /usr/src/asterisk-1.2.18, run the command: make clean, make and make install. Please do not run the command install samples, otherwise, the asterisk comfig files under /etc/asterisk will be overwritten and asterisk will lose connection with Trixbox.

4. Modifying the setting to support auto-load zaptel and opvxa1200 drivers after rebooting system.
First, user opens the file called zaptel under /etc/init.d, vi the zaptel file and edit it like this:
if [ -z "${MODULES}" ]; then
# Populate defaults if not present
MODULES="tor2 wct4xxp wct1xxp wcte11xp wcfxo wctdm opvxa1200"
#MODULES="ztdummypll"
fi

Second, user opens the zaptel under /etc/sysconfig, open the zaptel and add extra line:
MODULES="$MODULES opvxa1200" # OpenVOx A1200P

5. Modify the genzaptelconf file from /usr/local/sbin directory
In order to detect A1200P by using the command:genzaptelconf from trixbox, user has to edit the file and add the follow parts in genzaptelconf.

do
# in case this is a real channel.
chan_num=`echo $line |awk '{print $1}'`
case "$line" in
*WCT1/*) # we're yet to detect when a channel is active
echo "$rem_char channel $chan_num, WCT1, unhandled for now"
;;
*WCTDM/*)
# this can be either FXS or FXO
check_tdm_sigtype $chan_num fxs $mode || \
check_tdm_sigtype $chan_num fxo $mode || \
echo "$rem_char channel $chan_num, WCTDM, inactive."
;;
*OPVXA1200/*)
# this can be either FXS or FXO
check_tdm_sigtype $chan_num fxs $mode || \
check_tdm_sigtype $chan_num fxo $mode || \
echo "$rem_char channel $chan_num, OPVXA1200, inactive."
;;
*WCFXO/*)
check_tdm_sigtype $chan_num fxo $mode || \
echo "$rem_char channel $chan_num, WCFXO, inactive."
;;
......
6. Testing the system
Alternatively, to test the system, please stop asterisk and run the command under /usr/src/zaptel-1.2.18/xpp/util/./genzaptelconf -d. it will automatically detect your A1200P and generate the zaptel.conf under /etc. here, there are five FXS modules in A1200P, the zaptel.conf has such information:
# Span 1: OPVXA1200/0 "OpenVox A1200P Board 1"
fxoks=1
fxoks=2
fxoks=3
fxoks=4
fxoks=5
# Global data
loadzone = us
defaultzone = us




Zapata.conf has these parameters:
;
; Zapata telephony interface
; Configuration file
[trunkgroups]
[channels]
language=en
signalling=fxo_ks
context =demo
;rxwink=300 ; Atlas seems to use long (250ms) winks
; Whether or not to do distinctive ring detection on FXO lines
;usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no
group = 2
channel=>1-5
;faxdetect=both
;faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

Testing Trixbox in three different ways:
1) If the zaptel and opvxa1200 load successfully, user can run asterisk console by:
asterisk -r
2） access URL to see asterisk
3) User also can view the log message by opening /var/log/message:
vi /var/log/messages

6. Notices and Troubleshooting
A. Maybe, some new versions of zaptel and asterisk have little changes in compilation. User must adjust accordingly based on the user manual.

B. The test environment is trixbox-2.2 environment, if you want to test under old version of Trixbox, please read the documentation of that version.


C. If the zaptel and opvxa1200 drivers could not load automatically during system booting, most probably, user have to check the zaptel file from /etc/init.d and etc/sysconfig and add opvxa1200 module.

D. If you have other problems with A1200P, please post your questions to the forum of OpenVox ( www.openvox.com.cn/bbs/ ). Our technical staffs will give you assistance.

E. If any step is missing, please report your information to OpenVox forum.

after you finished the steps listed above, please follow the link below to modify the genzaptelconf file, so the system will always generate correct setup.

www.openvox.com.cn/bbs/viewtopic.php?t=43

to make genzaptelconf work with A1200P, I edit the code in genzaptelconf in
www.openvox.com.cn/bbs/viewtopic.php?p=321#321 .
Regards!
James.zhu

I have the next problem with the install the openvox a1200p in trixbox pro.

Trixbox pro SE v2.05
Version zaptel 1.2.22.1-1
version asterisk 1.2.26.1-48

I run the command make clean, but the other one, the command make, can not run correctly. The mistakes are:

.....
make[1]: Entering directory `/usr/src/kernels/2.6.9-42.EL-smp-i686'
CC [M] /usr/src/zaptel-1.2.18/zaptel-base.o
/usr/src/zaptel-1.2.18/zaptel-base.c:188: warning: 'fcstab' defined but
not used
LD [M] /usr/src/zaptel-1.2.18/zaptel.o
CC [M] /usr/src/zaptel-1.2.18/tor2.o
CC [M] /usr/src/zaptel-1.2.18/torisa.o
CC [M] /usr/src/zaptel-1.2.18/wcusb.o
CC [M] /usr/src/zaptel-1.2.18/wcfxo.o
CC [M] /usr/src/zaptel-1.2.18/wctdm.o
CC [M] /usr/src/zaptel-1.2.18/wctdm24xxp.o
CC [M] /usr/src/zaptel-1.2.18/ztdynamic.o
CC [M] /usr/src/zaptel-1.2.18/ztd-eth.o
/usr/src/zaptel-1.2.18/ztd-eth.c:189: warning: initialization from
incompatible pointer type
CC [M] /usr/src/zaptel-1.2.18/wct1xxp.o
CC [M] /usr/src/zaptel-1.2.18/wcte11xp.o
CC [M] /usr/src/zaptel-1.2.18/pciradio.o
CC [M] /usr/src/zaptel-1.2.18/ztd-loc.o
CC [M] /usr/src/zaptel-1.2.18/wcte12xp.o
make[2]: *** No rule to make target `/usr/src/zaptel-1.2.18/opvxa1200.c',
needed by `/usr/src/zaptel-1.2.18/opvxa1200.o'. Stop.
make[1]: *** [_module_/usr/src/zaptel-1.2.18] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.9-42.EL-smp-i686'
make: *** [all] Error 2


I appreciate any collaboration

hi:
could you edit the makefile for a1200.c, please edit as what the user manual shows you. if you use zaptel1-2.XXX, please use this a1200.c for zaptel1.2. the url is:
www.openvox.com.cn/bbs/viewtopic.php?p=1181#1181 .
regards!
james.zhu

lspci command display:
Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface

so the 1200p can't work .

please help me.

thanks!