http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29552 These are both a series of modem errors. First the modem's V.17 demodulator isn't compatible with the signal. Second, the modem's V.21 HDLC function is also less than perfect. So with +FRH=146 it won't detect the signal, but with +FRH=3 it mistakenly thinks that it's V.21 HDLC. Again, it's a fun modem. :-) HylaFAX always opens a TIFF file, but in this case the file may be closed and removed because no data was received. Your faxrcvd should be capable of handling this condition. Okay, good. Page 1. Um, but here the modem botches things. It's the same modem. Is this, by chance, a USR modem? Hrmm... this is interesting because it would appear that HylaFAX *lost* the page that was just received... although the receipt was not confirmed to the sender. You must have SaveUnconfirmedPages set to "no" in your modem config file... or there is a bug in your version of HylaFAX. I just tested this exact scenario with HylaFAX+ 5.2.7 and the page was saved as expected. Thanks, Lee. Lee Howard 2008-12-04T02:09:02 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29551 I've not yet seen a well-functional SmartLink modem configuration with HylaFAX. The modem seems ill-suited for fax. 1315 bytes is awfully short. It's shorter than the specification of 1.5 seconds. Again, same thing. Although 1564 is longer than 1315. Another short run. Again. Woohoo! It worked. So either there was something wrong with the V.17 14400/12000 demodulator in the SmartLink modem or the sender really wasn't sending a long-enough TCF signal. But... The modem seems to trip up on V.17 9600, too. Either that, or the audio is faulty. Or possibly the sender is quite buggy. BUT, since you're using a SmartLink modem, I'm guessing that's the whole matter there. Thanks, Lee. Lee Howard 2008-12-04T01:20:43 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29550 Something is wrong with your HylaFAX GNU Java API protocol... because the notification e-mail address is passed to the server from the client. The server doesn't generally make it up. Thanks, Lee. Lee Howard 2008-12-04T01:10:16 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29549 Lucas, Put this in your modem config files: RecvFileMode: 0644 Thanks, Lee. Lucas Burdick wrote: Lee Howard 2008-12-04T01:06:43 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29548 faxmail behavior between HylaFAX 4.4.4 and HylaFAX+ 5.2.7 vary on a number of points. I believe you're hitting one. The mail2fax.sh script that you're using is intended for HylaFAX+ behavior (as well as HylaFAX.org releases prior to 4.4... I think). Thanks, Lee. Lee Howard 2008-12-04T01:03:59 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29547 If using Class 1 you can configure in your modem config file to not permit unlimited length pages. This will get you supporting only A4 page length on reception: Class1PageLengthSupport: 0 Thanks, Lee. Lee Howard 2008-12-04T00:58:49 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29546 The Digicom modem is malfunctioning in fax mode. The OK result immediately following AT+FTH=3 (without a CONNECT first) is wrong. The <AD><8A><CF>_<8A> is quite confusing, too. Thanks, Lee. Lee Howard 2008-12-04T00:40:59 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29545 Look in the system mail log to see what has gone wrong. Thanks, Lee. Lee Howard 2008-12-04T00:35:27 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29544 Just to be clear - on the receive-side you're using HylaFAX 4.4.4 and a hardware modem on ttyS7. What happens is that the received audio is broken in the middle of Phase C. Thus the "assumed RCP frame with block end". This will happen, for example, with jitter. The receiving modem then goes to listen for the partial-page message (+FRH=3 - V.21 HDLC), the receiving modem erroneously reports CONNECT (twice) on V.17 audio, and then the receive-side gives up. So there was a glitch in the audio and then a small modem bug on the receiver mixed with a less-tolerant HylaFAX operation on the receiver caused the failure. Start analyzing the audio path to figure out why it's being disturbed. Even if the receiver didn't have a problem in recovering from this you'd still want the audio problem to be fixed. Thanks, Lee. Lee Howard 2008-12-04T00:34:26 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29543 How did you perform the installation? It would seem, maybe, that you are installing a package that was built on a different architecture. Thanks, 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< at >hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales< at >ifax.com.* Lee Howard 2008-12-04T00:05:01 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29542 What does the error message say exactly? (Maybe cut and paste directly from the log.) "doesn't look like a 1d G3 Fax!" doesn't come from HylaFAX. Thanks, Lee. Lee Howard 2008-12-04T00:00:53 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29541 Well, that seems to be exactly what dialrules intends to satisfy. If dialrules is not suitable, then JobControl will be the way to go. An upcoming version (5.2.8) of HylaFAX+ has some ability to send a fax on a modem that is already in-use. The feature was designed for a different purpose than yours, but in any case, I don't believe that this is what you want to do. It would make your operation significantly more complicated than it needs to be. Thanks, Lee. Lee Howard 2008-12-03T23:48:08 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29540 Hello Lucas, I also was playing around with a similar scenario today, after I went to the folders of the incoming tif files and run "chmod +r *" as root, everything was fine and I could open them. So I would also like to know for myself if there is a more elegant way? I could run a cronjob every minute to do that, but I think there was already a smart brain which designed this in a smarter way? Oliver Lucas Burdick schrieb: ____________________ 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< at >hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales< at >ifax.com.* Oliver Söder 2008-12-03T23:10:43 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29539 Oliver, That worked great...but you're right...perhaps the faxrcvd script can change the permissions when it creates the file? Lucas Burdick Sealing Device Specialist Progressive Sealing Inc. Vancouver, B.C. t: 604.263.1562 f: 604.263.8923 c: 604.861.2865 www.progressive-sealing.com This email and any attachments are intended solely for the use of the addressee(s) named. -----Original Message----- From: Oliver Söder [mailto:oliver.soeder< at >gmx.de] Sent: Wednesday, December 03, 2008 3:11 PM To: Lucas Burdick Cc: hylafax-users< at >hylafax.org Subject: Re: [hylafax-users] Viewing faxes over the network Hello Lucas, I also was playing around with a similar scenario today, after I went to the folders of the incoming tif files and run "chmod +r *" as root, everything was fine and I could open them. So I would also like to know for myself if there is a more elegant way? I could run a cronjob every minute to do that, but I think there was already a smart brain which designed this in a smarter way? Oliver Lu Lucas Burdick 2008-12-03T23:17:35 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29538 I have everything working just like I want, but there is something that has been bothering me. I’m running the latest version of + (5.2.7) and we use YAHJFC to submit fax jobs. I would like to be able to use YAHJCF to view the faxes as well, but whenever I double click on a fax to view I get an operation not permitted error. It seems to me that I have had this error before with other clients. In fact I can’t really view the faxes at all unless I have them sent to me via email or I login physically to the server. Any idea what’s necessary to view faxes? What protocol does the server use...I recall that it’s FTP or something similar. Maybe my permissions are messed up? Obviously I need to narrow this down, where should I start? thanks Lucas Burdick Lucas Burdick 2008-12-03T23:07:28 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29537 Hello Alexander, you can use Diva BRI: http://www.dialogic.com/products/tdm_boards/media_processing/Diva_BRI.htm It is available as PCI and PCIe and it comes with a driver which has been designed to support Hylafax TTYs so that you do not need to use CAPI4Hylafax. Oliver 2008/12/3 Alexander Busam <a.busam< at >hofmann-foerdertechnik.com> Oliver Söder 2008-12-03T11:31:31 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29536 Thank you for your ansewer Uwe. But I would like to know another thing. Why did Hylafax say that I have a file (recvq/fax000001698.tif) and the file is not there? There were some communications errors in the past, but Hylafax didn't log any file. For me, it would be normal. But... Thank you once more. -----Message d'origine----- De : Uwe Dippel [mailto:udippel< at >gmail.com] Envoyé : 2 décembre, 2008 19:50 À : Marcelo Godois Tavares Cc : Hylafax Users Objet : Re: [hylafax-users] The tif images doesn't exist in the recvq directory Marcelo Godois Tavares wrote: Hi, Marcelo. I am not an expert, but what I have found out by now on hylafax: When the reception incurs a serious error, there is no image file in /recvq. First, you'd have to debug the reason for that "Failure to raise V.21 transmission carrier." If you enter this phrase in Google (or search the archives, you'll find a bunch of hints. Good luck, Uwe ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscr Marcelo Godois Tavares 2008-12-03T13:35:27 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29535 PCI-E works fine under Linux. Just make sure it's enabled in the kernel. Michael ____________________ 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< at >hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales< at >ifax.com.* Michael 2008-12-03T11:28:43 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29534 Hello! I have to migrate my mail- and faxserver to a more powerful machine. Now, I cannot use the AVM-B1 controller anymore because the new server only support pce-express cards. Does anybody have any experience with pci-express isdn cards under Linux (currently I use OpenSuse 10.3) or can anybody recommend a pci-express card for Linux ? Thanks a lot. Best regards Alex ____________________ 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< at >hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales< at >ifax.com.* Alexander Busam 2008-12-03T11:26:49 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29533 Thanks for the quick reply. I'll have a look and see if we can get any info from the boards diagnostics about the real speeds and also work with Dialogic support to try sort out the issues here. On Wed, Dec 3, 2008 at 9:41 AM, Darren Nickerson <darren.nickerson< at >ifax.com>wrote: Dominique dHotman 2008-12-03T08:09:56 http://permalink.gmane.org/gmane.comp.telephony.fax.hylafax.user/29532 Dominique, According to a previous post, you turned off the Class 2 V34 speed indicator explicitly in the dialogic config. As a result, you've told the diva board to lie to HylaFAX even more than usual. I'm confident you'll find that your Dialogic board is sending at speeds higher than 14,400, it's just not telling HylaFAX about it as you have requested. Incidentally, this board is being discontinued by Dialogic at the end of the year .... if you're using their support a lot I would recommend you I would try to work out as many of the kinks before that time! -Darren On Dec 3, 2008, at 2:30 AM, Dominique dHotman wrote: Darren Nickerson 2008-12-03T07:41:36 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.telephony.fax.hylafax.user