asterisk users - Aug 2009 - Problems with pstn cards

Hi everybody,



I have a 1.6.0.5 asterisk system and I?m having many problems with my pstn
cards. This system has a Digium B410P with 4 BRIs configured, and an OpenVox
A400E.



The issue is that it?s impossible to make the system recognize the A400E,
despite  the ?lspci? output is:

0a:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface

11:00.0 ISDN controller: Digium, Inc. Wildcard B410 quad-BRI card (rev 01)



And ?dahdi_hardware? output is:

pci:0000:0a:00.0     wctdm-       e159:0001 Wildcard TDM400P REV E/F

pci:0000:11:00.0     wcb4xxp+     d161:b410 Digium Wildcard B410P



but ?dahdi_scan? just recognize the B410P:

[1]

active=yes

alarms=RED

description=B4XXP (PCI) Card 0 Span 1

name=B4/0/1

manufacturer=Digium

devicetype=Wildcard B410P

location=PCI Bus 17 Slot 01

basechan=1

totchans=3

irq=66

type=digital-TE

syncsrc=0

lbo=0 db (CSU)/0-133 feet (DSX-1)

coding_opts=B8ZS,AMI,HDB3

framing_opts=ESF,D4,CCS,CRC4

coding=AMI

framing=CCS

[2]

active=yes

alarms=RED

description=B4XXP (PCI) Card 0 Span 2

name=B4/0/2

manufacturer=Digium

devicetype=Wildcard B410P

location=PCI Bus 17 Slot 01

basechan=4

totchans=3

irq=66

type=digital-TE

syncsrc=0

lbo=0 db (CSU)/0-133 feet (DSX-1)

coding_opts=B8ZS,AMI,HDB3

framing_opts=ESF,D4,CCS,CRC4

coding=AMI

framing=CCS

[3]

active=yes

alarms=RED

description=B4XXP (PCI) Card 0 Span 3

name=B4/0/3

manufacturer=Digium

devicetype=Wildcard B410P

location=PCI Bus 17 Slot 01

basechan=7

totchans=3

irq=66

type=digital-TE

syncsrc=0

lbo=0 db (CSU)/0-133 feet (DSX-1)

coding_opts=B8ZS,AMI,HDB3

framing_opts=ESF,D4,CCS,CRC4

coding=AMI

framing=CCS

[4]

active=yes

alarms=RED

description=B4XXP (PCI) Card 0 Span 4

name=B4/0/4

manufacturer=Digium

devicetype=Wildcard B410P

location=PCI Bus 17 Slot 01

basechan=10

totchans=3

irq=66

type=digital-TE

syncsrc=0

lbo=0 db (CSU)/0-133 feet (DSX-1)

coding_opts=B8ZS,AMI,HDB3

framing_opts=ESF,D4,CCS,CRC4

coding=AMI

framing=CCS





Regarding the ?wctdm-? in dahdi_hardware output, I?ve found the following
error at ?dmesg?:

wctdm: probe of 0000:0a:00.0 failed with error -5





This A400E is a PCI Express card and I?ve tried to plug it in all 3 PCI
Express slots my server have (HP ML 110 G5) having the same problems. I?ve
even changed the card itself but still the same.



The versions I?m using are:

OS ? CentOS 5.3

Asterisk ? 1.6.0.5

Dahdi ? dahdi-linux-2.1.0.4 and dahdi-tools-2.1.0.2

Libpri ? 1.4.10

Asterisk add-ons ? asterisk-addons-1.4.8



Any idea on where the problem is? Does anybody knows what this error in
?dmesg? means? Could this problem affect B410P board (I suppose that no, but
just to be sure)?



Thanks and regards



Joan Antoni
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090817/46a724d2/attachment.htm

On Mon, Aug 17, 2009 at 10:10 AM, Joan Antoni Terre<nebheru at gmail.com>
wrote:
> Regarding the ?wctdm-? in dahdi_hardware output, I?ve found the following
> error at ?dmesg?:
>
> wctdm: probe of 0000:0a:00.0 failed with error -5
>
> This A400E is a PCI Express card and I?ve tried to plug it in all 3 PCI
> Express slots my server have (HP ML 110 G5) having the same problems. I?ve
> even changed the card itself but still the same.
>
>
> Any idea on where the problem is? Does anybody knows what this error in
> ?dmesg? means? Could this problem affect B410P board (I suppose that no,
but
> just to be sure)?
No, no idea what the problem is.
No, I don't know what that error means.
I don't know whether the problem could affect the B410P board.

Have you ever successfully used this particular kind of card in your
particular system? You could have something totally wacky going on
with firmware version conflict, IRQ conflict, etc.

You can usually get more output from the dahdi load by passing
arguments to the kernel module, like 'debug', etc. You can also try a
series of older versions of dahdi to see if you can get the card
working.

You could also have a dead card. I would ask the vendor for support
and see what they suggest. I've used multiple Digium-branded PCI /
PCI-e cards in my Dell systems and haven't had problems with the cards
getting detected.