This page was last edited on March 27, 2014, at 18:26.
Comments or questions about this documentation? Contact us for support!
Media Control Platform
The core component of the Genesys Voice Platform (GVP) 8.x that executes the actual voice applications in the GVP solution. In addition, it is used by other communication layer components, such as SIP Server, to provide broader customer service scenarios, such as agent interactions, and many other functions.
Use to play audio resources of the following type:
The Play Sound block has the following properties:
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
If specified, ORS will play treatments itself; otherwise, treatment playing is delegated to URS. The device should specify the DN where the call is currently located. If the call is on multiple DNs, specify the DN for which the treatment will be applied. Users can enter a value or select any runtime variable from the dropdown.
This property is for future use by Orchestration Server. Its use will be described in various action elements reference in the Orchestration Server wiki.
Set to a meaningful value or keep the default value, which is the system variable InteractionId. Can be used for "interaction-less" processing for scenarios where the InteractionId variable is not automatically initialized, but instead must wait for an event. An example would be an SCXML application triggered by a Web Service that does not add an interaction. Background: Previous to 8.1.1, Composer did not expose an Interaction ID property. Instead, when ORS started processing an interaction, a generated SCXML application automatically initialized the system variable, InteractionId. This variable was then used internally by Routing and certain eServices blocks when interacting with ORS. With the introduction of support for Interaction-less processing, you can now define a specific event (IPD Wait For Event property) to initialize InteractionId, or not define an event at all. For scenarios with an interaction (IPD Diagram/Wait For Event=interaction.present for example), you may keep the default value for the Interaction ID property. The default value is the system variable InteractionId, which is initialized automatically in this case. For other scenarios (any scenario where the system variable InteractionId is not set), you may choose to:
Find this property's details under Common Properties.
Select the variable to retrieve extensions data in event dialog.playsound.done as described in the Orchestration Developers Guide, Orchestration Extensions, Dialog Log Interface section of the Orchestration Server Wiki.
The time, in seconds, that the treatment is applied.
Specify the location of the sound resource. Testing will be done against Genesys Stream Manager, a media server that generates and processes media streams in Real-time Transport Protocol (RTP) format. For more information on Stream Manager, start with the Framework 7.6 Stream Manager Deployment Guide. You will need to configure special DNs for these treatments in Configuration Server.
Identifies the type of sound.
When using the Play Application, Play Sound (Music and ARM Types) Exit, and Disconnect blocks, voice applications can now optionally use a single VXML session on Media Control Platform to play/run multiple treatments instead of using one session per treatment. This enables DTMF buffering between multiple MSML treatments. For more information, see Single Session Treatments.