FaxBack Port Server - Manual - Manual (Page 4)

Connection Server
The Connection Server is the component that clients log in to in order to send and receive faxes, and
administrators connect to in order to manage user accounts, inbound DID routing assignments, and send routing
rules. It provides session tracking, authentication, quota and usage tracking functions.
Port Server
The Port Server is the component that facilitates SIP+T.38 “VoIP Fax” connections with media gateways. Client
software interacts with the port server using HTTP or HTTPS connections, using a real‐time protocol that is better
able to handle delays compared to a pure T.38 connection. The more timing sensitive T.38 protocol is only
implemented between the port server and the media gateway. Although clients interact directly with the port
server, the port server does not maintain a list of accounts. Send and receive connections are always initiated first
between the connection server and the port server, resulting in a unique “session id”. The port server will only
interact with clients that can produce this session id.
Https Proxy
The HTTPS Proxy is the component that enables client access to the Connection and Port Servers securely across
the open Internet. The HTTPS Proxy is an ASP.NET 2.0 application hosted on an IIS server.
Implementation Overview
Which Components Are Needed?
The fewest components required are just the Connection Server and the Port Server. This will allow sending and
receiving of faxes over unsecured HTTP through the port server to a T.38 media gateway.
It is not recommended to put the Port Server directly on the Internet. The HTTPS Proxy is used to provide Internet‐
accessible secure communication.
Implementation Patterns
There are three general types of NET SatisFAXtion IP Port Server installations.
Single Server (Consolidated)
Figure 2‐2: Single Server Installation