RFC 2897 (rfc2897) - Page 2 of 34

Proposal for an MGCP Advanced Audio Package

RFC 2897              MGCP Advanced Audio Package            August 2000


Table of Contents

   1. Introduction ................................................  2
   1.1. Audio Segments ............................................  3
   1.1.1. Sequences And Sets ......................................  3
   1.1.2. Segment Types ...........................................  4
   2. Advanced Audio Package ......................................  5
   3. Events ......................................................  5
   4. Event Parameters ............................................  7
   5. Return Parameters ...........................................  7
   6. Variables ................................................... 14
   7. Selectors ................................................... 17
   8. Aliases ..................................................... 18
   9. Examples .................................................... 21
   10. Formal Syntax Description .................................. 22
   11. References ................................................. 22
   12. Formal Syntax Description .................................. 25
   13. References ................................................. 32
   14. Author's Address ........................................... 33
   15. Full Copyright Statement ................................... 34

1.  Introduction

   The following syntax supports both simple and complex audio
   structures.  A simple audio structure might be a single announcement
   such as "Welcome to Bell South's Automated Directory Assistance
   Service".  A more complex audio structure might consist of an
   announcement followed by voice variable followed by another
   announcement, for example "There are thirty seven minutes remaining
   on your prepaid calling card," where "There are" is a prompt, the
   number of minutes is a voice variable, and "minutes remaining on your
   prepaid calling card" is another prompt.

   It is also possible to define complex audio structures that are
   qualified by user defined selectors such as language, audio file
   format, gender, accent, customer, or voice talent.  For instance, if
   the above example were qualified by language and accent selectors, it
   would be possible to play "There are thirty seven minutes remaining
   on your prepaid calling card" in English spoken with a southern
   accent or in English spoken with a mid-western accent, providing that
   the audio to support this had been provisioned.

   There are two methods of specifying complex audio.  The first is to
   directly reference the individual components.  This requires a
   complete description of each component to be specified via the
   protocol.  The second method is to provision the components on the
   Audio Server as a single entity and to export a reference to that
   entity to the call agent.  In this case, only the reference (plus any



Cromwell                     Informational