# System Administrator’s Guide

# Managing and Configuring Third Party Call Communication Services

The following section describes configuration and maintenance attributes and operations for the Oracle Communications Services Gatekeeper communication services that expose Parlay X 3.0 and Parlay X 2.1 Third Party Call Web Services interfaces. The sections also provide a workflow for the configuration. There are three plug-in services related to Third Party Call:

- Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control
- Parlay X 2.1 Third Party Call/INAP
- Parlay X 2.1 Third Party Call/SIP

## Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control

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

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

### Configuration workflow for Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control

1. Using either the Management Console or an MBean browser, select the MBean detailed in Properties for Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control.
2. Configure the attributes of the plug-in instance:

- Attribute: CallingParticipantNameMandantory
- Attribute: MaximumDurationEnforced
- Attribute: MultiMediaSupported
- Attribute: ChargingAllowed
- Attribute: StatusRetentionTime
- Attribute: ChangeMediaAllowed
- Attribute: MaximumParticipants
- Attribute: MaximumParticipants
- Operation: configCallGetInfoReq
- Operation: configLegGetInfoReq

3. Gather information about the OSA Gateway and configure the plug-in instance 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 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.
5. Setup 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 Third Party Call/Parlay MultiParty Call Control.
6. If desired, create and load a node SLA. See:

Defining Global Node and Service Provider Group Node SLAs

Managing Application SLAs

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

### Management Operations for Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control

The following operations are related to management:

- Operation: getCallLegs
- Operation: getCallSessionInfo
- Operation: getCallLegSessionInfo
- Operation: listCallSessionIds
- Operation: countPendingCallSession

### Properties for Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication ServicesPlugin_px30_third_party_call_parlay_mpcc
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName=Plugin_px30_third_party_call_parlay_mpcc Type=com.bea.wlcp.wlng.plugin.tpc.parlay.management.ThirdPartyCallMBean
Network protocol plug-in service ID | Plugin_px30_third_party_call_parlay_mpcc
Network protocol plug-in instance ID | Plugin_px30_third_party_call_parlay_mpcc
Supported Address Scheme | tel
North interface | com.bea.wlcp.wlng.px30.plugin.ThirdPartyCallPlugin
Service type | ThirdPartyCall
Exposes to the service communication layer a Java representation of: | Parlay X 3.0 Part 2: Third Party 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
Deployment artifacts | Plugin_px30_third_party_call_parlay_mpcc.jar, packaged in wlng_nt_third_party_call_px30.ear px30_third_party_call.war, packaged in wlng_at_third_party_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 the plug-in service and the plug-in instance. The plug-in instance is created when the plug-in service is started.

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

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

- Attribute: CallGetInfoReqConfig (r)
- Attribute: CallingParticipantNameMandantory
- Attribute: LegGetInfoReqConfig (r)
- Attribute: MaximumDurationEnforced
- Attribute: MultiMediaSupported
- Attribute: ChargingAllowed
- Attribute: StatusRetentionTime
- Attribute: ChangeMediaAllowed
- Attribute: MaximumParticipants
- Operation: configCallGetInfoReq
- Operation: configLegGetInfoReq
- Operation: countPendingCallSession
- Operation: getCallLegs
- Operation: getCallSessionInfo
- Operation: getCallLegSessionInfo
- Operation: listCallSessionIds

### Attribute: CallGetInfoReqConfig (r)

Read-only.

Scope: Cluster

Unit: n/a

Format: String

Indicates current configuration for the method getInfoReq operation in IpMultiPartyCall interface. The information includes:

- Supported: Boolean that indicates if the operation is supported or not.
- PCallInfoTimes: Boolean that indicates if P_CALL_INFO_TIMES tag is present or not in the operation.
- PCallInfoReleaseCause: Boolean that indicates if P_CALL_INFO_RELEASE_CAUSE tag is present in the operation.

Us Operation: configCallGetInfoReq to change these settings.

