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

78 HP-UX C SIP Stack Programmer’s Guide
Call-leg Transactions
RVSIP_CALL_LEG_TRANSC_STATE_CLIENT_GEN_REQUEST_SENT
After the application created a new call-leg transaction, it should call the
RvSipCallLegTranscRequest() function with a specific method. This function
will cause a request to be sent and the transaction will assume the GENERAL_
REQUEST_SENT state.
RVSIP_CALL_LEG_TRANSC_STATE_CLIENT_GEN_PROCEEDING
A call-leg transaction that received the first provisional response will assume
the PROCEEDING state.
RVSIP_CALL_LEG_TRANSC_STATE_CLIENT_GEN_FINAL_RESPONSE_RCVD
After a final response is received on a call-leg transaction, the transaction
assumes the FINAL_RESPONSE_RCVD state.
RVSIP_CALL_LEG_TRANSC_STATE_CLIENT_MSG_SEND_FAILURE
This state is assumed only if the SIP Stack works with the Enhanced DNS
feature. The call-leg transaction moves to this state when it fails to send a
request. A failure is defined as a timeout, network error or a request that was
responded to with 503.
In this state the application can:
 Continue DNS—try to send the request to the next address in
the transaction DNS list. For more information see the Working
with DNS chapter.
 Give Up—terminate the call-leg transaction.
RVSIP_CALL_LEG_TRANSC_STATE_TERMINATED
This state is the final call-leg transaction state. When the call-leg transaction is
terminated, it assumes the TERMINATED state. The application can no longer
reference the transaction.