FaxBack NET SatisFAXtion 8.7 (Including R3) - Manual - Manual (Page 143)

3 – Clients NET SatisFAXtion 8.7 Manual 143
3
Clients
3.1
Client Protocols
3.1.1
CAS
Normally, a CAS client will use UDP broadcast to locate the fax server. For ac-
tual 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
3.1.1.1.1
Multiple NICs
CAS clients and the server will only listen on the first adapter in the binding or-
der. 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.
3.1.1.1.2
Separate Subnet
Because clients find the server via UDP broadcast, they cannot connect to a fax
server on another subnet or another broadcast domain.
3.1.1.1.3
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 de-
pend on IIS or any other external web server.
It is generally not recommended to run another web server on the same ma-
chine as NET SatisFAXtion since port conflicts can likely occur.