This chapter describes how to set up an IM-SSF AIN 0.2 interworking module.
The process of IM-SSF AIN 0.2 setup requires the following:
Adding an IM-SSF AIN 0.2 to your Oracle Communications Service Controller deployment. You can add as many modules of type IM-SSF AIN 0.2 as you need. See "Adding an IM-SSF AIN 0.2 to the Service Controller Deployment" for more information.
Configuring the IM-SSF AIN 0.2. See "Configuring an IM-SSF AIN 0.2" for more information.
To add an IM-SSF AIN 0.2:
In the domain navigation pane, expand the OCSB node.
Expand the Processing Tier node.
Expand the Interworking Modules node.
Select IM Management.
On the bottom of the IM Management pane, click New.
In the New window, fill out the fields as follows:
In the Type list, select IMSSFAIN02.
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 Controller displays the error message and prompts you to enter a different name.
Click OK.
In the notification window that reminds you to commit the changes, click OK.
To add the new IM-SSF AIN 0.2 to your deployment, in the Change Center pane, click Commit.
A new module of type IM-SSF AIN 0.2 is now added to your Service Controller deployment. The new module is displayed in the domain navigation pane under the Interworking Modules node.
To configure an IM-SSF AIN 0.2:
In the Change Center, click Lock & Edit.
In the domain navigation pane, under the Interworking Modules node, select the newly added IM-SSF AIN 0.2.
The IM-SSF AIN 0.2 configuration pane contains the subtabs described in Table 17-1.
Table 17-1 IM-SSF AIN 0.2 Configuration Subtabs
Subtab | Description |
---|---|
General |
Enables you to configure general parameters for an Interworking Module instance. See "Configuring General Parameters" for more information. |
Call Handling |
Enables you to configure how the IM-SSF handles calls. See "Configuring Call Handling Parameters" for more information. |
Subscriber Data |
Enables you to define IN triggers that the IM-SSF invokes towards the SCP above. See "Configuring Subscriber Data Parameters" for more information. |
Operation Propagation |
Enables you to define whether the IM-SSF processes operations on its own or propagates these operations to another module. See "Configuring Operation Propagation Parameters" for more information. |
Media Resources |
Enables you to set up the media resources that Service Controller uses to play announcements. See "Configuring Media Resources Parameters" for more information. |
TCAP |
Enables you to set up the TCAP layer of the IM-SSF. See "Configuring TCAP Parameters" for more information. |
Monitoring |
Enables you to define how Runtime MBeans and notifications operate. See "Configuring Monitoring Parameters" for more information. |
The General subtab displays the protocol variant that is used to encode / decode SS7 messages and enables you to specify an alias for an Interworking Module instance.
Table 17-2 describes the configuration parameters on the General subtab.
Name | Type | Description |
---|---|---|
Alias |
STRING |
Specifies an alias of the IM instance. Using this alias, the SS7 SSU recognizes the instances of the IMs to which incoming messages should be routed. For more information on how the SS7 SSU uses aliases and how to configure incoming routing in the SS7 SSU, see the discussion on configuring the SS7 Signaling Server Unit for SIGTRAN in Service Controller Signaling Server Units Configuration Guide. |
Plugin |
STRING |
Specifies the protocol variant used over the SS7 interface. It informs the IM which plug-in (class) to use to enclode / decode SS7 messages. |
The Call Handling subtab enables you to define how the IM-SSF handles calls.
Table 17-3 describes configuration parameters on the Call Handling subtab.
Table 17-3 IM-SSF AIN 0.2 Call Handling Parameters
Name | Type | Description |
---|---|---|
IM-SSF Mode of Operation |
STRING |
Specifies the IM-SSF mode of operation. Possible values:
Default value: DYNAMIC |
Session Case |
STRING |
Specifies how the IM-SSF treats sessions that arrive on the southbound interface, from the OE. Possible values:
Default value: DYNAMIC |
Tssf Duration in Seconds |
INT |
Specifies the value, in seconds, of the IM-SSF Tssf timer. Default value: 20 |
Tssf User Interaction Duration in Seconds |
INT |
Specifies the value, in seconds, of the IM-SSF Tssf timer. This parameter is used when the IM-SSF is in the middle of interaction with a media resource. Default value: 1200 |
IM-SSF Media Capability |
BOOL |
Specifies whether or not the underlying network supports IP/SRF/MRF. This determines if the IM-SSF can handle media-related operations, such as EstablishTemporaryConnection or ConnectToResource. Possible values:
Default value: True |
Body Encoding Format |
STRING |
Specifies the method that the IM-SSF uses to encode IN parameters in the body of a SAL message. Possible options:
Default value: NONE |
NatureOfNumber of calledPartyID |
STRING |
Specifies the NatureOfNumber value of the calledPartyID/collectedAddressInfo fields that IM-SSF sets when invoking a trigger message towards the SCP. Trigger messages:
Possible values:
Default value: NATIONAL |
NumberingPlan of calledPartyID |
STRING |
Specifies the NumberingPlan value of the calledPartyID/collectedAddressInfo fields that IM-SSF sets when invoking a trigger message towards the SCP. Trigger messages:
Possible values:
Default value: ISDN |
NatureOfNumber of callingPartyID |
STRING |
Specifies the NatureOfNumber value in the CallingPartyID field that IM-SSF sets when invoking trigger message towards the SCP. Trigger messages:
Possible values:
Default value: NATIONAL |
NumberingPlan of callingPartyID |
STRING |
Specifies the NumberingPlan value in the CallingPartyID field that IM-SSF sets when invoking trigger message towards the SCP. Trigger messages:
Possible values:
Default value: ISDN |
ScreeningIndicator of callingPartyID |
STRING |
Specifies the ScreeningIndicator value in the CallingPartyID field that IM-SSF sets when invoking trigger message towards the SCP. Trigger messages:
Possible values:
Default value: USER_PROVIDED_NOT_VERIFIED |
User ID |
STRING |
Specifies the value that IM-SSF sets in the userID field when invoking trigger message towards the SCP. Trigger messages:
Default value: -1 |
BearerCapability |
STRING |
Specifies the value that IM-SSF sets in the bearerCapability field when invoking trigger message towards the SCP. Trigger messages:
Possible values:
Default value: SPEECH |
The Subscriber Data subtab enables you to define IN triggers that IM-SSF invokes towards the SCP above.
The table on the Subscriber Data subtab displays the rules for invoking triggers. Each row represents one rule. When defining a new rule, you need to specify the fields described in Table 17-4.
Table 17-4 IM-SSF AIN 0.2 Subscriber Data Fields
Name | Type | Description |
---|---|---|
Name |
STRING |
A unique identifier. |
DN |
STRING |
Specifies a condition on session DN. When the condition is met, IM-SSF invokes triggers towards the SCP. To apply a rule for all DNs, set this parameter to Default. |
SCP Address Alias |
STRING |
Specifies the SCP to which IM-SSF invokes a trigger. This is an alias to one of the SCCP addresses specified in the SS7 SSU configuration. |
Default Call Handling |
STRING |
Specifies how IM-SSF handles a call when a signal between IM-SSF and SCP fails (that is, invokes a trigger towards the failed SCP). Possible values:
Default value: CONTINUE_CALL |
TDP List |
STRING_LIST |
Specifies a list of TDPs that must be triggered. Each trigger is specified in the following format: id=type where: id is one of the following
type is one of the following:
Separate multiple TDPs with a comma. For example: 3607=R, 3616=N |
The Operation Propagation parameters subtab enables you to define whether the IM-SSF processes operations on its own or propagates these operations to another module.
The table on the Operation Propagation subtab displays a list of operations. Each row represents one operation for which you define whether IM-SSF processes this operation or propagates the operation to another module. When configuring a new operation, you need to specify the fields described in Table 17-5.
Table 17-5 IM-SSF AIN 0.2 Operation Propagation
Name | Type | Description |
---|---|---|
Name |
STRING |
Specifies a unique identifier. |
Operation |
STRING |
Specifies an operation. Possible values:
|
Module name |
STRING |
Specifies a name of a module instance to which an operation is propagated. |
Enable Propagation |
BOOL |
Specifies whether IM-SSF processes operations on its own or propagates a request to the session control layer. Possible values:
Default value: True |
The Media Resources subtab enables you to define the media resources that the SSP can connect in order to play announcements.
The table in the Media Resources subtab displays the media resources that are used to play announcements. Each row represents one media resource. When defining a new media resource, you need to specify the fields described in Table 17-6.
Table 17-6 IM-SSF AIN 0.2 Media Resource Definition Fields
Name | Type | Description |
---|---|---|
Name |
STRING |
Specifies a name of the media resource. |
Alias |
STRING |
Specifies a unique identifier that applications use to instruct IM-SCF which media resource to connect in order to play announcements. Alias is used by IM-SCF to lookup for media resource details in this table. Aliases are defined in a URI format. For example: mrf.network@domain.com. |
Announcement Operation |
INT |
Specifies which operation IM-SCF triggers towards the switch-based media resource. Possible values:
Default value: 0 |
Disconnect Flag |
BOOL |
Specifies whether or not to set the DisconnectFlag in SendToResource operation. Possible values:
Default value: Yes |
Answer Indication |
BOOL |
Specifies whether a switch sends Answer message to the calling party upon connection to the media resource. Possible values:
Default value: Yes |
The TCAP subtab enables you to set up parameters of the IM TCAP layer.
Table 17-7 describes configuration parameters on the TCAP subtab.
Name | Type | Description |
---|---|---|
Class4 Default Timeout in Seconds |
INT |
Specifies the time period in seconds that the IM waits for possible REJECT. The timer starts when sending INVOKE for class 4 operations. Default value: 5 |
Reject Timeout in Seconds |
INT |
Specifies the time period in seconds that the IM waits for possible REJECT. The timer starts when sending INVOKE for class 1-3 operations. Default value: 1000 |
Application Part Guard Timer |
INT |
Specifies the PSM timer, which is a timer for incoming operations. The PSM timer defines the maximum time in seconds that the application (TC-User) has to respond to incoming INVOKE messages. Default value: 200 |
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 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:
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. Default value: 512 |
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-SSF. For more information about configuring monitoring, see "Configuring Service Controller Monitoring" in "Monitoring Service Controller Using Runtime MBeans" in Service Controller System Administrator's Guide.