Re: c2faxrecv-mISDNcapid

Am 03.02.2018 um 14:25 schrieb Christoph Schulz:
>
>
>> Feb 01 17:25:07 arch c2faxrecv[3038]:             capi20.c:
>> 164              CapiDebug():[capi20_isinstalled]: other loop - module:
>> misdn
>> Feb 01 17:25:07 arch c2faxrecv[3038]:             capi20.c:
>> 164              CapiDebug():[capi20_isinstalled]: capi_fd: -1
>
> That's bad, because IsInstalled() returned an invalid file handle
> (-1). That happens if mISDNcapid is not running, or more exactly, if
> the corresponding UNIX socket cannot be opened (whose upstream path is
> /var/run/mISDNcapid/sock). And mISDNcapid is perhaps not running
> because /etc/capi20.conf did not contain the correct mISDN line, which
> must be
>
> mISDN 0 1 1
>
> or (shorter)
>
> mISDN 0
>
> assuming you have only one ISDN controller (ID 0) that you plan to use
> with mISDN.
 My /etc/capi20.conf:

debugmask 0x13  - example default debuglevel
mISDN 0 1 1  - first mISDN device is mapped to CAPI20 controller 1 and
enabled
mISDN 0 1 1  - second mISDN device is disabled for CAPI20

and yes I have only one controller.

During my research I tried to start capid without a /etc/capi20.conf,
cause  I read
that in this case both mISDN devices are enabled for the capi.
But the result in loading c2faxrecv-mISDNcapid wasnt deifferent against
the try
with /etc/capi20.conf

Thanks and regards


Jürgen



_______________________________________________
isdn4linux mailing list
[email protected]
https://www.isdn4linux.de/mailman/listinfo/isdn4linux