The following sections describe how to develop SIP Servlets that work with indirect content specified in the SIP message body:
Data provided by the body of a SIP message can be included either directly in the SIP message body, or indirectly by specifying an HTTP URL and metadata that describes the URL content. Indirectly specifying the content of the message body is used primarily in the following scenarios:
Oracle Communications Converged Application Server provides a simple API that you can use to work with indirect content specified in SIP messages.
The content indirection API provided by Oracle Communications Converged Application Server helps you quickly determine if a SIP message uses content indirection, and to easily retrieve all metadata associated with the indirect content. The basic API consists of a utility class, com.bea.wcp.sip.engine.server.ContentIndirectionUtil
, and an interface for accessing content metadata, com.bea.wcp.sip.engine.server.ICParsedData
.
SIP Servlets can use the utility class to identify SIP messages having indirect content, and to retrieve an ICParsedData
object representing the content metadata. The ICParsedData
object has simple “getter” methods that return metadata attributes.
Complete details about content indirection are available in a draft document: http://www.ietf.org/internet-drafts/draft-ietf-sip-content-indirect-mech-05.txt.
See also the Oracle Communications Converged Application Server JavaDoc for additional documentation about the content indirection API.