Using the IP Phone Suite with a Custom SIP or Media Stack (Windows Embedded CE 6.0)
1/5/2010
The VoIP Phone Suite along with the RTC Client API provides a full-featured VoIP 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 a SIP stack that is different from the SIP stack provided with Windows Embedded CE, you can replace the VoIP Phone Suite calls to the RTC Client API with calls to the different SIP stack.
Because any interaction with the RTC Client API is contained within the IP Dialer (PhoneApp) component of the VoIP Phone Suite, the other VoIP Phone Suite components work with no changes (or possibly only require changes to support any 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. You could still use the RTC Client API directly to add presence and/or instant messaging functionality to your device.
You can, however, use the RTC SIP stack with a custom media stack, or even use both the RTC media stack and a custom media stack. Again, all the related code is contained with the IP Dialer application, so changes would be localized to that application. There would be other changes, of course, if you made any UI changes or database storage changes in relation to using multiple stacks or a custom stack.
More Information
For more information about how to make these changes, please see Configuration Scenarios for the RTC SIP Stack and Using a Third Party Media Stack with RTC.
For other ideas on customization, please see Customizing the VoIP Phone Suite, Customizing the Supplied UI and Common VoIP Phone Customization Tasks.
See Also
Tasks
Other Resources
Common VoIP Phone Customization Tasks
Real-time Communications (RTC) Client API