Short Message Service Provider Registration

Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

A version of this page is also available for

Windows Embedded CE 6.0 R3

4/8/2010

Short Message Service (SMS) providers enable the SMS client to determine the application that should receive an incoming SMS message. SMS providers also format messages sent through the SMS API into messages that can be transmitted through RIL. Upon receiving a message, the SMS client directs the message to an application, based on the type of message received. All content types must have an associated SMS provider for messages to be routed successfully. When a message is sent, the SMS client sends the message through the provider associated with the type of message sent.

A Short Message Service (SMS) provider must be registered through a registry key that uses the following format:

	Copy Code
[HKEY_LOCAL_MACHINE\Comm\Cellular\SMS\Protocols\< PROVIDER>] "Name"="Microsoft < PROVIDER> SMS Protocol" "DLL"= "< EXPORT_DLL_NAME>" "ExportPrefix"="< PROVIDER>" "Priority"=dword:< PRIORITY> "AppName"="< APPLICATION_NAME>" "Params"="< PARAMETERS>"

Copy Code

[HKEY_LOCAL_MACHINE\Comm\Cellular\SMS\Protocols\<
PROVIDER>]
  "Name"="Microsoft <
PROVIDER> SMS Protocol"
  "DLL"= "<
EXPORT_DLL_NAME>"
  "ExportPrefix"="<
PROVIDER>"
  "Priority"=dword:<
PRIORITY>
  "AppName"="<
APPLICATION_NAME>"
  "Params"="<
PARAMETERS>"

The following table shows the placeholders from the previous registry key example.

Placeholder	Description
PROVIDER	SMS provider name. Used in the naming convention for all exported functions.
EXPORT_DLL_NAME	Name of the DLL that exports the function implementations.
PRIORITY	Numerical priority of the provider. Providers must be ordered so that providers with more specific < PROVIDER>_RecognizeMessage filters have higher numerical < PRIORITY> values. The priority ensures that if a message matches with multiple providers, it is recognized as associated with the most appropriate provider. The least specific provider is set to zero (0) and should not change. This enables a message to be accepted even if it does not match with any of the other providers. The following list shows the standard providers and their associated priority. Raw=0 Status=5 Text=10 Notification=15 WDP=20 WCMP=25 Broadcast=30
APPLICATION_NAME	Optional. Full path to the application associated with a given provider. If no read handles are open for a given message type, then the application specified by this value is launched.
PARAMETERS	Command-line parameters passed to the application specified by <APPLICATION_NAME>. This value is only used when <APPLICATION_NAME> is specified.

See Also

Concepts

Other Resources