Re: [hylafax-users] pagesend

[Tony Delov <Tony.Delov@xxxxxxxxxxxxxxx>]

Lee Howard wrote:
> Tony Delov wrote:
>
> > I've been wondering if its the way we have the modems set up?
> > We have out modems connected to a stallion port server  and  a small 
> > program running on the linux servers that maps a pseudo device pttya4 
> > to ttya4 device?
> That could very well be it, yes.  The easy way to test that would be 
> to take one of those modems and connect it directly to the HylaFAX 
> server's serial ports and test it there.
I don't have a Serial port no the Blade server that the faxserver is 
connected, so that is not an option. However, I have another functioning 
hylafax faxserver with a functioning and production mode fax server  and 
pager running hylafax-4.1.7 There is a modem on that system, connected 
to the serial connection. (ttyS0). The same sort of modem as on all tests.

That server can send pager messages through the serial device (ttyS0) 
without any problems.
Send fax works without a problem on the pseudo devices and sends faxes 
as per normal.
PageSend failed through the pseudo devices. (see logs)

This is from  a fax server running "hylafax-4.1.7". The same type of errors
See logs:

May 26 11:34:38 kate PageSend[11627]: <-- [5:ATM0\r]
May 26 11:34:38 kate PageSend[11627]: --> [2:OK]
May 26 11:34:38 kate PageSend[11627]: MODEM set parity: 7 bits, even parity
May 26 11:34:38 kate PageSend[11627]: MODEM tcsetattr: Invalid argument
May 26 11:34:38 kate PageSend[11627]: STATE CHANGE: BASE -> MODEMWAIT (timeout 30)
May 26 11:34:38 kate PageSend[11627]: MODEM input buffering enabled
May 26 11:54:33 kate PageSend[18890]: MODEM set baud rate: 38400 baud, input flow RTS/CTS, output flow RTS/CTS
May 26 11:54:33 kate PageSend[18890]: MODEM tcsetattr: Invalid argument

May 26 11:57:35 kate PageSend[22125]: MODEM set baud rate: 38400 baud, input flow RTS/CTS, output flow RTS/CTS
May 26 11:57:35 kate PageSend[22125]: MODEM tcsetattr: Invalid argument
May 26 11:57:35 kate PageSend[22125]: MODEM set DTR OFF
May 26 11:57:35 kate PageSend[22125]: MODEM set baud rate: 0 baud (flow control unchanged)
May 26 11:57:35 kate PageSend[22125]: MODEM tcsetattr: Invalid argument
May 26 11:57:35 kate PageSend[22125]: DELAY 75 ms
May 26 11:57:35 kate PageSend[22125]: MODEM set DTR ON
May 26 11:57:35 kate PageSend[22125]: DELAY 2600 ms
May 26 11:57:38 kate PageSend[22125]: MODEM set baud rate: 38400 baud, input flow RTS/CTS, output flow RTS/CTS
May 26 11:57:38 kate PageSend[22125]: MODEM tcsetattr: Invalid argument



> You may also want to review the patch on this bug report:
>
>  http://bugs.hylafax.org/show_bug.cgi?id=425
>
> The patch there contains lots of code changes that are unrelated to 
> the bug report itself, and the patch isn't likely to apply cleanly to 
> any current source code, but maybe it would give you some hints as to 
> where the problem lay.
I'm not much of a c programmer.. So, from what I could understand about 
those patches, they applied for "TCP modems"?
The svr_tty (stallion connected modems) appear as actual standard modem 
devices in the linux system, they are treated the same way a modem 
connected to the actual computer is treated.
Sendfax treats them as standard modems.




> > Which sends the faxes ok.
> >
> > May 25 11:23:52 hylafax FaxQueuer[17422]: SUBMIT JOB 141740
> > May 25 11:24:02 hylafax FaxSend[17216]: MODEM set DTR OFF
> > May 25 11:24:02 hylafax FaxSend[17216]: MODEM set baud rate: 0 baud 
> > (flow control unchanged) 
> This is  a log of Faxsend going through the the same modem as the 
> pagesend logs mentioned earlier.
>
> This is very interesting.  I'd like to get to the bottom of it.  I'm 
> relatively certain, however, that the only difference between FaxSend 
> and PageSend initializations is that setParity call... well, at least 
> I'm pretty sure that's it.
>
> Thanks,
>
> Lee.


Attention:
The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies.

Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of The Gribbles Group.

Thank You.

Whilst every effort has been made to ensure that this e-mail message and any attachments are free from viruses, you should scan this message and any attachments.
Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachment.

____________________ 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@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*