VAIL Configuration Data Store Registry Settings (Windows CE 5.0)
The VAIL uses the registry to persist configuration information. To use the configuration information stored in the registry, VAIL applications use the IVoIPConfigurationDataStore interface.
When an application calls IVoIPConfigurationDataStore::Initialize, the data store reads information in the registry into the data store, where it is available to applications.
When an application calls IVoIPConfigurationDataStore::Uninitialize, the data store writes the current values in the data store to the registry.
Note The IVoIPConfigurationDataStore interface provides a data repository. It does not dictate how the settings it stores are used. Instead, applications that use the configuration data store decide what to do with specific settings. For example, the TUI uses the data persisted in the voicemail_uri registry entry by forwarding calls to this URI in certain cases. These actions are defined by the TUI, not by the configuration data store. For more information about how the TUI uses the configuration data store, see Provisioning the TUI Application.
None of these registry entries exist in the registry in a new run-time image. Instead, they are created when an application persists the current values by calling IVoIPConfigurationDataStore::Uninitialize or when an OEM modifies run-time image registry settings.
The HKEY_CURRENT_USER\Software\Microsoft\VoIPConfig registry key contains VAIL configuration information.
The following table shows the named values.
| Value : type | Description |
|---|---|
| username : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. Name of the phone's user (for example, John Doe). |
| local_area_codes : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. Area codes considered as local (not requiring long-distance calls). For example, 425;206;. |
| voicemail_uri : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. URI for the voicemail server. For example, sip:2000@vmserver. The TUI uses this setting by forwarding calls to this URI if required (for example, if they are not answered or if the application using the VAIL supports a Do not disturb mode). |
| dial_out_prefix : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. Prefix that indicates a call for which external dialing rules should be applied (for example, 9). |
| sip_uri : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. URI of the SIP proxy/registrar server. In contrast to the sip_server registry entry, this entry identifies a user. For example, with the Microsoft Live Communications Server, this field is sip:username@mycompany.com. |
| sip_server : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. Server name of the SIP proxy/registrar server (for example, sipserver.microsoft.com). Unlike the sip_uri registry entry, this setting does not identify a user. |
| sip_transport_type : REG_SZ | The default setting is TLS.
If the value is not present in the registry, no value is assumed. Transport protocol used to communicate with the SIP proxy/registrar server (for example, TCP, UDP, or TLS). |
| sip_auth : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. The type of authentication to use when authenticating with the SIP server. Can be one or more of the following. (If multiple items are specified, they should be delimited by a space and are used in the specified order.)
For more information about this registry entry, see the CONFIG_DATA_PHONE_SIP_AUTHTYPE constant in CONFIG_DATA_. |
| sip_account : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. Username for the account on the SIP server specified using the sip_uri and sip_server registry entries. For example, with the Microsoft Live Communications Server, this field is domain\username. |
| exchange_owaserver : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. URL to access the Exchange Outlook Web Access (OWA) service (for example, https://mail.company.com). |
| exchange_http_proxy : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. HTTP proxy to use when connecting to the Exchange server, if necessary (for example, httpproxy). No proxy is used if this value is not set. |
| sms_server : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. The address of the Systems Management Server machine potentially used by the VAIL application for image update functionality (for example, servername or https://servername/devicemgmt/service.aspx). |
| presence_uri : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. URI used to register with the Live Communications Server (LCS) instance used for presence (for example, sip:username@mycompany.com). |
| presence_server : REG_SZ | There is no default setting.
If the value is not present in the registry, no value is assumed. The address of the Live Communications Server (LCS) machine that contains this user's presence information (for example, server.mycompany.com). |
See Also
Send Feedback on this topic to the authors