Asynchronous TAPI

This code sample is named ExTAPIAsync. It demonstrates Extended TAPI asynchronous functionality.
| Feature Area |
|---|
| Relevant APIs |
|---|
|
lineClose function |
|
lineGetDevCaps function |
|
lineGetGeneralInfo function |
|
lineGetOperatorStatus function |
|
lineInitializeEx function |
|
lineNegotiateAPIVersion function |
|
lineNegotiateExtVersion function |
|
lineOpen function |
|
lineShutdown function |
|
Telephony API API |
-
Navigate to the solution file (*.sln), and double-click it. By default, the solution file is copied to the following folder:
C:\Program Files\Windows Mobile 6 SDK\Samples\Common\CPP\Win32\CellCore\ExTAPIAsyncMicrosoft Visual Studio 2005 launches and loads the solution.
-
Build the solution (Ctrl+Shift+B).
-
Deploy the solution (F5).
-
Click Start > Run.
-
Type the path-name to SamplePrivDeveloper.pfx certificate, and click OK. By default, this is located in the following folder:
C:\Program Files\Windows Mobile 6 SDK\Tools\Security\SDK Development Certificates
-
Double-click the SamplePrivDeveloper.pfx certificate icon. The Certificate Import Wizard appears.
-
Click Next. The certificate path-name is filled-in.
-
Click Next.
-
Click Next (you do not need a password).
-
Click Next. Accept the default options; automatically select the certificate store based on certificate type.
-
9. Click Finish.
ExTAPIAsync demonstrates how to develop an application that is based on Extended TAPI asynchronous functionality.
ExTAPI is a privileged API. Applications that use it must be signed with a privileged certificate.
If you have not installed the SamplePrivDeveloper certificate, you will need to so that your DLL and CAB projects are signed correctly. See Windows Mobile Powered Device Security Model for further details on how to install the SDK certificates onto the mobile device, and how to use the privileged SDK certificate to sign this application.