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

50 HP-UX C SIP Stack Programmer’s Guide
Call-leg API
 When this function is used to reject a request, you cannot use
the outbound message mechanism to add information to the
outgoing response message. If you wish to change the response
message, you must use the regular reject function in the
OFFERING state.
RvSipCallLegSetForceOutboundAddrFlag()
You can use this function to force the call-leg to send every outgoing request to
the outbound address, regardless of the message content or object state.
EVENTS The Call-leg API supplies several events, in the form of callback functions, to
which your application may listen and react. In order to listen to an event, your
application should first define a special function called the event handler and
then pass the event handler pointer to the Call-legMgr. When an event occurs,
the call-leg calls the event handler function using the pointer.
The following events are supplied with the Call-leg API:
RvSipCallLegCreatedEv()
Notifies the application that a new incoming call-leg has been created. The
newly created call-leg always assumes the IDLE state. Your application can
exchange handles with the SIP Stack using this callback.
Note You must not terminate the call-leg from this event.
RvSipCallLegStateChangedEv()
This event is probably the most useful of the events that SIP call-leg reports.
Through this function, you receive notifications of SIP call-leg state changes
and the associated state change reason. For example, upon receipt of an
OFFERING state notification, your application may decide whether to accept or
reject the call.