Sessions

A CCXML session is one instance of the CCXML browser. At any given point in time, a session will be interpreting a single CCXML document, but it can switch to interpret another. All events for a CCXML session are queued on to a single queue. The session processes one event at a time. One or more CCXML sessions can be running concurrently on a Blueworx Voice Response for AIX system. The multiple sessions could all be interpreting the same document, or they could all be interpreting different documents, or some could be interpreting the same document while others were interpreting different documents.

CCXML browser sessions can either run on the Blueworx Voice Response Java and VoiceXML environment voice response node — on the system that includes the Blueworx Voice Response telephony — or they can run in application nodes, either on the system that includes the Blueworx Voice Response telephony or on a remote system. For detailed information on configuring your system and running applications, refer to Blueworx Voice Response for AIX: Deploying and Managing VoiceXML and Java Applications.

A CCXML session can be started by:

• A new incoming telephone call. (This is mediated by the Blueworx Voice Response Java and VoiceXML environment)

  ccxml.loaded events for such sessions have the parent attribute set to a value of undefined.

• A CCXML application executing a <createccxml> element to initiate a new CCXML session.

  ccxml.loaded events for such sessions have the parent attribute set to the value of the sessionid attribute of the <createccxml> element.

A session can exist without any associated connections. The execution of <createcall> or <move> elements, or an incoming telephone call can create representations of connections in an empty session.

A session can contain multiple sequential and⁄or concurrent connections. Associated connections can be moved from one session to another by the execution of a <move> element.

A CCXML session is ended by one of the following:

• A CCXML application executing an <exit> element.
• An unhandled error.* event.
• An unhandled ccxml.kill event.
• A ccxml.kill.unconditional event.

When a session ends, all active connections and dialogs or other resources that are owned by that session are automatically terminated. A session does not end when a connection terminates.