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

Working with the Transport Layer 299
Connection API
RVSIP_TRANSPORT_CONN_STATE_CONNECTING
Calling the RvSipTransportConnectionConnect() function in the READY state
will move the connection to the CONNECTING state. While in the
CONNECTING state, the SIP Stack tries to connect the connection to the
remote party. If the connect attempt succeeds, the connection assumes the
TCP_CONNECTED state. Otherwise, the connection assumes the
TERMINATED state with the
RVSIP_TRANSPORT_CONN_REASON_ERROR reason.
RVSIP_TRANSPORT_CONN_STATE_TCP_CONNECTED
Upon receiving the network connected event, the connection moves to the
TCP_CONNECTED state. While in this state, the connection can send and
receive SIP messages. Calling RvSipTransportConnectionTerminate() in this
state will move the connection to the CLOSING state and the connection will
start the disconnection procedure. This will also be the case for client
connections that are left with no owners.
RVSIP_TRANSPORT_CONN_STATE_CLOSING
A client connection that remains with no owners, or any connection on which
the application called the RvSipTransportConnectionTerminate() function
moves to the CLOSING state. While in this state, the connection cleans and then
shuts down the established socket connection. The connection will move to the
CLOSED state upon receiving a network event that indicates that the connection
was closed by the remote party.
RVSIP_TRANSPORT_CONN_STATE_CLOSED
The connection moves to the CLOSED state upon receiving a network event
that indicates that the connection was closed by the remote party. In the
CLOSED state, the connection closes its internal socket. The connection then
moves to the TERMINATED state.
RVSIP_TRANSPORT_CONN_STATE_TERMINATED
The final connection state. When a connection is terminated, the connection
assumes the TERMINATED state. Upon reaching the TERMINATED state,
you can no longer reference the connection.