|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
| MILESPExtension | Represents an ESP (External Service Protocol) extension. |
| MILESPFaultResponse | Represents a fault response. |
| MILESPRequest | Represents the low-level ESP (External Service Protocol) request passed by the ESP layer to the processing method. |
| MILESPResponse | Represents the ESP (External Service Protocol) response to an ESP request. |
| MILESPSuccessResponse | Represents a success ESP (External Service Protocol) response. |
| MILInteraction | Represents an MIL interaction. |
| MILInteractionManager | Creates and manages MILInteraction objects submitted to Interaction Server. |
| MILISInteractionParameters | Encapsulates interaction parameters specific to Interaction Server. |
| MILLCAManager | Provides the MIL Local Control Agent-related feature. |
| MILSynchronizer | Synchronizes with an asynchronous operation of the MILInteractionManager interface. |
| MILUCSFindCondition | Defines criteria for finding interactions in UCS. |
| MILUCSInteractionParameters | Encapsulates interaction parameters to save in UCS. |
| MILUCSManager | Provides MIL UCS-related features. |
| Class Summary | |
| MILBootstrapper | Represents a simple MIL server application that connects, and exits when the runmode
changes to MILLCARunMode.EXIT. |
| MILFactory | Entry point to Media Interaction Layer. |
| MILInitializationParameters | Placeholder for the additional MIL parameters required to initialize MIL. |
| MILLCARunMode | |
| MILStopProcessingReason | Placeholder for reason parameters associated with
StopProcessing requests to Interaction Server. |
| MILUCSInteractionStatus | Enumerates the possible statuses for an interaction stored in UCS. |
Exposes the main API classes of the Media Interaction Layer library.
This package contains all the interfaces for: Creating, submitting and stopping interactions in the Interaction Server. Saving and accessing interaction data in the Universal Contact Server. Managing the Local Control Agent-related feature. Use the Genesys ESP protocol to manage extension through the Interaction Server.
To start, initialize the MILFactory component.