gmane.comp.telephony.fax.hylafax.devel

hylafax/libhylafax update now available

2008-11-28T21:09:38

Update of /usr/local/cvsroot/hylafax/libhylafax In directory cvs.hylafax.org:/tmp/cvs-serv5790/libhylafax Modified Files: AtSyntax.c++ DialRules.c++ FaxClient.c++ TypeRules.c++ Log Message: Added translator comments for many unclear translatable strings ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/faxrm update now available

2008-11-28T21:09:38

Update of /usr/local/cvsroot/hylafax/faxrm In directory cvs.hylafax.org:/tmp/cvs-serv5790/faxrm Modified Files: faxrm.c++ Log Message: Added translator comments for many unclear translatable strings ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/po/hylafax-client update now available

2008-11-28T21:09:38

Update of /usr/local/cvsroot/hylafax/po/hylafax-client In directory cvs.hylafax.org:/tmp/cvs-serv5790/po/hylafax-client Modified Files: messages.pot Log Message: Added translator comments for many unclear translatable strings ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/po/libhylafax update now available

2008-11-28T21:09:39

Update of /usr/local/cvsroot/hylafax/po/libhylafax In directory cvs.hylafax.org:/tmp/cvs-serv5790/po/libhylafax Modified Files: messages.pot Log Message: Added translator comments for many unclear translatable strings ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/po update now available

2008-11-28T21:09:38

Update of /usr/local/cvsroot/hylafax/po In directory cvs.hylafax.org:/tmp/cvs-serv5790/po Modified Files: hylafax.pot Log Message: Added translator comments for many unclear translatable strings ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

[Bug 898] New: can connect to other computers but no fax

2008-11-21T23:53:24

http://bugs.hylafax.org/show_bug.cgi?id=898 Summary: can connect to other computers but no fax Product: HylaFAX Version: 4.3.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: faxsend AssignedTo: hylafax-devel< at >hylafax.org ReportedBy: carter2454< at >msn.com CC: carter2454< at >msn.com We have an IBM eSeries 346 with FC5 uses ttyS0 (one serial port) Can not send faxes Using class 2 we get.. ERR No carrier detected Using other classes we will get error in phase b & C Modem will dial out and the remote fax will answer, then our Multitech 5634zba will hang up.... Using mincom or kermit we can connect to remote computers..but can not send faxes.. --NextPart2864 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Your facsimile job to 7712094 failed because: No carrier detected ---- Transcript of session follows ---- Nov 14 14:19:15.06: [ 2727]: SESSION BEGIN 000000416 15017712094 Nov 14 14:19:15.06: [ 2727]: HylaFAX (tm) Version 4.3.0 Nov 14 14:19:15.06: [ 2727]: SEND FAX: JOB 317 DEST 7712094 COMMID 000000416 DEVICE '/dev/ttyS0' FROM 'carter fulleribm>' USER carter Nov 14 14:19:15.06: [ 2727]: <-- [9:AT+FLO=1\r] Nov 14 14:19:15.08: [ 2727]: --> [2:OK] Nov 14 14:19:15.08: [ 2727]: <-- [9:AT+FPP=0\r] Nov 14 14:19:15.09: [ 2727]: --> [2:OK] Nov 14 14:19:15.09: [ 2727]: <-- [9:AT+FBO=0\r] Nov 14 14:19:15.11: [ 2727]: --> [2:OK] Nov 14 14:19:15.11: [ 2727]: <-- [10:AT+FCT=30\r] Nov 14 14:19:15.13: [ 2727]: --> [2:OK] Nov 14 14:19:15.13: [ 2727]: <-- [11:AT+FCQ=1,0\r] Nov 14 14:19:15.14: [ 2727]: --> [2:OK] Nov 14 14:19:15.14: [ 2727]: <-- [15:AT+FNR=1,1,1,1\r] Nov 14 14:19:15.16: [ 2727]: --> [2:OK] Nov 14 14:19:15.16: [ 2727]: <-- [13:AT+FAP=1,1,1\r] Nov 14 14:19:15.18: [ 2727]: --> [2:OK] Nov 14 14:19:15.18: [ 2727]: <-- [9:AT+FIE=0\r] Nov 14 14:19:15.20: [ 2727]: --> [2:OK] Nov 14 14:19:15.20: [ 2727]: <-- [23:AT+FCC=1,5,2,2,1,1,0,0\r] Nov 14 14:19:15.22: [ 2727]: --> [2:OK] Nov 14 14:19:15.22: [ 2727]: DIAL 7712094 Nov 14 14:19:15.22: [ 2727]: <-- [28:AT+FCC=,,,,1,,,,0;DT7712094\r] Nov 14 14:19:34.28: [ 2727]: --> [2:OK] Nov 14 14:19:34.28: [ 2727]: SEND FAILED: JOB 317 DEST 7712094 ERR No carrier detected Nov 14 14:19:34.28: [ 2727]: <-- [5:ATH0\r] Nov 14 14:19:34.41: [ 2727]: --> [2:OK] Nov 14 14:19:34.41: [ 2727]: SESSION END ---- Unsent job status ---- Need your help please. Carter

