Re: [hylafax-users] Unspecified Phase D error with MT5634ZBA-V92 MultiTech modem

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2004.07.27 09:43 Steve Melo wrote:
> Greetings,
>
> Recently I obtained a MT5634ZBA-V92 MultiTech modem as suggested in
> the
> mailing list. Since then I have been receiving "Unspecified Phase D
> error"
> and I wonder if there is something wrong with my setup.  I have the
> latest
> firmware 1.28H, running the modem in Class 2.1, with Hylafax 4.1.8.

> Jul 27 05:13:02.54: [ 1038]: SESSION BEGIN 00002865 ##########
> Jul 27 05:13:02.54: [ 1038]: HylaFAX (tm) Version 4.1.8
> Jul 27 05:13:02.54: [ 1038]: <-- [19:AT+FCC=,,,,,,,,0;A\r]
> Jul 27 05:13:16.65: [ 1038]: --> [4:+FCO]
> Jul 27 05:13:16.65: [ 1038]: ANSWER: FAX CONNECTION  DEVICE
> '/dev/ttyS0'
> Jul 27 05:13:16.65: [ 1038]: STATE CHANGE: ANSWERING -> RECEIVING
> Jul 27 05:13:16.65: [ 1038]: MODEM input buffering enabled
> Jul 27 05:13:16.65: [ 1038]: RECV FAX: begin
> Jul 27 05:13:16.65: [ 1038]: --> [27:+FTI:"        ### #######"]
> Jul 27 05:13:16.65: [ 1038]: REMOTE TSI "### #######"
> Jul 27 05:13:16.65: [ 1038]: --> [22:+FCS:0,B,0,2,3,1,0,0,0]
> Jul 27 05:13:16.65: [ 1038]: REMOTE wants 28800 bit/s
> Jul 27 05:13:16.65: [ 1038]: REMOTE wants page width 1728 pixels in
> 215 mm
> Jul 27 05:13:16.65: [ 1038]: REMOTE wants unlimited page length
> Jul 27 05:13:16.65: [ 1038]: REMOTE wants 3.85 line/mm
> Jul 27 05:13:16.65: [ 1038]: REMOTE wants 2-D MMR
> Jul 27 05:13:16.65: [ 1038]: REMOTE wants T.30 Annex A, ECM
> Jul 27 05:13:16.65: [ 1038]: --> [2:OK]
> Jul 27 05:13:16.65: [ 1038]: <-- [7:AT+FDR\r]
> Jul 27 05:13:21.81: [ 1038]: --> [7:+FHS:A0]
> Jul 27 05:13:21.81: [ 1038]: REMOTE HANGUP: Unspecified Phase D error
> (codeA0)

"Unspecified Phase D error" means that there was an error in phase D 
(the post-page message portion).  In this case it used V.34 and ECM and 
we didn't get any page image data at all, so it would indicate that the 
error was with the partial page signal or with an associated V.34 
signal.  In any case, we can't tell much from Class 2/2.0/2.1 logs.  
MultiTech would have to help you if you want to continue with Class 2.1.

That said, the problem probably has to do with a firmware flaw in the 
ECM or V.34-Fax implementations.  So you could switch to Class 2.0 and 
see if the problem goes away, or you could disable ECM and do likewise.

However, my personal recommendation would be for you to upgrade to 
4.2.0 and then switch to Class 1.0.  You'll have all of the features 
that you get in Class 2.1 with that modem, plus you'll have more 
resolution capability.  Oh, and we'll be able to help you out much more 
in Class 1/1.0 than we can in Class 2/2.0/2.1.

Lee.

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