In addition to the interfaces described earlier in this appendix, using DLL calls and MSMQ messages, other mechanisms are available and currently in use by customers to interface with CopiaFacts applications.
Copia will consider adding additional custom message processing to accommodate customer requirements. This approach has been found simpler and quicker than attempting to adapt the existing core processing too operate in new ways. In addition it localizes the CopiaFacts custom code for a specific task, and minimizes the risk of collateral damage to other areas.
Other possible messaging mechanisms include:
Windows Messages
The COPIAFACTS engine (and the Document Converter) accept Windows messages to perform custom functions for specific customers. These may be specific WM_APP messages (for example to cause an operation in a voice call as if a particular DTMF key had been detected) or it could be a WM_COPYDATA message to pass a data buffer for processing. Such a buffer could for example contain the destination for an outbound fax, and the fax filenames to be sent; the arrival of the message on an idle channel would start the processing of an outbound call. The use of Windows messages would normally require the communicating processes to be running on the same machine.
HTTP Client
The built-in application support library has POST and GET functions for sending and receiving data via HTTP and HTTPS. These can be accessed from scripting to notify the results of an outbound or inbound operation, using a post-process or post-receive script. Scripts can be loaded dynamically or pre-loaded at startup. As usual, values of any variables can be included in the passed data.
HTTP Server
Copia has an unreleased HTTPS server which could be adapted to receive incoming messages for a CopiaFacts engine node, for example to initiate an outbound fax.
Documentation Links
Windows Messages (customer-specific messages are not documented here)
Application Support Library (HTTP functions)
