If you don't find the answers
to you questions below, please contact our
support helpdesk.
Q. What does FaxCore require for the Operating System?
A.
Currently, FaxCore requires the following on the server:
1. Windows Server 2003 SP1 Standard, or Windows Server 2003 Web Edition
2. Microsoft .NET framework 1.1
3. We do not recommend installing FaxCore on Active Directory or PDC/BDC servers
running Windows 2000/2003 OS. We recommend dedicating a server for FaxCore, but
in low-volume environments, customers can run other applications. These include
other web servers like Apache and site-specific applications.
Q.
What email systems does FaxCore work with?
A. FaxCore will integrate and send messages to any SMTP compliant mail system.
These include but are not limited to:
1. Microsoft Exchange 5.5 and 2000, 2003
2. Lotus Notes
3. Groupwise
FaxCore has an LDAP
compliant connector for use with:
1. Microsoft Exchange
2. Lotus Notes
Q.
How can I store my received
faxes?
A.
FaxCore provides storage
options for received faxes in the following formats:
1. Single page tiff files
2. Multi page tiff files
3. Storage by any of the following
Date
Time
Inbound DID
Inbound DTMF (Extension)
Module
Port
Timestamp
4. Unique storage specs for
each inbound routing address (DID/DTMF)
5. Token based inbound file
spec for inbound pages, i.e.
d:\faxcore\store\$$RA$$\$$DATE:yyyymmdd$$\$$TS$$-$GUID$$.$$PORT$$.$$PAGE$$.tif
These options allow sites to
store inbound faxes in any directory structure. The fax images can be located
on one or multiple disks.
Each inbound routing address
(DID/DTMF) can have a common or unique format.
In addition to inbound image
files, an optional INI or XML file can be dropped in the same directory of the
fax image for the transmission. The INI/XML file will contain all inbound
routing information.
These options will allow
integrators and application developers to synchronize with FaxCore with or
without the native Faxcore SDK. By scanning a directory, systems can pick-up
faxes with all routing information at regular intervals. In this scenario,
ActiveX, .NET, or DLLs will not be required to integrate.
This is a standard feature
in FaxCore. These are native archiving features in the FaxCore Document Server.
Q. Can
FaxCore be integrated with other applications?
A. Leveraging our .NET architecture and superior Software Developer Kit,
IT professionals can easily fax-enable CRM, ERP, Exchange, e-mail, and
office productivity software with just a few lines of code.
Microsoft Exchange
Lotus Notes
SAP
PeopleSoft
Microsoft Office
Siebel Systems
FileNET
Q.
Does FaxCore support automatic inbound routing to users?
The following methods are available
for users to route inbound fax transmissions:
1. DID - Direct Inward Dialing is a service feature that allows inward-directed
calls to a PBX to reach a specific PBX extension without
human intervention.
2. DTMF - Dual-Tone Multi-Frequency (DTMF) requires the caller to enter an
extension number when sending a fax.
3. CSID - Call Subscriber ID (CSID) is based on the Fax ID which can be matched
to a recipient.
4. Line Routing - Assign physical fax lines to specific users or groups.
5. Custom OCR processing - Run cover pages through one or more OCR engines to
help recognize
routable attributes of the fax transmission.
6. User Groups - Group of one or more FaxCore users.
7. Time of day - Time periods when fax transmission routing is activated.
8. Caller ID - Unique number of calling party.
9. Bar Code Date - Unique bar code data
assigned to users.
The Caller ID data that FaxCore captures also allows the product to maintain a
"White List"
and "Black List" of fax numbers. This allows organizations to Black List
the numbers
that Spam Faxes come from.
Q. How does
FaxCore integrate with Microsoft Exchange?
A. FaxCore integrates with Exchange through native LDAP interfaces. This
allows access to users directory information. Software does not have to be installed on the
Exchange server. Secure LDAP queries allow FaxCore to activate users in the Exchange user
database with faxing services.
IT administrators can fax-enable users without modification to mission critical Exchange servers.
FaxCore supports the following Microsoft Exchange configurations:
1. Microsoft Exchange 5.5 running in Windows NT 4.0 domain
2. Microsoft Exchange 2000 running in Windows 2000 Active Directory domain
3. Microsoft Exchange 2003 running in Active Directory domain
Q. Does FaxCore have an
SDK?
A. The
FaxCore SDK is included in the base product. More information can be found at
www.faxcore.com/sdk.
Samples are complied for the
following development environments:
1. Visual Studio .NET
(Native C#)
2. Visual Studio .NET (Native VB)
3. ASP.NET (Native C#)
4. ASP.NET (Native VB)
5. ASP (JavaScript)
6. ASP (VBScript)
Q. Does FaxCore require a
specific Port in IIS?
A. FaxCore uses the IIS
default port of 80. If the default Port is changed, the web port in the
axbootstrap.ini file must also be updated.
Q. What kind of Barcodes can
FaxCore read?
A. Data Matrix 2D barcodes
are currently supported by FaxCore. The 2D barcode allows up to 2300 characters
and have Error Correction built in, making them ideal for fax applications. 1-D
barcodes (the ones used in retail) do not work very well in a faxing environment
as the slightest bit of skew on the page, renders it unreadable.
Q. Can the FaxCore Cover
Page support additional Fonts?
A. Yes, additional fonts are
supported and adding new fonts to be used on the FaxCore Cover Page quite easy.
Simply install the new fonts on both the FaxCore Server and the PC where the
cover page editor is being used.
Q. I have questions about
"How to order and/or configure my telephone line from the telephone company or
PaBX system" when using a Brooktrout fax card. Do you have any information?
A. The
best source of information can be found at Brooktrout’s web site.
http://www.brooktrout.com/support/productinfo.cfm?frmProduct=LANfax&frmCategory=Knowledgebase&frmKnowBaseID=1457&Level=2
Q. Do I need a CSU to go
with my TR1034 digital fax board?
A. The short answer to this
question is, "Unless you’re connected to a PBX, you need a CSU." However, in
many cases a CSU may not be strictly necessary. Consider the following points
when making a decision about a particular installation:
The primary factor driving the need for a CSU is the loop length, or the
distance from the network interface to the source of the T-1 signal, which can
be a PBX, a central office switch, or a repeater. If that distance is more than
about 500 feet, a CSU may be required in order to maintain a clean signal. This
rule is not as straightforward as it sounds, however, because it is often
difficult to determine loop length. You can’t simply measure "as the crow
flies," because the wiring may take a very roundabout path from point A to point
B.
Another factor to consider is that you may have a hard time getting help from
your carrier unless a CSU is in place. If you call to report a problem and
you’re not using a CSU, oftentimes the first thing they’ll tell you is to
install one and see if the problem goes away. If the problem remains after the
CSU is installed, you will at least have a device that can generate some data to
help determine the nature of the problem.
Finally, the CSU provides a degree of isolation between the network and your
interface device. Burnt-out line drivers on network interface cards are not
unheard of, and the causes of this can range from lightning strikes to poor
quality lines. A CSU is usually easier and cheaper to replace than a network
interface card.
So, there are a number of situations where you can get away with not having a
CSU. Like a filtered and surge protected power strip however, a CSU provides
relatively inexpensive insurance against a variety of problems when the quality
of your T-1 trunk is unknown, which is most often the case unless you’re
directly connected to a PBX in the same room.
Q. What is the definition of
SOAP?
Simple Object Access
Protocol (SOAP) is a way for a program running in one kind of operating system
(such as Windows 2000) to communicate with a program in the same or another kind
of an operating system (such as Linux) by using the World Wide Web's Hypertext
Transfer Protocol (HTTP)and its Extensible Markup Language (XML) as the
mechanisms for information exchange. SOAP specifies exactly how to encode an
HTTP header and an XML file so that a program in one computer can call a program
in another computer and pass it information. It also specifies how the called
program can return a response.