hylafax/faxd update now available

2008-11-21T21:07:04

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv15292/faxd Modified Files: Tag: HYLAFAX-4_4-branch Class1Recv.c++ Class2Recv.c++ ClassModem.c++ ClassModem.h CopyQuality.c++ ModemServer.c++ ModemServer.h STATUS.txt faxGettyApp.c++ faxSendApp.c++ pageSendApp.c++ Log Message: Abort receive session on error writing to file So that we don't confirm a fax we won't actually have. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/faxd update now available

2008-11-21T20:55:48

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv14621/faxd Modified Files: Class1Recv.c++ Class2Recv.c++ ClassModem.c++ ClassModem.h CopyQuality.c++ ModemServer.c++ ModemServer.h STATUS.txt faxGettyApp.c++ faxSendApp.c++ pageSendApp.c++ Log Message: Abort receive session on error writing to file So that we don't confirm a fax we won't actually have. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

T38modem and Sip providers

Nagesh — 2008-11-14T10:54:07

Hi All, We are about to configure the T38modem with asterisk, we use the hylafax to send and receive our faxes. I just want to confirm whether T38modem and sip providers works the best and gives the commercial grade fax. Thanks, Nagesh.

Re: Where is ClassModem::dataTimeout initialized?

Lee Howard — 2008-11-09T01:47:15

Indeed. dataTimeout isn't being initialized. Please try the attached patch. Thanks, Lee.

Where is ClassModem::dataTimeout initialized?

Dave Huang — 2008-11-07T20:21:16

