Using CFCP to control remote applications

Summary of operations

CFCP can interact with COPIAFACTS and FFEXTERN instances on a different remote network than where CFCP is running, in the following ways:

COPIAFACTS can be started, stopped, paused and resumed in service mode, provided CFESERVICE is running on the remote machine.

FFEXTERN can be started, stopped, paused and resumed in service mode, provided CFXSERVICE is running on the remote machine.

Operational status and processing statistics for the COPIAFACTS and FFEXTERN service and desktop instances can be viewed.


To use CFCP from a remote location, it must be started from a shortcut or run box with remote on the command-line.  The COPIASERVICES installer will create such a shortcut if you opt to install only the CFCP program on a remote machine.  For example:

CFCP remote

CFCP will then display a dialog requesting connection information:

The Remote address is that of the machine where CFMSG service is running on your CopiaFacts network.  A password is optional: if you require a password you must edit CFMSG.INI in the FAXFACTS folder manually to add a password= item in the [CFMSG] section.

CFCP does not use the information on the $cfmsg command when connecting remotely; instead you must enter override local settings if you need to select a specific IP adapter or use a local port other than one chosen for you by Windows.

Data other than the password entered in this dialog is automatically saved in the local user registry, but the password is only saved (unencrypted) if the checkbox is checked.

If CFCP reports that it cannot connect when started in this way, you need to check the following:

Ensure that the IP and port number have been correctly entered.  The colon and port number can be omitted if it is 54321.

If you use NAT, the specified port number must be forwarded to the machine on which the CFMSG service is running. This will be the machine on which the Copia application data area resides (which has the COPIA share and the FAXFACTS and FAXFACTS\CALLBACK folders in it.

The CFMSG service must be running.  It will only run on the machine which has the folders specified above on it.

Your firewall must allow bi-directional TCP/IP traffic to and from the machine running the CFMSG service.  We recommend that you enable this only for the specific remote end-points(s) at which you wish to run CFCP.

If a password has been specified for CFMSG in CFMSG.INI, it has been entered correctly on starting CFCP from the remote location.

When correctly configured and connected, CFCP can be used to control and monitor your COPIAFACTS and FFEXTERN instances from a remote location, in the same way as if it was running on the same network as these instances.  However a remote instance of CFCP will not offer to control local copies of COPIAFACTS and FFEXTERN, even if they are found on the same machine as the remote CFCP instance.