# System Administrator’s Guide

# Managing and Configuring Audio Call Communication Services

The following section describes configuration and maintenance attributes and operations for the communication services that expose Parlay 3.0 Audio Call Web Services interfaces. The sections also provide a workflow for the configuration:

- Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

- Configuration Workflow for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction
- Reference: Attributes and Operations for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

## Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

This section contains a description of the configuration attributes and operations available for the Parlay X 3.0 Audio Call /Parlay MultiParty Call Control and Call User Interaction network protocol plug-in instance.

Most of the configuration is done in the OSA Access module, but with configuration parameters for Parlay MultiParty Call Control. See Managing OSA/Parlay Gateway Connections using Parlay_Access

For a configuration workflow, see Configuration Workflow for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction.

To see a | Refer to
--- | ---
Detailed list of necessary for managing and configuring the plug-in instance | Properties for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction
Configuration workflow | Configuration Workflow for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction
List of operations and attributes related to management and provisioning | None.
Reference of management attributes and operations | Reference: Attributes and Operations for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

### Properties for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication ServicesPlugin_px30_audio_call_parlay_mpcc_cui
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName=Plugin_px30_audio_call_parlay_mpcc_cui Type=com.bea.wlcp.wlng.plugin.ac.parlay.management.AudioCallManagementMBean
Network protocol plug-in service ID | Plugin_px30_audio_call_parlay_mpcc_cui
Network protocol plug-in instance ID | Plugin_px30_audio_call_parlay_mpcc_cui
Supported Address Scheme | tel:
North interfaces | com.bea.wlcp.wlng.px30.plugin.AudioCallPlayMediaPlugin com.bea.wlcp.wlng.px30.plugin.AudioCallCaptureMediaPlugin
Service type | AudioCall
Exposes to the service communication layer a Java representation of: | Parlay X 3.0 Part 11: Audio Call
Interfaces with the network nodes using: | Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control SCF; Subpart 7: MultiParty Call Control Service Open Service Access (OSA); Application Programming Interface (API); Part 5: User Interaction SCF
Deployment artifacts | osa_access.jar, Plugin_px30_audio_call_parlay_mpcc_cui.jar, and px30_audio_call_service.jar, packaged in wlng_nt_audio_call_px30.ear px30_audio_call.war, packaged in wlng_at_audio_call_px30.ear

This plug-in service does not support multiple instantiation using the Plug-in Manager. There is a one to one mapping between plug-in service and plug-in instance. The plug-in instance is created when the plug-in service is started.

### Configuration Workflow for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

Below is an outline for configuring the plug-in using Oracle Communications Services Gatekeeper Management Console:

1. Using the Management Console or an MBean browser, select the MBean detailed in Properties for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction.
2. Configure the behavior of the plug-in instance:

- Attribute: Retentiontime
- Attribute: CollectStartTimeout
- Attribute: CollectInterCharTimeout
- Attribute: ShutdownTimerInterval
- Attribute: Language
- Attribute: ChargingAllowed
- Attribute: Retentiontime
- Attribute: RepeatIndicator
- Attribute: ResponseRequested
- Attribute: MaxDigits
- Attribute: MinDigits
- Attribute: EndSequence
- Attribute: CollectStartTimeout
- Attribute: CollectInterCharTimeout

3. Gather information about the OSA Gateway and configure the MultiParty Call Control part of the protocol translator accordingly. The following information needs to be obtained from the OSA Gateway administrator and configured in the Parlay_Access service:

- OSA/Parlay SCS type to be used in the look up (service discovery) phase when requesting the MultiParty Call Control service (OSA/Parlay SCS) from the OSA/Parlay Gateway. Typically this is `P_MULTI_PARTY_CALL_CONTROL`.
- OSA/Parlay service properties to be used in the look up (service discovery) phase when requesting a service (OSA/Parlay SCS) from the OSA/Parlay Gateway. This depends on the OSA Gateway implementation.
- Authentication type used by the OSA/Parlay Framework.
- Encryption method used for the connection with the OSA Gateway.
- Signing algorithm used when signing the service level agreement with the OSA/Parlay Framework.

4. Setup the OSA Client and the OSA Client Mappings according to Creating an OSA client and Mapping the OSA client to an OSA Gateway and an OSA/Parlay SCS in Managing OSA/Parlay Gateway Connections using Parlay_Access for the MultiParty Call Control part of the plug-in instance.
5. Gather information about the OSA Gateway and configure the Call User Interaction part of the protocol translator accordingly. The following information needs to be obtained from the OSA Gateway administrator and configured in the OSA Access service:

