Oracle Server E10293-02 ユーザーズマニュアル
Advanced SIP Servlet Configuration 3-1
3
Advanced SIP Servlet Configuration
This chapter describes advanced topics related to SIP servlets through the following
sections:
sections:
■
■
Using the appId Parameter to Set Addresses for SIP Applications
Because JSR 116 does not state how to set the address for a SIP application, OCMS
extends the specification by including a parameter called appId, (application ID)
which is located either in the URI of the top-most ROUTE header (
extends the specification by including a parameter called appId, (application ID)
which is located either in the URI of the top-most ROUTE header (
), or in
the REQUEST URI (
) of request messages. The OCMS SIP servlet
container checks both of these fields for this parameter, one that ensures that the
appropriate application is invoked in response to incoming INVITE, MESSAGE,
PUBLISH
appropriate application is invoked in response to incoming INVITE, MESSAGE,
PUBLISH
, REGISTER, and SUBSCRIBE requests.
When the OCMS SIP servlet container receives incoming requests that do not contain
the appId parameter, it invokes the Application Router to insert the application
routing information in the request’s ROUTE header.
the appId parameter, it invokes the Application Router to insert the application
routing information in the request’s ROUTE header.
How the OCMS SIP Servlet Container Identifies the appId Parameter
The OCMS SIP servlet container interprets the value defined for the appId parameter
as the name of the application to invoke for an incoming request. This value can be
defined as either the full application name, or the application alias that is set using the
ApplicationAliases attribute of the SipServletContainer MBean (described in Oracle
Communication and Mobility Server Administrator’s Guide). For example, if the OCMS SIP
servlet container receives a request that includes the appId parameter, the container
searches for the value set for the parameter, such as presence in
as the name of the application to invoke for an incoming request. This value can be
defined as either the full application name, or the application alias that is set using the
ApplicationAliases attribute of the SipServletContainer MBean (described in Oracle
Communication and Mobility Server Administrator’s Guide). For example, if the OCMS SIP
servlet container receives a request that includes the appId parameter, the container
searches for the value set for the parameter, such as presence in
. If the
container cannot find an application named presence, it returns a 403 Response
(Forbidden). However, if the container locates the application defined by the appId
parameter, it requests this application to process the request using the match method
described in
(Forbidden). However, if the container locates the application defined by the appId
parameter, it requests this application to process the request using the match method
described in
. If the application does not have a servlet
with a matching rule, then the match method returns null and the container replies
with a 403 Response.
with a 403 Response.
If the request does not contain a ROUTE header, then the container checks appId
included in the REQUEST URI.
included in the REQUEST URI.
Note:
In general, any requests generated by a SIP client other than
Oracle Communicator will not contain the appId parameter in either
the ROUTE or REQUEST URI headers.
the ROUTE or REQUEST URI headers.