OpenVox A400E User Manual for zaptel
From Wiki
Contents |
A400E User Manual
Chapter 1 Overview
1. What is A400E
A400E is a modular analog telephony interface product. It is designed to be the small to middle business PBX usage.
A400E series must be used with FXO-100 or FXS-100 together to build a workable system. The FXO-100 and FXS-100 modules are also pin to pin compatible with X100M and S100M.
Key Benefits:
1) Scalable: just add additional cards to extend system
2) Support PCI-Express
RoHS compliant
Certificates: CE, FCC
trixbox Officially Certified
Disclaimers Asterisk is a registered trademark of Digium, Inc.
Misc
1) Temperature Operation: 0 to 50°C
2) Temperature Storage: - 40 to 125°C
3) Humidity:10 TO 90% NON-CONDENSING
4) Voltage:3.3/12V,3REN
5) Power Dissipation Max:2.06W/11.6W
2. What is Asterisk
The Definition of Asterisk is described as follow:
Asterisk is a complete PBX in software. It runs on Linux, BSD,Windows (emulated) and provides all of the features you would expect from a PBX and more. Asterisk does voice over IP in four protocols, and can interoperate with almost all standards-based telephony equipment using relatively inexpensive hardware. Asterisk provides:
2.1) Voicemail services with Directory
2.2) Call Conferencing
2.3) Interactive Voice Response
2.4) Call Queuing
2.5) Three-way calling
2.6) Caller ID services
2.7) ADSI, IAX, SIP, H.323, MGCP and SCCP/Skinny
Chapter 2 Software Installation and Configuration
1. Hardware Installation and Setup
A400E uses the 2 pins of it as a pair, to connect to your 2-wire telephone line(RJ11). If the card equips with a FXS, please plug in the power supply cable into power supply connector and connecting PSTN line into FXO port and telephone into FXS.
2. Software Installation and Setup
A400M supports zaptel software device driver on Linux. To use A400M, user should install zaptel and asterisk. Before installing zaptel and asterisk, please make sure that some supporting packages have been installed.
Note that if there is no kernel source in the system, user should install them. User can run yum again: yum install kernel-devel. It is time to check for the availability of some supporting packages:
rpm -q bison rpm -q bison-devel rpm -q ncurses rpm -q ncurses-devel rpm -q zlib rpm -q zlib-devel rpm -q openssl rpm -q openssl-devel rpm -q gnutls-devel rpm -q gcc rpm -q gcc-c++
If some packages are not installed, please install them by using yum to install
yum install bison yum install bison-devel yum install ncurses yum install ncurses-devel yum install zlib yum install zlib-devel yum install openssl yum install openssl-devel yum install gnutls-devel yum install gcc yum install gcc-c++
Attention：if you found J914（input）and J915（output）interfaces on the card, it means the card support clock line, for the detail information, please refer to the following link：
http://bbs.openvox.cn/viewthread.php?tid=874&extra=page%3D1
User can install the driver via the following steps (assuming user has the source code of zaptel device driver installed in /usr/src/zaptel-1.4.XX directory):
1) Checking the A400E hardware by command: lspci –vvvvv
00:0c.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Subsystem: Unknown device 9100:0001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (250ns min, 32000ns max) Interrupt: pin A routed to IRQ 185 Region 0: I/O ports at b800 [size=256] Region 1: Memory at febfe000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
User can see that there is a Tiger Jet chip base device.
2) Downloading and compiling
please go to asterisk offical website to download asterisk and zaptel.
please note, get a right combination of asterisk and zaptel
3) executing the commands under /usr/src/zaptel-1.4.XX,
./configure make make install make config
4) Installing asterisk
cd /usr/src/asterisk-1.4.XX ./configure make make install make samples // it is first time to install the system, run that.
5) Detecting and loading modules for wctdm
run command: genzaptelconf –sdvM
The command will automatically generate the zaptel.conf under /etc
After loading zaptel and wctdm driver, user should check the zapata.conf and zapata-channels.conf, make sure the zapata-channels.conf has been included into zapata.conf. Make sure that the context in zapata-channels.conf should exists in extensions.conf
# Span 1: A400P fxsks=1 fxsks=2 fxoks=3 fxoks=4 # Global data loadzone = us defaultzone = us
the zapata.conf and zapata-channels.conf under /etc/asterisk for you:
[trunkgroups] [channels] context=from-pstn signalling=fxs_ks rxwink=300 ; Atlas seems to use long (250ms) winks usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=no faxdetect=incoming echotraining=800 rxgain=0.0 txgain=0.0 callgroup=1 pickupgroup=1 ;Uncomment these lines if you have problems with the disconnection of your analog lines ;busydetect=yes ;busycount=3 immediate=no #include zapata_additional.conf #include zapata-channels.conf
signalling=fxs_ks callerid=asreceived group=0 context=from-pstn channel => 1 context=default signalling=fxs_ks callerid=asreceived group=0 context=from-pstn channel => 2 context=default signalling=fxo_ks callerid="Channel 3" <6003> mailbox=6003 group=5 context=from-internal channel => 3 callerid= mailbox= group= context=default signalling=fxo_ks callerid="Channel 4" <6004> mailbox=6004 group=5 context=from-internal channel => 4 callerid= mailbox= group= context=default
But be sure, sometimes, due to some reasons, it can not work perfectly. Please check the setting of zaptel.conf, if user changes something in zaptel.conf, you can use these commands to reload the driver again:
modprobe zaptel modprobe wctdm ztcfg –vvvv
6. Starting asterisk and test calls
Checking the zap channel loading from asterisk console:
asterisk –vvvvvvvgc
Entering asterisk console, run command: zap show channels. If user can see the zap channels, which means the zap channels have been loaded into asterisk.
zhu*CLI> zap show channels
Chan Extension Context Language MOH Interpret
pseudo default default
1 from-pstn default
2 from-pstn default
3 from-internal default
4 from-internal default
User must make sure that the context "from-pstn" and "from-internal" are in extensions.conf, here an example is given:
[from-pstn] exten => s,1,Answer() // answer the inbound call exten => s,n,Playback(cc_welcome) // please mesaage exten => s,n,Hangup() [from-internal] exten => 200,1,Dial(zap/1/outgoing_number) // dial 200 to dialout from zap 1 exten => 200,2,Hangup
Test environments are:
Centos-5.0 Kernel version: 2.6.18-8.el5 Zaptel: 1.4.12.1 Asterisk: 1.4.20.1 Hardware: OpenVox A400E
Some problems with compiling A400E have been summarized and documented into FAQ of A400E; please check that under A400E categories.
Chapter 3 Reference
www.openvox.com.cn
www.digium.com
www.asterisk.org
www.voip-info.org
www.asteriskguru.com
