Re: July CCXML Implementation Report: number of connection.merged events - ISSUE-723


We are in the process to address all ISSUES related to IR. The goal is to finalize the test-suite during the PR transition.
Please explicitly confirm that you accept the proposed resolution or after one week we will consider it implicitly accepted.
If you need clarifications, please ask them very soon.

Paolo Baggia
Author of CCXML-IR Plan


For interoperability reasons it will be fixed by adding a 'connection.merged' transition.

From: RJ Auburn <> 
Date: Thu, 29 Jul 2010 10:08:54 -0400
Cc: www-voice <>, W3C Voice Browser Working Group <> 
Message-Id: <> 
To: Petr Kuba <> 


This is also tracked as ISSUE-723. (same issue ID as your prior email on July 2nd).


On Jul 26, 2010, at 5:30 AM, Petr Kuba wrote:

> Hello www-voice,
> Tests 10_2_2_A, assertion 283, and 10_2_3, assertion 1295 suffer the same problem:
> They expect only one connection.merged event but according to the specification there must be two events thrown (one on each of the two calls affected by a merge). The tests get confused by the second connection.merged event which results in false FAILs being reported.
> I've already recommended to changed the specification to generate only one connection.merged but I'm still waiting for an answer. See here:
> Either the specification or the tests must be changed in this issue.
> Thanks,
> Petr
> -- 
>  Petr Kuba, Project Manager
>  OptimSys, s.r.o
>  Tel: +420 541 143 065
>  Fax: +420 541 143 066

Received on Thursday, 19 August 2010 09:30:17 UTC