Re: [CCXML] Query regarding <dialogstart> command - ISSUE-106 - ISSUE-229

Sajeesh,

The current version of the CCXML specification explicitly specifies the
rules for how attributes can be used on <dialogstart> when the
'prepareddialogid' is used.

In particular:

* The 'Attribute Constraints' column in 7.2.2.2 notes that src, type,
parameters, maxage, enctype, and method *cannot* be specified if
'prepareddialogid' is present.

* The description for connectionid and conferenceid explain the rules
for using these attributes in conjunction with 'prepareddialogid'.

The above are in addition to the constraint that you noted on
'mediadirection'.

At this point we consider this issue closed. If you disagree or have  
further comments on this item please contact us within 3 weeks so we  
can reopen in our issue database.

Best regards and thanks for the helpful review of the CCXML  
specification.

	RJ



On Feb 8, 2007, at 10:18 :31, RJ Auburn wrote:

>
> For your reference this is being tracked as ISSUE-106.
>
> 	RJ
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> tel:+1-407-418-1800
>
>
>
> On Feb 3, 2007, at 2:29 AM, Sajeesh wrote:
>
>> Hi,
>>
>>  In section 7.2.2.1 of W3C working draft for Voice browser call  
>> control - CCXML,  It says that
>>
>> "If the prepareddialogid attribute is specified and any attribute  
>> values  conflict with the values specified in the
>> <dialogprepare> element this  MUST result in the throwing of an  
>> error.dialog.notstartedevent"
>>
>> In this case, should we check all attributes of <dialogstart> like  
>> connectionid/conferenceid, maxage,
>> maxstale, enctype, method and hints against the corresponding  
>> <dialogprepare> command?
>>
>> Or only the checking of mediadiection (which is explicitly  
>> specified in CCXML draft) is enough?
>>
>> Regards,
>> Sajeesh
>>
>> ***************************************************************************************
>> This e-mail and attachments contain confidential information from  
>> HUAWEI, which is intended only for the person or entity whose  
>> address is listed above. Any use of the information contained  
>> herein in any way (including, but not limited to, total or partial  
>> disclosure, reproduction, or dissemination) by persons other than  
>> the intended recipient's) is prohibited. If you receive this e-mail  
>> in error, please notify the sender by phone or email immediately  
>> and delete it!
>>
>
>