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_sendmsg(3SIP)				   Session Initiation Protocol Library Functions				 sip_sendmsg(3SIP)

NAME

       sip_sendmsg - send an outbound SIP message to the SIP stack for processing

SYNOPSIS

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

       int sip_sendmsg(sip_conn_object_t obj, sip_msg_t sip_msg,
	    sip_dialog_t dialog, uint32_t flags);

DESCRIPTION

       The  sip_sendmsg()  function is used to send an outbound SIP message sip_msg to the SIP stack on its way to the peer. The connection object
       for the SIP message is passed as obj. The caller also provides the dialog associated with the message, if one exists. The value of flags is
       the result of ORing the following, as required:

       SIP_SEND_STATEFUL     Send  the	request  or response statefully. This results in the stack creating and maintaining a transaction for this
			     request/response. If this flag is not set transactions are not created for the request/response.

       SIP_DIALOG_ON_FORK    When this flag is set, the stack may create multiple dialogs for a dialog completing response. This may result due to
			     forking of the dialog creating request. If this flag is not set, the first response to a dialog creating request cre-
			     ates a dialog, but subsequent ones do not. It is only meaningful if the stack is configured to maintain dialogs.

RETURN VALUES

       The sip_sendmsg() function returns 0 on success and the appropriate error on failure.

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

ERRORS

       The sip_sendmsg() function can return one of the following errors on failure:

       EINVAL	 If a message is being statefully sent and the branchid in the VIA header does not conform to RFC  3261  or  when  accessing  CSEQ
		 header while creating a transaction.

       ENOENT	 If a message is being statefully sent, error getting the CSEQ header while creating a transaction.

       EPROTO	 If a message is being statefully sent, error getting the CSEQ value while creating a transaction.

       ENOMEM	 If  the  message  is  being  statefully  sent, error allocating memory for creating or adding a transaction or during transaction
		 related processing.

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_sendmsg(3SIP)
Man Page