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

Working with Register-Clients 133

The SIP Stack configuration determines the value of the timers and

retransmission count for all the SIP Stack transactions. The application can use

a set function to change the different timer values of the register-client

transactions. The application can also control the number of retransmissions

that the transactions perform.

Persistency Definition and Used Connection

When working with TCP, the application can instruct the register-client to try

and send all outgoing register requests on one TCP connection. The application

can also query the register-client about the connection used to send each request.

For more information on persistency level and Persistent Connection API

functions, see Persistent Connection Handling of the Working with the

Transport Layer chapter.

New Header Handles

Some of the register-client fields are message parts. For example, the To header

field is a Party header object and the Expires field is an Expires header object.

Before setting a parameter of this type in the register-client, you should request a

new handle for the given parameter from the register-client. After initializing

this parameter with your requested values, you can set the parameter back in the

CONTROL

The following API functions provide register-client control:

RvSipRegClientDetachFromMgr

Detaches a register-client from the Register-ClientMgr. By default, all the

Agent and therefore use the same Call-ID and an increased CSeq- Step. The

Call-ID and CSeq-Step are managed by the Register-ClientMgr. When

implementing a multi-user application, each register-client should have a

different Call-ID and should manage its own CSeq-step counting. Calling

RvSipRegClientDetachFromMgr() on a register-client will cause the register-

client to generate its own Call-ID and manage its own CSeq-Step counter.