Hi, I'm having trouble sending faxes with Hylafax 4.3.4 on NetBSD 4.99.72 on a DEC Alpha: [ stuff deleted ] Nov 07 02:42:42.86: [15730]: SEND training at v.17 14400 bit/s Nov 07 02:42:42.86: [15730]: DELAY 70 ms Nov 07 02:42:42.93: [15730]: <-- [9:AT+FTH=3\r] Nov 07 02:42:43.12: [15730]: --> [7:CONNECT] Nov 07 02:42:43.13: [15730]: <-- data [23] Nov 07 02:42:43.13: [15730]: <-- data [2] Nov 07 02:42:43.14: [15730]: --> [7:CONNECT] Nov 07 02:42:43.15: [15730]: <-- data [7] Nov 07 02:42:43.15: [15730]: <-- data [2] Nov 07 02:42:45.13: [15730]: --> [2:OK] Nov 07 02:42:45.13: [15730]: <-- [9:AT+FTS=7\r] Nov 07 02:42:45.21: [15730]: --> [2:OK] Nov 07 02:42:45.21: [15730]: <-- [11:AT+FTM=145\r] Nov 07 02:42:46.68: [15730]: --> [7:CONNECT] Nov 07 02:42:46.69: [15730]: <-- data [1024] Nov 07 02:42:46.69: [15730]: <-- data [1024] Nov 07 02:42:46.69: [15730]: <-- data [2] Nov 07 02:42:47.21: [15730]: Problem sending TCF data Nov 07 02:42:47.21: [15730]: <-- [9:AT+FRS=1\r] Nov 07 02:43:17.23: [15730]: MODEM [ more stuff deleted] I ran ktrace to log the system calls, and found that the second write of 1024 bytes at 02:42:46.69 was interrupted due to SIGALRM. Class1Modem::sendTCF() calls Class1Modem::transmitData(), which in turn calls Class1Modem::sendClass1Data() with a timeout of Class1Modem::getDataTimeout() ms. However, as far as I can tell, dataTimeout hasn't been initialized yet: the only call to setDataTimeout() in Class1Send.c++ is in Class1Modem::sendTraining(), and that's only done after the call to sendTCF(). Some extra logging in ModemServer::startTimeout() confirms it: Nov 07 03:34:19.80: [21626]: <-- [11:AT+FTM=145\r] Nov 07 03:34:19.80: [21626]: startTimeout(30000) Nov 07 03:34:19.80: [21626]: startTimeout(30000) Nov 07 03:34:19.81: [21626]: startTimeout(30000) Nov 07 03:34:21.28: [21626]: --> [7:CONNECT] Nov 07 03:34:21.28: [21626]: <-- data [1024] Nov 07 03:34:21.28: [21626]: startTimeout(1040910381272731340) Nov 07 03:34:21.28: [21626]: <-- data [2] Nov 07 03:34:21.29: [21626]: startTimeout(1040910381272731340) Nov 07 03:34:21.81: [21626]: Problem sending TCF data While I didn't see a maximum timeout mentioned in NetBSD's documentation for setitimer(), apparently trying to set a timeout of 33 million years doesn't work properly, and it raises SIGALRM almost immediately, interrupting the write(). ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

Re: hylafax/libhylafax update now available

Aidan Van Dyk — 2008-10-01T20:46:07

2008/9/30 Aidan Van Dyk ifax.com>: This goes back to the age old question, should "users" have *any* control over the tagline (or TSI) at all. If you go up to your local fax machine, do you change the TSI and tagline before you send every fax? And now that jobcontrol makes it so easy for an admin to do anything special for/based on a user... And remember that the "Admin" has the legal liability as to the TSI/Tagline transmitted as well... Now that I've fixed the accounting, so skipped pages don't appear in xferfaxlog, I'm of the opinion that "skipped pages" should *always* be counted... But that may be because the use of page ranges I've had in mind (resubmitting faxes using range to only include a few pages). So I don't see the "CountSkippedPages" as a knob that generally would be used (like most of the knobs we provide). If you're skipping pages of something, then likely your cover page should say that. But somebody, somewhere might like to not have the counted... Skipped pages are now no longer included in xferfaxlog, and notify has access to all the numbers, total pages, skipped pages, etc.

hylafax/faxd update now available

2008-10-01T20:43:25

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv15748/faxd Modified Files: ModemConfig.c++ Log Message: Whitespace cleanup ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/faxd update now available

2008-10-01T20:21:05

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv15072/faxd Modified Files: FaxSend.c++ Log Message: faxsend: Don't count skipped pages as transmitted in xferfaxlog accounting Including skipped pages (especially when large documetns are "Reprocessed" to send a page or two can really throw off reports based on xferfaxlog, such as xferfaxstats. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/man update now available

2008-10-01T20:06:52

Update of /usr/local/cvsroot/hylafax/man In directory cvs.hylafax.org:/tmp/cvs-serv14629/man Modified Files: hylafax-config.4f Log Message: Track skipped pages and cover pages Setting TagLineCoverNumString implies that you *don't* want to include the cover pages in the normal page numbering. The tagline page numbers will adjusted to not count the cover pages, and instead of using the page number of the cover page, the set string will used instead. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/faxd update now available

