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

Re: Outbound Call Handling

From: Jeff Haynie <jhaynie@mardome.com>
Date: Thu, 15 Mar 2001 16:33:43 -0500
Message-ID: <000a01c0ad97$9ce03460$700a11ac@tgix.com>
To: "Edgar, Bob" <Bob.Edgar@dialogic.com>
Cc: <www-voice@w3c.org>
Bob-

Thanks for your reply.  It would be beneficial to come up with a standard
way to control document acquisition -- both for answering an incoming call
and outbound call origination -- in a standardized way.

Example, we want to offer our clients the ability to send us a request (via
HTTP, etc.) to originate an outbound call, which will turn control over to
the document once the call is nailed up.  However, currently, the spec
doesn't really specify how that should be done.  Ideally, if there was a
common XML schema that described the outbound call and a common way to
handle receipt of the XML, then it would simply everyone's life (especially
application developers working with different implementations)... I've kept
this simple and ignored CPA issues (ideally, those might even be vendor
specific events such as dialogic's perfect call analysis...)

Example thoughts:

<vxml>
    <originate-call dest="phone://7705551212" timeout="30s">
                <goto next="http://someurl"/>
                <catch event="telephone.noanswer">
                        <...>
                </catch>
                <catch event="telephone.busy">
                        <...>
                </catch>
                ...
    </originate-call>
</vxml>

Ideally, this VoiceXML could be sent to a webserver to originate the
outbound call, which might handle the authentication of the request
(exchange keys, etc.) and then hand over the VoiceXML to the interpreter for
execution.

Any thoughts on this ?  I'd prefer to not re-invent the wheel.

Jeff

----- Original Message -----
From: "Edgar, Bob" <Bob.Edgar@dialogic.com>
To: "'Jeff Haynie'" <jhaynie@mardome.com>
Sent: Thursday, March 15, 2001 3:50 PM
Subject: RE: Outbound Call Handling


> Jeff, VoiceXML (both 1.0 & 2.0) by design does not address how calls first
> connect to the browser. That applies to in-bound and out-bound calls
> equally. An existing call (established by proprietary means outside the
> spec) is connected to the browser and given a start start page (determined
> also by proprietary means).
> Bob
>
> -----Original Message-----
> From: Jeff Haynie [mailto:jhaynie@mardome.com]
> Sent: Thursday, March 15, 2001 11:46 AM
> To: www-voice@w3.org
> Subject: Outbound Call Handling
>
>
> Does anyone know if and how VoiceXML 2.0 will address outbound call
handling
> (call origination)?
>
> Thanks,
>
> Jeff Haynie
> CTO
> Mardome, Inc.
>
Received on Thursday, 15 March 2001 16:33:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:53 GMT