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

290 HP-UX C SIP Stack Programmer’s Guide
Persistent Connection Handling
/*==========================================================================*/
SIP STACK OBJECT
P
ERSISTENCY APIS AND
E
VENTS
Each of the SIP Stack objects—call-legs, subscriptions, register-clients,
transactions and transmitters—offers several API functions to query and change
the persistency level of the object, and to query and determine the connection
that the object will use. In the following explanations, XXX represents each of
the SIP Stack object types.
RVSIPXXXSETPERSISTENCY()
You can use the RvSipXXXSetPersistency() API function to change the
persistency definition of each of the SIP Stack objects at runtime. This function
receives a Boolean value that indicates whether or not the application wishes the
specific object to be persistent. The persistency behavior of each object depends
on the object type. Persistent TU objects will apply their persistency to the
transactions they create.
The following API functions are supplied:
RvSipCallLegSetPersistency()
Sets the persistency level of call-legs and subscriptions.
Note To set the persistency level of a subscriptions, you must first get the
Subscription-associated call-leg and then use the Call-leg API. For more
information, see the Call-leg Functions chapter in the SIP Stack Reference Guide.
RvSipRegClientSetPersistency()
Sets the persistency level of reg-client objects.
RvSipTransactionSetPersistency()
Sets the persistency level of transactions.
RvSipTransmitterSetPersistency()
Sets the persistency level of transmitters.
RVSIPXXXGETPERSISTENCY()
You can use the RvSipXXXGetPersistency() function to query whether a
specific object is persistent or not.