Migrating a VoIP Phone (Windows Embedded CE 6.0)
1/5/2010
The Voice over IP (VoIP) phone support in Windows Embedded CE 6.0 has changed from the VoIP phone support in Windows CE 5.0.
The VoIP Phone Suite, while based originally on the Telephony User Interface (TUI) in Windows CE 5.0 has seen significant design changes that differ greatly from the original TUI. The VoIP Phone Suite is essentially a set of applications, each application (or component) having its own particular functionality. Each of these components can be removed from the overall design without impacting the others, save for the loss of their functionality when doing so.
For example, the IP Dialer (PhoneApp.exe) component uses the Real-time Communications (RTC) Client API to provide the core phone experience including registering on the network, placing and receiving voice calls and advanced call control.
In contrast, IP Home Screen (Homescreen.exe) is a "desktop" like application that shows the general user status. It also monitors the health of IP Dialer and invokes the other applications through hotkey presses.
The IP Contacts (PhInfo.exe) implements a User Interface (UI) for viewing Pocket Outlook Object Model (POOM) contacts as well as speed dial entries, call logs and global address list contacts.
Finally, IP Settings (settings.exe) implements a UI for viewing and changing settings, such as ringtones, call preferences and configuration information.
For more information about the VoIP Phone Suite, see IP Phone Suite.
The VoIP Core Components including the Real-time Communications (RTC) functionality used by the VoIP Phone Suite have also seen significant changes. The VoIP Application Interface Layer (VAIL) and PC Integration, like the TUI, are no longer a part of the architecture.
The VAIL Database Store, once part of the VAIL, is now a standalone VoIP Core Component, just like the OWA Exchange Client.
PhCommon is a Dynamic Link Library that provides the VoIP Phone Suite components with a common control and UI functionality.
The State and Notification API (SNAPI) is a core component that is used by the VoIP Phone Suite components to communicate and synchronize their activities through the Registry.
Finally, the Pocket Outlook Object Model is an optional component, which if present, is used by the IP Contacts component for the contacts list and the IP Dialer component for Caller ID lookups.
For more information about the RTC Client API, see**RTC Client API Migration.