You must provide an implementation of the dialing provider API for your dialer. A skeleton C++ project is available as a start, at:

For most dialers, it makes architectural sense to deliver two components; a dialer component and a dialing provider.

Typically, the dialer component provides an object model that encapsulates dialer communication. You might already have a component that can be used for this purpose or it might make sense to build a component that encapsulates dialer communication (for example TCP/IP messages, to and from the dialer). The QSAMP Dialer Interface Component encapsulates dialer communication to the UNICOM Intelligence Dialer. For information about the associated object model, see QSAMP Dialer Interface component; this might be useful as an example of a dialer component object model.

The dialing provider component implements the ISampleManagementProvider and the IDialingProvider interfaces. The ISampleManagementProvider interface is also implemented by the SampleManagementProvider components. Generally the dialing provider will pass most of the ISampleManagementProvider work off to the SampleManagementProvider component. The major effort in implementing the dialing provider is in implementing the Get and Return methods of the ISampleManagementProvider interface and all the methods of the IDialingProvider interface. If you want to support both extension and group dialing, you might want to provide a separate dialing provider component for each while using the same dialer component.