| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | mgetty + ifcico |
andrew clarke wrote in a message to Scott Little: ac> Tue 2005-05-10 05:07, Scott Little (3:712/848) wrote to andrew ac> clarke: ac>> Well, I have mgetty receiving faxes now! I don't have any easy way to ac>> test whether the front-end mailer (ifcico) works though. If anyone ac>> has any free time on their hands, and can afford the cost of the call, ac>> could they netmail 3:633/267 at +61-3-9787-8373, ie. poll via dialup. SL> I get CONNECT 14400/ARQ and then garble. The modem port might need SL> some setserial action... even though it claims it's not SL> necessary/obsolete, I find setting it manually to 38400 or 57600 SL> fixes this most of the time. ac> Hmm, well there's no setserial in FreeBSD. I have "speed 38400" ac> set in mgetty.config though. I managed to find an old Swann V34 ac> modem and my very first modem, a Telecom TEL 424. The best I could ac> get was a 2400 baud connect. ac> I tend to think the answering modem is faulty or that the line ac> quality is so bad that the modem can't deal with it. Sending a fax ac> to it has been perfect though, so the line is probably not too bad. ac> It's a Genius GM56flexE-G2, set to factory defaults (AT&F). I ac> might need to hunt around for another modem I think. ac> The Swann V34 was useless on the answering side as it hangs up ac> shortly after the CONNECT FAX when being called from a fax machine ac> (newish Samsung). Is this mgetty thing what I'd need to be able to send faxes? I suppose I'd need to install it on the firewall/router box where the modem is actually connected, then? ---* Origin: TANSTAAFL BBS 717-838-8539 (1:270/615) SEEN-BY: 633/267 270 @PATH: 270/615 150/220 3613/1275 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.