Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications
-
Upload
telestax -
Category
Technology
-
view
642 -
download
3
Transcript of Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications
![Page 1: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/1.jpg)
RestComm Cloud Communications
Presented By: Thomas Quintana
RestComm Project Lead
Director of Cloud Engineering @ TeleStax, Inc.
![Page 2: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/2.jpg)
Don't Know What RestComm Is?
● A Web Abstraction Layer● A Communications Platform
![Page 3: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/3.jpg)
Some of the Benefits
● Easy to get started● Scalable● Pluggable Architecture● Service Provider Agnostic● Compatible with Twilio's restful APIs and
TwiML markup language
![Page 4: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/4.jpg)
Some of the Difficulties
● The system has multiple pieces to configure and manage
● May require a B2B UA or SBC to handle NAT traversal
● Production deployments require knowledge of communications network topologies
![Page 5: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/5.jpg)
Architecture
![Page 6: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/6.jpg)
Where are we Today?
● Support for most of Twilio's restful APIs● Full TwiML support except the new additions
<Leave> and <Queue>● Support for faxing and SIP user agents● Very few changes are being accepted for the
1.x releases as we approach a final release and internal APIs are stabilizing.
![Page 7: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/7.jpg)
1.0 Roadmap
● Continue Testing and Stabilizing● Beta2 release first week of November.● Implement the remaining restful APIs● Implement Twilio's new TwiML elements
<Leave> and <Queue>● CR1 release end of December● Final release end of January
![Page 8: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/8.jpg)
Room for Improvement
● Using the project but not reporting on the mailing list
● Building applications in private● Asking questions via direct email● Few 3rd party contributions
![Page 9: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/9.jpg)
We Need Help!
● Open discussions on the mailing list.● 3rd Party Vendor Integration● Documentation● Web Site Enhancements● Testing!!!
![Page 10: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/10.jpg)
Lessons Learned
● RestComm is conceptually a pure message passing system. Therefore, we will be moving to an Actor model in the 2.x development tree.
● RestComm is built up of modules providing the necessary functionality to the RCML interpreter. Therefore, we will be moving to OSGi as the module system for RestComm.
![Page 11: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/11.jpg)
Benefits of moving to an Actor Model
● Scales better than the current approach on a single server● Simplified programming model● No need to worry about synchronization● Actors can be hot swapped with zero down time● Actor supervisors enable actors to be restarted in case of failure
(ex. A connection to the media server fails due to server failure; a different media server is selected to carry on the call and finally the supervisor restarts the connection on the new media server)
![Page 12: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/12.jpg)
Benefits of moving to OSGi
● Manages module dependencies for us● Increase re-use of the individual components
in projects outside of RestComm● Zero downtime updates of all but the
RestComm core
![Page 13: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/13.jpg)
The Future!
● 100% Twilio compatibility● 100% Tropo compatibility● Adopt Akka Actor Model Framework● Adopt Apache Felix embedded OGSi
container to manage RestComm's loadable modules
![Page 14: Mobicents Summit 2012 - Thomas Quintana - RestComm Cloud Communications](https://reader036.fdocuments.us/reader036/viewer/2022073101/55657981d8b42a723f8b45b1/html5/thumbnails/14.jpg)
Questions & Answers
Thank You!
Thomas Quintana
http://www.restcomm.org
@thomasquintana