Oracle Server E10293-02 Benutzerhandbuch

SIP Servlets in OCMS

2-18  Oracle Communication and Mobility Server Developer’s Guide

to false as does the whole rule while the three conditions are all inside the and 
condition.

This section describes the OCMS extensions to the SIP Servlet API as well as its 
implementation of it. Sections include:

■

■

■

■

■

■

When the SIP container receives an initial request, it attempts to invoke a SIP 
application. The SIP container selects the application based on the appId parameter. 
See 

 for information on appId. The 

workflow of the SIP container is as follows:

Check if the request contains an indication of which application to invoke.

If there is no name of an application to invoke, then the SIP container selects 
default applications.

If the application is named by the request, then the SIP container locates the 
application and then invokes it. 

For example, to respond to an incoming request, a SIP servlet container evaluates the 
following SIP applications: 

■

Application A has the following two SIP servlets defined in its sip.xml:

Servlet 1 matches INVITE requests.

Servlet 2 matches MESSAGE requests.

■

Application B has the following SIP servlet defined in its sip.xml:

Servlet 1 matches INVITE requests.

■

Application C has the following two SIP servlets defined in its sip.xml:

Servlet 1 matches REGISTER requests.

Servlet 2 matches all requests. 

■

Application D has the following two SIP servlets defined in its sip.xml:

Servlet 1 matches a SUBSCRIBE request.

Servlet 2 matches a PUBLISH request. 

■

Application E has the following SIP servlet defined in its sip.xml.

The container selects a default application when initial 

requests do not indicate which applications should be invoked.