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
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.
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:
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 18-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.
Note:
This operation is not supported in Network Gatekeeper 4.0
Signature:
getMediaNotification(correlator: String)
Table 18-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 18-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 18-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
Note:
This operation is not supported in Network Gatekeeper 4.0
Returns a list of correlators that uniquely identify each notification.
Signature:
listMediaNotifications()
Table 18-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 Network 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
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
callnotification_sip.jar, plug_in_call_notification_callback_ejb.jar, and px21_call_notification_service.jar packaged in wlng_nt_call_notification_px21.ear
px21_call_notification.war and px21_call_notification_callback.jar, packaged in wlng_at_call_notification_px21.ear
wlss-call-notification.war, packaged in wlss-int.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 2.1 Call Notification/SIP
Plugin_px30_call_notification_parlay_mpcc
