Mobicents SIP Presence Service 1.0.0.BETA4 released!
Eduardo Martins
What is new in this release?
-------------------------------------------------------------------------------
This release introduces the Resource List Server, completing the SIP
Presence Service functions. As a matter of fact every SIP Event
interface now includes Resource List subscription handling, which
means that it can be used for Mobicents XDM or Presence Servers. In
this first release the Resource List Server has a few limitations, it
only works with Mobicents XDM Server running in same JAIN SLEE host,
and rls-services document do not support <entry-ref/> or
<resource-list/> elemtents pointing to external HTTP URIs.
Also new on this release is the enhancement of the Presence Server
with OMA Presence Composition Policy.
Of course, this release also includes some bug fixes.
The list of Issues fixed and enhancements can be found at
http://code.google.com/p/mobicents/issues/list?can=1&q=component:SIPPresence-Service%20release:Type-Beta-4
The JAIN SLEE server bundled is Mobicents JAIN SLEE Server 1.2.3.GA,
which in turn relies on JBoss AS 4.2.3.GA.
What is included in this release?
------------------------------------------------------------------------------
+-- Mobicents XDM Server standalone installed in JBoss AS + Mobicents
JAIN SLEE Server (mobicents-sip-presence-xdms-<version>.zip)
+-- Mobicents XDM Server and Mobicents SIP Presence Servers integrated
installed in JBboss AS + Mobicents JAIN SLEE Server, plus two example
presence aware JAIN SLEE applications pre-deployed
(mobicents-sip-presence-integrated-<version>.zip)
+-- Mobicents SIP Presence Service binary package that you can use to
install XDM or Integrated servers in JBoss AS + Mobicents JAIN SLEE
Server (mobicents-sip-presence-<version>.zip)
+-- Mobicents SIP Presence Service source project that you can use to
build and install XDM or Integrated servers in JBoss AS + Mobicents
JAIN SLEE Server (mobicents-sip-presence-<version>-src.zip)
Where to download from?
------------------------------------------------------------------------------
https://sourceforge.net/project/showfiles.php?group_id=102670&package_id=287660&release_id=656979
SVN source code and tag:
-------------------------------------------------------------------------------
http://mobicents.googlecode.com/svn/tags/servers/sip-presence/mobicents-sip-presence-service-1.0.0.BETA4
How to get started:
-------------------------------------------------------------------------------
The servers that are bundled with JBoss AS just need to be started as usual.
For binary or source packages see the README file in the top directory
of the zip file.
Any other directory where additional instructions are needed has its
own README file.
Beta Documentation
-------------------------------------------------------------------------------
http://hudson.jboss.org/hudson/job/MobicentsDocumentation/lastSuccessfulBuild/artifact/html_single/index.html#chapter-Mobicents_SIP_Presence_Service
aayush
Can we add support for P-headers in the PS ? That will ensure it works
smoothly with any IMS core network connected as a SIP-AS.
Some small procedures need to be added to the server for this. If
added, it will ensure that I need not recompile from source after each
PS release :-)
1. Preserving the P-charging-vector header and adding a term-ioi
header parameter in the 200 OK of the PUBLISH message (term-ioi
pointing to the domain i.e. mobicents.org)
2. Addition of a P-charging-vector header with a locally generated
ICID header parameter (valid for 30 days) in each NOTIFY request sent
outside by the PS.
3. Preserving the P-Charging-Function-Addresses header in the 200 OK
response of the PUBLISH request and that of the SUBSCRIBE request.
4. Preserving the P-charging-Vector header in the 200 OK of each
SUBSCRIBE request, while also adding a term-ioi parameter pointing to
the home domain of the PS (mobicents.org etc)
Currently, the P-headers (even if present in the request) are not
preserved in the response, because of this API of JSIP --->
createResponse(int statusCode, Request request) only preserves the
mandatory headers of SIP and the Timestamp header if present. This is
fine from a routing perspective, but any other additional headers are
lost.
So, any additional headers have to be added when the API call returns
at the application. Either JSIP modifies/provides an API that simply
copies all the request headers in the response (including header
extensions)
else the application will need to take care of it itself........>>
Classes involved:
------------------------
1. sendResonse(args) method of SipSubscriptionHandler. (However, in
case of subscription refreshes, this API of the SipSubsriptionHandler
is not used)
2. sendOkResponse ( ) method of SipPublicationControlSbb.
3. notifySipSubscriber( ) and createAndSendNotify ( ) methods of
SipSubscriberNotificationHandler
Congrats for the release.
Please let me know if my request makes sense :-)
aayush
On Jan 29, 7:11 am, Eduardo Martins <emmart...@gmail.com> wrote:
> We are happy to announce Mobicents SIP Presence Service 1.0.0.BETA4!
>
> What is new in this release?
> -------------------------------------------------------------------------------
> This release introduces the Resource List Server, completing the SIP
> Presence Service functions. As a matter of fact every SIP Event
> interface now includes Resource List subscription handling, which
> means that it can be used for Mobicents XDM or Presence Servers. In
> this first release the Resource List Server has a few limitations, it
> only works with Mobicents XDM Server running in same JAIN SLEE host,
> and rls-services document do not support <entry-ref/> or
> <resource-list/> elemtents pointing to external HTTP URIs.
>
> Also new on this release is the enhancement of the Presence Server
> with OMA Presence Composition Policy.
>
> Of course, this release also includes some bug fixes.
>
> The JAIN SLEE server bundled is Mobicents JAIN SLEE Server 1.2.3.GA,
> which in turn relies on JBoss AS 4.2.3.GA.
>
> What is included in this release?
> ------------------------------------------------------------------------------
> +-- Mobicents XDM Server standalone installed in JBoss AS + Mobicents
> JAIN SLEE Server (mobicents-sip-presence-xdms-<version>.zip)
> +-- Mobicents XDM Server and Mobicents SIP Presence Servers integrated
> installed in JBboss AS + Mobicents JAIN SLEE Server, plus two example
> presence aware JAIN SLEE applications pre-deployed
> (mobicents-sip-presence-integrated-<version>.zip)
> +-- Mobicents SIP Presence Service binary package that you can use to
> install XDM or Integrated servers in JBoss AS + Mobicents JAIN SLEE
> Server (mobicents-sip-presence-<version>.zip)
> +-- Mobicents SIP Presence Service source project that you can use to
> build and install XDM or Integrated servers in JBoss AS + Mobicents
> JAIN SLEE Server (mobicents-sip-presence-<version>-src.zip)
>
> Where to download from?
> SVN source code and tag:
> How to get started:
> -------------------------------------------------------------------------------
> The servers that are bundled with JBoss AS just need to be started as usual.
> For binary or source packages see the README file in the top directory
> of the zip file.
> Any other directory where additional instructions are needed has its
> own README file.
>
> Beta Documentation
Eduardo Martins
before than feel free to provide a patch and I will review.
-- Eduardo
aayush
I did that change with an older version of the server..maybe beta3.
Will work on this version and have a deeper look :-)
aayush
On Jan 30, 4:46 pm, Eduardo Martins <emmart...@gmail.com> wrote:
> Sure, can you create an issue? And of course, if you already did that
> before than feel free to provide a patch and I will review.
>
> -- Eduardo
>
> >> SVN source code and tag:
Eric PTAK
Eduardo Martins
this to reach another XDM Server or simply split Mobicents SIP
Presence Service servers in different hosts?
-- Eduardo
Eric PTAK
Thanks Eric, regarding external links in the rls-services document, is
this to reach another XDM Server or simply split Mobicents SIP
Presence Service servers in different hosts?
-- Eduardo
Eduardo Martins
support a resource list pointing to another XDM Server, and this
limitation is due to the XDM client for external XDM Servers
(ExternalXDMClientSbb) not done yet...
As an example, this is fine if the Mobicents Presence and XDM Servers
are running in 192.168.0.1 :
<?xml version="1.0" encoding="UTF-8"?>
<rls-services xmlns="urn:ietf:params:xml:ns:rls-services"
xmlns:rl="urn:ietf:params:xml:ns:resource-lists"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<service uri="sip:mybu...@example.com">
<resource-list>
http://192.168.0.1:8080/resource-lists/user
s/sip:j...@example.com/index/~~/resource-lists/list%5b@nam
e=%22l1%22%5d
</resource-list>
<packages>
<package>presence</package>
</packages>
</service>
</rls-services>
-- Eduardo
On Tue, Feb 3, 2009 at 10:59 AM, Eric PTAK <eric.p...@gmail.com> wrote:
> For me, it's to allow to get only one expanded list.
> What I mean, it's when you have an expanded rls-service with entry nodes,
> you need to update both resource-list and rls-service when you
> add/change/remove a contact.
> Whereas with an external reference, you just need to update the
> resource-list.
> The fact is you can store both files on the same XDMS or on differents ones.
>
> OpenSIPS developpers initially didn't want to implement resource-list tag as
> it can provide a way for hack.
> After some discussions, they decided to implement it with an xcap-root check
> on referenced URIs in order to be sure that both rls-service and
> resource-list files are on the same server.
> OpenXCAP (same RLS dev as OpenSIPS) has already been modded to support
> resource-list tag within rls-service file but I'm still waiting for OpenSIPS
> That's why I'm impatient ;)
>
> Eric.
> 2009/2/3 Eduardo Martins <emma...@gmail.com>
>>
>> Thanks Eric, regarding external links in the rls-services document, is
>> this to reach another XDM Server or simply split Mobicents SIP
>> Presence Service servers in different hosts?
>>
>> -- Eduardo
>>
Eric PTAK
You can use a resource-list element with BETA4, it just doesn't
support a resource list pointing to another XDM Server, and this
limitation is due to the XDM client for external XDM Servers
(ExternalXDMClientSbb) not done yet...
As an example, this is fine if the Mobicents Presence and XDM Servers
are running in 192.168.0.1 :
<?xml version="1.0" encoding="UTF-8"?>
<rls-services xmlns="urn:ietf:params:xml:ns:rls-services"
xmlns:rl="urn:ietf:params:xml:ns:resource-lists"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<service uri="sip:mybu...@example.com">
<resource-list>
http://192.168.0.1:8080/resource-lists/user
s/sip:j...@example.com/index/~~/resource-lists/list%5b@nam
e=%22l1%22%5d
</resource-list>
<packages>
<package>presence</package>
</packages>
</service>
</rls-services>
-- Eduardo
Eric PTAK
<rls-services xmlns="urn:ietf:params:xml:ns:rls-services" xmlns:rl="urn:ietf:params:xml:ns:resource-lists">
<resource-list>http://10.24.238.113:8080/xcap-root/resource-lists/users/sip%3aalice%40domain/index/~~/resource-lists/list%5b@name=%22Default%22%5d</resource-list>
<packages>
<package>presence</package>
</packages>
</service>
</rls-services>
* /resource-lists/users/sip:alice@domain/index :
<list name="Default">
<display-name>All Contacts</display-name>
<entry uri="sip:bob@domain" xmlns="urn:ietf:params:xml:ns:resource-lists">
<display-name>bob</display-name>
</entry>
</list>
</resource-lists>
Via: SIP/2.0/UDP 10.24.238.150:1852;rport;branch=z9hG4bK292
From: <sip:alice@domain>;tag=153
To: <sip:alice@domain;pres-list=Default>
Call-ID: 123685...@10.24.238.150
CSeq: 601 SUBSCRIBE
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, REFER
Contact: <sip:al...@10.24.238.150:1852;transport=udp>
Expires: 600000
Event: presence
Supported: eventlist
Accept: application/pidf+xml, application/rlmi+xml, multipart/related, multipart/signed
Allow-Events: presence, presence.winfo
Content-Length: 0
Via: SIP/2.0/UDP 10.24.238.150:1852;received=10.24.238.150;rport=1852;branch=z9hG4bK292
From: <sip:alice@domain>;tag=153
To: <sip:alice@domain;pres-list=Default>
Call-ID: 123685...@10.24.238.150
CSeq: 601 SUBSCRIBE
Contact: "Mobicents SIP Event Server" <sip:10.24.238.113:5070>
Require: eventlist
Content-Length: 0