HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Recipient Not Receiving Fax

--- On Tue, 8/10/10, Lee Howard <lee.howard@xxxxxxxxxxxx> wrote:

> From: Lee Howard <lee.howard@xxxxxxxxxxxx>
> Subject: Re: [hylafax-users] Recipient Not Receiving Fax
> To: "Yong Tze-Howe" <tze-howe@xxxxxxxxxxxxxx>
> Cc: "HylaFAX-Users" <hylafax-users@xxxxxxxxxxx>
> Date: Tuesday, August 10, 2010, 4:19 AM
> Yong Tze-Howe wrote:
> > Previous I was having trouble faxing with a USB fax
> modem. Recently I acquired a Mainpine IQ Express board
> hoping that it could solve any issues related to the fax
> hardware.
> > 
> > I think I have old problems solved but was met with
> new problem. I test sent batches of faxes from 20+ to 50+.
> The issue I discovered is that for some numbers, although
> the log indicates that fax was successfully sent. The
> intended recipients did not receive them.
> >   
> The session log indicated that the receiver signaled MCF
> but the intended recipients did not receive them?  What
> is the destination to which you are sending these batches of
> faxes?  Are the faxes really being sent in batches
> (multiple fax jobs in one call)?

I'm not sure I get this. Does the string below indicate that the receiver acknowledges that it received the MCF signal?

Aug 09 15:47:50.96: [ 2851]: SEND recv MCF (message confirmation)
Aug 09 15:47:50.96: [ 2851]: <-- [9:AT+FRS=7\r]
Aug 09 15:47:51.13: [ 2851]: --> [2:OK]

There are mixtures of local and other state calls.

Sorry for not making this clear. I send faxes to multiple numbers at one time. Wait until the queue was empty. Then only check the results. This is what I mean by one "batch". After that I proceed to send another "batch" containing numbers for recipients that failed to receive fax during the 1st "batch".

> > This issue seems to be random. For the same number,
> the recipient may not have received the fax for the 1st send
> job, but did receive fax for the 2nd send job. I compared
> both logs and the communication method/procotol are
> identical.
> > 
> > I have no idea how to go about tracing this issue. Any
> help would be appreciated.
> Start by showing us a session log where the recipient did
> not get the fax.

Sorry about that. Here's the log files. The recipients did not receive fax from the 1st send job for the numbers in the log.

> > Below is some of the information about my fax
> hardwares and softwares:
> > 
> > OS: CentOS 5.5 (64-bit)
> > Kernel (Patched): 2.6.18-194.8.1.el5.ifax3; Patched
> following the guides from http://www.hylafax.org/content/Handbook:Basic_Server_Configuration:Modem-specific_Guidance
> and http://wiki.centos.org/HowTos/Custom_Kernel
> > HylaFAX: hylafax-server-6.0.4-1rhel5
> > Fax Board: Mainpine CFAX34 (October 30 2009)
> Polaris DP3SH
> There is a firmware update available for the IQ Express,
> but you'd need to move the card temporarily into a Windows
> system and have a Mainpine technician connect remotely to
> perform the firmware update.  I do not believe that
> merely performing the firmware update will resolve the
> problem you mention.

I agree with you. Firmware upgrade is not an option for me unless it's highly likely to be able to solve this issue.



> Thanks,
> Lee.
> -- *Lee Howard*
> *Mainpine, Inc. Software Development Lead*
> Tel: +1 866 363 6680 | Fax: +1 360 462 8160
> lee.howard@xxxxxxxxxxxx
> | www.mainpine.com


Attachment: session_log.zip
Description: Zip archive

Project hosted by iFAX Solutions