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

[Armin Schindler]

On Fri, 21 Mar 2008, Roland Colberg wrote:
> Armin Schindler schrieb:
>> On Fri, 21 Mar 2008, Roland Colberg wrote:
>>> Armin Schindler schrieb:
>>>> On Fri, 21 Mar 2008, Roland Colberg wrote:
>>>>> Armin Schindler schrieb:
>>>>>> 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
>>>>>> 
>>>>>> _
>>>>> Thank you.
>>>>> 
>>>>> I installed that version (libcapi20-3.0.5-cm) and set the 
>>>>> /etc/capi20.conf:
>>>>> 
>>>>> TRACEFILE /var/log/capi20.log
>>>>> TRACELEVEL 2
>>>>> 
>>>>> but the log file remains empty.
>>>> Are you sure the program is using this lib and has write access to that
>>>> file/path?
>>>> 
>>>> Armin
>>>> 
>>> o.k., after changing the access rights there is binary data in the logfile 
>>> when
>>> starting or killing c2faxrecv, but nothing happens on incoming calls.
>>> 
>>> The Diva Card is connected to an internal S0-Bus, maybe this is a problem?
>> 
>> What do you mean? Do you think your internal S0-Bus is the problem?
>> I cannot help with that problem. Check the configuration of your PBX that
>> your calls are signaled at the internal S0-Bus.
>> 
>> Regarding the log file, this contains raw CAPI messages. If you sent me the 
>> binary, I can convert it easier.
>
> I don't think the PBX is misconfigured, because other ISDN Devices work 
> correctly on the internal S0-Bus.
>
> Now I made some tests regarding the trace file: starting or stopping only 
> c2faxrecv gives some short entries, but there are no entries on incoming 
> calls.
>
> When Asterisk is running simultanously, there are entries on every incoming 
> call. Nevertheless c2faxrecv doesn't pick up the call.
>
> I have attached 2 logfiles: one with TRACELEVEL 1 and the other with 2.

Man kann im Log sehen, dass sich Asterisk und eine andere Applikation 
(c2faxrecv) anmeldet. Aber diese andere Applikation sendet ein LISTEN_REQ 
nur einige Verbindungsarten:
    LISTEN REQ               AppID 0x0002 MsgNr 0x0001 CNTR: 0x00000001
     Info mask: 0x0
     CIP mask: 0x20012 (speech, 3.1 kHz audio, fax group 2/3)

Normalerweise reicht das auch. Aber per ISDN wird beim Anruf ein anderer CIP
gesetzt (das scheint speziell bei dieser Anlage so zu sein):
   CONNECT IND              AppID 0x0004 MsgNr 0x0000 PLCI: 0x00000101
     CIP value: 16 (telephony)

und da 'telephony' nicht mit angemeldet wurde, wird der Anruf nur an 
Asterisk signalisiert.
c2faxrecv muss also beim LISTEN_REQ in der CIP-mask das bit 16 mit setzen.


Armin