If you have a fax server on your network... If you are running Win2K... (1) You can use the Fax Service Client API for Windows 2000. (There's a set of COM objects you can tlbimp.) ms-help://MS.VSCC/MS.MSDNVS/fax/faxlegacy_9lf4.htm
If you are running Windows .Net Server... (2) You can use the Fax Service Extended COM API (A different set of COM objects you can tlbimp.) ms-help://MS.VSCC/MS.MSDNVS/fax/faxportal_9nol.htm A nice object model can be found here: ms-help://MS.VSCC/MS.MSDNVS/fax/faxabout_6t2k.htm If you don't have a fax server... (3) Build one or buy one. For a low rent, low volume, fax server you can stick a fax modem card into a server, plug it into a phone line and use the Fax Service that comes bundled with Win2K and up. Alternatively... (4) Use an Internet based fax service. There's lots of different flavors/price ranges out there. Many of them use an email based system where you send an email (with attached document(s)) and they convert it to CCIT Group3/4 fax format and send it. I suspect SOAP based fax services are just around the corner, if not already available. Here's a link to a page outlining some of the more well-known services. It's from an end user perspective, but will give you a head start if you decide to go that way: http://www.savetz.com/fax/ Because services generally charge per minute, at a higher rate than your typical per minute line costs, it may be cheaper to purchase a 3rd party fax server (including hardware) and do (1) or (2) instead. When making this determination be sure to factor in not only your expected volume, but also things like: (pro) A. Long distance fees. The larger services have local numbers in most major markets so they can charge a flat rate per minute for all faxes. B. Some Fax services charge on a per-page basis. You can reap some big savings using one of these if most of your faxes are being sent to old, slower than molasses, fax machines at long distance area codes. Using a per-page service agreement has another advantage in that it's a lot easier to forecast your costs. C. Scalability. Scaling out an in-house fax server can get quite expensive. Especially if you have to pull wire or increase your junction board capacity. If using a fax service, scaling is their problem. D. Maintenance costs for a fax server. Somebody will need to ensure it's up and running and properly patched as time goes on. E. Fax server software/hardware could include high recurring (monthly or annual) support fees and/or "per fax" usage fees. (con) F. If you plan on a volume low enough to make alternative (3) viable, and most of your faxes are to your local calling area, the fees (weekly/monthly + per page/per minute) of a service provider are wasted money. F. Getting a fax server up and running, and having written the client code to send/receive faxes will look good on your resume. No matter the costs. <g> (neutral) G. The good 3rd party fax server packages include add-ins that integrate with existing desktop apps (like Outlook or Lotus Notes). Then again, so do some of the service providers. or... (4) For masochists with way too much time on their hands, roll your own using TAPI. You'll still need hardware of course. Keep Smilin' Ed Stegman -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Agus Kurniawan Sent: Wednesday, May 29, 2002 7:49 AM To: [EMAIL PROTECTED] Subject: Fax over TCP/IP in .NET Does anyone know how to send message via web (ASP.NET using C#) to fax machine ? is there URL about this ? agus k. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
