Microlink Office

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

hi,

On Tue, Nov 02, 1999 at 09:15:01PM +0100, Sascha Ziemann wrote:
> I am working on a small tool for the ELSA Microlink Office to download
> fax pages and run mgettys new_fax.  My code reads some pages from the
> modem, but I have no information about the file format.  The file
> contains AT commands and binary data mixed.  The following dump shows
> the beginning of a file:
> 
> 00000000    0d0a 2b46 434f 0d0a  0d0a 2b46 5449 3a22    ..+FCO....+FTI:"
> 00000010    3439 2035 3639 2031  3430 3420 2020 2020    49 569 1404     
> 00000020    2020 2020 220d 0a0d  0a2b 4643 533a 312c        "....+FCS:1,
> 00000030    352c 302c 322c 302c  302c 302c 300d 0a0d    5,0,2,0,0,0,0...
> 00000040    0a4f 4b0d 0a0d 0a2b  4644 520d 0a0d 0a43    .OK....+FDR....C
> 00000050    4f4e 4e45 4354 0d0a  0080 b259 0150 362b    ONNECT.....Y.P6+

Actually, it's just what the modem would send to sendfax in a normal class
2.0 conversation.  Everything after the CONNECT[0d][0a] is G3 data, up to
a <DLE><ETX> sequence.  (Normal <DLE> characters are doubled).  See the
reception code in sendfax how to handle <DLE>.

After DLE ETX, the next few status responses are sent, and then a new
page starts.

If you can keep your patience for maybe two more weeks, I shall have my
MLO tool ready, which will properly decode this :-)

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de