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

Working with Transactions 93

Transaction API

TRANSACTION

ARAMETERS

You can set or examine transaction parameters via transaction Set and Get API

functions. The following parameters are available:

To Header, From Header, Call-ID and CSeq

When creating a client transaction, you must set the To and From headers of the

transaction. The Call-ID and CSeq are optional. You can either set them, or the

SIP Stack will generate them for you.

Method

Specifies the method of the SIP request. For client transactions, you supply the

method when calling the RvSipTransactionRequest() API function. For server

transactions you can only access the method parameter with a Get function and

the parameter is not modifiable.

Local Address

Defines the address from where the transaction will send the request (the

network card). This is also the address that will be placed in the top Via header

of a Request message. If the local address is not set, the transaction will use a

default local address according to the SIP Stack configuration.

Outbound Details

Addressing details of an outbound proxy that the transaction should use. The

outbound address is used only if the transaction sends a Request message. In

this case, the transaction will use the outbound address as a remote address and

the Request-URI will be ignored. The outbound address of the transaction is

ignored if the request contains a Route header, or if the

RvSipTransactionIgnoreOutboundProxy() function was called. You can force

the usage of the outbound proxy regardless of the message content by calling the

RvSipTransactionSetForceOutboundAddrFrag() function.

Received Message

The last message (Request or Response) that was received by the transaction.

You can get this message only in the context of the transaction state-changed

callback function when the new state indicates that the transaction received a

new message.