Install A400P with zaptel and B100P with misdn will not work together,please just change the driver to dahdi,it is a better way to solve the problem.
you just need to follow the manual below and two ...
Hi, I'm using trixbox 2.6.2.1 with a PRI card and i'm installing the b100p so i need to change driver from zaptel to dahdi but I 've read that asterisk needs zaptel to work.
Also, as soon as i physically installed the b100p asterisk would not start. I had to do service zaptel stop.
could you please tell me what is the correct way to remove Zaptel?
downloaded and executed the patch from Openvox. While executing the patch I was asked twice about the file to patch. Since there was no reference to this in the tutorial I mentioned no file.
Installed the correct kernel devel and the other pre-requisites (gcc etc), only two were missing.
changed file ./tools/modules.sample to allow vzaphfc
Confirmed both cards were detected with lspci -vvvv
in dahdi directory : make all
make install
make config
Since I'm using asterisk 1.4.22-2 I didn't change any channels file (according to tutorial it was supposed to be done in version 1.6.xx of asterisk)
Now when i try to run "Service dahdi stop" i get a messagelike :"dahdi: unrecognized service"
modprobe dahdi runs without error.
modprobe vzaphfc returns:
FATAL: Module vzaphfc not found.
Those were my last steps to install.
I restarted system after installing dahdi. Also in asterisk dahdi commans don't exist, maybe because it cannot start correctly.
I also ran dahdi_genconf and it only detected the analog card, wich is understandable since ISDN driver (vzaphfc) is not working, altough when system is booting it waits for zaptel module, so I may need to configure asterisk to use dahdi instead of zaptel. I just don't know how that's done.
Can anyone help me on this?
I'll provide logs or any info is needed.
at the end of installation I always get the message that it was installed ok, altought I now see a few warnings.
Since my last post there were some improvements:
Openvox patch aplied sucessfully (option -p2 should be -p1 to work).
Service dahdi is installed.
dahdi_genconf detects both the analog and ISDN card.
Problems i still found:
modprobe does not recognize vzaphfc
no dahdi commands in asterisk (as i said earlier I haven't changed any asterisk file. I'm using trixbox 2.6.2.1 and asterisk 1.4.22-2 was already installed. Same with libpri, using version 1.4.7-1.488)
dahdi_genconf only configures analog card but dahdi_hardware detectes both analog and ISDN card:
Here are the warnings i found while running make all:
(...)
touch /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/xpp/init_fxo_modes.verified
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
CC /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/dahdi.mod.o
(...)
make[3]: Entering directory `/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/tools/xpp'
Makefile:141: .depend: No such file or directory
make[3]: Leaving directory `/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/tools/xpp'
And here are the warnings running make install:
(...)
make[2]: Entering directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
make[2]: Leaving directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
(...)
make[2]: Entering directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
make[2]: Leaving directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
(...)
Also, make config returns the next warnings:
(...)
make[2]: Entering directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
make[2]: Leaving directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
(...)
make -C /lib/modules/2.6.18-92.1.18.el5/build SUBDIRS=/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m
make[2]: Entering directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd for /usr/src/dahdi-linux-complete-2.3.0.1+2.3.0/linux/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o
make[2]: Leaving directory `/usr/src/kernels/2.6.18-92.1.18.el5-i686'
build_tools/uninstall-modules dahdi 2.6.18-92.1.18.el5
I managed to get further by...reading the tutorial more carefully and analising some situatins like the patch command need to be -p1 instead of -p2 like the tutorial said.
So most of the problemas are now solved and my mistake was only that I downloaded the patch to the dahdi_complete_source folder instead of dahdi_complete_source/linux .
I applied the patch in the correct folder and vzaphfc is now available. Also dahdi_genconf configures /etc/dahdi/system.conf and /etc/asterisk/dahdi_channels.conf with both cards.
So now the problem is that dahdi commands do not show up in asterisk. It's like dahdi module is not loaded by asterisk, wich might be understandable because asterisk was already installed.
To solve this last part I need to reinstall asterisk or is there a chance to just tell it to use dahdi instead of zaptel?
Hi Bruno,
Please send ssh to me, I will install it for you, my Email: This email address is being protected from spambots. You need JavaScript enabled to view it.