2008-10-01T20:06:52

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv14629/faxd Modified Files: Class1.h Class1Send.c++ Class2.h Class20.c++ Class20.h Class2Ersatz.c++ Class2Ersatz.h Class2Send.c++ FaxModem.c++ FaxModem.h FaxRequest.c++ FaxRequest.h FaxSend.c++ FaxServer.h ModemConfig.c++ ModemConfig.h TagLine.c++ faxQueueApp.c++ faxSendApp.c++ faxSendApp.h mkhash.c Log Message: Track skipped pages and cover pages Setting TagLineCoverNumString implies that you *don't* want to include the cover pages in the normal page numbering. The tagline page numbers will adjusted to not count the cover pages, and instead of using the page number of the cover page, the set string will used instead. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/man update now available

2008-10-01T20:03:40

Update of /usr/local/cvsroot/hylafax/man In directory cvs.hylafax.org:/tmp/cvs-serv14392/man Modified Files: sendfax.1 Log Message: Track cover pages in page range handling Making the "page range" be inclusive of everything is problematic, since continuation cover pages can "change" the pages of a document. This tracks cover pages, and makes the page-range handling exlude cover pages from it's range handling. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/faxd update now available

2008-10-01T20:03:39

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv14392/faxd Modified Files: FaxRequest.c++ FaxRequest.h faxQueueApp.c++ mkhash.c Log Message: Track cover pages in page range handling Making the "page range" be inclusive of everything is problematic, since continuation cover pages can "change" the pages of a document. This tracks cover pages, and makes the page-range handling exlude cover pages from it's range handling. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

hylafax/faxd update now available

2008-10-01T20:03:24

Update of /usr/local/cvsroot/hylafax/faxd In directory cvs.hylafax.org:/tmp/cvs-serv14322/faxd Modified Files: faxQueueApp.c++ Log Message: Cleanup pagehandling/skip in faxq ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null

Re: hylafax/libhylafax update now available

Aidan Van Dyk — 2008-10-01T01:19:44

* Lee Howard howardsilvan.com> [080930 19:13]: Yes, that's more common than I would like.. Unfortunately... And the times it does, it's usually in the middle of a long document, and "users" seldom have the tools to easily pull pages out of a longer document ;-( ;-( ;-( In the wild we see recievers without ECM, who get single bad pages in the midst of many acceptable pages... This patch currently supports that. At least if page numbering in the tagline uses "page number of job" instead of just "page number". Ya, I'm currently working on cleaning up that accounting a bit. My thoughts recently is that the tagline counting and "accounting" counting need to be seperated from eachother. For more reasons just that (think continuation cover pages). Well, that's why there was the "Count Skipped Pages", which was supposed to make those pages "just disappear" instead of be counted as having a 0:00 time. But that turned out to be a bit inflexible. The other thing your missing is that the ranges also get buggered on continuation cover pages ;-) I've got something in the back burner to fix that (and the accounting bit), but I keep getting interrupted with "other work" ;-( Hopefully tomorrow will leave me a chance to finish that up... a.

Re: hylafax/libhylafax update now available

Lee Howard — 2008-09-30T23:12:41

Okay, certainly this page range thing is kind of cool... say I have a document and I want to send pages 1, 3, 5, 7, and 9-12. So, it's cool, but I have a hard time envisioning the practical purpose behind its coolness. I do see a purpose in, perhaps, skipping some initial pages in a situation where maybe it was able to send those initial pages in a previous job (and then failed). Is it for the case where the receiver may contact the sender and say, "Hey, I can't read pages 4-5 and pages 10-11. Can you resend just those pages?" Does that happen often enough that a user will employ the feature? And certainly for such a purpose the user may want to ensure that the tagline page counting, etc., reflect that of the original and not the resend. But, to put the decision of whether or not to include those skipped pages on the tagline counts in the hands of the modem configuration instead of in the hands of the client (who requested the skipping) seems misguided. And then to actually account for those pages as being sent in 00:00 in xferfaxlog seems a sure-fire way to work against xferfaxstats credibility and the pages-sent information reported back by notify. I haven't read through the entire set of related code changes. Am I missing something? Thanks, Lee. ____________________ HylaFAX(tm) Developers Mailing List ____________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-devel-request< at >hylafax.org < /dev/null