SIP Java Servlets

Extends functionality of SIP client by passing messages to the SIP servlets.

Servlets are similar to the CGI concept, but instead of using a separate process, the messages are passed to a class that runs within a Java Virtual Machine (JVM) inside the server.

Servlets are portable between servers and operating systems, due to the portability of the Java code.

For details see: K. Peterbauer, J. Stadler, et al., “SIP Servlet API Extensions”, February 2001, (an expired internet draft) http://www.cs.columbia.edu/sip/drafts/draft-peterbauer-sip-servlet-ext-00.txt Links to an external site.

SIP Servlets were defined in A. Kristensen and A. Byttner, “The SIP Servlet API”, IETF Draft, September 1999, http://www.cs.columbia.edu/sip/drafts/draft-kristensen-sip-servlet-00.txt Links to an external site.

Unfortunately this draft expired and was not carried forward, but is referenced (and large parts included) in subsequent work. See also [Byttner 2000].
Today SIP Java Servlets are specified in JSR 116 and JSR 289.

Slide Notes

Anders Byttner, “SIP Caller Preferences”, M.Sc. thesis, Department of Teleinformatics, Royal Institute of Technology, March 2000.

Java Specification Requests (JSR 116): SIP Servlet API https://jcp.org/en/jsr/detail?id=116 Links to an external site.

Java Specification Requests (JSR 289): SIP Servlet v1.1 http://www.jcp.org/en/jsr/detail?id=289 Links to an external site.

Transcript

[slide331] You can also write these Java servlets, and there's a nice description of that by Anders Byttner, who did a thesis about this. The bad problem is that, oops, the draft expired, and there was never any subsequent document. So here we have all the JavaScript servlets that are around, rely upon this draft, which never became a standard. So there is no standard, but everyone... Yes, you're not supposed to rely on drafts. But after he finished his thesis, his thesis was done in 2000. No one ever actually finally finished the protocol.