RouterNET Integration
Softdial Contact Center (SCC) core services are accessible via a single protocol that is routable at an application level. This means that through a single connection to any core SCC service it is possible to address other services. For example, if you have a connection to Softdial CallGem, it is possible to use that physical connection to drive a conversation with a Softdial Campaign Manager Server instance.
For a description of how to use the Campaign Manager API in order to drive Softdial Campaign Manager™ Server, and documentation on the XML schemas used within the Campaign Manager API, see RouterNET API.
Method and event names shown are those of the CampaignManagerClass class exposed by RouterNET.dll. The messages that make up the SDMP API for Softdial Campaign Manager™ are documented but there is no tutorial information on how to use the messages.
General principles
Softdial Campaign Manager™ manages a series of property sets that tie data in a database to a Softdial CallGem™ campaign. Each instance of Softdial Campaign Manager™ Server manages campaign data on behalf of one tenant.
Campaigns are indexed by integer ID within a tenant. Translating from a name to an integer ID can be done by getting the set of campaigns through the Status Request [SR]/ Status Broadcast [SB] message pair. This delivers an XML document containing outline statistics for each campaign including data to cross-reference names to IDs.
The API is intended to be context-free and to deal with many client connections, and so can deal with client connection failures.
From V10.6.403 - breaking change - the requirement to lock / unlock access to a campaign before performing updates to the campaign properties and associated Lock Campaign [LC] / Unlock Campaign [UC] API has been removed . Any customers using this will need to reorganise their code.