WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Configuring Parlay X SMS over SMPP

To make the Parlay X SMS over SMPP Web service implementation ready for use, configure a primary and secondary backend server using the TWSS Administration Console.

Before you begin
You must have completed the following steps:
  • Completed the initial installation and configuration for TWSS base components and Web service implementations, which includes running the First Steps configuration script
  • Started WebSphere® Application Server, version 7.0.0.7 or 6.1.0.29
  • Started the deployment manager, node agents, and application servers where you have deployed the EAR file for this Web service implementation
About this task

Complete the following steps to configure Parlay X SMS over SMPP:

  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  2. Open the TWSS Administration Console.
  3. In the Navigation pane, click Web Services > Clusters.
  4. Click cluster_name.
  5. Click PX21_SMS_SMPP.
  6. Create a new primary backend:
    1. Click SMS Backends.
    2. Click New to create a new primary backend.
    3. Type primary_backend_name: the name for the server where the application will attempt to send the messages first. This value must not use any special characters or contain spaces.
    4. Click Add.
  7. Assign the connection properties to the primary backend:
    1. Click primary_backend_name.
    2. Type the value for the Host name. This is the host name for the backend server.
    3. Type the value for the Port. This value is the port where the backend server listens.
    4. In the System ID field, type the user name to access the backend server.
    5. In the Password field, type the password for the user name.
    6. In the System Type field, supply the name of the system that requests the connection to the SMSC. Examples include VMS (voice mail system) and OTA (over-the-air activation system). This step may not be required for your SMSC, in which case you can either specify NULL or leave the field blank. The input string must be 12 characters or less.
    7. In the Max Message Size field, type the maximum size for messages that are sent to the backend server. The messages will be segmented if they are larger than the defined value. Set the value to zero to prevent segmentation. The default value is 254.
    8. In the Max Targets Size field, type the maximum size for a single target to be sent to the backend server. The default value is 255.
    9. In the Confirmed Delivery field, select true to receive delivery confirmation.
    10. In the DataCoding field, select a value (for example, SMSC Default Encoding) to define the encoding type.
    11. In the Type of Bind to SMSC field, select a bind type to send to the SMSC. Possible values are:
      • Transmitter(Tx)
      • Receiver(Rx)
      • Transceiver(Trx)
    12. In the Type of Message field, set the type of messages to send. Possible values are:
      • Synchronous SMS
      • StatusLess SMS
      • Asynchronous SMS
    13. Click OK.
  8. Create a new secondary backend:
    1. Click SMS Backends.
    2. Click New to create a new secondary backend.
    3. Type secondary_backend_name for the name for the server where the application will attempt to send the messages if the primary server is not available. This value must not use any special characters or contain spaces.
    4. Click Add.
  9. Assign the connection properties to the secondary backend:
    1. Click secondary_backend_name.
    2. Type the value for the Host name. This is the host name for the backend server.
    3. Type the value for the Port. This value is the port where the backend server listens.
    4. In the System ID field, type the user name to access the backend server.
    5. In the Password field, type the password for the user name.
    6. In the System Type field, supply the name of the system that requests the connection to the SMSC. Examples include VMS (voice mail system) and OTA (over-the-air activation system). This step may not be required for your SMSC, in which case you can either specify NULL or leave the field blank. The input string must be 12 characters or less.
    7. In the Max Message Size field, type the maximum size for messages that are sent to the backend server. The messages will be segmented if they are larger than the defined value. Set the value to zero to prevent segmentation. The default value is 254.
    8. In the Max Targets Size field, type the maximum size for a single target to be sent to the backend server. The default value is 255.
    9. In the Confirmed Delivery field, select true to receive delivery confirmation.
    10. In the DataCoding field, select a value (for example, SMSC Default Encoding) to define the encoding type.
    11. In the Type of Bind to SMSC field, select a bind type to send to the SMSC. Possible values are:
      • Transmitter(Tx)
      • Receiver(Rx)
      • Transceiver(Trx)
    12. In the Type of Message field, set the type of messages to send. Possible values are:
      • Synchronous SMS
      • StatusLess SMS
      • Asynchronous SMS
    13. Click OK.
  10. Define the SMS Aliases:
    1. Click SMS Alias Details.
    2. Click New.
    3. Type default for the Name.
    4. Click Add.
    5. Click default and verify the alias is configured to communicate with the correct primary and secondary backend servers.
    6. Click New.
    7. Type device_1 for the Name.
    8. Click Add.
    9. Click device_1 and verify that the alias is configured to communicate with the correct primary and secondary backend servers.
    10. Click New.
    11. Type device_2 for the Name.
    12. Click Add.
    13. Click device_2 and verify that the alias is configured to communicate with the correct primary and secondary backend servers.
  11. Configure values for Services and SMS SMPP ENQUIRELINK and Bind Settings. For details about these settings, refer to the topic Administering Parlay X SMS over SMPP.
  12. Configure ESMC settings for SMS over SMPP. For details, refer to the topic Configuring communication with the SMSC.
  13. Click Save to save changes to the master configuration.
Results

In conjunction with defining an alias, you can use policies to establish message priorities. Different aliases represent different accounts that are created in the Short Message Service Center (SMSC). Each account has a different priority and uses a unique user ID and password for the backend. Other details, such as the IP address and port number, are the same for all accounts.

Set the following policies to invoke priority :
service.custom.priorityEnabled
If the priority is set to false, then the priority check is not complete and no message priority will be set. However, if the priority is set to true, then the code will invoke a method which will override it.
service.custom.requestPriorty
Define aliases, and set a priority value for each alias. 1 is the alias with the highest priority.
service.config.target.Aliases
Supply a list of aliases to use for routing traffic to different SMSCs.
service.config.target.Ranges
Supply a list of target URI ranges.
Note: TWSS supports address URIs that use the following schemes only: tel:, sip:, sips:, short:.

For more information, refer to the topic Default service policies for Parlay X SMS over SMPP.




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