### Attribute: CallingParticipantNameMandantory

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies if the parameter `callingParticipantName` in the method `makeCallSession` defined in the Parlay X 3.0 Third Party Call interface shall be used as the original address or not.

If `callingParticipantName` is required, it must be in the form of a string which can be translated to a URI, for example `tel:123456`.

Enter:

- True if `callingParticipantName` shall be used as the originating address
- False if not

### Attribute: LegGetInfoReqConfig (r)

Read-only

Scope: Cluster

Unit: n/a

Format: String

Indicates current configuration for the method getInfoReq operation in IpCallLeg interface. The information includes:

- Supported: Boolean that indicates if the operation is supported or not
- PcallLegInfoTimes: Boolean that indicates if P_CALL_LEG_INFO_TIMES tag is present or not in the operation.
- PcallLegInfoReleaseCause: Boolean that indicates if P_CALL_LEG_INFO_RELEASE_CAUSE tag is present or not in the operation.
- PcallLegInfoAddress: Boolean that indicates if P_CALL_LEG_INFO_ADDRESS tag is present or not in the operation.
- PcallLegInfoAppInfo: Boolean that indicates ifP_CALL_LEG_INFO_APPINFO tag is present or not in the operation.

Use Operation: configLegGetInfoReq to change these settings.

### Attribute: MaximumDurationEnforced

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies if a call which duration exceeds the maximum value shall be terminated or not

Enter:

- True to terminate the call.
- False to allow the call to continue.

### Attribute: MultiMediaSupported

Scope: Cluster

Unit: n/a

Format: Boolean

Indicates if multimedia is supported

- `true` if multimedia is supported
- `False` if not

### Attribute: ChargingAllowed

Scope: Server

Unit: n/a

Format: Boolean

Specifies whether charging is allowed.

- `true` if an application is alllowed to specify charging information when creating a call session (operation `makeCallSession`).
- `False` if not.

### Attribute: StatusRetentionTime

Scope: Server

Unit: Seconds

Format: int [0-]

Specifies the length of time information about a call is stored after the call is terminated.

### Attribute: ChangeMediaAllowed

Scope: Server

Unit: n/a

Format: int Boolean

Specifies if an end user, that is, a call participant, is allowed to change the media used in the call.

- `true` if an end user is alllowed to change media for an existing call session. In order for a end user to change the media type for a given call session, this attribute must be true and the application must have allowed it when the call session was established (operation `makeCallSession`) and Attribute: MultiMediaSupported must be True.
- `False` if not.

### Attribute: MaximumParticipants

Scope: Server

Unit: n/a

Format: int [2-]

Specifies the maximum number of participants in a call.

### Operation: configCallGetInfoReq

Scope: Cluster

Configures the parameters in the getInfoReq operation in the interface IpMultiPartyCall.

Signature:

    configCallGetInfoReq(Supported: Boolean, PCallInfoTimes: Boolean, PCallInfoReleaseCause: Boolean)

Table 21-1 configCallGetInfoReq
configCallGetInfoReq
Parameter | Description
--- | ---
Supported | Specifies if the operation is supported or not by the OSA/Parlay Gateway.
PCallInfoTimes | Specifies if the P_CALL_INFO_TIMES tag shall be present in TpCallInfoType or not. Use: True to add it to TpCallInfoType False to not
PCallInfoReleaseCause | Specifies if the P_CALL_INFO_RELEASE_CAUSE tag shall be present in TpCallInfoType or not. Use: True to add it to TpCallInfoType False to not

### Operation: configLegGetInfoReq

Scope: Cluster

Configures the parameters in the getInfoReq operation in the interface IpCallLeg.

Signature:

    configLegGetInfoReq(Supported : Boolean, PCallLegInfoTimes : Boolean, PCallLegInfoReleaseCause : Boolean, PCallLegInfoAppInfo : Boolean)

