# System Administrator’s Guide

# Managing and Configuring Call Notification Communication Services

The following section describes configuration and maintenance attributes and operations for the Parlay X Call Notification communication services:

- Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

- Configuration Workflow for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control
- Management and Provisioning Operations for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control
- Reference: Attributes and Operations for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

- Parlay X 2.1 Call Notification/SIP

- Configuration Workflow for Parlay X 2.1 Call Notification/SIP
- Reference: Attributes and Operations Parlay X 2.1 Call Notification/SIP

## Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

This section contains a description of the configuration attributes and operations available for the Parlay X 3.0 Call Notification/Parlay MultiParty Call Control 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.

Two different types of notifications are managed:

- Regular notifications, started by an application invoking `startCallNotification` or `startCallDirectionNotification`
- Media notifications, started by an application invoking `startPlayAndCollectNotification`

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

### Configuration Workflow for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

1. Using the Management Console or an MBean browser, select the MBean detailed in Properties for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control.
2. Gather information about the OSA/Parlay Gateway and configure the protocol translator accordingly. The following information needs to be obtained from the OSA/Parlay 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.

3. Set up the OSA/Parlay Client and the OSA/Parlay Client Mappings according to Mapping the OSA client to an OSA Gateway and an OSA/Parlay SCS in section Managing OSA/Parlay Gateway Connections using Parlay_Access.
4. Set up the routing rules to the plug-in instance, see Configuring the Plug-in Manager. Use the plug-in instance ID and address schemes detailed in Properties for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control.
5. If desired, create and load a node SLA, see:

Defining Global Node and Service Provider Group Node SLAs

Managing Application SLAs

Move on to the provisioning of service provider accounts and application accounts.

### Properties for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication ServicesPlugin_px30_call_notification_parlay_mpcc
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName=Plugin_px30_cn_parlay Type=com.bea.wlcp.wlng.px30.plugin.callnotification.parlay.management.mbean.CallNotificationMBean
Network protocol plug-in service ID | Plugin_px30_call_notification_parlay_mpcc
Network protocol plug-in instance ID | Plugin_px30_call_notification_parlay_mpcc
Supported Address Scheme | tel
North interfaces | com.bea.wlcp.wlng.px30.plugin.CallNotificationManagerPlugin com.bea.wlcp.wlng.px30.plugin.CallDirectionManagerPlugin com.bea.wlcp.wlng.px30.callback.CallDirectionCallback com.bea.wlcp.wlng.px30.callback.CallNotificationCallback
Service type | CallNotification
Exposes to the service communication layer a Java representation of: | Parlay X 3.0 Part 3: Call Notification
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
Deployment artifacts | px30_callnotification_parlay.jar, packaged in wlng_nt_call_notification_px30.ear px30_call_notification.war and px30_call_notification_callback.jar, packaged in wlng_at_call_notification_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.

### Management and Provisioning Operations for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

The following operations are related to provisioning and management:

- Operation: deleteMediaNotification
- Operation: deleteNotification
- Operation: getMediaNotification
- Operation: getNotification
- Operation: listNotifications
- Operation: listMediaNotifications

### Reference: Attributes and Operations for Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

Managed object: Communication ServicesPlugin_px30_call_notification_parlay_mpcc

MBean: com.bea.wlcp.wlng.px30.plugin.callnotification.parlay.management.mbean.CallNotificationMBean

Below is a list of attributes and operations for configuration and maintenance:

- Operation: deleteMediaNotification
- Operation: deleteNotification
- Operation: getMediaNotification
- Operation: getNotification
- Operation: listNotifications
- Operation: listMediaNotifications

### Operation: deleteMediaNotification

Scope: Cluster

Deletes a media notification.

Signature:

    deleteMediaNotification(correlator: String)

Table 22-1 deleteMediaNotification
deleteNotification
Parameter | Description
--- | ---
correlator | ID for the subscription. Given by an application when the subscription was started.

### Operation: deleteNotification

Scope: Cluster

Deletes a notification from the storage and removes it from OSA Gateway.

Signature:

    deleteNotification(correlator: String)

Table 22-2 deleteNotification
deleteNotification
Parameter | Description
--- | ---
correlator | ID for the subscription. Given by an application when the subscription is started.

### Operation: getMediaNotification

Scope: Cluster

Displays information about a media notification. The information includes:

