The gateway also includes a powerful MMSC Messaging Server with content adaptation and conversion services not found on many higher end products.

Normally an MMSC is only utilized when a mobile phone user sends/originates an MMS message. The mobile phone sends the message to the MMSC for delivery. However, phones may also assume that the MMSC is responsible for the delivery of all MMS messages, and this may cause phones to disregard or get confused over MMS messages that are sent via the gateway instead of the operator’s MMSC.

The MMSC Messaging Server built into the Now SMS/MMS Gateway implements the MMS protocols, and allows you to bypass the operator MMSC.

The MMSC supports sending MMS messages between mobile phones, and also supports sending and receiving MMS messages between mobile phones and standard internet e-mail systems.

While extremely powerful, the MMSC integrated into the gateway is a lightweight version of the Now MMSC product which is designed for operator environments (and includes user provisioning systems to integrate into the operator network).

Configuration for the MMSC can be found under the “MMSC” and “MMSC Users” configuration tabs of the gateway.

The “MMSC” configuration tab specifies general configuration information for the MMSC:

The MMSC runs as a separate service process from the gateway. To activate the MMSC service, check the box next to the prompt “Activate MMSC Service”.

When a mobile phone sends or receives an MMS message, it makes an HTTP connection to an MMSC (usually through a WAP gateway). The MMSC contains an integrated HTTP server to process these connections. Please specify an available “HTTP Port Number” on the local computer for the HTTP server to accept connections from mobile phones.

MMS messages can be sent to and received from, standard internet e-mail accounts. To support this functionality, the MMSC provides message format conversions between MMS and SMTP. To accept messages from internet e-mail accounts, the MMSC contains an integrated SMTP server. Please specify an available “SMTP Port Number” on the local computer for the SMTP server to accept e-mail messages from internet e-mail recipients. Note that the standard SMTP port number is 25, and you will require special configuration of another SMTP mail server in your network to support relaying to a port other than 25.

The PC that is running the gateway might have other web and mail services installed. For this reason, the gateway allows you to specify which of the available IP addresses on the current PC should be used by the gateway. The “IP Address” prompt displays the available IP addresses on the current PC. To make the gateway service available via any address on the current PC, select “(all available)”, otherwise select a specific IP address.

“Local Host Name or IP Address” specifies the local host name or IP address of the computer that is running the MMSC service. The name or address specified here will be used to construct URLs when sending MMS messages to mobile phones. If a host name is used, this host name must be defined in DNS and resolve back to the computer running the MMSC service.

“Domain Name for MMS E-Mail” specifies the SMTP domain name that is associated with users defined to the MMSC. When MMS users exchange e-mail messages with internet recipients, this is the SMTP domain name associated with the MMSC users. Note that the MMSC acts as an e-mail server, and you will need to configure DNS for this domain name so that internet mail sent to this domain name is properly routed to the PC running the gateway.

When an MMS user sends a message to an SMTP recipient, the MMSC requires an “SMTP Relay Host” to transfer the message to the correct internet mail server for the intended recipient. Please define an appropriate SMTP mail server in your network that will perform this SMTP message relay capability.

Checking “Enable Dynamic Image and Audio Conversion” enables the dynamic content adaptation and conversion services of the MMSC. The MMSC uses WAP/MMS “User Agent Profile” capabilities to determine the MIME formats that a device supports, as well as the maximum size of images supported by the device. Where required, the MMSC converts between common image formats (including, but not limited to GIF, JPG, PNG, BMP and WBMP) to deliver an image supported by the device. For images larger than the maximum size supported by the device, the MMSC will automatically scale the image to fit the device, speeding up download times. For audio formats, conversion between WAV and AMR is provided in the e-mail gateway interface. MIME types not supported by the receiving device, which cannot be supported, will be removed prior to delivery to the receiving device to prevent compatibility issues and unnecessary download delays.

Checking “Enable E-Mail WAV to AMR Conversion” enables conversion between WAV (audio/wav) and AMR (audio/AMR) formats when messages are exchanged between e-mail and MMS recipients. For audio recordings, the WAV format is more commonly supported for e-mail recipients, while the AMR format is more commonly supported for MMS recipients. When this setting is enabled, AMR sound files going from MMS to e-mail are converted to WAV format, and WAV sound files going from e-mail to MMS are converted to AMR format.

Checking “Enable E-Mail BMP to JPEG Conversion” enables conversion of files from BMP (image/bmp) to JPEG (image/jpeg) format when messages are sent from an e-mail sender to an MMS recipient. The BMP format is somewhat common in PC environment, but is not frequently supported in MMS environments. Even when supported in MMS environments, BMP files are very large, which makes them awkward and inconvenient to transmit to MMS devices.

The “Enable E-Mail to SMS Support” checkbox enables the SMTP interface to be used to send SMS messages. This setting is used primarily in conjunction with bulk e-mail delivery via SMTP Authentication, as described in the “SMS User Accounts” section of this document. Gateway user accounts can be allowed to login via SMTP with an e-mail account to perform bulk delivery of SMS messages. If this configuration setting looks out of place, it is because this SMS gateway capability is provided through the MMSC’s SMTP server. When enabled, specify a “Domain Name for SMS E-Mail”, so that the gateway can identify by the domain name of the message recipient whether to route the message via SMS or MMS. Additionally, specify the “Maximum number of SMS messages per e-mail” to be used when converting from SMTP to SMS. When set to a value greater than 1, the gateway will use long (concatenated) SMS messages to support messages longer than 160 characters.

An administrative interface for adding, deleting and modifying users is available via the HTTP port of the MMSC if an “Admin User” is defined on the MMSC dialog. If an administrative user is defined, then the administrative interface is available by connecting via a web browser to “/ADMIN” on the MMSC HTTP port (e.g., http://127.0.0.1/ADMIN), and supplying the defined administrative user name and password. The administrative interface provides functionality similar to that described for the “MMSC Users” tab dialog, defined in the following section.

The “MMSC Users” tab defines users that are allowed to utilize the MMSC.

To define a user to use the MMSC, you must define a phone number using international format, and an alias name for the user account. (The alias name will be used as the user name when sending and receiving SMTP e-mail.)

Note that for a mobile phone user to use the simple MMSC integrated with this gateway, the mobile phone user must configure their MMSC (MMS Messaging Server) to point to the address of the MMSC, and include their user name and password in the MMSC URL.

Example

http://x.x.x.x:81/username=password or http://host.domain:81/username=password

The username can be either the user’s alias name or phone number.