RFC 3261 SIP headers

You can set a limited number of SIP headers independently for applications that initiate an outbound call with one of the following:

• A REFER as a result of a blind or consultative transfer

• An INVITE as a result of bridged transfer or a CCXML outbound call

  	Note:
  	Not all headers that are available to be set on an INVITE are available to be set on a REFER.

You can set the following headers with the VoiceXML <property> element before <transfer> element. In the table, <sip_prop> represents AVAYA_SIPHEADER.session.connection.protocol.sip.

	Note:
	If you want to set a header in your application, you must use the complete text in your code. For example, code <sip_prop>.callid as AVAYA_SIPHEADER.session.connection.protocol.sip.callid.

SIP Header	<property>	Notes
Call-Info	<sip_prop>.callinfo	Provides additional information about the source or target of the call, depending on whether it is found in a request or response.
To.displayname	<sip_prop>.to.displayname	Displays the name of the call’s target.
From.displayname	<sip_prop>.from.displayname	Displays the name of the call’s source.
P-asserted Identity	<sip_prop>.passertedid.displayname <sip_prop>.passertedid.uri	The unique identifier of the source sending the SIP message. This identifier is used for authentication purposes if your SIP configuration requires trusted connections. Note: If you define the P-Asserted-Identity parameter for the SIP connection through the EPM, Experience Portal ignores any attempt by an application to change this identity.
Subject	<sip_prop>.subject	A summary of the call.
Organization	<sip_prop>.organization	The name of the organization to which the SIP element issuing the request or response belongs.
Priority	<sip_prop>.priority	The priority of the request.