Configure the SIP container

Configure the SIP container to adjust message response times or set a custom property.

Use the administrative console to configure SIP container settings. Complete the following steps to find and configure the SIP container settings.

Tasks

1. Start WebSphere Application Server.

2. From the administrative console, click...

           Servers > Server Types > WebSphere application servers > server.

3. From Container Settings, expand SIP Container Settings, and click SIP Container. Select the container settings to change.

   • From General Properties, we can configure session, message, and response time maximums. See Session Initiation Protocol container settings and SIP container custom properties.

   • From Additional Properties, we can define custom properties, manage transport chains or inbound channel settings, or configure the session manager.

4. After configuring the SIP container, click Apply to save the changes.

5. Restart WAS.

Changes to the SIP container settings take effect after you restart WAS.

As the number of SIP containers grow in a deployment, the larger the heap settings need to be on the SIP proxy server. For example, a deployment of 20 containers requires a minimum heap size of 60 MB, so a -Xmo60m parameter should be added to the Generic JVM arguments field on the Java virtual machine panel of the admin console. However, a deployment of 70 containers requires a larger value such as 200 MB (-Xmo200m). See the information center topic Java virtual machine settings for more information about Generic JVM arguments.

Subtopics

• Enable SIP flow token security
  SIP container supports client-initiated connection reuse. SIP flow token security allows us to establish communication between a server and SIP clients in situations where the SIP clients can create a connection to the server, but are not prepared to accept connections from the server.
• SIP container custom properties
  We can add any of the following custom properties to the configuration settings for a SIP container.
• Use DNS procedures to locate SIP servers
  The Session Initiation Protocol (SIP) can use Domain Name Server (DNS) procedures for a client to resolve a SIP Uniform Resource Identifier (URI).
• SIP container settings
  Use this page to configure the SIP container settings for SIP.
• SIP stack settings
  Configure values for the Session Initiation Protocol (SIP) stack settings that are different from those specified in RFC 3261. The default values are the same as those specified for RFC 3261.
• SIP timers settings
  Set values for the Session Initiation Protocol (SIP) timers that are different from those specified in RFC 3261. SIP timers provide a mechanism for session expiration.The default values are the same as those specified for RFC 3261.
• Configure SIP timers
  We can configure SIP timers to set values for the SIP timers that are different from default values specified in RFC 3261. SIP timers provide a mechanism for session expiration. The default values are the same as those specified for RFC 3261.
• Performing controlled failover of SIP applications
  We can take an active application out of the loop using a controlled failover.
• Replicating SIP sessions
  We can set up a replication domain for SIP sessions if we want replication of session, and dialog state information to occur during typical SIP processing. The SIP container typically uses the Data Replication Service (DRS) to replicate all state information. Because DRS does not provide a way to confirm when data replication has completed, the only thing that can be quantified is when a piece of state information is queued for replication. Within this topic, references to replication of data only means that the data has been queued for replication.

Browse all SIP topics

Configure transport chains

Configure security for the SIP container

Configure digest authentication for SIP

SIP PMI counters

SIP container inbound channel settings

SIP digest authentication settings

Java virtual machine settings