Table 21-2 configLegGetInfoReq
configLegGetInfoReq
Parameter | Description
--- | ---
Supported | Specifies if the operation is supported or not by the OSA/Parlay Gateway.
PCallLegInfoTimes | Specifies if the P_CALL_LEG_INFO_TIMES tag shall be present in TpCallLegInfoType or not. Use: True to add it to TpCallLegInfoType False to not
PCallLegInfoReleaseCause | Specifies if the P_CALL_LEG_INFO_RELEASE_CAUSE tag shall be present in TpCallLegInfoType or not. Use: True to add it to TpCallLegInfoType False to not
PCallLegInfoAddress | Specifies if the P_CALL_LEG_INFO_ADDRESS tag shall be present in TpCallLegInfoType or not. Use: True to add it to TpCallLegInfoType False to not
PCallLegInfoAppInfo | Specifies if the P_CALL_LEG_INFO_APPINFO tag shall be present in TpCallLegInfoType or not. Use: True to add it to TpCallLegInfoType False to not

### Operation: getCallLegs

Scope: Cluster

Displays a list of IDs for all call legs in a call session.

Signature:

    getCallLegs(CallSessionId: String)

Table 21-3 getCallLegs
getCallLegs
Parameter | Description
--- | ---
CallSessionId | ID if the call session to list call legs for.

### Operation: getCallSessionInfo

Scope: Cluster

Displays information about a call session. This includes:

- `callSessionId`: the ID of the call session.
- `callStatus`: the current status of the call. The status is one of :

- `Established`, during call duration.
- `Terminated`, when the call has terminated but informnation is still present in the internal storage, see Attribute: StatusRetentionTime.
- `Expired`, when the call is terminated and information is no longer available.

- `originalAddress`: the originator (a-party) of the call.
- `appInstGrpId`: the application instance ID associated with the application that created the call session.
- `callRef`: the CORBA reference to the call object in the Parlay Gateway (IpMultiPartyCall).
- `srcPlugin`: the type of plug-in instance that initiated the call. The type is one of:

- ThirdPartyCall
- CallNotification
- CallDirection

Signature:

    getCallSessionInfo(CallSessionId: String)

Table 21-4 getCallSessionInfo
getCallSessionInfo
Parameter | Description
--- | ---
CallSessionId | ID if the call session to get information about.

### Operation: getCallLegSessionInfo

Scope: Cluster

Displays information about a call leg in a call session.

- `id:` the CORBA reference to the call leg object in the Parlay Gateway (IpCallLeg).
- `callSessionId`: the ID of the call session.
- `callParticipantIdentifier`: the URI identifying the terminal associated with the call leg.
- `callParticipantStatus`: the status of the call participant. The status is one of:

- `Initial`, during call setup.
- `Connected`, during call duration.
- `Terminated`, the participant has left the call.

- `callParticipantStartTime`: the time when the call participant was connected to the the call.
- `callParticipantEndTime`: the time when the call participant was disconnected from the call.
- `callParticipantDuration`: the duration of the call for the participant. Given in seconds.
- `callPariticipantTerminationCause`: the cause of the participant leaving the call. One of:

- `Noanswer`, no answer from the participant.
- `Busy`, the participant was busy (off-hook)
- `Hangup`, the participant went on-hook.
- `Notreachable`, could not reach the participant.
- `Aborted`, the call was terminated for other reason than Hangup.

- `appInstGrpId`: the application instance associated with the application that created the call session.
- `callRef`: the CORBA reference to the call object in the Parlay Gateway (IpMultiPartyCall).
- `srcPlugin`: the type of plug-in instance that initiated the call. The type is one of:

- ThirdPartyCall
- CallNotification
- CallDirection

Signature:

    getCallLegSessionInfo(CallLegSessionId: String)

Table 21-5 getCallLegSessionInfo
getCallLegSessionInfo
Parameter | Description
--- | ---
CallLegSessionId | ID if the call leg session to get information about.

### Operation: listCallSessionIds

Scope: Cluster

