Oracle Server E10293-02 Benutzerhandbuch

Seite von 108
Using the appId Parameter to Set Addresses for SIP Applications
Advanced SIP Servlet Configuration  3-3
Figure 3–1  Setting the Application Routing for an INVITE Request 
The SipUriList attribute is comprised of a comma-separated list of URIs, transport 
methods, and appIds of applications that the Application Router inserts in the 
ROUTE header of an incoming request.
The default list, which routes requests to the Proxy Registrar, is defined as
sip:<SIP Container IP Address>:<SIP port>;transport=TCP;lr;appId=proxyregistrar
For example:
sip:144.25.174.189:5060;transport=TCP;lr;appId=proxyregistrar
Request routing is set according to the order of the applications listed in this attribute. 
For example, to call an application called dialin as the first destination for an INVITE 
request, insert the information for dialin as the first item on the list as follows: 
sip:144.25.174.189:5060;transport=TCP;lr;appId=dialin
,sip:144.25.174.189:5060;    
   transport=TCP;lr;appId=proxyregistrar
Adding Deployed Applications to the SipUriList Attribute
To ensure that applications that you deploy to the OCMS SIP servlet container are 
invoked in response to incoming requests, you must add any request-related 
application that you deploy to this list. The name of the application defined for the 
appId
 parameter (which is case-sensitive) can either be the full name of the deployed 
application, or an alias for the application. For an alias, the name must match the 
application alias set for the ApplicationAliases parameter of the SIP Servlet Container 
MBean. For more information on the SIP Servlet Container MBean and deploying 
applications to the OCMS SIP servlet container, see Oracle Communication and Mobility 
Server Administrator’s Guide
.
Note: 
The Proxy Registrar must always be the last item listed in the 
SIPUriList attribute.