Skip Headers
Oracle® Communications Service Broker Modules Configuration Guide
Release 6.1

Part Number E29454-01
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
PDF · Mobi · ePub

29 Setting Up IM-PSX ANSI-MAP

This chapter describes how to set up an IM-PSX ANSI-MAP interworking module.

About IM-PSX ANSI-MAP Setup

The process of IM-PSX ANSI-MAP setup requires the following:

  1. Adding an IM-PSX ANSI-MAP to your Oracle Communications Service Broker deployment. You can add as many modules of type IM-PSX ANSI-MAP as you need. See "Adding an IM-PSX ANSI-MAP to the Service Broker Deployment" for more information.

  2. Configuring the IM-PSX ANSI-MAP. See "Configuring an IM-PSX ANSI-MAP" for more information.

Adding an IM-PSX ANSI-MAP to the Service Broker Deployment

To add an IM-PSX ANSI-MAP:

  1. In the domain navigation pane, expand the OCSB node.

  2. Expand the Processing Tier node.

  3. Expand the Interworking Modules node.

  4. Select IM Management.

  5. On the bottom of the IM Management pane, click New.

  6. In the New window, fill out the fields as follows:

    • In the Type list, select IMPSXANSIMAP.

    • In the Version list, select the required version.

    • In the Name field, enter a name for this module as it should appear in the list of modules. In this field, you can only use lower case letters (a-z), upper case letters (A-Z), numbers (0-9), and underscores (_). If you attempt to use a character which is not allowed, Service Broker displays the error message and prompts you to enter a different name.

  7. Click OK.

  8. In the notification window that reminds you to commit the changes, click OK.

  9. To add the new IM-PSX ANSI-MAP to your deployment, in the Change Center pane, click Commit.

    A new module of type IM-PSX ANSI-MAP is now added to your Service Broker deployment. The new module is displayed in the domain navigation pane under the Interworking Modules node.

Configuring an IM-PSX ANSI-MAP

To configure an IM-PSX ANSI-MAP:

  1. In the Change Center, click Lock & Edit.

  2. In the domain navigation pane, under the Interworking Modules node, select the newly added IM-PSX ANSI-MAP.

    The configuration screen of the IM-PSX ANSI-MAP contains the tabs described in Table 29-1.

    Table 29-1 IM-PSX ANSI-MAP Configuration Subtabs

    Tab Description

    General

    Enables you to specify an alias 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 ANSI-MAP interface.

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

    TCAP

    Enables you to set up parameters of the 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 enables you to specify an alias for an Interworking Module instance.

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

Table 29-2 IM-PSX General Parameter

Name Type Description

Alias

STRING

Specifies an internal Service Broker alias given to an IM-PSX instance.

This alias is used in the SSU configuration, in the Incoming Routing Rules tab to specify routing rules towards this IM-PSX instance.

Plugin

STRING

Specifies the protocol ASE plugin class name.

Default value: com.convergin.common.ase.plugin.oss.ansi.map.is41e.OssIs41ePlugin


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 29-3.

Table 29-3 SIP Subscription Tabs

Subtab Description

General

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

For more information, see "General".

Accept Header

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

For more information, see "Accept Header".


General

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

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

Table 29-4 General Parameters

Name Type Description

Generate Pending NOTIFY

BOOL

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

Possible values:

  • TRUE

  • FALSE

Default value: TRUE

PSX SIP Domain

STRING

Specifies a 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 Header

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 a format 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 29-5.

Table 29-5 Accept Header Value Fields

Field TYPE Description

Name

STRING

Specifies a format in which a in-dialog and out-of-dialog SIP NOTIFY message body is encoded. This is a read-only field.

IM-PSX can support the following formats:

  • application/pidf+xml

  • application/ansi-is41e+ber

  • application/ansi-is41e+xml

You can define which of these formats IM-PSX supports.

Allowed

BOOL

Specifies whether IM-PSX supports each of the formats displayed in the Name column. When it is supported, SIP applications can set the 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 29-6 describes the configuration parameters in the Map Handling tab.

Table 29-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 to one of the SCCP addresses configured in the SS7 SSU. The parameter is used only when the To header domain part of a SIP SUBSCRIBE message equals to the PSX domain.

Default value: hlr

Location Operation

STRING

Specifies a default ANSI-MAP operation that the IM-PSX sends to an HLR.

Possible values:

  • SMSReq

  • Search

Default value: Search

HLR Notify When Available

BOOL

Specifies whether or not an HLR sends SMSNotification to the IM-PSX when a mobile subscriber who was previously unavailable becomes available again. This parameter is set in the SMSReq operation that Service Broker sends to an HLR.

Possible values:

  • TRUE

    The HLR sends an SMSNotification message to IM-PSX when a subscriber becomes available again. The notification contains information about the subscriber's

  • FALSE

    The HLR does not send a notification when a subscriber becomes available again.

Default value: True

To enable IM-PSX to forward an SMSNotification to the application server that requested the information, perform the following actions:

  • In the configuration settings of IM-ASF, define the AS to which IM-PSX needs to forward an SMSNotification.

  • Go to the General tab in the OE Configuration screen and set the Subscriber Profile parameter to OlpLssInfoReceiver.

  • In the orchestration profile, in addition to the entry for SUBSCRIBE messages, add an entry for NOTIFY messages.

Search Service ID

STRING

Specifies the identifier of a service of the AS that requests information about a mobile subscriber

MDN NatureOfAddress

STRING

Specifies the NatureOfAddress of the MDN parameter that IM-PSX sets in ANSI-MAP operations. 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:

  • NATIONAL

  • INTERNATIONAL

Default value: NATIONAL


Configuring TCAP Parameters

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

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

Table 29-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.

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.

Activate Invoke Alarm in Application Layer

BOOL

When the TCAP layer receives an INVOKE, it triggers back PABORT if there is no response. The waiting time period for a 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.

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 Service Broker Monitoring" in "Monitoring Service Broker Using Runtime MBeans" in Oracle Communications Service Broker System Administrator's Guide.