HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Problem with adaptuve answer



On Wed, 02 Mar 2005 17:40:17 +0100, Sam Przyswa <samp@xxxxxxxxxxxxxxxxx> wrote:
> Hi,
> 
> I have a problem with the adaptive answering with severals modems able
> to accept the AT+FAA=1 command, as the modem CONEXANT
> V90/ACF3_V1.702A-V90_P21_FSH, with this modem when I call for data
> On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
>  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*

I think you'll have an hard time :-)

First, you need to setup GettyArgs properly to hand off data calls to
the proper getty.

Second, you need to make adaptive answer work in the first place.

Here are some notes I wrote for my own reference about AA and conexant
based modems (maybe something is changed with new firmware, so you can
try and see it):

1) when you get a fax call the modem will report
ATA
FAX
CONNECT
Note: see if this is true for your modem too by waiting on it with cu/minicom

2) when you get a data call the modem will report
ATA
DATA
Note:
- you don't get "CONNECT"
- see if this is true for your modem too by waiting on it with cu/minicom

Based on the above observations (if you get the same behavior),
a) when the call is fax you'd have to use ModemWaitForConnect:
ModemWaitForConnect:   yes
ModemSetupAACmd:       AT+FCLASS=0;+FAE=1
b) when the call is data you'd need
ModemWaitForConnect:   no
ModemSetupAACmd:       AT+FCLASS=0;+FAE=1
so effectively, it's a bit impossible to make it work at least it was
last time I tried

If you see that your modem behaves exactly like mines, and you really
need adaptive answer, you can try:
- ModemWaitForConnect:   yes
- then use the following patch to use waitforconnect only for fax
calls (NOTE: it may/will break adaptive answer for other chipsets; it
was just a quick fix I tried before I decided to avoid adaptive answer
on rockwell chipsets due to the fact that the reliability was not so
perfect, again this was with the firmware I had at the time)

====
--- faxd/ClassModem.c++.orig    Thu May  6 22:29:15 2004
+++ faxd/ClassModem.c++ Fri May  7 12:15:29 2004
@@ -231,7 +231,10 @@
        break;
    const AnswerMsg* am = findAnswer(rbuf);
    if (am != NULL) {
-       if (am->expect != AT_NOTHING && conf.waitForConnect) {
+       if (am->expect != AT_NOTHING
+           // rockwell bug: no CONNECT after DATA
+           && am->type == CALLTYPE_FAX
+           && conf.waitForConnect) {
        /*
         * Response string is an intermediate result that
         * is only meaningful if followed by AT response
===


-- 
giulioo@xxxxxxxxx

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*




Project hosted by iFAX Solutions