Re: The CAPI device is not present or accessible

Hans Petter Selasky schrieb:
> On Sunday 11 November 2007, Kristijan Vrban wrote:
>  
>> Hi, is just installed i4b, and  isdnconfig shows my
card:
>>
>> controller 0 = {
>>   Layer 1:
>>     description : HFC-2BDS0 128K PCI ISDN adapter
>>     type        : passive ISDN (Basic Rate, 2xB)
>>     channels    : 0x3
>>     serial      : 0xabcd
>>     power_save  : on
>>     dialtone    : enabled
>>     attached    : yes
>>     PH-state    : G3: Active
>>   Layer 2:
>>     driver_type : DRVR_DSS1_NT
>> }
>>
>> But when i try to start callweaver with the
chan_capi.callweaver, i get
>> this:
>>
>>  [chan_capi.so] => (Common ISDN API 2.0,
CAPI2.0, for OpenPBX)
>>   == Parsing '/usr/local/etc/callweaver/capi.conf':
Parsing
>> /usr/local/etc/callweaver/capi.conf - Found
>> Nov 11 19:45:04 WARNING[23320]: chan_capi.c:1434
capi_application_alloc:
>> The CAPI device is not present or accessible!
>> Nov 11 19:45:04 WARNING[23320]: chan_capi.c:8357
load_module: CAPI is
>> disabled!
>> Nov 11 19:45:04 WARNING[23320]: loader.c:348
__load_resource:
>> chan_capi.so: load_module failed, returning -1
>> Nov 11 19:45:04 WARNING[23320]: loader.c:488
load_modules: Loading
>> module chan_capi.so failed!
>>
>> What does the "capi20_is_installed"
function check to tell me: "No 
>> Chapi"
>> The capitest command is working
>>     
>
> This is a permissions issue.
>
> See "capi_delegate" in "man
isdnconfig". You need to delegate CAPI to 
> callweaver, hence it does not run like root 
>
> --HPS
>
>
>   
thanks, my bad habit to read only the firt 1/2 of the
manpages... But 
now the next error:

[chan_capi.so] => (Common ISDN API 2.0, CAPI2.0, for
OpenPBX)
 == Parsing '/usr/local/etc/callweaver/capi.conf': Parsing 
/usr/local/etc/callweaver/capi.conf - Found
 == Reading config for ISDN2
   -- config entry 'ISDN2' T=(*,isdn_in_nt,2) C=[0,0]
E=(0,0,64,1) 
G=(1.000000/1.000000) H=(0)
      > supplementary services : 0x00000061
   -- CAPI controller 0 supports:
[HOLD/RETRIEVE][CD][MCID][DTMF][echo 
cancellation][supplementary]
   -- listening on controller=0, cip_mask=0x1fff03ff
 == Registered channel type 'CAPI' (Common ISDN API 2.0
Driver )
 == Registered application 'capiCommand'
Nov 11 22:32:25 ERROR[24111]: chan_capi.c:8321 load_module:
Unable to 
register CAPI application
 == Unregistered channel type 'CAPI'
Nov 11 22:32:27 WARNING[24111]: chan_capi.c:8357
load_module: CAPI is 
disabled!
Nov 11 22:32:27 WARNING[24111]: loader.c:348
__load_resource: 
chan_capi.so: load_module failed, returning -1
Nov 11 22:32:27 WARNING[24111]: loader.c:488 load_modules:
Loading 
module chan_capi.so failed!

-- 
Kristijan Vrban

_______________________________________________
freebsd-isdnfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn

To unsubscribe, send any mail to
"freebsd-isdn-unsubscribefreebsd.org"

On Sunday 11 November 2007, Kristijan Vrban wrote:
> chan_capi.c:8321

I think you manually have to comment out the following line
in "chan_capi" and 
recompile:

chan_capi.c:8321

--HPS
_______________________________________________
freebsd-isdnfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn

To unsubscribe, send any mail to
"freebsd-isdn-unsubscribefreebsd.org"

Hans Petter Selasky schrieb:
> On Sunday 11 November 2007, Kristijan Vrban wrote:
>   
>> chan_capi.c:8321
>>     
>
> I think you manually have to comment out the following
line in "chan_capi" and 
> recompile:
>
> chan_capi.c:8321
>
> --HPS
>
>
>   

Yeah! It's running now! But I reckon iam the first person
running 
callweaver with chan_capi-hps? Or
one of an group <10. However, now i have and good BRI
solution *and* T.38

Kristijan
_______________________________________________
freebsd-isdnfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isdn

To unsubscribe, send any mail to
"freebsd-isdn-unsubscribefreebsd.org"