OpenVox A1200P Asterisk 1.8 Dahdi en
From Wiki
Contents |
OpenVox A1200P User Manual for Asterisk 1.8 on Dahdi
Chapter 1 Overview
Features
- A1200P is a modular analog telephony interface product. It is designed to be the small to middle business PBX usage. For example, 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 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.
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.3V,5V
5. Power Dissipation Max:1.7W,6W
Key Benefits
- Low CPU Payload : below 25% with 8 PCs of A1200P(96 ports) after driver installed, on a Celereon D 2.53Ghz
- Scalable: just add additional cards to extend system
- Be easy to use: module Pin to Pin compatible with Digium’s X100M and S100M. User can use diguim's X100M/S100M module on this card, or use our FXO-100/ FXS-100 Module on TDM400P
- Excellent choice of upgrade Digium’s TDM400P based Asterisk system to A1200P, achieving 96 ports density or more in one PC, and protecting user investment by directly making use of user investment on modules of TDM400P
- RoHS compliant
- Certificates: CE, FCC, A-Tick
- trixbox Officially Certified
- elastix Officially Certified
What is Asterisk
- 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:
- Voicemail services with Directory
- Call Conferencing
- Interactive Voice Response
- Call Queuing
- Three-way calling
- Caller ID services
- ADSI, IAX, SIP, H.323, MGCP and SCCP/Skinny
Chapter 2 Software Installation and Configuration
Step 1: Hardware Installation and Setup
A1200P series has 3 RJ45 sockets for A1200P on the bracket. There are 4 corresponding modules supported on each jack on main motherboard.
There are 8 pins on the each RJ45 socket. A1200P series uses the 2 pins of it as a pair, to connect to your 2-wire telephone line, so each RJ45 socket can connect 4 telephone lines. User has to use a splitter (refer figure 4 in pdf) to connect RJ11 normal telephone line. 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.
Step 2: Software Installation and Setup
A1200P series supports zaptel software device driver on Linux. To use A1200P, user should install Dahdi and asterisk.
Get all necessary software package
A1200P series device driver is a signal file named opvxa1200.c. It can be downloaded from http://downloads.openvox.cn/pub/drivers/dahdi-patches/a800p_a1200p/opvxa1200.c
Before installing Dahdi 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 dahdi device driver installed in /usr/src/ directory):
1） Check hardware
Checking the A800P/A1200P 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 based device.
2) Downloading and compiling
2.1. Please go to www.asterisk.org to download asterisk-1.8.XX, dahdi-linux-complete-XX and unzip the files to /usr/src
2.2. Copy opvxa1200.c to /usr/src/dahdi-linux-complete-xx/linux/driver/dahdi/.
2.3. Open Kbuild under /usr/src/dahdi-linux-complete-xx/linux/driver/dahdi/.
2.4. Find the line: obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTDM) += wctdm.o
2.5. Add a new line after that line: obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTDM)+= opvxa1200.o, the file looks like this:
obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCT4XXP) += wct4xxp/ obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTC4XXP) += wctc4xxp/ obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTDM24XXP) += wctdm24xxp/ obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTE12XP) += wcte12xp/ obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTDM) += wctdm.o obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTDM) += opvxa1200.o // this is for a1200/a800p obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCT1XXP) += wct1xxp.o obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTE11XP) += wcte11xp.o
2.5. compile dahdi-linux-complete-XX change directory to /usr/src/dahdi-linux-complete-xx, under that directory, run:
make make install make config
3. Installing asterisk
change directory to /usr/src/asterisk-1.8.XX, run:
./configure make make install make samples
4. Detecting and loading modules for opvxa1200:
run command: dahdi_genconf, the command will automatically generate the /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf.
Note: the dahdi-channels.conf should be included in /etc/asterisk/chan_dahdi.conf
if not, please run a command to include that file:
echo "#include dahdi-channels.conf" >> /etc/asterisk/chan_dahdi.conf
system.conf will be like this:
# Span 1: OPVXA1200/0 "OpenVox A1200P Board 1" (MASTER) fxsks=1 fxsks=2 fxoks=3 fxoks=4 echocanceller=mg2,1-4 # channel 5, WCTDM, no module. # channel 6, WCTDM, no module. # channel 7, WCTDM, no module. # channel 8, WCTDM, no module. # channel 9, WCTDM, no module. # channel 10, WCTDM, no module. # channel 11, WCTDM, no module. # channel 12, WCTDM, no module. # Global data loadzone = cn ; please change to your COUNTRY defaultzone = cn ; please change to your COUNTRY
edit asterisk/indications.conf：
country = cn
chan_dahdi.conf:
[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 disconection of your analog lines ;busydetect=yes ;busycount=3 immediate=no #include dahdi_additional.conf #include dahdi-channels.conf
dahdi-channels.conf
; Span 1: OPVXA1200/0 "OpenVox A1200P Board 1" (MASTER) ;;; line="1 OPVXA1200/0/0" signalling=fxs_ks callerid=asreceived group=0 context=from-pstn channel => 1 context=default ;;; line="2 OPVXA1200/0/1" signalling=fxs_ks callerid=asreceived group=0 context=from-pstn channel => 2 context=default ;;; line="3 OPVXA1200/0/2" signalling=fxo_ks callerid="Channel 3" <6003> mailbox=6003 group=5 context=from-internal channel => 3 callerid= mailbox= group= context=default ;;; line="4 OPVXA1200/0/3" signalling=fxo_ks callerid="Channel 4" <6004> mailbox=6004 group=5 context=from-internal channel => 4 callerid= mailbox= group= context=default
5. Load the driver by these commands:
modprobe dahdi ; load dahdi driver modprobe opvxa1200 opermode=YOUR COUNTRY; load the a1200/a800 driver with your country dahdi_cfg –vvvv ; start channels
6. Starting asterisk and test calls
Checking the dahdi channel loading from asterisk console:
asterisk –vvvvvvvgc
Entering asterisk console, run command: dahdi show channels. If user can see the dahdi channels, which means the dahdi channels have been loaded into asterisk.
zhu*CLI> dahdi 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 an inbound call exten => s,n,Playback(cc_welcome) // please a message exten => s,n,Hangup() [from-internal] exten => 200,1,Dial(dahdi/1/outgoing_number) // dial 200 to dialout from dahdi channel 1 exten => 200,2,Hangup
Test environments are:
Centos-5.5 Kernel version: 2.6.18-194.el5 dahdi-linux-complete: 2.3.0.1+2.3.0 Asterisk: 1.8.0 Hardware: OpenVox A1200P
Some problems with compiling A1200P have been summarized and documented into FAQ of A1200P; please check that under A800P/A1200P categories.
Chapter 3 Reference
www.openvox.com.cn
www.digium.com
www.asterisk.org
www.voip-info.org
www.asteriskguru.com
