Using the TUI and the VAIL with a Custom SIP Stack (Windows CE 5.0)
The TUI and the VAIL, along with the RTC Client API, provide a full-featured IP phone implementation, including a user-tested UI, call log, caller information, speed dial, and advanced features like Exchange integration.
These features can be used with a variety of SIP stacks for signaling. To use an SIP stack that is different from the SIP stack provided with Windows CE, you can replace the VAIL calls to the RTC Client API with calls to the different SIP stack.
Because you leave the API exposed by the VAIL constant, the TUI works with no changes (or only requires changes to support new functionality in your SIP stack).
If you use another SIP stack for signaling, you do not need to give up the additional functionality (like presence and instant messaging) provided with the RTC Client API SIP stack. The TUI already uses the VAIL for signaling and the RTC Client API directly for presence and instant messaging.
For more information about how to make this change, see Customizing TUI.
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