OpenVox B200P User Manual for Bristuff
From Wiki
Contents |
B200P user manual
Chapter 1 Overview
1. What is B200P
B200P series is a PCI 2.2 compliant card supporting 2 BRI S/T interfaces, with an onboard multi NT power feeding circuit. NT/TE mode can be independently configured on each of the 2 ports.
B200P can be implemented for building Open Source Asterisk based
systems such as ISDN PBX and VoIP gateway.
Target Applications:
High Performance ISDN PC Cards
ISDN PABX for BRI
VoIP Gateways
ISDN LAN Routers for BRI
ISDN Least Cost Routers for BRI
ISDN Test Equipment for BRI
Main Features:
Two/Four integrated S/T interfaces
ITU-T I.430 and TBR 3 certified and S/T ISDN supporting in TE and NT mode
Integrated PCI bus interface (Spec.2.2) for 3.3V and 5V signal environments
DTMF detection on all B-channels
Multiparty audio conferences bridge
Onboard power feeding
PCM bus connectors daisy chaining
Each port can be independently configured for TE or NE mode
Full software and hardware compatible with bristuff and mISDN driver
Application ready: use Asterisk to build your IP-PBX/Voicemail system
RoHS compliant
Certificates: CE, FCC
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/12V(NT ONLY)
5) Power Dissipation Max:0.44W/0.66W/4.4W
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:
1) Voicemail services with Directory
2) Call Conferencing
3) Interactive Voice Response
4) Call Queuing
5) Three-way calling
6) Caller ID services
7) ADSI, IAX, SIP, H.323, MGCP and SCCP/Skinny.
Chapter 2 Card Installation and Configuration
1. Hardware Installation and Setup
Please check jumper setting for details. To install B200P, user should
follow these steps:
A. Setting Card ID Switch
If user wants to install more than one cards of B200P or B400P in one
pc, you should take care of the card id switch. It has three rules,
which user must follow:
1. The card id of the first card must be set to 0, and the second card
should be set to 1, and so on.
2. The First Card is a card that will be initialized (i.e installing
driver) first when system is booting.
3. At most of cases, Linux will initialize PCI devices according to
PCI slot order. The slot is nearest to the CPU will be initialized
first; the slot at the far end from CPU will be initialized at last.
That is to say, if user has more than one cards of B200P in pc, the one is nearest to CPU should be set to card id 0.
B. Adjusting Termination of S/T Interface (100 ohm)
1. If a port will work on NT mode, you should set jumper to CONNECT
(ON).
2. If a port will work on TE mode, Theoretically it should be to
OPEN(OFF), but user might connect to some non-standard isdn
terminal equipments that do not have terminal resistors, for such
equipments, you should set it to CONNECT(ON).
C. Power Feeding Connector
These jumpers control whether the card will feed power to the external
isdn terminal. User should adjust accordingly.
1) If the port will work on TE mode, user MUST set the jumper to
OPEN(OFF)
2) If this port will work on NT mode, the ISDN terminal requires
ISDN power supply, user should set the jumper to CONNECT(ON).
ISDN terminal does not require ISDN power supply, user should
set the jumper to OPEN(OFF).
D. Power Feeding Input
if user sets one of ports is NT mode, please plug in the power supply cable.
chapter 3 Software Configuration and configuration
1) check the hardware detection by : lspci -vvvvvv
User should see the device information like this:
ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
If user can not see that, please swap to other slots to try.
2) Checking the supporting packages
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 other 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 any of those packages is not installed, please install those packages 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 yum install gcc-c++
1. Download OpenVox patch called qozap.c from www.openvox.com.cn.
Download the stable version of bristuff drivers from http://www.junghanns.net/, and copy the tar file to /usr/src/
cp bristuff-<version>.tar.gz /usr/src
cd /usr/src/
tar -xvzf bristuff-<version>.tar.gz
2. Make links with kernel source:
ln -s /usr/src/kernels/2.6.18-8.el5-i686/ /usr/src/linux-2.6
Here, under /usr/src there is kernel source, user must create link
linux-2.6 under /usr/src/. There are many files under
/usr/src/bristuff-0.3.0-PRE-1y-j
3. Compiling Bristuff
cd /usr/src/usr/src/bristuff-0.3.0-PRE-1y-j chmod 777 install.sh ./install.sh
overwrite the orginal qozap.c file with the new qozap.c under /usr/src/bristuff-<version>/qozap.
run ./compile.sh to recompile all packages.
Above steps will install zaptel, libpri and asterisk.
After finishing the three steps, under asterisk directory, running make
samples if user install asterisk for first time.
4. Modifying and loading modules for zaptel and qozap
vi /etc/zaptel.conf, and edit the zaptel.conf like this:
loadzone=nl defaultzone=nl # qozap span definitions # most of the values should be bogus because we are not really zaptel span=1,1,3,ccs,ami span=2,2,3,ccs,ami bchan=1,2 dchan=3 bchan=4,5 dchan=6
cd /usr/src/bristuff-0.3.0-PRE-1y-j/qozap modprobe zaptel modprobe qozap.ko (for kernel 2.6.o) ztcfg –vvvvvvvvvvvvvvv
5. If user wants to modify the call rules, edit zapata.conf file under
/etc/asterisk to make sure asterisk run successfully
asterisk –vvvvvvvvvvgc zap show channels // there must be some channels.
Notes: Test environments: OS: Centos 5 Kernel version: 2.6.18-8.15 Bristuff version: bristuff-0.3.0-PRE-1y-j Hardware：OpenVox B200P
