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

Working with Call-legs (Dialogs) 75
Call-leg Transactions
RVSIP_CALL_LEG_PRACK_STATE_PRACK_RCVD
A PRACK request was received.
RVSIP_CALL_LEG_PRACK_STATE_PRACK_FINAL_RESPONSE_SENT
A PRACK final response was sent.
CALL-LEG
T
RANSACTIONS
A call-leg transaction is a transaction that is sent in the context of a call-leg but
does not change the call-leg state. Such a transaction uses the call-leg identifiers
(To, From and Call-ID), an increased CSeq, Route list, and Authentication
information when it exists. An example of a call-leg transaction is the INFO
transaction sent in the context of a call-leg.
The Call-leg API contains a set of functions and function callbacks that enables
you to handle transactions inside a call-leg.
CALL-LEG
TRANSACTION
CONTROL
The following API functions provide call-leg transaction control:
RvSipCallLegTranscCreate()
Creates a new general transaction that is related to the supplied call-leg. The
transaction will have the call-leg characteristics, such as To header, From
header, Call-ID, and local and outbound addresses. The application can define
an application handle to the transaction and supply it to the Stack when calling
this function. The application handle will be supplied back to the application
when the RvSipCallLegTranscStateChangedEv() callback is called.