W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2008

Re: <disconnect/> on outbound call - ISSUE-524

From: RJ Auburn <rj@voxeo.com>
Date: Wed, 19 Nov 2008 09:42:41 -0500
Cc: ranjit@huawei.com, www-voice@w3.org, 'W3C Voice Browser Working Group' <w3c-voice-wg@w3.org>
Message-Id: <95474017-7818-424D-A8B9-212D251FEC83@voxeo.com>
To: rethishkumarps@huawei.com
Rethish,

We actually updated the diagram to correct this. The new version is  
attached.

can you please let us know if there are any future issues?

Best regards,

	RJ

---
RJ Auburn
CTO, Voxeo Corporation
Chair, Editor and Chair, CCXML, VBWG, W3C


On Nov 18, 2008, at 11:14 PM, Rethish wrote:

>
>
> Dear RJ,
>
> I agree with the decision to generate 'connection.disconnected' if
> <disconnect> is used to abandon an outbound call,
>
> But I still find an ambiguity in the below case:
>
> 10.2.1: Connection State:
>   The figure illustrates that a connection.disconnected in PROGRESSING
> state transitions to ' FAILED ' state.
>    But, the table below this mentions that when a  
> connection.disconnected
> in PROGRESSING or CONNECTED  state it transitions to ' DISCONNECTED  
> 'state."
> 	
> Thanks & regards
> Rethish
>
>
> -----Original Message-----
> From: RJ Auburn [mailto:rj@voxeo.com]
> Sent: Thursday, November 13, 2008 21:42
> To: ranjit@huawei.com; rethishkumarps@huawei.com
> Cc: www-voice@w3.org; W3C Voice Browser Working Group
> Subject: Re: <disconnect/> on outbound call - ISSUE-524
>
> Rethish,
>
> This has been clarified in the internal draft of the spec. We have  
> settled
> on the use of connection.disconnected to cover this case.
> Thank you for raising this issue with the working group.
>
> Please let us know in the next 2 weeks (by 11/27/2008) if you have any
> comments or concerns with this resolution.
>
> Best regards,
>
> 	RJ
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> Chair, Editor and Chair, CCXML, VBWG, W3C
>
> On Jul 17, 2008, at 10:32 AM, RJ Auburn wrote:
>
>> Rethish,
>>
>> We are tracking this as ISSUE-524. Thanks for the comment, we will
>> have a reply back wit a fix shortly.
>>
>> 	RJ
>>
>> On May 13, 2008, at 3:40 AM, Rethish wrote:
>>
>>> Hi,
>>> I find some ambiguity in the CCXML specification regarding the  
>>> nature
>>> of <disconnect/> handling while an outbound call is in progress.
>>>
>>> 10.2.1: Connection State:
>>>   The figure illustrates that a connection.disconnected in
>>> PROGRESSING state transitions to FAILED state.
>>>   But, the table below this mentions that a connection.disconnected
>>> is received for an outbound call in progress when the <createcall>
>>> request was abandoned at the request of the application (using
>>> <disconnect>). "The Connection Object transitions to the  
>>> DISCONNECTED
>>> state."
>>>
>>> Is there any other case where a connection.disconnected can be
>>> received while an outbound call is in progress that would lead to
>>> FAILED state?
>>>
>>> 10.5.9: <disconnect> mentions:
>>> A CCXML document may use <disconnect> to abandon an outbound
>>> connection created using <createcall> which has not yet entered the
>>> CONNECTED state.  If <disconnect> is used to abandon an outbound
>>> call, it results in the generation of a 'connection.failed' event.
>>>
>>> IMHO the handling of <disconnect/> contradicts each other in the
>>> two sections. Please let me know your opinion on   this.
>>> Thanks & regards
>>> Rethish
>>>
>>
>
>
>
>



CallState-20081113.png
(image/png attachment: CallState-20081113.png)

Received on Wednesday, 19 November 2008 14:42:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 November 2008 14:42:59 GMT