Skip Headers
Oracle® Communications Service Broker Processing Domain Configuration Guide
Release 6.0

Part Number E23525-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

30 Configuring IM-PSX GSM MAP

The following sections describe how to configure IM-PSX using the Service Broker Administration Console and Java MBeans.

Configuring IM-PSX MAP with the Administration Console

This section describes how to configure IM-PSX module instances using the Service Broker Administration Console.

To access the IM-PSX Configuration screen:

  1. In the domain navigation pane, expand OCSB.

  2. Expand Processing Tier.

  3. Expand Interworking Modules.

    A list of currently deployed Interworking Modules is displayed.

  4. From the module list, select the module instance that you want to configure.

    The IM-PSX configuration pane contains the tabs described in Table 30-1.

Table 30-1 IM-PSX Configuration Subtabs

Tab Description

General

Enables you to configure general parameters for an Interworking Module instance.

See "Configuring General Parameters" for more information.

SIP Subscription

Enables you to configure the SIP SUBSCRIBE and SIP NOTIFY interface that IM-PSX exposes to SIP applications.

See "Configuring the SIP Subscription Parameters" for more information.

Map Handling

Enables you to configure the IM-PSX MAP interface.

See "Configuring the Map Handling Parameters" for more information.

TCAP

Enables you to set up parameters of the IM TCAP layer.

See "Configuring TCAP Parameters" for more information.

Monitoring

Enables you to define the way that Runtime MBeans and notifications operate.

See "Configuring Monitoring Parameters" for more information.


Configuring General Parameters

The General tab displays the protocol variant that is used to encode and decode SS7 messages and enables you to specify an alias for an IM instance.

Table 30-2 describes the configuration parameter in the General tab.

Table 30-2 IM-PSX General Parameter

Name Type Description

Alias

STRING

Specifies the alias of the IM's SS7 address. The alias is an index to the SS7 SSU configuration, where the IM's SS7 address is configured. The IM uses this alias to set the origination field of outgoing SS7 messages. This ensures that further session messages arrive to this IM instance.

Plugin

STRING

Specifies the protocol variant used over the SS7 interface. It informs the IM which plug-in (class) to use to encode and decode SS7 messages.


Configuring the SIP Subscription Parameters

The SIP Subscription tab enables you to configure the SIP SUBSCRIBE and SIP NOTIFY interface that IM-PSX exposes to SIP applications.

The SIP Subscription tab contains the subtabs described in Table 30-3.

Table 30-3 SIP Subscription Tabs

Subtab Description

General

Enables you to set up a pending NOTIFY message and define a PSX SIP domain.

See "General" for more information.

Accept Header

Enables you to select allowed values to which a SIP application can set the Accept header.

See "Accept" for more information.


General

The General subtab enables you to set up a pending NOTIFY message and define a PSX SIP domain.

Table 30-4 describes the configuration parameters on the General subtab.

Table 30-4 General Parameters

Name Type Description

Generate Pending NOTIFY

BOOL

Specifies whether or not Service Broker needs to generate a SIP NOTIFY message with the Subscription-State set to pending together with an empty body when a new subscription is created and the terminal state is still unknown.

Possible values:

  • True

  • False

Default value: True

PSX SIP Domain

STRING

Specifies a SIP domain name for IM-PSX.

The application can use this value in the domain part of the RequestURI header and the To header to refer a request to a specific SS7 entity whose alias is configured in DefaultSS7EntityAlias.

Default value: ocsb-psx.net


Accept

The Accept subtab enables you to select formats of the body message that IM-PSX supports.

The Accept subtab contains a table in which each row represents one of the formats that SIP applications are allowed to set in the Accept header of SIP SUBSCRIBE messages. When setting up a format, you need to specify the values described in Table 30-5.

Table 30-5 Accept Header Value Fields

Field TYPE Description

Name

STRING

Specifies the name of the format. This field is read-only.

Allowed

BOOL

Specifies whether IM-PSX supports the respective SIP NOTIFY message body format. When the format is supported, SIP applications can set this format in the Accept header of SIP SUBSCRIBE messages.

Possible values:

  • True

  • False

Default value: True


Configuring the Map Handling Parameters

The Map Handling tab enables you to configure the IM-PSX MAP interface. Table 30-6 describes the configuration parameters in the Map Handling tab.

Table 30-6 Map Handling Parameters

Name Type Description

Default SS7 Entity Alias

STRING

Specifies an SS7 entity to which the IM-PSX sends a MAP request. The parameter defines an alias for one of the SCCP addresses configured in the SS7 SSU. The parameter is used only when the address is not provided in the To header of the SIP SUBSCRIBE message.

Default value: hlr

gsmSCF Address

STRING

Specifies a value to be set in the gsmSCF-Address parameter of the MAP request. The parameter defines the address that identifies an IM-PSX in a mobile network.

Default value: Unknown

gsmSCF Nature of Address

STRING

Specifies the NatureOfAddress of the gsmSCF-Address parameter in the MAP request

