WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Configuring Parlay X Multimedia Messaging over MM7

To make the Parlay X Multimedia Messaging over MM7 Web service implementation ready for use, configure a primary server (and optionally, a secondary backend) 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 Multimedia Messaging over MM7:

  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. Create a new primary backend for MMS:
    1. In the Navigation pane, click Web Services > IMS Multimedia Messaging > Network Resources.
    2. Click MMS Backends.
    3. Click New to create a new primary backend.
    4. Type primary_backend_name in the Name and Value fields. This value must not use any special characters or contain spaces.
    5. Click Add.
  4. 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 on which the primary backend is running, for example 9080.
    4. Type the user name to access the backend server in the System ID field.
    5. Type the password for the user name in the Password field.
    6. Type the maximum size for messages that are sent to the backend server in the Max Message Size field. The messages will be segmented if they are larger than the defined value. Set the value to zero to prevent segmentation. The recommended value is 260.
    7. Type the maximum size for a single target to be sent to the backend server in the Max Targets Size field. The default value is 255.
    8. In the Confirmed Delivery field, select false.
    9. In the Message Encoding field, select MMSC_Default_Encldoing to define the encoding type.
    10. Click OK.
  5. Optionally, create a new secondary backend:
    1. Click MMS 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.
  6. 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 on which the secondary backend is running, for example 9080.
    4. Type the user name to access the backend server in the System ID field.
    5. Type the password for the user name in the Password field.
    6. Type the maximum size for messages that are sent to the backend server in the Max Message Size field. The messages will be segmented if they are larger than the defined value. Set the value to zero to prevent segmentation. The recommended value is 260.
    7. Type the maximum size for a single target to be sent to the backend server in the Max Targets Size field. The default value is 255.
    8. In the Confirmed Delivery field, select false.
    9. In the Message Encoding field, select MMSC_Default_Encldoing to define the encoding type.
    10. Click OK.
  7. Define the MMS Alias:
    1. Click MMS Alias Details.
    2. Click New.
    3. In the Name field, type default.
    4. Click Add.
    5. Click default and verify that the alias is configured to communicate with the correct primary and secondary backend servers.
  8. 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 Multimedia Message Service Center (MMSC). 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
For each alias you defined, set to true to enable priority checking.
service.custom.requestPriorty
For each alias, set a priority value. 1 is the alias with the highest priority.
service.config.messaging.target.Aliases
Supply a list of aliases to use for routing traffic to different MMSCs.
service.config.messaging.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 Multimedia Messaging over MM7.




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