Sun Java System Messaging Server 6.3 Administration Guide

C.5.12 Configuration Example for Two-Way SMS

Assumptions on Behavior

For the sake of this example, let us assume that the following behavior is desired:

In order to bring about this behavior, the following assumptions and assignments are made

Further Assumptions and Assignments

SMS Channel Configuration

To effect the above behavior, the following SMS channel configuration may be used in the imta.cnf file (add these lines to the bottom of the file):

(blank line)

SMS Channel Option File

The channel’s option file, sms_option, would then contain the following settings:

SMS Gateway Server Configuration

Finally, the Gateway Server configuration file, sms_gateway.cnf, should look like the following:




Testing This Configuration

If you do not have an SMSC to test on, you may want to perform some loopback tests. With some additional settings in the sms_option file, some simple loop back tests may be performed for the above configuration.

C.5.12.1 Additional sms_option File Settings

The additional settings for the sms_option file are:

! So that we don’t add text to the body of the SMS message

Without these settings, an email containing: (Sample subject) Sample text

would get converted into the SMS message: Subject:Sample Subject Msg:Sample text

That, in turn, would not be in the format expected by the mobile-to-email code, which wants to see: (Sample subject) Sample text

Hence the need (for loopback testing) to specify empty strings for the FROM_FORMAT, SUBJECT_FORMAT, and CONTENT_PREFIX options.

Performing the Loopback Test

Send test email messages addressed to, such as: (Test message) This is a test message which should loop back

The result is that this email message should be routed back to the email recipient sure to have added to your DNS or host tables for the test.