× Questions about B100/200/400/800 ISDN BRI Cards

OpenVox B100P Install Manual for dahdi on openSUSE

7 years 11 months ago #7155 by Joe.Yung
Yes, it seems that it's more difficult to find the dependent packages based on OpenSUSE than CentOS or Debian, so you might need to forward to corresponding forums to get more professional assistance.

7 years 11 months ago #7159 by sipi
I'll post a manual but that is very complex because you need to prepare some services and configure that all of them run on suse correctly. Example: you need run two apache if you use other application on http. FreePBX webuser must be asterisk and other application or/and default webuser is wwwrun on suse.

I have a lot of notes from installation and I create a manual now but it'll be more pages...

I think it'll use to other cards as B200P and B400P but you need change dahdi conf, FreePBX trunks and routes.
7 years 11 months ago #7187 by sipi
I think I have already finished my documentations. Shortly. I use openSUSE 11.3 with Xen virtualization and I need one VOIP PBX. I get an OpenVox B100P ISDN BRI card and installed it on openSUSE with asterisk and dahdi. But I need an GUI for managing asterisk because I installed FreePBX. There was some problem because openSUSE default apache user and group are wwwrun:www nad FreePBX can't run if apache user and group aren't asterisk:asterisk. I need that apache runs with default user because I made that run two apache same machine. Next problem was that I need fax-toe-mail and e-mail-to-fax service that I not need a fax machine. Because I installed HylaFAX server on openSUSE and WinPrintHylafax client on WindowsXP machine. It was an very big challenge but story finished successfully.I searched info, bolg, faq, manual, tips and everything what can help for me. I found a lot of useful information and "manual" but there aren't completely for my problems. Because I made some "manual". I copied useful information and attached my opinion and final experimental results. I hope that it will help somebody.

i] Last edited by sipi at 2011-8-2 01:54 [/i
Attachments:
7 years 8 months ago #7457 by reinerotto
Hi,

I exactly followed your http://bbs.openvox.cn/attachment.php?aid=216 , with one execption:
...
If you have an error „implicit declaration of function kzalloc” on dahdi_echocan_oslec.c file when you
compile dahdi-linux-complete-2.3.0.1+2.3.0 then you need modifiy the /usr/src/dahdi-linux- complete-
2.3.0.1+2.3.0/linux/dahdi/dahdi_echocan_oslec.c file. Insert #include <linux/slab.h> here:
........ MUST BE ....
2.3.0.1+2.3.0/linux/drivers/dahdi/dahdi_echocan_oslec.c
Anyway, compile then generates an error:

/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/dahdi_transcode.c:433:2: error: unknown field ioctl specified in initializer
/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/dahdi_transcode.c:433:2: warning: initialization from incompatible pointer type
make[5]: *** [/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/dahdi_transcode.o] Error 1

Most likely to be connected to the new kernel, I have: 2.6.37.6-0.7.1

So I am stuck.
7 years 8 months ago #7462 by tim.june
Hi,

I have tested dahdi-linux-complete-2.3.0.1+2.3.0 with the patch B100_dahdi_2.3.0.1_complete_patch.extra on Suse 11.4, as the kernel version of Suse is too high to complete compiling the old version of dahdi, so you need to change a newer verson of dahdi.

We have released a newer one which has been patched for B100P, you just need to download it from OpenVox website and compile it to install on your server. The link is below:

http://downloads.openvox.cn/pub/drivers/dahdi-linux-complete/releases/1.3.3/openvox_dahdi-linux-complete-2.5.0.1+2.5.0.1.tar.gz

This version has been tested on Suse 11.4, you can take it easy to compile and install on your server.

Good Luck!

Email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Skype: tim.jjune
7 years 8 months ago #7463 by reinerotto
.. I do not see the ISDN channels :-)
I have an "almost virgin" SuSE 11.4 for testing, only asterisk device is the B100P card.

Here some excerpts from my files/logs:

*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service

*CLI> dahdi show status
Description Alarms IRQ bpviol CRC Fra Codi Options LBO
HFC-S PCI A ISDN card 0 [TE] OK 0 0 0 CCS AMI 0 db (CSU)/0-133 feet (DSX-1)
*CLI>


