Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sip_create_dialog_req_nocontact(3sip) [opensolaris man page]

sip_create_dialog_req(3SIP)			   Session Initiation Protocol Library Functions		       sip_create_dialog_req(3SIP)

NAME

       sip_create_dialog_req, sip_create_dialog_req_nocontact - create an in-dialog request

SYNOPSIS

       cc [ flag ... ] file ... -lsip [ library ... ]
       #include <sip.h>

       sip_msg_t sip_create_dialog_req(sip_method_t method,
	    sip_dialog_t dialog, char *transport, char *sent_by,
	    int sent_by_port, char *via_param, uint32_t smaxforward,
	    int cseq);

       sip_msg_t sip_create_dialog_req_nocontact(sip_method_t method,
	    sip_dialog_t dialog, char *transport, char *sent_by,
	    int sent_by_port, char *via_param, uint32_t smaxforward,
	    int cseq);

DESCRIPTION

       The  sip_create_dialog_req()  function  creates and returns a SIP request with the state information contained in dialog. The method in the
       resulting request is from method. The method can be one of the following:
	 INVITE
	 ACK
	 OPTIONS
	 BYE
	 CANCEL
	 REGISTER
	 REFER
	 INFO
	 SUBSCRIBE
	 NOTIFY
	 PRACK

       The resulting request line in the SIP message has the SIP-Version of "2.0". The URI in the request line is from the remote  target  in  the
       dialog  or  from  the  route  set in the dialog, if present. See RFC 3261 (section 12.2) for details. The FROM, TO, and CALL-ID headers are
       added from the dialog. The MAX-FORWARDS header is added using the value in maxforward. The CSEQ header is added using  the  SIP	method	in
       method  and the sequence number value in cseq. If cseq is -1, the sequence number is obtained from the local sequence number in the dialog.
       The local sequence number in the dialog is incremented and is used in the CSEQ header. The VIA header added is created using the transport,
       sent_by,  sent_by_port  (if non-zero), and via_param (if any). If dialog has a non-empty route set, the resulting SIP request has the route
       set from the dialog.

       The sip_create_dialog_req_nocontact() function is similar to sip_create_dialog_req(), except that it does not add the contact header.

RETURN VALUES

       The sip_create_dialog_req() and sip_create_dialog_req_nocontact() functions return the resulting SIP message on success and NULL  on  fail-
       ure.

       The value of errno is not changed by these calls in the event of an error.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Committed 		   |
       +-----------------------------+-----------------------------+
       |MT-Level		     |MT-Safe			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       libsip(3LIB), attributes(5)

SunOS 5.11							    6 Aug 2007					       sip_create_dialog_req(3SIP)

Check Out this Related Man Page

sip_create_response(3SIP)			   Session Initiation Protocol Library Functions			 sip_create_response(3SIP)

NAME

       sip_create_response - create a response for a SIP request

SYNOPSIS

       cc [ flag ... ] file ... -lsip [ library ... ]
       #include <sip.h>

       sip_msg_t sip_create_response(sip_msg_t sip_request,
	    int response_code, char *response_phase,
	    char *totag, char *contact_uri);

DESCRIPTION

       The  sip_create_response()  function creates and returns a SIP message in response to the SIP request sip_request. The response line in the
       resulting SIP message is created using the response code in response_code and the phrase in response_phrase. The response line has the SIP-
       Version	of  "2.0".  If	a non-null totag is specified, the resulting SIP response has a TO header with a tag value from totag. If totag is
       null and the response_code is anything other than 100 (TRYING), sip_create_response() adds a TO header with a randomly generated tag value.
       If the response_code is 100 and totag is null, the SIP response has a TO header without a tag parameter. If contact_uri is non-null, a CON-
       TACT header is added to the SIP response with the URI specified in contact_uri. The SIP response has  the  following  headers  copied  from
       sip_request:
	 All VIA headers
	 FROM header
	 TO header (with tag added, if required, as stated above)
	 CALL-ID header
	 CSEQ header
	 All RECORD-ROUTE headers

RETURN VALUES

       The sip_create_response() function returns the resulting SIP message on success and NULL on failure.

       The value of errno is not changed by these calls in the event of an error.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Committed 		   |
       +-----------------------------+-----------------------------+
       |MT-Level		     |MT-Safe			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       libsip(3LIB)

SunOS 5.11							    25 Jan 2007 					 sip_create_response(3SIP)
Man Page