Re: April CCXML: 4 issues w/7_2.txml - ISSUE-705 [cc]

This is tracked as ISSUE-705 
---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800

Come join us at our Voxeo Customer Summit
June 21st – June 23rd at the Hard Rock Hotel
Register today for your All Access Pass:  
http://www.voxeo.com/summits/customer




On May 14, 2010, at 9:38 AM, Chris Davis wrote:

> Hello www-voice,
> 
> 1)  note: dialogterminate has the immediate boolean/string problem
>  7.2.3.2 says of the immediate attribute that it is "An ECMAScript expression which returns a character string,"
>  It seems simpler for the "type" to be "ECMA script expression returning boolean", but that is not the way
>  things are currently written.
> 
> 2) <var name="paramcc3='Hello world'"/> should be
> <var name="paramcc3" expr="'Hello world'"/>
> 
>  As written, it causes ECMA errors
> 
> 3) When <dialogterminate> is called, the browser generates as a side effect conference.unjoined.
>    This is consistent with 7.2.3.1, which says:
>   "The platform MUST tear down any existing bridges to the dialog and send a conference.unjoined     to the CCXML document once the media paths have been freed."
>    The problem is that the script is not expecting this, and treats the conference.unjoined as an error
> 4) <dialogstart> has maxage/maxstale passed as integers not strings. A string result of the ECMA script expression
> is implied in  7.2.2.2 where it says "The character string returned must be interpreted as a time interval."
>   It seems simpler for the "type" to be "ECMA script expression returning integer", but that is not how it is written.
> 
> Regards,
> Chris
> 
> -- 
> Chris Davis
> Interact Incorporated R&D
> 512-502-9969x117
> 
> 
>

Received on Wednesday, 26 May 2010 05:10:46 UTC