HP-UX C SIP Stack Programmer's Guide (February 2008)

128 HP-UX C SIP Stack Programmer’s Guide
Using Transactions
UA2 receives two INVITE requests with same request
identifiers, but with different Via headers.
2. UA2 handles the first INVITE request as usual—it creates a
call-leg in the OFFERING state, and waits for the application
decision of whether to accept or reject this request.
3. UA2 discovers that the second INVITE request has the same
request identifiers, and therefore rejects it with 482.
4. UA2 accepts the call-leg, and sends a 200 response on the first
request message.
5. Proxy1, receiving both 482 and 200 responses, forwards the
200 response to UA1.
D
ISABLING MERGING
S
UPPORT
The SIP Stack supports merging behavior by default. However, applications
may choose to disable the merging behavior. In this case, all INVITE requests
will be handled in the same way—server transactions will be created and passed
over to call-leg handling, even though they were all caused by the same initial
INVITE request.
The following new configuration parameter is supplied for this purpose:
bDisableMerging
Defines whether or not to activate the merging support. If RV_FALSE, the
merging behavior is enabled. If RV_TRUE, the merging behavior is disabled.
The default value is RV_FALSE.