FaxBack NET SatisFAXtion 9.0 - Fax Server Manual - Manual (Page 125)

Section 3 ­ Clients
3.1 Client Protocols
3.1.1 CAS
Normally, a CAS client will use UDP broadcast to locate the fax server. For actual communication,
clients will use a random UDP port. This typically makes CAS clients only work on the same
subnet/broadcast domain as the fax server.
CAS clients include the Administration program.
3.1.1.1 Network Challenges for CAS Clients
Multiple NICs
CAS clients and the server will only listen on the first adapter in the binding order. If
CAS clients are having difficulty connecting, make sure both the client and the server
have the proper NIC as first in the binding order.
Separate Subnet
Because clients find the server via UDP broadcast, they cannot connect to a fax server on
another subnet or another broadcast domain.
Force HTTP Connections
It is possible to force HTTP instead of the proprietary UDP protocol by setting these
registry keys in HKCU\Software\FaxBack.
XmlHttpServerUrl [string]: The URL to use for CAS clients. Usually
http://faxserver/casxml.api .
XmlHttpOverride [boolean]: Client setting. Forces CAS clients to use HTTP instead of UDP.
3.1.2 HTTP
The FaxOut Client Suite, Connector for Microsoft Fax, and FAXability all use HTTP to communicate
with the fax server. Fax Machine Integration Server also uses HTTP. NET SatisFAXtion’s HTTP
server is a module loaded by the fax server and runs whenever the fax server service is running,
and does not depend on IIS or any other external web server.
It is generally not recommended to run another web server on the same machine as NET
SatisFAXtion since port conflicts can likely occur.
3.1.2.1 Requirements
DNS Resolution of Server Name
The client installer MSIs are pre­populated with the fax server’s name and port. The URL will be
in the form of http://:/HttpService. api (FMIS uses /CASDrive.api rather
than /HttpService.api). Note that the name used is not the fully qualified name, it is the short
machine name. The fax server’s machine name must resolve on all computers that will use the
client software. If this is not possible, the MSIs can be changed to have a fully qualified domain
name; see 3.1.2.2 Using HTTP Clients over the Internet below.
Port
The HTTP module uses a non­standard HTTP port 84/tcp. If that port was in use at the time the
server was installed, the installer prompted for an alternate port. To identify the port the NET
SatisFAXtion HTTP service uses, open the Program Files\NET
SatisFAXtion\NETSatisFAXtion.log.xml file, and locate the HttpServer.dll output.
HttpServer.dll
IP/Port: 10.0.1.110/84
Server Url: http://netsatappliance:84/HttpService.api
CAS Url: http://netsatappliance:84/casxml.api
Proprietary FaxBack, Inc. 2014 125