HylaFAX The world's
most advanced open source fax server
Re: [hylafax-users] What's the best solution
From: "Jeremy Fowler"
> Ok, I have a problem and I need to get some opinions. Our current fax
setup is a
> single Linux Box with 4 modems that receive incoming faxes from a hunt
> our Nortel Meridian 1 Option 11C PBX for our one main fax number that
> uses. Hylafax receives the faxes and emails them to our receptionist to be
> sorted and forwarded. Recently there was a mix-up and someone received a
> they shouldn't have. This upset some VIPs, so now we are looking for a
> so it "never happens again".
It is inevitable that any time something bad happens, those in power need to
an edict saying to "Never Let It Happen Again". Whether or not this is
irrelevant. My Sympathies :(
> The idea was thrown out that everyone gets their
> own fax line and then manages their own faxes. Besides being very costly,
> think it would be a nightmare to implement. What are our options? Caller
> and/or TID routing isn't an option since people may use the same external
> machine to fax different people in the office. I have some ideas, but I
> know if it's possible since I'm not a Telco guy and don't have very much
> experience with corporate fax solutions and what products are available.
> Ideal solution 1 (probably doesn't exist):
> A person faxes to someone here at their normal DID (voice) extension. The
> auto-detects that the incoming call is a fax and routes it to a digital
> on our Linux box. Hylafax sees the DID extension that the fax was sent to
> looks up the extension in a database to find the email address and happily
> it on it's way. Everyone is happy.
> Now I know they have line share devices for normal analog (POTS) lines
> able to detect whether an incoming call is a voice or fax and route it to
> appropriate device. However, the Telco guy that administers our PBX
> think there is such a device for digital systems. Has anyone heard of
> doing something similar?
Number one doesn't sound so good. If you could get some form of hardware for
PBX that would sense the incoming fax call, and be able to pass the call,
along with the
DID information in question, to HylaFAX, then you'd be good to go. This
piece of your PBX could be hard to come by however.
> Ideal solution 2 (probably another long shot):
> We provision another set of DID numbers for everyone in the office for use
> incoming fax lines. Anything that comes in on those DIDs are forwarded to
> type of digital fax card running on our Linux box. The card tells Hylafax
> DID number the call came in on and thus forwards it to the appropriate
> The card doesn't need to handle 80+ inbound calls at once, but should be
> tell what DID it was meant for. Meaning, the card should have about 10-20
> it can use at any one time and an incoming fax will use the next available
> on the card.
Considerably more likely. What you would need would be your 80 DIDs, ISDN
line incoming, the cooperation of your local telco to provide the DID
ISDN card which works with HylaFAX, a little time and patience, and voila.
not be a cheap solution, but it is doable. I believe that the Eicon DIVA
been reported to work well in this application. I have not done this, but
it for our own setup. When I gave my boss the price tag, it was quickly shot
If there is a hard core push for this, there is now a commercial provider of
support that you can consult with, email firstname.lastname@example.org if you want to go
Otherwise, check the mailing list archives for DID and/or DNIS, it should
some hits for you.
BTW, if anyone who has done this is feeling generous, this would probably
great topic for a how-to. The question comes up often enough.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe email@example.com < /dev/null
*To learn about commercial HylaFAX(tm) support, mail firstname.lastname@example.org.*