[Asterisk-Users] Setting up an EICON CARD with CAPI

[cédric Buzay]

Hi everybody.

I'm trying to setting up a V4 BRI EICON card on ASTERISK 1.0.7
My linux is a debian.
It was working during a few days an suddenly (after a lot of reboot)
I've got this error message that seems to be very popular but I couldn't
find any
answer on the net :

==============================================.
Asterisk Dynamic Loader Starting:
  == Parsing '/etc/asterisk/modules.conf': Found
[chan_capi.so] => (Common ISDN API for Asterisk)
  == Parsing '/etc/asterisk/capi.conf': Found
Feb 21 03:08:34 NOTICE[10319]: chan_capi.c:2645 load_module: unable to
listen!
Feb 21 03:08:34 WARNING[10319]: loader.c:345 ast_load_resource:
chan_capi.so: load_module failed, returning -1
  == Unregistered channel type 'CAPI'
Feb 21 03:08:34 WARNING[10319]: loader.c:391 load_modules: Loading
module chan_capi.so failed!
===============================================

I've got all the persmissions on the .conf files and on the /dev/capi20

my drivers are those :
dmesg | grep -i capi
Eicon DIVA - CAPI Interface driver (http://www.melware.net)
divacapi: Rel:2.0  Rev:1.24  Build: 105-75(local)
divacapi: module unloaded.
Eicon DIVA - CAPI Interface driver (http://www.melware.net)
divacapi: Rel:2.0  Rev:1.24  Build: 105-75(local)

and they work at a CAPI  level :

Update CFGLib information ... succeeded
Start adapter Nr:1 - 'Diva Server V-4BRI-8', SN: 23208 ... OK (already
active)
  Successfully updated configuration of Diva Server V-4BRI-8 PORT: 0 SN:
  Successfully updated configuration of Diva Server V-4BRI-8 PORT: 1 SN:
  Successfully updated configuration of Diva Server V-4BRI-8 PORT: 2 SN:
  Successfully updated configuration of Diva Server V-4BRI-8 PORT: 3 SN:
  Successfully updated configuration of Diva TTY driver
  Successfully updated configuration of Diva MTPX driver
  Successfully updated configuration of Diva CAPI driver

My modules.conf seems correct:
=================================================
[....]
noload => app_intercom.so
;
; Explicitly load the chan_modem.so early on to be sure
; it loads before any of the chan_modem_* 's afte rit
;
;load => chan_modem.so
;load => res_musiconhold.so
load => chan_capi.so
;
; Load either OSS or ALSA, not both
; By default, load OSS only (automatically) and do not load ALSA
;
noload => chan_alsa.so
noload => chan_oss.so

;
; Module names listed in "global" section will have symbols globally
; exported to modules loaded after them.
;
[global]
;chan_modem.so=yes
chan_capi.so=yes

And my capi.conf also :

;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8

[interfaces]
msn=0MYNUMBER0
incomingmsn=*
controller=1
;softdtmf=1
;accountcode=
context=demo
;echosquelch=1
echocancel=yes
;echotail=64
;callgroup=1
;deflect=12345678
devices=2
=================================================

Any ideas ???

Thanks

Cédric