# Communication Service Reference

# Parlay X 3.0 Audio Call Communication Service

This chapter describes the Parlay X 3.0 Audio Call communication service in detail:

- An Overview of the Parlay X 3.0 Audio Call Communication Service

- How It Works
- Supported Network Protocols

- Configuration Specifics for the Parlay X 3.0 Audio Call Communication Service

- Charging Data Records
- Event Data Records
- Statistics
- Supported Address Schemes

## An Overview of the Parlay X 3.0 Audio Call Communication Service

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:

- Play audio to one or more call participants in an existing call session set up by the Parlay X 3.0 Third Party Call communication service.
- Find out if the audio is currently being played or has not yet started to play.
- Explicitly end playing of the audio.
- Collect digits from call participants in response to an audio message that has been played to them and, in conjunction with the Parlay X 3.0 Call Notification communication service, return the information to the application.
- Interrupt an ongoing interaction, such as on-hold music.

### How It Works

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.

### Supported Network Protocols

Off the shelf, the Parlay X 3.0 Audio Call communication service supports a combination of the following network protocols:

- Parlay 3.3 Multi-Party Call Control and Call User Interaction

#### Parlay 3.3 Multi-Party Call Control and Call User Interaction

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.

## Configuration Specifics for the Parlay X 3.0 Audio Call Communication Service

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:

- Charging Data Records
- Event Data Records
- Statistics
- Supported Address Schemes

### Charging Data Records

##### Generation of CDRs

There are two Audio Call-Parlay 3.3 MPCC/CUI-specific CDRs. They occur when the following criteria are met:

- When `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.
- When `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.

### Event Data Records

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.

Table 2-1 Event types emitted in Audio Call communication service
EdrId | Method Called
--- | ---
11100 | playAudioMessage
11101 | getMessageStatus
11102 | endMessage
11103 | startPlayAndCollectInteraction
11104 | stopMediaInteraction
11105 | sendInfoRes
11106 | SendInfoErr
11107 | sendInfoAndCollectRes
11108 | SendInfoAndCollectErr
11109 | attachMediaRes
111010 | attachMediaErr
111011 | detachMediaRes
111012 | detachMediaErr
111013 | abortActionRes
111014 | abortActionErr

### Statistics

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:

Table 2-2 Transaction types for Parlay X 3.0 Audio Call-Parlay MPCC/CUI communication service
Method | Transaction type
--- | ---
startPlayAndCollectInteractions | TRANSACTION_TYPE_CALL_CONTROL_SERVICE_INITIATED
playAudioMessage | TRANSACTION_TYPE_CALL_CONTROL_SERVICE_INITIATED

### Supported Address Schemes

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.