[Asterisk-Users] Re: Asterisk and Capi

[Bruno Hertz]

On Thu, 2004-12-23 at 19:28 +0100, Aldo Bergamini wrote:

> [app_capiCD.so]Dec 23 19:21:45 WARNING[1076850816]: loader.c:242
> ast_load_resource: /usr/lib/asterisk/modules/app_capiCD.so: undefined
> symbol: capidebug
> Dec 23 19:21:45 WARNING[1076850816]: loader.c:423 load_modules: Loading
> module app_capiCD.so failed!
> 

Hi Aldo

don't know about Suse, but I have a working setup with asterisk 1-0
stable, chan_capi 0.3.5 and fcpci-suse9.1-3.11-02 on Debian Sarge,
though not prepackaged but all self compiled.

Looking at your log messages, chan_capi obviously is installed, but the
load of app_capiCD.so fails due to an undefined symbol capidebug.

This symbol should be defined in chan_capi.so, which has to be loaded
before app_capiCD.so. I.e. the load order on my box looks like:

[chan_capi.so] => (Common ISDN API for Asterisk)
  == Parsing '/opt/asterisk/etc/asterisk/capi.conf': Found
  == ast_capi_pvt(0439602910,9602910,isdn-in,0,2) (1,2,64)
  == ast_capi_pvt(0439602910,9602910,isdn-in,0,2) (1,2,64)
    -- listening on contr1 CIPmask = 0x1fff03ff
  == Registered channel type 'CAPI' (Common ISDN API Driver (0.3.5) aLaw CVS HEAD)
[app_capiCD.so] => ((CAPI*) Call Deflection, the magic thing.)
  == Registered application 'capiCD'
[app_capiHOLD.so] => ((CAPI*) HOLD)
  == Registered application 'capiHOLD'
[app_capiRETRIEVE.so] => ((CAPI*) RETRIEVE)
  == Registered application 'capiRETRIEVE'
[app_capiECT.so] => ((CAPI*) ECT)
  == Registered application 'capiECT'
[app_capiMCID.so] => ((CAPI*) Malicious Caller ID, the evil thing.)
  == Registered application 'capiMCID'
[app_capiNoES.so] => ((CAPI*) No Echo Suppression.)
  == Registered application 'capiNoES'

So either your modules.conf is messed up, or there's a problem with the
chan_capi package itself, which you should then report to Suse.

But take a look at your modules.conf. I myself have autoload enabled, and
all works automagically. Maybe you have it disabled, and the module load
order is affected by this .... ?

Also, you can check if you like wether the symbol is actually defined in
chan_capi.so:
# nm chan_capi.so | grep capidebug
00010720 B capidebug

If you see a 'U' instead of a 'B' there, your chan_capi package is messy.

Regards, Bruno.