Re: CCXML: question on assertion for 7_3 #427 - ISSUE-771

Yes, this works for me. With the change to the test-suite you can now 
close this issue.

Regards,
Chris

On 03/30/2011 03:40 AM, Baggia Paolo wrote:
> Chris,
>
> You recently raised the ISSUE-771. The goal is to close all changes to 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.
>
> Regards,
> Paolo Baggia
> Author of CCXML-IR Plan
>
> ISSUE-771:
>
> Your request has been accepted. We did a minor change to avoid customization in the transfer destination for conference test. See the attached document. Please explicitly confirm that you accept the change.
>
> =================================
> From: RJ Auburn<rj@voxeo.com>
> Date: Thu, 24 Mar 2011 11:26:19 -0400
> Cc: www-voice<www-voice@w3.org>, kuba@optimsys.cz, paolo.baggia@loquendo.com
> Message-Id:<266C0273-6556-4FDA-898F-95B0C472A12E@voxeo.com>
> To: Chris Davis<davisc@iivip.com>
>
> This is tracked as ISSUE-771
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> tel:+1-407-418-1800
> skype:zscgeek
>
> On Mar 16, 2011, at 12:43 PM, Chris Davis wrote:
>
>> Hello www-voice,
>>
>> In assertion #427 the caller is required to hit a DTMF digit to make a VoiceXML dialog
>> terminate its<transfer>  tag.
>>
>> The problem is that I cannot see from the 7_3.txml how the DTMF is supposed to make it
>> to the VoiceXML dialog.
>>
>> The caller is switched full duplex to a conference as part of the ASSERTION_NMBR_427
>> transitions. The<join>  for this does not have the dtmfclamp attribute set to false, so by
>> default his DTMF won't make it to other conference mixers.
>>
>> The VoiceXML dialog is receiving signal from the conference, not the caller. Because the
>> DTMF is clamped from the caller in<transition event="conference.joined" state="ASSERTION_NMBR_427">
>> the VoiceXML will never receive signal.
>>
>> I can make our integration pass the assertion only if I change the caller's<join>  to specify noclamping
>> via:
>> <join id1="ConnectionID" id2="ConferenceID" duplex="'full'" dtmfclamp="false"/>
>> as part of the<transition event="conference.joined" state="ASSERTION_NMBR_427">.
>>
>> Does the test need changing or am I missing something?
>>
>> Regards,
>> Chris
>>
>> -- 
>> Chris Davis
>> Interact Incorporated R&D
>> 512-502-9969x117


-- 
Chris Davis
Interact Incorporated R&D
512-501-2692

Received on Wednesday, 30 March 2011 13:31:32 UTC