- Parlay X correlator.
- Parlay X callSessionIdentifier
- needNotify -internal field. If true, Parlay X 3.0 Audio Call for MPCC and CUI plug-in instance needs to invoke the Parlay X 3.0 Call Notification for MPCC callback method sendInfoAndCollectRes.
- Parlay IpAppUICallRef (CORBA IOR)
- Parlay X endPoint to where the notification is sent
- Data about the owner of the notification:

- Service provider account ID
- Application account ID
- Application instance ID
- notifMode, used to distinguish which kind of media notification the notification belongs to. That is, which Parlay X operation that created the notification:

- 1 -the notification was created using startPlayAndCollectInteraction.
- 2 -the notification was created using startPlayAndRecordInteraction.

Signature:

    getMediaNotification(correlator: String)

Table 22-3 getMediaNotification
getMediaNotification
Parameter | Description
--- | ---
correlator | ID for the subscription. Given by an application when the subscription is started.

### Operation: getNotification

Scope: Cluster

Displays information about a notification. The information includes:

- Parlay X Correlator.
- Parlay X Endpoint where notifications are sent.
- List of Parlay `notificationsIds` associated with the Parlay X notification. There is one for each called party address for which notifications should be triggered supplied in the Parlay X operations `startCallNotification` or `startCallDirectionNotification.`
- Data about the owner of the notification:

- Service provider account ID
- Application account ID
- Application instance ID

Signature:

    getNotification(correlator: String)

Table 22-4 getNotification
getNotification
Parameter | Description
--- | ---
correlator | ID of the notification. Given by an application when the notification is started.

### Operation: listNotifications

Scope: Cluster

Displays all active call notifications. That is, notifications registered by an application using:

- Operation:`startCallDirectionNotification`
- Operation: `startCallNotification`

Returns a list of correlators that uniquely identifies each notification.

Signature:

    listNotifications()

Table 22-5 listNotifications
listNotifications
Parameter | Description
--- | ---
- | -

### Operation: listMediaNotifications

Scope: Cluster

Displays all active media notifications. That is, notifications that have been registered by an application using:

- Operation: startPlayAndCollectNotification
- Operation: startPlayAndRecordNotification

Returns a list of correlators that uniquely identify each notification.

Signature:

    listMediaNotifications()

Table 22-6 listMediaNotifications
listNotifications
Parameter | Description
--- | ---
- | -

## Parlay X 2.1 Call Notification/SIP

This section contains a description of the configurations attributes and operations available for the Parlay X 2.1 Call Notification/SIP plug-in instance.

Parlay X 2.1 Call Notification/SIP uses two parts for SIP connectivity, a part that executes as a network protocol plug-in instance in Oracle Communications Services Gatekeeper container, and a part that executes as a SIP application in the SIP Server container. The two parts execute in different containers and must be configured in both.

To see a | Refer to
--- | ---
Detailed list of necessary information for managing and configuring the plug-in | Properties for Parlay X 2.1 Call Notification/SIP
Configuration workflow | Properties for Parlay X 2.1 Call Notification/SIP
List of operations and attributes related to management and provisioning | Management for Parlay X 2.1 Call Notification/SIP
Reference of management attributes and operations | Reference: Attributes and Operations Parlay X 2.1 Call Notification/SIP

### Properties for Parlay X 2.1 Call Notification/SIP

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication ServicesPlugin_px21_call_notification_sip
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName=Plugin_px21_call_notification_sip Type=com.bea.wlcp.wlng.plugin.callnotification.sip.management.CallNotificationMBean
Network protocol plug-in service ID | Plugin_px21_call_notification_sip
Network protocol plug-in instance ID | Plugin_px21_call_notification_sip
Supported Address Scheme | sip
North interfaces | com.bea.wlcp.wlng.px21.plugin.CallNotificationManagerPlugin om.bea.wlcp.wlng.px21.plugin.CallDirectionManagerPlugin
Service type | CallNotification
Exposes to the service communication layer a Java representation of: | Parlay X 2.1 Part 3: Call Notification
Interfaces with the network nodes using: | SIP: Session Initiation Protocol, RFC 3261
Deployment artifacts NT EAR wlng_nt_call_notification_px21.ea | px21_call_notification_service.jar, Plugin_px21_call_notification_sip.jar, and px21_call_notification_sip.war
AT EAR: Normal wlng_at_call_notification_px21.ear | px21_call_notification.war, px21_call_notification_callback.jar, and rest_call_notification.war
AT EAR: SOAP Only wlng_at_call_notification_px21_soap.ear | px21_call_notification.war and px21_call_notification_callback.jar

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 2.1 Call Notification/SIP

