|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
SIP Servlet Container (sipserver.xml)This document describes how to configure the SIP servlet container capabilities provided by SIP Servlet Engine. The configuration information of the SIP servlet container is stored in the configuration file sipserver.xml. This file is located in the WebLogic domain directory (for example, $BEA_HOME/user_projects/domains/mydomain). When the following settings have been edited directly, you need to restart WebLogic Server to reflect the changes. If the settings were specified via Administration console, restarting the server may not be requisite in some cases. Setting Up a PropertyProperty is configuration information referenced by SIP Servlet Engine at run time, and is 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 or its value, respectively. The following values can be set for the <param-name> tag:
Setting Up a FilterA filter is a component for filtering received SIP messages before they are processed by SIP Servlet container. Filtering process has the pipeline structure. The SIP messages are processed through the 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.
SIP Servlet Engine 3.0 provides the following filters.
You can set a parameter to the filter by using the <filter-param> tag. The configurable parameter varies depending on the filter. For information about the configurable parameter, see each filter. The following shows the settings configured during installation. <filter classname="com.oki.sip.engine.security.BlockingFilter"> <filter-param> <param-name>ignore</param-name> <param-value>recorder</param-value> </filter-param> </filter> <filter classname="com.oki.sip.engine.security.WLSSecurityManagerFilter"/> com.oki.sip.engine.security.BlockingFilterThis filter checks the incoming lockout and outgoing lockout flags configured by the administrator for the user. If the outgoing lockout flag of the user whose URI specified in the From header is enabled, the 403 response will be returned. If the incoming lockout flag of the user whose URI specified in the To header is enabled, the 480 response will be returned. To set the incoming lockout and outgoing lockout flags for the user, use the SIP Servlet Engine Management tool (See sip-admin Users Guide). The configurable parameter is:
com.oki.sip.engine.security.WLSSecurityManagerFilterThis filter is used to implement the security features defined in the sip.xml (for example, <security-constraint>). For more information about using the security features, see Security. The configurable parameter is:
com.oki.sip.engine.server.AccessLogFilterAccessLogFilter is a filter to record server access by SIP. In AccessLogFilter, you can set the following values to <param-name>.
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.oki.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 ServerA 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.
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:
The following shows the example. If the destination determined in accordance with the routing rule of RFC 3261, the message is sent to that destination. If not, the message is sent to "172.21.146.198." <proxy> <proxy-policy>domain,proxy</proxy-policy> <default-proxy host="172.21.146.198" port="5060" transport="udp"/> <!-- Other proxy tags can be added. --> </proxy> Settings for Incoming-Call RegulationTo enable incoming-call regulation, set <income-call> (For details on incoming-call regulation, see Blockage Function). The <income-call> tag has the following three tags. Settings for these tags are required at all times.
The "session generation rate" and "queue length" cannot be monitored at the same time. Here is an example setting in the sipserver.xml. It is configured to trigger the regulation at 50 sessions/sec and terminate the regulation at 40 sessions/sec. <income-call> <threshold-policy>session-rate</threshold-policy> <threshold-value>50</threshold-value> <release-value>40</release-value> </income-call> Setting Up a Load BalancerIf the SSE is to be operated with a load balancer, configure the <loadbalancer> tag. The <loadbalancer> tag has the following two attributes.
The port of the load balancer is set by <port-info> tag. The <port-info> tag has the following two attributes.
The following is a configuration when the load balancer runs on the host having an address of 192.168.0.1 and UDP port number of 6080. <loadbalancer host="192.168.0.1" enable="true"> <port-info port="6080" transport="udp"/> </loadbalancer> Setting Up a ConnectorA 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.
The execute queue provided by WebLogic Server is used to handle the SIP messages received by the connector. This execute queue is specified with the <thread-pool-name>. During installation, the execute queue "sip.transport.Default" is configured to be used. The setting of the execute queue is contained in the config.xml. <connection-timeout> specifies the time in seconds which the connector that uses TCP will keep the connection while the connection is established. During installation, this value is set to 60 seconds. The following shows the settings configured during installation. The connector which uses both TCP and UDP is configured to receive the SIP TCP messages and the SIP UDP messages through the port 5060 and 5060, respectively. <transport> <connector port="5060" transport="udp" classname="com.oki.sip.bea.wls81.connector.WLSConnector"/> <connector port="5060" transport="tcp" classname="com.oki.sip.bea.wls81.connector.WLSConnector"/> <thread-pool-name>sip.transport.Default</thread-pool-name> <connection-timeout>60</connection-timeout> </transport> Last Modified:Mon Jan 17 17:05:31 JST 2005 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|