keywords: ip pbx voip gateway gsm gateway

× Questions about A810/1610/2410 Advanced Analog Interface Card

A2410P/AE2410P_Dahdi_User_Manual

10 years 4 months ago #6049 by lisa.gao
A2410P/AE2410P_Dahdi_User_Manual

1 Hardware Setting
1. Checking power supply: Board must be provided power, please plug the power supply cable into power supply connector.
2. Splitting the RJ45 to RJ11: User has to use a splitter to split RJ45 interface to four RJ11 normal telephone line. And please connect PSTN line into FXO port and telephone into FXS port.

2 Software Installation and Configure
2.1 Download asterisk, dahdi, driver and firmware
1. Asterisk can be downloaded from:
http://downloads.asterisk.org/pub/telephony/asterisk/releases/

2. Dahdi can be downloaded from:
1) http://downloads.openvox.cn/pub/ ... .2.0.2+2.2.0.tar.gz
If user download dahdi from link 1, jump to 2.3

2) http://downloads.asterisk.org/pub/telephony/
If user downloads dahdi from link 2, please follow these steps.

3. Download A2410P/AE2410P driver from:
http://downloads.openvox.cn/pub/drivers/dahdi-patches/a2410p/opvxa24xx_dahdi-linux.tar.gz
copy the tar file to /dahdi-xx/linux/drivers/dahdi/

4. If user uses AE2410P, user should download firmware from:
http://downloads.openvox.cn/pub/firmwares/opvx-dahdi-fw-oct6114-032-1.07.01.tar.gz
tar –xzvf opvx-dahdi-fw-oct6114-032-1.07.01.tar.gz
cp dahdi-fw-oct6114-032.bin /lib/firmware/
mkdir /usr/lib/hotplug/firmware
mv dahdi-fw-oct6114-032.bin /usr/lib/hotplug/firmware


2.2 Edit the configure file
To edit the configure file, user must follow these steps:
1. Add opvxa24xx in /usr/src/dahdi-xx/linux/build_tools/live_dahdi
add opvxa24xx shown in red
MODULES_LOAD="$MODULES_LOAD xpp/xpp_usb"
;;
wctdm24xxp | wct4xxp | wcte12xp | wctc4xp | opvxa24xx)
MODULES_LOAD="$MODULES_LOAD $mod/$mod"

2. Add opvxa24xx in /usr/src/dahdi-xx/linux/drivers/dahdi/Kbuild
obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCT4XXP) += wct4xxp/
obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCT4XXP) += opvxa24xx/
obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCTC4XXP) += wctc4xxp/

3. Add opvxa24xx in /usr/src/dahdi-xx/linux/drivers/dahdi/Kconfig
config DAHDI_WCT4XXP
tristate "Digium Wildcard dual- and quad-T1/E1/J1 Support"
depends on DAHDI && PCI
default DAHDI
---help---
This driver provides support for the following Digium
Wildcard products:

* TE205/206/207/210/211/212P (PCI/PCI-X)
* TE220 (PCI-E)
* TE405/406/407/410/411/412P (PCI/PCI-X)
* TE420 (PCI-E)

To compile this driver as a module, choose M here: the
module will be called wct4xxp.

If unsure, say Y.

config DAHDI_OPVXA24XX
tristate "OpenVox 24 ports analog card Support"
depends on DAHDI && PCI
default DAHDI
---help---
This driver provides support for the following OpenVox
Wildcard products:
* A2410P (PCI)

To compile this driver as a module, choose M here: the
module will be called opvxa24xx.

If unsure, say Y.


4. Add opvxa24xx in /usr/src/dahdi-xx/linux/README
- wctdm:
* Digium TDM400P: up to 4 analog ports
- xpp: Xorcom Astribank: a USB connected unit of up to 32 ports
(including the digital BRI and E1/T1 modules)
- wcfxo: X100P, similar and clones. A simple single-port FXO card
- opvxa24xx:
* OpenVox A2410P: up to 24 analog ports


5. Add opvxa24xx in
/usr/src/dahdi-xx/tools/xpp/perl_modules/Dahdi/Hardware/PCI.pm
# from opvxa24xx
'1b74:2410' => { DRIVER => 'opvxa24xx', DESCRIPTION => 'OpenVox A2410P' },


# from wctdm24xxp
'd161:2400' => { DRIVER => 'wctdm24xxp', DESCRIPTION => 'Wildcard TDM2400P' },
'd161:0800' => { DRIVER => 'wctdm24xxp', DESCRIPTION => 'Wildcard TDM800P' },

