Special attention should be paid to the best practices used in the application. In the interests of time and simplicity, not all best practices are implemented here. Moreover, the SIP servlet specification is fairly young and some best practices are still in development. However, detail was paid to the following key practices:
ConferenceManagerclass in the
com.bea.appserver.conferencingpackage. This enables both SIP and HTTP servlets to refer to the same objects, establishing SIP/HTTP convergence.
sip.xmlfile explicitly refuses to route SIP REGISTER requests, therefore acknowledging that the SIP servlet may be deployed alongside an existing registrar. In fact, the registrar and proxy functionality are provided separately. This hints that SIP servlets should be granular, modular, and logically separated to ensure optimal flexibility in service creation and deployment.
The following items discussed in this article can be downloaded:
This article presents a sample application that illustrates converged HTTP/SIP application development with WebLogic SIP Server and WebLogic Workshop, media server interoperability with WebLogic SIP Server, and best practices around building SIP-based applications when considering multiple presentation media and divergent media standards. I hope you enjoy the sample, and I look forward to your comments.
The following use cases are implemented by the application. I also include links to diagrams showing the associated SIP call flows.
Jeff Bean is a Technical Manager working for the BEA Global Alliances Group. He has 9 years of IT experience as a software developer, professional services consultant, and systems engineer.
Sudhrity Mondal is a Senior Principal Architect working for BEA Global Alliances Group. He has 14 years of industry experience and specializes in enterprise integration solutions.
Marcelo Oliveira is a Software Engineer currently working for Cisco Systems in the Emerging Markets Business Unit.