D410E/DE410E on DAHDI User Manual
General Safety Instructions
- 1. The computers that have D410E/DE410E card installed must comply with the country’s specific safety regulations.
- Only service personnel should go to install D410E/DE410E card.
- Before installing D410E/DE410E card, please unplug the power cord and remove the cover from your PC.
- For avoiding personal injuries and damages to your machine and
D410E/DE410E card, make sure bracket of the card is secured to the PC’s chassis ground by fastening the card with a screw.
- Electrical Surges, ESD are very destructive to the equipment. To avoid it, make sure there is a low impedance discharge path from your computer to chassis ground.
- To reduce the risk of damage or injury, please follow all steps or procedures as instructed.
Kernel version: 2.6.18-194. el5
Hardware: OpenVox D410E/DE410E
Chapter 1 Overview
1.1 What is Asterisk
The Definition of Asterisk is described as follows:
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 standard-based telephony equipment using relatively cost-effective hardware. Asterisk provides Voicemail services with Directory, Call Conferencing, Interactive Voice Response, Call Queuing. It supports for three-way calling, caller ID services, ADSI, IAX, SIP, H323 (as both client and gateway), MGCP (call manager only) and SCCP/Skinny (voip-info.org).
Figure 1 Topology
1.2 What is D410E/DE410E
The DE410E is a D410E with an EC module, and they support E1, T1 and J1 environments. It is selectable on a per-card or per-port basis. This feature enables signaling translation between E1 and T1 equipments and allows inexpensive T1 channel banks to connect with E1 circuits.
D410E supports industry standard telephony and data protocols, including Primary Rate ISDN (both N. American and Standard Euro) protocol families for voice, PPP, Cisco, HDLC, and Frame Relay data modes. Both line-side and trunk-side interfaces are supported.
D410E works with Asterisk®, Elastix®, FreeSWITCH™, PBX in a Flash, trixbox®, Yate™ and IPPBX/IVR projects as well as other Open Source and proprietary PBX, Switch, IVR, and VoIP gateway applications.
D410E/DE410E supports industry standard telephony and data protocols, including Primary Rate ISDN (both N. American and Standard Euro) protocol families for voice, PPP, Cisco, HDLC, and Frame Relay data modes. Both line-side and trunk-side interfaces are supported.
- Voice-over Internet Protocol (VoIP) Services
- Complex IVR Trees
- “Meet-Me” Bridge Conferencing
- Calling Card Platforms
- VoIP Gateways (support SIP, H.323, and IAX)
- Legacy PBX/IVR Services
- Voice/Data Router (replace expensive routers)
- PRI/Switch Compatibility – Network or CPE
Chapter 2 Hardware Setup
There are some points that should be paid attention to when setting up D410E/DE410E.
2.1 Span type setup
Each DIP switch controls one span configuration for E1 or T1 mode. Setting DIP1 to ON means SPAN1 will be E1.Setting DIP1 to OFF means SPAN1 will be T1.
2.2 CardID switch setup
If want to install more than one card of D410E/DE410E in a PC, you should take care of the card ID switch. There are two pieces of rules you must obey:
- The first card must be set to 0, which is a card that will be initialized (i.e. installing driver) firstly when the system boot up. And the second should be set to 1, and so forth.
- At most cases, Linux will initialize PCI devices according to their slot order. The slot nearest to the CPU will be initialized firstly and the far end slot will be initialized at last. That is to say, the card which is nearest to the CPU ID should be set to 0 if there is more than one D410E/DE410E on your machine.
2.3 Slot compatibility
D410E/DE410E is compatible with PCI-E ×1 (slot 1) and ×2, ×4, ×8, ×16 slot, except PCI slot; you should confirm your slot type and insert D410E/DE410E into any type of PCI-E slot as previously described.
Figure 2 PCI-E and PCI slots
2.4 Timing cable
If you have just one card in the system, all channels on that card have already run under the same clock source, so timing cable is unnecessary. But if there are more than one card, using timing cable has some advantages. Before using the clock line, each card works on its own clock, therefore precision of the clock is limited; each card will send /receive voice data at different speeds. In voice usage, this small issue can be omitted, but in data communication such as Fax/Modem, it will cause big problems. Data loss will cause communication broken or fax broken. Timing cable will force all cards to work at the same clock source, send data at the same speed, as a result no data will lost.
If you found J914 (input) and J915 (output) interfaces on the card, it means the card supports clock line, for details, please refer to HERE.
Chapter 3 Software Installation and Configuration
D410E/DE410E supports DAHDI software driver on Linux. To make full use of D410E/DE410E, you should download, compile, install and configure Libpri, DAHDI and Asterisk.
DAHDI software packages are available on OpenVox official website or Digium. Some patches should be added while the driver source is from Digium, therefore, it is recommended that downloading the DAHDI driver package from OpenVox official website.
Gain DAHDI source package from OpenVox:
Get Asterisk software package from Digium official website:
Get Libpri software package from Digium official website:
Execute the following commands under the directory of /usr/src/ in generally, the former two below are used for downloading these two packages and the later two are for unzipping them.
# tar –xvzf asterisk-18.104.22.168.tar.gz
# tar –xzvf libpri-22.214.171.124.tar.gz
1. Hardware detection
# lspci –vvvv
Check the outcome and confirm your system has recognized D410E/DE410E. If it has been recognized, “communication controller“ will be displayed in the output information like that:
Figure 3 Hardware detection
If D410E/DE410E is not recognized by the system, you have to power off and take out the card, then try to insert it into another PCI-E slot.
2. Software installation
Some dependencies are crucial. If any of them is absent, the software installation process would not go through successfully. Let’s run “yum install XX“ (XX stands for the dependency’s name) to check the availability of dependencies.
# 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++
# yum install libxml2
If there is no kernel source in the system, users should also install it by running like:
# yum install kernel-devel
If the dependency has been installed, system indicates that nothing to do which means you could go to next one directly. Otherwise, the system will keep on installing it.
Among Libpri, DAHDI and Asterisk, let’s install libpri firstly. Please execute those commands under the directory of /usr/src/ in generally:
# cd libpri-XX
# make install
Change to the directory of dahdi-linux-complete-XX (XX represents DAHDI version), then perform commands one by one to install DAHDI.
# cd /usr/src/dahdi-linux-complete-XX
# make install
# make config
Caution: If there is something wrong after “make“, please refer to HERE. In the url link, the moderator introduces you a method how to patch. After patching, save your changes and exit. Then run “make“ again, if successfully done, it is time for you to install Asterisk.
Please operate those commands to install Asterisk.
# cd asterisk-126.96.36.199
# make install
# make samples
“make samples” will install the standard sample configuration file in the directory /etc/asterisk. As a freshman, you should perform “make samples”, that is to say, it is unnecessary to perform “make samples” every time. Because once performed, it will cover the old sample configuration files you have installed.
1. Driver loading
After compiling and installing DAHDI and Asterisk, please load the driver by running:
# modprobe dahdi
# modprobe wct4xxp
If there is any error, please trace the cause. Until all errors are clear up, you could execute “dahdi_genconf“ again, and then go to the next step. By running “dahdi_genconf“, it will generate /etc/dahdi/system.conf and etc/asterisk/dahdi-channels.conf automatically. Checking whether the generated files information agrees with your hardware setup, if not, you should modify to your specific requirements. Do not forget to confirm dahdi-channels.conf is included in chan_dahdi.conf, if not, run command:
# echo “#include dahdi-channels.conf” >> /etc/asterisk/chan_dahdi.conf
A part of system.conf which is one of the basic channel configuration files is displayed.
Figure 4 A part of system.conf
2. Country mode modification
In order to match your country pattern, you need to change parameters loadzone and defaultzone to your country. For example, your system is in CHINA, you would like them change to:
loadzone = cn
defaultzone = cn
Some zonedata is available in the file
.. /dahdi-XX/tools/zonedata.c, you can refer to it to match your country mode. Meanwhile, you also need to modify another parameter which is in file /etc/asterisk/indications.conf.
A part of file /etc/asterisk/dahdi-channels.conf is showed as below. (Modification, if it is not agree with the hardware setup)
Figure 5 A part of dahdi-channels.conf
After modifying the country mode, please execute the following command:
# dahdi_cfg –vvvvvv
The command is used for reading and loading parameters in the configuration file system.conf and writing to the hardware. A part of outputs are showed in the following figure.
Figure 6 Channel map
3. Asterisk initiation
# asterisk –vvvvvvvgc
If Asterisk is already activate, run “asterisk –r“ instead. In the CLI, please run the following command:
localhost*CLI> dahdi show channels
Figure 7 channels show
If DAHDI channels are found, it means they have been loaded into Asterisk. You are going to edit dialplan by your requirements.
4. Dialplan edit
Users must make sure that the context “from-pstn“ and “from-internal“ are in extensions.conf, here a simple example is given:
# vim /etc/asterisk/extensions.conf
Figure 8 dial plan
Users should run command “cat /proc/interrupts“ to check D410E/DE410E has independent interrupt. If it shares interrupt with other device, it may cause some problems even cannot work normally. Or you can see if the EC module is working as follows:
Figure 9 EC module show
Chapter 4 Reference
Any questions during installation, please consult in our forum or look up for answers from the following websites:
Appendix A Specifications
• Weight and size
Weight: D410E 95g
Size: DE410P 13×10.3×2cm3
PCI-E ×1, ×2, ×4, ×8, or ×16 slot
Four T1/E1/J1 ports with PCI-E interface for high performance voice and data applications
Storage temperature: D410P -65 ~ 125°C
EC100 -40 ~ 75°C
Operation temperature: 0 ~ 50°C
Humidity: 10 ~ 90% NON-CONDENSING
• Power consumption
Voltage: 3.3V, 5V
Power: 2.6W Minimum, 3.9W Maximum at 3.3 V or 5 V
• Hardware and software requirements
RAM 128 + MB
Linux kernel 2.4.X or 2.6.X
CPU 800+ MHZ