|
|
This chapter describes the Parlay X 3.0 Audio Call communication service in detail:
The Audio Call communication service implements the Parlay X 3.0 Audio Call set of interfaces. For the exact version of the standard the communication service supports, see “Appendix A: Standards and Specifications” of Concepts and Architectural Overview, another document in this set.
Using the Audio Call communication service, an application can:
The Audio Call communication service can be used by applications to play audio messages to one or more call participants in an existing call. The existing call is identified by the Call Session Identifier returned to the application at the time the call session is set up using the Parlay X 3.0 Third Party Call communication service. If desired, applications can receive digits collected from those participants in response to the audio message using a notification set up using the Parlay X 3.0 Call Notification communication service.
The audio message content to be played must be defined in a binary format such as WAV stored at a URL available to the network and rendered by an audio player. Oracle Communications Oracle Communications Services Gatekeeper does not actually render the message: this is the responsibility of equipment that must be present on the target telecom network, such as Interactive Voice Response (IVR) systems.
Off the shelf, the Parlay X 3.0 Audio Call communication service supports a combination of the following network protocols:
When Oracle Communications Services Gatekeeper is configured to use these protocols, it connects to a Parlay 3.3 Multi-Party Call Control SCS and a Parlay 3.3 Call User Interaction SCS provided by an OSA/Parlay Gateway. See “Appendix A: Standards and Specifications” of Concepts and Architectural Overview, another document in this set, for the exact version of the standards Oracle Communications Services Gatekeeper supports.
Communication services share many common features, covered in “Introducing Communication Services” in Concepts and Architectural Overview, but each one has a few characteristics that are specific only to that service. This section describes those specific features for the Audio Call communication service, including:
There are two Audio Call-Parlay 3.3 MPCC/CUI-specific CDRs. They occur when the following criteria are met:
sendInfoRes is sent from the network to Oracle Communications Services Gatekeeper, indicating that the audio message has completed playing, if this is not the result of an explicit request to stop from the application.sendInfoAndCollectRes is sent from the network to Oracle Communications Services Gatekeeper, indicating that the audio message has completed playing and the call participant’s response has been collected in the form of digits.Table 2-1lists the EDR IDs created by the Audio Call-Parlay 3.3 MPCC/CUI communication service. This does not include EDRs created when exceptions are thrown. For more information, see Events, Alarms, and Charging.
The table below outlines the correlation between the methods being invoked from either the application (in application-initiated requests) or the telecom network (in network-initiated requests) and the transaction type collected by the statistics counters in Oracle Communications Services Gatekeeper for the Parlay X 3.0 Audio Call-Parlay 3.3 MPCC/CUI communication service:
The Parlay X 3.0 Audio Call-Parlay 3.3 MPCC/CUI communication service does not use any address schemes directly, but in working with the Parlay X 3.0 Third Party Call and Call Notification communication services, it uses the tel: scheme indirectly.
|