|
Replies:
26
-
Last Post:
Feb 5, 2008 8:43 AM
by: deruelle_jean
|
|
|
|
|
|
|
Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 15, 2008 1:41 AM
|
|
|
We are happy to announce Mobicents Sip Servlets v 0.1.
Mobicents Sip Servlets implementation is based on the sip servlets v1.1 in progess specification (JSR 289) and run currently on top of Tomcat 5.x.
The highlights of this release are support for Servlet Loading in Tomcat 5.x container,
Application Routing, Proxying, B2BUA (currently limited to 2 call legs), Http Converged Applications, Sessions and Timers and a first set of examples to get started with.
What is included in this release:
---------------------------------
* Core Mobicents Sip Servlets Server
* Educational examples: Click To Call, Call Blocking - Call Forwarding (both working standalone or composed), Speed Dial - Location Service (both working standalone or composed)
Project site :
-------------------
https://sip-servlets.dev.java.net
Where to download from?
-----------------------
The distribution can be found on java.net. The main binary package is Sip-Servlet-0.1_Apache-Tomcat-5.5.25.zip :
https://sip-servlets.dev.java.net/source/browse/*checkout*/sip-servlets/trunk/sip-servlets-bootstrap/release/Sip-Servlet-0.1_Apache-Tomcat-5.5.25.zip?rev=370
SVN tag:
----------------
release-0.1
Source repositories:
-------------------
* SVN
https://sip-servlets.dev.java.net/source/browse/sip-servlets/
How to get started:
-------------------
You'll find online instructions at https://sip-servlets.dev.java.net/installation.html on how to get the server running.
Once the server is running, you'll find online instructions at https://sip-servlets.dev.java.net/examples/examples.html to try out the examples.
Alternatively, there is a README file in the top directory of the zip file.
SIP-SERVLETS-README.txt
Roadmap
---------------------------------
To check our progress and know what lies ahead for the sip servlets project, please check out
https://sip-servlets.dev.java.net/roadmap.html
Looking forward to your feedback:
---------------------------------
please feel free to post a mail on the dev list at dev@sip-servlets.dev.java.net or post an issue in the bugtracker at https://sip-servlets.dev.java.net/servlets/ProjectIssues
Mobicents Sip Servlets Team
|
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 2:46 AM
in response to: deruelle_jean
|
|
|
hello
Is there any document/discussion about what kind of "interoperability standards" are envisaged between this SIP servlet container and mobicents JAIN SLEE
regards
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 5:24 AM
in response to: hsmi
|
|
|
Good question. There are documents describing interop between web apps and JSLEE using the SleeConnection API. SIP Servlets will integrate with JSLEE in a similar fashion.
A more interesting question is how to unify the programming models, so that developers don't have to learn both SIP Servlets and JSLEE. Ideally we would like VoIP features to be an intuitive extension of EJB3 and Web Beans. Looking forward to your ideas.
Ivelin
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 6:45 AM
in response to: ivelin
|
|
|
The best way to interop IMHO is through SIP. May be it's also possible to enable some kind of in-memory interop through shared factory and listener objects in JNDI or some other context, which would fit more nicely with EJB3 and Web Beans.
JSLEE API is overly descriptive, while EJB3 and WB (and SIP servlets) simply deduce a lot of the metadata from the code itself or default to reasonable values. JSLEE events and interfaces are too generic to allow this and there will always be a lot of glue to do something simple.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 8:59 AM
in response to: vralev
|
|
|
> The best way to interop IMHO is through SIP.
That is one option.
> May be
> it's also possible to enable some kind of in-memory
> interop through shared factory and listener objects
> in JNDI or some other context, which would fit more
> nicely with EJB3 and Web Beans.
This is the more interesting scenario in my mind. Concrete proposals are welcome.
>
> JSLEE API is overly descriptive, while EJB3 and WB
> (and SIP servlets) simply deduce a lot of the
> metadata from the code itself or default to
> reasonable values. JSLEE events and interfaces are
> too generic to allow this and there will always be a
> lot of glue to do something simple.
Then let's either extend SIPS to be more real-world friendly and allow basic concurrency control and multiple protocols or alternatively simplify JSLEE. Constructive criticism is welcome.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 8:14 AM
in response to: deruelle_jean
|
|
|
From my point of view, now that we have the SIP SERVLET container, the SIP-RA becomes deprecated because the SIP messages are managed by the SIP SERVLET programming model. Am I wrong? What do you think about?
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 8:30 AM
in response to: michele83
|
|
|
Not necessarily. How would you write a SIMPLE service that needs SIP, Diameter, XCAP and RTP?
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 8:53 AM
in response to: ivelin
|
|
|
Are you saying that with a SIP-ONLY application I have to use SIP-SERVLET and with a multiprotocol application I have to use SIP-RA?
Why did you write the "simple" word in capital letters? What do I have to do with a complex service?
Message was edited by: michele83
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 9:07 AM
in response to: michele83
|
|
|
> Are you saying that with a SIP-ONLY application I
> have to use SIP-SERVLET and with a multiprotocol
> application I have to use SIP-RA?
Yes. Until SIP Servlets allows multiple protocols to be orchestrated in a standard way.
> Why did you write the "simple" word in capital
> letters? What do I have to do with a complex service?
SIP for Instant Messaging and Presence Leveraging Extensions (simple)
http://www.ietf.org/html.charters/simple-charter.html
|
|
|
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 3:21 PM
in response to: ivelin
|
|
|
> > Are you saying that with a SIP-ONLY application I
> > have to use SIP-SERVLET and with a multiprotocol
> > application I have to use SIP-RA?
>
> Yes. Until SIP Servlets allows multiple protocols to
> be orchestrated in a standard way.
On the first part of the question, I would argue that for a SIP-only application you don't *have* to use SIP Servlet, but you have the option whether you use SIP Servlet or JSLEE. As Ivelin points out in his blog you might use SIP Servlet for prototyping a pure-SIP application but as soon as you need a richer programming model you need to migrate to JSLEE.
For anything multiprotocol yes you have no choice in the first instance but JSLEE.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 1:04 AM
in response to: skar22
|
|
|
Thanks for your reply. So I have another question...
How do SIP-RA and SIP-Servlet work in the same enveironment? I mean, are there 2 different SIP stacks? Let's take a look to the next scenario...
1- I deploy Application1 which is a SIP servlet
2- I deploy Application2 which is a JSLEE service
When a SIP message arrives, what happens? Does it reach both the application? How does an application understand if it has to process the message or not?
Thanks. Michele
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 2:20 AM
in response to: michele83
|
|
|
Indeed those are different sip stacks.
SipRA has its own sip stack listening on its IP address and port and Sip Servlets has its own sip stack listening on a different IP address and port. (Both are using jain-sip behind the scene)
Thus, the message will be processed either by one or the other but not both.
Jean
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 3:42 AM
in response to: deruelle_jean
|
|
|
So there are 2 "entry point": IP-port_1 for Application_1 and IP2-port_2 for application_2.
Could it be a problem? Will a softphone (which wants to use both the applications) have to change its configuration (e.g. the proxy IP address)?
Thanks, bye
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 4:07 AM
in response to: michele83
|
|
|
The way I see it is that you will want to use the features easily done in sip servlets like authentication and web context sharing as a front end and then proxy requests to the JSLEE app to play media or other JSLEE service. For example - configure your SIP client to use a sip servlet as a proxy. This sip servlet can require authentication. If the auth succeeds, you can register it in the servlet context or the session context so that the status of this call can be displayed in a web page. After that you can proxy the request to the JSLEE stack where a voicemail/conference JSLEE app will establish the call. Additionally the interop through SIP may implement something like "SIP tunneling" and when dispatched by the JSLEE app the SIP request can carry instructions about generating events for other protocols. That's a hack, but could be useful in some, if not most cases.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 5:01 AM
in response to: vralev
|
|
|
Indeed, this could also use mecanisms defined in section 15.3.2 of the SIP Servlet spec on Inter-Container application routing as pointed out by hsmi.
Alternatively one can use the SleeConnection to fire events directly into the Slee from a sip servlet to interoperate with the JSLEE appserver
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 5:28 AM
in response to: deruelle_jean
|
|
|
Is there any way to receive a response from JSLEE when you fire an event with SleeConnection?
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 6:59 AM
in response to: vralev
|
|
|
Yes, JSLEE 1.1 allows calls via SleeConnection to receive responses from the SLEE.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 8:28 AM
in response to: deruelle_jean
|
|
|
you mean e.g java.sip.RequestEvent ? or custom application dependent events? or you have something else in mind ?
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 24, 2008 1:32 PM
in response to: hsmi
|
|
|
Thanks for your replies, I've just read them because I was out...
This topic seems to be still opened so we have to investigate the different opportunities...
I'll read the spec chapter that it was mentioned because I don't know it...
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 9:15 AM
in response to: deruelle_jean
|
|
|
So web/JEE/SIP services would be more easily placed in the servlet container but when there are other protocols SMPP , CAP , DIAMETER etc the SLEE becomes very useful.
Its maybe also interesting to interoperate according to principles in section 15.3.2 of the new SIP Servlet spec Inter-Container application routing.. what do you think ?
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 9:28 AM
in response to: hsmi
|
|
|
> Its maybe also interesting to interoperate according
> to principles in section 15.3.2 of the new SIP
> Servlet spec Inter-Container application routing..
> what do you think ?
Yes, interop is an open and very important topic for SIPS. Stay tuned for future revisions and chime in as you have concrete suggestions.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Jan 23, 2008 9:43 AM
in response to: hsmi
|
|
|
> So web/JEE/SIP services would be more easily placed
> in the servlet container but when there are other
> protocols SMPP , CAP , DIAMETER etc the SLEE becomes
> very useful.
>
Indeed, Sip servlets spec focus currently on sip + http/Jee only
> Its maybe also interesting to interoperate according
> to principles in section 15.3.2 of the new SIP
> Servlet spec Inter-Container application routing..
> what do you think ?
you will leverage sip here as a way of achieving interop, but we all agree that tighter integration with other protocols in an extensible way would be more handy
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Feb 1, 2008 1:01 AM
in response to: deruelle_jean
|
|
|
Jean, Ivelin, Ranga,
this is interesting news. Mobicents SIP Servlets. I strongly believe in your capabilities to create a more serious open source SIP application server than those being currently around.
I am also interested in your motivation to implement the SIP Servlet specification - and also in why you started with a Tomcat based implementation instead of already moving down the JEE / JBoss path?
Also, the comment from Ivelin about merging the programming models is interesting - why would you do so?
So, a lot of questions in my mind - but overall ... Congratulations!
Best regards,
Michael.
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Feb 1, 2008 7:52 AM
in response to: maretzke
|
|
|
Hi Michael,
> I am also interested in your motivation to implement
> the SIP Servlet specification -
I believe I answered this question in response to your comment on my blog:
http://ivelinivanov.blogspot.com/2008/01/mobicents-jslee-or-mobicents-sip.html#c3057729096317912364
"we decided that it is important to encompass the largest possible community of developers".
> and also in why you
> started with a Tomcat based implementation instead of
> already moving down the JEE / JBoss path?
1. Tomcat is a JBoss technology. Its been sponsored, supported and lead by JBoss employees for years now.
2. As of this week, Mobicents SIP Servlets deploys in both JBoss AS and Tomcat standalone. The upcoming Mobicents Server 1.2.Beta2 will package both the JSLEE and SIP Servlet engines running in the *same* VM on top of the same microkernel, sharing the same JBoss building blocks. Isn't this sweet! 
>
> Also, the comment from Ivelin about merging the
> programming models is interesting - why would you do
> so?
Because we believe developers like simplicity. They have better things to do than learning 3 different ways to do the same thing.
>
> So, a lot of questions in my mind - but overall ...
> Congratulations!
Thank you.
Cheers,
Ivelin
|
|
|
|
|
|
|
|
|
Re: Mobicents Sip-Servlets 0.1 Released
Posted:
Feb 5, 2008 3:32 AM
in response to: maretzke
|
|
|
Hi Michael
> Jean, Ivelin, Ranga,
>
> this is interesting news. Mobicents SIP Servlets. I
> strongly believe in your capabilities to create a
> more serious open source SIP application server than
> those being currently around.
>
> I am also interested in your motivation to implement
> the SIP Servlet specification - and also in why you
> started with a Tomcat based implementation instead of
> already moving down the JEE / JBoss path?
>
Actually, as Ivelin pointed out we are now able to deploy both on Tomcat 6.x and Jboss 4.2.2.GA (currently available from the svn trunk). I think this is interesting for the community to be able to choose one or the other since many people shy away from J2EE to use more lightweight container with Dependency Injection frameworks like SEAM by example; this way, they'll still be able to use their favorite DI framework with sip servlets on top of Tomcat or fully leverage sip servlet with JEE capabilities on the Jboss container. Moreover, as Jboss is using Tomcat internally the codebase to maintain is pretty much similar so we are able to support a much larger user base in being abke to deploy on top of Tomcat and Jboss.
> Also, the comment from Ivelin about merging the
> programming models is interesting - why would you do
> so?
In addition to Ivelin's answer, I'd like to point out that the sip servlets spec is pretty focused currently on SIP + HTTP/JEE but we see that many vendors offering a sip servlets compliant container offers proprietary extensions to be able to use other protocols such as Diameter hand in hand with sip servlets. One of the benefit of merging the models would be to have a simple devolpement model (ala sip servlets) where multiple protocols (ala jslee) could be used to enhance typical jee applications with telco features easily.
>
> So, a lot of questions in my mind - but overall ...
> Congratulations!
>
Thanks for your support !
Jean
> Best regards,
> Michael.
|
|
|
|
|
java.net RSS
