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

46 HP-UX C SIP Stack Programmer’s Guide
Call-leg API
Persistency Definition and Used Connection
When working with TCP, the application can instruct the call-leg to try and send
all outgoing requests on one TCP connection. The application can also query the
call-leg about the connection used to send each request. For more information
on the persistency level and persistent connection API functions, see Persistent
Connection Handling of the Working with the Transport Layer chapter.
New Message Element Handles
Some of the call-leg fields are message parts. For example, the To header field is
a Party header object and the Local Contact field is a SIP address object. Before
setting a parameter of this type in the call-leg, you should request a new handle
for the parameter from the call-leg. After initializing the message part, you can
set it back in the call-leg.
CALL-LEG CONTROL The API functions that are listed below provide call-leg control.
B
ASIC FUNCTIONALITY The following API functions provide basic call-leg functionality:
RvSipCallLegMake()
After creating a call-leg, you can use this function to set the To and From
headers in the call-leg and send the INVITE request. This function receives the
To and From headers in a textual format.
RvSipCallLegConnect()
After creating a call-leg and setting the To and From headers, you can use
RvSipCallLegConnect() for generating and sending the required INVITE
message to connect the call.
RvSipCallLegAccept()
You can use RvSipCallLegAccept() in the OFFERING state to accept an
incoming call. You can also use this function to accept an incoming re-INVITE
request.
RvSipCallLegReject()
You can use RvSipCallLegReject() in the OFFERING state to reject an
incoming call. You can also use this function to reject an incoming re-INVITE
request.