VoIP Phone Functionality in Windows Embedded CE (Windows Embedded CE 6.0)

  • Article

1/5/2010

Windows Embedded CE provides two major areas of Voice over IP (VoIP) phone functionality:

  • Software that implements common VoIP phone features, either directly or by using other code. These pieces of functionality do not provide a User Interface (UI).
  • A full-featured UI - the VoIP Phone Suite - that ties the non-UI VoIP phone functionality together and provides a display to users.

The following diagram shows how the pieces of VoIP phone functionality included with Windows Embedded CE relate.

Note

This diagram does not include general Windows Embedded CE functionality, even if the VoIP phone implementation in Windows Embedded CE uses this functionality. For example, you can use the Device Management functionality in Windows Embedded CE to update the run-time image on a VoIP phone, but the Device Management Catalog item is not included in the diagram.

Ee480564.03874d0b-aca5-4460-88f7-90137a689541(en-US,WinEmbedded.60).gif

The VoIP Phone Suite provides UI screens and integration with VoIP phone hardware buttons. For more information about the VoIP Phone Suite, see VoIP Phone Suite Functionality.

The VoIP Phone Suite obtains most of its underlying functionality from these core software modules or components:

  • VAIL Database Store. Provides an API for call and caller information storage. For more information, see Non-UI VoIP Phone Functionality.
  • Real-time Communications (RTC). Includes a SIP stack that provides call control, presence, and instant messaging functionality. Also provides an RTP implementation for media transport. For more information, see Real-time Communications.
  • Exchange Client. Accesses an Exchange server to obtain contact, global address list, and schedule information. **For more information, see Non-UI VoIP Phone Functionality.
  • Pocket Outlook Object Model (POOM). Accesses Outlook Mobile Personal Information Management (PIM) data items and container objects, such as appointment, task and contact information. **For more information, see Non-UI VoIP Phone Functionality.
  • State and Notification API (SNAPI). Enables the VoIP Phone Suite components a way to communicate and synchronize their activities through the Registry. **For more information, see Non-UI VoIP Phone Functionality.
  • PhCommon. Common functionality used by the IP Phone Suite components. For more information, see Non-UI VoIP Phone Functionality.

This modular architecture enables you to customize the VoIP phone you develop.

Without modifying the VoIP Phone Suite, you can replace core components or customize the implementation of a component. By modifying the VoIP Phone Suite, you can provide additional custom functionality. Because the functionality is provided by distinct pieces of software, you can create solutions using code you have written or purchased from other companies.

VoIP Phone Suite functionality uses RTC. The VoIP Phone Suite provides call control by using RTC. RTC in turn uses its SIP and RTP stacks to implement this functionality. These components can be customized and used independently. For example, you can use RTC's SIP stack for call control but have RTC use a different (custom) RTP stack for media transport.

See Also

Concepts

VoIP Phone Architecture