| Oracle® Communications Service Broker Modules Configuration Guide Release 6.1 E29454-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications Service Broker Modules Configuration Guide Release 6.1 E29454-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how to set up an IM-OCF ECE interworking module.
The process of IM-OCF ECE setup requires the following:
Adding an IM-OCF ECE to your Oracle Communications Service Broker deployment. You can add as many modules of type IM-OCF ECE as you need. See "Adding an IM-OCF ECE to the Service Broker Deployment" for more information.
Configuring the IM-OCF ECE. See "Configuring an IM-OCF ECE" for more information.
To add an IM-OCF ECE:
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 IMOCFECE.
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.
Click OK.
In the notification window that reminds you to commit the changes, click OK.
To add the new IM-OCF ECE to your deployment, in the Change Center pane, click Commit.
A new module of type IM-OCF ECE is now added to your Service Broker deployment. The new module is displayed in the domain navigation pane under the Interworking Modules node.
To configure an IM-OCF ECE:
In the Change Center, click Lock & Edit.
In the domain navigation pane, under the Interworking Modules node, select the newly added IM-OCF ECE.
The IM-OCF ECE configuration consists of three main tabs:
Configuration tab
Redirection tab
Ro ECE Mediation tab - Enables you to define how IM-OCF PCP translates Ro messages to PCP messages and communicates with BRM applications. See "Configuring Ro ECE Mediation", for more information.
The IM-OCF ECE configuration pane contains the subtabs described in Table 25-1.
Table 25-1 IM-OCF ECE Configuration Subtabs
| Subtab | Description |
|---|---|
|
Call Handling |
Enables you to define how the IM-OCF ECE handles calls. See "Configuring Call Handling Parameters" for more information. |
|
Diameter Credit Control Application |
Enables you to configure parameters specific to the IM-OCF ECE DCCA interface. See "Configuring Diameter Credit Control Application Parameters" for more information. |
|
Async Announcement Manager |
Enables you to set up how IM-OCF ECE triggers the MRF to play announcements. See "Configuring Asynchronous Announcement Manager Parameters" for more information. |
|
Monitoring |
Enables you to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information. |
|
Degraded Mode |
Enables you to set up how a session is charged when an online charging server is not available. See "Configuring the Degraded Mode" for more information. |
The Call Handling configuration tab enables you to set up how IM-OCF ECE handles sessions. Table 25-2 describes configuration parameters in the Call Handling tab.
Table 25-2 IM-OCF ECE Call Handling General Parameters
| Name | Type | Description |
|---|---|---|
|
Termination-Cause AVP on SAL BYE |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL BYE message. Possible values:
Default value: DIAMETER_LOGOUT |
|
Termination-Cause AVP on SAL CANCEL |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL CANCEL message. Possible values:
Default value: DIAMETER_SERVICE_NOT_PROVIDED |
|
Termination-Cause AVP on SAL Final Error Response |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL final error response message. Possible values:
Default value: DIAMETER_SERVICE_NOT_PROVIDED |
|
Send CCR OnThresholdIndication |
BOOL |
Indicates whether the IMOCF should send CCR if a SAL message indicating a threshold has been reached. Default value: FALSE |
The Diameter Credit Control Application tab enables you to configure parameters related to the IM-OCF ECE Diameter Credit Control Application (DCCA) interface. The Diameter Credit Control Application tab contains subtabs described in Table 25-3.
Table 25-3 IM-OCF ECE Diameter Credit Control Application Subtabs
| Subtab | Description |
|---|---|
|
AVPs |
Enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs. See "Configuring AVPs" for more information. |
|
General |
Enables you to set up a DCCA dialect and enables monitor call duration. See "Configuring DCCA General Parameters" for more information. |
The AVPs subtab enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs. Table 25-4 describes the AVPs that you can specify.
Table 25-4 IM-OCF ECE DCCA AVPs Subtab Parameters
| Name | Type | Description |
|---|---|---|
|
Destination-Host AVP |
STRING |
Specifies the value to set in a CCR Destination-Host AVP. The Destination-Host AVP combined with the Destination-Realm AVP defines a Diameter destination node that communicates with the IM-OCF ECE. The IM-OCF ECE sends messages to the address you specify for the Diameter destination node. An alternative way to specify a Diameter destination node is to set the Destination-Realm AVP field with an alias of a Diameter destination node, which you define in the Diameter SSU Outbound Destination (see the discussion on configuring outbound destinations in the Diameter SSU in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information.). In this case, the Destination-Host AVP is ignored. |
|
Destination-Realm AVP |
STRING |
Specifies the value to set in a CCR Destination-Realm AVP. The Destination-Realm AVP combined with the Destination-Host AVP defines a Diameter destination node that communicates with the IM-OCF ECE.The IM-OCF ECE sends messages to the address you specify for the Diameter destination node. An alternative way to specify a Diameter destination node is to set the Destination-Realm AVP field with an alias of a Diameter destination node, which you define in the Diameter SSU Outbound Destination (see the discussion on configuring outbound destinations in the Diameter SSU in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information.). In this case, the Destination-Host AVP is ignored. If you leave this field blank, the IM-OCF works in the degraded mode. |
|
Service-Context-Id AVP |
STRING |
Specifies the value to set in a CCR Service-Context-Id AVP. Default value: 32260@3gpp.org |
|
User-Name AVP |
STRING |
Specifies the value to set in a CCR User-Name AVP. |
|
Ro Node-Functionality AVP |
INT |
Specifies the value to set in a CCR Node-Functionality AVP. Possible values:
Default value: AS |
The General subtab enables you to set up a DCCA dialect and enable monitor call duration. Table 25-5 describes the parameters you can configure.
You can set up IM-OCF ECE to trigger an MRF to play announcements. Using the Async Announcement Manager tab, you can specify the alias of the MRF that plays announcements. In addition, you set up the rules that define the announcement to be played and the way how the MRF plays this announcement. For example, you can define that the MRF plays an announcement to a calling party when the time granted for the call is over, and the mobile subscriber is located in the home network.
You set up the Announcement Manager by configuring parameters on the subtabs described in Table 25-6.
Table 25-6 IM-OCF ECE Async Announcement Manager Subtabs
| Subtab | Description |
|---|---|
|
General |
Enables you to specify the alias of the MRF that plays announcements. See "Configuring Asynch Announcement General Parameters" for more information. |
|
Async Announcements |
Enables you to set up the rules that define announcements to be played as well as to specify how the MRF plays these announcements. See "Configuring Async Announcements" for more information. |
The General subtab enables you to specify the alias of the MRF that plays announcements. Table 25-7 describes the parameter you can configure.
The Async Announcements subtab enables you to set up rules for playing announcements. In addition, you set up the rules that define the announcement to be played and the way how the MRF plays this announcement.
The subtab contains the table in which each row represents a single rule. Table 25-8 describes the parameters you can configure. To configure a new rule, click New.
Table 25-8 Async Announcement Manager Announcements Parameters
| Name | Type | Description |
|---|---|---|
|
Name |
STRING |
Specifies the unique identifier of the rule. |
|
Enabled |
BOOL |
Specifies whether or not the announcement is enabled. Possible values:
Default value: TRUE |
|
Reason Type |
STRING |
Specifies the parameter that IM-OCF ECE checks in the CCA message received from the online charging server. When the value of the specified parameter matches the range that you defined using the Lower Limit and Upper Limit parameters, IM-OCF ECE triggers the MRF to play the announcement. Possible values:
Default value: ANY Note: When you set Reason Type to ANY, IM-OCF ECE always triggers the MRF to play the announcement. |
|
Lower Limit |
INT |
Specifies the lower limit of the range for the parameter that you specified in Reason Type. When the value of the specified parameter is greater than the value set in Lower Limit and less than the value set in Upper Limit, IM-OCF ECE triggers the MRF to play the announcement. To configure IM-OCF ECE to trigger the MRF to play the announcement, regardless of the value of the lower limit, set this parameter to -1. Note: IM-OCF ECE does not use the Lower Limit parameter if you set Reason Type to ANY. |
|
Upper Limit |
INT |
Specifies the upper limit of the range for the parameter that you specified in Reason Type. When the value of the specified parameter is greater than the value set in Lower Limit and less than the value set in Upper Limit, IM-OCF ECE triggers the MRF to play the announcement. To configure IM-OCF ECE to trigger the MRF to play the announcement, regardless of the value of the upper limit, set this parameter to -1. Note: IM-OCF ECE does not use the Upper Limit parameter if you set Reason Type to ANY. |
|
Network |
STRING |
Specifies the location of the mobile subscriber required for triggering the MRF to play the announcement. Possible values:
Alternatively, you can specify the ID of a specific MSC that serves the mobile subscriber. |
|
Service Side |
STRING |
Specifies the IM-OCF ECE's service side required for triggering the MRF to play the announcement. Possible values:
Default value: BOTH |
|
Call State |
STRING |
Specifies the call state when IM-OCF ECE triggers the MRF to play the announcement. Possible values:
Default value: PRECALL |
|
Priority |
INT |
Specifies the order in which the MRF plays different announcement when the conditions of multiple rules are met. |
|
Announcement Code |
INT |
Specifies the identifier of the announcement that the MRF plays. |
|
Threshold |
INT |
Specifies how much time, in seconds, prior to the end of quota, IM-OCF ECE triggers the MRF to play the announcement. IM-OCF ECE uses the Threshold parameter only for the announcements whose Call State parameter is set to MIDCALL. Note: Setting the Threshold parameter to any positive value when Call State set to PRECALL or POSTCALL causes an error. |
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-OCF ECE. 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.
Service Broker relies on an external online charging server (OCS) to apply charges for the use of network services.
When an OCS is unavailable, IM-OCF ECE switches to the special mode known as degraded mode. This mode enables IM-OCF ECE to continue a session and charge a mobile subscriber during the time when the OCS is temporarily unavailable.
Each time IM-OCF ECE sends an accounting request to the OCS, IM-OCF ECE waits for a response for a specified period of time. If the server does not respond, IM-OCF ECE switches to the degraded mode for the charging session.
In degraded mode, IM-OCF ECE handles the session until terminated even if the OCS becomes available. Service Broker records charging session activity to a call detail record (CDR). Stored CDRs are played back to the OCS once availability returns.
In the degraded mode, IM-OCF ECE communicates with the Service Broker local online charging server (OCS). The local OCS assumes the role of the external OCS. This means that the local OCS can receive Credit Control Requests (CCRs) from, and send Credit Control Answers (CCAs) to, IM-OCF ECE.
For more information, see the discussion on Degraded Mode in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
You use the Degraded Mode tab to configure the parameters of this mode as described in Table 25-9.
Table 25-9 Degraded Mode Parameters
| Name | Type | Description |
|---|---|---|
|
On OCFFailure |
STRING |
Specifies the behavior of IM-OCF Ro when the OCF fails. Possible values:
Default value: USE_LOCAL_REFUSE |
|
CDR Mode |
STRING |
Specifies how IM-OCF ECE writes CDRs. Possible options:
Default value: NORMAL |
|
CDR Writer Impl |
STRING |
Specifies the full path of the bundle that implements the CDR writer functionality. This is a preset parameter. Do NOT change the value of this parameter. |
|
CDR Writer Service |
STRING |
Specifies the full path of the CDR writer service. This is a preset parameter. Do NOT change the value of this parameter. |
|
Degraded Mode Timer |
INT |
Specifies the period of time, in milliseconds, that IM-OCF ECE waits for a response from the external OCS. If the OCS does not respond within the specified period of time, IM-OCF ECE switches to the Degraded Mode. |
|
Local-OCF Alias |
STRING |
Specifies the alias of the local OCS. This alias is mapped to the destination host and destination realm of the local online charging server as defined in the configuration of Diameter SSU outbound routing rules. For more information, see the discussion on configuring outbound destinations in Diameter SSUs in Oracle Communications Service Broker Signaling Server Units Configuration Guide. |
|
Local-OCF External Protocol |
STRING |
Specifies the protocol that IM-OCF ECE uses to communicate with the local OCS. |
|
Degraded Mode Error Codes |
STRING |
Specifies the error codes that trigger IM-OCF Ro to enable the Degraded Mode. You can type several error codes separated by comma. |
IM-OCF ECE translates Ro messages to ECE messages and communicates with ECE applications using the Ro ECE mediator.
You set up the mediator by configuring parameters on the Ro ECE Mediation subtabs described in Table 25-10.
Table 25-10 Ro ECE Mediation Subtabs
| Subtab | Description |
|---|---|
|
General |
Enables you to define how IM-OCF ECE communicates with ECE. See "Configuring Ro ECE Mediation General Parameters" for more information. |
|
Services types default |
Enables you to configure the resolution mechanism that routes requests based on the value of an AVP inside the request. See "Configuring Services Types Default" for more information. |
|
Service types |
Enables you to set up mapping between Diameter Ro Service-Identifier AVP and ECE processor types. See "Configuring Service Types" for more information. |
|
Processor mapping |
Enables you to map new Diameter Ro requests to ECE processors. See "Configuring Processor Mapping" for more information. |
|
Monitoring |
Enables you to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information. |
Using the General subtab, you define how IM-OCF ECE communicates with ECE. Table 25-11 describes the parameters that you can configure.
Table 25-11 Ro to ECE Mediation General Parameters
| Name | Type | Description |
|---|---|---|
|
Default Request Timeout |
INT |
The CCR request timeout value in milliseconds. Default value: 1950 |
|
Charging Session State Timeout |
INT |
The charging session state timeout value. Default value: 86400000 |
|
Customized Mapping Keyclass |
STRING |
A class to be used for mapping processor key generation. It is needed only when processor mapping tree structure is modified. Otherwise, the default processor key will be used. |
|
ResultCode List for Blocked Session |
STRING |
Sessions with response (CCA) ResultCode matching entries in this list will be regarded as blocked. Enter ResultCodes as a list separated by commas. |
IM-OCF ECE routes outgoing ECE requests through the Coherence connection you configure. For more information, see the discussion on connecting to the ECE Coherence cluster in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
Requests bound for the ECE Coherence connection may include ECE rating group and service identifier AVPs. When this information is not included IM-OCF ECE will use the default information specified in the following parameters.
Table 25-12 describes the parameters that you can configure.
Table 25-12 Services Types Default Parameters
| Name | Type | Description |
|---|---|---|
|
Default Rating Group |
INT |
The default ECE Rating-Group AVP value used when the Rating-Group AVP is not included in the MSCC. Default value: 0 |
|
Default Service-Identifier |
INT |
The default ECE Service-Identifier AVP value used when the Service-Identifier AVP is not included. Default value: 1 |
Using the Service types tab, you set up mapping between Diameter Ro Service-Identifier AVP and ECE service types. Table 25-13 describes the parameters that you can configure.
Table 25-13 Ro to ECE Mediation Service Types Parameters
| Name | Type | Description |
|---|---|---|
|
Service-Context-Id AVP |
STRING |
The Diameter Ro service identifier to be mapped to ECE service type. |
|
Rating-Group AVP |
INT |
The ECE rating group AVP if rating groups are defined in the ECE implementation. |
|
Service-Identifier AVP |
INT |
The Diameter Ro service identifier to be mapped to ECE service type. |
|
ECE Product Type |
STRING |
The ECE product type. For example, Voice or Data. |
|
ECE Event Type |
STRING |
The ECE event type. For example, 3G. |
|
ECE Service Id |
STRING |
The ECE service Id. For example, Voice, Message or Data. |
|
ECE Service Context |
STRING |
The ECE service context. For example, usage. |
|
ECE Request Specification Version |
STRING |
The ECE request specification version. |
Using the Processor Mapping tab, you map new Diameter Ro requests to ECE processors.
To map new Diameter Ro requests to ECE processors:
In the Processor Mapping tab, in the navigation tree, select the type of Diameter request that you want to add mapping for.
Click the Plus (+) button at the bottom of the navigation tree area. A new AVP node is added.
In the AVP tab in the right hand pane, enter the following fields for the AVP that you want to map:
AVP Code
AVP Vendor ID
AVP Value
Click the Add Processor Mapping button. The Mapping tab appears.
In the Mapping tab, set the following fields as described:
In the Processor Class field, enter name of the name of the processor class implementing the mapping that you are currently configuring.
In the Processor Timeout field, enter the time to allow for the ECE operation to execute before it is considered to have timed out. Given in milliseconds.
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-OCF PCP. 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.
Charging IMs handling Diameter responses from online charging systems can perform session redirection based on criteria in Credit Control Answers (CCA). Configure the default IM redirection behavior in the IM configuration node Redirection tab.
See the discussion on redirection in Oracle Communications Service Broker Online Mediation Controller Implementation Guide for more information on using session redirection.
|
 Copyright © 2010, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
