Re: [hylafax-users] ModemClass problem

[Darren Nickerson <darren@dazza.org>]

>>>>> On Mon, 31 Jul 2000, "Mohan" == Mohan Khurana wrote:

  Mohan> Hi HylaFax enthusiasts,

  Mohan> I have hylafax-4.1.b2 installed on a FreeBSD 4.0 system, using 2 
3Com/USR
  Mohan> Courier V.Everything modems.  I'm trying to use the ModemClass value 
in my
  Mohan> config file to tell HylaFax to only send outbound faxes from the cuaa1
  Mohan> device on my system.

Cool! Looks like you got a long way down the line with HylaFAX!! ;-)

  Mohan> So this is what I have:

  Mohan> faxengine# grep "ModemClass" /var/spool/fax/etc/config
  Mohan> ModemClass:             "any:cuaa1"

You might want to be trying ModemGroup . . . it was changed in this release 
because people were confusing it with fax class 1/2/2.0.

  Mohan> Yet when I do:

  Mohan> faxengine# sendfax -n -d 7987070 /etc/defaults/rc.conf
  Mohan> request id is 6 (group id 6) for host localhost (1 file)

  Mohan> Above I am trying to tell it to send from cuaa1 to cuaa0, which is the
  Mohan> 7987070 number.

  Mohan> I then see:

  Mohan> faxengine# faxstat
  Mohan> HylaFAX scheduler on faxengine.ny.razorfish.com: Running
  Mohan> Modem cuaa1 (+1.212.798.6618): Running and idle
  Mohan> Modem cuaa0 (+1.212.798.7070): Sending job 6

  Mohan> This is just wrong.

From man config (5):

       ModemGroup
              Define  a  logical name for a set of modem devices.
              This parameter can be used to define  a  name  that
              clients can use to refer to a collection of modems.
              The syntax is ``<name>:<regex>''  where  <name>  is
              the  name  for  the  group and <regex> is a regular
              expression  that  faxq(8C)  matches  against  known
              modems.  Thus for example, the default modem to use
              for a job, any, is  defined  as  ``any:.*''.   This
              parameter may be specified multiple times to define
              multiple modem classes.  Modem classes may overlap.
              The  actual set of modems in a modem class that are
              considered for use may vary based on  which  modems
              are believed to be ready for use.


You know, even if you had that config param right, I think it might not be 
that wrong at all! You see, you have two modems, and you set one up as 
belonging to ModemGroup "any", which is the default group anyway, so you 
didn't really accomplish much there ;-) You still had both modems in the same 
pool. The final nail in the proverbial coffin is that you didn't specify which 
modem group HylaFAX should use when you invoked sendfax:

       -h [modem@]host[:port]
                   Force the jobs to be processed on  a  specific
                   host   and,  optionally,  using  a  particular
                   modem.  The host may be either a symbolic name
                   or a network address.  If no -h option is sup­
                   plied, sendfax uses the FAXSERVER  environment
                   variable  to  identify  the  HylaFAX server to
                   which the jobs  should  be  directed.   If  no
                   server  is  specified then sendfax attempts to
                   contact a server on the  local  host.   If  no
                   modem  is specified, the job will be submitted
                   to any available modem.

Get all these ducks in a row and it should "just work"(tm).

-d




____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null