hylafax-devel Mailing List for HylaFAX
Brought to you by:
faxguy
Menu
▾
▴
hylafax-devel — discussion on the development of HylaFAX
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(15) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(23) |
Aug
(1) |
Sep
(6) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2015 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
(5) |
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Paweł U. <pa...@ur...> - 2023-03-22 14:05:17
|
Hello, Yes, it will work. It is not the topic for the devel group. -- Pawel From: kaan.sayim--- via hylafax-devel <hyl...@li...> Sent: Wednesday, March 22, 2023 1:35 PM To: hyl...@li... Subject: [hylafax-devel] Hylafax+ SIP Trunk Hello all, We want to use hylafax+ application in Vcenter virtual server with SIP trunk connection. Is there anyone which have done that kind of installation and succeed? Thank you for your help. Best regards. Kaan <http://image.teb.com.tr/TEBMailSignature/Banka/e-imza-logo.jpg> Kaan Sayım Uygulama Yönetimi Proje Sorumlusu Uygulama Yönetimi Birimi Genel Müdürlük T: +90 (216) 645 24 83 - F: +90 (216) 636 36 36 kaa...@te... <mailto:kaa...@te...> teb.com.tr <http://www.teb.com.tr> <http://image.teb.com.tr/TEBMailSignature/agac.jpg> Lütfen gerekli olmadıkça bu dokümanın kağıt çıktısını almayın, doğayı koruyun. _____ Bu elektronik posta mesajı ve ekleri sadece gönderildiği kişi veya kuruma özeldir ve gizli bilgiler içerebilir. Eğer bu mesajı hataen aldıysanız lütfen bu durumu gönderen kişiye derhal bildiriniz ve mesajı sisteminizden siliniz. Eğer doğru kişiye ulaşmadığını düşünüyorsanız, bu mesajın gizlenmesi, yönlendirilmesi, kopyalanması veya herhangi bir şekilde kullanılması yasaktır. Internet iletişiminde güvenlik ve hatasız gönderim garanti edilemeyeceğinden, mesajın yerine ulaşmaması, geç ulaşması, içeriğinin bozulması ya da mesajın virüs taşıması gibi problemler oluşabilir. Gönderen taraf bu tip sorunlardan sorumlu tutulmaz. Türk Ekonomi Bankası A.Ş. Ticaret Sicil No: 189356 Mersis No: 0876004342000105 TEB Kampüs C ve D Blok Saray Mah. Sokullu Cad. No:7A - 7B Ümraniye 34768 / İSTANBUL www.teb.com.tr <http://www.teb.com.tr> This e-mail message and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this message in error, please notify the sender immediately and delete it from your system. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is prohibited. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The sender therefore does not accept liability for any errors or omissions in the context of this message which arise as a result of Internet transmission Türk Ekonomi Bankası A.Ş. Trade Registry Number: 189356, Central Registration System Number: 0876004342000105 TEB Kampüs C ve D Blok Saray Mah. Sokullu Cad. No:7A - 7B Ümraniye/ İSTANBUL/Turkey www.teb.com.tr <http://www.teb.com.tr> |
|
From: <kaa...@te...> - 2023-03-22 12:53:11
|
Hello all, We want to use hylafax+ application in Vcenter virtual server with SIP trunk connection. Is there anyone which have done that kind of installation and succeed? Thank you for your help. Best regards. Kaan [http://image.teb.com.tr/TEBMailSignature/Banka/e-imza-logo.jpg] Kaan Say?m Uygulama Y?netimi Proje Sorumlusu Uygulama Y?netimi Birimi Genel M?d?rl?k T: +90 (216) 645 24 83 - F: +90 (216) 636 36 36 kaa...@te...<mailto:kaa...@te...> teb.com.tr<http://www.teb.com.tr> [http://image.teb.com.tr/TEBMailSignature/agac.jpg]L?tfen gerekli olmad?k?a bu dok?man?n ka??t ??kt?s?n? almay?n, do?ay? koruyun. ________________________________ Bu elektronik posta mesaj? ve ekleri sadece g?nderildi?i ki?i veya kuruma ?zeldir ve gizli bilgiler i?erebilir. E?er bu mesaj? hataen ald?ysan?z l?tfen bu durumu g?nderen ki?iye derhal bildiriniz ve mesaj? sisteminizden siliniz. E?er do?ru ki?iye ula?mad???n? d???n?yorsan?z, bu mesaj?n gizlenmesi, y?nlendirilmesi, kopyalanmas? veya herhangi bir ?ekilde kullan?lmas? yasakt?r. Internet ileti?iminde g?venlik ve hatas?z g?nderim garanti edilemeyece?inden, mesaj?n yerine ula?mamas?, ge? ula?mas?, i?eri?inin bozulmas? ya da mesaj?n vir?s ta??mas? gibi problemler olu?abilir. G?nderen taraf bu tip sorunlardan sorumlu tutulmaz. T?rk Ekonomi Bankas? A.?. Ticaret Sicil No: 189356 Mersis No: 0876004342000105 TEB Kamp?s C ve D Blok Saray Mah. Sokullu Cad. No:7A - 7B ?mraniye 34768 / ?STANBUL www.teb.com.tr <http://www.teb.com.tr> This e-mail message and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this message in error, please notify the sender immediately and delete it from your system. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is prohibited. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The sender therefore does not accept liability for any errors or omissions in the context of this message which arise as a result of Internet transmission T?rk Ekonomi Bankas? A.?. Trade Registry Number: 189356, Central Registration System Number: 0876004342000105 TEB Kamp?s C ve D Blok Saray Mah. Sokullu Cad. No:7A - 7B ?mraniye/ ?STANBUL/Turkey www.teb.com.tr <http://www.teb.com.tr> |
|
From: Lee H. <fa...@ho...> - 2023-02-18 06:04:36
|
Thank you. The patch has been committed to the SVN repository and will be in the next release. See: https://sourceforge.net/p/hylafax/HylaFAX+/2704/ Lee. On 2/17/23 12:26 PM, Florian Weimer wrote: > We are porting Fedora to future C compilers, and our hylafax+ package > has issues that might cause build failures or incorrect feature > detection because it relies on support for implicit ints and implicit > function declarations in the compiler. > > The attached patch tries to address the issues in the configure script. > I think it still applies to the current sources in Subversion. > > More information about the Fedora efforts is available here: > > <https://fedoraproject.org/wiki/Changes/PortingToModernC> > <https://fedoraproject.org/wiki/Toolchain/PortingToModernC> > > Thanks, > Florian > > > _______________________________________________ > hylafax-devel mailing list > hyl...@li... > https://lists.sourceforge.net/lists/listinfo/hylafax-devel |
|
From: Florian W. <fw...@re...> - 2023-02-17 20:26:26
|
We are porting Fedora to future C compilers, and our hylafax+ package has issues that might cause build failures or incorrect feature detection because it relies on support for implicit ints and implicit function declarations in the compiler. The attached patch tries to address the issues in the configure script. I think it still applies to the current sources in Subversion. More information about the Fedora efforts is available here: <https://fedoraproject.org/wiki/Changes/PortingToModernC> <https://fedoraproject.org/wiki/Toolchain/PortingToModernC> Thanks, Florian |
|
From: Lee H. <fa...@ho...> - 2023-01-05 21:52:01
|
I've committed the following according to recommendations by libtiff developers: https://sourceforge.net/p/hylafax/HylaFAX+/2695/ Thanks, Lee. |
|
From: Nico Kadel-G. <nk...@gm...> - 2023-01-05 00:42:51
|
On Wed, Jan 4, 2023 at 5:09 PM Lee Howard <fa...@ho...> wrote: > > On 1/1/23 9:59 PM, Nico Kadel-Garcia wrote: > > On Sun, Jan 1, 2023 at 9:38 PM Giuseppe Sacco via hylafax-devel > > <hyl...@li...> wrote: > >> Hello, > >> a rebuild of hylafax failed with libtiff 4.5. It seems the same problem apply > >> to hylafax+. > >> > >> More details at the original bug report against the Debian package: > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027681 > >> > >> Bye, > >> Giuseppe > > I see a stack of changes in libtiff-4.5.0 listed at > > http://www.simplesystems.org/libtiff/releases/v4.5.0.html . The > > discussion there is right, HylaFAX was renamed as HylaFAX+ years ago > > and should be built only as that package. > I had HylaFAX+ in EPEL 5, 6, and 7. It's not in 8 or 9 because of > missing uucp. Someone would need to modify a fair bit of HylaFAX code > to get it to not need uucp. It's just easier for me to install uucp > when I am dealing with an EPEL 8 or 9 system, and then build and install > HylaFAX+ from SRPM. Fedora has uucp, ane mgetty. RHEL no longer does. I've published some tools to build those along with HylaFAX+ at: https://github.com/nkadel/hylafaxrepo/ Nico Kadel-Garia > Thanks, > > Lee. > |
|
From: Lee H. <fa...@ho...> - 2023-01-04 22:09:59
|
On 1/1/23 9:59 PM, Nico Kadel-Garcia wrote: > On Sun, Jan 1, 2023 at 9:38 PM Giuseppe Sacco via hylafax-devel > <hyl...@li...> wrote: >> Hello, >> a rebuild of hylafax failed with libtiff 4.5. It seems the same problem apply >> to hylafax+. >> >> More details at the original bug report against the Debian package: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027681 >> >> Bye, >> Giuseppe > I see a stack of changes in libtiff-4.5.0 listed at > http://www.simplesystems.org/libtiff/releases/v4.5.0.html . The > discussion there is right, HylaFAX was renamed as HylaFAX+ years ago > and should be built only as that package. The libtiff developers say that we were "warned". My memory is that it was broken before, they fixed it before, although in the same breath they seemed to be unhappy about it. Not really a "warning" as I see it. https://gitlab.com/libtiff/libtiff/-/issues/504 Nevertheless, until we can get these copied from libtiff into HylaFAX (seems odd to copy library code... as this is the purpose of a library) we need to patch libtiff: https://gitlab.com/libtiff/libtiff/-/issues/511 We had to patch libtiff v4.4.0, too, so for fax servers patching libtiff seems to be an expected procedure now, sadly. As for the Debian package maintainer choosing to not follow the HylaFAX+ source code, that's a policy or political decision that was made a long time ago that I think they should revisit. > Fedora rawhide is still at libtiff 4.4.x. libtiff v4.4.0 had a regression, too, and should be patched. I don't think that they've applied the fix in Fedora rawhide. https://gitlab.com/libtiff/libtiff/-/issues/489 > I note that HylaFAX+ is not currently published for RHEL, only for > Fedora. I had HylaFAX+ in EPEL 5, 6, and 7. It's not in 8 or 9 because of missing uucp. Someone would need to modify a fair bit of HylaFAX code to get it to not need uucp. It's just easier for me to install uucp when I am dealing with an EPEL 8 or 9 system, and then build and install HylaFAX+ from SRPM. Thanks, Lee. |
|
From: Nico Kadel-G. <nk...@gm...> - 2023-01-02 06:00:12
|
On Sun, Jan 1, 2023 at 9:38 PM Giuseppe Sacco via hylafax-devel <hyl...@li...> wrote: > > Hello, > a rebuild of hylafax failed with libtiff 4.5. It seems the same problem apply > to hylafax+. > > More details at the original bug report against the Debian package: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027681 > > Bye, > Giuseppe I see a stack of changes in libtiff-4.5.0 listed at http://www.simplesystems.org/libtiff/releases/v4.5.0.html . The discussion there is right, HylaFAX was renamed as HylaFAX+ years ago and should be built only as that package. Fedora rawhide is still at libtiff 4.4.x., and libtiff 4.5.0 includes a .soname update along with various functional changes. It's not shocking that libtiff and HylaFAX, and HylaFAX+, have been so stable since Sam Leffler wrote HylaFAX and invented TIFF. He was also one of the core authors of BSD UNIX. I note that HylaFAX+ is not currently published for RHEL, only for Fedora. I took the liberty of bundling RPM build tools for it over at https://github.com/nkadel/hylafaxrepo/ . It's not the first time, I did the original ports for SunOS and for Red Hat compatible repoforge repositories a *long* time ago, back when my last name was Garcia-Otero. Nico Kadel-Garcia |
|
From: Giuseppe S. <giu...@sg...> - 2023-01-02 02:38:05
|
Hello, a rebuild of hylafax failed with libtiff 4.5. It seems the same problem apply to hylafax+. More details at the original bug report against the Debian package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027681 Bye, Giuseppe |
|
From: <pa...@ur...> - 2021-02-11 23:23:04
|
Makes sense. Many thanks Lee! -- Pawel From: Lee Howard <fa...@ho...> Sent: Thursday, February 11, 2021 11:53 PM To: pa...@ur...; hyl...@li... Subject: Re: [hylafax-devel] ImageLength missing in recvq TIFF files for interrupted transmission When HylaFAX answers a call it creates a TIFF file and starts a TIFF directory (page). No data is in it yet. It then starts to write data into the directory as it gets it, and at the end of the communication it write the number of received lines into the directory. If the communication is interrupted after a page is started but before any data is received, then HylaFAX has an empty directory in the TIFF file that it can't easily dispose of without rewriting the TIFF file. This is the condition of your fax000000944.tif file. The proper thing for the TIFF application to do with such a TIFF file is to process the directories that have data and skip or ignore pages that don't. Applications may issue warnings or error messages, but they shouldn't fail to process the directories that have data. Unfortunately, tiff2pdf doesn't process the data that it could. This is a problem with tiff2pdf, and you may get some traction by filing a bug report with them. However, it may just be easier to pre-process the TIFF file before handing it off to tiff2pdf or whatever other application you may be using: tiffcp -i fax000000944.tif fax000000944-new.tif ... then work with the "new" file. This will solve a lot of ills related to this condition as well as other tricky situations (like a non-ECM fax receiving corrupt MH/MR data from the sender). This can be done within the faxrcvd, FaxAccounting, or FaxDispatch scripts as may suit your situation best. One might say that HylaFAX should only produce perfectly clean TIFF files as output. I can understand that perspective... I certainly sympathize with it (as I have to use the same tiffcp for all of the faxes that I receive). However, historically HylaFAX was designed to have the TIFF file honestly reflect the fax communication as best as possible... so by default data isn't being altered in the TIFF file from what was sent by the sender. This may or may not make practical sense, but it's the design that HylaFAX has had since the beginning. In some forensic or diagnostic sense the "raw" state of the TIFF files is sometimes helpful, though. Thanks, Lee. On 02/10/2021 02:28 PM, pa...@ur... <mailto:pa...@ur...> wrote: Hello, When the inbound fax transmission is interrupted, the tiff file generated in the recvq directory is missing the ImageLength field. Some apps using libtiff have issues with these files. For example, tiff2pdf: [root@hylafax tmp]# tiff2pdf -p A4 -o 944.pdf fax000000944.tif MissingRequired: TIFF directory is missing required "ImageLength" field. tiff2pdf: Can't set directory 3 of input file fax000000944.tif. tiff2pdf: An error occurred creating output PDF file Example tiff file (zipped) - 3 pages, the last one was interrupted: https://drive.google.com/file/d/16edQY9NZkq5mNNALqEyx6TARefwa3GlH/view?usp=s haring Hylafax+ 7.0.3 CentOS 7(2009) -- Pawel |
|
From: Lee H. <fa...@ho...> - 2021-02-11 22:52:47
|
When HylaFAX answers a call it creates a TIFF file and starts a TIFF directory (page). No data is in it yet. It then starts to write data into the directory as it gets it, and at the end of the communication it write the number of received lines into the directory. If the communication is interrupted after a page is started but before any data is received, then HylaFAX has an empty directory in the TIFF file that it can't easily dispose of without rewriting the TIFF file. This is the condition of your fax000000944.tif file. The proper thing for the TIFF application to do with such a TIFF file is to process the directories that have data and skip or ignore pages that don't. Applications may issue warnings or error messages, but they shouldn't fail to process the directories that have data. Unfortunately, tiff2pdf doesn't process the data that it could. This is a problem with tiff2pdf, and you may get some traction by filing a bug report with them. However, it may just be easier to pre-process the TIFF file before handing it off to tiff2pdf or whatever other application you may be using: tiffcp -i fax000000944.tif fax000000944-new.tif ... then work with the "new" file. This will solve a lot of ills related to this condition as well as other tricky situations (like a non-ECM fax receiving corrupt MH/MR data from the sender). This can be done within the faxrcvd, FaxAccounting, or FaxDispatch scripts as may suit your situation best. One might say that HylaFAX should only produce perfectly clean TIFF files as output. I can understand that perspective... I certainly sympathize with it (as I have to use the same tiffcp for all of the faxes that I receive). However, historically HylaFAX was designed to have the TIFF file honestly reflect the fax communication as best as possible... so by default data isn't being altered in the TIFF file from what was sent by the sender. This may or may not make practical sense, but it's the design that HylaFAX has had since the beginning. In some forensic or diagnostic sense the "raw" state of the TIFF files is sometimes helpful, though. Thanks, Lee. On 02/10/2021 02:28 PM, pa...@ur... wrote: > > Hello, > > When the inbound fax transmission is interrupted, the tiff file > generated in the recvq directory is missing the ImageLength field. > > Some apps using libtiff have issues with these files. For example, > tiff2pdf: > > [root@hylafax tmp]# tiff2pdf -p A4 -o 944.pdf fax000000944.tif > > MissingRequired: TIFF directory is missing required "ImageLength" field. > > tiff2pdf: Can't set directory 3 of input file fax000000944.tif. > > tiff2pdf: An error occurred creating output PDF file > > Example tiff file (zipped) – 3 pages, the last one was interrupted: > > https://drive.google.com/file/d/16edQY9NZkq5mNNALqEyx6TARefwa3GlH/view?usp=sharing > > Hylafax+ 7.0.3 > > CentOS 7(2009) > > -- > > Pawel > |
|
From: <pa...@ur...> - 2021-02-10 22:55:40
|
Hello, When the inbound fax transmission is interrupted, the tiff file generated in the recvq directory is missing the ImageLength field. Some apps using libtiff have issues with these files. For example, tiff2pdf: [root@hylafax tmp]# tiff2pdf -p A4 -o 944.pdf fax000000944.tif MissingRequired: TIFF directory is missing required "ImageLength" field. tiff2pdf: Can't set directory 3 of input file fax000000944.tif. tiff2pdf: An error occurred creating output PDF file Example tiff file (zipped) - 3 pages, the last one was interrupted: https://drive.google.com/file/d/16edQY9NZkq5mNNALqEyx6TARefwa3GlH/view?usp=s haring -- Pawel |
|
From: <pa...@ur...> - 2021-02-10 22:29:00
|
Hello, When the inbound fax transmission is interrupted, the tiff file generated in the recvq directory is missing the ImageLength field. Some apps using libtiff have issues with these files. For example, tiff2pdf: [root@hylafax tmp]# tiff2pdf -p A4 -o 944.pdf fax000000944.tif MissingRequired: TIFF directory is missing required "ImageLength" field. tiff2pdf: Can't set directory 3 of input file fax000000944.tif. tiff2pdf: An error occurred creating output PDF file Example tiff file (zipped) - 3 pages, the last one was interrupted: https://drive.google.com/file/d/16edQY9NZkq5mNNALqEyx6TARefwa3GlH/view?usp=s haring Hylafax+ 7.0.3 CentOS 7(2009) -- Pawel |
|
From: <pa...@ur...> - 2021-02-10 22:24:18
|
Adding missing info: Hylafax+ 7.0.3 CentOS 7(2009) -- Pawel From: pa...@ur... <pa...@ur...> Sent: Wednesday, February 10, 2021 10:51 PM To: hyl...@li... Subject: ImageLength missing in recvq TIFF files for interrupted transmission Hello, When the inbound fax transmission is interrupted, the tiff file generated in the recvq directory is missing the ImageLength field. Some apps using libtiff have issues with these files. For example, tiff2pdf: [root@hylafax tmp]# tiff2pdf -p A4 -o 944.pdf fax000000944.tif MissingRequired: TIFF directory is missing required "ImageLength" field. tiff2pdf: Can't set directory 3 of input file fax000000944.tif. tiff2pdf: An error occurred creating output PDF file Example tiff file (zipped) - 3 pages, the last one was interrupted: https://drive.google.com/file/d/16edQY9NZkq5mNNALqEyx6TARefwa3GlH/view?usp=s haring -- Pawel |
|
From: Lee H. <fa...@ho...> - 2017-10-08 05:31:48
|
On 10/07/2017 07:01 PM, Nico Kadel-Garcia wrote: > I've been following a thread in the Fedora-devel mailing list where > the current maintainer of ghostscript-fonts wants to retire it. He's > published notes at https://bugzilla.redhat.com/show_bug.cgi?id=1499240 > > HylaFAX++ is apparently one of the very, very few packages still using > this package. That maintainer suggests switching to the > urw-bas35-fonts. Is ghostscript-fonts? I have to admit that I don't > actually *have* any modems in my hot greedy hands to test this with, > and lack cycles to set up a test build. But as one of the old > maintainers from yester-year, I thought I'd bring the information over > to the current maintainers and develoeprs. Thanks. I've been following it since yesterday when the bug was filed. However, I haven't had a chance to examine it thoroughly and address it. I suspect that the issue is merely an RPM dependency and that replacing the ghostscript-fonts dependency with a urw-bas35-fonts dependency will be sufficient. However, if it turns out that there is an actual dependency in the code - faxsetup and textfmt would be where that would be most-apparent - then I think that the right thing will be to work on the code rather than arguing that the ghostscript-fonts package should remain. So, I'm planning on needing to set aside a few hours to manage it. If it turns out to be a simple thing, then I'll be pleased. Thanks, Lee. |
|
From: Nico Kadel-G. <nk...@gm...> - 2017-10-08 02:01:38
|
I've been following a thread in the Fedora-devel mailing list where the current maintainer of ghostscript-fonts wants to retire it. He's published notes at https://bugzilla.redhat.com/show_bug.cgi?id=1499240 HylaFAX++ is apparently one of the very, very few packages still using this package. That maintainer suggests switching to the urw-bas35-fonts. Is ghostscript-fonts? I have to admit that I don't actually *have* any modems in my hot greedy hands to test this with, and lack cycles to set up a test build. But as one of the old maintainers from yester-year, I thought I'd bring the information over to the current maintainers and develoeprs. |
|
From: Lee H. <fa...@ho...> - 2017-04-17 21:39:26
|
The modem or serial port is not functioning properly. So, you're going
to have to troubleshoot... try changing flow control, bitrates, verify
the modem configuration, etc.
Thanks,
Lee.
On 04/17/2017 02:31 PM, Ryan Bair wrote:
>
> hylafax running on an 8port serial card 2 ports populated and working.
> added a third port/modem but it will not receive.
>
>
> i have checked the line and swapped the modem
>
> Apr 17 09:58:09.07: [ 1168]: SESSION BEGIN 000000239 +5756279535
> Apr 17 09:58:09.07: [ 1168]: HylaFAX (tm) Version 5.5.9
> Apr 17 09:58:09.07: [ 1168]: MODEM set XON/XOFF/FLUSH: input ignored,
> output disabled
> Apr 17 09:58:09.07: [ 1168]: <-- [4:ATA\r]
> Apr 17 09:58:15.10: [ 1168]: --> [7:CONNECT]
> Apr 17 09:58:15.10: [ 1168]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS5'
> Apr 17 09:58:15.10: [ 1168]: STATE CHANGE: ANSWERING -> RECEIVING
> Apr 17 09:58:15.10: [ 1168]: RECV FAX: begin
> Apr 17 09:58:15.10: [ 1168]: <-- HDLC<32:FF C0 04 B5 00 AA 12 9E 36 86
> 62 82 1A 04 14 2E B6 94 04 6A A6 4E CE 96 F6 76 04 AC 74 AC 74 9C>
> Apr 17 09:58:15.10: [ 1168]: <-- data [32]
> Apr 17 09:58:15.10: [ 1168]: <-- data [2]
> Apr 17 09:58:22.65: [ 1168]: --> [0:]
> Apr 17 09:58:22.65: [ 1168]: MODEM <Empty line>
> Apr 17 09:58:22.65: [ 1168]: MODEM TIMEOUT: sending NSF frame
> Apr 17 09:58:22.65: [ 1168]: DELAY 70 ms
> Apr 17 09:58:22.72: [ 1168]: <-- [9:AT+FTH=3\r]
> Apr 17 09:58:30.27: [ 1168]: --> [0:]
> Apr 17 09:58:30.27: [ 1168]: MODEM TIMEOUT: sending HDLC frame
> Apr 17 09:58:30.27: [ 1168]: DELAY 70 ms
> Apr 17 09:58:30.34: [ 1168]: <-- [9:AT+FTH=3\r]
> Apr 17 09:58:37.89: [ 1168]: --> [0:]
> Apr 17 09:58:37.89: [ 1168]: MODEM TIMEOUT: sending HDLC frame
> Apr 17 09:58:37.89: [ 1168]: DELAY 70 ms
> Apr 17 09:58:37.96: [ 1168]: <-- [9:AT+FTH=3\r]
> Apr 17 09:58:45.51: [ 1168]: --> [0:]
> Apr 17 09:58:45.51: [ 1168]: MODEM TIMEOUT: sending HDLC frame
> Apr 17 09:58:45.51: [ 1168]: DELAY 70 ms
> Apr 17 09:58:45.59: [ 1168]: <-- [9:AT+FTH=3\r]
> Apr 17 09:58:53.14: [ 1168]: --> [0:]
> Apr 17 09:58:53.14: [ 1168]: MODEM TIMEOUT: sending HDLC frame
> Apr 17 09:58:53.14: [ 1168]: DELAY 70 ms
> Apr 17 09:58:53.21: [ 1168]: <-- [9:AT+FTH=3\r]
> Apr 17 09:59:00.76: [ 1168]: --> [0:]
> Apr 17 09:59:00.76: [ 1168]: MODEM TIMEOUT: sending HDLC frame
> Apr 17 09:59:00.76: [ 1168]: RECV FAX: No sender protocol (T.30 T1
> timeout) {E102}
> Apr 17 09:59:00.76: [ 1168]: RECV FAX: end
> Apr 17 09:59:00.76: [ 1168]: No sender protocol (T.30 T1 timeout) {E102}
> Apr 17 09:59:00.76: [ 1168]: <-- [5:ATH0\r]
> Apr 17 09:59:05.76: [ 1168]: MODEM TIMEOUT: reading line from modem
> Apr 17 09:59:05.76: [ 1168]: MODEM <Timeout>
> Apr 17 09:59:05.76: [ 1168]: MODEM set DTR OFF
> Apr 17 09:59:05.76: [ 1168]: SESSION END
>
> Ryan Bair
> Kymera Medical IT Staff
> rya...@ky... <mailto:rya...@ky...>
> 575-627-3137 <tel:%28575%29%20627-3137>
>
> DISCLAIMER: This communication, along with any documents, files or
> attachments, is intended only for the use of the addressee and may
> contain legally privileged and confidential information. If you are
> not the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of any information contained in
> or attached to this communication is strictly prohibited. If you have
> received this message in error, please notify the sender immediately
> and destroy the original communication and its attachments without
> reading, printing or saving in any manner. Please consider the
> environment before printing this e-mail.
>
>
> DISCLAIMER: This communication, along with any documents, files or
> attachments, is intended only for the use of the addressee and may
> contain legally privileged and confidential information. If you are
> not the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of any information contained in
> or attached to this communication is strictly prohibited. If you have
> received this message in error, please notify the sender immediately
> and destroy the original communication and its attachments without
> reading, printing or saving in any manner. Please consider the
> environment before printing this e-mail.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> hylafax-devel mailing list
> hyl...@li...
> https://lists.sourceforge.net/lists/listinfo/hylafax-devel
|
|
From: Ryan B. <rya...@ky...> - 2017-04-17 21:31:23
|
hylafax running on an 8port serial card 2 ports populated and working.
added a third port/modem but it will not receive.
i have checked the line and swapped the modem
Apr 17 09:58:09.07: [ 1168]: SESSION BEGIN 000000239 +5756279535
Apr 17 09:58:09.07: [ 1168]: HylaFAX (tm) Version 5.5.9
Apr 17 09:58:09.07: [ 1168]: MODEM set XON/XOFF/FLUSH: input ignored,
output disabled
Apr 17 09:58:09.07: [ 1168]: <-- [4:ATA\r]
Apr 17 09:58:15.10: [ 1168]: --> [7:CONNECT]
Apr 17 09:58:15.10: [ 1168]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS5'
Apr 17 09:58:15.10: [ 1168]: STATE CHANGE: ANSWERING -> RECEIVING
Apr 17 09:58:15.10: [ 1168]: RECV FAX: begin
Apr 17 09:58:15.10: [ 1168]: <-- HDLC<32:FF C0 04 B5 00 AA 12 9E 36 86 62
82 1A 04 14 2E B6 94 04 6A A6 4E CE 96 F6 76 04 AC 74 AC 74 9C>
Apr 17 09:58:15.10: [ 1168]: <-- data [32]
Apr 17 09:58:15.10: [ 1168]: <-- data [2]
Apr 17 09:58:22.65: [ 1168]: --> [0:]
Apr 17 09:58:22.65: [ 1168]: MODEM <Empty line>
Apr 17 09:58:22.65: [ 1168]: MODEM TIMEOUT: sending NSF frame
Apr 17 09:58:22.65: [ 1168]: DELAY 70 ms
Apr 17 09:58:22.72: [ 1168]: <-- [9:AT+FTH=3\r]
Apr 17 09:58:30.27: [ 1168]: --> [0:]
Apr 17 09:58:30.27: [ 1168]: MODEM TIMEOUT: sending HDLC frame
Apr 17 09:58:30.27: [ 1168]: DELAY 70 ms
Apr 17 09:58:30.34: [ 1168]: <-- [9:AT+FTH=3\r]
Apr 17 09:58:37.89: [ 1168]: --> [0:]
Apr 17 09:58:37.89: [ 1168]: MODEM TIMEOUT: sending HDLC frame
Apr 17 09:58:37.89: [ 1168]: DELAY 70 ms
Apr 17 09:58:37.96: [ 1168]: <-- [9:AT+FTH=3\r]
Apr 17 09:58:45.51: [ 1168]: --> [0:]
Apr 17 09:58:45.51: [ 1168]: MODEM TIMEOUT: sending HDLC frame
Apr 17 09:58:45.51: [ 1168]: DELAY 70 ms
Apr 17 09:58:45.59: [ 1168]: <-- [9:AT+FTH=3\r]
Apr 17 09:58:53.14: [ 1168]: --> [0:]
Apr 17 09:58:53.14: [ 1168]: MODEM TIMEOUT: sending HDLC frame
Apr 17 09:58:53.14: [ 1168]: DELAY 70 ms
Apr 17 09:58:53.21: [ 1168]: <-- [9:AT+FTH=3\r]
Apr 17 09:59:00.76: [ 1168]: --> [0:]
Apr 17 09:59:00.76: [ 1168]: MODEM TIMEOUT: sending HDLC frame
Apr 17 09:59:00.76: [ 1168]: RECV FAX: No sender protocol (T.30 T1 timeout)
{E102}
Apr 17 09:59:00.76: [ 1168]: RECV FAX: end
Apr 17 09:59:00.76: [ 1168]: No sender protocol (T.30 T1 timeout) {E102}
Apr 17 09:59:00.76: [ 1168]: <-- [5:ATH0\r]
Apr 17 09:59:05.76: [ 1168]: MODEM TIMEOUT: reading line from modem
Apr 17 09:59:05.76: [ 1168]: MODEM <Timeout>
Apr 17 09:59:05.76: [ 1168]: MODEM set DTR OFF
Apr 17 09:59:05.76: [ 1168]: SESSION END
Ryan Bair
Kymera Medical IT Staff
rya...@ky...
575-627-3137 <(575)%20627-3137>
DISCLAIMER: This communication, along with any documents, files or
attachments, is intended only for the use of the addressee and may contain
legally privileged and confidential information. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of any information contained in or attached to this
communication is strictly prohibited. If you have received this message in
error, please notify the sender immediately and destroy the original
communication and its attachments without reading, printing or saving in
any manner. Please consider the environment before printing this e-mail.
--
DISCLAIMER: This communication, along with any documents, files or
attachments, is intended only for the use of the addressee and may contain
legally privileged and confidential information. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of any information contained in or attached to this
communication is strictly prohibited. If you have received this message in
error, please notify the sender immediately and destroy the original
communication and its attachments without reading, printing or saving in
any manner. Please consider the environment before printing this e-mail.
|
|
From: Lee H. <fa...@ho...> - 2017-03-24 17:13:39
|
On 03/24/2017 09:43 AM, Ryan Bair wrote: > modem will not answer fax > > do i need to configure faxgetty? Well, you need to run faxgetty. faxgetty is what receives faxes. Thanks, Lee. |
|
From: Ryan B. <rya...@ky...> - 2017-03-24 17:08:41
|
My name is Ryan new to hylafax ubuntu 14.04 modem us robotics 5686G onboard serial ttyS0 (future i will add 8 port serial card and modems) purpose is high volume incoming faxes make install (done as root) after install faxsetup faxaddmodem (all defaults) class1modem modem will not answer fax do i need to configure faxgetty? minicom works i can send/receive calls using atdt (number) *sudo probemodem* here is the output of probemodem :~$ sudo probemodem ttyS0 Now we are going to probe the tty port. This takes a few seconds, so be patient. Note that if you do not have the modem cabled to the port, or the modem is turned off, this may hang (just go and cable up the modem or turn it on, or whatever). Probing for best speed to talk to modem: 38400 OK. This looks like a Class 1, 2 and 2.0 modem. ATI0 RESULT = "OK" RESPONSE = "5601" ATI1 RESULT = "OK" RESPONSE = "068A" ATI2 RESULT = "OK" RESPONSE = "OK" ATI3 RESULT = "OK" RESPONSE = "U.S. Robotics 56K FAX EXT V5.4.5" ATI4 RESULT = "OK" RESPONSE = "U.S. Robotics 56K FAX EXT Settings..." ATI5 RESULT = "OK" RESPONSE = "U.S. Robotics 56K FAX EXT NVRAM Settings..." ATI6 RESULT = "OK" RESPONSE = "U.S. Robotics 56K FAX EXT Link Diagnostics..." ATI7 RESULT = "OK" RESPONSE = "Configuration Profile..." ATI8 RESULT = "OK" RESPONSE = "OK" /usr/local/sbin/probemodem: line 337: printf: missing unicode digit for \U ATI9 RESULT = "OK" RESPONSE = "(1.0USR2082\Modem\PNPC107\U.S. Robotics 56K FAX EXT)FF" Class 1 stuff... AT+FCLASS=? RESULT = "OK" RESPONSE = "0,1,2,2.0" AT+FCLASS? RESULT = "OK" RESPONSE = "1" AT+FCLASS=0 RESULT = "OK" RESPONSE = "OK" AT+FCLASS=1 RESULT = "OK" RESPONSE = "OK" AT+FCLASS? RESULT = "OK" RESPONSE = "1" AT+FJUNK=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FJUNK? RESULT = "ERROR" RESPONSE = "ERROR" AT+FAA=? RESULT = "OK" RESPONSE = "(0-1)" AT+FAA? RESULT = "OK" RESPONSE = "0" AT+FAE=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FAE? RESULT = "ERROR" RESPONSE = "ERROR" AT+FTH=? RESULT = "OK" RESPONSE = "3,24,48,72,73,74,96,97,98,121,122,145,146" AT+FRH=? RESULT = "OK" RESPONSE = "3,24,48,72,73,74,96,97,98,121,122,145,146" AT+FTM=? RESULT = "OK" RESPONSE = "3,24,48,72,73,74,96,97,98,121,122,145,146" AT+FRM=? RESULT = "OK" RESPONSE = "3,24,48,72,73,74,96,97,98,121,122,145,146" AT+FTS=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FRS=? RESULT = "ERROR" RESPONSE = "ERROR" Class 2 stuff... AT+FCLASS=? RESULT = "OK" RESPONSE = "0,1,2,2.0" AT+FCLASS? RESULT = "OK" RESPONSE = "1" AT+FCLASS=0 RESULT = "OK" RESPONSE = "OK" AT+FCLASS=1 RESULT = "OK" RESPONSE = "OK" AT+FCLASS=2 RESULT = "OK" RESPONSE = "OK" AT+FCLASS? RESULT = "OK" RESPONSE = "1" AT+FJUNK=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FJUNK? RESULT = "ERROR" RESPONSE = "ERROR" AT+FAA=? RESULT = "OK" RESPONSE = "(0-1)" AT+FAA? RESULT = "OK" RESPONSE = "0" AT+FAXERR=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FAXERR? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBADLIN=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBADLIN? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBADMUL=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBADMUL? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBOR=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBOR? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBUF=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBUF? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBUG=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FBUG? RESULT = "ERROR" RESPONSE = "ERROR" AT+FCIG=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FCIG? RESULT = "ERROR" RESPONSE = "ERROR" AT+FCQ=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FCQ? RESULT = "ERROR" RESPONSE = "ERROR" AT+FCR=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FCR? RESULT = "ERROR" RESPONSE = "ERROR" AT+FTBC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FTBC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDCC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDCC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDCS=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDCS? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDIS=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDIS? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDT=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDT? RESULT = "ERROR" RESPONSE = "ERROR" AT+FECM=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FECM? RESULT = "ERROR" RESPONSE = "ERROR" AT+FET=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FET? RESULT = "ERROR" RESPONSE = "ERROR" AT+FLID=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FLID? RESULT = "ERROR" RESPONSE = "ERROR" AT+FLNFC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FLNFC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FLPL=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FLPL? RESULT = "ERROR" RESPONSE = "ERROR" AT+FMDL? RESULT = "ERROR" RESPONSE = "ERROR" AT+FMFR? RESULT = "ERROR" RESPONSE = "ERROR" AT+FMINSP=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FMINSP? RESULT = "ERROR" RESPONSE = "ERROR" AT+FPHCTO=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FPHCTO? RESULT = "ERROR" RESPONSE = "ERROR" AT+FPTS=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FPTS? RESULT = "ERROR" RESPONSE = "ERROR" AT+FRBC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FRBC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FREL=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FREL? RESULT = "ERROR" RESPONSE = "ERROR" AT+FREV? RESULT = "ERROR" RESPONSE = "ERROR" AT+FSPL=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FSPL? RESULT = "ERROR" RESPONSE = "ERROR" AT+FTBC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FTBC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FVRFC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FVRFC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FWDFC=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FWDFC? RESULT = "ERROR" RESPONSE = "ERROR" AT+FK=? RESULT = "ERROR" RESPONSE = "ERROR" Class 2.0 stuff... AT+FCLASS=? RESULT = "OK" RESPONSE = "0,1,2,2.0" AT+FCLASS? RESULT = "OK" RESPONSE = "2.0" AT+FCLASS=0 RESULT = "OK" RESPONSE = "OK" AT+FCLASS=1 RESULT = "OK" RESPONSE = "OK" AT+FCLASS=2.0 RESULT = "OK" RESPONSE = "OK" AT+FCLASS? RESULT = "OK" RESPONSE = "2.0" AT+FJU=? RESULT = "ERROR" RESPONSE = "ERROR" AT+FJU? RESULT = "ERROR" RESPONSE = "ERROR" AT+FDR=? RESULT = "OK" RESPONSE = "OK" AT+FDT=? RESULT = "OK" RESPONSE = "OK" AT+FIP=? RESULT = "OK" RESPONSE = "00" AT+FAA=? RESULT = "OK" RESPONSE = "(0-1)" AT+FAA? RESULT = "OK" RESPONSE = "0" AT+FAP=? RESULT = "OK" RESPONSE = "(00,01),(00,01),(00,01)" AT+FAP? RESULT = "OK" RESPONSE = "00,00,00" AT+FBS? RESULT = "OK" RESPONSE = "1000,0800" AT+FBO=? RESULT = "OK" RESPONSE = "00-03" AT+FBO? RESULT = "OK" RESPONSE = "00" AT+FBU=? RESULT = "OK" RESPONSE = "00,01" AT+FBU? RESULT = "OK" RESPONSE = "00" AT+FCC=? RESULT = "OK" RESPONSE = "(00-7F),(00-05),(00-02),(00-02),(00-03),(00-01),(00),(00-07),(00-7F)" AT+FCC? RESULT = "OK" RESPONSE = "01,05,00,02,00,01,00,00,00" AT+FCQ=? RESULT = "OK" RESPONSE = "(00-01),(00)" AT+FCQ? RESULT = "OK" RESPONSE = "00,00" AT+FCR=? RESULT = "OK" RESPONSE = "00,01" AT+FCR? RESULT = "OK" RESPONSE = "01" AT+FCS=? RESULT = "OK" RESPONSE = "OK" AT+FCS? RESULT = "OK" RESPONSE = "00,00,00,00,00,00,00,00,00" AT+FCT=? RESULT = "OK" RESPONSE = "00-FF" AT+FCT? RESULT = "OK" RESPONSE = "1E" AT+FEA=? RESULT = "OK" RESPONSE = "00" AT+FEA? RESULT = "OK" RESPONSE = "00" AT+FFC=? RESULT = "OK" RESPONSE = "(00),(00),(00),(00)" AT+FFC? RESULT = "OK" RESPONSE = "00,00,00,00" AT+FFD=? RESULT = "OK" RESPONSE = "00" AT+FFD? RESULT = "OK" RESPONSE = """" AT+FHS? RESULT = "OK" RESPONSE = "00" AT+FIE=? RESULT = "OK" RESPONSE = "00" AT+FIE? RESULT = "OK" RESPONSE = "00" AT+FIS=? RESULT = "OK" RESPONSE = "(00-7F),(00-05),(00-02),(00-02),(00-03),(00-01),(00),(00-07),(00-7F)" AT+FIS? RESULT = "OK" RESPONSE = "01,05,00,02,00,01,00,00,00" AT+FIT=? RESULT = "OK" RESPONSE = "(00),(00)" AT+FIT? RESULT = "OK" RESPONSE = "00,00" AT+FLI=? RESULT = "OK" RESPONSE = "(20-7E)" AT+FLI? RESULT = "OK" RESPONSE = "" "" AT+FLO=? RESULT = "OK" RESPONSE = "(0-2)" AT+FLO? RESULT = "OK" RESPONSE = "2" AT+FLP=? RESULT = "OK" RESPONSE = "00,01" AT+FLP? RESULT = "OK" RESPONSE = "00" AT+FMI? RESULT = "OK" RESPONSE = "U.S. Robotics" AT+FMM? RESULT = "OK" RESPONSE = "U.S. Robotics 56K FAX EXT V5.4.5" AT+FMR? RESULT = "OK" RESPONSE = "V5.4.5" AT+FMS=? RESULT = "OK" RESPONSE = "00-05" AT+FMS? RESULT = "OK" RESPONSE = "00" AT+FNR=? RESULT = "OK" RESPONSE = "(00,01),(00,01),(00,01),(00,01)" AT+FNR? RESULT = "OK" RESPONSE = "00,00,00,00" AT+FNS=? RESULT = "OK" RESPONSE = "20" AT+FNS? RESULT = "OK" RESPONSE = """" AT+FPA=? RESULT = "OK" RESPONSE = "(20-7E)" AT+FPA? RESULT = "OK" RESPONSE = "" "" AT+FPI=? RESULT = "OK" RESPONSE = "(20-7E)" AT+FPI? RESULT = "OK" RESPONSE = "" "" AT+FPP=? RESULT = "OK" RESPONSE = "00" AT+FPP? RESULT = "OK" RESPONSE = "00" AT+FPR=? RESULT = "OK" RESPONSE = "(0-20)" AT+FPR? RESULT = "OK" RESPONSE = "0" AT+FPS=? RESULT = "OK" RESPONSE = "1-3" AT+FPS? RESULT = "OK" RESPONSE = "01" AT+FPW=? RESULT = "OK" RESPONSE = "(20-7E)" AT+FPW? RESULT = "OK" RESPONSE = "" "" AT+FRQ=? RESULT = "OK" RESPONSE = "(00-64),(00-FF)" AT+FRQ? RESULT = "OK" RESPONSE = "14,05" AT+FRY=? RESULT = "OK" RESPONSE = "00-FF" AT+FRY? RESULT = "OK" RESPONSE = "00" AT+FSA=? RESULT = "OK" RESPONSE = "(20-7E)" AT+FSA? RESULT = "OK" RESPONSE = "" "" AT+FSP=? RESULT = "OK" RESPONSE = "00,01" AT+FSP? RESULT = "OK" RESPONSE = "00" AT+IFC=? RESULT = "OK" RESPONSE = "00" AT+IFC? RESULT = "OK" RESPONSE = "00" AT+IPR=? RESULT = "OK" RESPONSE = "00" AT+IPR? RESULT = "OK" RESPONSE = "00" AT+FKS=? RESULT = "OK" RESPONSE = "OK" -- DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail. |
|
From: Italos M. <it...@in...> - 2016-03-12 03:21:59
|
Hello, Is there anyone to provide some paid help to us to properly and reliably install hylafax+ with t.38 and explain to us how he did? Let us know if anyone is available. Kind Regards Marios |
|
From: Lee H. <fa...@ho...> - 2015-10-07 18:13:34
|
Thank you. I've committed your changes to the SVN repository and they will be in the upcoming 5.5.7 release. Thanks, Lee. On 10/07/2015 04:43 AM, Zesen Qian wrote: > Hello list, > I 'm a user of Hylafax for two years, and it works very well. However > I find the Chinese translation not quite good(seems a machine > translation), so I modified it to make it more native and hope it will > help other Chinese users. > > Thanks! > |
|
From: Zesen Q. <hyl...@ri...> - 2015-10-07 11:59:26
|
Hello list, I 'm a user of Hylafax for two years, and it works very well. However I find the Chinese translation not quite good(seems a machine translation), so I modified it to make it more native and hope it will help other Chinese users. Thanks! |
|
From: Lee H. <fa...@ho...> - 2015-07-27 15:27:37
|
If any on this list are interested, I have resolved the matter below. The SVN repository at Sourceforge is fully-restored, I believe. Thanks, Lee. -------- Original Message -------- Subject: SourceForge SVN repository data gap notification for project hylafax Date: Sun, 26 Jul 2015 22:37:12 +0000 From: SourceForge Support <no...@so...> To: fa...@ho... SourceForge experienced a storage fault on 2015-07-16. Service restoration has been in-progress since that time, and our latest full status update is online at: http://sourceforge.net/blog/sourceforge-infrastructure-and-service-restoration-update-for-724/ Subversion data has generally been restored to the 2015-07-14 backup. We have identified 497 Subversion repositories which received commits after 2015-07-13 and before the storage fault. Your project, hylafax, is one of those repositories. To determine which repositories are missing recent commits, we compared the revision count currently in your repository on disk (Current revision on disk) to the revision count seen by our repository tracking (Current revision in database). The repository tracking database does not house a full copy of your commit data. We determined data needed to be committed again because the Current revision on disk is less than the Current revision in database. Analysis of your repository compared to our SCM repository tracking data shows: Current revision on disk: 2374 Current revision in database: 2375 Recent commit events tracked in database: r2375 faxguy Thu Jul 16 2015 05:06:49 GMT+0000 (UTC) DynamicConfig assignment of Class 1 modem data ... Since commits were made to your repository after our restore point, it will be necessary for you to coordinate within your team to ensure these changes are recommitted. We recommend you make a backup of your existing repository checkout, then make a fresh checkout of the repository in another directory, copy over any changes and commit. Depending on the number of developers on your team and the granularity of change tracking you need for these uncommitted changes, you may need to tune this process for your project. Please coordinate with the other developers on your project team before committing. If you have any follow-up questions or concerns, please contact the SourceForge Support team by submitting a ticket at: https://sourceforge.net/p/forge/site-support/new/ Thank you, SourceForge Support |
|
From: Robert M. <ro...@mi...> - 2015-01-22 21:45:53
|
Swap out the 3com/USR modem to another modem. These errors pretty much
went away when we swapped them out to something other then 3Com/USR
modems. The faxing support of the 3Com/USR modems seems to be really
poor when being used in the real world.
Thanks
Robert
On 01/22/2015 02:29 PM, Randy Jonasz wrote:
> Hello,
>
> My name is Randy Jonasz. I work for McMaster University in Hamilton
> Ontario Canada for the Department of Family Medicine. We develop an
> open source EMR called OSCAR. Recently I implemented the ability to
> send and receive faxes from within EMR using java, hylafax+ and
> gnu-hylafax library. Everything works well except for about 10 percent
> of the outgoing faxes to various recipients. With them, we keep getting
> "No response to PPS repeated 3 times. {E147}" errors. Since hylafax
> reports this as an error my code marks the fax as having failed which
> leads to an administrator resending the fax. Unfortunately the faxes are
> being successfully received despite the error. The recipients are
> complaining we are sending too many copies of the same fax!
>
> Is it possible for myself to look at the hylafax code which generates
> this error and have it behave differently than it currently does? If
> the fax is successfully sent then this is not really an error. Any
> guidance or suggestions would be most welcome. Below is a log of one
> session which generates the error.
>
> Thanks!
>
> Randy Jonasz
>
|
3 messages has been excluded from this view by a project administrator.
