The APIs
The SCC API is presented at its lowest level as a formal protocol over a TCP socket connection. This delivers high performance and real-time interaction with line-of-business services but is inherently fragile.
There are various ways in which the API is re-presented to deliver robust APIs that are either stateless or stateful, to suit integrators needs.
In brief, the various API presentations are:
Sytel.Mdn2 library
The Sytel.Mdn2 library namespace Sytel.Mdn.SDConnection is a class library used by Sytel’s .NET-based services, and is also published for integrator use. This provides a series of classes that perform message cracking and handling of socket-based communication with CallGem.
The 2 main classes used by integrators are:
- SoftdialConnection – this class wraps up a socket connection to CallGem and provides helpers and message handler method invocation. Depending on the connection URI, SoftdialConnection will either use an underlying socket connection or will use HTTP and message queuing.
- SoftdialMessage – This class is a message cracker for SDMP message strings.
RouterNet
RouterNet is a .NET DLL that exposes the various APIs to CallGem and Softdial Campaign Manager™ (CM) as .NET classes with methods (messages sent to CallGem) and events (messages sent by CallGem). RouterNet is generated automatically from protocol metadata, so will always be up-to-date with the protocol as it evolves.
CallGem HTTP Proxy
The CallGem HTTP Proxy is a DLL hosted by CallGem and CM to deliver a HTTP API to SCC in various flavours. Again this is generated from protocol metadata so will be up-to-date with the protocol. For more details, see The HTTP API