Displays a list of IDs for ongoing call sessions. These are the Parlay X 3.0 `callSessionIDs`.

Signature:

    listCallSessionIds()

Table 21-6 listCallSessionIds
listCallSessionIds
Parameter | Description
--- | ---
- | -

### Operation: countPendingCallSession

Scope: Server

Displays the number of ongoing call sessions for this plug-in instance.

Signature:

    countPendingCallSession()

Table 21-7 countPendingCallSession
countPendingCallSession
Parameter | Description
--- | ---
- | -

## Parlay X 2.1 Third Party Call/INAP

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

This plug-in instance uses the TietoEnator SS7 stack to connect to the network.

When configuring the SS7 connectivity, the settings in the management interface for the plug-in instance must be correlated with a sub-set of the settings in the following Stack-in-a-Box configuration files, see Configuration files and dependencies.

Configuration and management of other parts of Stack-in-a-Box are outside the scope of this descriptio.Refer to the TietoEnator SS7 product documentation.

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

### Configuration Workflow for Parlay X 2.1 Third Party Call/INAP

1. Make sure the SS7 stack is configured and up and running. You must define an INAP user for each plug-in instance.
2. Using the Management Console or an MBean browser, select the MBean detailed in Management for Parlay X 2.1 Third Party Call/INAP.
3. Configure connection information for the connection to the SS7 stack:

- Attribute: LocalSpc
- Attribute: LocalSsn
- Attribute: RemoteSpc
- Attribute: RemoteSsn
- Attribute: TSCFTimeout
- Attribute: NoAnswerTimeout
- Attribute: SccpPriority
- Attribute: SccpQualityOfService
- Attribute: InapUserId
- Attribute: Ss7Host
- Attribute: Ss7PortNumber
- Attribute: InapBindTimeout

Note: | When any of these attributes are changed, the INAP API configuration file is overwritten and the plug-in service must be restarted.

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 2.1 Third Party Call/INAP.
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 2.1 Third Party Call/INAP

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication ServicesPlugin_third_party_call_inap
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName=Plugin_third_party_call_inap Type=com.bea.wlcp.wlng.plugin.tpc.inap.management.InapTpcMBean
Network protocol plug-in service ID | Plugin_third_party_call_inap
Network protocol plug-in instance ID | Plugin_px21_third_party_call_inap
Supported Address Scheme | tel
North interface | com.bea.wlcp.wlng.px21.plugin.ThirdPartyCallPlugin
Service type | ThirdPartyCall
Exposes to the service communication layer a Java representation of: | Parlay X 2.1 Part 2: Third Party Call
Interfaces with the network nodes using: | ETSI 94 INAP CS1, ETS 300 374-1
Deployment artifacts NT EAR wlng_nt_third_party_call_px21.ear | Plugin_px21_third_party_call_inap.jar. Plugin_px21_third_party_call_sip.jar, px21_third_party_call_service.jar, and px21_third_party_call_sip.war
AT EAR: Normal wlng_at_third_party_call_px21.ear | px21_third_party_call.war and rest_third_party_call.war
AT EAR: SOAP Only wlng_at_third_party_call_px21_soap.ear | px21_third_party_call.war

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 for Parlay X 2.1 Third Party Call/INAP

None.

### Reference: Attributes and Operations for Parlay X 2.1 Third Party Call/INAP

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

- Attribute: LocalSpc
- Attribute: LocalSsn
- Attribute: RemoteSpc
- Attribute: RemoteSsn
- Attribute: TSCFTimeout
- Attribute: NoAnswerTimeout
- Attribute: SccpPriority
- Attribute: SccpQualityOfService
- Attribute: InapUserId
- Attribute: Ss7Host
- Attribute: Ss7PortNumber
- Attribute: InapBindTimeout

### Attribute: LocalSpc

Scope: Server

Unit: n/a

Format: int [0-16383] or [0-16777215], depending on standard used.

