Supporting Video Conferencing (Windows CE 5.0)
The Windows CE IP phone implementation provides most, but not all, of the functionality that you might need to build a customized IP phone.
One feature that Windows CE does not include is multi-party, client-managed video conferencing.
In this context, video conferencing means the following:
- Setting up video conversations using a SIP stack
- Sending and receiving video data using RTP
- Exposing video in the UI
Windows CE includes the basic building blocks necessary to support video conferencing (like video input, streaming of video over a network, and video playback) but they are not directly supported by the TUI, the VAIL, and the RTC Client API.
You can create your own video conferencing solution by replacing the RTC Client API SIP stack with a SIP stack that supports video (both for signaling and media transport) and by providing a UI that includes video functionality.
Replacing the included SIP stack does not mean that you must give up benefits provided by the TUI and the VAIL. For example, you can use the TUI and the VAIL with a video conferencing SIP stack by replacing the signaling and media transport stacks that the VAIL uses.
Because you still use the VAIL in this scenario, you can continue to take advantage of the UI functionality provided by the TUI and the common VoIP functionality provided by the VAIL.
For more information about using VAIL with a new SIP stack, see Customizing Non-UI IP Phone Functionality and Changing the Media Transport Implementation.
You can also customize the TUI to include video input and playback using the guidelines in the Customizing the Supplied UI and Customizing TUI topics.
See Also
Common IP Phone Customization Tasks | How to Develop an IP Phone | Telephony User Interface (TUI) | VoIP Application Interface Layer (VAIL) | Real-time Communications (RTC) Client API
Send Feedback on this topic to the authors