Development |
Development.GSoC-IdeasList HistoryHide minor edits - Show changes to markup February 18, 2018, at 03:00 PM
by
- Changed line 7 from:
This page is outdated! For the GSoC 2018 ideas list page, go here. to:
This page is outdated! For the GSoC 2018 ideas list page, go here. February 18, 2018, at 02:59 PM
by
- Added lines 6-7:
This page is outdated! For the GSoC 2018 ideas list page, go here. February 14, 2014, at 08:24 PM
by
- Changed line 39 from:
SIP to SMPP Gatewayto:
SIP to SMPP gatewayFebruary 14, 2014, at 08:24 PM
by
- Changed lines 76-77 from:
RTPProxy Architecture re-design for multi-core supportto:
RTPProxy architecture re-design for multi-core supportChanged line 98 from:
RTPProxy Failover mechanism for on-going media sessionsto:
RTPProxy failover mechanism for on-going media sessionsFebruary 14, 2014, at 06:58 PM
by
- Changed lines 76-77 from:
RTPProxy Architecture re-design for multi-core supportto:
RTPProxy Architecture re-design for multi-core supportChanged lines 98-99 from:
RTPProxy Failover mechanism for on-going media sessionsto:
RTPProxy Failover mechanism for on-going media sessionsChanged line 120 from:
Real-time collecting/reporting of media-related statisticsto:
Real-time collecting/reporting of media-related statisticsFebruary 14, 2014, at 06:58 PM
by
- Added line 71:
February 14, 2014, at 06:57 PM
by
- Changed lines 75-76 from:
Architecture re-design in order to offer multi-core supportto:
RTPProxy Architecture re-design for multi-core supportChanged lines 93-94 from:
Applying studentsto:
Applying students Changed lines 97-98 from:
Failover mechanism for the on-going media sessionsto:
RTPProxy Failover mechanism for on-going media sessionsChanged lines 115-116 from:
Applying studentsto:
Applying students Changed lines 119-120 from:
Real-time collecting/reporting of media-related statisticsto:
Real-time collecting/reporting of media-related statisticsChanged line 137 from:
Applying studentsto:
Applying students February 14, 2014, at 06:56 PM
by
- Changed line 70 from:
RTPProxy enhancementsto:
RTPProxy enhancements February 14, 2014, at 06:56 PM
by
- Changed lines 7-8 from:
Quick Introductionto:
IntroductionChanged lines 11-13 from:
to:
Important NoticeChanged lines 22-24 from:
to:
Student Proposal GuideFebruary 14, 2014, at 06:51 PM
by
- Changed lines 62-63 from:
Mentor to:
Mentor: February 14, 2014, at 04:28 PM
by
- Changed line 123 from:
Real-time collecting/reporting of statisticsto:
Real-time collecting/reporting of media-related statisticsFebruary 14, 2014, at 04:27 PM
by
- Changed lines 7-8 from:
Quick Introductionto:
Quick IntroductionChanged lines 40-43 from:
Ideas for the 2014 Google Summer of CodeSIP to SMPP Gatewayto:
Ideas for the 2014 Google Summer of CodeSIP to SMPP GatewayChanged lines 56-57 from:
Knowledge Prerequisite to:
Knowledge Prerequisites Changed lines 74-75 from:
RTPProxy enhancementsto:
RTPProxy enhancementsRTPProxy is a media relay server integrated in several Voice over IP (VoIP) platforms. It is mainly used to make communication between clients behind NAT (Network Address Translation) possible, but also provides several features like call recording or playing music announcements. As part of a VoIP platform, it acts as a standalone server in public networks controlled by a SIP server such as OpenSIPS that provides the call establishment logic. RTPProxy handles media streams (audio, video, fax), relaying RTP (Real Time Protocol) packets from one end to the other. Architecture re-design in order to offer multi-core supportAdded lines 83-91:
RTPProxy processes all the RTP traffic in a single thread, thus underutilizes the resources that modern computers provide. This project aims to enhance the RTPProxy media relay with a multi-threaded design that uses the computers resources more efficient while increasing the server's throughput. Expected Results The first challenge of this project is to study the possible techniques of parallelizing a network IO bound application and find the best approach to use in a media relay server. The next step is the implementation of this model in the RTPProxy server. Finally, some performance measurements have to be performed in order to prove the efficiency of the design. Knowledge Prerequisites The project requires strong C skills and knowledge of the Posix Threads API. Some experience with GDB would be a plus. Deleted lines 93-100:
Expected Results:
Added lines 95-139:
Răzvan Crainea (razvanc on IRC) Applying studentsPeter Perfect - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect Failover mechanism for the on-going media sessionsBrief Explanation RTPProxy runs as a daemon that continuously processes users traffic. If it stops, due to unexpected errors like software crashes or hardware failures or even explicitely turn down for maintenance, then the users will no longer be able to hear each other. Therefore, in order to ensure availability a failover mechanism is required. Expected Results The goal of this project is to design and implement a replication mechanism for the RTPProxy server. Namely, each instance of the proxy has to duplicate its internal media sessions information to one or more remote instances. Knowledge Prerequisites The project requires strong C network programming skills.
Applying studentsPeter Perfect - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect Real-time collecting/reporting of statisticsBrief Explanation In order to monitor the status of the entire VoIP platform, we have to monitor each of its subsystems. Since RTPProxy is one of them, we would like to be able to monitor it closely using multiple indices. Although it provides a way to retrieve some statistics, the current method is not very flexible and only provides limited information. Expected Results This project aims to improve the statistics interface of the RTPProxy Media Server by adding a set of new monitoring indices. A few examples are processed sessions, ongoing calls, failed sessions, etc. Knowledge Prerequisites This project requires good skills in C, as well as networking and communication protocols knowledge.
February 14, 2014, at 01:44 PM
by
- Changed lines 44-45 from:
Brief Explanation: to:
Brief Explanation The Short Message Peer-to-Peer (SMPP) in telecommunications is an open, industry standard protocol designed to provide a flexible data communication interface for the transfer of short message data between External Short Messaging Entities (ESME), Routing Entities (RE) and Message Centres. Changed lines 50-51 from:
Expected Results: to:
Expected Results The goal of this project is to create a OpenSIPS module that is able to communicate with a SMPP gateway. In other words, to create a new module that provides SIP to SMPP message translation. Changed lines 56-57 from:
Knowledge Prerequisite: to:
Knowledge Prerequisite The project requires good skills in C, as well as networking and communication protocols knowledge. Changed lines 62-67 from:
Mentor: Applying studentsPeter Perfect - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect to:
Mentor Răzvan Crainea (razvanc on IRC) Added lines 68-73:
Student applications Peter Perfect - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect
Changed line 76 from:
Brief Explanation: to:
Brief Explanation February 14, 2014, at 11:55 AM
by
- Added line 27:
February 13, 2014, at 11:27 PM
by
- Changed lines 59-60 from:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect to:
Peter Perfect - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect Changed line 81 from:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect to:
Peter Perfect - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect February 13, 2014, at 11:26 PM
by
- Changed line 35 from:
to:
Changed lines 59-60 from:
Perfect Peter - http://www.opensips.org/Support/Contact to:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect Changed lines 81-83 from:
Perfect Peter - http://www.opensips.org/Support/Contact \\ to:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect February 13, 2014, at 08:30 PM
by
- Changed lines 9-10 from:
These are our proposals for this year's student projects. This page is globally editable, and you are free to add your own project ideas. They will be actively analyzed by our mentors, and all good ideas with volumes of work which fit the 3-month coding period have great chances of being accepted. to:
These are our proposals for this year's student projects. This page is globally editable (create a wiki account and start hacking), and you are free to add your own project ideas. They will be actively analyzed by our mentors, and all good ideas with volumes of work which fit the 3-month coding period have great chances of being accepted. Changed line 35 from:
to:
Changed lines 59-60 from:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect to:
Perfect Peter - http://www.opensips.org/Support/Contact Changed lines 81-83 from:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect to:
Perfect Peter - http://www.opensips.org/Support/Contact \\ February 13, 2014, at 08:14 PM
by
- Changed lines 81-83 from:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect \\ to:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect February 13, 2014, at 08:14 PM
by
- Changed lines 59-60 from:
Perfect Peter - http://www.opensips.org/Support/Contact to:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect Changed line 81 from:
Perfect Peter - http://www.opensips.org/Support/Contact to:
Perfect Peter - http://www.opensips.org/Development/GSoC-Proposal-Peter-Perfect February 13, 2014, at 08:13 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 08:10 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 08:10 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:50 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:50 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:50 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:08 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:07 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:07 PM
by
- Changed line 35 from:
to:
February 13, 2014, at 07:06 PM
by - February 13, 2014, at 07:05 PM
by
- Changed line 36 from:
to:
February 13, 2014, at 07:04 PM
by
- Changed line 34 from:
to:
February 13, 2014, at 07:03 PM
by
- Changed line 16 from:
to:
Changed lines 32-35 from:
create your own opensips.org/Development/GSoC-Proposal-NAME-SURNAME page starting from this template to:
February 13, 2014, at 06:47 PM
by
- Changed lines 12-14 from:
IMPORTANT to:
IMPORTANT Changed lines 25-26 from:
TODO instruct students to create their own proposal pages to:
STUDENT PROPOSAL GUIDE
create your own opensips.org/Development/GSoC-Proposal-NAME-SURNAME page starting from this template Changed line 82 from:
\\ to:
\\ February 13, 2014, at 06:23 PM
by
- Changed line 17 from:
to:
February 13, 2014, at 06:23 PM
by
- Changed line 17 from:
to:
February 13, 2014, at 06:21 PM
by
- Changed lines 12-13 from:
To get in touch with us, visit the Contact page. to:
IMPORTANT
\\ February 13, 2014, at 12:12 PM
by
- Added lines 56-61:
Applying studentsPerfect Peter - http://www.opensips.org/Support/Contact \\ February 13, 2014, at 12:12 PM
by
- Deleted lines 34-35:
Added line 39:
\\ February 13, 2014, at 12:11 PM
by
- Added lines 34-39:
Applying studentsPerfect Peter - http://www.opensips.org/Support/Contact February 13, 2014, at 12:03 PM
by
- Changed lines 7-10 from:
SIP to SMPP GatewayBrief Explanation: to:
Quick IntroductionThese are our proposals for this year's student projects. This page is globally editable, and you are free to add your own project ideas. They will be actively analyzed by our mentors, and all good ideas with volumes of work which fit the 3-month coding period have great chances of being accepted. Added lines 13-24:
To get in touch with us, visit the Contact page. TODO instruct students to create their own proposal pages Ideas for the 2014 Google Summer of CodeSIP to SMPP GatewayBrief Explanation:
Changed line 36 from:
RTPProxy enhancementsto:
RTPProxy enhancementsFebruary 11, 2014, at 04:45 PM
by
- Changed lines 7-10 from:
SIP to SMPP GatewayRTPProxy enhancementsto:
SIP to SMPP GatewayBrief Explanation:
RTPProxy enhancementsBrief Explanation:
February 11, 2014, at 03:25 PM
by
- Deleted line 8:
Integrating libpurple IM libraryFebruary 11, 2014, at 01:00 PM
by
- Changed line 9 from:
libpurple integrationto:
Integrating libpurple IM libraryFebruary 11, 2014, at 12:59 PM
by
- Changed lines 1-2 from:
Development -> GSoC Ideas Listto:
Development -> Google Summer of Code - Ideas ListDeleted lines 5-6:
Google Summer of Code - Ideas ListFebruary 11, 2014, at 12:58 PM
by
- Changed lines 1-7 from:
Google Summer of Code - Ideas ListSIP to SMPP Gatewaylibpurple integrationRTPProxy enhancementsto:
Development -> GSoC Ideas List(:toc-float Table of Content:) Google Summer of Code - Ideas ListSIP to SMPP Gatewaylibpurple integrationRTPProxy enhancementsFebruary 11, 2014, at 12:57 PM
by
- Added lines 1-7:
Google Summer of Code - Ideas ListSIP to SMPP Gatewaylibpurple integrationRTPProxy enhancements |