Introduction
In this article, I would like to demonstrate why it is easy and comfortable to use Ozeki VoIP SIP SDK. I will demonstrate it through a WPF soft phone sample program. I would like to begin with why it is good for us to use the SDK offered by Ozeki.
In spite of the fact that VoIP and SIP are only sounding abbreviations, the content behind them and the technology requires a deep and exact knowledge. Knowledge about network, sound, sound processing, sound transfer and last but not least about the mysterious world of SIP (Session Initiation Protocol) which is the essential pillar of VoIP technology. The task of SIP protocol is to reconcile the attributes of telephone sets and soft phones, and then it establishes a telephone line between two or more parties who want to communicate. I would like to note casually that SIP needs other protocol implementations to do its task, like SDP (Session Description Protocol), RTP (Real-time Transport Protocol), RTCP (Real-time Transport Protocol), DTMF (Dual-tone multi-frequency). I would not like to disjoint the underlying content of these abbreviations; they can be viewed on the linked addresses. Now to return to the original question why the VoIP SIP SDK offered by Ozeki is good for us has a simple answer. The answer is that it provides all the knowledge and functionality that a VoIP technology communication requires. It provides this communication simply and comfortably. The only thing the developer needs to do is to outlet the events of the call process onto the GUI. This way, the developer can spare the long development time and money that the study of the essential RFC and the small pitfalls that occur during the programming would consume.
After the introduction, let’s see the usage of Ozeki VoIP SIP SDK through a WPF soft phone sample program.
Read more: Codeproject