The system runs on your own server. Fax documents, the database and the logs all stay under your control, with no dependency on an external fax cloud.
Browsers and business systems all reach the fax server, which schedules the ports that talk to the outside world.
Installed on a server you already run, in the same network as your other internal systems, reached from the browser over the LAN.
Suits moderate fax volume where server capacity already existsA machine set aside for fax, with the compute and the board slots to itself, so nothing else competes for resources.
Suits higher volume and larger line countsDeployed into your existing virtualisation platform. Note that the fax board is physical hardware, so the VM must be able to access it via passthrough.
Suits organisations with an established virtualisation platformBecause this depends on physical board passthrough, feasibility has to be confirmed against your specific hypervisor and board model. Talk to us before implementation.
From environment check to handover training, each stage has a defined outcome.
Confirm the server model, OS version, number of PCI-E slots and how many fax lines are involved.
Install the fax board and driver, connect the phone lines, and verify each channel can go on and off hook.
Run the installer, set the service port and data directory, and register the system service.
Configure ports to match the board channel count, then set up routing rules and voice prompts.
Send and receive for real, checking success rate, legibility and whether routing lands correctly.
Deliver the manual and train administrators and end users.
The fax board is physical hardware and occupies a PCI-E slot, so the server must be a physical machine that can take the board (or a virtualised environment that supports passthrough). Sizing follows your line count and volume.
| Server | Physical server or industrial PC with an available PCI-E slot |
|---|---|
| Operating system | Windows Server x64 |
| Fax board | Synway analogue fax board, such as SHT-8B or SHT-16C |
| Lines | Analogue telephone lines (PSTN) or PBX trunks |
| Port count | Determined by the board channel count; multiple boards can be installed |
| Database | Built-in database by default, switchable to SQL Server |
| Client | A current mainstream browser — no client software to install |
The guiding principle is that your data stays local: fax documents, the database and the logs all live on your own server, backed up and managed by you.
Every access requires a login; accounts are created and disabled by an administrator.
Function permissions are assigned per role, defining what each person may do.
Fax data is separated by ownership, so standard users cannot see other people’s faxes.
Fax files are served only after authorisation — a guessed URL will not download them.
Key business actions are recorded, so who did what and when can be traced afterwards.
Login times and sources are recorded, making unusual access visible.
Transmission, line events and conversion are logged separately for fault diagnosis.
The API authenticates by key; keys can be scoped and disabled at any time.
HTTPS can be configured so traffic between browser and server is encrypted.
Tell us about your server and how many fax lines you need, and we will recommend a board and a deployment plan.