Using a Third Party Call Parlay X 2.1 communication service, an application can:

Set up a call between two parties. For example, an application could set up a call between an investor and a broker if a particular stock reaches a predetermined price. Or a computer user could set up a call between himself and someone in the address book with a mouse click.

Query for the status of a previously set up call

Cancel a call it is creating as it is about to be set up

Terminate an ongoing call it created

10.1.1 How It Works

In the Parlay X 2.1 Third Party Call communication services model, a call has two distinct stages:

10.1.1.1 Call Setup

There are two parties involved in Third Party Call calls: the A-party (the caller) and the B-party (the callee). When a call is set up using a Third Party Call communication service, OWLCS attempts to set up a call leg to the A-party. When the caller goes off-hook (“answers”), OWLCS attempts to set up a call leg to the B-party. When the callee goes off-hook, the two call legs are connected using the underlying network. This ends the call setup-phase.

The application can cancel the call during this phase.

10.1.1.2 Call Duration

While the call is underway, the audio channel that connects the caller and the callee is completely managed by the underlying network. During this phase of the call, the application can only query as to the status of the call. A call can be terminated in two ways, either using the application-facing interface, or having the caller or callee hang up.

Requests using a Parlay X 2.1 Third Party Call communication service flow only in one direction, from the application to the network. Therefore this communication service supports only application-initiated (or mobile-terminated) functionality.

Note:

Third Party Call communication services manage only the signalling, or controlling, aspect of a call. The media, or audio, channel is managed by the underlying network. Only parties residing on the same network can be controlled, unless:

· The network plug-in connects to a media gateway controller

· One of the participants is connected to a signalling gateway so that, from a signalling point of view, all parties reside on the same network

10.1.2 Supported Networks

Off the shelf, Parlay X 2.1 Third Party Call communication services can be configured to support the SIP network protocol.

Note:

OWLCS acts as a Back-to-Back User Agent. During the call duration phase, the actual call is peer-to-peer.

10.2 Configuring Parlay X 2.1 Third Party Call

This section contains a description of the configuration attributes and operations available for the Parlay X 2.1 Third Party Call.

10.2.1 Configuration Workflow for Parlay X 2.1 Third Party Call/SIP

Follow these configuration steps:

Using the Management Console or an MBean browser, select the MBean detailed in Properties for Parlay X 2.1 Third Party Call/SIP.

10.2.2 Attributes and Operations for Parlay X 2.1 Third Party Call

Table 10-2 contains a list of attributes for configuration and maintenance

Table 10-2 Configuration and Maintenance Attributes

Attribute

Scope

Unit

Format

Description

ThirdPartyCall ControllerURI

Cluster

NA

String in URI format

Specifies the Controller SIP URI that is used to establish the third party call. If this value is set, a call appears to the callee to come from this URI. By default, the value is “None”, where no controller URI is used to establish the call. In this case, the call appears to the callee to come from the caller

ISCRouteURI

Cluster

NA

String in URI format

Specifies the URI of the IMS service control route.

MaximumCall Duration

Cluster

minutes

int

Specifies for how long time a call is allowed to be ongoing. If this time expires, the call is terminated.

StatusRetentionTime

Cluster

minutes

int

Specifies for how long time to retain status information about the call after it has been terminated.

PAssertedIdentity URI

Cluster

NA

String in URI format

Specifies the SIP URI used in the P-Asserted-Identity header added by the Third Party Call service. If left blank no P-Asserted-Identity header is added.

10.3 Statement of Compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Third Party call.

The Parlay X 2.1 interface complies to ETSI ES 202 391-2 V1.2.1 Open Service Access (OSA); Parlay X Web Services; Part 2: Third Party Call (Parlay X 2). For more information, see the relevant specification at http://parlay.org/en/specifications/pxws.asp

Table 10-3 Statement of Compliance, Parlay X 2.1 Third Party Call

Method

Compliant Yes/No

Interface: ThirdPartyCall

MakeCall

Y

GetCallInformation

Y

EndCall

Y

CancelCall

Y

The SIP plug-in for Parlay X 2.1 Third Party Call is an integration plug-in that utilizes the Oracle WebLogic SIP Server to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The SIP Servlet uses the SIP API provided by the WebLogic SIP server, which in its turn converts the API calls to SIP messages.

The implementation of the SIP based third party call is in compliance with RFC 3725 - Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) Flow I (http://www.ietf.org/rfc/rfc3725.txt).

Table 10-4 Statement of Compliance, SIP for Parlay X 2.1 Third Party Call