WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Administering Parlay X SMS over SMPP

After you deploy Parlay X SMS over SMPP, you can use the TWSS Administration Console to change the deployment configuration properties for the Web service and related Service Platform components.

You can receive additional information on specific properties from the online help in the TWSS Administration Console. Click More information about this page at the top right corner of the panel. Help for the module is then displayed in a separate browser window.

TWSS Administration Console settings

This Web service implementation adds the following configurable settings to the TWSS Administration Console:
  • Global: Policy values that are used for all services.
    • Common Service Settings: Use these settings to configure naming schemes for groups. The Access Gateway uses the IBM® XDMS component to resolve groups, and it can define and configure groups apart from the group scheme.
      • Country and code: The local country and code.
      • Address plan: The local address plan.
      • Enable Transaction Monitoring: Whether or not to enable transaction monitoring.
      • Supported Group Scheme: A comma-separated list of URI schemes that the service treats as a group URI. This setting must be coordinated with the Group List Manager component configuration. The default value is glmgroup.
      For more information about these settings, refer to the topic Group schema configuration.

  • Services: Default values used for Parlay X SMS over SMPP:
    • SMS Service: The following lists the configurable runtime properties:
      • Purge Enabled: True if cleanup activity occurs for expired delivery status data; false if cleanup activity does not occur. The default value is false.
      • Purge Interval: The time interval, in minutes, used to trigger the cleanup activity on Parlay X SMS over SMPP data. The default value is 10.
      • Purge Block: The number of records to retrieve each time there is a query to find expired data records. In effect, the cleanup operation is limited to cleaning up this much data during each purge interval. A value of 0 indicates that all records found should be removed. The default value is 1000.
      • Service Enabled: True if the service is enabled, false if disabled (when false, all requests are rejected). The default value is true.
      • Network Resource Name: The name of the network resource. Must match the name specified in Network Resources > Network Resources Configuration > resource_name for Parlay X SMS over SMPP. The default value is PX21_SMS_SERVICE.
      • Default Requester for Orphan Messages: The requester name to be included in orphan messages. In a notifySmsReception operation, an orphan message is defined as a message that is sent to a target where notification is not enabled, or a message in which the SMS destination does not fulfill the criteria specified in a previous startSmsNotification operation.
      • Default Endpoint for Orphan Messages: Endpoint to be notified when an orphan message is received.
      • Default Correlator for Orphan Messages: Correlator for the incoming orphan MO messages, used to correlate the messages while retrieving the received MO messages. The default value is an empty string, which indicates that any criteria will be matched. If you specify a non-empty string, then a given message will be retrieved only when a matching correlator is provided.
      • Default Expiry Time for Orphan messages: Amount of time, in minutes, to keep the orphan MO messages that have been received in the database. The default value is 1440.
  • Network Resources: Configure network elements to prepare them to receive messages from Parlay X SMS over SMPP.
    • SMS Backends: The SMPP network mapper provides configuration for binding to the backend SMSC.
      • Backend Name: The name of the backend that will communicate with the SMSC.
      • Hostname: The location of the target SMSC.
      • Port: The port of the target SMSC.
      • System ID: The System ID that is used to bind to the SMSC.
      • Password: The password for the System ID.
      • System Type: The type of ESME system that requests the connection to the SMSC. The input string must be 12 characters or less. The default value is a null string.
      • Max Message Size: The maximum allowable size, in bytes, of an individual message as stipulated by the SMSC. If the incoming message size is greater than MaxMessageSize, it will be sent using the SAR message segmentation policy. If the incoming message size is greater than the protocol maximum but smaller than MaxMessageSize, the message will be sent using the message_payload. Valid values are 1 through 64000. The default value is 260.
      • MaxTargetsSize: The maximum number of targets allowed in a single message according to the protocol specification or network support. Valid values are 0 through 255. A value of 0, which is the default, indicates that there is no limit.
      • Confirmed Delivery: True if a delivery receipt will be requested on each message sent to the SMSC; false if not. The default value is true.
      • Data Coding: The type of data coding to use for the messages on the target SMSC. The default value is US-ASCII.
      • Type of Bind to SMSC: The bind type to send to the SMSC. TWSS supports three types of bindings, which are defined in the SMPP Protocol Specification. The field is a drop-down list containing the following choices:
        • Transceiver(Trx): The connection can be used both for sending Mobile Terminated (MT) messages to the SMSC and for receiving Mobile Originated (MO) messages from the SMSC.
        • Transmitter(Tx): The backend will be used only for sending Mobile Terminated (MT) messages. Any Mobile Originated (MO) messages sent from the SMSC using the connection will be discarded.
        • Receiver(Rx): The backend will not be used for sending Mobile Terminated (MT) messages. It will be used only for receiving Mobile Originated (MO) message sent from the SMSC. Note that outbound enquire_link operation are not initiated on back ends that use Rx mode binding.
        The default value is Transceiver(Trx).
      • Type of Message: The way in which SMS messages are to be sent. The field is a drop-down list containing the following choices:
        • SynchronousSMS: Send SMS messages in synchronous fashion. If you choose this setting, you will need to configure connection pool settings at the following location in the Integrated Solutions Console: Resource adapters > SMPP v3.4 JCA Connector > J2C connection factories > PX21_SMS_SMPPJ2CCF > Connection pools.
        • StatusLessSMS: Send SMS messages in synchronous fashion and maintain the status of SMS in the database. If you choose this setting, you will also need to configure connection pool settings in the Integrated Solutions Console.
        • AsynchronousSMS: Send SMS messages in asynchronous fashion. This is the default value.
        Note: In TWSS version 7.0, the Enable Synchronous SMS and Enable StatusLess SMS controls were used to specify the message type. These controls are no longer used, and your existing setting is not preserved when you migrate to version 7.1. The default message type is SynchronousSMS, when you migrate from TWSS 7.0 to TWSS 7.1 After installing version 7.1, you will need to set Type of Message explicitly.
    • SMS Alias Details: The alias represents a mapping between the target address for a short message and the back end network element that will receive the physical message.
      • Alias: The alias to assign the given range of addresses.
      • Primary Backend Server: Primary server for handling messages.
      • Secondary Backend Server: Secondary server for handling messages. If the primary server is not available, the secondary server is used.
    • SMS SMPP ESMC Settings:

      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 more information, refer to the topic Configuring communication with the SMSC.

  • Common Components: Click the name of a Service Platform component–for example Fault Alarm Client or Usage Record Client–to configure it to work with this Web service implementation. If you leave the endpoint URI empty for a component, then the component is disabled.

Policies

Policy attributes are retrieved from Subscription Management in the Access Gateway and are passed to the Parlay X SMS over SMPP Web service in the SOAP headers. If the policies are not found in the Telecom Web Services Server SOAP header, then the Web service uses the values that are defined in the TWSS Administration Console.

For information about default policy configuration, refer to the following topic: Default service policies for Parlay X SMS over SMPP.




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