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

[Roland Colberg]

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.


Roland
-------------- nächster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : capi20.log_1
Dateityp    : application/octet-stream
Dateigr??e  : 3634 bytes
Beschreibung: nicht verf?gbar
URL         : http://lists.melware.net/pipermail/chan-capi-users/attachments/20080321/c104e6e2/attachment.obj 
-------------- nächster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : capi20.log_2
Dateityp    : application/octet-stream
Dateigr??e  : 1157 bytes
Beschreibung: nicht verf?gbar
URL         : http://lists.melware.net/pipermail/chan-capi-users/attachments/20080321/c104e6e2/attachment-0001.obj