Partager via

2.2.20 Call Context Syntax

  • Article

This section follows the product behavior described in endnote <14>.

This section describes the call context syntax that can be used by SIP elements to convey notes about the current call or the call being transferred. The call context description is delivered as application/ms-conversation-context+xml content in the body of a SIP INVITE request to initiate a new call.

  <xs:complexType name="XmlConvContextType" >
    <xs:sequence>
      <xs:element name="id" type="xs:token"  minOccurs="1" maxOccurs="1"/>
      <xs:element name="from" type="callctns:XmlConvContextParticipantType" minOccurs="1" maxOccurs="1"/>      
      <xs:element name="to" type="callctns:XmlConvContextParticipantType" minOccurs="1" maxOccurs="1"/>      
      <xs:element name="participants" type="callctns:XmlConvContextParticipantCollectionType" minOccurs="1" maxOccurs="1" />
      <xs:element name="date" type="xs:dateTime" minOccurs="1" maxOccurs="1"/>
      <xs:element name="mode" type="xs:token" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="conversationId" type="xs:token" minOccurs="1" maxOccurs="1"/>
      <xs:element name="dataFormat" type="xs:string" minOccurs="1" maxOccurs="1"/>
      <xs:element name="contextData" type="xs:string" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
  </xs:complexType>

The complete schema is defined in section 8.

The call context content type provides notes about the current call from a server to a protocol client. The call context MUST contain the elements specified in sections 2.2.20.1 through 2.2.20.9, and can contain additional elements specified in section 2.2.20.10.