WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Administering Parlay X Multimedia Messaging over MM7

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

Parlay X Multimedia Messaging over MM7 is a service implementation over an MM7 interface protocol, which is used to communicate with network elements. It depends on the Access Gateway to insert a transaction identifier into the original Web service request that is received by the Web Service Controller in the MMS service.

The Web service's deployment descriptor, located in the Web Service Controller layer, includes entries for the handlers that are used for each Web service operation.

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 Multimedia Messaging over MM7:
    • Multimedia Messaging Web Service: The following properties can be configured:
      • Purge Enabled: Specifies whether cleanup activity occurs (true) or does not occur (false) for expired delivery status data. The default value is false.
      • Purge Interval: Time interval, in minutes, used to trigger the cleanup operation for expired delivery status data.
      • Purge Block: 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.
      • Service Enabled: Specifies whether the Parlay X Multimedia Messaging over MM7 service is enabled (true) or disabled (false). 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 Multimedia Messaging over MM7. The default value is PX21_MM_MM7.
      • Destination Element: Defines the element to be used to get the destination number. This configuration option is used to switch between the <Sender> and <Recipient> elements of DeliveryReportReq, depending on the Multimedia Messaging Service Center's (MMSC) interpretation of the MM7 spec. The default value is Recipient.
      • InMemoryAttachmentHandling: Determines whether the MMS attachments should be persisted into the database or not, for the sendMessage operation. Setting the value to true ensures the attachments are handled in-memory and the operation is performed in a synchronous manner. The default value is false.
    • Multimedia Messaging HTTP Connector Settings: HTTP default connection settings that are used to send MMS messages to the MMSC. These settings are commonly applicable to all the backends that are created under the MMS Backends option. The following properties can be configured:
      • Default connections per host: The maximum number of connections that can be configured for any host configuration. The default value is 20.
      • Maximum total connections: The maximum number of connections that can be configured for all hosts. The default value is 100.
      • Connection time out period: The time, in milliseconds, to wait before establishing a connection. A value of 0 means that the timeout is not used. The default value is 0.
      • Socket time out period: The socket timeout time, in milliseconds. This value represents the timeout for waiting for data. A value of 0 means an infinite timeout. The default value is 0.
      • Enable MMS SI to make security enabled calls to MMSC: true if security is enabled for the MMS service implementation (SI) to make HTTP calls to the MMSC server using the user name and password provided; false if security is not enabled. When security is not enabled, the user name and password are not used to make the connection. The default value is false.
      • Gateway Support for MMS Message without Attachment: Defines the gateway support for MMS messages without attachments: if true, allow the MMS service indication (SI) to send MMS message without attachments to the gateway; if false, generate an exception when an attempt is made to send an MMS message without attachments. The default value is true.
  • Network Resources: Configure network elements to prepare them to receive MMS messages.
    • Multimedia Messaging Backends: The following properties can be configured:
      • Backend: The name of the backend currently being edited.
      • Host Name: The host name or IP address of the target MMSC server. The default value is localhost.
      • Port: The port for the target MMSC server. The default value is 7000.
      • URL Path: The URL path of the target MMSC server. The default value is /MMSCSimulator/MMSCServlet.
      • System ID: The user name or ID for binding to the MMSC.
      • Password: The password for binding to the MMSC.
      • Maximum Message Size: The maximum number of characters in messages that are sent to the MMSC. When a message is larger, it will be split into multiple messages (segmented) before sending. The default value is 260.
      • Maximum Targets Size: The maximum number of targets allowed in a single message. The default value is 255.
      • Confirmed Delivery: Specifies whether a delivery receipt is requested (true) or not requested (false) for each message sent to the MMSC. The default value is false.
      • Data Coding: Indicates the data coding type to be used for the messages on the target ESMC. The default value is MMSC Default Encoding.
    • Multimedia Messaging Alias Details: The following properties can be configured:
      • Primary Backend Server: The name of the primary server for handling messages.
      • Secondary Backend Server: The name of the secondary server, used if the primary server is unavailable.
    • Multimedia Messaging Optional Parameters Settings: The following properties can be configured:
      • VASP ID: The Value Added Service Provider (VASP) ID configured at the messaging gateway.
      • VAS ID: Identifies the originating application.
      • Linked ID: Identifies a correspondence to a previous valid message delivered to the VASP.
      • Message Class: The class of the MMS message.
      • Charged Party: Identifies which party is expected to be charged for a message submitted by the VASP.
      • Allow Adaptations: Indicates whether the VASP allows adaptation of the message content (true) or not (false). The default value is true.
      • Distribution Indicator: Indicates whether the VASP allows the message content to be redistributed (true) or not (false). The default value is false.
  • 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.

MMS/MM7 service RFC2822 support

An e-mail address identifies a location in which e-mail messages are delivered. The e-mail address resolution in MMS is executed by the MMS Relay/Server. The MMS Relay/Server sends messages that are transmitted as Internet e-mail using SMTP. You can send and retrieve Internet e-mail service to and from the MMS through the SMTP.

The RFC2822 service supports both the MO (Mobile Originated) and MT (Mobile Terminated) messages format.

MO support

