FaxTalk Multiline Server: Complete Setup & Configuration Guide

How to Optimize Performance on FaxTalk Multiline Server

1) Hardware & OS

• CPU: Use a modern multi‑core CPU; prefer at least 4 cores for medium workloads.
• RAM: 8–16 GB minimum; increase if you store many faxes/PDFs on the server.
• Disk: Use SSD for the FaxTalk data folder and spool directories. Ensure ~20% free space.
• Network: Gigabit LAN for server and clients; reduce latency to T.38 SIP provider if used.
• OS: Run on a supported, up‑to‑date Windows Server/Windows 10‑11 machine; keep Windows updates tested.

2) Fax Lines & Modems

• Right‑size lines: Start with required concurrent lines (FaxTalk supports up to 8). Match modem/T.38 channels to peak concurrency.
• Use T.38 when possible: T.38 (FoIP) is more reliable and faster than analog PSTN modems over WAN.
• Modem selection: Use high‑quality, V.34 capable modems (or SIP/T.38 gateways) and keep firmware current.
• Line configuration: Configure lines as send/receive only where appropriate to avoid contention.

3) FaxTalk Configuration

• Data folder placement: Move the FaxTalk data/spool folder to the SSD/fast disk.
• Per‑line settings: Enable automatic printing/saving selectively; disable unnecessary per‑line tasks.
• Retry & timeouts: Tune retry intervals and connection timeouts to avoid long blocking on bad numbers.
• Broadcast throttling: Limit simultaneous sends during broadcasts to avoid queue buildup and carrier penalties.
• Event actions: Route received faxes to file or email rather than auto‑printing if print spool is slow.

4) Network & SIP/T.38 Best Practices

• QoS: Prioritize T.38/SIP traffic (DSCP) on LAN/WAN to reduce packet loss and jitter.
• SIP ALG: Disable SIP ALG on routers/firewalls.
• Firewall rules: Allow only necessary SIP/T.38 ports and whitelist your provider IPs where possible.
• MTU & fragmentation: Ensure MTU avoids fragmentation for SIP/RTP packets; adjust if using VPNs.

5) Storage, Archival & Retention

• Archive policy: Move older faxes to cheaper storage (network share or backup) and keep the active database small.
• Compression: Save received faxes as compressed PDFs/JPGs when quality permits.
• Backups: Regularly back up FaxTalk data folder and configuration; test restores.

6) Monitoring & Maintenance

• Logs: Monitor FaxTalk logs for repeated errors (modem failures, line disconnects).
• Health checks: Track queue length, average send time, failure rate, and disk usage weekly.
• Updates: Keep FaxTalk and modem/SIP gateway firmware updated; test upgrades in staging.
• Reboot schedule: If running on a general‑purpose Windows host, schedule occasional reboots during off‑hours to clear resource leaks.

7) Troubleshooting Performance Issues

• High queue length: Check line availability, modem status, and carrier errors; reduce broadcast concurrency.
• Slow sends: Verify modem V.34 negotiation, network latency to SIP provider, and CPU/disk saturation.
• Frequent failures: Inspect SIP/T.38 logs, disable SIP ALG, test with another provider or direct PSTN line.

8) Quick checklist (apply in this order)

1. Move data/spool to SSD.
2. Match number of lines/modems to concurrency needs.
3. Prefer T.38 trunks and enable QoS.
4. Tune retry/timeouts and limit broadcast concurrency.
5. Archive old faxes and keep active DB small.
6. Monitor logs and update software/firmware.

If you want, I can generate a one‑page checklist customized to your expected monthly fax volume and current hardware (I’ll assume typical small‑office: 100–500 pages/month).