HP-UX Java SIP Stack Programmer's Guide (September 2007)
Table Of Contents
- HP-UX Java SIP Stack Programmer's Guide
- Table of Contents
- About This Document
- 1 Introduction
- 2 JSR32 JAIN SIP APIs
- 3 Creating an Application
- 4 Compiling and Running Applications Using the HP-UX JSR32 Kit
- 5 Troubleshooting HP JSR32 APIs
- Glossary
- Index

Table 2-1 SIP Stack Parameters (continued)
DescriptionParameter Name
Specifies the fully qualified classpath for an
implementation of the MessageLogFactory.
The SIP stack calls the MessageLogFactory
functions to log the messages that are received
or sent. The MessageLogFactory enables
you to log auxiliary information related to the
application or environmental conditions into
the log stream.
com.hp.net.javax.sip.LOG_FACTORY
Specifies whether RFC 2543 (SIP: Session
Initiation Protocol) is fully supported in the
stack. If RFC 2543 is fully supported, check
whether the To tag is disabled. As a result,
forked dialogs do not work properly. If dialog
forking is not important for an application,
you can set this flag to true.
com.hp.net.javax.sip.RFC_2543_SUPPORT_ENABLED
Specifies the frequency (in milliseconds) with
which an application can audit the SIP stack
about the health of its internal threads. The
audit of the SIP stack enables an application
to detect failures, such as internal thread
terminating caused by an exception or a
deadlock condition. Such events results in the
stack becoming inoperable and, therefore,
requires immediate action from the application
layer. The immediate action can be an alarm,
trap, reboot, or failover. Thread audits are
disabled by default.
com.hp.net.javax.sip.THREAD_AUDIT_INTERVAL_
IN_MILLISECS
50 JSR32 JAIN SIP APIs