Asynchronous TAPI

Windows Mobile SupportedWindows Embedded CE Not Supported


This code sample is named ExTAPIAsync. It demonstrates Extended TAPI asynchronous functionality.

Feature Area

Networking - Core


Extended TAPI

Relevant APIs

lineClose function

lineGetDevCaps function

lineGetGeneralInfo function

lineGetOperatorStatus function

lineInitializeEx function

lineNegotiateAPIVersion function

lineNegotiateExtVersion function

lineOpen function

lineShutdown function

Telephony API API

To run the code sample

  1. 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\ExTAPIAsync

    Microsoft Visual Studio 2005 launches and loads the solution.

  2. Build the solution (Ctrl+Shift+B).

  3. Deploy the solution (F5).

To install the certificate from the windows desktop

  1. Click Start > Run.

  2. 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
  3. Double-click the SamplePrivDeveloper.pfx certificate icon. The Certificate Import Wizard appears.

  4. Click Next. The certificate path-name is filled-in.

  5. Click Next.

  6. Click Next (you do not need a password).

  7. Click Next. Accept the default options; automatically select the certificate store based on certificate type.

  8. 9. Click Finish.

Development Environments

SDK: Windows Mobile 6 Professional SDK and Windows Mobile 6 Standard SDK

Development Environment: Visual Studio 2005.

ActiveSync: VersionĀ 4.5.


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.

See Also


Code Samples for Windows Mobile

Other Resources

Extended TAPI