Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ECF/SIP VoIP"
(→Summary) |
(→References) |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
== Details == | == Details == | ||
| − | + | There are 3 distinct stages in the project | |
| − | # | + | # Research about the protocol and Studying it |
| − | # | + | # Protocol Implementation |
| − | # | + | # SIP Provider Implementation |
| − | The | + | The research on the protocol is planned to be carried out using the following methods |
| − | # | + | <nowiki>:</nowiki> |
| − | # | + | # Online Material referring - In this forums posts, blogs and other documents such as RFC will be studied. |
| − | # | + | # Study the SIP messages - This task can be easily done using open source network protocol analyzers and packet analyzers as SIP is a text based protocol syntaxes such as HTTP. In this step SIP requests and reply messages will be examined. |
| + | # Studying existing SIP implementations - There are existing Java SIP implementations which are distributed under GNU GPL. | ||
| − | + | As all these are successful methods of studying the protocol, I'm planing to use them as necessary. | |
| − | + | First, i will read the RFC and other online documents which describes about SIP protocol and its specifications. In this process i will be able to get a good idea about the protocol. So the next step will be examining the SIP messages which are been transfered between server and clients. This will be done by writing small simulators which are able to send requests and the reply will be examined using network protocol analyzers and packet analyzers. | |
| − | + | As SIP protocol is quite complex, the protocol implementation will be carried out while studying the protocol. So the implementation will follow rapid development model. | |
| − | + | Based on these observations i will be able to get an idea about protocol implementation. While developing I'm planing to simulate the requests using the simulators i have implemented to validate my implementations. So it will be easy to fix the bugs in my implementation as it is in the first phase. | |
| − | After | + | |
| + | After validating and verifying the implementation, i will start developing the SIP provider for ECF. In this task i'm planning to take existing provider as a model and to proceed in developing the SIP provider. | ||
| + | |||
| + | == Project Scope == | ||
| + | |||
| + | '''Proposed implementations:''' | ||
| + | *SIP protocol implementation in Java | ||
| + | *SIP Provider for ECF | ||
| + | |||
| + | <nowiki>*</nowiki>The implementations will be extended to use TCP tunneling as well. | ||
| + | <br> | ||
| + | <nowiki>*</nowiki>All the implementations will be consist of Appropriate Documentations. | ||
| + | |||
| + | |||
| + | == Deliverables == | ||
| + | |||
| + | *SIP Protocol Implementation under EPL | ||
| + | *SIP Provider for ECF | ||
| + | *Relevant Documentations and User Guides. | ||
| + | |||
| + | |||
| + | == Challenges == | ||
| + | |||
| + | The key challenge is to implement the SIP protocol and the SIP provider to support all its specified features in an any environment such as directly connected,from behind a proxy, from behind a Firewall. Usually Media packets are transported using UDP and Firewalls block them. To avoid this i have to use TCP tunneling. In this case i have to tunnel the UDP media packets with in TCP or HTTP/ HTTPS packets and send them. | ||
| + | |||
| + | ==References== | ||
| + | #<nowiki>Wikipedia [http://en.wikipedia.org/wiki/Session_Initiation_Protocol]</nowiki> | ||
| + | #<nowiki>ECF source and documentation [http://eclipse.org/ecf]</nowiki> | ||
| + | #<nowiki>EPL definitions and FAQ page [http://www.eclipse.org/legal]</nowiki> | ||
| + | #<nowiki>ECF mailing list</nowiki> | ||
| + | #<nowiki>BSD Vs GPL [http://www.matusiak.eu/numerodix/blog/index.php/2007/12/15/gpl-vs-bsd-a-matter-of-sustainability/]</nowiki> | ||
Latest revision as of 14:00, 3 April 2009
Contents
SIP protocol & Provider Implementation for ECF under Eclipse Public License
This page contains the project proposal created by [Harshana Martin] for the GSoC idea taken from [GSoC 2009 Ideas list]. Comments from the viewers are welcome.
Summary
Eclipse Communication Framework is consists of several messaging protocol such as XMPP, MSN, Yahoo & IRC. There are providers plugged in to the Eclipse for these protocols at the moment. But there is no successfully working SIP Provider for ECF yet. So the aim of this project is to integrate a successful SIP provider to ECF. During the project SIP protocol will be implemented under Eclipse public License as most of the existing SIP implementations are under GNU GPL or Commercial License which are incompatible with EPL.
Details
There are 3 distinct stages in the project
- Research about the protocol and Studying it
- Protocol Implementation
- SIP Provider Implementation
The research on the protocol is planned to be carried out using the following methods :
- Online Material referring - In this forums posts, blogs and other documents such as RFC will be studied.
- Study the SIP messages - This task can be easily done using open source network protocol analyzers and packet analyzers as SIP is a text based protocol syntaxes such as HTTP. In this step SIP requests and reply messages will be examined.
- Studying existing SIP implementations - There are existing Java SIP implementations which are distributed under GNU GPL.
As all these are successful methods of studying the protocol, I'm planing to use them as necessary.
First, i will read the RFC and other online documents which describes about SIP protocol and its specifications. In this process i will be able to get a good idea about the protocol. So the next step will be examining the SIP messages which are been transfered between server and clients. This will be done by writing small simulators which are able to send requests and the reply will be examined using network protocol analyzers and packet analyzers.
As SIP protocol is quite complex, the protocol implementation will be carried out while studying the protocol. So the implementation will follow rapid development model.
Based on these observations i will be able to get an idea about protocol implementation. While developing I'm planing to simulate the requests using the simulators i have implemented to validate my implementations. So it will be easy to fix the bugs in my implementation as it is in the first phase.
After validating and verifying the implementation, i will start developing the SIP provider for ECF. In this task i'm planning to take existing provider as a model and to proceed in developing the SIP provider.
Project Scope
Proposed implementations:
- SIP protocol implementation in Java
- SIP Provider for ECF
*The implementations will be extended to use TCP tunneling as well.
*All the implementations will be consist of Appropriate Documentations.
Deliverables
- SIP Protocol Implementation under EPL
- SIP Provider for ECF
- Relevant Documentations and User Guides.
Challenges
The key challenge is to implement the SIP protocol and the SIP provider to support all its specified features in an any environment such as directly connected,from behind a proxy, from behind a Firewall. Usually Media packets are transported using UDP and Firewalls block them. To avoid this i have to use TCP tunneling. In this case i have to tunnel the UDP media packets with in TCP or HTTP/ HTTPS packets and send them.
References
- Wikipedia [http://en.wikipedia.org/wiki/Session_Initiation_Protocol]
- ECF source and documentation [http://eclipse.org/ecf]
- EPL definitions and FAQ page [http://www.eclipse.org/legal]
- ECF mailing list
- BSD Vs GPL [http://www.matusiak.eu/numerodix/blog/index.php/2007/12/15/gpl-vs-bsd-a-matter-of-sustainability/]