VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
halflife4 at gmx.com
Guest
|
 Posted: Thu Aug 07, 2014 5:10 am Post subject: [asterisk-users] Dahdi > CAPI migration |
 |
|
Hello Folks,
I looking to migrate a pbx from one server to another. The original server has this ISDN card:
00:00.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
The new server:
00:00.0 I2O: Digital Equipment Corporation StrongARM DC21285 (rev 04) << AVM ISDN Controller C4
Now I'm not fully aware of both's cards functions since the manuals are very brief. What I heard is that the later card does not support some NT commands what I might going to need at this migration. I can't really say if one card is "better" than the other one.
Unfortunately the two uses completely different drivers. The first card uses dahdi, the second uses capi. I want this migration go as smooth as possible with the least downtime so I looking for some help
maybe someone has more experience with these cards.
I also read something about CAPI uses completely different dial plans.
So all the Asterisk configurations are migrated from the old server to the new one.
By following this guide:
http://www.asteriskguru.com/tutorials/avm_c4.html
I have the C4 modul loaded. My asterisk box is Asterisk 1.6.0.26-FONCORE-r78 (Trixbox).
How can I see that this C4 card is really working from asterisk?
What is the difference between the chan_dahdi.conf and chan_capi.conf?
Can't I just tell it somewhere to use the new card and I don't have to touch the existing dialplans etc?
Thanks!
--
_____________________________________________________________________
-- 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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
 |
