Unlike a busy signal (Code 023) or a handshake failure (Code 034), Code 700 means the fax was successfully sent . The remote machine received the TIFF/PDF data. The problem occurred after the call ended, when the XMedius server tried to deliver the received fax to its final destination (e.g., an email inbox, a network folder, a printer, or an ECM system like SharePoint or Documentum).
This content is structured for an IT administrator or a system integrator who needs to move beyond a surface-level understanding. 1. The Abstract Definition Error Code 700 in XMedius FAX (formerly Omtool, now part of OpenText) is a Post-Transmission Routing Failure . xmedius fax error code 700
The router thread may wake up 50ms before the FaxReceive thread has fully flushed the TIFF file from memory to disk. The router tries to read a file that is still locked. The result: Code 700. Unlike a busy signal (Code 023) or a
SELECT RouteID, DestType, DestAddress, IsActive FROM tblRouteTable WHERE DestType IN ('EMAIL','FOLDER','PRINTER'); If DestAddress contains a trailing space or a non-ASCII character (e.g., a "smart quote" from copy-paste), the router will fail silently with Code 700. The Race Condition: On high-volume servers (2000+ faxes/day), Code 700 can appear intermittently for one specific sender. This is often a timing issue between the FaxReceive thread and the Router thread. This content is structured for an IT administrator
Increase the RouterRetryDelay registry key from default 0 to 500 (milliseconds) under: HKLM\SOFTWARE\XMediusFAX\CurrentVersion\Routing 6. Resolution Matrix | Scenario | Immediate Fix | Permanent Fix | | :--- | :--- | :--- | | Single user gets 700 for all incoming faxes | Check user's email quota or network home drive space | Set up a default "dead letter" route (Code 702 fallback) | | All users get 700 randomly | Restart Print Spooler service (if using direct print) | Move XMedius DB from SQL Express to full SQL Standard | | 700 only for faxes >10 pages | Reduce scan resolution from Superfine to Fine | Increase MaxAttachmentSize in SMTP connector | | 700 after server reboot | Ensure network drives are mapped with Persistent=Yes | Use UNC paths ( \\server\share ) not mapped drives ( Z:\ ) | 7. Proactive Monitoring Rule Add this to your SIEM (Splunk/ELK): Alert when EventID 700 occurs >3 times within 60 minutes for the same SenderCSID . If you see that, the remote fax machine is sending a valid document, but your routing metadata (likely DTMF or TSI) is mismatched against your rule set. Final Verdict: Code 700 is rarely a fax board or telco issue. It is always a post-processing integration fault . Treat it as a routing or permissions problem, not a fax protocol problem.