Asynchronous TAPI
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
8/28/2008
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 |
To run the code sample
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).
To install the certificate from the windows desktop
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 CertificatesDouble-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.
Development Environments
SDK: Windows Mobile 6 Professional SDK and Windows Mobile 6 Standard SDK
Development Environment: Visual Studio 2005.
ActiveSync: Version 4.5.
Demonstrates
ExTAPIAsync demonstrates how to develop an application that is based on Extended TAPI asynchronous functionality.
Comments
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
Concepts
Code Samples for Windows Mobile
Other Resources
Extended TAPI
phoneDevSpecific
phoneSetGain
phoneSetHookSwitch
phoneSetRing
phoneSetVolume