Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)  |  Nominations
JSRs: Java Specification Requests
JSR 359: SIP Servlet 2.0

Stage Access Start Finish
Final Release Download page 11 Apr, 2015  
Final Approval Ballot View results 24 Mar, 2015 06 Apr, 2015
Proposed Final Draft Download page 30 Dec, 2014  
Public Review Ballot View results 20 May, 2014 02 Jun, 2014
Public Review Download page 16 Apr, 2014 16 May, 2014
Early Draft Review Download page 01 May, 2013 15 Jun, 2013
JSR Review Ballot View results 17 Jul, 2012 30 Jul, 2012
JSR Review   02 Jul, 2012 16 Jul, 2012
Status: Final
JCP version in use: 2.8
Java Specification Participation Agreement version in use: 2.0

SIP Servlet API is the standard platform for implementing SIP based services.

Expert Group Transparency:
  Public Communications
  Issue Tracking


Specification Leads
  Binod PG Oracle
Expert Group
: Eric Cheung
: Daniel Timoney
Cisco Systems
: Subramanian Thamaraisamy
  Ericsson AB
: Kristoffer Gronowski
: Nitzan Nissim
: Brian Pulito
  Open Cloud Limited
: David Ferry
: Tomas Ericson
: Binod PG
  TeleStax, Inc.
: Jean Deruelle
TeleStax, Inc.
: George Vagenas
: Keith Lewis
: Tom Strickland
Tropo, Inc.
: Wei Chen
Twilio Inc.
: Jonas Borjesson

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Oracle

Name of Contact Person: Binod P.G

E-Mail Address:

Telephone Number: +91 80 67284070

Fax Number: +91 80 22231794

Specification Lead: Binod P.G

E-Mail Address:

Telephone Number: +91 80 67284070

Fax Number: +91 80 22231794

Initial Expert Group Membership:


Supporting this JSR:

TeleStax, Inc.

Section 2: Request

2.1 Please describe the proposed Specification:

SIP Servlet 1.1 made significant progress in standardization of SIP programming based on the Java EE platform. The purpose of the SIP Servlet 2.0 specification is to further evolve the SIP Servlet technology to address the new requirements pertaining to converged application development.

The specification would align the SIP Servlets with latest Java EE standards . As part of this effort, the following Java EE 6 enhancements are planned to be extended to SIP Servlets.

- Servlet 3.0 enhancements like asynchronous servlets, new annotations (eg: InitParam) and pluggability.
- JNDI namespaces for portable JNDI lookups: java:global, java:module, and java:app
- Context and Dependency Injection APIs.

Expert group would look at aligning with Java EE 7 features that are being standardized now.

This specification also intend to enhance the SIP and communication functionality in the following areas.

- Interworking of SIP Servlets with other protocols.

A typical SIP Servlet application interact with a number of different protocols (eg: diameter, MSRP). Many times, application listeners and sessions of such protocols interwork with SIP servlets and SIP sessions. The specification would look at standardizing interworking of such protocols with SIP servlets by defining a generic model wherever possible.

- Simplification of SIP Servlet development.

SIP Servlet 1.1 introduced many new concepts for simplifying the development of SIP applications. These include new annotations, dependency injection, helper class for back to back user agent pattern etc. This specification will look at further simplification of the programming model to enable rapid development of communication services.

- Incorporate requirements from other standardization efforts.

A number of groups are working on standardizing technologies relevant to SIP Servlet outside JCP. One example is WebRTC standardization in IETF and W3C. The SIP Servlet expert group will examine any requirements from such efforts for potential standardization.

- Other enhancements and bug fixes.

The expert group will also look at enhancing other features of SIP Servlets. Potential areas for enhancement and bug fixing could include, but not limited to,

- Optimize application composition for intra-container routing of requests.
- Concurrency issues related to SIP Servlets.
- Listener for ProxyBranch expiration.
- Handle stray SIP Messages for better error handling.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

The Java Standard Edition or the Java Enterprise Edition.

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.

This specification has no direct impact on the Java Enterprise Edition or the Java Standard Edition. An implementation of this specification may run on the Java Standard Edition or Java Enterprise Edition run-time.

2.4 Should this JSR be voted on by both Executive Committees?

No. It should be voted on by the Java SE / EE Executive Committee only.

2.5 What need of the Java community will be addressed by the proposed specification?

See 2.1 above.

2.6 Why isn't this need met by existing specifications?

This specification is an update to the existing SIP Servlet specification.

2.7 Please give a short description of the underlying technology or technologies:

See 2.1 above. A detailed description of the SIP Servlet technology can be found in the SIP Servlet 1.1 specification,

2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

javax.servlet.sip package and its sub-packages.

2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?


2.10 Are there any security issues that cannot be addressed by the current security model?


2.11 Are there any internationalization or localization issues?


2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

This is an update to SIP Servlet 1.1 (JSR 289).

2.13 Please describe the anticipated schedule for the development of this specification.

Aug 2012 Expert Group formed
Q4 2012 Early Draft
Q1 2013 Public Review
Q3 2013 Final Release

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.

The primary means of communication will be email and conference calls. Face-to-face meetings will be scheduled if needed.

2.15 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:

- Is the schedule for the JSR publicly available, current, and updated regularly?

The schedule will be available on the project page for the JSR.

- Can the public read and/or write to a wiki for the JSR?

We'll use a public mailing list for comments.

- Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?

We'll track such discussions and respond to them on the public comment mailing list.

- Have you spoken at conferences and events about the JSR recently?

There was a BOF session at JavaOne 2011 covering this JSR.

- Are you using open-source processes for the development of the RI and/or the TCK?


- What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?

The terms will be available on the project page for the JSR.

- Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR?

Yes, it will point to the project page for the JSR.

2.16 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

The RI and TCK will be delivered stand-alone, just like SIP Servlet v1.1.
The RI and TCK will be built upon the SIP Servlet v1.1 RI and TCK.

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).


2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

Specification license
RI license
TCK license

2.19 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.

The Expert Group will conduct business on mailing list which is publicly readable.

2.20 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?

A JIRA issue tracker for sipservlet-spec project will be used for this purpose. The issue tracker URL is

2.21 Please provide the location of the publicly accessible document archive you have created for the Expert Group.

Expert Group's publicly readable mailing list will be archived at

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

SIP Servlet 1.1 specification,

3.2 Explanation of how these items might be used as a starting point for the work.

The SIP Servlet API as defined by JSR-289 will be the starting point for this work. This is an update to the SIP Servlet 1.1.