Default sipserver.xml Configuration (Deprecated)

Setting Up a Property

Configuration properties are referenced by WebLogic SIP Server at run time, and are specified with the <container-param> tag. The <container-param> tag has two children: the <param-name> and <param-value> tags. Each tag specifies the property name and its value, respectively.

The following values can be set for the <param-name> tag:

SessionSwapoutDuration - Set the period (by ms) from the last accessed time of the application session to the time when it is swapped out. However, the timing of swap-out would be every 1/10 seconds of this value (For example, if the period until swap-out is set as 10 minutes, it would happen every 1 minute. If a value shorter than 30 seconds is specified, it would be every 30 seconds). Accordingly, swap-out may not always occur immediately after the specified period of time has passed. If a negative value is set, the swapping function is disabled. A value less than 60000 cannot be specified. If you have not specified SessionSwapoutDuration, the value is set to 600000 (10 minutes).

listenAddressCacheDuration - Specify the period to cache the address information retrieved by network channel function. The specification is made by msec and the shortest period that can be specified is 500 (msec). In addition, the default is 30 seconds (30,000) and this default period is also used when a negative value is specified.

Setting Up a Filter (Deprecated)

Note: This release of WebLogic SIP Server deprecates creating general-purpose SIP filters by extending a base filter class.

A filter is a component for filtering received SIP messages before they are processed by SIP Servlet container. The filtering process uses the pipeline structure. SIP messages are processed with filters in the order which the filters are configured in the sipserver.xml. A filter is specified with the <filter> tag which has the following attribute:

classname - Specifies the class name which implements the filter. This attribute is required.

com.bea.wcp.sip.engine.server.AccessLogFilter

AccessLogFilter is a filter to record access to WebLogic SIP Server. In AccessLogFilter, you can set the following <param-name> values:

The following tokens can be specified:

The access log is stored to the file specified in the log4j.properties in the directory where WebLogic Server runs. The default setting is (the directory where WLS runs)/logs/sip/access.log.

The following shows the settings configured during installation.

   <filter classname="com.bea.wcp.sip.engine.server.AccessLogFilter">
     <filter-param>
       <param-name>format</param-name>
       <param-value>{0} {1}, {2}, {3}, {4}, {5}</param-value>
     </filter-param>
     <filter-param>
       <param-name>0</param-name>
       <param-value>%date</param-value>
     </filter-param>
     <filter-param>
       <param-name>1</param-name>
       <param-value>%time</param-value>
     </filter-param>
     <filter-param>
       <param-name>2</param-name>
       <param-value>%mtype</param-value>
     </filter-param>
     <filter-param>
       <param-name>3</param-name>
       <param-value>%method</param-value>
     </filter-param>
     <filter-param>
       <param-name>4</param-name>
       <param-value>%from_uri</param-value>
     </filter-param>
     <filter-param>
       <param-name>5</param-name>
       <param-value>%to_uri</param-value>
     </filter-param>
   </filter>

Setting Up a Proxy Server

A proxy server is specified with the <default-proxy> tag. You can configure multiple proxy servers. The TCP messages are sent to the proxy servers in the order which the proxy servers are configured. The UDP messages are sent only to the first proxy server. The <default-proxy> tag has the following three attributes. These attributes are required.

host - The host name or IP address of the proxy server.

port - The connection port number for the proxy server.

transport - The transport name used by the proxy server. The possible values are "tcp" and "udp."

You can change the behavior of proxy process by setting a policy. A policy is specified with the <proxy-policy> tag. The possible values are as follows:

domain - Sends messages as per the routing rule defined by RFC 3261.

proxy - Sends the message to the downstream proxy specified in the "default-proxy". If there are multiple specifications for "default-proxy," they are tried in the order in which they are specified. However, if the transport tries the UDP proxy, the settings for the subsequent proxies are ignored.

domain,proxy - If the destination domain can be resolved, behaves like when domain is specified. If it cannot be resolved, behaves like when proxy is specified.

The following shows the default proxy configuration for new WebLogic SIP Server domains. If the destination is determined in accordance with the routing rule of RFC 3261, the message is sent to that destination. If not, the message is sent to the host "siplb.bea.com" (which would need to be configured appropriately).

   <proxy>
     <proxy-policy>domain,proxy</proxy-policy>
     <default-proxy host="siplb.bea.com" port="5060" transport="udp"/>
     <!-- Other proxy tags can be added. -->
   </proxy>

Settings for Incoming-Call Regulation

Setting Up a Connector (Deprecated)

Note: WebLogic SIP Server 2.0.1 deprecates the use of connectors for configuring port numbers fo SIP TCP or UDP. The method for specifying port numbers may change in the future.

A connector is a component to convert the SIP message received using TCP or UDP to the recognizable format for the SIP Servlet Container. A connector is specified with the <connector> tag. The <connector> tag has the following four attributes. You can configure multiple connectors.