W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2008

Re: inbound transfer request on CCXML [cc] ISSUE-487

From: RJ Auburn <rj@voxeo.com>
Date: Thu, 27 Mar 2008 07:58:32 -0400
Cc: www-voice@w3.org, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>
Message-Id: <5929C6CD-6B94-428A-A0B2-DB9A3759E194@voxeo.com>
To: Roland Auckenthaler <roland_auckenthaler@nmss.com>

Roland,

For your reference this has been tracked as ISSUE-487 for CCXML 1.1.

Best regards,

	RJ

---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800



On Mar 27, 2008, at 07:55:27, RJ Auburn wrote:
>
> Roland,
>
> At the moment this case is not modeled but it would be something we  
> would definitely consider looking into for CCXML 1.1 as an extension  
> of the connection model. I suspect we would just add an event to the  
> connection group (connection.transfer or something like thaT) that  
> way your application could process this request. Things like SIP  
> REFER requests would probably be expected to fall into this class  
> but the exact mapping still is yet to be done.
>
> Best regards,
>
> 	RJ
>
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> tel:+1-407-418-1800
>
>
>
> On Feb 28, 2008, at 08:55:51, Roland Auckenthaler wrote:
>>
>> Hi,
>>
>> I was looking through the CCXML specification and have a question  
>> regaring an incoming transfer request. On a dialog resource a  
>> transfer request is passed to the CCXML session via the  
>> dialog.transfer event. Now if I have a connection resource (i.e.  
>> connected to a SIP client), how would I get notified of an  
>> incomming transfer request? There is no connection.transfer event  
>> that I can react on.
>>
>> Can you explain to me how this may work?
>>
>> best regards
>>
>> Roland Auckenthaler
>> Sales Engineer CEEME, NMS Communications
>>
>> Address:  Richard Strauss Strasse 71, D-81679 Munich, Germany
>> Phone: +49 89 945484-78, Fax: +49 89 945484-70
>> MSN-IM: rauckenthaler@hotmail.com
>>
>> Amtsgericht Muenchen: HRB 132404, Geschäftsführer: Herb Shumway
>>
>>
>>
>>
>
>
Received on Thursday, 27 March 2008 11:59:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 27 March 2008 11:59:51 GMT