WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Configuring communication with the SMSC

The SMPP-based Web service implementations (SMS over SMPP and WAP Push over SMPP), use predefined values when communicating with the Short Message Service Center (SMSC). The values are used in each message sent to the SMSC. You can modify these values using the TWSS Administration Console.

For additional details about configuring the SMPP-based Web service implementations, refer to their respective Administering topics.

Preparation

Before configuring for communication with the SMSC, you must have completed the following tasks:
  • Installed and configured WebSphere® Application Server
  • Installed the WebSphere Telecom Web Services Server base components, including the Telecom Web Services Server Administration Console
  • Installed one or both of the SMPP-based Web service implementations: SMS over SMPP and WAP Push over SMPP
  • Installed and configured the JCA adapter (this is normally done using the First Steps script)

List of ESMC settings

ESMC settings represent the SMSC default values that will be used in each message sent to the SMSC.

If you want to use settings that are different from the SMPP default values, open the TWSS Administration Console and navigate to the Message Data Services Configuration section. Click SMS SMPP ESMC Settings and set the following properties on the General Property Runtime tab:
ESMC SOURCE TON
Type of Number (TON) to be used in the Short Messaging Entity (SME) address parameters for the message source. The default value is 1 (international).
ESMC SOURCE NPI
Numeric Plan Indicator (NPI) to be used in the SME address parameters for the message source. The default value is 1 (ISDN E163/E164).
ESMC DESTINATION TON
TON to be used in the SME address parameters for the message destination. The default value is 0.
ESMC DESTINATION NPI
NPI to be used in the SME address parameters for the message destination. The default value is 0.
ESMC ESM CLASS
Special message attributes associated with the short message. The default value is 0 (none).
ESMC PROTOCOL ID
Protocol ID used to route the messages. The default value is 0 (none).
ESMC PRIORITY FLAG
Allows the originating SME to assign a priority level to the short message. The default value is 0.
ESMC REPLACE IF PRESENT FLAG
Used to request that the SMSC replace a previously submitted message that is still pending for delivery. The field is a drop-down list containing the following choices:
  • Don't replace [0]
  • Replace [1]
The default value is 1 (replace).
ESMC MESSAGE ID
An integer in the range 0–254 that specifies the SMSC index for a predefined or "canned" message. The default value is 0. This indicates a reserved value.
ESMC ESM CLASS SAR
Fragmentation using SAR. The default value is 0.
Message ID Format
Format for message IDs returned by the SMSC in submit_sm_resp and submit_multi_resp protocol data units (PDUs). This is an opaque value and must set according to the SMSC implementations. The field is a drop-down list containing two choices:
  • HEXADECIMAL: The returned message ID format will be hexadecimal.
  • DECIMAL: The returned message ID format will be decimal. This is the default value.

Implementation notes

When you change these values, it is not necessary to restart your system for the changes to take effect.

An SMSC delivery receipt is requested when the ConfirmedDelivery flag is set to true, either in the message itself or in the TWSS Administration Console (connection properties for the backend server).

When you are deploying Parlay X SMS over SMPP or WAP Push over SMPP, it may be necessary to update the configuration for the SMSC for your network. Consequently, you need to understand the SMSC behavior before you adjust the ESMC settings in the TWSS Administration Console.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.