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

Event Notification 237

Subscription API

State

Indicates the state of the subscription setup between two SIP User Agents. You

can only access the state parameter with a Get function and it is not modifiable.

Subscription Type

Indicates whether the subscription represents the subscriber or notifier side of

the subscription. You can only access the type parameter with a Get function

and it is not modifiable.

Event Package Type

The type of event package of a subscription.

Reject Status Code On Creation

You can set the “reject status code on creation” parameter to automatically reject

the request that created this subscription. If you set this status code, the

subscription will be destructed automatically when the RvSipSubsCreatedEv()

callback returns. You will not get any further callbacks that relate to this

subscription (you will not get the RvSipSubsMsgToSendEv() for the reject

response message or the TERMINATED state for the subscriptions). This

parameter should not be used for rejecting a request in a normal scenario. For

this you should use the RvSipSubsRespondReject() function. You should use

this function only if your application is incapable of handling this new

subscription at all, for example, if the application is out of resources.

Remark: 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 RVSIP_SUBS_STATE_SUBS_RCVD state.

SUBSCRIPTION

ONTROL

The following API functions provide subscription control:

RvSipSubsInit()

After creating a subscription, you can use this function to set the To, From and

Event headers, and the Expires header value in the subscription. If the

subscription was created within an existing call-leg, you should not set the To

and From parameters.