[chan-capi-users] No fax reception with chan-capi, divas4linux and c2faxrecv

[Armin Schindler]

On Tue, 18 Mar 2008, Roland Colberg wrote:
> Armin Schindler schrieb:
>> On Sun, 16 Mar 2008, Roland Colberg wrote:
>>> Hi,
>>>
>>> due to problems with Asterisk and Hylafax simultaneous on an AVM B1 I switched to a
>>> Diva Server BRI.
>>>
>>> Manufacturer: Eicon Networks
>>> CAPI Version: 2.0
>>> Manufacturer Version: 3.0
>>> Serial Number: 17
>>> BChannels: 2
>>>
>>>
>>> I have installed chan_capi-1.1.0 and divas4linux-melware-3.0.10-107.884-1, not using
>>> iaxmodem.
>>>
>>> So Asterisk is working as well as sending faxes, but capi4hylafax (c2faxrecv) doesnt
>>> pickup incoming calls.
>>>
>>> Strangely there is no output of any ISDN calls in /var/log/messages,
>>> /var/log/isdn.log or other log-files. Maybe this is the reason of the disfunction, so
>>> that c2faxrecv gets no signal of the incoming calls.
>>>
>>> Whats wrong??
>>
>> It sounds like c2faxrecv is not configured to pickup a call. Did you
>> configure the correct MSN and controller to listen on?
>> /var/log/messages may not show incoming calls. This depend on the programs
>> and their configuration.
>> I don't know much about the capi4hylfax stuff, but I think this tool has own
>> log file. Maybe more help is possible if you provide the configuration of
>> it.
>>
>> Armin
>
> This is my config file (now /etc/config.faxCAPI in openSuSE 10.3) without comments:
>
> SpoolDir:               /var/spool/fax
> FaxRcvdCmd:             /var/spool/fax/bin/faxrcvd
> PollRcvdCmd:             /var/spool/fax/bin/pollrcvd
> FaxReceiveUser:         fax
> FaxReceiveGroup:        dialout
> LogFile:                /var/log/capifax.log
> LogTraceLevel:          4
> LogFileMode:            0644
> {
>     HylafaxDeviceName:          faxCAPI
>     RecvFileMode:               0644
>     FAXNumber:                  +49.xxxx.668518
>     LocalIdentifier:            "xxxxxxxxxxxxxx"
>     MaxConcurrentRecvs:         2
>     OutgoingController:         1
>     OutgoingMSN:                668518
>     SuppressMSN:                0
>     NumberPrefix:
>     UseISDNFaxService:          0
>     RingingDuration:            0
>     {
>         Controller:             1
>         AcceptSpeech:           1
>         UseDDI:                 0
>         DDIOffset:              "12345"
>         DDILength:              3
>         IncomingDDIs:
>         IncomingMSNs:           668518
>         AcceptGlobalCall:   1
>     }
> }
>
> Starting c2faxrecv gives:
>
> asterisk:~ # c2faxrecv -v
> The config file is /etc/config.faxCAPI.
>
> C4H-Version 01.03.00 (32Bit).
>
> The SpoolDirectory is /var/spool/fax.
> Changed to effective user "fax" and group "dialout" succesfully.
>
> Device "faxCAPI" uses 2 receive thread(s) with the following config:
> Controller=1 : IncomingMSNs=668518
>
> Started in Hylafax mode and waiting on incoming calls.
>
>
> This looks o.k., I think. Nevertheless hylafax doesn't pick up the 668518. The same
> configuration works with an AVM B1. Leaving IncomingMSNs empty (= accept all) also
> doesn't help.

The configuration looks good. So if the MSN is correct (as signaled on 
incoming call) and you don't have any log, the only way to find out is to 
have a look at the CAPI messages. I think capi4hylfax doesn't provide this
trace, so you could use the libcapi20 version from ftp.melware.net. This
libcapi20 can create CAPI message traces (if enabled in a special config 
file).

Armin