JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SIP API Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  SIP Overview

2.  Oracle Solaris SIP Internals

3.  Multithreading and URI Support

4.  SIP API Functions

Stack Initialization Function

Message Allocation Functions

SIP Header Addition Functions

SIP Request and Response Creation Functions

Header and Message Copying Functions

Header and Value Deleting Functions

Header Lookup Functions

Value Retrieval and Response Description Functions

SIP ID Generating Functions

VIA Functions

SIP Message Sending Function

Processing Inbound Messages

Transaction Layer Functions

Dialog Layer Functions

URI Functions

SIP Header Value Retrieval Functions

Connection Object Functions

Miscellaneous Functions

A.  Examples of Use

B.  Programming with the SIP API

C.  Transaction Timers


Stack Initialization Function

int sip_stack_init(sip_stack_int_t *stack_init);

This function initializes the SIP stack. This is the stack initialization structure:

typedef struct sip_stack_init_s {
        int                     sip_version;
        uint32_t                sip_stack_flags;
        sip_io_pointers_t       *sip_io_pointers;
        sip_ulp_pointers_t      *sip_ulp_pointers;
        sip_header_function_t   *sip_function_table;

The structure has the following elements:


The value of this variable is equal to the value of the SIP_STACK_VERSION attribute.


Set the value of this variable to SIP_STACK_DIALOGS to make the stack manage dialogs.


The values in this field provide the connection manager interfaces.


The values in this field contain the upper layer registrations. Upper layer registrations are functions that the application must register with the stack during initialization.


The values in this field are the custom headers that the application registers and the parsing functions that are associated with those headers. The application can specify the following elements for each custom header:

  • header_name

  • header_short_name (optional)

  • header_parse_func

  • header_check_compliance (optional)

  • header_is_equal (optional)

  • header_free