- OSA/Parlay SCS type to be used in the look up (service discovery) phase when requesting the Generic User interaction service (OSA/Parlay SCS) from the OSA/Parlay Gateway. Typically this is `P_USER_INTERACTION`.
- OSA/Parlay service properties to be used in the look up (service discovery) phase when requesting a service (OSA/Parlay SCS) from the OSA/Parlay Gateway. This depends on the OSA Gateway implementation.
- Authentication type used by the OSA/Parlay Framework.
- Encryption method used for the connection with the OSA Gateway.
- Signing algorithm used when signing the service level agreement with the OSA/Parlay Framework.

6. Set up the OSA Client and the OSA Client Mappings according to Creating an OSA client and Mapping the OSA client to an OSA Gateway and an OSA/Parlay SCS in Managing OSA/Parlay Gateway Connections using Parlay_Access for the Generic User Interaction part of the plug-in instance.
7. If desired, create and load a node SLA, see:

Defining Global Node and Service Provider Group Node SLAs

Managing Application SLAs

Note: | It is not necessary to set up routing rules to the plug-in instance.

### Reference: Attributes and Operations for Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

Below is a list of attributes for configuration and maintenance:

- Attribute: CollectStartTimeout
- Attribute: CollectInterCharTimeout
- Attribute: Language
- Attribute: ChargingAllowed
- Attribute: Retentiontime
- Attribute: RepeatIndicator
- Attribute: ResponseRequested
- Attribute: RetensionTime
- Attribute: ShutdownTimerInterval
- Attribute: MaxDigits
- Attribute: MinDigits
- Attribute: EndSequence

### Attribute: CollectStartTimeout

Scope: Cluster

Unit: Seconds

Specifies the start time-out when collecting user input, the value for the first character time-out timer.

The value corresponds to the parameter `TpUICollectCriteria.StartTimeout` in the `sendInfoAndCollectReq` requests towards the Generic User Interaction SCS.

### Attribute: CollectInterCharTimeout

Scope: Cluster

Unit: Seconds

Specifies the inter-character time-out when collecting user input, the value for the inter-character time-out timer.

The value corresponds to the parameter `TpUICollectCriteria.InterCharTimeOut` in the `sendInfoAndCollectReq` requests towards the Generic User Interaction SCS.

### Attribute: Language

Scope: Cluster

Unit: n/a

Format: String according to valid language strings as defined in ISO 639.

Specifies the language of the message to be played for the call participant.

### Attribute: ChargingAllowed

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies whether charging is allowed.

- true if an application is allowed to specify charging information when playing a message (Parlay X operation playAudioMessage).
- False if not.

### Attribute: Retentiontime

Scope: Cluster

Unit: Seconds

Format: int [0-]

Specifies the length of time status information about a message (Parlay X MessageStatus) is stored after play operation has finished or an error related to the playing of a message has been received.

### Attribute: RepeatIndicator

Scope: Cluster

Unit: n/a

Format: int

Specifies the number of times a message should be played to the call participant.

The value corresponds to the parameter `repeatIndicator` in the `sendInfoReq` requests towards the Generic User Interaction SCS.

### Attribute: ResponseRequested

Scope: Cluster

Unit: n/a

Format: int [1,2,4]

Specifies if a response is required from the Generic User Interaction SCS, and what, if any, action the service should take.

The value corresponds to the parameter `responseRequested` in the `sendInfoReq` requests towards the Generic User Interaction SCS.

Use:

- 1 for P_UI_RESPONSE_REQUIRED
- 2 for P_UI_LAST_ANNOUNCEMENT_IN_A_ROW
- 4 for P_UI_FINAL_REQUEST

### Attribute: RetensionTime

Scope: Cluster

Unit: Seconds

Format: int

Specifies the time-interval for which status information is retained after a message is played or an error occurs.

### Attribute: ShutdownTimerInterval

Scope: Server

Unit: Seconds

Format: int

Specifies the time-interval to wait for call sessions to end before terminating when performing a graceful shutdown.

### Attribute: MaxDigits

Scope: Server

Unit: n/a

Format: int [1 -]

Specifies the maximum number of digits that can be collected from the call participant.

The value corresponds to the parameter `TpUICollectCriteria.MaxLength` in the `sendInfoAndCollectReq` requests towards the Generic User Interaction SCS.

### Attribute: MinDigits

Scope: Server

Unit: n/a

Format: int [1 -]

Specifies the minimum number of digits that can be collected from the call participant.

The value corresponds to the parameter `TpUICollectCriteria.MinLength` in the `sendInfoAndCollectReq` requests towards the Generic User Interaction SCS.

### Attribute: EndSequence

Scope: Server

Unit: n/a

Format: String

Specifies the digit to be used for ending collection of data of various lengths from a call participant.

The value corresponds to the parameter `TpUICollectCriteria. EndSequence` in the `sendInfoAndCollectReq` requests towards the Generic User Interaction SCS.