Re: [hylafax-users] Adaptive answer, MT5634ZBA-V92 (was Receive problems with MT2834ZDX modems)

[Bill Campbell <hylafax@xxxxxxxxxxxxx>]

On Tue, Mar 21, 2006, Lee Howard wrote:
>Bill Campbell wrote:
>
>>I received the MT5634ZBA-V92 yesterday, and have spent the better part of
>>two days trying to figure out how to get it to work with adaptive answer as
>>it needs to accept data calls as well as faxes.
>>
>>The only thing I've found that gets data calls to work is to use
>>``ModemSetupAACmd: AT%A1+FAA=1'' which causes HylaFAX to hand data
>>connections off to getty properly.  Unfortunately fax calls then fail.  If
>>I leave out ModemSetupAACmd, faxes are handled properly, but data calls
>>fail.  I have tried various combinations of ModemAnswerCmd,
>>ModemAnswerDataCmd, and ModemAnswerFaxCmd with no success.
>> 
>>
>
>I've used the MT5634ZBA-V92 for data, voice, and fax... and it worked 
>well in all of those, but I've never used it with all of those on the 
>same line and modem with adaptive answer.
>
>You *are* going to need to use ModemSetupAACmd to get things to work... 
>or at least you're going to need to minimally put AT+FAA=1 somewhere in 
>the initialization sequence.
>
>After setting "ModemSetupAACmd: AT+FAA=1" what does a fax call session 
>log look like that fails?

Here's the log on the receiving side with ModemSetupAACmd: AT%A1+FAA=1.
Leaving off that %A1 results in a somewhat different error, and data calls
don't work at all.

Mar 21 15:18:03.18: [15400]: SESSION BEGIN 000005520 12062329186
Mar 21 15:18:03.18: [15400]: HylaFAX (tm) Version 4.2.3
Mar 21 15:18:03.18: [15400]: <-- [14:AT+FCLASS=1;A\r]
Mar 21 15:18:11.56: [15400]: --> [3:FAX]
Mar 21 15:18:11.56: [15400]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS0'
Mar 21 15:18:11.56: [15400]: RECV FAX: begin
Mar 21 15:18:11.56: [15400]: <-- data [32]
Mar 21 15:18:11.56: [15400]: <-- data [2]
Mar 21 15:18:11.56: [15400]: --> [3:FAX]
Mar 21 15:18:11.56: [15400]: DELAY 1500 ms
Mar 21 15:18:13.06: [15400]: <-- [9:AT+FTH=3\r]
Mar 21 15:18:13.06: [15400]: --> [6:^H ^H^H ^H]
Mar 21 15:18:13.06: [15400]: DELAY 1500 ms
Mar 21 15:18:14.56: [15400]: <-- [9:AT+FTH=3\r]
Mar 21 15:18:14.56: [15400]: --> [5:ERROR]
Mar 21 15:18:14.56: [15400]: RECV FAX: RSPREC error/got EOT
Mar 21 15:18:14.56: [15400]: RECV FAX: end
Mar 21 15:18:14.56: [15400]: SESSION END

Here's the sending log (MT2834ZDXb with Hylafax)

Mar 21 15:17:49.01: [24363]: SESSION BEGIN 000000128 12062329186
Mar 21 15:17:49.01: [24363]: HylaFAX (tm) Version 4.2.3
Mar 21 15:17:49.01: [24363]: SEND FAX: JOB 87 DEST 232-9186 COMMID 000000128 DEVICE '/dev/ttyS0' FROM 'Bill Campbell <bill@xxxxxxxxxxxxxxxxxxxxx>' USER bill
Mar 21 15:17:49.01: [24363]: <-- [9:AT+FLO=1\r]
Mar 21 15:17:49.18: [24363]: --> [2:OK]
Mar 21 15:17:49.18: [24363]: <-- [10:AT+FTBC=0\r]
Mar 21 15:17:49.34: [24363]: --> [2:OK]
Mar 21 15:17:49.34: [24363]: <-- [10:AT+FBOR=0\r]
Mar 21 15:17:49.51: [24363]: --> [2:OK]
Mar 21 15:17:49.51: [24363]: <-- [13:AT+FPHCTO=30\r]
Mar 21 15:17:49.67: [24363]: --> [2:OK]
Mar 21 15:17:49.67: [24363]: <-- [24:AT+FDCC=1,5,2,2,2,0,0,0\r]
Mar 21 15:17:49.84: [24363]: --> [2:OK]
Mar 21 15:17:49.84: [24363]: DIAL 2329186
Mar 21 15:17:49.84: [24363]: <-- [17:ATDTW*70W2329186\r]
Mar 21 15:18:49.19: [24363]: --> [5:+FCON]
Mar 21 15:19:17.99: [24363]: --> [8:+FHNG:11]
Mar 21 15:19:18.00: [24363]: REMOTE HANGUP: No answer (T.30 T1 timeout) (code 11)
Mar 21 15:19:18.00: [24363]: SEND FAILED: JOB 87 DEST 232-9186 ERR No answer (T.30 T1 timeout)
Mar 21 15:19:18.00: [24363]: <-- [5:ATH0\r]
Mar 21 15:19:22.99: [24363]: MODEM <Timeout>
Mar 21 15:19:22.99: [24363]: SESSION END

The time on each of these systems is sync'ed with NTP.

>ModemAnswerDataCmd and ModemAnswerFaxCmd are used in conjuntion with 
>AdaptiveAnswer and AnswerRotary and DistinctiveRings, and I don't think 
>you want AdaptiveAnswer/AnswerRotary.  (Don't confuse 
>AdaptiveAnswer+AnswerRotary with ModemSetupAACmd - the first is an 
>adaptive answering mechanism performed by faxgetty answering the calls 
>in different ways and the second is an adaptive answering mechanism 
>performed by the modem listening to the call and trying to determine the 
>call type from the audio.)  I've never used AnswerRotary, but the idea 
>behind it is that as calls come in (perhaps just failed ones) faxgetty 
>will rotate through the rotary with different ways to answer the call.  
>Therefore if, for some reason, a call fails to negotiate it will rotate 
>to the next AnswerCmd and perhaps that will allow the answer to be 
>successful.
>
>As for DistinctiveRings, you say below that you have distinctive ring 
>support, so...
>
>>I've tried Class1RecvIdentTimer, AdaptiveAnswer, and AnswerRotary, but
>>these never handed data calls off to getty.
>> 
>>
>
>All of these are part of the faxgetty adaptive answering with rotary 
>approach, and I don't think that these are what you want.  I think that 
>you want modem-based adaptive answering.
>
>>We have distinctive lines with two phone numbers coming into the fax modem
>>so I tried DistinctiveRings, with DRingOn and DRingOff, which would come up
>>with things like ``WFR: received cadence 20, 0, 0, 0, 0'', ``ANSWER: Ring
>>detected without successful handshake'' even though I had DistintiveRings
>>``D-20,F-8'' which I think should have been a data call.
>>
>
>I suspect that you can use ModemSetupAACmd in conjuction with 
>DistinctiveRings, but I don't think that you would want to.  If you have 
>DistinctiveRing support then certainly it's what you want to use instead 
>of anything else.

That makes sense to me as well, but I haven't been able to get distinctive
ring to recognize the ring patterns at all.

Bill
--
INTERNET:   bill@xxxxxxxxxxxxx  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676

The most serious doubt that has been thrown on the authenticity of the
biblical miracles is the fact that most of the witnesses in regard to
them were fishermen.
		-- Arthur Binstead

____________________ 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*