When a mobile phone user sends a message to an e-mail recipient, the MMSC will convert the message to a SMTP e-mail format. In the case of a MO message, the originator's number will always be a E.164 address, which is either the embedded SIM card number or the 10 digit international unique number provided by the service provider. If the originator's address is E.164, the address fields uses RCPT, and you can convert it to the following format by the sender's MMS Relay/Server:

+E.164/TYPE=PLMN@recipient-mmse

Where recipient-mmse is a FQDN of the recipient's MMS Relay/Server, for example:

+358401234567/TYPE=PLMN@mmse.sonera.net
The following key points define the RFC2822 support e-mail address format in TWSS MMS/MM7 SI:
  • Use a sip: address scheme to perform a startMessageNotification operation.
  • To perform a startMessageNotification operation, do the following:
    • You must have a valid sip: address.
    • The number used in the sip: address should conform to the appropriate specified address format. The format will appear like the following:
      +E.164/TYPE=PLMN@recipient-mmse

Examples of sip: addresses:

sip:9886061490@in.ibm.com – valid

sip:+9886061490@in.ibm.com – valid

sip:+9886061490/TYPE=PLMN@in.ibm.com – valid

sip:samatada@in.ibm.com – not valid

sip:samatada – not valid
Note: If the sip: address does not have a + sign associated with it, it is considered a local number. A country code, which is set in the administrative console, will be appended. If the sip: address does not have /TYPE=PLMN” defined, the MMS SI will append the string /TYPE=PLMN. This must be completed before the message is sent to the MMSC, and the domain name must pass completely.

Assumptions

  • The startMessageNotification operation is a MT operation and should be performed using the sip: address.
  • The MMS SI sends the sip:+E.164/TYPE=PLMN@recipient-mmse address to the notification endpoint that is specified during the startMessageNotification operation.

The MO RFC2822 address must adhere to the following format:

+358401234567/TYPE=PLMN@mmse.sonera.net
Note: All of the MO RFC2822 addresses are assumed to be global numbers. If they are not, then it is the MMSC responsibility to convert or encode the numbers to the
+358401234567/TYPE=PLMN@mmse.sonera.net
format.

MT support

A MMS message can be sent to a mobile phone using an e-mail client (MT messages). You can use one of the following address formats:
  • username@mmscdomainname and phonenumber@mmscdomainname
  • username@mmscdominname

When using the SMTP interface, you can send MMS messages to a mobile phone using the phonenumber@mmscdomainname format. This is done by logging into the SMTP server using an e-mail client that supports SMTP Authentication. After authenticating through SMTP, you can send a MMS message to any recipient by addressing the message to phonenumber@mmscdomainname. The domain name is mmscdomainname for MMS e-mail, and is defined on MMSC.

The following key points define the RFC2822 support e-mail address format for TWSS MMS/MM7 SI:
  • Use a sip: address scheme to perform the sendMessage operation (MT).
  • Adhere to the following considerations when performing a startMessageNotification operation:
    • A sip: address without numbers is not valid.
    • The following numbers used in the sip: address should conform to the address format indicated below:

      +E.164/TYPE=PLMN@recipient-mmse

      Examples of sip: addresses:

      sip:9886061490@in.ibm.com – valid

      sip:+9886061490@in.ibm.com – valid

      sip:+9886061490/TYPE=PLMN@in.ibm.com – valid

      sip:samatada@in.ibm.com – not valid

      sip:samatada – not valid

    Note: If the sip: address does not have a + sign associated with it then it is considered a local number, and a country code set in the MBean will be appended. If the sip: address does not have /TYPE=PLMN” defined, the MMS SI will append the string “/TYPE=PLMN". This has to be completed prior to sending it to the MMSC, and the domain name has to pass completely.

Assumptions

  • If you want to initiate a sendMessage operation to use the RFC2822 address format, then the sendMessage operation is performed using the sip: address.
  • If you initiate a sendMessage operation with the receipt request, the sip:+E.164/TYPE=PLMN@recipient-mmse address is sent to the endpoint specified in the receipt request.
  • Before you send a message to the MMSC from the MMS SI, it has to be encoded in the following format:
+E.164/TYPE=PLMN@recipient-mmse
+358401234567/TYPE=PLMN@mmse.sonera.net

Configuring the MMSC URI

Mobile Originated messages are sent by the MMSC to the MMS SI. You have to configure the MMSC URI in order for the MO messages to be sent successfully to MMS.

http://:/TWSS/ParlayX21/MM7Receive/MultimediaMessaging/MM7 
  • Host_Name: This is the fully qualified host name of the server where the MMS/MM7 application is running.
  • Port: The port used to access MMS/MM7 SI.
  • Context_Root=/TWSS/ParlayX21/MM7Receive/MultimediaMessaging/MM7: This is the MO receive servlet context root where the MMS SI servlet listens for the incoming MO messages.

MMS/MM7 service short code support

MMS over MM7 provides support for short code numbers. Short code support is provided for both MO and MT messages. All MO and MT operations for short codes can be performed using the short:xxxxx format. Where short: is the schema part that identifies the number as a short code, and xxxxx is the actual number, for example short:88888.

Policies

Policy attributes are retrieved from the Service Policy Manager and are passed to the Parlay X Multimedia Messaging over MM7 Web service in the SOAP headers.

For information about default policy configuration, 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.