Hylafax Mailing List Archives

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

Re: [hylafax-users] MT5634ZBA-V92 with Hylafax



X-Arial Concept-MailScanner: Found to be clean
X-MailScanner-From: samp@xxxxxxxxxxxxxxxxx

Samuel De Leon a écrit :

Sam,

I have installed the MT5634ZBA -V.92 modem in Linux Red Hat Enterprise
running Hylafax fax server .4.21

I installed the modem as class 2 fax modems and I left all the defaults in
the software.



I succeeded to configure it in class 2 with the help of Giulio Orsero and the lucent-mt-2 config file. See my previous message on this list.


I ran a test receiving faxes from 3 different fax machines and I can not
make the faxes to fail.
From the tif file that you sent me it seems that the problem is do the FBOR
setting.

Try setting the command AT+FBOR=1  or AT+FBOR=0   in your configuration file
for what ever tty port the software is using. This will set the reverse bit
order while receiving.

At this point I can not tell you how to set the software to receive voice
and data calls, due that you need to configure Hylafax with the right getty
program to take the data call.

This is the info from Hylafax setup documentation;

"Call answering is done as follows: 1. Send the modem one of ModemAnswerDataCmd, ModemAnswerFaxCmd, and
ModemAnswerVoiceCmd according to whether the call is to be answered as data,
fax, or voice, respectively. If any of these are not set then ModemAnswerCmd
is used instead. 2. Wait for a response from the modem that signifies carrier has been
established and which identifies the type of call. The exact set of
responses is given in config(4F). 3. If ModemWaitForConnect is enabled, then HylaFAX will read responses from
the modem until a CONNECT response is sent to the host or an error is
detected; e.g. 4. Host Modem
5. ATA -->
6. <-- DATA
<-- CONNECT
7. If a call is successfully answered, then one of ModemAnswerDataBeginCmd,
ModemAnswerFaxBeginCmd, and ModemAnswerVoiceBeginCmd, is sent to the modem
according to the call type deduced above. This mechanism is useful for
modems that automatically change DTE-DCE communication to a fixed line speed
or flow control setting for inbound facsimile calls. At this point the call has been answered, carrier established, and the call
type is known. * Data calls are handled by invoking a system getty program; but only if the
GettyArgs parameter is set. * Voice calls are handled by invoking a system vgetty program; but only if
the VGettyArgs parameter is set. * Facsimile calls are handled directly in faxgetty. For a data or voice call faxgetty forks and execs the appropriate program.
The UUCP lock file is setup so that it is owned by the child (important for
SLIP and PPP) and the parent handles cleanup of various resources when the
child process terminates. For fax operation faxgetty drops into the facsimile receive protocol. "
So is seems that if the configuration in the software is not correct the
data call will not work.
I just tried setting adaptive answer in the software and the modem will
answer in either fax or data mode.
The problem is this the configuration in that my configuration somewhere in
the system is wrong and this what the log file is showing.


Mar 22 14:37:01.92: [ 3145]: HylaFAX (tm) Version 4.2.1
Mar 22 14:37:01.92: [ 3145]: <-- [4:ATA\r]
Mar 22 14:37:06.03: [ 3145]: --> [4:DATA]
Mar 22 14:37:06.03: [ 3145]: ANSWER: DATA CONNECTION
Mar 22 14:37:06.05: [ 3145]: runGetty::initgroups: Operation not permitted
Mar 22 14:37:06.06: [ 3145]: GETTY: START "/sbin/agetty -h ttyS0 dx_19200",
pid
6310
Mar 22 14:37:16.14: [ 3145]: GETTY: exit status 0400
Mar 22 14:37:16.14: [ 3145]: SESSION END
So at this point the modem will answer in fax or data mode but the software
the system and the software need to be configured correctly. I'm not an
expert in Hylafax or Linux this is the reason I can not tell you what to
check.


Perhaps a getty setting, I use mgetty and after fix some points in the mgetty config file the data call are well passed to it from FaxGetty, but it seems that the "runGetty::initgroups" error is a bug corrected in the last cvs, there is a message on this list about this bug.

Thanks for your help.

Sam.


-- Ce message a été vérifié par MailScanner pour des virus ou des polluriels et rien de suspect n'a été trouvé.



____________________ 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*



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services