patrick at laimbock.com
Guest
|
| Posted: Thu Aug 07, 2014 5:55 am Post subject: [asterisk-users] Dahdi > CAPI migration |
|
|
Hi Toney,
Comments inline.
On 07-08-14 12:10, Toney Mareo wrote:
| Quote: | Hello Folks,
I looking to migrate a pbx from one server to another. The original server has this ISDN card:
00:00.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
The new server:
00:00.0 I2O: Digital Equipment Corporation StrongARM DC21285 (rev 04) << AVM ISDN Controller C4
Now I'm not fully aware of both's cards functions since the manuals are very brief. What I heard is that the later card does not support some NT commands what I might going to need at this migration. I can't really say if one card is "better" than the other one.
Unfortunately the two uses completely different drivers. The first card uses dahdi, the second uses capi. I want this migration go as smooth as possible with the least downtime so I looking for some help
maybe someone has more experience with these cards.
|
In the past I have used Eicon Diva Server cards with chan_capi for years
and they worked great. I
| Quote: | I also read something about CAPI uses completely different dial plans.
So all the Asterisk configurations are migrated from the old server to the new one.
|
That is correct although the differences/changes you need to make are
limited. Adjusting the Dial command will go a long way.
That Asterisk version is rather old and assuming that's the old Trixbox
CE it is without security updates since 2012. I recommend you use a
fresh install of something like CentOS 6.5 + all updates and Asterisk
11.11.0 (or later if available) with the latest dahdi-linux, dahdi-tools
and libpri releases. Also get the latest chan_capi from here:
ftp://ftp.chan-capi.org/chan-capi/ The version with -HEAD in the name
has the latest fixes and is the one I always used.
| Quote: | How can I see that this C4 card is really working from asterisk?
|
Once you have the AVM C4 kernel module loaded and Asterisk with
chan_capi is installed and capi is enabled in the Asterisk config, start
Asterisk and then you should have a 'capi' command in the CLI. Executing
it should show you info about the status of your ISDN channels.
| Quote: | What is the difference between the chan_dahdi.conf and chan_capi.conf?
|
One is for DAHDI supported cards and the other is for CAPI cards like
the Eicon Diva Server and the AVM C4.
| Quote: | Can't I just tell it somewhere to use the new card and I don't have to touch the existing dialplans etc?
|
Nope.
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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
halflife4 at gmx.com
Guest
|
| Posted: Fri Aug 08, 2014 3:10 am Post subject: [asterisk-users] Dahdi > CAPI migration |
|
|
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:
pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN 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:
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
Any ideas how to proceed from this point?
Thanks
Sent: Thursday, August 07, 2014 at 12:55 PM
From: "Patrick Laimbock" <patrick@laimbock.com>
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Dahdi > CAPI migration
Hi Toney,
Comments inline.
On 07-08-14 12:10, Toney Mareo wrote:
| Quote: | Hello Folks,
I looking to migrate a pbx from one server to another. The original server has this ISDN card:
00:00.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)
The new server:
00:00.0 I2O: Digital Equipment Corporation StrongARM DC21285 (rev 04) << AVM ISDN Controller C4
Now I'm not fully aware of both's cards functions since the manuals are very brief. What I heard is that the later card does not support some NT commands what I might going to need at this migration. I can't really say if one card is "better" than the other one.
Unfortunately the two uses completely different drivers. The first card uses dahdi, the second uses capi. I want this migration go as smooth as possible with the least downtime so I looking for some help
maybe someone has more experience with these cards.
|
In the past I have used Eicon Diva Server cards with chan_capi for years
and they worked great. I
| Quote: | I also read something about CAPI uses completely different dial plans.
So all the Asterisk configurations are migrated from the old server to the new one.
|
That is correct although the differences/changes you need to make are
limited. Adjusting the Dial command will go a long way.
That Asterisk version is rather old and assuming that's the old Trixbox
CE it is without security updates since 2012. I recommend you use a
fresh install of something like CentOS 6.5 + all updates and Asterisk
11.11.0 (or later if available) with the latest dahdi-linux, dahdi-tools
and libpri releases. Also get the latest chan_capi from here:
ftp://ftp.chan-capi.org/chan-capi/ The version with -HEAD in the name
has the latest fixes and is the one I always used.
| Quote: | How can I see that this C4 card is really working from asterisk?
|
Once you have the AVM C4 kernel module loaded and Asterisk with
chan_capi is installed and capi is enabled in the Asterisk config, start
Asterisk and then you should have a 'capi' command in the CLI. Executing
it should show you info about the status of your ISDN channels.
| Quote: | What is the difference between the chan_dahdi.conf and chan_capi.conf?
|
One is for DAHDI supported cards and the other is for CAPI cards like
the Eicon Diva Server and the AVM C4.
| Quote: | Can't I just tell it somewhere to use the new card and I don't have to touch the existing dialplans etc?
|
Nope.
HTH,
Patrick
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com[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]
--
_____________________________________________________________________
-- 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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
patrick at laimbock.com
Guest
|
| Posted: Fri Aug 08, 2014 8:35 am Post subject: [asterisk-users] Dahdi > CAPI migration |
|
|
On 08-08-14 10:09, Toney Mareo wrote:
| Quote: | 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:
pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card
|
IIRC the wcb4xx module is correct for this card.
| Quote: | 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?
| Quote: | 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.
| Quote: | 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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
tzafrir.cohen at xorco...
Guest
|
| Posted: Sat Aug 09, 2014 10:40 am Post subject: [asterisk-users] Dahdi > CAPI migration |
|
|
On Fri, Aug 08, 2014 at 03:34:44PM +0200, Patrick Laimbock wrote:
| Quote: | On 08-08-14 10:09, Toney Mareo wrote:
| Quote: | 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:
pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card
|
IIRC the wcb4xx module is correct for this card.
|
Not only that, but the '+' means that this module handles this specific
hardware.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen@xorcom.com
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com
--
_____________________________________________________________________
-- 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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
halflife4 at gmx.com
Guest
|
| Posted: Mon Aug 11, 2014 4:10 am Post subject: [asterisk-users] Dahdi > CAPI migration |
|
|
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@laimbock.com>
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Dahdi > CAPI migration
On 08-08-14 10:09, Toney Mareo wrote:
| Quote: | 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:
pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card
|
IIRC the wcb4xx module is correct for this card.
| Quote: | 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?
| Quote: | 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.
| Quote: | 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]
--
_____________________________________________________________________
-- 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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
patrick at laimbock.com
Guest
|
| Posted: Mon Aug 11, 2014 5:28 pm Post subject: [asterisk-users] Dahdi > CAPI migration |
|
|
On 11-08-14 11:09, Toney Mareo wrote:
| Quote: |
Hello
The answers to your questions are:
1, OS
CentOS release 5.5 (Final)
|
That version is ancient and full of security holes. It is recommended to
at least update to CentOS 5.10 + updates. That's assuming there are
Trixbox kmod-dahdi-linux* RPMs for CentOS 5.10.
| Quote: | Trixbox installed at: Autogenerated by /usr/sbin/dahdi_genconf on Fri Nov 25 18:03:26 2011
|
Trixbox CE no longer exists and is no longer supported. Why continue
using it?
| Quote: | 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
|
All ancient, with many (security) bugs and no longer supported.
| Quote: | 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.
|
Right.
| Quote: | 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)
|
Ok.
| Quote: | 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
|
Maybe the wcb4xx module is interfering with the mISDN modules. Try
blacklisting the wcb4xx kernel module and restart DAHDI and mISDN. Or
try stopping mISDN, restart DAHDI with the wcb4xx module configured and
see if DAHDI is happy. Or something might be wrong with the udev rules.
| Quote: | 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
|
With such an exotic setup and ancient versions of something that no
longer exists, I think you are SOL.
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
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
