Re: flexfax: HylaFAX 4.0pl1: Use multiple modems for sending alpha-pages?

[Bill Suetholz <bill@centonline.com>]

Digi Realport Drivers look just like actual LOCAL terminal ports.  With
full control over the signals.  Now I would recommend that the faxmodems
be class 2 at least because of network issues.  When I had HylaFAX working
here I used realport drivers, and both 14.4 Sportsters, and Telebit
Worldblazer modems.

Bill Suetholz

>
>On Wed, 11 Feb 1998, Nico Garcia wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> On Tue, 10 Feb 1998, Paul Dugas wrote:
> 
> > For my first fax/paging server, I setup HylaFAX on my SPARC Solaris machine 
> > using a single USR 28,800 Fax modem.  Works great.  My customer, the Georgia 
> > DOT, is using it for personnel notifications of traffic problems.  It's 
> > become very popular and the single modem won't hack it so I added a couple 
> > more and thought I was done!
> 
> GOOD! You might also want to publish any changes you had to make on
> your USR's config files.
> 
> > the same server.  I know it will have to make a call for each one but does it 
> > have to do so on the same modem?  Can't it spin up all three at once?  I've 
> 
> It should be able to. How do you submit faxes? As text, Postscript, or
> TIFF files? And do you have funky things in your config files like
> ModemClass, which should be set to blank?
> 
> > what I'm seeing.  I've even tried running three 'sendpage' jobs to three 
> > different pager centrals with three different pin numbers but they still end 
> > up on the first modem.
> 
> > The details:
> > 	Sun SPARC Ultra
> > 	Solaris 2.5.1
> > 	HylaFAX v4.0pl1
> > 	One USR Sportster 28,800 (on cua/b)
> > 	Two MultiTech MT2834BR (on remote Digi PortServerII using their RealPort 
> > drivers)
> 
> WHOA RIGHT HERE! Try swapping the modems around. Put your Multitech
> modems on cua/b, see if they work there. Also be aware that HylaFAX
> isn't guaranteed to work remote terminal servers, for a lot of
> reasons. 
> 
> Try moving the USR over to ther remote server as well, and see what
> you get there. It just might be a modem configuration problem.
> 
> 			Nico Garcia
> 			Engineer, CIRL 
> 			Mass. Eye and Ear Infirmary
> 			raoul@cirl.meei.harvard.edu
> 
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
> 
> iQCVAwUBNOHKWT/+ItycgIJRAQG3FAQAgklZx9/mW5AomOu1fUQysR7PyxOnAfqY
> P2dAaOpSAnaH3Vsq50Vde0ahClX5wshaLMUK0nBwiJO7NmwuZ8LfKejybbM41YAr
> Au62NB8NIDGmn2JulyEkhimXUlDa6/zJD2GstRDyTz5OBXCseznMu/kFUQApZ49Y
> zaO2arWUj+g=
> =Q7lF
> -----END PGP SIGNATURE-----
> 
>