Your SlideShare is downloading. ×
From MSS to TelScale - Mobicents Summit 2011
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

From MSS to TelScale - Mobicents Summit 2011

697
views

Published on

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
697
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
35
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. From MSS To TelScale Mobicents 2011 Summit
  • 2. Agenda
      • MSS Achievements
      • Community
      • Introducing TelScale
      • Roadmaps
  • 3. MSS Achievements Mobicents 2011 Summit
  • 4. Innovation Branches and Initiatives
      • MSS 2.X Added Servlet 3.0 Support through Tomcat 7
      • Started CDI Telco Framework : CDI Integration with SIP Servlets with the end goal to feed it back to SIP Servlet 2.0 spec (See Georges' Presentation)
      • Started Arquillian Integration to create a standard test framework for testing SIP Servlets applications (See Georges' Presentation)
      • Started RestComm : our turnkey private cloud Telco 2.0 SaaS based on Mobicents
      • Experimented and Delivered a Proof of Concept of MSS AutoScaling in the Cloud to be the foundation of our future turnkey Mobicents PaaS.
  • 5. SIP Passivation
      • Passivation : Control memory usage by removing relatively unused sessions from memory while storing them in persistent storage. If a passivated session is requested by a client, it can be "activated" back into memory and removed from the persistent store.
      • MSS supports passivation of SipSessions (and by extension SIP Dialogs) and SipApplicationSessions
      • Passivation occurs at 2 points during the lifecycle of a sip application:
      • When the container requests the creation of a new SIP Session or SIP Application Session. If the number of currently active session exceeds a configurable limit, an attempt is made to passivate sessions to make room in memory.
      • Periodically (by default, every ten seconds) as the JBoss Web background thread runs.
      • A session will be passivated if one of the following holds true:
      • The session hasn't been used in greater than a configurable maximum idle time.
      • The number of active sessions exceeds a configurable maximum and the session hasn't been used in greater than a configurable minimum idle time.
      • Need to be enabled in the application jboss-web.xml or container wide at $JBOSS_HOME/server/<profile>/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
  • 6. MSS Failover Capabilities confidential INVITE Trying Ringing OK ACK BYE OK INVITE Ringing OK ACK BYE OK UA1 UA2 SIP AS 1 2 3 4 5 6 7 8 9 10 11 12
      • Mobicents supports from 9 to 12 in CONFIRMED Dialog Failover
      • Mobicents now supports from 5 to 12 in EARLY Dialog Failover (introduces more overhead as more JAIN SIP state is replicated)
  • 7. RFC 3263 Support
      • An client that wishes to send a request need to perform DNS processing to determine the IP address, port, and transport protocol of a next hop elemen (it can be a proxy or a user agent)
      • DNS canprovide the ability for a given domain to configure a set of servers, along with prioritization and weights, in order to provide a crude level of capacity-based load-balancing and failover
      • DNS lookup is done once per transaction (so for ACK to 2xx as well)
      • Simplified flow :
      • NAPTR query for the domain in the URI to check the preferred transport ; order pref flags service regexp replacement IN NAPTR 50 50 &quot;s&quot; &quot;SIPS+D2T&quot; &quot;&quot; _sips._tcp.example.com. IN NAPTR 90 50 &quot;s&quot; &quot;SIP+D2T&quot; &quot;&quot; _sip._tcp.example.com IN NAPTR 100 50 &quot;s&quot; &quot;SIP+D2U&quot; &quot;&quot; _sip._udp.example.com.
      • SRV lookup on _sip._tcp.example.com
      • ;; Priority Weight Port Target IN SRV 0 1 5060 server1.example.com IN SRV 0 2 5060 server2.example.com
      • A or AAAA record lookup of the domain name to get the IP Address
      • If the hop fails (timeout) the next one is tried.
  • 8. E.164 NUmber Mapping
      • Telephone number mapping is the process of unifying the telephone number system of the public switched telephone network with the Internet addressing and identification name space. Telephone numbers are systematically organized in the E.164 standard, while the Internet uses the Domain Name System for linking domain names to IP Addresses and other resource information.
      • Telephone number mapping systems provide facilities to determine applicable Internet communications servers responsible for servicing a given telephone number by simple lookups in the Domain Name System.
      • ENUM uses special DNS Record types to translate a telephone number into a URI or IP address that can be used in Internet communications.
      • the Registrar provides the Subscriber (or Registrant) with a domain name, the URI that will be used for accessing a DNS server to fetch a NAPTR record, a personal E.164 telephone number. The URI domain name is one-to-one mapped to the subscriber E.164 ENUM number. The NAPTR record corresponding to the subscriber URI contains the subscriber call forwarding/termination preferences.
  • 9. E.164 NUmber Mapping
      • Subscriber A calls +34 98 765 4321 which is translated to 1.2.3.4.5.6.7.8.9.4.3.e164.arpa.
      • A request is sent to the Domain Name System asking it to look up the ENUM domain 1.2.3.4.5.6.7.8.9.4.3.e164.arpa.
      • The query returns :
    • $ORIGIN 1.2.3.4.5.6.7.8.9.4.3.e164.arpa.
    • IN NAPTR 100 10 &quot;u&quot; &quot;E2U+sip&quot; &quot;!^.*$!sip:phoneme@example.net!&quot; .IN NAPTR 102 10 &quot;u&quot; &quot;E2U+mailto&quot; &quot;!^.*$!mailto:myemail@example.com!&quot; .
      • The first result can be used as a URI to contact the callee over SIP. This URI will then go through RFC 3263 lookups to get the IP Address, port and transport to contact the callee.
  • 10. Simple global logging config
      • Provides templates for log4j.xml
        • DEFAULT
        • DEBUG
        • TRACE
        • PRODUCTION
      • Configurable through Management Consoles or JMX
  • 11. SNMP Support
      • Refactored and revamped the old JBoss AS SNMP Adaptor
      • Moved from joesnmp obsolete stack to snmp4j living stack
      • New features :
        • Real compliance with SNMP (was not the case before)
        • Added Support for v3 of the protocol
        • Added Security for v3 and v2c
        • Support for INFORMs in addition to TRAPs
        • Support for Tables
        • Capability for applications to expose their JMX Beans through SNMP and send TRAPs and INFORMs
        • Maven MIB Generator plugin to avoid double editing pain
  • 12. DoS Attack Prevention
      • Improved Transaction Maximum Retention in the stack to avoid transaction leaks
      • Improved Message Handling and Parsing
      • Limit Stack Max Message Size
      • Added JAIN SIP Congestion Control Valve
  • 13. General
      • More than 165 bug fixes scattered over MSS, SIP LB, JAIN SIP, JAIN SIP HA, JAIN SIP Ext, Cluster
      • More Extensions to JSR 289
  • 14. Community Mobicents 2011 Summit
  • 15. MSS Company Contributors
  • 16. MSS Individual Contributors
  • 17. Contributions
      • Georges Vagenas : Led MSS 2.X (2 ALPHA releases before merging to trunk), Leading CDI Telco Framework and Sip Servlets Testing with Arquillian
      • Thomas Quintana : Leading the RestComm
      • Thibault Leruitte who has greatly contributed to boostrap our Mobicents in the cloud initiative by porting Mobicents Sip Servlets in the cloud
      • Subramanian Thamaraisamy from Cisco : Dos Attacks Prevention
      • Ivan Dubrov : bug fixes
      • Oifa Yulian from Web Ukraine : bug fixes
      • Andrew Miller from Crocodile RCS : bug fixes
      • Horaci Macias from Avaya : bug fixes
      • Naoki Nishihara from OKI : bug fixes
  • 18. Downloads
      • 6200+ downloads on cumulated versions since last Summit (source http://sourceforge.net/projects/mobicents/files/Mobicents%20Sip%20Servlets/stats/timeline?dates=2010-10-07+to+2011-12-02 )
      • 1,5x improvements since last Summit
  • 19. International Events Presence
      • Fosdem 2011 (Belgium) : Global Platform Presentation
      • JUDCon/JBossWorld 2011 (Boston, USA) : Co Presentation with OKI on Mobicents Perf Tuning and Frameworks
      • JBoss In Bossa 2011 (Brazil) : Done by Community RHQ + MSS Integration http://rafaeltuelho.wordpress.com/2011/10/12/jboss-in-bossa-2011-eu-participei/
  • 20. ShortComings
      • Too few community releases : Two 1.X FINAL releases, Two 2.X ALPHA releases
      • Late on schedule : due to too much travel for both me and vlad + increasing support from JBCP
  • 21. Introducing TelScale Mobicents 2011 Summit
  • 22. Mobicents Sip Servlets Stack
  • 23. TelScale Stack
  • 24. TelScale Project
      • http://code.google.com/p/telscale/
      • Container Abstraction layer : can support any JavaEE vendor that makes sense for our community and customers (Tomcat, Jetty, JBoss, Glassfish, ...)
      • HA Abstraction Layer independent of a particular vendor technology (See Container independent failover framework presentation)
      • Focus toward Cloud paradigm and running Mobicents as a Telco 2.0 PaaS
      • Increasing number of contributors, moving to Git will ease the collaborative work on community
  • 25. Cloud Communications
      • Main focus for the 12-18 month roadmap
      • Sponsored by several service providers
    confidential
  • 26. Cloud Notions confidential
  • 27. Cloud Vendor Agnostic confidential
      • Strong demand for private deployments for SaaS and PaaS
      • Moving from Standalone static Vitual Image to Dynamic Puppet/Chef Configuration and Image Management
  • 28. Mobicents Turnkey PaaS confidential
      • Auto-scaling prototyped
      • Rolling upgrades
      • Media Server in the cloud
      • Working on production grade cloud packaging
  • 29. RestComm : SaaS turnkey solution confidential
      • www.restcomm.org
    • ALPHA1 : REST API Based on Twilio Simple APIs and TwiML (Twilio Markup Language)
      • ALPHA2 will offer RCML superset above TwiML adding Fax and MMS
  • 30. Roadmaps Mobicents 2011 Summit
  • 31. MSS 1.X Legacy Branch Roadmap
    • Stable Branch where all Stability and Enterprise Features will be added
      • ICE TURN support
      • RFC 5626 support
      • RFC 5393 support
      • Application Rolling Upgrades
      • TLS and HTTPS support in Converged LB
      • DoS / Fraud Detection-Intrusion
      • NIO TCP/TLS JAIN SIP Connectors
      • Media Libraries (MSML, Netann, MSRP, ...)
      • Bug fixes
  • 32. TelScale 2.X Roadmap
    • Cloud Communications Branch
      • Rebranding to TelScale
    • Container Abstraction Layer
      • HA Independent Layer
      • DataGrid Integration
      • Geo Failover
      • Rolling Upgrades
      • AutoScaling Capabilities
      • Chef/Puppet integration
  • 33. TelScale 3.X Roadmap
      • SIP Servlets 2.0 Non Backward Compatible Work
  • 34. confidential Thank you ! http://telestax.com/