- From: RJ Auburn <rj@voxeo.com>
- Date: Mon, 27 Nov 2006 12:12:35 -0500
- To: "Hrvoje Nezic" <hrvoje.nezic@envox-lab.hr>
- Cc: <www-voice@w3.org>
Hrvoje, As the spec is currently written the assumption would be that you can NOT start dialogs that are detached from both Conference and Connection ID's. Do you have a use case that would require this functionality? If so it's something we could consider for future versions. Thanks, RJ --- RJ Auburn CTO, Voxeo Corporation tel:+1-407-418-1800 On Nov 27, 2006, at 11:58 AM, Hrvoje Nezic wrote: > 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! >
Received on Monday, 27 November 2006 17:13:57 UTC