| 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-UIX-SMS interworking module.
IM-UIX-SMS is a network-facing module that enables Oracle Communications Service Broker to receive messages from, and send them to, Short Message Service Centers (SMSCs) through the Short Message Peer-to-Peer Protocol (SMPP).
In conjunction with application-facing IMs (for example, IM-ASF), IM-UIX-SMS provides a solution for routing messages between SMSCs and applications.
IM-UIX-SMS communicates with SMSCs as follows:
An SMSC sends messages to IM-UIX-SMS.
IM-UIX-SMS receives a delivery_sm request sent by an SMSC through the SMPP SSU. IM-UIX-SMS translates the request to a SAL message and sends it to the OE. The OE routes the message to an appropriate IM based on the orchestration logic.
See the discussion on configuring incoming routing rules in the chapter on configuring SMPP Signaling Server Units in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information about setting up rules for routing messages to IM-UIX-SMS instances.
IM-UIX-SMS sends messages to an SMSC.
IM-UIX-SMS receives a message sent by an application through an application-facing IM that supports the appropriate protocol (for example, through IM-ASF when a message is sent over SIP). Based on the received message, IM-UIX-SMS generates a submit_sm message and sends it to an SMSC through the SMPP SSU.
See the discussion on configuring SMPP network entities in the chapter on configuring SMPP Signaling Server Units in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information about setting up rules for routing messages to SMSCs.
To set up the communication between SMSCs and IM-UIX-SMS, you need to configure the following parameters:
The body encoding format, which defines the format that IM-UIX-SMS uses to encode the parameters of a delivery_sm message. See "Specifying the Body Encoding Format" for more information.
Parameters of SMPP operations that IM-UIX-SMS uses to generate a submit_sm message. See "Configuring SMPP Handling Operations" for more information.
Monitoring parameters of IM-UIX-SMS. See "Configuring Monitoring Parameters" for more information.
The process of IM-PSX GSM MAP setup requires the following:
Adding an IM-UIX-SMS to your Service Broker deployment. You can add as many modules of type IM-UIX-SMS as you need. See "Adding an IM-UIX-SMS to the Service Broker Deployment" for more information.
Configuring the IM-PSX GSM MAP. See the following sections for more information:
To add an IM-PSX GSM MAP:
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 IMUIXSMSSMPP34.
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-UIX-SMS to your deployment, in the Change Center pane, click Commit.
A new module of type IM-UIX-SMS is now added to your Service Broker deployment. The new module is displayed in the domain navigation pane under the Interworking Modules node.
IM-UIX-SMS receives delivery_sm messages from SMSCs. Before routing these messages to the OE, IM-UIX-SMS translates them into SAL messages. You can select the encoding format that IM-UIX-SMS uses to encode parameters of delivery_sm messages in the body of SAL messages.
To specify the body encoding format:
In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Expand Interworking Modules.
Select the instance of IM-UIX-SMS that you want to configure.
The IM-UIX-SMS configuration pane appears.
Click the General tab.
From the Body Encoding Format list, select the format that IM-UIX-SMS uses to encode the parameters of a short message in the body of SAL messages:
NONE
Select if you do not want to encode the parameters of a short message.
BER
Select to use Basic Encoding Rules.
XER
Select to use XML Encoding Rules.
Click Apply.
To route a message sent by an application to an SMSC, IM-UIX-SMS generates a submit_sm message. You configure how IM-UIX-SMS generates this message by configuring SMPP operations.
To configure SMPP operations:
In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Expand Interworking Modules.
Select the instance of IM-UIX-SMS that you want to configure.
The IM-UIX-SMS configuration pane appears.
Click the SMPP Handling tab.
Fill in the fields described in Table 32-1.
Table 32-1 SMPP Handling Parameters
| Name | Type | Description |
|---|---|---|
|
Default SMSC Alias |
STRING |
Specifies the alias of the SMSC to which IM-UIX-SMS sends the message. You map this alias to the physical address of an SMSC by configuring the SMPP SSU. See the discussion on configuring SMPP network entities in the chapter on configuring SMPP Signaling Server Units in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information. |
|
Service Type |
STRING |
Specifies the identifier of destination service in the SMSC, for submit_sm messages. |
|
Submit Destination Address Type of Number |
STRING |
Specifies the type of number of the destination address, which is set in the short message. Possible values:
Default value: UNKNOWN |
|
Submit Destination Address Numbering Plan Identification |
STRING |
Specifies the numbering plan identification of the destination address, which is set in the short message. Possible values:
Default value: UNKNOWN |
|
Submit Message Mode |
STRING |
Specifies how the SMSC should deliver messages to the recipient SME. Possible values:
Default Value: DEFAULT_SMSC_MODE Note: The current release of Service Broker does not currently support FORWARD. |
|
Submit Message Type |
STRING |
Specifies the type of message that an SMPP operation carries. Possible values:
Default value: DEFAULT_MESSAGE_TYPE |
|
Submit SM Priority Level |
STRING |
Specifies the priority level of a short message. Possible values:
Default value: LEVEL_0 |
|
SMSC Delivery Receipt Request |
STRING |
Specifies the type of the delivery receipt that the SMSC sends after receiving the short message. Possible values:
Default value: NO_DELIVERY_RECEIPT_REQUESTED |
|
SME Acknowledgement Request |
STRING |
Specifies the type of the acknowledgement that the SME sends after receiving the short message from an SMSC. Possible values:
Default value: NO_RECEIPIENT_SME_ACKNOWLEDGDEMENT _REQUESTED |
|
Submit Validity Period Format |
STRING |
Specifies the format in which validity of the short message is defined. Possible values:
Default value: VP_NOT_PRESENT |
|
Submit Validity Period Source |
STRING |
Specifies the source that defines the validity period of the short message. Possible values:
Default value: STATIC_CONFIGURATION |
|
Submit Validity Period Value |
INT |
Specifies the time, in seconds, during which the short message is valid. IM-UIX-SMS applies this value only when:
Default value: -1 |
|
Replace if Present |
STRING |
Specifies whether to request the SMSC to replace a previously submitted message, that is still pending delivery. Possible values:
Default value: DONT_REPLACE |
|
Data Coding |
STRING |
Specifies the coding scheme of the short message. Possible values:
Default value: SMSC_DEFAULT_ALPHABET |
|
Privacy Indicator |
STRING |
Specifies the privacy level of the short message. Possible values:
Default value: NOT_RESTRICTED |
|
Submit Include User Message Reference |
STRING |
Specifies whether IM-UIX-SMS sets the user_message_reference parameter in the submit_sm message. Possible values:
Default value: FALSE |
Click Apply.
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-UIX-SMS. 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.
|
 Copyright © 2010, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
