CCXML 1.0-W3C Development Guide

<meta> element

The <meta> element functions in CCXML 1.0 as it does in HTML. It denotes meta information about the document, and its http headers. Note that cache-control is ignored; see our documentation on caching, and how to control it.

usage

attributes

content	Data Type: CDATA	Default: Required
	The content attribute specifies the value of the metadata property.
http-equiv	Data Type: NMTOKEN	Default: Optional
	The http-equiv attribute specifies the name of the HTTP response header that should be honored for a specified VoiceXML document. Note that this will not affect the caching of vxml documents on the platform; caching should be controlled at the server level, as detailed in the caching tutorial. Either the http-equiv or the name attribute is required, but do not specify both or you will get a compile error.
name	Data Type: NMTOKEN	Default: Optional
	The name attribute specifies the name of the meta-data property. The more commonly used properties are: Author: information about the author Copyright: copyright information Description: description of the document for search engines Keywords: keywords describing the document Maintainer: document maintainer’s email address Robots: directives to search engine robots Either the http-equiv or the name attribute is required, but do not specify both or you will get a compile error. If you need to retrieve the SIP body and associated content type for the last received body, you can implement the following Voxeo-specific `sip.body` parameter for this attribute: `<meta name="sip.body" content="true"/>` where the `content` parameter is a Boolean to enable or disable retrieval of the SIP body. `protocol.sip.body` is an array of body messages with the following properties: `contenttype contentdata` The SIP body is only on the protocol object for the event and not the protocol on the global connection object (under session.connections). Search for "application/gtd" to find the UUI payload in the logs. After SIP body retrieval, you can use a java script, for example, to extract the data fields required as shown in the second code example below.

parents

none

children

none

code samples

<1.0 metadata>

<?xml version="1.0" encoding="UTF-8"?>
<ccxml version="1.0" xmlns="http://www.w3.org/2002/09/ccxml">

<meta name="author" content="Jeff Menkel"/>
<meta name="copyright" content="2007 Voxeo Corporation"/>
<meta name="keywords" content="ccxml meta"/>
<meta name="maintainer" content="YOUR_EMAIL@HERE.COM"/>

<var name="algore" expr="''"/>
<var name="statevar" expr="'state0'"/>

<eventprocessor statevariable="statevar">

<transition state="state0" event="connection.alerting">
<accept/>
<log expr="'***** Answering the Call *****'"/>
<assign name="statevar" expr="'state1'"/>
</transition>

<transition state="state1" event="connection.connected">
<assign name="algore" expr="'I invented the intarweb!!!'"/>
<log expr="'*** Al Gore says: ' + algore + ' ***'"/>
<exit/>
</transition>

<transition event="error.*">
<log expr="'Well, it didn't work because: '+ event$.reason + '. I demand a recount!'"/>
<exit/>
</transition>
</eventprocessor>

</ccxml>

<1.0 sip.body> sample

<?xml version="1.0" encoding="UTF-8"?>
<ccxml version="1.0" xmlns:voxeo="http://community.voxeo.com/xmlns/ccxml">
<meta name="sip.body" content="true"/>
<var name="state0" expr="'init'"/>
<eventprocessor statevariable="state0">
<transition event="connection.alerting">
<log expr="'body='+JSON.stringify(event$.connection.protocol.sip.body)"/>
</transition>
...

additional links

none

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page