6. Add opvxa24xx in /usr/src/dahdi-xx/tools/xpp/perl_modules/Dahdi/Chans.pm
my $dahdi_cfg = $ENV{DAHDI_CFG} || '/usr/sbin/dahdi_cfg';
sub probe_type($) {
my $self = shift;
my $fqn = $self->fqn;
my $num = $self->num;
my $type;

if($fqn =~ m:WCTDM/|WRTDM/|OPVXA1200/|OPVXA24XX/:) {
my %maybe;

undef %maybe;
foreach my $sig (qw(fxo fxs)) {
my $cmd = "echo ${sig}ks=$num | $dahdi_cfg -c /dev/fd/0";

$maybe{$sig} = system("$cmd >/dev/null 2>&1") == 0;
}

7. Add opvxa24xx in /usr/src/dahdi-xx/tools/modules.sample
# Digium TE205P/TE207P/TE210P/TE212P: PCI dual-port T1/E1/J1
# Digium TE405P/TE407P/TE410P/TE412P: PCI quad-port T1/E1/J1
# Digium TE220: PCI-Express dual-port T1/E1/J1
# Digium TE420: PCI-Express quad-port T1/E1/J1
wct4xxp

# OpenVox A2410P: up to 24 analog ports
opvxa24xx


8. Add opvxa24xx in /usr/src/dahdi-xx/tools/blacklist.sample
blacklist wctdm
blacklist opvxa24xx
blacklist wctc4xxp
blacklist wcb4xxp

2.3 Installation
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 // confirm GCC-4.0 above
rpm -q gcc-c++
If any of those packages are not installed, please install them by using yum
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 // install GCC-4.0 above
yum install gcc-c++

User can install the driver via the following steps (assuming user has the source code of dahdi device driver installed in /usr/src/dahdi-2.2.XX directory):

1. Checking the A2410P/AE2410P hardware by command: lspci –vvvvv
From the following, user can see that there is a device called communication controller interface be found.
01:01.0 Communication controller: Unknown device 1b74:2410 (rev 01)
Subsystem: Unknown device 1b74:0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- <PERR-
Latency: 64, Cache Line Size: 16 bytes
Interrupt: pin A routed to IRQ 50
Region 0: Memory at dcd00000 (32-bit, non-prefetchable) [size=1M]
2. Compiling
1) If user uses dahdi-linux-complete-XX, execute the commands:
cd /usr/src/dahdi-linux-complete-XX
./configure
make
make install
make config


If user uses dahdi-linux-XX and dahdi-tools-XX, execute the commands:
cd /usr/src/dahdi-linux-XX,
make
make instsll


cd /usr/src/dahdi-tools-XX,
./configure
make
make install



2) Installing asterisk
cd /usr/src/asterisk-XX
./configure
make
make install
make config


2.4 Configure
1. Loading modules for opvxa24xx:
modprobe dahdi
modprobe opvxa24xx opermode=YOUR COUNTRY
dahdi_genconf
dahdi_cfg –vvvv

Then run dmesg
If user uses AE2410P, user can find EC module has been detected.
OpenVox A2410P version: 1.0
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Installed -- AUTO FXO (FCC mode)
Module 2: Installed -- AUTO FXO (FCC mode)
Module 3: Installed -- AUTO FXO (FCC mode)
Module 4: Installed -- AUTO FXS/DPO
Module 5: Installed -- AUTO FXS/DPO
Module 6: Installed -- AUTO FXS/DPO
Module 7: Installed -- AUTO FXS/DPO
Module 8: Installed -- AUTO FXO (FCC mode)
Module 9: Installed -- AUTO FXO (FCC mode)
Module 10: Installed -- AUTO FXO (FCC mode)
Module 11: Installed -- AUTO FXO (FCC mode)
Module 12: Installed -- AUTO FXS/DPO
Module 13: Installed -- AUTO FXS/DPO
Module 14: Installed -- AUTO FXS/DPO
Module 15: Installed -- AUTO FXS/DPO
Module 16: Installed -- AUTO FXO (FCC mode)
Module 17: Installed -- AUTO FXO (FCC mode)
Module 18: Installed -- AUTO FXO (FCC mode)
Module 19: Installed -- AUTO FXO (FCC mode)
Module 20: Installed -- AUTO FXS/DPO
Module 21: Installed -- AUTO FXS/DPO
Module 22: Installed -- AUTO FXS/DPO
Module 23: Installed -- AUTO FXS/DPO
VPM450: echo cancellation supports 32 channels
VPM450: echo cancellation for 32 channels

VPM450: hardware DTMF disabled.
VPM450: Present and operational servicing 1 span(s)

2. Checking the configure files
The command dahdi_genconf will automatically generate the system.conf under /etc/dahdi and dahdi-channels.conf under /etc/asterisk. Please check the setting of system.conf, it looks like the following:
# Autogenerated by /usr/sbin/dahdi_genconf on Thu Jul 22 00:56:58 2010
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: OPVXA24XX/24 "OpenVox A2410 Board 25" (MASTER)
fxsks=1
fxsks=2
fxsks=3
fxsks=4
fxoks=5
fxoks=6
fxoks=7
fxoks=8
.
part of the file
.
.

# Global data

loadzone = us ;please change to your country
defaultzone = us ;please change to your country

