Assigning Header Formats with WlssSipServletMessage

3-4 Developers Guide

3.2 Using Content Indirection in SIP Servlets

This section describes how to develop SIP Servlets that work with indirect content specified in the SIP message body.

3.2.1 Overview of Content Indirection

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: ■ When the message bodies include large volumes of data. In this case, content indirection can be used to transfer the data outside of the SIP network using a separate connection or protocol. ■ For bandwidth-limited applications. In this case, content indirection provides enough metadata for the application to determine whether or not it must retrieve the message body potentially degrading performance or response time. OWLCS provides a simple API that you can use to work with indirect content specified in SIP messages.

3.2.2 Using the Content Indirection API

The content indirection API provided by OWLCS 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.util.ContentIndirectionUtil, and an interface for accessing content metadata, com.bea.wcp.sip.util. 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.

3.2.3 Additional Information

Complete details about content indirection are available in RFC 4483. See the Oracle Fusion Middleware WebLogic Communication Services API Reference for additional documentation about the content indirection API.

3.3 Generating SNMP Traps from Application Code

This section describes how to use the OWLCS SipServletSnmpTrapRuntimeMBean to generate SNMP traps from within a SIP Servlet.

3.3.1 Overview

OWLCS includes a runtime MBean, SipServletSnmpTrapRuntimeMBean, that enables applications to easily generate SNMP traps. The OWLCS MIB contains seven new OIDs that are reserved for traps generated by an application. Each OID FORCE_LONG LONG Contact Table 3–3 Cont. API Behavior for System Headers