Re: Fax pooling performance
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Wed, 18 Jan 2006 07:42:29 +1100
HMMMM, your cost per page just skyrocketed :-) (over 5yrs)
even at that volume I'd still seperate the task from the server and use
'proper' fax server software, ISDN lines and multiple ISDN FAX devices.
We've gone from a scenario having 3 busy workstations performing this task
to one unit which is not quite so busy.
With this level of demand I also expect that the more advanced features
offered by dedicated FAX software would benefit the organisation. Complex
FAX forms, programmatic submission of FAX, that sortta thing.
and we haven't mentioned incoming. Direct In Dial, where one or several
devices can handle 100's of numbers, routing faxes received on a single line
(or multiple) to individual users. This facility is not available in SBS
FAX.
I should mention. I was a support guy for a modem manufacturer who was also
the sole AU distributor of ZetaFax from Equisys, for a time I was the
primary support person for ZetaFax in AU. I'm not pushing you this direction
because of this previous relationship, just due to experience. If you want
robust FAX handling you need a system designed for the task.
"RMarmion" <RMarmion@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7664311A-38DE-4E24-9BF9-86FE58396B1F@xxxxxxxxxxxxxxxx
> SuperGumby,
>
> Thank you so much for your fact packed reply to my question! As I said in
> my reply to Brandy, I mis-stated the duty volume and it should be 50,000
> pages a month, not per week.
>
> I'll review all your suggestions in detail and incorporate them into my
> proposal.
>
> Regards, Rob
> --
> Robert Marmion
> ITBridges Inc
> 609 844 0949
> "Connecting your Business with your Software"
>
>
> "SuperGumby [SBS MVP]" wrote:
>
>> Brandy's theoretical calculations are reasonable, in a perfect world, and
>> we'd all like to live in one of them wouldn't we.
>>
>> Such high volume FAX starts to hit other limits, retries due to busy
>> signal,
>> mistyped or changed numbers retrying several times, people with shared
>> fax/voice lines going 'sh1t, it's not a person it's a fax, gotta run tell
>> the machine to answer', device reset times between calls, device
>> renegotiation due to noise on the line, exchange (that's Telephone
>> Exchange)
>> congestion. (that may be most, but I doubt it's all)
>>
>> Is the OP suggesting he is currently doing 60000 pages per week on four
>> lines? If so I know a major FAX software vendor who would like to have a
>> chat about the devices in use (yeah, I saw brooktrout mentioned). My gut
>> feel is that every sending, and receiving, device would need to be doing
>> 33K6 FAX to support this level of activity.
>>
>> Would SBS handle it? Not in my lunchtime! No matter what the faxboard's
>> capabilities the system behind it still needs to process the
>> transmissions,
>> convert those Word docos to .tif, and pump them across the bus to the
>> card(s). Keeping in mind that FAX is a very time critical process.
>>
>> SO, you're planning on 60000+ faxes per week, that's 3+mil per year.
>> Amortise the cost of the system over 5yrs and we're talking about 'How
>> much
>> does it cost to put together a system capable of sending 15or16mil fax
>> pages
>> in 5 years?'
>>
>> 3 workstations, each having a 4 port FAX device. Let's call it AU$1000
>> for
>> the PC's and AU$1500 for the fax boards. 7.5 grand AU$. Once off.
>> Software from ZetaFax (my preference) or maybe GFI, plus configuration
>> services and ongoing support. 10G AU$. over five years but most up front.
>> 12 ISDN phone lines. (not even sure of ballpark cost in AU, let alone
>> your
>> neck of the woods, wherever that may be)
>> Call costs.
>>
>> The ISDN line changes and call costs are a variable outside the scope of
>> any
>> argument, you're going to pay them whatever system you use.
>>
>> AU$17.5G divided by 15mil pages. AU$0.00583 per page, and it would work.
>> Throw in an SBS, the hardware to run it on, CALs and a copy of Office
>> Small
>> Business 2003 for a dozen users and over five years the complete system
>> _might_ cost them AU$0.01 per page (plus line rental and call charges).
>>
>> ""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:xJbnyEzGGHA.3696@xxxxxxxxxxxxxxxxxxxxxxxx
>> > Dear Customer,
>> >
>> > Thank you for posting to the SBS Newsgroup.
>> >
>> > I understand that you want to know whether SBS 2K3 Server can support
>> > over
>> > 60,000 faxes every week. If I have misunderstood your concern, please
>> > let
>> > me know.
>> >
>> > From my point of view, this issue is more related with the performance
>> > of
>> > the fax modem. SBS 2K3 Server can support up to four fax modems at the
>> > same
>> > time. According to the fax modem performance, it normally takes you
>> > about
>> > 1
>> > min to send out one page of fax. Ideally, four fax modems can send out
>> > 5760
>> > pages of faxes every day, which is 40,320 pages of faxes each week.
>> >
>> > If you plan to use SBS 2K3 Server, you need to make sure the fax modem
>> > is
>> > compatible with Windows Server 2003 operating system. You can check it
>> > in
>> > our Windows Server Catalog below:
>> >
>> > Windows Server Catalog
>> > http://www.microsoft.com/windows/catalog/server/
>> >
>> > For your additional information:
>> >
>> > Step-by-Step Guide for Configuring and Using Fax on Windows Small
>> > Business
>> > Server 2003
>> > http://www.microsoft.com/downloads/details.aspx?FamilyID=1b7510a0-1595-4776-
>> > a101-c3bec7512594&displaylang=en
>> >
>> > If you have any further questions or concerns, please feel free to let
>> > me
>> > know. I am looking forward to hearing from you!
>> >
>> > Best regards,
>> >
>> > Brandy Nee
>> >
>> > Microsoft CSS Online Newsgroup Support
>> >
>> > Get Secure! - www.microsoft.com/security
>> > ======================================================
>> > This newsgroup only focuses on SBS technical issues. If you have issues
>> > regarding other Microsoft products, you'd better post in the
>> > corresponding
>> > newsgroups so that they can be resolved in an efficient and timely
>> > manner.
>> > You can locate the newsgroup here:
>> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>> >
>> > When opening a new thread via the web interface, we recommend you check
>> > the
>> > "Notify me of replies" box to receive e-mail notifications when there
>> > are
>> > any updates in your thread. When responding to posts via your
>> > newsreader,
>> > please "Reply to Group" so that others may learn and benefit from your
>> > issue.
>> >
>> > Microsoft engineers can only focus on one issue per thread. Although we
>> > provide other information for your reference, we recommend you post
>> > different incidents in different threads to keep the thread clean. In
>> > doing
>> > so, it will ensure your issues are resolved in a timely manner.
>> >
>> > For urgent issues, you may want to contact Microsoft CSS directly.
>> > Please
>> > check http://support.microsoft.com for regional support phone numbers.
>> >
>> > Any input or comments in this thread are highly appreciated.
>> > ======================================================
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >
>> >
>> >
>> > --------------------
>> >>Thread-Topic: Fax pooling performance
>> >>thread-index: AcYa69YK3jj2ybk8RpOll3fQeXkn7A==
>> >>X-WBNR-Posting-Host: 69.141.140.44
>> >>From: "=?Utf-8?B?Uk1hcm1pb24=?=" <RMarmion@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >>Subject: Fax pooling performance
>> >>Date: Mon, 16 Jan 2006 14:26:03 -0800
>> >>Lines: 25
>> >>Message-ID: <E5542D6D-3D5C-48B2-95AC-210E85F92821@xxxxxxxxxxxxx>
>> >>MIME-Version: 1.0
>> >>Content-Type: text/plain;
>> >> charset="Utf-8"
>> >>Content-Transfer-Encoding: 7bit
>> >>X-Newsreader: Microsoft CDO for Windows 2000
>> >>Content-Class: urn:content-classes:message
>> >>Importance: normal
>> >>Priority: normal
>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >>Newsgroups: microsoft.public.windows.server.sbs
>> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:237145
>> >>X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >>
>> >>We have a client who has been using an old (10 years old) BrookTrout
>> >>fax
>> >>board and software to handle pretty heavy outbound fax traffic through
>> > four
>> >>phone lines. He needs it to be updated. We originally spec'd a newer
>> >>version of the BrookTrout board (TR1034), but we'd like to pursue the
>> > option
>> >>of installing SBS 2003 and using it's built in fax pooling capability
>> >>as
>> > it
>> >>seems to be a much better value.
>> >>The question I have is will SBS 2003 handle 60,000 plus pages of fax a
>> > week?
>> >> If so, what would you recommend for the fax hardware. Would you just
>> >>install four hardware compliant individual fax boards, or is there a
>> >>more
>> >>optimal solution?
>> >>If you don't think that SBS 2003 can handle this volume of outbound
>> >>fax,
>> >>please be candid with me before I commit to SBS 2003. I'd really like
>> >>to
>> > go
>> >>with the SBS 2003 option because of all the additional capabilities
>> >>available, but if it won't reliably handle the outbound fax volume, I'm
>> >>afraid that it is a non-starter.
>> >>If you think it is a good option, can you please please pass on
>> >>whatever
>> >>wisdom you have on the topic, and if possible, cite some sources,
>> > statistics
>> >>or other empirical information I can refer to.
>> >>Thanks,
>> >>-Rob
>> >>--
>> >>Robert Marmion
>> >>ITBridges Inc
>> >>609 844 0949
>> >>"Connecting your Business with your Software"
>> >>
>> >
>>
>>
>>
.
- References:
- RE: Fax pooling performance
- From: "Brandy Nee [MSFT]"
- Re: Fax pooling performance
- From: SuperGumby [SBS MVP]
- Re: Fax pooling performance
- From: RMarmion
- RE: Fax pooling performance
- Prev by Date: Re: Different Password for Exchange
- Next by Date: Re: Event ID 6008
- Previous by thread: Re: Fax pooling performance
- Next by thread: RE: Fax pooling performance
- Index(es):
Relevant Pages
|