Edit /etc/asterisk/indications.conf
country = us ;please change to your country

After loading dahdi and opvxa24xx driver, user should check the chan_dahdi.conf and dahdi-channels.conf under /etc/asterisk. Please make sure dahdi-channels.conf has been included into chan_dahdi.conf. If not, run the command:
echo "#include dahdi-channels.conf" >> /etc/asterisk/chan_dahdi.conf
Make sure that the context in dahdi-channels.conf should exist in extensions.conf. File dahdi-channels.conf should look like the following:
FXO ports use FXS signaling, the configure file looks like this:
; Autogenerated by /usr/sbin/dahdi_genconf on Thu Jul 22 00:56:58 2010
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;
; Span 1: OPVXA24XX/24 "OpenVox A2410 Board 25" (MASTER)
;;; line="1 OPVXA24XX/24/0"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

;;; line="2 OPVXA24XX/24/1"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
callerid=
group=
context=default

FXS ports use FXO signalling, the configure file looks like this:
;;; line="5 OPVXA24XX/24/4"
signalling=fxo_ks
callerid="Channel 5" <4005>
mailbox=4005
group=5
context=from-internal
channel => 5
callerid=
mailbox=
group=
context=default

;;; line="6 OPVXA24XX/24/5"
signalling=fxo_ks
callerid="Channel 6" <4006>
mailbox=4006
group=5
context=from-internal
channel => 6
callerid=
mailbox=
group=
context=default

3. Starting asterisk and test calls
Checking the dahdi channel loading from asterisk console:
asterisk –vvvvvvvgc
Entering asterisk console, run command: dahdi show channels. If dahdi channels can be shown, which means the dahdi channels have been loaded into asterisk.
*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
Pseudeo default default In service
1 from-pstn default In service
2 from-pstn default In service
3 from-pstn default In service
4 from-pstn default In service
5 from-internal default In service
6 from-internal default In service
7 from-internal default In service
8 from-internal default In service
9 from-pstn default In service
10 from-pstn default In service
11 from-pstn default In service
12 from-pstn default In service
13 from-internal default In service
14 from-internal default In service
15 from-internal default In service
16 from-internal default In service
17 from-pstn default In service
18 from-pstn default In service
19 from-pstn default In service
20 from-pstn default In service
21 from-internal default In service
22 from-internal default In service
23 from-internal default In service
24 from-internal default In service


When user makes an inbound call, CLI will show as the following:
-- Starting simple switch on 'DAHDI/4-1'
-- Executing [[email protected]:1] Answer("DAHDI/4-1", "") in new stack
-- Executing [[email protected]:2] BackGround("DAHDI/4-1", "demo-congrats") in new stack
-- Playing 'demo-congrats.gsm' (language 'en')
-- Executing [[email protected]:3] Hangup("DAHDI/4-1", "") in new stack
== Spawn extension (from-pstn, s, 3) exited non-zero on 'DAHDI/4-1'
Hungup 'DAHDI/4-1'

When user makes an outbound call, CLI will show as the following:
-- Starting simple switch on 'DAHDI/5-1'
-- Executing [[email protected]:1] Dial("DAHDI/5-1", "dahdi/4/910000") in new stack
-- Called 4/910000
-- DAHDI/4-1 answered DAHDI/5-1
-- Native bridging DAHDI/5-1 and DAHDI/4-1
-- Hungup 'DAHDI/4-1'
== Spawn extension (from-internal, 910000, 1) exited non-zero on 'DAHDI/5-1'
-- Hungup 'DAHDI/5-1'

The status of channel looks like the following. If user uses AE2410P, EC Status of active channel should be ON; otherwise it would be OFF.

*CLI> dahdi show channel 4
Channel: 4
File Descriptor: 19
Span: 1
Extension:
Dialing: no
Context: from-pstn
Caller ID:
Calling TON: 0
Caller ID name:
Mailbox: none
Destroy: 0
InAlarm: 0
Signalling Type: FXS Kewlstart
Radio: 0
Owner: DAHDI/4-1
Real: DAHDI/4-1
Callwait:
Threeway:
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: yes
Busy Detection: no
TDD: no
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
DND: no
Echo Cancellation:
128 taps
currently ON

Master Channel: 24
Actual Confinfo: Num/24, Mode/0x0009
Actual Confmute: No
Hookstate (FXS only): Offhook

Notes:
Test environments are:
CentOS-5.5
Kernel version: 2.6.18-194.el5
Dahdi: dahdi-linux-complete-2.3.0.1+2.3.0
Asterisk: 1.6.1.11
Hardware: OpenVox A2410P/AE2410P

i] Last edited by lisa.gao at 2010-8-31 13:41 [/i

10 years 2 months ago #6372 by seo117
THanks.:lol :lol

<a href=" dental-dam.info/ " target="_blank">dental dam</a> <a href=" dental-dam.info/ " target="_blank">dental dam</a>
Time to create page: 0.042 seconds
Powered by Kunena Forum