Support Blog

MMS Message Retries, Expiration, Conversion to SMS

There was a good simple question posted on the NowSMS Discussion Board. We are using the MMS Gateway service. For how long does the MMS contentstays in the system?Can we set a specific time for the message expiration?We also use the option of converting the mms to SMS with web link. Forhow long is the content stored in the platform? As I replied to that question, I realized that there are a...

Read More

Routing SMS messages to a Specifc SMSC Route

If you need control over routing to particular SMSC connections, the logic in NowSMS works like this: When NowSMS routes a message, it first looks to see if a sender address has been specified for the message submission (normally there is not a sender address specified, unless either you submitted the message via HTTP and specified a “Sender=” parameter, or a “Forced Sender...

Read More

One WAP Gateway for both MMS and Browser Data

Smaller mobile operators often ask us how to deploy a single WAP Gateway (or WAP Proxy if you prefer that terminology, as our marketing folks seem to prefer) to deploy both MMS traffic and general browser traffic. Of course, technically there is no reason that a single WAP Gateway can’t support both types of traffic. So if you’re not a mobile operator, you’re probably wondering...

Read More

GSM Modem CMS Error Code List

When sending and/or receiving SMS messages with a GSM modem, if an error occurs, the modem will report a “+CMS ERROR” with a numeric code to indicate the reason for the problem. These error codes are defined in the ETSI GSM specifications, specifically GSM 07.05, GSM 03.40 and GSM 04.11. I posted a list of CMS ERROR codes on the NowSMS discussion board almost 5 years ago at...

Read More

SMSC Speed Limits

In a perfect world, we’d all be able to send SMS messages as fast as we wanted. But the reality is that there is a combination of commercial and technical limitations throughout the message distribution chain. NowSMS has commercial limitations where outbound message delivery is throttled at a per minute or per second license limit. Individual SMS service providers have similar limits that...

Read More

Migrating to a Multiple Server MMSC, WAP Gateway, or NowSMS Gateway

The recent postings about multiple server redundant NowSMS or NowWAP configurations have generated a lot of questions from existing customers about how to migrate an existing installation to a multiple server configuration. Migrating an existing NowWAP installation to a multiple server configuration is the easiest task to explain. That’s because there is no shared data storage requirement,...

Read More

NowSMS in Fault Tolerant or Redundant Load Balanced Environment

For many configurations it is desirable to install NowSMS on multiple servers in order to achieve fault tolerance and/or improved throughput and performance. NowSMS offers extreme configuration flexibility to facilitate these requirements. This document outlines the multi-server configuration options that exist for NowSMS v2008.06.03 and later versions. Preferred Solution for Load-Balanced...

Read More

NowWAP in Fault Tolerant or Redundant Load Balanced Environment

For many configurations it is desirable to install NowWAP on multiple servers in order to achieve fault tolerance and/or improved throughput and performance. The only special consideration when running NowWAP in this type of clustered configuration is if NowWAP is configured to use RADIUS accounting to supply MSISDN information to one or more content servers, such as an MMSC. This document...

Read More

MMSC MM4 Interconnection Basics

MM4 is the standard protocol that is defined for connecting together two or more MMSCs. MM4 is an SMTP based protocol, meaning that the MM4 protocol defines how MMS messages are encapsulated for delivery over the SMTP protocol. In NowSMS, to define an MM4 interconnection, it is necessary to define two components. The outbound connection to the other MMSC is defined under “MMSC...

Read More

2-way SMS: Multiple operators with the same shortcode

This configuration issue comes up quite a bit. Let’s say that you are connecting directly to multiple mobile operators, and your service is using the same short code on each operator. When customers send a message in to your short code, you want to make sure that the reply is sent back via the same mobile operator as which the message was received. Additionally, if that message from the...

Read More