1. Name of Presentation Red Hat Presenter RED HAT Developer conference Brno 2009 Mobicents/JBCP Pavel Slegr

2. Agenda ● Introduction of Mobicents ● JAIN SLEE ● Sip Servlets ● Media Server ● Presence ● Diameter

3. What is Mobicents ? ● Mobicents is the first and only Open Source VoIP Platform certified for JSLEE 1.0 and SIP Servlets 1.1 compliance. ● Mobicents brings to telecom applications a robust component model and execution environment. It compliments J2EE to enable convergence of voice, video and data in next generation intelligent applications. ● http://www.mobicents.org/ http://www.mobicents.org/

4. What is a Communications Platform ? ● Enable creation, deployment and management of services and applications that integrate voice, video and data across a range of IP and communications network by multiple devices ● Mobicents Communications Platform drives Convergence by bringing to you the infrastructure to build your next generation applications

5. Mobicents convergence “Any content” + “Any network” + “Any device” = Convergence

7. JAIN SLEE overview

9. Quiz – What will be the Response for the CallBlocking ?

10. Quiz answer ● Response: public static final int FORBIDDEN = 403;

12. JBoss World 2009 | PRESENTER NAME 12 JAIN SLEE Example

16. SIP Servlets overview

20. Media overview

21. JBoss World 2009 | PRESENTER NAME 21 Media Server - Goals ● Deliver competitive, complete, best-of-breed, high quality media gateway. ● Meet the demands of modern telco markets - convergence, landline-mobile, IMS and so on. ● Provide flexibility with multi-protocol support and extensible architecture. ● React quickly to dynamic market requirements.

23. 23 Deployment Scenario Web

24. Quiz – What is RTSP

25. Quiz - answer

26. Mobicents SIP Presence Service Responsible for handling the management of user (a.k.a. resources) XML documents stored on the network side, such as authorization rules, buddy and group lists (a.k.a. resource lists), etc. Accepts, stores and distributes Presence Information Handles subscriptions to resource lists, through back- end subscriptions to all the resources in the list

27. Current Features: XDM Server Full RFC 4825 XCAP Server Implementation, including HTTP Digest User Authentication and Request Authorization Notifications on XCAP Operations through XCAP-Diff SIP Subscription Event Package draft 3 IMS Headers Support XCAP-Caps (RFC 4825), OMA Pres-Rules (OMA PS 1.1), IETF Pres- Rules (RFC 5025), RLS-Services (RFC 4826), Resource-Lists (RFC 4826) XCAP Application Usages Framework for easy plugging of additional XCAP Application Usages  small code effort (plenty abstract components available to extend), dynamic (un)deploy Documents stored in JBoss AS default datasource Internal XDM Client SBB for applications to interact with the XDM Server in same JAIN SLEE container

28. Current Features: Presence Server Core functionality defined by RFC 3625 (SIP Event Subscription/Notification), 3903 (SIP Event Publication) and 3856 (Presence Event Package) PIDF and RPID content accepted on Publication interface, easy to extend  just add new JAXB pojo packages OMA Presence Composition Policy IETF and OMA Pres-Rules to authorize and transform content subscribed IMS Headers Support Internal Presence Client SBB for applications to interact with the Presence Server in same JAIN SLEE container

29. Current Features: Resource List Server Core functionality defined by RFC 5367 OMA Service URI Template support Advanced management of flat lists of resources, subscribing not only the base RLS-Services document, but also all referenced Resource-Lists documents Currently coupled with Presence Server, thus either PS or PS+RLS is supported Internal Presence Client SBB also supports subscriptions to resource lists

30. Features: Extras XCAP Client API JAIN SLEE XCAP Client Resource Adaptor Easy to extend abstract SIP Event Framework with publication and subscription interfaces for single resources or resource lists, supporting IMS Headers and exposing JMX configuration interfaces  XDMS and PS SIP interfaces are built on top of it Internal SIP Event Framework Publication and Subscription Client SBB for applications to interact with SIP Event framework n same JAIN SLEE container  PS Internal Client SBB implemented on top of it

31. Features needed towards 1.0 GA SIP Event Notification Filtering (RFC 4660 & 4661)  the ability for a subscriber to define filters on the notifications it will receive per subscription Partial Notification (RFC 5263)  the SIP Event Framework only notifies the content which changed, not full state (depending on capabilities of the subscriber) Partial Publication (RFC 5264)  the SIP Event Framework accepts publication of content which changed, not just full state UA-Profile concrete extension of SIP Subscription interface for the XDM Server, needed to achieve OMA XDMS 1.1 compliancy External version of client SBBs for Presence Server and XDM Server  allows easy coupling/decoupling of servers, allows JAIN SLEE apps to interact with other SIP Presence Services Automated functionality and load testing

32. Diameter overview

33. JBoss World 2009 | PRESENTER NAME 33 JBCP Diameter Architecture

34. Diameter features

35. What was not covered here, but is ongoing and COOL? ● IMS implementation ● SS7 implementation for Media ● Variety implementation of other protocol stacks ● STF (Seam Telco Framework) ● HA, Clustering,LB ● SLEE 2.0 – going towards certification to 1.1 ● Sip Servlets 2.0 – more features (check online)

36. Questions?