The escape mechanism enables an application using the JTAPI system to send a direct request to a CallPath Enterprise Server (and any daemons associated with that Server) and receive a response for that request. Alternatively, the user can directly request an event monitor be set in CallPath Enterprise for a specific event.
Figure 13 illustrates the structure of the object or objects that must be sent in order to use the escape mechanism.
Figure 13. Structure of the object or objects that must be sent to use the escape mechanism
This object is the delivery mechanism for the message. The user does not need to directly interact with this object; it will construct the CallPath Enterprise header around the data object.
The object is one of two types: CSASetEvtMonDataObj or CSARemProcCallDataObj. Other types of CallPath Enterprise requests are not supported.
Use this object if you want to start monitoring on a resource. Parameters are the numeric identifier of the event which is to be monitored--the mode, TADS_START_MONITORING or TADS_STOP_MONITORING, and a byte array containing additional parameters if there are any or null if no additional information is necessary. Events monitored for are received by any Observers on the Provider used to send the request.
Use this object if you want to make a Remote Procedure Call to a to a CallPath Enterprise Server. Parameters are the String identifier for the target daemon, the String name of the function to call, and a byte array containing the data (parameters) required for the specific function. The format of this byte array is an issue between the CallPath Enterprise Server and the application. Because it varies, the PrivateDataRequest can only serve as a delivery vehicle. The application writer must know the proper byte array format.