31 Configuring IM-PSX ANSI-MAP

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

Configuring IM-PSX ANSI-MAP with the Administration Console

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

To access the IM-PSX ANSI-MAP Configuration screen:

In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Expand Interworking Modules.

A list of currently deployed Interworking Modules is displayed.
From the module list, select the module instance that you want to configure.

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

Table 31-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 31-2 describes the configuration parameter in the General tab.

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

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.

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

Table 31-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".

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".

General

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

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

Table 31-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

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

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 31-5.

Table 31-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

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 31-6 describes the configuration parameters in the Map Handling tab.

Table 31-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 31-7 describes configuration parameters in the TCAP subtab.

Table 31-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 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.
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 ANSI-MAP with Java MBeans

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

Figure 31-1 IM-PSX MBeans Hierarchy

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

Note:

MBeans described in this guide may 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":

MonitoringGeneralMBean
ThresholdCrossedNotificationRulesMBean
ThresholdCrossedNotificationRuleMBean
StateChangedNotificationRulesMBean
StateChangedNotificationRuleMBean

ImpsxAnsiMBean

ImpsxAnsiMBean is the root MBean for the IM-PSX ANSI-MAP configuration. It provides reference to other configuration MBeans in the hierarchy, and does not expose any specific configuration in addition.

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

GeneratePendingNotify
PsxSipDomain

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

Operations

ObjectName getAccptHeadersMBean()

Gets the qualified ObjectName of the AccptHeadersMBean instance

AcceptHeadersMBean

AcceptHeadersMBean is a set of AcceptHeaderMBean instances, each 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 may 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 31-5.

Operations

None

MapHandlingMBean

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

Factory Method

Created automatically.

Attributes

DefaultSs7EntityAlias
LocationOperation
HlrNotifyWhenAvailable
SearchServiceID
MdnNatureOfAddress

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

Operations

None

TcapMBean

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

Factory Method

Created automatically

Attributes

Class4DefaultTimeout
RejectTimeoutInSeconds
ActivateInvokeAlarmInApplicationLayer
ApplicationPartGuardTimer
ResultSplitLength

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

Operations

None