Auto Dial for ICS
Other versions of this page are also available for the following:
.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.")
.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.")
8/28/2008
The operation of auto dial on a Windows Embedded CE-based device is similar to the operation of auto dial on a Windows-based desktop computer. If an application generates network packets and the Windows Embedded CE-based device is not connected to a network, auto dial attempts to dial a preset phone book entry without user intervention, unless the device is configured to behave otherwise.
Auto dial for Microsoft® Windows NT® includes functionality that Windows Embedded CE does not implement. The following differences exist between auto dial on Windows NT and on Windows Embedded CE:
- Windows NT allows auto dial to make multiple connections simultaneously. Windows Embedded CE only supports one auto dial connection at a time.
- Windows NT exports APIs to administer auto dial. No auto dial APIs are exported on Windows Embedded CE. OEMs must manually configure the registry to change auto dial properties on Windows Embedded CE. Windows Embedded CE auto dial uses the same phone entry information regardless of the Internet destination of the packets. In general, there are many more options available under Windows NT. For example, the RasGetAutodialAddress function allows the application programmer to create mappings between specific IP addresses and phone book entries in Windows NT.
- Windows NT has a user interface (UI) that allows you to configure the auto dial. Windows Embedded CE relies on Web pages to configure auto dial, and provides a set of Web pages that modify the registry settings as a sample for OEMs.
For information about RAS AutoDial, see AutoDial-Compatible Dialers.