Specifies the local SCCP Signaling Point Code (SPC) served by the local SS7 stack, that is, the SS7 network address for the plug-in instance. Used as the originating SPC by the plug-in instance.

Must be correlated with the property SCCP Local SPC in the back-end configuration file for the SS7 stack.

### Attribute: LocalSsn

Scope: Server

Unit: n/a

Format: int [2-254]

Specifies the local SCCP Sub System Number, to which the plug-in instance will bind itself.

Must be correlated with the property SCCP Local SSN in the back-end configuration file for the SS7 stack.

### Attribute: RemoteSpc

Scope: Server

Unit: n/a

Format: int [0-16383] or [0-16777215], depending on standard used.

Specifies the remote SCCP Signaling Point Code (SPC). Used in the destination address.

Must be correlated with the property SCCP Remote SPC in the back-end configuration file for the SS7 stack.

### Attribute: RemoteSsn

Scope: Server

Unit: n/a

Format: int [2-254]

Specifies the remote SCCP Signaling Sub System Number (SPC). Used in the destination address.

Must be correlated with the property SCCP Remote SSN in the back-end configuration file for the SS7 stack.

### Attribute: TSCFTimeout

Scope: Server

Unit: seconds

Format: int

Specifies the timeout value for the T(SCF) timer, used for supervising call establishment. It specifies how long the plug-in instance should wait for a response from an SCP after sending a request. If the time-out value is exceeded the TCAP dialogue is aborted.

### Attribute: NoAnswerTimeout

Scope: Server

Unit: seconds

Format: int [0-2047]

Specifies the time-out value for an INAP noAnswer event. The time-out value is used towards the signaling network in INAP DpSpecificCriteria when arming the noAnswer event.

### Attribute: SccpPriority

Scope: Server

Unit: n/a

Format: int [0-3]

Specifies the SCCP priority indicator. 0 is the lowest priority and 3 is the highest priority.

### Attribute: SccpQualityOfService

Scope: Server

Unit: n/a

Format: int [0-3]

Specifies the SCCP quality of service indicator.

### Attribute: InapUserId

Scope: Server

Unit: n/a

Format: String

Specifies the user ID used by the INAP plug-in when connecting to the SS7 stack. Must be defined in the common parts configuration file, see Common parts configuration file.

### Attribute: Ss7Host

Scope: Server

Unit: n/a

Format: String

Specifies the host name or IP address of the SS7 stack. Separate the host names or IP addresses with a comma (,) if the stack is running in HA mode.Also if you are using HA mode, use this attribute to define the port number to use: for example 192.168.0.19:99, and do not use Attribute: Ss7PortNumber to specify the port number.

### Attribute: Ss7PortNumber

Scope: Server

Unit: n/a

Format: int

Specifies the port number to use in connecting to the stack.

### Attribute: InapBindTimeout

Scope: Server

Unit: milliseconds

Format: int

Specifies the stack bind timeout value.

### Configuration files and dependencies

There are a set of dependencies and settings that must be correlated between the configuration files and the configuration settings in the plug-in instance. The following files have touch-points:

- INAP API configuration file (`Plugin_px21_third_party_call_inap.properties`): see INAP API configuration file.
- SS7 back-end configuration file `(itu_ss7.cfg`): see Back-end configuration file.
- Common parts configuration file (`cp.cnf`): see Common parts configuration file.

The specific settings are explained in the sections describing the settings in the management interface for the plug-in instance and the description of the files. Figure 21-1below presents an overview of the dependencies.

Figure 21-1 Dependencies between settings in the plug-in instance and properties in the configuration files for the SS7 stack

#### INAP API configuration file

The INAP API configuration file is a configuration file for the TietoEnator JAIN INAP API library used by the plug-in instance.

This file provides the API with information on where to connect, how to bind to the stack, and values for some parameters that are not exposed in the API. If any of the properties are not set, default values are used.

The properties that are related to the interface between the plug-in instance and the stack are described in Table 21-9. See the documentation for the stack for a full description of all settings.