MSISDN NatureOfAddress

STRING

Specifies the NatureOfAddress of the MSISDN parameter that IM-PSX sets in the MAP operation. Service Broker uses the NatureOfAddress specified in this parameter only if the NatureOfAddress is not specified in the RequestURI header of the SIP SUBSCRIBE message.

Possible values:

  • NETWORK_SPECIFIC

  • SUBSCRIBER_NUMBER

  • UNKNOWN

  • NATIONAL

  • INTERNATIONAL

Default value: UNKNOWN

IM-PSX also uses this parameter to set the gsmScfAddressNoa

Default Numbering Plan

STRING

Specifies a default numbering plan used to set the MSISDN and gsmSCF-Address in the MAP request.

Possible values:

  • ISDN

  • DATA

  • TELEX

Default value: ISDN


Configuring TCAP Parameters

The TCAP subtab enables you to set up the parameters of the TCAP layer.

Table 30-7 describes configuration parameters in the TCAP subtab.

Table 30-7 TCAP Parameters

Name Type Description

Class4 Default Timeout in Seconds

INT

Specifies the time period in seconds that the IM waits for a possible REJECT. The timer starts when sending INVOKE for class 4 operations.

Default value: 5 seconds.

Reject Timeout in Seconds

INT

Specifies the time period in seconds that the IM waits for a possible REJECT. The timer starts when sending INVOKE for class 1-3 operations.

Activate Invoke Alarm in Application Layer

BOOL

When the TCAP layer receives an INVOKE, it triggers back P-ABORT if there is no response. The waiting time period for response is configured in the encoding library.

The Activate Invoke Alarm in Application Layer parameter specifies whether or not to activate this timer.

Possible values:

  • True

  • False

Default value: False.

Application Part Guard Timer

INT

Specifies the PSM timer, which is a timer for incoming operations.

The PSM timer defines the maximum time that the application (TC-User) has to respond to incoming INVOKE messages.

Result Split Length

INT

Specifies the maximum length of the TCAP RESULT message. When the actual length of the message exceeds the specified value, the message is split.


Configuring Monitoring Parameters

The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-PSX. For more information about configuring monitoring, see "Configuring Monitoring with the Administration Console".

Configuring IM-PSX MAP with Java MBeans

Service Broker provides a set of MBeans with attributes and operations for configuring the IM-PSX through JMX. Figure 30-1 shows the hierarchy of the IM-PSX MBeans.

Figure 30-1 IM-PSX MBeans Hierarchy

IM-PSX MBeans Hierarchy

The following sections provide reference information for the IM-PSX configuration MBeans.

Note:

MBeans covered in this guide might include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.

The following MBeans are common for all components of Service Broker and described in "Configuring Monitoring with Java MBeans":


ImpsxMap3MBean

ImpsxMap3MBean is the root MBean for the IM-PSX MAP phase 3 configuration. It provides reference to other configuration MBeans in the hierarchy, and does not expose any additional specific configuration.

Factory Method

Created automatically.

Attributes

None

Operations

ObjectName getSipSubscriptionMBean()

Gets the qualified object name of the SipSubscriptionMBean instance

ObjectName getMapHandlingMBean()

Gets the qualified object name of the MapHandlingMBean instance

ObjectName getMonitoringMBean()

Gets the qualified object name of the MonitoringMBean instance


SipSubscriptionMBean

SipSubscriptionMBean enables you to configure the SIP SUBSCRIBE and SIP NOTIFY interface that the IM-PSX exposes to SIP applications.

Factory Method

Created automatically.

Attributes

For more information on these attributes, see Table 30-4.

Operations

ObjectName getAccptHeadersMBean()

Gets the qualified ObjectName of the AccptHeadersMBean instance


AcceptHeadersMBean

AcceptHeadersMBean is a set of AcceptHeaderMBean instances. Each instance represents one SIP NOTIFY message body format that IM-PSX supports. These are the formats that SIP applications are allowed to set in the Accept header of SIP SUBSCRIBE messages.

Factory Method

Created automatically.

Attributes

None

Operations

ObjectName getAcceptHeaderMBean()

Gets the qualified object name of a specific AcceptHeaderMBean instance

ObjectName getAcceptHeaderMBeans()

Gets a list of qualified object names of all AcceptHeaderMBean instances


AcceptHeaderMBean

Each AcceptHeaderMBean instance represents one SIP NOTIFY message body format that IM-PSX can support. The format name is visible in the AcceptHeaderMBean registration name.

Factory Method

Created automatically.

Attributes

Allowed

For more information on this attribute, see Table 30-5.

Operations

None


MapHandlingMBean

MapHandlingMBean enables you to configure the IM-PSX MAP interface.

Factory Method

Created automatically.

Attributes

For more information on these attributes, see Table 30-6.

Operations

None


TcapMBean

TcapMBean enables you to configure the TCAP layer of the module.

Factory Method

Created automatically

Attributes

For more information on these attributes, see Table 30-7.

Operations

None