Mobicents SIP Presence 1.0.0.CR1 released

Hi there, say hello to Mobicents SIP Presence Service 1.0.0.CR1, the first
candidate release for the popular open source SIP Presence service
implementation, now adding RCS to supported standard networks.

What is new?
--------------------------------------------------------------------------

1) Performance & Stability:
+-- Latest SLEE 2.4.1.FINAL;
+-- Optimized SLEE app code, taking full advantage of custom Mobicents
JAIN SLEE 1.1 Extensions;
+-- Several issues fixed;
+-- Network Simulation tools ensures stable memory and performance
behavior on long runs.

2) XDM Server:
+-- XCAP Diff interface completed, fully compatible with RFC 5875, support
for XML Patch Ops included;
+-- IETF Presence Document Content Manipulation (RFC 4827) XCAP App
Usage, for storage of permanent presence state;
+-- OMA XDM 2.0 Presence Content XCAP App Usage, for storage of content
such as status icons;
+-- Optimized XCAP App Usage management, pooling of instances not
needed anymore;
+-- XCAP Diff Super Users support, these will have authorization to subscribe
changes in any document or collection.

3) Presence and Resource Lists Servers:
+-- Pres Rules Transformations, documents are now used not only to authorize
presence subscriptions, but to transform the presence state notified. Polite
blocking supported too;
+-- Service that monitors permanent presence state in the XDMS, such state is
then composed with the state published through SIP;
+-- Extended Accepted Presence Content:
   - OMA Extensions to PIDF and Presence Data Model, OMA PDE 1.0, OMA
PDE 1.1
   - IETF RFCs 3863, 4479, 4480, 4481, 4482, 4199, 5196;
+-- Simpler extension of accepted presence content, just drop xsd files in
related configuration directory and the server will automatically combine all
to achieve the supported documents schema;
+-- JAXB replaced with DOM in publication and subscription interfaces, faster
and better validation of state published, no unneeded XML namespaces in the
notified state;
+-- Multiple event packages now supported in the SIP Event Publication
Control, opens the door for the support of other publishing services in the
integrated server.

What is included?
------------------------------------------------------------------------------
+-- Mobicents XDM Server standalone installed in JBoss AS + Mobicents
JAIN SLEE (mobicents-sip-presence-xdms-1.0.0.CR1.zip)
+-- Mobicents XDM Server and Mobicents SIP Presence Servers integrated
installed in JBboss AS + Mobicents JAIN SLEE, plus two example
presence aware JAIN SLEE applications pre-deployed
(mobicents-sip-presence-integrated-1.0.0.CR1.zip)
+-- Mobicents SIP Presence Service binary package that you can use to
install XDM or Integrated servers in JBoss AS + Mobicents JAIN SLEE 2.4.1.FINAL
(mobicents-sip-presence-1.0.0.CR1.zip)

Download URL:
-------------------------------------------------------------------------------
http://sourceforge.net/projects/mobicents/files/Mobicents%20SIP%20Presence%20Service/1.0.0.CR1

Enjoy.

Update for SAKURA

There you go, first update for Mobicents JAIN SLEE 2.4 a.k.a. SAKURA, click here for the release announcement and the download link.

iMessage: Apple vs Operators Pt.2

Apple yesterday unveiled 10 key features of iOS 5, and iMessage app is one of these, a mobile IM client, which I suspect includes SMS integration, as I don't see Apple having two message systems in iOS.

Including or not integration between IM and SMS, this will be the second Apple stab to traditional telco operators revenue - Facetime was #1 - since iOS will exchange free messages among iOS users, perhaps even OSX users at some point (same route as Facetime), going around SMS. Of course, IM is nothing new, just like video calling was nothing new, but what is relevant here, is that #1 mobile platform (according to yesterday's keynote) is replacing/extending the standard mobile device messaging system, SMS, with IM, and that opens doors for a much clever system, and where the traditional telco operator is not involved, other than be the data pipe if 3G is used instead of Wi-Fi.

The details about iMessage system are almost none, besides what you can view at the keynote video (iMessage is announced at around 1h and 11min), the Apple SVP just slips the detail that it will use the proven and reliable Apple Push Notification System, which serves billions of notifications. If I remember correctly this system uses XMPP. In humble opinion Apple is in the right direction, choosing finest standards for each functionality needed, SIP for call control, XMPP for IM.

In my mind there are a few doubts for what is coming next, the first about iOS 6, will there be an iVoice/iCall, closing the circle and providing a final stab into operators? The second, related with Android, will Google turn GTalk the main messaging system too, with SMS integration, and put SMS as "past" feature for old mobile phones? The third related with all mobile OSes, will there be any interop?