WAS v8.5 > Develop applications > Develop Communications Enabled Applications > Develop communications enabled applications

Develop SIP communications applications

• Use the SIP application router to select the order in which SIP applications are triggered.

  When configuring a SIP application router, we can either use the default application router or create a custom application router.

• 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.

• Use the Domain Resolver API to perform DNS lookups of SIP URIs using the RFC 3263 protocol.

  The Domain Resolver API provides an interface that enables an application to perform DNS queries for SIP URIs.

• Create a SIP servlet request that includes proprietary header fields.

  SIP proprietary header fields enable certain SIP settings to be implemented on a per message basis. SIP settings set at the SIP container level apply to all SIP messages handled by that SIP container.

Subtopics

• JSR 289 overview
  v8.5 includes support for SIP Servlet Specification 1.1, also referred to as Java Specification Request (JSR) 289.
• Asynchronous Invocation API
  Use the Asynchronous Invocation API to transfer events that require processing in a SIP application session to any server in a cluster based on an application session ID.
• Domain Resolver API
  Use the Domain Resolver API to perform DNS lookups of SIP URIs using the RFC 3263 protocol. These lookups can be performed synchronously to avoid having to preserve state in order to handle an asynchronous callback. They can also be performed asynchronously if you need a better performing interface.
• Domain Resolver API
  Use the Domain Resolver API to perform DNS lookups of SIP URIs using the RFC 3263 protocol. These lookups can be performed synchronously to avoid having to preserve state in order to handle an asynchronous callback. They can also be performed asynchronously if you need a better performing interface.
• SIP proprietary header fields
  We can create a SIP servlet request that includes proprietary header fields. SIP proprietary header fields enable certain SIP settings to be implemented on a per message basis. SIP settings set at the SIP container level apply to all SIP messages handled by that SIP container.

Reference:

SIP proprietary header fields

+

Search Tips   |   Advanced Search