1. In Oracle Communications Services Gatekeeper Management Console, set up the routing rules to the plug-in instance: see Configuring the Plug-in Manager. Use the plug-in instance ID and address schemes detailed in Properties for Parlay X 2.1 Call Notification/SIP.
2. If desired, create and load a node SLA, see:

Defining Global Node and Service Provider Group Node SLAs

Managing Application SLAs

Move on to the provisioning of service provider accounts and application accounts.

### Management for Parlay X 2.1 Call Notification/SIP

The following operations are related to management:

- Operation: getCallDirectionSubscription
- Operation: getNotificationSubscription
- Operation: listCallDirectionSubscriptions
- Operation: listNotificationSubscriptions
- Operation: removeAllCallDirectionSubscriptions
- Operation: removeAllNotificationSubscriptions
- Operation: removeCallDirectionSubscription
- Operation: removeNotificationSubscription

### Reference: Attributes and Operations Parlay X 2.1 Call Notification/SIP

Below is a list of attributes and operations for configuration and maintenance:

- Operation: getCallDirectionSubscription
- Operation: getNotificationSubscription
- Operation: listCallDirectionSubscriptions
- Operation: listNotificationSubscriptions
- Operation: removeAllCallDirectionSubscriptions
- Operation: removeAllNotificationSubscriptions
- Operation: removeCallDirectionSubscription
- Operation: removeNotificationSubscription

### Operation: getCallDirectionSubscription

Scope: Cluster

Displays call direction subscription information.

Signature:

    getCallDirectionSubscription(Correlator: String)

Table 22-7 getCallDirectionSubscription
getCallDirectionSubscription
Parameter | Description
--- | ---
Correlator | ID for the subscription. Given by an application when the subscription was started.

### Operation: getNotificationSubscription

Scope: Cluster

Displays call notification subscription information.

Signature:

    getNotificationSubscription(Crrelator: String)

Table 22-8 getCallDirectionSubscription
getCallDirectionSubscription
Parameter | Description
--- | ---
Correlator | ID for the subscription. Given by an application when the subscription was started.

### Operation: listCallDirectionSubscriptions

Scope: Cluster

Displays a list of correlators for call direction subscriptions.

Signature:

    listCallDirectionSubscriptions(Offset: int, Length: int)

Table 22-9 listCallDirectionSubscriptions
listCallDirectionSubscriptions
Parameter | Description
--- | ---
Offset | Start of offset.
Length | Number of entries returned.

### Operation: listNotificationSubscriptions

Scope: Cluster

Displays a list of correlators for call notification subscriptions.

Signature:

    listNotificationSubscriptions(Offset: int, Length: int)

Table 22-10 listNotificationSubscriptions
listNotificationSubscriptions
Parameter | Description
--- | ---
Offset | Start of offset.
Length | Number of entries returned.

### Operation: removeAllCallDirectionSubscriptions

Scope: Cluster

Removes all call direction subscriptions.

Signature:

    removeAllCallDirectionSubscriptions()

Table 22-11 removeAllCallDirectionSubscriptions
removeAllCallDirectionSubscriptions
Parameter | Description
--- | ---
- | -

### Operation: removeAllNotificationSubscriptions

Scope: Cluster

Removes all call notification subscriptions.

Signature:

    removeAllNotificationSubscriptions()

Table 22-12 removeAllNotificationSubscriptions
removeAllNotificationSubscriptions
Parameter | Description
--- | ---
- | -

### Operation: removeCallDirectionSubscription

Scope: Cluster

Removes a call direction subscription.

Signature:

    removeCallDirectionSubscription(Correlator: String)

Table 22-13 removeCallDirectionSubscription
removeCallDirectionSubscription
Parameter | Description
--- | ---
Correlator | ID for the subscription. Given by an application when the subscription was started.

### Operation: removeNotificationSubscription

Scope: Cluster

Removes a call notification subscription.

Signature:

    removeNotificationSubscription(Correlator: String)

Table 22-14 removeNotificationSubscription
removeNotificationSubscription
Parameter | Description
--- | ---
Correlator | ID for the subscription. Given by an application when the subscription was started.