2.2.9 Routing Script Preamble Syntax

  • Article

This section specifies the syntax of the routing preamble published by the protocol client in the routing category. The complete schema is defined in section 6.

  <xs:complexType name="routing-type">
    <xs:annotation>
      <xs:documentation>The name and version attributes are both mandatory.         </xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="preamble" type="tns:preamble-type" minOccurs="1" maxOccurs="1"/>
    </xs:sequence>
    <xs:attribute name="name" type="xs:string" />
    <xs:attribute name="version" type="xs:integer" />
    <xs:attribute name="minSupportedClientVersion" type="xs:string" use="optional" />
  </xs:complexType>
  <xs:element name="routing" type="tns:routing-type" />

The routing preamble MUST contain the identification attributes specified in section 2.2.9.1, and MUST contain the preamble element. The preamble provides the data used by the server while routing audio calls sent to the protocol client. The preamble can contain additional elements specified in sections 2.2.9.3 through 2.2.9.5.

If the value of the version attribute is 1, the minSupportedClientVersion attribute SHOULD NOT be present.<7>

The minSupportedClientVersion attribute, if present, SHOULD be ignored while processing an incoming INVITE request. In addition any unknown element or attribute SHOULD be ignored while processing an incoming INVITE request.<8>