The base object for DMCC communication.

Convert one or more dial strings to E164 format.

Convert one or strings which are in E164 format to dial strings.

The default name of the application which invoked the Service Provider.

This destructor will also close the socket to the server (if it has not already been closed).

The protocol version that DMCC is using.

Lets the application know if auto keep alive is enabled.

Returns a reference to the CallInformationLink object

Given a device name (Id), returns a reference to the associated Device.

Get all the Device IDs that are active on the DMCC server.

Get all the Device Ids that are active for a particular session id.

Get a list of all the monitors which are active on this DMCC server.

Get a list of all the monitors which are active on a particular session id.

Creates a new Device object and returns a reference to it.

Returns the session name (id) as a string

Retrieve all the active sessions that are running in a DMCC server.

Returns a reference to the ThirdPartCallControl object

Returns a reference to the XML Processor object

The name of the log4net error logger. The config file is DMCC.config and must be in the same folder as the application that is using the .NET API is in.

Handler for ConvertDialStringToE164Response responses.

Handler for ConvertE164ToDialStringResponse responses.

Handler for GetDeviceIdListEvent events.

Handler for GetDeviceIdListResponse responses.

Handler for GetMonitorListEvent events.

Handler for GetMonitorListResponse responses.

Handler for GetSessionIdListResponse responses.

Handler for Missed Keep Alive events.

Handler for ResetApplicationSession responses.

Handler for Server Connection Down events.

Handler for Server Connection Not Active events.

Event registration for responses to SessionManagementStartMonitor requests.

Event registration for responses to SessionManagementStopMonitor requests.

Handler for StartApplcationSession responses.

Handler for StopApplicaitonSession responses.

Handler for TransferMonitorObjectsEvent events.

Handler for TransferMonitorObjectsResponse responses.

Sends a StartApplicationSession message to the server. If sessionId is not null then the server will try to reconnect a session that has timed out or become inactive.

Send a ResetApplicationSession XML message to the server.

Start the monitor for session management.

Stop a session magagement monitor.

Allows the application to tell the Service Provider to shutdown. The Service Provider will in turn notify ThirdPartyCallControl, CallInformationLink, and all the Devices that have been created to also shut down. The Devices in turn will notify their Phone objects. The Phone Pbjects will in turn notify their Media Objects. Calling this method will also force the socket to the server to be closed. Therefore, once this method returns control to the application the application should not invoke any methods which will result in a message being sent to the server. If the application does do this then exceptions will be thrown back to the application. Note: The API provides a callback (OnObjectDeactivatedEvent) for all publicly exposed objects. This will allow the application the ability to easily be notified when an object has bee shutdown (deactivated).

Sends a StartApplicationSession message to the server.

Sends a StartApplicationSession message to the server.

Tell the API to start automatically sending the ResetApplicationSession messages every InernalInMs milliseconds. 1,000 milliseconds is 1 second. If the API is already sending messages then it will cease doing so on the previous interval.

Sends a Stop ApplicationSession XML message to the server. If Devices have objects that are registered the API will attempt to unregister them BEFORE sending this message. In general, the application should have unregistered all devices (and processed the unregistration response) BEFORE invoking this method.

Stops the ResetApplicationSession messages from automatically being sent to the server.

Transfer all the devices and monitors from one session to another session. The session which the monitors are being trasferred from will be closed by the DMCC server.