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] routing received faxes to clients



Lee,

  You are (as usual) right about DID being the best way to do this.
However, I have tried to make that sale to a small business client, and
it's a high hurdle.  In many cases, it involves switching at least phone
plans, and in his case phone companies.  It simply wasn't worth the
effort.

  I hope I don't move this off-topic, but right now, we're primarily
concerned with routing faxed-in applications.  These are on our standard
forms, and it is very possible for us to "force"  them to send in apps on
our forms (we already do for regulatory reasons).

  I have floated the idea of barcoding through my customer, and they love
the idea.  However, after searching the archive, I have found little help
(Basically, one guy said he found a $50 solution.... but didn't post it
:(  ).

  Lee, do you have any experience with this?  I know you have settled on
DID for your current application, but perhaps you have a trail you've
given up on that I could pick up?  (It would be VERY nice to route inbound
apps to the processor for the right state.  I know that sounds minor, but
it really isn't in this case.)

Thanks
Bill



On Tue, 6 Jul 2004, Lee Howard wrote:

> On 2004.07.04 08:56 Ted Egan wrote:
> > I need a way to route received faxes.
>
> Plain and simple, there is no better way than to use DID/DNIS or a
> separate line+modem for each recipeint.  Looking for some other way to
> route faxes will ulimately result in something less-reliable, although
> less expensive up-front.
>
> > I am considering forcing
> > senders to use
> > a standardized cover page which I can then convert to text and parse.
>
> While you're at it (forcing senders to do stuff) could you force them
> to send a subaddress (SUB)?  You can route based on subaddressing.  You
> wouldn't need any OCR application for that.  Some fax machines don't
> have that capability, however, so that may not work for you.
>
> > The
> > faxes can come from anywere, so TSI and CSI won't work.
>
> I think that you mean TSI and CID.  CSI is the called station
> identification (you, the receiver).
>
> > Is there a simple way to extract the text contents of a received fax?
>
> Look through the archives for "OCR".
>
> Lee.
>
> ____________________ HylaFAX(tm) Users Mailing List _______________________
>   To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
>  On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
>   *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
>
>


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*




Project hosted by iFAX Solutions