SIP stack settings

Use this page to 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. To view this console page, click Servers > Server Types > WebSphere application servers > server_name > SIP container settings > SIP container > SIP stack.

Automatically reply to INVITE with "100 Trying" response

Whether to automatically reply to INVITE requests with a 100 Trying response. Disabling this setting might increase the number of INVITE retransmissions.

Information	Value
Data type	Boolean
Default	True

Hide message body

Whether to hide message content in log files. Set the value to True to remove the message body text from SIP messages printed in the log files. This setting only affects the representation of the messages in log files.

Information	Value
Data type	Boolean
Default	False

Enable outbound connection timeout

Whether to enable the outbound connection timeout.

Information	Value
Data type	Boolean
Default	False

Outbound connection timeout

Amount of time, in milliseconds, for creating outbound connections. This setting is relevant only for stream transports, such as Transmission Control Protocol (TCP) and Transport Layer Security (TLS). The default value of 0 provides an infinite amount of time.

Information	Value
Data type	Integer
Default	0

Maximum transmission unit

Maximum transmission unit, in bytes, for outbound User Datagram Protocol (UDP) requests. The SIP stack measures the size of a request before sending it out on the UDP channel. If the request is higher than the value specified for PATH_MTU-200, 1300 bytes by default, then the transport is switched from UDP to TCP before transmission.

Increase this value to send larger requests over the UDP channel; however, messages might be truncated or discarded. See the RFC 3261-18.1.1 specification for details.

Information	Value
Data type	Integer
Default	1500

Outbound proxy

Fixed address for routing all outbound SIP messages. The format is address:port/transport, such as 1.2.3.4:5065/tcp.

Best Practice: Do not use this setting if the container is fronted by an application server SIP proxy.

Information	Value
Data type	String
Default	empty string

Reference topic