Your message dated Sat, 04 Apr 2020 21:13:32 +0200 with message-id <9ec1e06c8b9fb5fef57994628c1dfa9e2ee3e52b.ca...@eppesuigoccas.homedns.org> and subject line Re: Bug#515740: hylafax-server: COMREC error (code 72) with 4.4.4 + ELSA MicroLink has caused the Debian Bug report #515740, regarding hylafax-server: COMREC error (code 72) with 4.4.4 + ELSA MicroLink to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 515740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515740 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: hylafax-server Version: 2:4.4.4-10.1 Severity: normal Hi, [ This might be a modem issue, but the previous version of hylafax worked all right, so I guess something has changed :-) ] After upgrading my system to Debian Lenny (with Hylafax 4.4.4 (Debian version 2:4.4.4-10.1)), my ELSA MicroLink 56k can no longer receive incoming fax transmissions. Error message is=20 | [...] | Feb 16 14:38:33.99: [ 3358]: STATE CHANGE: ANSWERING -> RECEIVING | Feb 16 14:38:38.98: [ 3358]: --> [27:+FTI:" b.com Computer AG"] | Feb 16 14:38:38.98: [ 3358]: REMOTE TSI "b.com Computer AG" | Feb 16 14:38:38.98: [ 3358]: --> [20:+FCS:0,5,0,2,0,0,0,0] | Feb 16 14:38:38.98: [ 3358]: MODEM protocol botch, can not parse "0,5,0,2= ,0,0,0,0" | Feb 16 14:38:38.98: [ 3358]: REMOTE HANGUP: COMREC error (code 72) | ... I browsed the source code and I think this problem could be caused by "useJP" incorrectly set to true. In Class2Modem::parseRange, where +FCC is checked: Feb 17 10:39:20 tardis FaxGetty[18561]: <-- [9:AT+FCC=3D?\r] Feb 17 10:39:20 tardis FaxGetty[18561]: --> [45:(0,1),(0-5),(0-2),(0-2),(0)= ,(0),(0),(0-7),(0)] Feb 17 10:39:20 tardis FaxGetty[18561]: --> [2:OK] useJP is set to true # masked = 1; # if (vparseRange(cp, masked, 9, &n,&n,&n,&n,&n,&n,&n,&n,&p.jp)) { # useJP = true; In Class2Modem::parseClass2Capabilities when useJP is true, it requires 9 arguments for +FCS. The modem only returns 8 | [20:+FCS:0,5,0,2,0,0,0,0] Modem type: | "MicroLink 56k","Revision "Version 1.66 / 11.06.1999" I'm not sure if the analysis is correct, though. Does anyone know a workaround for the problem? Thanks in advance, Cheers, MB -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (700, 'stable'), (655, 'MB'), (200, 'testing'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.28.4-tardis (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages hylafax-server depends on: ii adduser 3.110 add and remove users and groups ii debconf [debconf-2 1.5.24 Debian configuration management sy ii ghostscript 8.62.dfsg.1-3.2lenny0 The GPL Ghostscript PostScript/PDF ii ghostscript-x [gs] 8.62.dfsg.1-3.2lenny0 The GPL Ghostscript PostScript/PDF ii gs 8.62.dfsg.1-3.2lenny0 Transitional package ii hylafax-client 2:4.4.4-10.1 Flexible client/server fax softwar ii libc6 2.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1.1 GCC support library ii libpam0g 1.0.1-5 Pluggable Authentication Modules l ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii libtiff-tools 3.8.2-11 TIFF manipulation and conversion t ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii mailutils [mailx] 1:1.2+dfsg1-4 GNU mailutils utilities for handli ii psmisc 22.6-1 Utilities that use the proc filesy ii sed 4.1.5-6 The GNU sed stream editor ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime hylafax-server recommends no packages. Versions of packages hylafax-server suggests: ii mgetty 1.1.36-1.5 Smart Modem getty replacement ii psrip 1.3-7 Extract images from PostScript fil -- debconf information: * hylafax-server/configure_note: hylafax-server/attachment: hylafax-server/start_now: true hylafax-server/setup_failed:
--- End Message ---
--- Begin Message ---Hi Michael, I noticed this bug report is still open while upstream already changed the source code with a similar patch to the one supplied at http://bugs.hylafax.org/show_bug.cgi?id=904. I am closing the bug report. Bye, Giuseppe
--- End Message ---
