WAS v8.5 > Develop applications > Develop SIP applications

Develop SIP applications

A SIP application is a set of SIP servlets packaged in a SIP application archive file (SAR).

A SIP servlet is an application component managed by the SIP container that performs SIP signaling. The programming and deployment models are analogous to web servlets and therefore will be mapped to the WebSphere administrative model accordingly. It is possible to include web servlets in a SAR file (along with the required web.xml deployment descriptor) to create what is known as a converged application. See JSR 116 for details on SIP applications, servlets, converged applications, and status codes.

Subtopics

• Develop a custom trust association interceptor
  When you develop SIP applications, we can create a custom TAI.
• Develop SIP applications that support PRACK
  A SIP response to an INVITE request can be final or provisional. Final responses are always sent reliably, but provisional responses typically are not. For cases where you need to send a provisional response reliably, we can use the PRACK (Provisional response acknowledgement) method.
• Set up SIP application composition
  The JSR 116 standard for SIP applications states in section 2.4 that multiple applications may be invoked for the same SIP request. The process of setting up applications to comply with this standard is called application composition.
• SIP servlets
  This topic describes SIP servlets.
• Develop SIP applications that support PRACK
  A SIP response to an INVITE request can be final or provisional. Final responses are always sent reliably, but provisional responses typically are not. For cases where you need to send a provisional response reliably, we can use the PRACK (Provisional response acknowledgement) method.
• Set up SIP application composition
  The JSR 116 standard for SIP applications states in section 2.4 that multiple applications may be invoked for the same SIP request. The process of setting up applications to comply with this standard is called application composition.
• SIP servlets
  This topic describes SIP servlets.
• Develop applications that use the Asynchronous Invocation API
  We can use the Asynchronous Invocation API to transfer events that require processing in the context of a Session Initiation Protocol (SIP) application session to any server in a cluster based on the related application session ID. The Asynchronous Invocation API transfers the event task to the correct server.

Subtopics

• Develop a custom trust association interceptor
  When you develop SIP applications, we can create a custom TAI.
• Develop SIP applications that support PRACK
  A SIP response to an INVITE request can be final or provisional. Final responses are always sent reliably, but provisional responses typically are not. For cases where you need to send a provisional response reliably, we can use the PRACK (Provisional response acknowledgement) method.
• Set up SIP application composition
  The JSR 116 standard for SIP applications states in section 2.4 that multiple applications may be invoked for the same SIP request. The process of setting up applications to comply with this standard is called application composition.
• SIP servlets
  This topic describes SIP servlets.
• Develop SIP applications that support PRACK
  A SIP response to an INVITE request can be final or provisional. Final responses are always sent reliably, but provisional responses typically are not. For cases where you need to send a provisional response reliably, we can use the PRACK (Provisional response acknowledgement) method.
• Set up SIP application composition
  The JSR 116 standard for SIP applications states in section 2.4 that multiple applications may be invoked for the same SIP request. The process of setting up applications to comply with this standard is called application composition.
• SIP servlets
  This topic describes SIP servlets.
• Develop applications that use the Asynchronous Invocation API
  We can use the Asynchronous Invocation API to transfer events that require processing in the context of a Session Initiation Protocol (SIP) application session to any server in a cluster based on the related application session ID. The Asynchronous Invocation API transfers the event task to the correct server.

Related concepts:

SIP IBM Rational Application Developer for WebSphere framework

Related

Browse all SIP topics

Reference:

SIP industry standards compliance
Runtime considerations for SIP application developers

+

Search Tips   |   Advanced Search