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

318 HP-UX C SIP Stack Programmer’s Guide

SIP Stack and TLS

RvSipTransportConnectionTlsGetEncodedCert()

Gets the encoded certificate of a connection.

RvSipTransportConnectionTlsRenegotiate()

Restarts the TLS handshake on the next received message. As a result, the

certificate will be renegotiated and the session key will be regenerated. The state

of the connection is not affected by the undergoing process of the renegotiation.

The application does not receive any indication about renegotiation success.

However, in case of failure, the connection will be terminated.

TLS CONNECTION

VENTS

The TLS connection supplies several events in the form of callback functions to

which your application may listen and react. Use

RvSipTransportMgrSetEvHandlers() to register on these callbacks.

Note To work with TLS, you must implement and register on the

RvSipTransportConnectionTlsStateChangedEv() callback.

RvSipTransportConnectionTlsSequenceStartedEv()

The SIP Stack lets you create your own handle to a TLS connection. This will

prove useful when you have your own application TLS connection database.

You can provide the SIP Stack with your TLS connection handle, which the

SIP Stack will supply when calling your application callbacks.

After a TLS connection has reached the TCP CONNECTED state, the

RvSipTransportConnectionTlsSequenceStartedEv() callback will be called,

allowing the application to exchange handles with the SIP Stack.

RvSipTransportConnectionTlsStateChangedEv()

Informs the application of the various stages of the TLS connection

establishment. In this callback the application will be informed of the

HANDSHAKE_READY state. In this state the application must call the

RvSipTransportConnectionTlsHandshake() function to start the handshake

process. An application that wishes to work with TLS must implement this

callback.