/var/log/messages:
....
Oct 27 15:26:47 localhost kernel: [ 981.055334] dahdi_echocan_mg2: Registered echo canceler 'MG2'
Oct 27 15:26:47 localhost kernel: [ 981.055938] vzaphfc: card 0: chan B1: TX FIFO has become empty
Oct 27 15:26:47 localhost kernel: [ 981.055944] vzaphfc: card 0: chan B1 opened as ZTHFC1/0/1.
Oct 27 15:26:47 localhost kernel: [ 981.055967] vzaphfc: card 0: chan B1 closed as ZTHFC1/0/1.
Oct 27 15:26:47 localhost kernel: [ 981.055981] vzaphfc: card 0: chan B2: TX FIFO has become empty
Oct 27 15:26:47 localhost kernel: [ 981.055986] vzaphfc: card 0: chan B2 opened as ZTHFC1/0/2.
Oct 27 15:26:47 localhost kernel: [ 981.055992] vzaphfc: card 0: chan B2 closed as ZTHFC1/0/2.
Oct 27 15:26:47 localhost kernel: [ 981.056059] vzaphfc: card 0: chan D opened as ZTHFC1/0/3.
Oct 27 15:26:47 localhost kernel: [ 981.056068] vzaphfc: card 0: chan D closed as ZTHFC1/0/3.
dmesg:
...
[ 981.055334] dahdi_echocan_mg2: Registered echo canceler 'MG2'
[ 981.055938] vzaphfc: card 0: chan B1: TX FIFO has become empty
[ 981.055944] vzaphfc: card 0: chan B1 opened as ZTHFC1/0/1.
[ 981.055967] vzaphfc: card 0: chan B1 closed as ZTHFC1/0/1.
[ 981.055981] vzaphfc: card 0: chan B2: TX FIFO has become empty
[ 981.055986] vzaphfc: card 0: chan B2 opened as ZTHFC1/0/2.
[ 981.055992] vzaphfc: card 0: chan B2 closed as ZTHFC1/0/2.
[ 981.056059] vzaphfc: card 0: chan D opened as ZTHFC1/0/3.
[ 981.056068] vzaphfc: card 0: chan D closed as ZTHFC1/0/3.

/var/log/asterisk/messages:

.....
[Oct 27 15:32:06] NOTICE[2938] cdr.c: CDR simple logging enabled.
[Oct 27 15:32:06] NOTICE[2938] loader.c: 188 modules will be loaded.
[Oct 27 15:32:07] NOTICE[2938] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[Oct 27 15:32:07] WARNING[2938] loader.c: Error loading module 'res_pktccops': /usr/lib/asterisk/modules/res_pktccops.so: cannot open shared object file: No such file or directory
[Oct 27 15:32:07] WARNING[2938] loader.c: Error loading module 'chan_mgcp.so': /usr/lib/asterisk/modules/chan_mgcp.so: undefined symbol: ast_pktccops_gate_alloc
[Oct 27 15:32:07] WARNING[2938] loader.c: Module 'chan_mgcp.so' could not be loaded.
[Oct 27 15:32:07] WARNING[2938] config.c: parse error: No category context for line 11 of /etc/asterisk/dahdi-channels.conf
[Oct 27 15:32:07] WARNING[2938] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 23.
[Oct 27 15:32:07] WARNING[2938] chan_dahdi.c: Ignoring any changes to 'vmsecret' (on reload) at line 31.
[Oct 27 15:32:07] WARNING[2938] chan_dahdi.c: Ignoring any changes to 'hassip' (on reload) at line 35.
[Oct 27 15:32:07] WARNING[2938] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 39.
[Oct 27 15:32:07] WARNING[2938] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 47.
[Oct 27 15:32:07] NOTICE[2938] chan_skinny.c: Configuring skinny from skinny.conf
[Oct 27 15:32:08] NOTICE[2938] pbx_ael.c: Starting AEL load process.
[Oct 27 15:32:08] NOTICE[2938] pbx_ael.c: AEL load process: parsed config file name '/etc/asterisk/extensions.ael'.
[Oct 27 15:32:08] NOTICE[2938] pbx_ael.c: AEL load process: checked config file name '/etc/asterisk/extensions.ael'.
[Oct 27 15:32:08] NOTICE[2938] pbx_ael.c: AEL load process: compiled config file name '/etc/asterisk/extensions.ael'.
[Oct 27 15:32:08] ERROR[2938] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory

/etc/asterisk/dahdi-channels.conf:
; Autogenerated by /usr/sbin/dahdi_genconf on Thu Oct 27 15:26:09 2011
; 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: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] "
group=0,11
context=from-isdn
overlapdial=yes
switchtype = euroisdn
signalling = bri_cpe_ptmp
channel => 1-2
context = default
group = 63


I used your http://downloads.openvox.cn/pub/drivers/dahdi-linux-complete/releases/1.3.3/openvox_dahdi-linux-complete-2.5.0.1+2.5.0.1.tar.gz
and http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-1.8.7.1.tar.gz
and the libpri 1.4.12 from SuSE

Any ideas ?
Time to create page: 0.036 seconds
Powered by Kunena Forum