Edit comment LC-1685 for Voice Browser Working Group

Quick access to LC-1667 LC-1668 LC-1669 LC-1670 LC-1671 LC-1672 LC-1673 LC-1674 LC-1675 LC-1676 LC-1677 LC-1678 LC-1679 LC-1683 LC-1684 LC-1685 LC-1687 LC-1688 LC-1689

Comment LC-1685

Comment Shortname:

Commenter: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeVoice Browser Call Control: CCXML Version 1.0 /**/ /... Voice Browser Call Control: CCXML Version 1.0 W3C Working Draft 19 January 2007 Abstract Status of this Document Conventions of this Document Table of Contents 1: Introduction 2: Motivation (Informative) 3: Concepts and Architecture CCXML Session: A CCXML session is comprised of an executing... Connection: Connections can be "call legs" (real-world phone... Conference object: A Conference Object models a resource for... Dialog: When active, a Dialog may interact with other Connec... 3.1: Event Processing 3.2: Conferencing 3.3: Scripting 3.4: Definitions CCXML Application/Program - A collection of CCXML documents... CCXML Interpreter - The software that processes CCXML docume... CCXML Platform - An implementation of CCXML for a specific n... 3.5: Session Life-Cycle 3.5.1: Startup 3.5.2: Shutdown 3.5.3: Session Life-Cycle Diagrams 3.5.3.1: session can live before and after active connections (or no connections at all) 3.5.3.2: connection life shorter than session 3.5.3.3: session ends, kills all active connections 3.5.3.4: session can have multiple sequential connections 3.5.3.5: session can have multiple sequential connections and multiple concurrent connections 3.5.3.5: move a connection to a newly created session 3.5.3.7: move a connection to a "master" session 3.5.3.8: optional "master" session for inbound call handling 3.5.3.9: ccxml.kill.unconditional event raised 3.5.3.10: Normal session shutdown requested by the platform 4: Simple Examples 4.1: Hello World 4.2: Accept or Reject a Call 4.3: Simple Dialog dialog.ccxml: dialog.vxml: 5: CCXML Elements Listing 6: Document Control Flow and Execution 6.1: Overview 6.2: Elements 6.2.1: <ccxml> 6.2.1.1: Overview 6.2.1.2: <ccxml> Attribute Details 6.2.2: <meta> 6.2.2.1: Overview <meta> 6.2.2.2: <meta> Attribute Details 6.2.3: <metadata> 6.2.3.1: Overview <metadata> 6.2.3.2: <metadata> Attribute Details 6.2.4: <if> 6.2.4.1: Overview 6.2.4.2: <if> Attribute Details 6.2.5: <elseif> 6.2.5.1: Overview 6.2.5.2: <elseif> Attribute Details 6.2.6: <else> 6.2.6.1: Overview 6.2.6.2: <else> Attribute Details 6.2.7: <fetch> 6.2.7.1: Overview 6.2.7.2: <fetch> Attribute Details 6.2.8: <goto> 6.2.8.1: Overview 6.2.8.2: <goto> Attribute Details 6.2.8.3: <fetch> and <goto> Example 6.2.9: <createccxml> 6.2.9.1: Overview 6.2.9.2 <createccxml> Attribute Details 6.2.10: <exit> 6.2.10.1: Overview 6.2.10.2 <exit> Attribute Details 6.2.11: <log> 6.2.11.1: Overview 6.2.11.2 <log> Attribute Details 6.3: Events 6.3.1: Overview 6.3.2: fetch.done - Fetch Completion Event 6.3.3: error.fetch - Fetch Error Event 6.3.4: ccxml.exit - CCXML Document Exit Event 6.3.5: ccxml.loaded - CCXML Document Loaded Event 6.3.6: ccxml.kill - CCXML kill Event 6.3.7: ccxml.created - CCXML Session Create Completion Event 6.3.8: error.createccxml - CCXML Session Create Failed Event 6.3.9: error.unsupported - CCXML Unsupported Operation 7: Dialogs 7.1: Overview 7.2: Elements 7.2.1: <dialogprepare> 7.2.1.1: Overview 7.2.1.2: <dialogprepare> Attribute Details 7.2.2: <dialogstart> 7.2.2.1: Overview 7.2.2.2: <dialogstart> Attribute Details 7.2.3: <dialogterminate> 7.2.3.1: Overview 7.2.3.2: <dialogterminate> Attribute Details 7.3: Events 7.3.1: Overview 7.3.2: dialog.started 7.3.3: dialog.exit 7.3.4: dialog.disconnect 7.3.5: dialog.transfer 7.3.6: dialog.terminatetransfer 7.3.7: error.dialog 7.3.8: error.dialog.notstarted 7.3.9: blank 7.3.10: dialog.user.* 7.3.11: dialog.prepared 7.3.12: error.dialog.notprepared 7.4: Dialog Object Properties 7.5: Dialog class 8: Variables and Expressions 8.1: Overview 8.2: Elements <assign> <var> 8.2.1.1: Overview 8.2.1.2: <var> Attribute Details 8.2.1.3: <assign> Attribute Details 8.2.2: <script> 8.2.2.1: Overview 8.3: Session Variables 8.4: Application Variables 9: Event Handling 9.1: Overview 9.2: Elements 9.2.1: <eventprocessor> 9.2.1.1: Overview 9.2.1.2: <eventprocessor> Attribute Details 9.2.2: <transition> 9.2.2.1: Overview 9.2.2.2: <transition> Attribute Details 9.2.2.3: <transition> Event Matching 9.2.3: <send> 9.2.4: <move> 9.2.4.1: Overview 9.2.4.2: <move> Attribute Details 9.2.5: <cancel> 9.2.5.1: Overview 9.2.5.2: <cancel> Attribute Details 9.3: Events 9.3.1: error.notallowed 9.3.2: error.semantic 9.3.3: error.send.targetunavailable 9.3.4: error.send.targettypeinvalid 9.3.5: error.send.failed 9.3.6: send.successful 9.3.7: move.successful 9.3.8: cancel.successful 9.3.9: error.move 9.4: Standard Events 9.4.1: Overview 9.4.2: Standard Event Attributes 9.4.2.1: Overview 9.4.2.2: Standard Event Attribute Table 9.4.3: Connection Events 9.4.3.1: Overview 9.4.4: Language Events 9.4.5: Error Events 9.4.5.1: Overview 9.5: Error Handling 9.5.1: Fetching & compilation errors 9.5.2: Document Initialization Errors 9.5.3: Error In <eventprocessor> attributes 9.5.4: Error in <transition> attributes 9.5.5: Errors While Handling Error Events 10: Telephony Operations and Resources 10.1: Overview 10.1.1 Concepts Background (INFORMATIVE) 10.2 Connections 10.2.1: Connection State 10.2.2: Connection Object 10.2.3: Connection Events 10.2.4: Connection Operations 10.2.5: Connection Class 10.3: Conferences 10.3.1: Conference Object Properties 10.3.2: Conference class 10.4: Bridges 10.4.1: <join> Outcomes 10.4.2: Invariant Examples 10.4.3: Media Endpoint Properties 10.5: Elements 10.5.1: <accept> 10.5.1.1: Overview 10.5.1.2: <accept> Attribute Details 10.5.2: <redirect> 10.5.2.1: Overview 10.5.2.2: <redirect> Attribute Details 10.5.3: <reject> 10.5.3.1: Overview 10.5.3.2: <reject> Attribute Details 10.5.4: <createcall> 10.5.4.1: Overview 10.5.4.2: <createcall> Attribute Details 10.5.4.3: <createcall> examples 10.5.5: <createconference> 10.5.5.1: Overview 10.5.5.2: <createconference> Attribute Details 10.5.6: <destroyconference> 10.5.6.1: Overview 10.5.6.2: <destroyconference> Attribute Details 10.5.7: <join> 10.5.7.1: Overview 10.5.7.2: <join> Attribute Details 10.5.8: <unjoin> 10.5.8.1: Overview 10.5.8.2: <unjoin> Attribute Details 10.5.9: <disconnect> 10.5.9.1: Overview 10.5.9.2: <disconnect> Attribute Details 10.5.10: <merge> 10.5.10.1: Background 10.5.10.2: Overview 10.5.10.3: <merge> Attribute Details 10.6: Events 10.6.1: Overview 10.6.2: connection.alerting 10.6.3: connection.progressing 10.6.4: connection.connected 10.6.5: connection.disconnected 10.6.6: connection.redirected 10.6.7: connection.merged 10.6.8: connection.failed 10.6.9: error.connection 10.6.10: connection.signal Section 10.6.11: conference.created Section 10.6.12: conference.destroyed Section 10.6.13: conference.joined Section 10.6.14: conference.unjoined Section 10.6.15: error.conference.create Section 10.6.16: error.conference.destroy Section 10.6.17: error.conference.join Section 10.6.18: error.conference.unjoin 10.6.19: connection.merge.failed 10.6.20: error.connection.wrongstate 10.6.21: error.conference 10.6.22: connection.redirect.failed 10.6.23: connection.accept.failed 10.6.24: connection.reject.failed 11: Complex Examples 11.1: Calling Card Application calling_card.ccxml pin.vxml error.vxml callee.vxml VXML page returned by checktime.asp 11.2: Conferencing application First page to all callers CCXML page returned by conference.asp to first callers browser CCXML page returned by conference.asp to all subsequent callers vconference.asp newcaller.vxml leave.vxml CCXML page returned by teardown.asp to all but the last participant CCXML page returned by teardown.asp to last participant 11.3: Personal Assistant main.ccxml welcome_message.vxml outbound_greetings.vxml vm.vxml connecting.vxml holdmusic.vxml Appendix A - Related Work CPL CallXML ECMA-CSTA TXML SIP Appendix B - CCXML DTD Appendix C - CCXML XML Schema Appendix D - VoiceXML 2.0 Integration Details D.1 Overview D.2 Events D.3 VoiceXML Session Variables D.4 CCXML <dialogprepare> D.5 CCXML <dialogstart> D.6 CCXML <dialogterminate> D.7 VoiceXML <exit> D.8 VoiceXML <disconnect> D.9 VoiceXML <transfer> dialog.transfer.complete dialog.terminatetransfer D.10 User Disconnect D.11 VoiceXML 2.0 Example Appendix E - Telephony Protocol Names Overview Protocol names Appendix F - Changes Changes in Working Draft 2 Changes in Working Draft 3 Changes in Last Call Working Draft Changes in Last Call Working Draft 2 Changes in Last Call Working Draft 3 Changes in Working Draft 7 Changes in Last Call Working Draft 4 Appendix G - Acknowledgments Appendix H - References [CSTA] [IANA] [JSR021] [MIME-TAG] [RFC2119] [RFC3261] [RFC2806] [S.100] [SALT] [VOICEXML] [XML] [Q.931/DSS1] [SS7] [ECMAScript] [ECMA327] [XMLNS] [XML-BASE] [HTML] [RDF-SYNTAX] [RDF-SCHEMA] [DC] [SCHEMA2] [RFC2396] [RFC2732] [RFC3023] [CSS2] [RFC2119] [H.323] [CALLXML] [TXML] [RFC2616] [RFC2617] [RFC2109] [RFC4267] Appendix J - Conformance J1. Conforming CCXML Document J2. Using CCXML with other namespaces J3. Conforming CCXML Processors Appendix K - Basic HTTP Event I/O Processor K.1 Overview K.2 Access URI K.3 Receiving Events K.4 Sending Events Appendix L - Session Creation Event I/O Processor L.1 Overview L.2 Access URI L.3 Receiving Session Creation Events
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Comment:

Dear group,

I would highly appreciate if someone would clarify usage of connectionid and conferenceid
attributes of <startdialog> element.

The question is:
Is it possible to start a dialog which is not joined with a connection or a conference, and join the dialog later by an explicit <join>?

The specification states the following:

"If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter must use the id as specified on the dialogprepare element.
If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter must use the id indicated in the current event being processed."

But specification doesn't say what happens if the current event is not a connection or conference event, and so doesn't have a connection or conference id. Is it an error, or is it allowed, meaning that the dialog is not joined with a connection or conference?

Thanks!

Related issues: (space separated ids)

WG Notes: http://lists.w3.org/Archives/Public/www-voice/2006OctDec/0059.html http://lists.w3.org/Archives/Public/www-voice/2006OctDec/0062.html

Resolution:

(Please make sure the resolution is adapted for public consumption)