Customizing TUI (Windows CE 5.0)
This topic outlines the customization options provided by the TUI. For detailed information about these options see Common IP Phone Customization Tasks and Telephony User Interface (TUI).
The TUI is provided in source code form in the %_WINCEROOT%\Public\VoIP\Oak\Phone\TUI directory. You can use or customize it as needed. For example, you can:
- Change the look of the UI slightly — like adding your own logo — but leave most of the code that implements the underlying phone functionality intact.
- Make extensive changes, like changing how the underlying code implements the features provided by the UI or by adding supplementary functionality to the UI.
- Customize the provided UI or write your own. For example, you can add elements to the UI to launch custom applications written using the .NET Compact Framework or other Windows CE programming environments, or you can create a new two-line UI (for use on a small LCD display) that uses the same underlying software components as the UI that runs on a 320x240 screen.
The TUI ties together the VoIP functionality provided in Windows CE: it uses VAIL, RTC, Exchange integration, and other VoIP functionality. Whether you customize the TUI or build your own UI, you only need to use the libraries that provide functionality you need.
For example, you can mimic the TUI by using Exchange integration for contact and free/busy schedule information, RTC directly for presence and instant messaging, and VAIL for signaling and media transport, or you can use any Catalog item by itself or in combination with your own code.
As a general rule, the TUI provides a UI but does not implement the underlying functionality. For example, the VAIL provides call log and caller information storage and retrieval, but no UI. TUI adds to and updates call log and caller information data using the appropriate VAIL methods, and provides a UI to enable users to view this information. Because of this modular design, you can write your own UI without needing to re-implement the common VoIP functionality provided by the VAIL.
The TUI also implements the VAIL IVoIPUI interface, and the VAIL calls back into the TUI to notify it of telephony events like call status changes, using the IVoIPUI::OnCallEvent method, or system events, using the IVoIPUI::OnSystemEvent method. For more information about the code in the TUI implementation, see TUI Application Development.
See Also
Customizing IP Phone Functionality | Supporting Video Conferencing | Using the TUI and the VAIL with a Custom SIP Stack | Customizing the Supplied UI | Using Exchange Integration
Send Feedback on this topic to the authors