Oracle Server E10293-02 Manual Do Utilizador
Using the appId Parameter to Set Addresses for SIP Applications
3-2 Oracle Communication and Mobility Server Developer’s Guide
, illustrates a ROUTE header present in the request. If the OCMS SIP
servlet container has been configured to acknowledge the IP address of 192.168.0.100
as its address, it then uses the appId in the ROUTE header and invokes the
application called presence.
as its address, it then uses the appId in the ROUTE header and invokes the
application called presence.
Example 3–1 The appId Parameter in the Route Header of an Incoming Request
SUBSCRIBE sip:bob@example.com
To: .
From: .
Route: <sip:192.168.0.100:5060;appId=presence>
the OCMS SIP servlet container uses the appId in the REQUEST URI header and
invokes the application presence if it has been configured to acknowledge 192.168.0.100
as its IP address.
invokes the application presence if it has been configured to acknowledge 192.168.0.100
as its IP address.
Example 3–2 The appId Parameter in the Request URI of an Incoming Request
SUBSCRIBE sip:bob@example.com;appId=presence
To: .
From: .
Route: <sip:192.168.0.100:5060>
In some instances, an OCMS SIP servlet container may receive requests that are
intended for other IP addresses if the outbound proxy for a SIP client is not a
pre-loaded route, but rather a connection to an outbound proxy through which it
sends requests. An OCMS SIP servlet container can only consider the appIds
contained in requests that are intended for it; even if the container hosts an application
that matches the one designated by the appId parameter, it cannot honor the request,
as the requested application resides at another IP address and the user requesting the
application may not belong to the system.
intended for other IP addresses if the outbound proxy for a SIP client is not a
pre-loaded route, but rather a connection to an outbound proxy through which it
sends requests. An OCMS SIP servlet container can only consider the appIds
contained in requests that are intended for it; even if the container hosts an application
that matches the one designated by the appId parameter, it cannot honor the request,
as the requested application resides at another IP address and the user requesting the
application may not belong to the system.
Configuring the appId Parameter
The appId parameter is configured as part of the SipUriList
attribute of the
Application
Router MBean (ocmsrouteloaderear, illustrated in
). Using this attribute,
you set the behavior of the OCMS SIP servlet container in response incoming INVITE,
MESSAGE
MESSAGE
, PUBLISH, REGISTER, and SUBSCRIBE requests by setting the application
routing sequence.