Formulation of Core Team for whitelassi

2 views
Skip to first unread message

aayush bhatnagar

unread,
Nov 20, 2008, 10:59:58 AM11/20/08
to us...@whitelassi.dev.java.net, white...@googlegroups.com
Hi..

Ideally this thread should have come after the Stage 3 discussion. But
i am still making it, as it is a little long and descriptive.

Every project requires a core team to back it up. This is the right
time to form such a team and move forward, now as the code base is
also setup. Once we form this task force, we can schedule a team
building exercise to get to know each other more. Then we can review
the entire progress so far including the service descriptions,
designing activities that lie ahead, coding and our future path.

The areas of development for the core team will include the following:

1. Telco SIP and IMS core procedures for application
servers...covering the core PNM procedures and 3GPP specs.

2. DIAMETER offline and online charging implementation for IMS PNM
server as per IMS specs.

3. XCAP over HTTP interface implementation for the IMS Ut
interface..and also from the PNM server to the XDM server.

4. GUI development and integration with XDM server.

These points will make sense more when the stage 3 description is up
on the blog.

In addition to the above points, the core team will also acquire
domain knowledge of the JSR 240 JSLEE standard, which is the
standardized service delivery framework being used for the PNM server
development.

For being part of the core team, just reply to this thread...and we
can set the ball rolling and take it from there :)

Warm Regards
Aayush.

Nitin Gupta

unread,
Nov 20, 2008, 11:14:26 AM11/20/08
to white...@googlegroups.com, us...@whitelassi.dev.java.net
Hi,
                 Its a good idea of making core-team before final stage-3 discussion and so they can start the coding work on it asap.
and also this project involves different modules so there would be need for separate teams, so its always be better to understand responsibility in advance.


Regards:-
Nitin Gupta.
--
Regards:-
Nitin Gupta.

Ron Steinke

unread,
Nov 20, 2008, 11:42:32 AM11/20/08
to white...@googlegroups.com
Aayush,
 
I would be pleased to contribute in whatever way you feel would be best based on our previous discussion of my background and experience. We can email or chat if you want to discuss.
 
Best regards,
Ron

aayush bhatnagar

unread,
Nov 20, 2008, 9:26:48 PM11/20/08
to white...@googlegroups.com
Great Ron, Nitin..

I have put up some code on the SVN already. I have tried to comment it
as much as possible. you guys are already part of the google group..so
you can check it out.

The pre requisites for going along smoothly are that we all should
have JBOSS AS 4.2 binary with mobicents jslee and the eclipse plugin
installed. The plugin download link is at my blog sidebar.

The jboss and mobicents bundled binary download details are here:
http://forums.java.net/jive/thread.jspa?threadID=53634&tstart=0

From what i understand, we have to handle three protocols..SIP,
DIAMETER and XCAP/HTTP, and some rudimentary functions such as CDRs
etc. As far as SIP and DIAMETER are concerned, i will take care of
them...with Nitin..whom i believe also has a background in SIP.

XCAP/HTTP protocol is something that you can have a look at Ron. We
are using a XDM server..which is an open source offering on JSLEE.
This XDM server is an XML metadata repository that stores xml
documents in a systamatic tree structure. The client (IMS mobile
device) can chop and change this data over the IMS Ut interface. The
protocol used for this manipulation is XCAP (RFC 4825) and HTTP is
used for transport.
The PNM server will also act as a client to this
server..as it will need to check the data on a per user basis during
an IMS call. For enabling this, the XDM server exposes a java
interface that we can directly use from our PNM server SBBs. I have
posted some useful links on the googlegroup earlier..that give an
intro to this XDM server. There is also a spec in the files section
named OMA-XDM-TS.

I have shared the xdm.jar file on the googlegroup earlier. For
deploying it, we need the xcap client RA and the http servlet RA. Then
both RA deployable units (DUs) and xdm.jar can be dropped in the /default/deploy directory
of JBOSS. This will be a nice hands on experience :)

The third major chunk is the GUI...which i think is Dominic's area of expertise. This GUI will eventually need to act as an XCAP client to the XDM server, as the user will manipulate his data over this GUI.


While doing all this..i will post the stage 3 desciption ASAP and also keep the coding going. Nitin can help me out there. I will keep you all posted

aayush.

aayush bhatnagar

unread,
Nov 20, 2008, 9:33:34 PM11/20/08
to white...@googlegroups.com
Actually, a new bug fixed XDM server is also released here with Jboss
4.3 and not 4.2...
http://forums.java.net/jive/thread.jspa?threadID=53721&tstart=0
Reply all
Reply to author
Forward
0 new messages