Use Session Initiation Protocol to provide multimedia and interactive services
Follow these procedures for creating SIP applications and configuring the SIP container.
Session Initiation Protocol (SIP) is used to establish, modify, and terminate multimedia IP sessions including IP telephony, presence, and instant messaging. A SIP application in WebSphere is a Java program that uses at least one Session Initiation Protocol (SIP) servlet. A SIP servlet is a Java-based application component that is managed by a SIP servlet container.
The servlet container is a part of an application server that provides the network services over which requests and responses are received and sent. The servlet container decides which applications to invoke and in what order. A servlet container also contains and manages a servlet through its lifecycle.
SIP servlet containers can employ SIP proxy servers as surrogates to handle load balancing and security issues.
See about the SIP proxy server, see: Session Initiation Protocol proxy server.
This page is divided into the following subsections:
- Set the SIP container: Information and instructions for configuring SIP container properties and timers.
- Develop SIP applications: Reference information for developers.
- Deploy SIP applications: Information for installing, starting, and stopping, the applications.
- Securing SIP applications: Instructions for enabling security providers and setting up a TAI.
- Tracing a SIP container: Troubleshoot SIP applications through traces on the SIP container.
SIP in WAS
SIP applications
SIP container
SIP converged proxy
SIP high availability
Set the SIP container
Develop SIP applications
Deploy SIP applications
Secure SIP applications
Tracing a SIP container
Upgrading SIP applications
Replicating SIP sessions
Troubleshooting SIP applications
Tuning SIP servlets for Linux
SIP timer summary
Related tasks
Browse all SIP topics
Install a Session Initiation Protocol proxy server