This chapter describes how to set up an IM-SSF CAP Phase 3 interworking module.
The process of IM-SSF CAP Phase 3 setup requires the following:
Adding an IM-SSF CAP Phase 3 to your Oracle Communications Service Controller deployment. You can add as many modules of type IM-SSF CAP Phase 3 as you need. See "Adding an IM-SSF CAP Phase 3 to the Service Controller Deployment" for more information.
Configuring the IM-SSF CAP Phase 3. See "Configuring an IM-SSF CAP Phase 3" for more information.
To add an IM-SSF CAP phase 3:
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 IMSSFCAP3.
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 CAP phase 3 to your deployment, in the Change Center pane, click Commit.
A new module of type IM-SSF CAP phase 3 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 CAP Phase 3:
In the Change Center, click Lock & Edit.
In the domain navigation pane, under the Interworking Modules node, select the newly added IM-SSF CAP Phase 3.
The IM-SSF CAP Phase 3 configuration pane contains the subtabs described in Table 12-1.
Table 12-1 IM-SSF CAP Phase 3 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. |
Charging |
Enables you to configure functionality related to charging operations. See "Configuring Charging 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. |
SMS Handling |
Enables you to define how the IM-SSF handles SMS messages. See "Configuring SMS Handling" 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 12-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 encode / decode SS7 messages. |
The Call Handling subtab enables you to define how IM-SSF handles calls.
Table 12-3 describes configuration parameters on the Call Handling subtab.
Table 12-3 IM-SSF CAP Phase 3 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 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 |
Nature of Address of Called Party Number |
STRING |
Specifies how to set the NatureOfAddress of the CalledPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: NATIONAL |
Internal Network Number Indicator of Called Party Number |
BOOL |
Specifies how to set the InternalNetworkNumberIndicator of the CalledPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: TRUE |
Numbering Plan Indicator of Called Party Number |
STRING |
Specifies how to set the NumberingPlanIndicator of the CalledPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: ISDN |
Nature of Address of Calling Party Number |
STRING |
Specifies how to set the NatureOfAddress of the CallingPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: NATIONAL |
Number Incomplete Indicator of Calling Party Number |
BOOL |
Specifies how to set the IncompleteIndicator of the CallingPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: True |
Numbering Plan Indicator of Calling Party Number |
STRING |
Specifies how to set the NumberingPlanIndicator of the CallingPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: ISDN |
Screening Indicator of Calling Party Number |
STRING |
Specifies how to set the NumberingPlanIndicator of the CallingPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: USER_PROVIDED_NOT_VERIFIED |
Calling Party Category |
STRING |
Specifies how to set the CallingNumberCategory of the CallingPartyNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: LANGUAGE_ENGLISH |
Type of Number of Called Party Number |
STRING |
Specifies how to set the TypeOfNumber of the CalledPartyBCDNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: NationalNumber |
Numbering Plan Indicator of Called Party BCD Number |
STRING |
Specifies how to set the NumberingPlanIndicator of the CalledPartyBCDNumber. This parameter is used when the IM-SSF sends a new InitialDP message to the SCP. Possible values:
Default value: DataNumberingPlan |
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 12-4.
Table 12-4 IM-SSF CAP Phase 3 Subscriber Data Fields
Name | Type | Description |
---|---|---|
Name |
STRING |
A unique identifier. |
IMSI |
STRING |
Specifies a condition on session IMSI. When the condition is met, IM-SSF invokes triggers towards the SCP. To apply the rule for all IMSIs, set this parameter to default (case sensitive). |
MSISDN |
STRING |
Specifies a condition on session MSISDN. When the condition is met, IM-SSF invokes triggers towards the SCP. To apply the rule for all MSISDNs, set this parameter to default (case sensitive). |
Service Key |
STRING |
Specifies a Service Key to set on the trigger to the SCP. |
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:
13=R, 14=N |
The Charging subtab enables you to configure functionality related to charging operations.
Table 12-5 describes configuration parameters on the Charging subtab.
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 12-6.
Table 12-6 IM-SSF CAP Phase 3 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 operations on its own or propagates a request to the session control layer. Possible values:
|
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 12-7.
Table 12-7 IM-SSF CAP Phase 3 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 Service Controller which media resource to connect in order to play announcements. Aliases are defined in a URI format. For example: mrf.network@domain.com. |
Address Digits |
STRING |
Specifies the digits part of the media resource address. The media resource address is used to set up a connection towards the media resource. |
Nature of Address |
STRING |
Specifies the NatureOfAddress part of the media resource address. The media resource address is used to set up a connection towards the media resource. Possible values:
Default value: NATIONAL |
Address Numbering Plan Indicator |
STRING |
Specifies the NumberingPlanInd part of the media resource address. The media resource address is used to set up a connection towards the media resource. Possible values:
Default value: ISDN |
Numbering Qualifier |
STRING |
Specifies the numbering qualifier of the media resource address. Possible values:
Default value: NONE |
Number Screening |
STRING |
Specifies the numbering screening of the media resource address. Possible values:
Default value: UNDEFINED |
Presentation Restriction |
STRING |
Specifies the presentation restriction of the media resource address. Possible values:
Default value: UNDEFINED |
Operation Type |
STRING |
Possible values:
Default value: internal |
Answer Indication |
BOOL |
Specifies how to set the bothwayThroughConnectionInd in the ServiceInteractionIndicatorTwo parameter in the ETC and CTR operations. Possible values:
Default value: Yes |
Note:
When an internal media resource is used (CTR), the Address Digits, Nature of Address and Address Numbering Plan Indicator parameters can be set to 'None' in order to instruct the network's session control entity to connect its pre-configured media resource.The TCAP subtab enables you to set up parameters of the IM TCAP layer.
Table 12-8 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 SMS Handling tab enables you to define how the IM-SSF handles SMS messages.
The SMS Handling tab contains the subtabs described in Table 12-9.
Table 12-9 SMS Handling Subtabs
Subtab | Description |
---|---|
SMS General |
Enables you to define how the IM-SSF should set the parameters of the DestinationSubscriberNumber and CallingPartyNumber. See "Configuring SMS Handling General Parameters" for more information. |
SMS-CSI |
Enables you to define CAMEL Subscription Information (CSI) for SMS messages. See "Configuring SMS CSI Parameters" for more information. |
The SMS General subtab enables you to define how the IM-SSF should set the parameters of the DestinationSubscriberNumber and CallingPartyNumber.
Table 12-10 describes configuration parameters on the SMS General subtab.
Table 12-10 SMS Handling General Parameters
Name | Type | Description |
---|---|---|
Numbering Plan Indicator Of Destination Subscriber Number |
STRING |
Specifies how the IM-SSF CAP3 should set the NumberingPlanIndicator of the DestinationSubscriberNumber. The IM-SSF CAP3 uses this parameter when sending an InitialDPSMS message to the SCP. Possible values:
Default value: DataNumberingPlan |
Type Of Number Of Destination Subscriber Number |
STRING |
Specifies how the IM-SSF CAP3 should set the NatureOfAddress of the DestinationSubscriberNumber. The IM-SSF CAP3 uses this parameter when sending an InitialDPSMS message to the SCP. Possible values:
Default value: NationalNumber |
Numbering Plan Indicator Of SMS Calling Party Number |
STRING |
Specifies how the IM-SSF CAP3 should set the NumberingPlanIndicator of the CallingPartyNumber for the SMS message. The IM-SSF CAP3 uses this parameter when sending an InitialDPSMS message to the SCP.
Default value: DataNumberingPlan |
NOA Of SMS Calling Party Number |
STRING |
Specifies how the IM-SS CAP3 should set the NatureOfAddress of the CallingPartyNumber for the SMS message. The IM-SSF CAP3 uses this parameter when sending an InitialDPSMS message to the SCP. Possible values:
Default value: NATIONAL |
The SMS-CSI subtab enables you to define CAMEL Subscription Information (CSI) for SMS messages.
The table on the SMS-CSI 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 12-11.
Table 12-11 SMS CSI Parameters
Name | Type | Description |
---|---|---|
Name |
STRING |
Specifies a unique identifier. |
IMSI |
STRING |
Specifies a condition on session IMSI. When the condition is met, the IM-SSF invokes triggers towards the SCP. To apply the rule for all IMSIs, set this parameter to default (case sensitive). |
MSISDN |
STRING |
Specifies a condition on session MSISDN. When the condition is met, the IM-SSF invokes triggers towards the SCP. To apply the rule for all MSISDNs, set this parameter to default (case sensitive). |
Service Key |
STRING |
Specifies a Service Key to set on the trigger to the SCP. |
SCP Address Alias |
STRING |
Specifies the SCP to which the 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 the IM-SSF handles a call when a signal between the IM-SSF and the SCP fails (that is, invokes a trigger towards the failed SCP). Possible values:
Default value: continue_call |
TDP List |
STRING |
Specifies a list of comma separated 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:
For example: 13=R, 14=N |
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.