[asterisk-users] Dahdi > CAPI migration
Toney Mareo
halflife4 at gmx.com
Mon Aug 11 04:09:55 CDT 2014
Hello
The answers to your questions are:
1, OS
CentOS release 5.5 (Final)
Trixbox installed at: Autogenerated by /usr/sbin/dahdi_genconf on Fri Nov 25 18:03:26 2011
2, Kernel
Linux 2.6.18-164.11.1.el5xen #1 SMP Wed Jan 20 08:53:10 EST 2010 i686 i686 i386 GNU/Linux
3, Packages
asterisk16-dahdi.i386 1.6.0.26-1_trixbox installed
dahdi-firmware.noarch 2.0.0-1_centos5 installed
dahdi-firmware-oct6114-064.noarch 1.05.01-1_centos5 installed
dahdi-firmware-oct6114-128.noarch 1.05.01-1_centos5 installed
dahdi-firmware-tc400m.noarch MR6.12-1_centos5 installed
dahdi-firmware-vpmadt032.noarch 1.07-1_centos5 installed
dahdi-linux.i386 2.3.0.1-1_trixbox installed
dahdi-tools.i386 2.3.0-1_trixbox installed
dahdi-tools-doc.i386 2.2.0-4_trixbox installed
kmod-dahdi-linux.i686 2.3.0.1-1_trixbox.2.6.18_164.11.1.el5
kmod-dahdi-linux-xen.i686 2.3.0.1-1_trixbox.2.6.18_164.11.1.el5
dahdi-linux-devel.i386 2.3.0.1-1_trixbox trixbox28
kmod-dahdi-linux-PAE.i686 2.3.0.1-1_trixbox.2.6.18_164.11.1.el5
libpri.i386 1.4.10.2-1_centos5 installed
libpri-devel.i386 1.4.10.2-1_centos5 trixbox28
asterisk16.i386 1.6.0.26-1_trixbox installed
kmod-mISDN.i686 1.1.7.2-4_centos5.2.6.18_164.11.1.el5
kmod-mISDN-xen.i686 1.1.7.2-3_centos5.2.6.18_164.11.1.el5
mISDN.i386 1.1.7.2-4_centos5 installed
mISDNuser.i386 1.1.7.2-2_centos5 installed
asterisk-chan_misdn.i386 1.4.22-3 trixbox
kmod-mISDN-PAE.i686 1.1.7.2-3_centos5.2.6.18_164.11.1.el5
mISDN.i686 1.1.7-27 trixbox
mISDN-debuginfo.i686 1.1.7-24 trixboxaddons
mISDN-devel.i686 1.1.7-27 trixbox
mISDN-devel.i386 1.1.7.2-4_centos5 trixbox28
mISDN-kmod-base.i686 1.1.7.2-1_centos5.2.6.18_128.1.10.el5
mISDN-modules.i686 1.1.7-27.2.6.18_92.1.18.el5 trixbox
mISDNuser-debuginfo.i386 1.1.7-15 trixboxaddons
mISDNuser-devel.i386 1.1.7.2-2_centos5 trixbox28
Asterisk 1.6.0.26-FONCORE-r78, Copyright (C) 1999 - 2010 Digium, Inc. and others.
4, What do you mean with "the OS-es were clones ..."? Did you create an
image of the old Trixbox machine and installed that on the new machine?
It means that they are Xen virtual machines, exact bit by bit vm clones so they should have all the same configuration files, run the exact same Xen kernels. What complicates things a bit, and probably the cause of my errors is Xen's PCI passthrough. The only reason why I use something so obsolete like Xen is just this feature otherwise I would be using kvm, vmware, virtualbox or whatever virt technologies but for those you must have vt(d) hardware support and the machine I dealing with here doesn't have this, neither the old one.
5, Lsdadhi (this is on the first, working machine)
### Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS
1 BRI Clear (In use) (SWEC: MG2)
2 BRI Clear (In use) (SWEC: MG2)
3 BRI Hardware-assisted HDLC (In use)
### Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS
4 BRI Clear (In use) (SWEC: MG2)
5 BRI Clear (In use) (SWEC: MG2)
6 BRI Hardware-assisted HDLC (In use)
### Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
7 BRI Clear (In use) (SWEC: MG2) RED
8 BRI Clear (In use) (SWEC: MG2) RED
9 BRI Hardware-assisted HDLC (In use) RED
### Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS
10 BRI Clear (In use) (SWEC: MG2)
11 BRI Clear (In use) (SWEC: MG2)
12 BRI Hardware-assisted HDLC (In use)
6, Asterisk logs (new machine when it failed)
full.4:[Aug 7 12:39:58] WARNING[1654] chan_dahdi.c: Unable to specify channel 1: No such device or address
full.4:[Aug 7 12:39:58] ERROR[1654] chan_dahdi.c: Unable to open channel 1: No such device or address
full.4:[Aug 7 12:39:58] ERROR[1654] chan_dahdi.c: Unable to register channel '1-2'
full.4:[Aug 7 12:39:58] VERBOSE[1654] logger.c: -- codec_dahdi: using generic PLC
full.4:[Aug 7 12:39:58] ERROR[1654] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory
full.4:[Aug 7 12:39:58] VERBOSE[1654] logger.c: codec_dahdi.so => (Generic DAHDI Transcoder Codec Translator)
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Registered application 'DAHDIBarge'
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: app_dahdibarge.so => (Barge in on DAHDI channel application)
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Setting global variable 'TRUNK' to '"DAHDI/G2"'
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Registered application 'DAHDIRAS'
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: app_dahdiras.so => (DAHDI ISDN Remote Access Server)
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Setting global variable 'OUT_1' to 'DAHDI/g0'
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Setting global variable 'OUT_2' to 'DAHDI/g1'
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Setting global variable 'OUT_3' to 'DAHDI/g3'
full.4:[Aug 7 12:39:59] VERBOSE[1654] logger.c: == Setting global variable 'ASTCHANDAHDI' to '1'
full.4:[Aug 7 18:12:04] VERBOSE[1707] logger.c: == Registered application 'DAHDIScan'
full.4:[Aug 7 18:12:04] VERBOSE[1707] logger.c: app_dahdiscan.so => (Scan DAHDI channels application)
full.4:[Aug 7 18:12:04] VERBOSE[1707] logger.c: == Registered application 'DAHDISendKeypadFacility'
full.4:[Aug 7 18:12:04] VERBOSE[1707] logger.c: == Parsing '/etc/asterisk/chan_dahdi.conf': [Aug 7 18:12:04] VERBOSE[1707] logger.c: == Found
full.4:[Aug 7 18:12:04] VERBOSE[1707] logger.c: == Parsing '/etc/asterisk/dahdi-channels.conf': [Aug 7 18:12:04] VERBOSE[1707] logger.c: == Found
full.4:[Aug 7 18:12:04] VERBOSE[1707] logger.c: == Parsing '/etc/asterisk/chan_dahdi_additional.conf': [Aug 7 18:12:04] VERBOSE[1707] logger.c: == F
ound
The xen-pciback hide's setup properly on the machines so the xen guests have access to the card. The only difference is between the 2 host machines host kernels:
old: Linux 2.6.32-5-xen-686
new: Linux 3.13-0.bpo.1-amd64
Sent: Friday, August 08, 2014 at 3:34 PM
From: "Patrick Laimbock" <patrick at laimbock.com>
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Dahdi > CAPI migration
On 08-08-14 10:09, Toney Mareo wrote:
> Hello
>
> Thank you for your response. I thought it could be easier moving the old card to the new machine and using the DAHDI driver. Unfortunately my first attempt for this failed. The card shows up in the original machine as:
>
>> dahdi_hardware -v
> pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card
IIRC the wcb4xx module is correct for this card.
> 00:00.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
> Subsystem: Cologne Chip Designs GmbH HFC-4S [IOB4ST]
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Interrupt: pin A routed to IRQ 20
> Region 0: I/O ports at 9400 [size=8]
> Region 1: Memory at f2841000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [40] Power Management version 2
> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> The second machine recognized it as well and as I said the OS-es were clones (so all drivers, settings should be indentical), still after start the DAHDI driver loaded but didn't work from Asterisk:
What do you mean with "the OS-es were clones ..."? Did you create an
image of the old Trixbox machine and installed that on the new machine?
Which versions are you using of:
the OS?
dahdi-linux?
dahdi-tools?
libpri?
asterisk?
Are you using mISDN too?
> Running dahdi_cfg: DAHDI_SPANCONFIG failed on span 1: No such device or address (6)
> No hardware timing source found in /proc/dahdi, loading dahdi_dummy
In general it could be that the card is not recognized or that there's a
conflict with another kernel module or your dahdi config is incorrect or
the udev rules are missing or wrong, etc.
> Any ideas how to proceed from this point?
Since you have provided not very much information one can only guess.
Only by providing as much information as possible can you help us help you.
So please answer all the questions, provide the versions as asked, give
the output of lsdahdi, check the logfiles (/var/log/messages etc) for
dahdi info, check the dahdi config and blacklist files and provide that
with anything else you can think of.
AFAIK the Junghanns QuadBRI ISDN card should work fine with a recent
DAHDI so why do you want to change to an AVM C4 card that requires
chan_capi that hasn't seen any recent development and does not support
Asterisk 11 or later? Asterisk 1.8 will only be supported for another
year and then you are stuck again with an obsolete system that no longer
gets any (security!) updates.
If you can, why not stay with the Junghanns card and put a fresh CentOS
6.5 + updates on the new machine together with the latest version of
dahdi-linux, dahdi-tools, libpri and asterisk. And then copy your old
dialplan over to the new machine and make the required changes so it
works with the latest Asterisk 11. Or you could install the latest
FreePBX iso on the new machine if you prefer a GUI.
HTH,
Patrick
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello[http://www.asterisk.org/hello]
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users[http://lists.digium.com/mailman/listinfo/asterisk-users]
More information about the asterisk-users
mailing list