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

324 HP-UX C SIP Stack Programmer’s Guide
SIP Stack and TLS
numOfTlsEngines
The maximum number of TLS engines. TLS engines are used to give a set of
properties to a TLS connection.
maxTlsSessions
The maximum number of TLS sessions. A TLS session is the TLS equivalent to
a TCP connection and contains TLS data required to manage the TLS
connection. For more information see the Configuration chapter.
Both local and remote peers can change their multihoming address sets by
removing the binding to some of the multihoming IPs, or by binding sockets to
the multihoming IPs. Local multihoming addresses can be updated both for
connection and local address objects.
The following API functions can be used to change the local multihoming
addresses:
The following callback can be used for monitoring changes of the multihoming
addresses by the remote peer:
RvSipTransportConnectionStatusEv()
The connection notifies the application about events that do not affect the
connection state using the connection status callback. Upon receiving
notification about changes in the multihoming addresses from the remote peer,
the SIP Stack calls the status callback. With the call to the callback, the SIP
Stack provides the following:
 The address that was changed
 The type of change (address removal or addition)
Sample Code
The following code sample monitors the status of the remote multihoming
addresses.
/*==============================================================*/
void RVCALLCONV AppConnectionStatusEvHandler(
IN RvSipTransportConnectionHandle hConn,
IN RvSipTransportConnectionOwnerHandle hOwner,
IN RvSipTransportConnectionStatus eStatus,
IN void* pInfo)
{
switch(eStatus)
{