The file is located on the file system of the host where the plug-in instance is running; in default installations this is in the domain home directory of Oracle Communications Services Gatekeeper. The file is created and updated when an attribute is updated using the MBean for the Parlay x 2.1 Third Party Call/INAP plug-in. The plug-in service needs to be restarted for the changes to effect.

The file is named `Plugin_px21_third_party_call_inap.properties` and it is located in $DOMAIN_HOME.

Any changes to the MBean attributes causes the file to be overwritten, and hence any modifications to it are lost.

Table 21-8 INAP API properties used
Property | Comments
--- | ---
priority | SCCP Message priority.
quality-of-service | SCCP QoS.
inap-user-id | The common parts module ID used by the plug-in instance. See Common parts configuration file. Either INAPUP or any of the USERxx IDs are to be used by the plug-in instance. The numeric identifier of the ID shall be used, not the ID itself (as used in the common parts configuration file). The module ID numeric values can be found in `/opt/ss7/ss7_ITU/include/portss7.h` in an installed stack. USER01 has decimal value 40, USER02 41, and so on.
ss7host | The host name or IP-address of the host running the SS7 back-end, that is, the address to which the SS7_BASE module ID is bound in the common parts configuration file. See Common parts configuration file. If several SS7 back-ends are used, either in high-availability mode or horizontally distributed mode, enter the host name (or IP-address) for the servers in a comma separated list.
port-number | The port number to which the SS7_BASE module ID is bound in the common parts configuration file.
bind-timeout | Time to wait for bind response before a bind operation is considered a failure. Unit: milliseconds.
heartbeat-interval | Heartbeat interval between the INAP API and the common parts module. Must correspond to the MSGHBRATE and MSGHBLOST properties defined in the common parts configuration file. See Common parts configuration file.
Note: | This property is not generated from the settings in the MBean of the Parlay X 2.1 Third Party Call/INAP plug-in. The absence of the property means that no heartbeats are sent. If heartbeats are used, this property must be added manually in the configuration file. If used the recommended value is MSGHBRATE times MSGHBLOST. Any changes to the MBean attributes causes the file to be overwritten, and hence this setting is lost.
Unit: milliseconds.

Listing 21-1 Example INAP JAIN API Configuration file

    local-ssn: 254

    priority: 0

    quality-of-service: 0

    trace-level: 0

    inap-user-id: 40

    ss7host: 192.168.20.1,192.168.20.2

    port-number: 7001

    bind-timeout: 5000

#### Common parts configuration file

The SS7 Common parts configuration file is a configuration file specifying the interprocess communication for the SS7 stack, including users of the stack. The plug-in instance acts as user of the stack via the INAP API. The dependencies to the plug-in instance and the stack is described in Table 21-9. All other settings are related to the stack itself: see the documentation for the stack for a description of these settings.

The file is located on the file system of the host running the back-end part of the SS7 stack. In default installations this is in`/opt/ss7/ss7_ITU/etc/cp.cnf`.

Table 21-9 Common parts configuration file properties with dependencies to plug-in instance settings
Property | Comments
--- | ---
MSGIPA | There must be one MSGIPA entry per plug-in instance. First, choose a Message Port owner ID (MP OwnerID). Use one of the following: INAPUP USER01 USER02 USER03 USER04 USER05 USER06 USER07 USER08 USER09 USER10 MP OwnerID shall correspond to inap-user-id specified in Attribute: InapUserId The IP-address (or host name) with TCP port number must correspond to the host where the plug-in instance is deployed. Make sure there is a MSGINTERACT entry per MP OwnerID. Instances of MP OwnerIDs are not supported. Example: MSGIPA=USER01,192.168.20.2:6701 10.10.10.11:6701
MSGHBLOST | Must correspond to Attribute: LocalSpc.
MSGHBRATE | Must correspond to heartbeat-interval in INAP API configuration file

#### Back-end configuration file

