Asterisk – 1.8.4.1
Dahdi-linux – 2.4.1.2
Dahdi-tools – 2.4.1
Kernel: 2.6.37.6
Kernel BKL: enabled

I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog
card with 1 FXO and 1FXS module.

This server has been running just fine for two years with Asterisk 1.6.1.0

I’ve just upgraded all the OS and installed Asterisk 1.8.4.1. On trying
to configure the A400P I get:

# modprobe dahdi

# modprobe wctdm

# dahdi_genconf
Empty configuration — no spans
Empty configuration — no spans

# dahdi_cfg -vvv
DAHDI Tools Version – 2.4.1

DAHDI Version: 2.4.1.2
Echo Canceller(s):
Configuration
======================

Channel map:

0 channels to configure.

# dahdi_hardware
driver should be ‘wctdm’ but is actually ‘netjet’
pci:0000:01:09.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F

Where am I going wrong? Why is dahdi_genconf not seeing the card, when
dahdi_hardware does see it? I’ve tried “modprobe netjet”, but makes no
difference.

Thanks for any suggestions,

Sebastian

I now have an OpenVox A400P and it is working well. Thanks to Ade
Vickers for the recommendation, which I second.

However, I need to make a slow transition between a conventional
multiple-extension setup and a full VoIP network on these premises. So
at the moment the Asterisk box shares the PSTN connection with several
conventional analogue handsets.

The desired result for an incoming call is that the Asterisk server will
wait N seconds before answering (which I can arrange easily enough), and
if the call has been answered on one of the handsets by that time the
Asterisk server should ignore it completely. Otherwise it should start
checking CLID, prompting for extensions, and other good stuff, which
again I know how to do.

What is a good approach to making sure the Asterisk server doesn’t pick
up a call that has been answered elsewhere? (Ideally in pure dialplan,
but a perl AGI would also do.)

R

Roger Burton West wrote:

> I want to hook one of them to the PSTN. Given that I am in
> the UK, what is a reasonably easily-available device to
> provide an FXO interface from a Linux box, with a minimum of
> faffing around with drivers? Just one line is needed, though
> in theory two might eventually be useful. My usual white-box
> hardware suppliers don’t seem to play in this field.

I’ve had good experiences with an OpenVox A400P, once you’ve done the “Dahdi
dance”, it settles down to be very reliable. Reasonable price, too. I bought
mine from Voipon, although I’m sure a bit of shopping around will find other
vendors.

Cheers,
Ade.