| Platform SDK: TAPI |
Starting with the Windows 2000 release, telephony service providers that negotiate a version of 3.0 are expected to have a matching media service provider. The precise division of operational responsibilities is implementation dependent. For example, a TSP might use the capabilities of the matching MSP to perform media type determination on an incoming session. However, the TSP must conform to the TSPI, which means getting that determination from the MSP and reporting it to TAPI.
TSPI provides the following functions and messages to allow a virtual connection between a TSP and an MSP.
TSPI_lineCloseMSPInstance
TSPI_lineCreateMSPInstance
TSPI_lineMSPIdentify
TSPI_lineReceiveMSPData