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] Question: Communication error, call aborted




On Thu, 7 Dec 2000, Lee Howard wrote:

> At 02:15 PM 12/7/00 +0100, Derrick R. Sambo wrote:
> >Dear all,
> >
> >We have an HP9000/D330 (s800) running HP-UX 10.20 with a Wisecom
> >V.90/K56flex class 2 faxmodem (it has a Rockwell AC/K56 chip). But I
> >cannot get HylaFax to work correctly on this system.
> 
> I'm assuming that you're using 4.1beta2 from tarball?  I'm also assuming
> that faxaddmodem detected your modem and used a prototype config template?
> Or did you manually enter in all of the AT+F commands?
>

No, I used version 4.0pl2-2, the binary build. I didn't want to use a beta
version since this is quite a critical system to us. And faxaddmodem
detected my modem and used a prototype config template (Rockwell)
 
> >I downloaded and installed all necessary software and ran faxsetup. Adding
> >the modem prooved difficult, so I changed some timeouts in the faxaddmodem
> >script (ONLY timeouts!) and the modem was recognised. Sending faxes also
> 
> You may want to post your alterations to the hylafax-devel list.  Robert
> may be interested in seeing them.  There have been many changes in the CVS
> as of late, though, to faxaddmodem.

It only concerned timeouts ('sleep 2' instead of 'sleep 1'). And
incidentally the original version also worked well. But I'll send my
findings to the devel-list, even though I used an older version.

> ....
> >The difference starts at line 06. The old server ends with AT+FET=2\r,
> >while the new server uses AT+FK\r. Apparently this is not the correct way
> >of terminating the communication. But since I cannot find a list of
> >AT+Fxxx commands, I can not verify the correctness of it.
> >
> >If this is indeed the problem, how can it be solved? How can I specify
> >which AT command should be used to close the connection?
> 
> It would appear that the config file is wrong.  (And that's why I ask about
> using a prototype config file by default.)  I'd bet that if you moved the
> old modem to the new server and then re-ran faxaddmodem, that you would not
> have this trouble with the faxes.  If so, then you probably need to work
> out your config file for the new modem.
> 

I tried different configs but nothing worked. So I moved the old modem to
the new server and we were in business! So for the time being we will work
with the old modem, but since we don't have a replacement in case of
hardware failure, I'll try to work out something to get the new modem
working. If I succeed, I'll notify the devel-list.

> Lee.
> 

Thanks very much

Derrick Sambo

-----------------------------------------------------------------------------
Derrick R. Sambo                Technische Universiteit Delft
UNIX Systems Specialist         Dienst Technische Ondersteuning
                                Mekelweg 6
                _               2628 CD  Delft, Nederland
               /                Tel:  +31 15 278 3161
              dtO               Fax:  +31 15 278 6359
                _/              Mail: D.R.Sambo@dto.tudelft.nl
                                WWW:  http://nic.ced.tudelft.nl/~derrick
-----------------------------------------------------------------------------





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




Project hosted by iFAX Solutions