32 Setting Up IM-UIX-SMS

This chapter describes how to set up an IM-UIX-SMS interworking module.

About IM-UIX-SMS

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.

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.

Specifying the Body Encoding Format

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.

Configuring SMPP Handling Operations

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.

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:

UNKNOWN

INTERNATIONAL

NATIONAL

NETWORK_SPECIFIC

SUBSCRIBER_NUMBER

ALPHANUMERIC

ABBREVIATED

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:

UNKNOWN

ISDN

DATA

TELEX

LAND_MOBILE

NATIONAL

PRIVATE

ERMES

INTERNET

WAP_CLIENT_ID

Default value: UNKNOWN

Submit Message Mode

STRING

Specifies how the SMSC should deliver messages to the recipient SME.

Possible values:

DEFAULT_SMSC_MODE

DATAGRAM_MODE

FORWARD

STORE_AND_FORWARD_MODE

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_MESSAGE_TYPE

SM_CONTAINS_ESME_DELIVERY_ACKNOWLEDGEMENT

SM_CONTAINS_ESME_MANUAL_USER_ACKNOWLEDGEMENT

Default value: DEFAULT_MESSAGE_TYPE

Submit SM Priority Level

STRING

Specifies the priority level of a short message.

Possible values:

LEVEL_0

LEVEL_1

LEVEL_2

LEVEL_3

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:

NO_DELIVERY_RECEIPT_REQUESTED

DELIVERY_RECEIPT_REQUESTED_FOR_SUCCESS_OR_FAILURE

DELIVERY_REQUEST_RECEIPT_REQUESTED_FOR_FAILURE

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:

NO_RECEIPIENT_SME_ACKNOWLEDGDEMENT _REQUESTED

SME_DELIVERY_ACKNOWLEDGEMENT_REQUESTED

SME_MANUAL_USER_ACKNOWLEDGEMENT_REQUESTED

BOTH_DELIVERY_AND_MANUAL_USER_ACKNOWLEDGEMENT_REQUESTED

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:

VP_NOT_PRESENT

VP_RELATIVE_FORMAT

VP_ABSOLUTE_FORMAT

Default value: VP_NOT_PRESENT

Submit Validity Period Source

STRING

Specifies the source that defines the validity period of the short message.

Possible values:

STATIC_CONFIGURATION

SAL_MESSAGE

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:

Submit Validity Period Source is set to STATIC_CONFIGURATION

Submit Validity Period Format is set to VP_RELATIVE_FORMAT

Default value: -1

Replace if Present

STRING

Specifies whether to request the SMSC to replace a previously submitted message, that is still pending delivery.

Configuring Monitoring Parameters

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.