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

Working with Transactions 105
Transaction State Machine
RVSIP_TRANSC_STATE_SERVER_GEN_REQUEST_RCVD
Upon receipt of a request (that is not a retransmission) by a server transaction,
the transaction assumes the SERVER_GENERAL_REQUEST_RECEIVED
state. In this state, it is up to you to respond to the request using the transaction
API. You may begin with sending provisional responses. You must end with
sending a final response, or terminating the transaction. The transaction does
not set any timer in this state.
RVSIP_TRANSC_STATE_SERVER_GEN_FINAL_RESPONSE_SENT
When calling RvSipTransactionRespond(), the transaction generates and sends
a response message. The transaction will then assume the
SERVER_GENERAL_FINAL_RESPONSE_SENT state. When entering this
state, a transaction timer is set to generalLingerTimer if the transport is an
unreliable transport. When this timer expires, the transaction is terminated and
assumes the TERMINATED state. If the transport is a reliable transport, the
transaction is terminated and assumes the TERMINATED state immediately
when it reaches this state. (Timer J as defined in RFC 3261).