TUI Registry Settings (Windows CE 5.0)
The TUI application uses the registry to store both configuration data used in phone operation and to persist most recently used settings.
The TUI uses the VAIL configuration data store for phone provisioning. VAIL provisioning registry settings are described in more detail in VAIL Registry Settings.
The HKEY_LOCAL_MACHINE\Software\Microsoft\TUI registry key contains TUI configuration and saved settings. The following table shows the named values.
| Value : type | Description |
|---|---|
| ActiveDirectory : REG_SZ | If the value is not present in the registry, no value is assumed.
The machine name of the Active Directory server used by the TUI application to retrieve provisioning settings. If the AutoConfigType registry entry is 0 (corresponding to the e_actLdapServer value), the TUI queries the specified Active Directory server and retrieves all values that are set to be automatically synchronized in the bitfield value in the AutoConfigSettings registry setting. The TUI ultimately retrieves the settings by calling the IVoIPConfigurationDataStore::UpdateSettingsFromServer function. If the value is empty, the TUI uses the Active Directory server name returned by DsGetDcName. This function returns the Active Directory server that corresponds to the current user's domain. |
| AutoConfigSettings : REG_DWORD | If the value is not present in the registry, CONFIG_DATA_ALL is assumed. This setting synchronizes all CONFIG_DATA_ values.
This value is a bit field that determines which of the CONFIG_DATA_ settings are automatically synchronized from an XML file or LDAP-compliant server (for example, an Active Directory server). A user can use the Settings screen in the phone UI to override the settings that are synchronized automatically. Any setting that has been manually overridden is not synchronized during future automatic updates. |
| AutoConfigType : REG_DWORD | Default setting is 0 (LDAP server).
If the value is not present in the registry, TUI creates the value with the default setting of 0. The phone can be provisioned in three modes:
|
| AutodialEnabled : REG_DWORD | If the value is not present in the registry, TRUE is assumed. This setting turns on autodial functionality.
If this setting is TRUE, the TUI attempts to dial phone numbers when the complete phone number is entered. For example, with the default dial plans, the TUI dials a seven-digit number that does not start with the a '1', with a '011', or with an area code. If this setting is FALSE, the TUI never automatically dials a call. The phone user must manually connect the call after dialing the phone number using the Dial soft button or the corresponding hard button, if one exists. For more information about dial plans, see Modifying TUI Dial Plans. |
| ContactFilterType : REG_DWORD | Default setting is 0 (first name).
If the value is not present in the registry, TUI creates the value with the default setting of 0. The filtering type used most recently when viewing contact information. There are three possibilities:
|
| DoNotDisturb : REG_DWORD | If the value is not present in the registry, FALSE is assumed, turning off do not disturb mode.
If this value is TRUE, all incoming calls are rejected. If your SIP server is configured appropriately, all rejected calls can be sent to a voicemail server. If this value is FALSE, calls are accepted and processed by the phone. |
| GalFilterType : REG_DWORD | Default setting is 1 (first name).
If the value is not present in the registry, TUI creates the value with the default setting of 1. The filtering type used most recently when viewing global address list information. There are three possibilities:
|
| HandsetVolume : REG_DWORD | Default setting is 5 (medium volume).
If the value is not present in the registry, TUI creates the value with the default setting of 5. The most recent volume setting for the handset speaker and handset microphone. Changes to this setting are applied when the phone uses the handset speaker and microphone. The volume setting ranges from 0 to 10. |
| MicrophoneVolume : REG_DWORD | Default setting is 5 (medium volume).
If the value is not present in the registry, TUI creates the value with the default setting of 5. The most recent input setting for the speakerphone microphone. Changes to this setting are applied when the phone uses the microphone. The volume setting ranges 0 to 10. |
| MRUForwardingNumbers : REG_SZ | If the value is not present in the registry, no value is assumed.
This entry stores the numbers that have most recently been used as call forwarding numbers. Numbers are separated by a semicolon, like this: "sip:12345@microsoft.com;sip:23456@microsoft.com" |
| RingerVolume : REG_DWORD | Default setting is 5 (medium volume).
If the value is not present in the registry, TUI creates the value with the default setting of 5. The most recent volume setting for the phone ringer. Changes to this setting are applied when the phone uses the ringer. The volume setting ranges from 0 to 10. |
| SpeakerVolume : REG_DWORD | Default setting is 5 (medium volume).
If the value is not present in the registry, TUI creates the value with the default setting of 5. The most recent volume setting for the external (non-handset) speaker. Changes to this setting are applied when the phone uses the external speaker. The volume setting ranges from 0 to 10. |
| TiedToPCBOOL : REG_DWORD | If the value is not present in the registry, FALSE is assumed, indicating that the phone is not tied to a PC.
If TRUE, the TUI checks with the PC specified in the TiedToPCName registry entry to determine if the phone should be locked or unlocked when accessing secure screens. For more information about the Catalog item that provides this functionality, see PC Authentication. |
| TiedToPCName : REG_SZ | If the value is not present in the registry, no value is assumed.
If the TiedToPCBool registry entry is TRUE, the PC specified in this entry is queried for lock status when a user accesses secure screens. For more information about the Catalog item that provides this functionality, see PC Authentication. |
| XMLDataFileName : REG_SZ | If the value is not present in the registry, phone.xml is assumed.
If the AutoConfigType is set to XML file, the XML file specified by this registry entry is used by the TUI (through the VAIL provisioning APIs) for provisioning when network provisioning is cancelled or cannot be accomplished because of network or server issues. If this value does not contain a path, the VAIL tries to locate the file in the Windows directory on the device, and then tries the Release directory (for debugger-enabled run-time images). |
See Also
Telephony User Interface (TUI)
Send Feedback on this topic to the authors