The back-end configuration file contains the configuration of the SS7 back-end stack layers. Each stack layer has a dedicated section in this file, and it is where, for example, SS7 network routing and protocol timers are configured. The dependencies between the plug-in instance and the stack are described in Table 21-9. All other settings are related to the stack itself: see the documentation for the stack for a description of these settings.

The file is located on the file system of the host running the back-end part of the SS7 stack, in default installations this is in `/opt/ss7/ss7_ITU/etc/ss7_itu.cnf`

Table 21-10 Back-end configuration file properties with dependencies to plug-in instance settings
Property | Comments
--- | ---
INAP-T (bind) | Must correspond to Attribute: InapBindTimeout given in Plugin_third_party_call_inap.
SCCP-LOCAL SPC | Must correspond to Attribute: LocalSpc given in Plugin_third_party_call_inap.
SCCP-LOCAL SSN | Must correspond to Attribute: LocalSsn given in Plugin_third_party_call_inap.
SCCP-REMOTE SPC | Must correspond to Attribute: RemoteSpc given in Plugin_third_party_call_inap.
SCCP-REMOTE SSN | Must correspond to Attribute: RemoteSsn given in Plugin_third_party_call_inap.

## Parlay X 2.1 Third Party Call/SIP

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

Parlay X 2.1 Third Party Call/SIP uses two parts for SIP connectivity, a part that executes a 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.

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

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

1. Using the Management Console or an MBean browser, select the MBean detailed in Properties for Parlay X 2.1 Third Party Call/SIP.
2. Configure behavior of the network protocol plug-in instance:

- Attribute: ChargingAllowed
- Attribute: ControllerURI
- Attribute: ISCRouteURI
- Attribute: MaximumCallLength
- Attribute: StatusRetentionTime

3. 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 Third Party Call/SIP.
4. 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 Third Party Call/SIP

None.

### Properties for Parlay X 2.1 Third Party Call/SIP

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication ServicesPlugin_third_party_call_sip
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName=Plugin_px21_third_party_call_sip Type=com.bea.wlcp.wlng.plugin.tpc.sip.management.TPCMBean
Network protocol plug-in service ID | Plugin_px21_third_party_call_sip
Network protocol plug-in instance ID | Plugin_px21_third_party_call_sip
Supported Address Scheme | sip
North interface | com.bea.wlcp.wlng.px21.plugin.ThirdPartyCallPlugin
Service type | ThirdPartyCall
Exposes to the service communication layer a Java representation of: | Parlay X 2.1 Part 2: Third Party Call
Interfaces with the network nodes using: | SIP: Session Initiation Protocol, RFC 3261
Deployment artifacts | px21_third_party_call_service.jar, Plugin_px21_third_party_call_sip.jar and Plugin_px21_third_party_call_sip.war, packaged in wlng_nt_third_party_call_px21.ear px21_third_party_call.war, packaged in wlng_at_third_party_call_px21.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.

### Reference: Attributes and Operations for Parlay X 2.1 Third Party Call/SIP

Below is a list of attributes for configuration and maintenance:

- Attribute: ChargingAllowed
- Attribute: ControllerURI
- Attribute: ISCRouteURI
- Attribute: ISCRouteURI
- Attribute: MaximumCallLength
- Attribute: StatusRetentionTime

### Attribute: ChargingAllowed

Scope: Cluster

Unit: n/a

Format: boolean

Specifies if charging is allowed or not. That is, if the parameter charging is allowed to be present in a request from an application.

### Attribute: ControllerURI

Scope: Cluster

Unit: n/a

Format: 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 will be used to establish the call. In this case, the call appears to the callee to come from the caller

### Attribute: ISCRouteURI

Scope: Cluster

Unit: n/a

Format: String in URI format

Specifies the URI of the IMS service control route.

### Attribute: MaximumCallLength

Scope: Cluster

Unit: minutes

Format: int

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

### Attribute: StatusRetentionTime

Scope: Cluster

Unit: minutes

Format: int

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