Re: c2faxrecv-mISDNcapid

Christoph Schulz <[email protected]> Sat, 03 Feb 2018 14:25:18 +0100

Newsgroups	gmane.linux.isdn.i4l.user
Message-ID	<20180203142518.Horde.JoO5H5s7LyJml_KLFbHPBEA@localhost>

Hello!

jm <[email protected]> schrieb am Fr 02 Feb 2018 04:48:04 CET:

>> You will need a line like "mISDN 0" in your /etc/capi20.conf /
>> Du wirst eine Zeile wie "mISDN 0" in deiner /etc/capi20.conf benötigen.
>
> Can you tell me this more verbose.

Well, your first log contained the lines:

>             capi20.c: 164              CapiDebug():[capi20_isinstalled]:
> other loop - module: misdn
>             capi20.c: 164              CapiDebug():[capi20_isinstalled]:
> capi_fd: 5

That's from capiinfo, and that's good -- IsInstalled() returned a file  
handle (5).

However, in your invocation of c2faxrecv-mISDNcapid, the log contained  
the lines:

> 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.


Regards,

Christoph Schulz

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

signature.asc (application/pgp-signature, 213 B)