HP-UX C SIP Stack Programmer's Guide (Novembery 2007)

22 HP-UX C SIP Stack Programmer’s Guide
Conformance to Standards
TRANSACTION API
The Transaction API enables you to handle transactions that are not related to a
call-leg, such as OPTIONS. Using the API, you can create new transactions,
send outgoing requests, and respond to incoming requests. The Transaction API
provides a set of callbacks and hooks that enables you to control some of the
transaction behavior. You can use the Transaction API to implement SIP servers
such as Registrars or Proxies.
L
OW-LEVEL API The Low-level API includes:
 Message API
 Transmitter API
 Transport API
MESSAGE API
The Message API provides access to SIP message content, enabling the
application to browse and edit any part of the message. There are API functions
for complete SIP messages and also for message parts, such as headers and
URLs.
The message API is also the interface to the parsers and encoders provided with
the SIP Stack. You can copy, store and re-use messages and message parts.
TRANSMITTER API
The Transmitter API enables you to send a single message that does not belong
to a transaction. The transmitter is responsible for address resolution and the
actual message sending, including DNS queries such as SRV and NAPTR.
TRANSPORT API
The Transport API provides control over connection persistency, TLS and TOS
implementation, and dynamic local address functionality. It also provides low-
level hook functions for tight control over SIP Stack functionality.
CONFORMANCE TO
S
TANDARDS
SIP Stack was developed in conformity with IETF standards and includes SIP
related features.
SIP STACK The SIP Stack component of the SIP Stack was developed in conformity with
the specifications of RFC 3261 and various SIP extensions.