From 103be0cecb76800109f9ba0b78665e20e341cc84 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 12 Jun 2013 20:50:07 -0600 Subject: [PATCH] 0.2 --- xep-0327.xml | 96 +++++++++++++--------------------------------------- 1 file changed, 24 insertions(+), 72 deletions(-) diff --git a/xep-0327.xml b/xep-0327.xml index ddbcf51d..3b4f7011 100644 --- a/xep-0327.xml +++ b/xep-0327.xml @@ -34,6 +34,12 @@ jdecastro@voxeo.com http://voxeolabs.com + + 0.2 + 2013-06-10 + psa +

Updates to address open issues.

 + 0.1 2013-05-06 @@ -52,7 +58,7 @@ @@ -82,9 +88,9 @@ ]]> -

In this example, a call from 'tel:+13058881212' has reached the Rayo server 'shakespeare.lit' by calling 'tel:+18003211212', and been assigned an ID '9f00061'. The server has determined that 'juliet@capulet.lit' is a valid candidate for delegating control of the call, and so has directed an offer event to her 'balcony' resource.

+

In this example, a call from 'tel:+13058881212' has reached the Rayo server 'shakespeare.lit' by calling 'tel:+18003211212', and been assigned an ID '9f00061'. The server has determined that 'juliet@capulet.lit' is a valid candidate to be the client to whom the server delegates control of the call, and so has directed an offer event to her 'balcony' resource.

-

The client then decides that it is able to handle the incoming call, and so accepts it from the server, thus gaining exclusive control and indicating to the calling party that the call will be processed and that it should ring.

+

The client, 'juliet@capulet.lit', then decides that it is able to handle the incoming call, and so accepts it from the server, thus gaining exclusive control and indicating to the calling party that the call will be processed and that it should ring.

- + ]]> @@ -269,7 +275,7 @@ -

A Rayo server is an entity which is capable of receiving and intiating calls and being party to their media stream, while exposing a Rayo interface to a client in order to permit control over its calls. The Rayo server may handle calls in any way supported by the implementation, such as SIP, Jingle, etc, and should expose a full XMPP domain at the root level of the service deployment (eg shakespeare.lit).

+

A Rayo server is an entity which is capable of receiving and initiating calls and being party to their media stream, while exposing a Rayo interface to a client in order to permit control over its calls. The Rayo server may handle calls in any way supported by the implementation, such as SIP, Jingle, etc, and should expose a full XMPP domain at the root level of the service deployment (eg shakespeare.lit).

The Rayo server is responsible for keeping track of valid clients, routing calls to the correct potential controlling parties, performing authorization measures on received stanzas, etc.

For the purposes of this specification, complex server-side deployments such as clusters, proxies, gateways, protocol translators, etc are not considered. Further details of such concepts may be found in their (present or future) relevant specifications.

 @@ -288,7 +294,7 @@

Mixers have separate presence from the root domain of the service and its calls and thus appear to be separate entities.

-

A Rayo command is a simple combination of request and response and may be issued directly to the service domain, or to a call or a mixer. Commands are executed serially and are generally very short-lived.

+

A Rayo command is a simple combination of request and response and may be issued directly to the service domain, a call, a mixer or a component attached to any of the former. Commands are executed serially and are generally very short-lived.

Components extend the Rayo protocol by providing additional media and call control functionality.

@@ -1479,19 +1485,10 @@ match (indicating that one of the grammars matched the received input).
  • - initial-timeout (indicating that the initial timeout was triggered). + noinput (indicating that no input was received before a timeout was encountered).
  • - inter-digit-timeout (indicating that the inter-digit timeout was triggered). -
    • -
  • - max-silence (indicating that the max-silence timeout was triggered). -
    • -
  • - min-confidence (indicating that the minimum confidence threshold was not reached). -
    • -
  • - no-match (indicating that input was received which did not match any of the specified grammars). + nomatch (indicating that input was received which did not match any of the specified grammars).
    • @@ -2322,7 +2319,7 @@ repeat-times Indicates the number of times the output should be played. - An integer greater than 0. + A positive integer or 0 to repeat forever. 1 OPTIONAL @@ -2472,7 +2469,7 @@ mode The method by which to collect input. - any|dtmf|speech + any|dtmf|voice any OPTIONAL @@ -2593,28 +2590,10 @@ - -

    Indicates that the component came to an end because the initial timeout was triggered.

    -

    The <initial-timeout/> element MUST be empty.

    -

    The <initial-timeout/> element has no attributes.

    -     - - -

    Indicates that the component came to an end because the inter-digit timeout was triggered.

    -

    The <inter-digit-timeout/> element MUST be empty.

    -

    The <inter-digit-timeout/> element has no attributes.

    -     - - -

    Indicates that the component came to an end because the max-silence timeout was triggered.

    -

    The <max-silence/> element MUST be empty.

    -

    The <max-silence/> element has no attributes.

    -     - - -

    Indicates that the component came to an end because the minimum confidence threshold was not reached.

    -

    The <min-confidence/> element MUST be empty.

    -

    The <min-confidence/> element has no attributes.

    + +

    Indicates that the component came to an end because a timeout was triggered before input was received.

    +

    The <noinput/> element MUST be empty.

    +

    The <noinput/> element has no attributes.

     @@ -3593,7 +3572,7 @@ - + Indicates the number of times the output should be played. @@ -3817,7 +3796,7 @@ - + @@ -3939,37 +3918,10 @@ - + - Indicates that the component came to an end because the initial timeout was triggered. - - - - - - - - - Indicates that the component came to an end because the inter-digit timeout was triggered. - - - - - - - - - Indicates that the component came to an end because the max-silence timeout was triggered. - - - - - - - - - Indicates that the component came to an end because the minimum confidence threshold was not reached. + Indicates that the component came to an end because a timeout was triggered before input was received.