The JSR-289 SIP Servlet v1.1 specification is now final!
By user742711 on Aug 25, 2008
In anticipation of a complete product implementation (aka OCCAS 4.0), I thought I'd take a minute to imagine what life would be like with these new features:
Application Composition. The servlet mapping rules have been replaced by an "application router", a single spot for defining application interactions. In turn, each application has a single, 'main', entry point for handling the SIP messages. This sounds promising, because the previous use of servlet mapping rules to define behavior was prone to conflicts and was sensitive to application deployment order.
B2BUA Helper. Nearly all applications I encounter are some variant of a back-to-back user agent. The B2buaHelper class attempts to simplify the process of creating B2BUA applications by handling functionality like session management and the automatic forwarding of unrecognized SIP headers. If I don't want to look like a fool, I'd better start using it.
Annotations. SIP applications now support Java 5 style annotations. I suppose it's a matter of programming preference as to whether they should be used, but since I've found them valuable in the development of Web Services, I have a hunch I'll be using them with SIP Servlet v1.1 as well.
SIP/Java EE Convergence. Finally, you should be able to reference the SIP Factory within an HTTP session by calling getServletContext().getAttribute(SIP_FACTORY). I know this sounds trivial, but it was a pet-peeve of mine to have to write funky servlet initialization logic just to implement a simple "click-to-dial" application.
Session Key Based Targeting Mechanism. This provides the ability to route initial requests to an existing SipApplicationSession instead of automatically creating a new one. Hmm... I've been recently exploring the need for a SCIM-like application for monitoring sessions within an individual call center (as opposed to on the carrier network). I bet this will help me in its implementation.
Ok, I'm sure I left a lot out. What has you excited about the JSR-289 SIP Servlet v1.1 API?