Do you still fax things like this? You type a document in your favorite word processor, save the document, print it to a laser printer, walk over to get the document, walk to the physical fax machine, and find a cover page. (Oops, who has a pen?) You fill out the cover page, load the document, then stop to make sure that it’s not upside down and that it’s oriented the correct way. (Where is that guy's fax number? It's back at the desk.) You dial the number. Busy. Wait. Redial. Connect. Paper jammed. Clear the jam. Retry. Busy. Wait. Redial. Connect. It’s sent! Whew!
There is a better, more efficient way. By adding fax services to your organization’s server, you can send faxes directly from your computer using your network connection. Here’s how you can lay the foundation for server-based faxing.
Why do I need a fax server?
There are many reasons why you might want to add fax services to your server:
- NetWare is robust and does a good job of hosting faxing services.
- Network laser printers can print a cheaper, and sometimes faster, page than a traditional fax machine.
- Your departmental fax machine is overloaded with incoming faxes.
- You need to keep copies of incoming faxes on your server.
- You can cut communication costs while allowing broader services.
- You can provide every user with the ability to send faxes from their PC (just like a print queue).
- If you have GroupWise, you can have incoming faxes automatically routed to users.
- It can help increase employee productivity.
It sounds good, but how will I use this service?
The NetWare server hosting a fax application server can be set up in a variety of configurations. For example, the server can be set up to only receive or to only send faxes. You can also assign users permission to route, print, and delete unimportant faxes that come in and give anyone with a login account the ability to send faxes from their PC.
If your server is on a WAN with many servers, you should consider getting a large user license so that remote users can also send out faxes. In terms of bandwidth, the average file size of a one-page fax is around 150 KB, so it is feasible for WAN users.
The fax hardware adapter manufacturers specify the operating system recommendations. Because NetWare does a good job handling the amount of network overhead and traffic that faxing can create, many fax vendors support it. You will probably be able to just add network fax hardware and software NLMs to your existing server.
Examining your phone lines
The first task on your list when preparing for a switch to network-based faxing is to determine the number of lines you'll need, based on the number of users and anticipated usage of the fax system.
A single NetWare server can scale from one line to 144 lines. You just need the hardware and horsepower to drive it. If your server is correctly sized for your user base, then you won’t need to add any hardware to your server other than the PCI fax card(s). That’s why it makes sense to first determine how many phone lines you need because it will probably be more of a bottleneck than your server.
I believe Direct Inward Dial (DID) lines are the best thing since sliced bread. You should consider getting this type of line if you want to provide users on the network with their own personal fax numbers. People really love having their own fax number; no more digging through a pile of faxes to find the one you want, no more wondering if someone else saw the fax first. Beyond just making them happy, you might actually need to provide users with their own fax numbers in order for them to receive faxes.
DID lines work similarly to network interface cards that can have multiple IP addresses assigned or bound to them. With DID, the general rule of thumb is that you assign 10 to 15 numbers to one physical DID line.
As ”Inward” suggests, this type of line can only receive calls; it cannot originate them. So count on getting a few additional lines to deliver outbound faxes. Two to three lines for outgoing faxes will work well in smaller environments, as shown in Figure A.
The numbers game
When you order the DID lines from the telephone company, purchase a range of phone numbers (for example, 555-4500 through 555-4530). Expect to pay around $80 per month for a block of 100 phone numbers. Once you know how many numbers you’ll be using, you’ll be able to know how many lines you’ll need. For example, let’s say you’ll be using 30 numbers. As I mentioned earlier, 10 to 15 numbers can be assigned to one DID line. So with 30 numbers, you would purchase two physical DID lines and have the first 15 numbers (555-4500 through 555-4515) point to one DID line and the last 15 (555-4516 through 555-4530) point to the other DID line.
To use DID lines, you will need a PCI fax card that has DID ports on it. In my opinion, Brooktrout has the best quality fax cards available. Don't consider using Class 2.0 fax modems as they eat server power and are not as reliable or efficient as an intelligent fax server adapter. Trust me—don't skimp on hardware. If incoming or outgoing faxes fail, people will stop trusting the technology and then stop using it. With an intelligent server-based fax adapter, you'll have a near perfect success rate and be able to send and receive faxes anywhere (even to the old 1980s thermal facsimile units some people still seem to have in use).
DID lines require the fax adapter to get power from a special -48v DC transformer that you must connect externally to the fax adapter. If you do get a DID fax card, the power supply should come with it; if not, you can order one from Tellabs.
T1 service for your network fax card
If you're going to deploy a lot of numbers immediately, however, consider getting a high-density ISDN (Integrated Services Digital Network) PRI E1 or T1 line that carries dedicated channels of voice or data traffic. You’ll need an ISDN or T1 card or cards installed in your server. These cards in turn are connected internally to your fax card or cards as shown in Figures B and C.
|A typical configuration for a T1 hookup for fax lines|
|A typical configuration for an ISDN PRI hookup for fax lines|
With T1-based fax bandwidth, you have 24 clean digital channels available to you coming in on one piece of wire. I say channels because that's really what they are, and this is much better than having 24 analog lines. For example, let's say you have the T1 service, and you have 100 personal user fax numbers and a few company 800-number fax numbers pointed at the T1. All of a sudden, you have a flood of incoming faxes on one of the 800 numbers. Twenty of the channels can simultaneously accept faxes for that one particular number, without having to have 20 physical copper wires with that particular 800 number written on them.
By the same token, if all 100 users decide to send a two-page fax at the same time, 20 of the channels will service all of these outgoing jobs, and it will only take about 15 minutes. I've used the number 20 in these examples because you can create a pool of channels that can be dynamically allocated by any number of phone/fax numbers, while still leaving four channels on reserve for special numbers. It would be pretty tough to light all 24 channels at the same time sending and receiving faxes.
You can get help from your telecom provider when you set this up. There are many phone companies offering fantastic rates on phone service and providing T1 service. I know in some large companies there is a separate department for phone services, but with faxes it’s basically just data and you don't have to interfere with your company’s PBX—you can just get the T1 installed right next to your server.
Making the leap to network-based faxing can help your organization work more efficiently, but only if you plan the change carefully and thoughtfully. By following the specifics outlined here, however, you should be on track to ensuring that the transition will be a smooth one.
Do you think your organization could benefit from network-based faxing? Do you believe the benefits outweigh the investment? Let us know what you think. Post a comment or send us a note.