Access Keys:
Skip to content (Access Key - 0)









SLEE Freephone Service for IN and IMS

Print this page

What is the best way to create a call-control application for IN and IMS?

The goal of this article is to present and discuss the best practices for creating call-control applications that can be deployed in both IN and IMS networks. As an example, it uses the SLEE Freephone Service to demonstrate how to create an application that can use more than one communication protocol, with exactly the same application-logic implementation.

This article includes:

  • a discussion of what multi-protocol means, especially for JSLEE applications
  • recommended strategies for writing multi-protocol applications
  • possible architectures for JSLEE multi-protocol applications
  • a review of the initial architecture of the SLEE Freephone Service, to be used as an example of converting to a multi-protocol application
  • an example of enhancing the SLEE Freephone service with an architecture that makes use of Java inheritance to abstract the application's logic from the communications protocols implementation
  • an example of further enhancing the SLEE Freephone service using independent SBBs.

References

Footnotes
Ref Notes
1 Cosmadopoulos, Y., Kulkarni, M., SIP Servlet API Version 1.1, http://www.jcp.org/en.jsr/detail?id=289, August 2008
2 IETF RFC 3261, SIP: Session Initiation Protocol, http://www.ietf.org/rfc/rfc3261.txt, June 2002
3 3GPP TS 23.218, IP Multimedia (IM) session handling; IM call model; Stage 2, http://www.3gpp.org/ftp/Specs/html-info/23218.htm, December 2008
4 John-Luc Bakker, Telcordia Technologies, Inc., JSR21: JAINTM JCC Specification, http://jcp.org/en/jsr/detail?id=21, June 2002
Adaptavist Theme Builder Powered by Atlassian Confluence