HP-UX Java SIP Stack Programmer's Guide (February 2008)

Table 2-1 SIP Stack Parameters (continued)
DescriptionParameter Name
Logs valid incoming messages. If SERVER_LOG
is not specified (that is, it contains a null value)
and the value of TRACE_LEVEL is more than
16, the error message are printed to standard
output.
com.hp.net.javax.sip.SERVER_LOG
Specifies the location for storing the debug log
messages.
com.hp.net.javax.sip.DEBUG_LOG
Sets tracing and debugging using the TRACE
and DEBUG strings. If you set TRACE_LEVEL
to a value greater or equal to 16, the incoming
valid messages are logged in the SERVER_LOG.
If you set TRACE_LEVEL to 32 and specify a
DEBUG_LOG, that trace information is dumped
in the specified DEBUG_LOG file.
com.hp.net.javax.sip.TRACE_LEVEL
Specifies a boolean value that captures the
message content into a log file. HP does not
recommend you to log content if you are using
SIP to push a lot of information through TCP.
The default value is false.
com.hp.net.javax.sip.LOG_MESSAGE_CONTENT
Specifies the maximum size of data that a TCP
connection can read. The minimum value is 4
KB. MAX_MESAGE_SIZE prevents Denial of
Service (DoS) attacks that are launched by
writing to a TCP connection until the server
chokes. The default value is infinity, that is,
no limit.
com.hp.net.javax.sip.MAX_MESSAGE_SIZE
Specifies a boolean value that closes the server
socket after a server transaction enters the
TERMINATED state, if
CACHE_SERVER_CONNECTIONS is set to false.
This enables a server to protect against
TCP-based DoS attacks launched by clients
that initiate multiple transactions. If
CACHE_SERVER_CONNECTIONS is set to true,
the stack retains the socket in open state to
maximize the performance of the stack at the
expense of the thread and memory resources,
and exposes itself to DoS attacks. The default
value is true.
com.hp.net.javax.sip.CACHE_SERVER_CONNECTIONS
HP-UX JSR32 Features 47