Support Blog – NowSMS

NowSMS NextGen Quick Setup: Mobile Operator MMSC

2021-03-16T18:17:30Z

Step 1: Open a terminal session with the server and ensure that you are logged in with a user account that has root privileges available via sudo.

Step 2: Download the NowSMS version that is appropriate for your environment by using one of the following commands:

Standard Linux (Intel/AMD64 microprocessor):

wget https://www.nowsms.com/download/linux/nowsms.tar.gz

ARM 64-bit microprocessor:

wget https://www.nowsms.com/download/linuxarm64/nowsms.tar.gz

Step 3: Extract the installation program, NowSMSInstall with the following command:

tar -xzf nowsms.tar.gz

Step 4: Start the installation with the following command:

./NowSMSInstall

Step 5a: If you are operating in a terminal window under a desktop login, a web browser window will be opened to continue the installation. If you are connected to remote terminal session, continue with Step 5b.

The default directory locations are appropriate for most installations:

Program files will be installed in /usr/local/bin

Data files will be stored in /var/lib/nowsms

After clicking on the “Install Service” button, in most environments, NowSMS might prompt for the root/admin password, if the system requires it to complete the service installation. This password will be used with the sudo command to perform the installation.

If this is a new (not yet configured) installation, the “System Configuration” menu will be displayed. If the browser reports an error instead, wait a minute, and press the reload button, and/or try manually connecting to http://localhost:8800 to continue. When you see a screen resembling what is shown below, continue with Step 6.

Step 5b: Use the command line interface when installing via a terminal session outside of the desktop environment.

If NowSMS was previously installed, options might be displayed to update the existing install or remove the service. For a new installation, press the “I” key to install NowSMS.

Program files will be installed in /usr/local/bin

Data files will be stored in /var/lib/nowsms

In most environments, NowSMS might prompt for the root/admin password, if the system requires it to complete the service installation. This password will be used with the sudo command to perform the installation.

Before exiting, NowSMSInstall will display instructions for completing the installation by connecting with a web browser and using a temporary password, similar to this example:

To complete installation remotely, connect to http://192.168.0.99:8800, and login with username admin and temporary password AMGJCF8S

NowSMS defaults to using port 8800 for the web interface that is used for configuring the system. If another application is already using this port, a different port number might be displayed. If you are unable to connect to this port, it may be necessary to open this port in the Linux system firewall. If you wish to use a different port, it is possible to change this later via the web-based configuration interface, or by manually editing /var/lib/nowsms/SMSGW.INI.

Connect with a web browser to this address, and a NowSMS login window will be displayed.

After logging in to this website, the “System Configuration” menu will be displayed, as described in the next step.

Step 6: The “System Configuration” menu should be displayed.

Press the “Create SMS Account” button to define an admin account that will allow you to administer the system.

Define an initial account to be used to administer the system (additional accounts can be configured in the future, as necessary).

We recommend not defining any IP address restrictions on this account at present, as there is a system-wide IP restriction setting that can be applied elsewhere.

We also recommend using an external firewall to limit access to the port number (default 8800) that is being used for the NowSMS web interface.

Press the Save button.

After a few seconds, the system will recognize that an admin account has been defined, and a login window will be displayed. Login with the credentials of the account that was just created.

Step 7: NowSMS NextGen supports MariaDB or MySQL as a back-end database, which allows multiple servers to share the same configuration settings and provide MMSC services.

To enable a database connection, on the “System Configuration” page, scroll down to the header labeled “Database Connection”. Click on this header to open this settings category.

Press “Add Database Connection”.

Specify an IP address and user credentials for connecting to the database server. NowSMS uses two databases, one is exclusively used for message logs, while the other database is used for configuration data and message queues.

If the databases do not exist, NowSMS will attempt to create them when you press “Connect to Database”.

“NowSMS Server ID” is an indicator that will be used in the logs to record which server processed each event. The default value for this setting is the server’s primary IP address, but this value can be set to a simple text-based name for the server.

The default options are recommended for most connections.

If this is the first server to connect to the database, NowSMS will upload the current configuration files to the database.

If another server has previously connected to the database, NowSMS will download the current configuration files from the server and replace any current configuration on the server. If a server has previously connected to the database, but the connection was severed, and you wish to replace the configuration settings in the database use “Upload Current Configuration Files From This Server To Database”.

Press the “Connect to Database” button to login to the database server.

The MMSC will need to restart, and it will be necessary to login again.

Step 8: When the MMSC delivers an MMS message to a subscriber, it sends 2 binary SMS messages to the recipient. This is known as the MMS notification. An SMPP SMSC connection should be configured for the MMSC to use.

Use the “Add SMSC Connection” to define a new SMPP SMSC connection (or expand the “SMSC Connections” section of the configuration by clicking on the section header).

When the “Add SMSC Connection” window opens, click on “SMPP SMSC”.

There are many configuration settings for SMPP connections, but most settings can be left at their default values.

“Server Host Name” must define the IP address or DNS host name of the SMPP server and “Server Port” must define the port number. If the connection uses SSL/TLS, enable that setting. “User Name” (sometimes known as “System ID”) and “Password” refer to the credentials to be sent in the SMPP bind.

“Default Sender Address” specifies a source (sender) address for the SMS messages. The end user will not see this address, but most SMSC will not deliver a message that does not include a source address.

The “Keep-Alive Interval” specifies how often NowSMS will send an “enquire link” packet to the server, in order to keep the connection active. Most SMPP servers will timeout idle connections, but for performance reasons, it is desirable to keep the connection active. The default value is just under one minute, which is below the threshold for most servers, without generating excessive network requests.

The “Window Size for SMPP Async” is a performance related setting. The default value is good for most installations, however if you experience a problem with SMSC timeout errors, replace the value with a blank value to disable SMPP async mode for maximum compatibility.

“Use for any outbound messages” must be enabled to establish this connection as a default route for SMS messages.

Disable the “Receive SMS” and “Bind as Transceiver” settings, as this will be a send-only (transmitter) connection.

Scroll down and press the “Save” button to save the settings.

Test the SMSC connection by sending a simple test message. From the top menu, select “Send Message” / “Text”

Consult “Admin” / “System Log” to review activity if the message is not received.

Step 9: Initial configuration of the MMSC.

The “MMSC Server Settings” is used to configure the basic settings of the MMSC. The image below shows the parameters that need to be configured for most installations.

Mobile phones use the HTTP protocol to interface with the MMSC, issuing HTTP POST requests to send messages and HTTP GET to retrieve messages. Phones will need to be configured with a server address which is a combination of the settings “External Host Name or IP” and “MMSC Port Number”. (The MMSC also sends this host name and port in MMS notifications to tell the receiving device how to receive content.

SMTP/MM4 is used to interconnect with other networks, and typically uses port 25.

The “MM4/E-Mail Domain Name” is the domain name applied to your subscribers when a message is routed out via MM4.

“MSISDN HTTP Header” – The MMS protocol does not define user authentication/identification. The MMSC receives all requests via TCP/IP. There are different ways that the MMSC can authenticate users but all of these techniques involve other network components inserting an HTTP header that contains the MSISDN. This HTTP header is usually X-MSISDN.

This header can be inserted by the SGSN, or other proxies or gateways. Or, the MMSC can use the ICAP protocol to query a network component for the MSISDN.

“Automatically Provision Subscribers” means that the MMSC will automatically provision a subscriber when the subscriber first sends an MMS. By default, the MMSC will only directly deliver MMS messages to provisioned subscribers.

For initial testing purposes, it may be useful to change the default routing to be “Direct Delivery (internal MMSC)”. This setting is configured in “MMSC Connections”:

Note that when an MM4 connection is defined for external routing, that MM4 connection will be configured as the “Default Route” for MMS.

To circumvent the requirement that subscribers must be provisioned, an HTTP-based callback must be created that allows the MMSC to query whether the recipient of a message is local, should be routed to an external route via MM4, or blocked/rejected. The following link describes this interface: https://www.nowsms.com/doc/mmsc-messaging-server/operator-mmsc-considerations/mobile-number-portability-mnp-considerations

Special testing note: If you are experiencing delays implementing the “MSISDN HTTP Header”, there are ways to test the MMSC with real live devices, circumventing the header requirement:

a.) Many modern devices include the sender MSISDN when submitting an MMS message. However, this is not a trustworthy means of identification. To enable this setting for testing purposes, add MSISDNHeaderTrustClient=Yes under the [MMSC] section of MMSC.INI.

b.) If a password is included when manually provisioning an account under “MMSC Users”, the mobile phone can be configured with an account specific URL using the format http://server:port/username=password

Step 10: MM4 Connectivity

Please refer to our training document: NowSMS MMSC Training: MMSC Interconnection Protocol (MM4), which is available at: https://www.nowsms.com/techsupport/training/mmsc-interconnection-protocol-mm4

The configuration settings described in that document include references to the Windows version of NowSMS. Similar settings can be found in the “MMSC Connections” section of the NextGen “System Configuration” interface.

NowSMS NextGen: Multiple Servers for Scalability and Fault Tolerance

2020-10-17T20:55:14Z

To help explain how NowSMS NextGen can support clustered servers for fault tolerance and scalability, we are reposting this thread from our support forum.

Hi,

Your release notes for NowSMS NextGen says:

Clustered Servers – Multiple front-end servers can share their workload via a shared database, offering powerful new options for fault tolerant systems and scalability.

And there is also a note about SMSGW.INI configuration changes being propagated to other servers.

Can you provide more detail on how to configure this, and how it works? Limitations?

Hi Peter,

It’s really quite simple.

By default, NowSMS NextGen uses a file and directory based interface. Queued messages are stored as files in particular directories. This is the same format as NowSMS has always used.

One of the questions that we frequently get asked is how to support multiple server configurations, for either fault tolerance, or performance and scalability to support a large number of users/subscribers.

In past versions of NowSMS, we have supported this via shared network storage, essentially multiple servers using mapped drives, so that they can share the same configuration and message queues. While this works, performance problems are too frequent, as network storage is not designed to handle large numbers of transactions involving a lot of small files. However, this is exactly what database servers are designed for.

NowSMS NextGen supports using a database server for its shared storage, currently supporting MariaDB and MySQL. All system configuration, message queues and user accounts are stored in the database. This makes it very easy to have multiple servers cooperating as a cluster to function as one big NowSMS server. This can provide fault tolerance if a particular server fails, and it can also provide scalability.

For example, if you have a large number of SMPP clients or MMSC subscribers, you can use a load balancer to spread them across multiple servers. The clients will have the same experience, regardless of which server they connect to.

All NowSMS NextGen servers connected to the same database can provide the same service. For inbound connections, all servers can process any transaction. But if you want to dedicate particular servers to particular tasks, you can use a load balancer and/or firewall as desired. For example, inbound SMPP connections might be directed to a subset of server.

We also recognize that outbound connections, such as to upstream SMSCs, may have limits on the number of simultaneous connections allowed. So, it may be desirable to dedicate some servers to outbound only connections…this is a configuration option for each individual server.

Here’s what the configuration looks like:

In the web interface, under “Admin/System Configuration”, scroll to “Database Connection”, and click the button to “Add Database Connection”.

This will allow you to define the connection parameters for your MariaDB or MySQL database.

Here you provide the IP address or host name of the database server, and the account credentials. NowSMS uses two databases, one is dedicated to activity/message logs, and the other for configuration, user accounts and message queues. If the databases do not already exist, NowSMS will attempt to create them (assuming sufficient access rights).

A few notes on the config options…

The “NowSMS Server ID” defaults to the server’s IP address, but can be changed as desired. This ID is used primarily for the activity/message logs to report which server processed a transaction.

If this is the first time connecting to a database, NowSMS will automatically upload existing configuration information and user accounts to the database. If the database has previously been initialized, and you wish to replace the existing configuration information and user accounts with the current server’s configuration, enable “Upload Current Configuration Files From This Server To Database”.

If you are migrating an existing server to a database, there is also an option to upload existing log files to the database server.

Assuming the database server credentials are valid, the NowSMS server will need to restart, and you will see the following prompts:

Earlier, I mentioned how an individual server in a cluster can be restricted on whether it supports outbound connections. After the restart, if you log back in, the “Database Connection” settings will allow this option:

That’s a quick overview. If I can provide further clarification, let me know.

Regards,

Bryce Norwood
NowSMS Support

Originally posted @ https://support.nowsms.com/discus/messages/113328/113340.html

NowSMS NextGen for Linux (and Mac)

2020-10-07T03:22:37Z

Now available as a beta release, NowSMS NextGen is the next generation platform of NowSMS, being released initially for Linux and macOS environments.

NowSMS NextGen builds on the foundation of the existing NowSMS product. We reviewed every line of code and every configuration setting, no matter how well hidden. Anything that is possible with NowSMS is possible with NowSMS NextGen.

Initially, NextGen only supports Linux and macOS. A release for Windows is planned for the first half of 2021. Initial Linux support is for the 64-bit AMD/Intel architecture supporting Debian, Red Hat, CentOS, Ubuntu and Mint.

The most significant new feature of NextGen is database support (MariaDB and MySQL). Database support is significant for two reasons:

Log Files – Databases make it far easier to manage and monitor message and traffic history.

Clustered Servers – Multiple front-end servers can share their workload via a shared database, offering powerful new options for fault tolerant systems and scalability.

Speaking of log files, even if you’re not using a database, we’ve made major improvements in our log files. A consistent format and headers make it easy to import these CSV log files into other applications for analysis, even common applications such as Excel and Numbers.

The new web interface has query and export tools, which simplify system management tasks.

Speaking of system management, all configuration and control is via a web interface. This new configuration interface is far more comprehensive than the standalone configuration program of past versions. That said, we still use the same SMSGW.INI config file format, and you can still edit SMSGW.INI directly. Heck, even if you’re in a clustered server environment, we’ll automatically propagate those manual edits out to the other nodes.

On other fronts, we’ve expanded the NowSMS HTTP API to support JSON & XML formats, in addition to the existing HTTP GET or POST URL encoded (form variable formats. These formats are all supported for submitting SMS to NowSMS, or receiving from NowSMS as a 2-way command.

Speaking of HTTP, there is also a new configuration setting to forward a user account’s received messages and delivery reports via HTTP.

There’s more…but, those are the more interesting new features…

As usual, we have a free 30-day trial available for download. It is limited to a throughput of only 30 messages per minute, but if you need to validate higher throughput, contact us for a higher throughput trial license.

For download and setup instructions, read NowSMS NextGen Quick Install Guide

For support or questions, contact us, or visit our Support Forum Website.

Selecting MMS Route when sending MMS

2019-01-14T22:11:21Z

When submitting an MMS message, it is frequently desirable to direct the message to a specific connection. The method for doing this varies depending on the protocol being used to submit the MMS message.

HTTP URL or POST Submission

If you are submitting via HTTP (https://nowsms.com/doc/submitting-mms-messages/now-smsmms-proprietary-url-su bmission), you can specify an MMSCRoute=xxxx parameter, where xxxx is the name of the “MMSC Routing” definition. This will force the MMS message to go out the named route.

PHP

If you are using our PHP example at https://nowsms.com/doc/submitting-mms-messages/send-mms-message-with-php

When building the MMS message add:

$mmsMessage = MmsAddField ($mmsMessage, “MMSCRoute”, “routename”);

Java

If you are using our Java example at https://nowsms.com/doc/submitting-mms-messages/send-mms-message-with-java

When building the MMS message add:

mms.addparameter (“MMSCRoute”, “routename”);

Command Line Interface

If you are using our command line example at https://nowsms.com/doc/submitting-mms-messages/send-mms-message-from-command – line

Include MMSCRoute=routename as a command line parameter.

VB.Net

If you are using our VB.Net example at https://nowsms.com/doc/submitting-mms-messages/send-mms-message-with-vb-net

When building the MMS message add:

form(“MMSCRoute”) = “routename”

C#.Net

If you are using our C#.Net example at https://nowsms.com/doc/submitting-mms-messages/send-mms-message-with-c-net

When building the MMS message add:

form(“MMSCRoute”) = “routename”;

Other Protocols

Sender address based routing is also available, where the outbound MMSC Route is selected based upon a match between the From address in the MMS message and the phone number of the modem.

Note that the modem phone number is not automatically configured by NowSMS (it is not readily available on some operator networks). For modems, this is the phone number configured for the modem in the SMSC list.

For other types of connections, this is the default sender address in the MMSC Routing definition.

Note that this phone number does not need to be the actual phone number, it can be an internal number that is only used for coordinating modem selection. In this way, if multiple modems are configured with the same phone number, a matching sender address can be routed via any matching modem.

Multiple Routes

It is also possible to specify that any of several routes can be used.

Instead of specifying only one routename in any of the above examples, use the following syntax in place of the route name:

route1:route2:route3

(i.e., separate route names with : character)

Priority SMS Message Queue

2018-10-18T16:11:15Z

NowSMS 2018 supports a priority queue for SMS messages. A user account attribute (under “SMS Users”) is use to indicate that all SMS messages submitted by this account should be processed before messages submitted by non-priority accounts.

Limit SMS Messages Sent Per Day, Hour, Minute, or Second

2018-10-17T15:50:11Z

Especially useful for modem connections, NowSMS 2018 supports restrictions that can be used to limit the number of SMS messages sent over any individual SMS connection.

These restrictions can be accessed from the “SMSC” page in the NowSMS configuration. Highlight an SMSC connection and press the “Restrictions” button.

These settings are also available in the NowSMS Cloud Edition under Admin/Modem/Properties.

Daily Message Limit sets a limit on the number of SMS messages sent over this connection during any single day. If this limit is reached, the connection will stop being used for sending SMS until the next day. Messages will continue to be sent using other connections.

Monthly Message Limit sets a limit on the number of SMS messages sent over this connection during any individual month. If this limit is reached, the connection will stop being used for sending SMS until the next month. Messages will continue to be sent using other connections. By default, it is assumed that new months begin on the 1st day of the calendar month, however, a setting is available to define the first day of a new billing month to be used instead.

Quiet Hours define a time period during which no messages should be sent over this connection. Time is configured using a 24 hour clock. For example, to prevent sending messages between 8pm and 8am, define the time period as between 20:00 and 07:59.

Per Minute or Per Second Message Limit is defined using an expression of X messages per Y seconds. For example, to limit an SMPP connection to 5 messages per second, define a limit of 5 messages per 1 seconds. To limit a modem to 10 messages per minute, define a limit of 10 messages per 60 seconds or 1 messages per 6 seconds.

MMS Notifications: SMS Sender Address & SMPP Connection Choice

2017-07-21T19:16:23Z

An interesting series of questions from our support mailbox:

Hi Now SMS Technical Support,
Hope you are all keeping well.
Just had a question. Is there any way to define a sender ID for MMS where the leg out to the SMSC seems to have no Calling Party Address?

Define a “Default Sender Address” under the properties for the SMSC connection.

SMS messages that are generated for MMS notifications are posted by the MMSC with a blank SMS sender address, with the intent that this default sender address is applied.

Thank you for coming back to me. Would this only be used if the sender address was blank and will not override an existing sender address?

I assume there are other applications sending SMS via this same server.

As long as “allow sender address override” is checked, the default value will only be applied for a blank/missing sender. If UNchecked, the default is applied for all.

If I have multiple SMPP connections defined, how do I select a particular SMPP account for MMS notifications?

This is a very good question. For the MMSC, we generally make an assumption that if a server is being used as an MMSC, then it is dedicated to that purpose.

Of course, that is not an absolute requirement…I am just explaining our original design intent.

That said, there is a way to force MMS notifications to a specific SMPP account.

Create an SMS User account named localsystem-mmsc … disable all login protocols so that the user cannot actually login … like this:

For the SMPP connection to be used for MMS Notifications only:

Add localsystem-mmsc to the preferred list…and make certain “Support any outbound message traffic” is checked.

When the preferred list contains one or more user accounts, the connection is preferred for that account and blocked for others. However, for these preferred accounts, normal routing rules still apply. So this combination routes all messages submitted by localsystem-mmsc (an internal name used by the MMSC) only via this SMPP connection, and blocks all others.

Important Note: On most versions of NowSMS, there is a bug where this technique only works if the “Default Sender Address” setting is not blank.

UCP to SMPP Converter / Proxy

2017-07-21T16:20:26Z

We’ve had a few inquiries related to the UCP protocol recently. UCP is a legacy application to SMS protocol that was implemented by SMSCs from a company named CMG. (Bryce posted some background info on this over 12 years ago in response to questions in our support forum at https://support.nowsms.com/discus/messages/1/8150.html)

UCP was never a widely adopted protocol, but for a period of time in the late 1990s to early 2000s, it was the preferred application to SMS protocol for some mobile operators, specifically those using CMG SMSCs.

A few of those operators have continued to support UCP over the years, well past its life expectancy.

It may only be of use to a small audience, but we’ve added UCP server support to NowSMS, so that it can convert and proxy SMS messages from multiple UCP clients to SMPP or HTTP based services.

This is similar to how the existing NowSMS can proxy multiple SMPP clients to an SMPP or HTTP based SMS service.

If you have a need for this capability, please use the contact form at https://nowsms.com/contact to contact us.

Release notes from the beta version that includes this capability:

Added UCP/EMI Server support, allowing UCP clients to connect to NowSMS. UCP is a legacy protocol. This support is mostly useful for proxying UCP clients to send SMS via an SMPP or HTTP based service. The UCP server is enabled by specifying a UCP server port number on the “Web” page of the configuration program.

If clients are authenticating via UCP type 60, an account for the client should be defined in “SMS Users”, with the username and passwword matching UCP credentials (username is typically a short code or phone number), and SMPP access enabled.

It is also possible to authenticate by IP address with or without UCP type 60 authentication by specifying the client IP address as the username of an “SMS Users” account, with SMPP access enabled. (In this authentication by IP address scenario, if the client sends a UCP type 60 auth, it will be accepted regardless of content.)

It is also possible to accept all UCP connections, without defining accounts, by adding UCPAcceptAll=Yes to the [SMSGW] section of SMSGW.INI.

By default, NowSMS will disconnect any clients idle for more than 12 hours. This timeout is configurable using the UCPInactivityTimeout=#### setting in the [SMSGW] section header of SMSGW.INI, where #### is a value in seconds, and 0 disables idle disconnect.

Send MMS Message from PHP Script

2017-07-15T19:35:53Z

Note: For additional APIs for sending and receiving SMS and MMS messages, please see our Developer APIs for SMS + MMS page.

Back in 2003, we posted an example PHP script for sending MMS via NowSMS on our discussion board at https://nowsms.com/discus/messages/1/1113.html.

While this script has worked well over the years, it has a serious limitation in that it does not support SSL/TLS. Version 2 of this script adds support for SSL/TLS.

If you are migrating from the version 1 script, SSL/TLS requires a slight change in parameters. The first two parameters for the old version were host name or IP, followed by the port number. In the new version, instead these are combined into a single parameter, which is the URL of the NowSMS server (e.g., http://127.0.0.1:8800 or https://sample.smshosts.com/).

The Version 2 script can be downloaded at the following link: https://nowsms.com/download/sendmms-php.txt.

The sendmms.php script is considerably more complex than the sendsms.php script. The reason for this increased complexity is because an MMS message is more complex than an SMS message.

The first part of sendmms.php consists of PHP functions that you will call in your PHP script … namely MmsInit, MmsAddField, MmsAddFile and MmsSend. Include these functions in your PHP script “as is” without editing them.

After these functions, sendmms.php contains a simple example showing how to use these functions to send an MMS message through a NowSMS server.

1.) Begin by using MmsInit to initialise the MMS message structure.

$mmsMessage = MmsInit();

2.) Add header fields and attributes desired for your MMS message, calling the MmsAddField fuction.

$mmsMessage = MmsAddField ($mmsMessage, "PhoneNumber", "+447777777777");
$mmsMessage = MmsAddField ($mmsMessage, "MMSFrom", "+447777777777");
$mmsMessage = MmsAddField ($mmsMessage, "MMSSubject", "Subject of Message");
$mmsMessage = MmsAddField ($mmsMessage, "MMSText", "Hello!");

The “PhoneNumber” field specifies the recipient(s) for the MMS message. This can be a comma delimited list of phone numbers, or it can be the name of a NowSMS distribution list.

The “MMSFrom” field specfies the sender of the MMS message. Normally, this would be a phone number, short code or e-mail address. (If the message is sent via a modem, this will be ignored, but if you have multiple modems, this field can be used to select a particular modem.)

The “MMSSubject” field specifies the subject of the MMS message, and is optional.

The “MMSText” field to specifies some text to be included in the MMS message, and is also optional. Text can also be included in an MMS message as a text file reference.

3.) Specify the files (usually images) to include in the MMS message. Files can be added using a local directory path or remote URL. For a local directory path, use MmsAddFile.

The last parameter of MmsAddFile is the MIME content type (e.g., “image/gif”, “image/jpeg”, “image/png”, “text/plain” or “application/smil”). However, note that current versions of NowSMS ignore the MIME content type when messages are submitted via the interface used by this PHP script. Instead, NowSMS uses the file extension to determine the content type (e.g., “.gif”, “.jpg”, “.png”, “.txt”, “.smil”.

$mmsMessage = MmsAddFile ($mmsMessage, "f:/temp/file.gif", "image/gif");

An MMS message can contain one or more of these file objects.

When using MmsAddFile, the files referenced in the PHP script must be local files, residing on the same server as the PHP script.

To include a file (image) by URL reference, instead of a local file, use MmsAddField with field name MMSFile:

$mmsMessage = MmsAddField ($mmsMessage, "MMSFile", "https://nowsms.com/nowsmsicon.png");

4.) Use MmsSend to submit the MMS message to your NowSMS Server.

$nowsmsHostURL  = "https://sample.smshosts.com";    // URL of NowSMS Server
$nowsmsUsername = "username";                       // "SMS Users" account name 
$nowsmsPassword = "password";                       // "SMS Users" account password

$x = MmsSend ($nowsmsHostURL, $nowsmsUsername, $nowsmsPassword, $mmsMessage);

The MmsAddField function can be used to specify any NowSMS URL parameter that is valid for sending an MMS message.

The complete Version 2 script can be downloaded at the following link: https://nowsms.com/download/sendmms-php.txt.

For example … here is an incomplete list of additional parameter fields that can be specfied using the MmsAddField function.

“MMSDeliveryReport” – “Delivery Report” specifies whether or not a delivery report is requested for the message. Set to “Yes” to request a delivery report. Note that any delivery report would be directed back to the phone number or e-mail address specified in the “MMSFrom” address.

“MMSReadReport” – “Read Report” specifies whether or not a read receipt is requested for the message. Note that the receiving client may choose not to send a read receipt. Any read receipt report would be directed back to the phone number or e-mail address specified in the “MMSFrom” address.

“MMSPriority” – “Priority” is a user defined priority to be associated with the message. Generally, any priority definition associated with the message is ignored by the underlying transport, but the receiving client may decide to display messages differently based upon this priority setting.

“MMSMessageClass” – “Message Class” is an attribute defined in the MMS specifications. “Personal” is the message type that is used for standard user-to-user communications. Other defined message classes that are supported by this parameter include: “Informational” and “Advertisement”.

“MMSWAPPush” – Set to “Yes” to indicate that the message being sent should be sent as an “Multimedia WAP Push” message instead of as an MMS message.

It is also possible to specify forward locking and DRM constraints to be applied against the content of the MMS message. Forward locking and DRM constraints apply to non-text parts of the MMS message (i.e., in a forward locked message, text could still be forwarded, but images or video could not). Please note that not all devices support forward locking and DRM constraints, therefore use these parameter settings only after testing thoroughly with mobile phones used by your message recipients.

“MMSForwardLock” – Forward locking is the most basic level of DRM (Digital Rights Management). When “Forward Lock” is set to “Yes”, this indicates that the receiving device should not allow any non-text objects in the message to be forwarded off of the device. The device may allow the user to extract pictures, videos or sounds from the message and save them on the phone. However, any such objects remain forward locked, such that they cannot be forwarded to another user or transferred to another device. (IMPORTANT NOTE: NOT ALL DEVICES SUPPORT FORWARD LOCK, WHEN NOT SUPPORTED THE CONTENT WILL APPEAR AS GARBAGE OR MAY BE REJECTED BY THE OPERATOR MMSC.)

“DRMRestrict” – Beyond forward locking, More advanced DRM (Digital Rights Management) restrictions can be applied to limit the number of times that the user can access an object, or start and end dates can be specified to limit how long the user can access an object.
These advanced DRM restrictions can be applied by setting “DRMRestrict” to “Yes”. When this setting is enabled, forward lock is also implied, and the value of the “MMSForwardLock” setting is ignored. (IMPORTANT NOTE: NOT ALL DEVICES SUPPORT DRM RESTRICTIONS, WHEN NOT SUPPORTED THE CONTENT WILL APPEAR AS GARBAGE OR MAY BE REJECTED BY THE OPERATOR MMSC.)

“DRMRestrictTextXML” – “Yes” specifies that the rights object should be encoded in text XML format. “No” specfies that the rights object should be encoded in binary XML format. The default is “No”.

When DRM Restrictions are specfied, it is generally necessary to specify one or more DRM Permissions and one or more DRM Constraints regarding the MMS message content.

DRM Permissions specify what types of access are allowed against the objects in a message that is protected with DRM.

For example, an audio or video object requires “Play” permission before the user can access it. An image requires “Display” permission before the user can access it, and it requires “Print” permission if the user is to be allowed to print the image to a printer , perhaps over Bluetooth. An application requires “Execute” permission before the user can make use of the application. In all cases, the forward locking is assumed, so that the user is not allowed to forward or transfer the object from the device.

If you are sending multiple types of objects in the MMS message, specify all permissions that are required for the different types of objects that are being sent.

“DRMPermissionPlay” – Set to “Yes” to enable DRM “Play” Permission.

“DRMPermissionDisplay” – Set to “Yes” to enable DRM “Display” Permission.

“DRMPermissionExecute” – Set to “Yes” to enable DRM “Execute” Permission.

“DRMPermissionPrint” – Set to “Yes” to enable DRM “Print” Permission.

DRM Constraints specify constraints with regard to how long a DRM protected object object should remain accessible to the user.

“DRMConstraintCount” – “# of Accesses (count)” specifies the the user can only access the DRM protected object this number of times before access is no longer allowed.

“DRMConstraintStart” – “Start Date (yyyy-mm-dd)” specifies that the user will not be allowed to access the DRM protected object until on or after the specified date. (Note that you must specify the date in yyyy-mm-dd format, e.g., 2008-12-24.)

“DRMConstraintEnd” – “End Date (yyyy-mm-dd)” specifies that the user will not be allowed to access the DRM protected object after the specified date. (Note that you must specify the date in yyyy-mm-dd format, e.g., 2008-02-24.)

“DRMConstraintInterval” – “# of Days (interval)” specifies that the user will be allowed to access the DRM protected object for this number of days after initial receipt of the object. The user can either enter a number of days here, or they can enter any valid value defined for the “” element in the OMA DRM Rights Expression Language specification. For example, P2Y10M15DT10H30M20S represents a duration of 2 years, 10 months, 15 days, 10 hours, 30 minutes and 20 seconds.

Send SMS from PHP Script

2018-01-04T18:26:12Z

Note: For additional APIs for sending and receiving SMS and MMS messages, please see our Developer APIs for SMS + MMS page.

Back in 2003, we posted an example PHP script for sending SMS via NowSMS on our discussion board at https://nowsms.com/discus/messages/1/867.html.

While this script has worked well over the years, it has a serious limitation in that it does not support SSL/TLS. Version 2 of this script adds support for SSL/TLS.

The Version 2 script can be downloaded at the following link: https://nowsms.com/download/sendsms-php.txt.

The SendSMS function is the important part of the example. This is the function that needs to be included in your PHP script. You call this function, specifying the base URL of the NowSMS server, along with a username and password for an “SMS Users” account on the NowSMS server, plus the recipient phone number and text of the SMS message.

The SendSMS function uses these parameters to build an HTTP POST for connecting to the NowSMS server.

Additional optional parameters are supported. For additional information on NowSMS URL parameters, see https://nowsms.com/doc/submitting-sms-messages/url-parameters.

Following the SendSMS function, we show two examples of how this function might be called from within a PHP script. The first example sends an SMS text message with only the required parameters. The second example includes an extra optional parameter to illustrate how these parameters are encoded.

// This code provides an example of how you would call the SendSMS function from within
//  a PHP script to send a message. 
 
SendSMS('https://sample.smshosts.com/', 'username', 'password', '+44999999999', 'Test Message');

// This example adds an additional URL parameter, ReceiptRequested=Yes
SendSMS('https://sample.smshosts.com/', 'username', 'password', '+44999999999', 'Test Message with delivery report', 'ReceiptRequested', 'Yes');

The script detailed below can be downloaded at the following link: https://nowsms.com/download/sendsms-php.txt.

"$phoneNoRecip", 'Text'=>"$msgText");
   if (($n1 != NULL) && ($v1 != NULL)) $postfields[$n1] = $v1;
   if (($n2 != NULL) && ($v2 != NULL)) $postfields[$n2] = $v2;
   if (($n3 != NULL) && ($v3 != NULL)) $postfields[$n3] = $v3;
   if (($n4 != NULL) && ($v4 != NULL)) $postfields[$n4] = $v4;
   if (($n5 != NULL) && ($v5 != NULL)) $postfields[$n5] = $v5;
   if (($n6 != NULL) && ($v6 != NULL)) $postfields[$n6] = $v6;
   if (($n7 != NULL) && ($v7 != NULL)) $postfields[$n7] = $v7;
   if (($n8 != NULL) && ($v8 != NULL)) $postfields[$n8] = $v8;
   if (($n9 != NULL) && ($v9 != NULL)) $postfields[$n9] = $v9;
   $ch = curl_init();
   curl_setopt($ch, CURLOPT_URL, $hostUrl);
   curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
   curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
   curl_setopt($ch, CURLOPT_POST, 1);
   curl_setopt($ch, CURLOPT_POSTFIELDS, $postfields);
// TODO: This script does not currently validate SSL Certificates
// curl_setopt($ch, CURLOPT_VERBOSE, true);
// curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
// curl_setopt($ch, CURLOPT_CAINFO, 'cacert.pem');
   curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0); // change to 1 to verify cert
   curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
   curl_setopt($ch, CURLOPT_USERPWD, "$username:$password");
   curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); 
   $result = curl_exec($ch);

   return $result;

}


// This code provides an example of how you would call the SendSMS function from within
//  a PHP script to send a message. 
// The response from the NowSMS server is echoed back from the script.
 
$x   = SendSMS('https://sample.smshosts.com/', 'username', 'password', '+44999999999', 'Test Message');
echo $x;

// This example adds an additional URL parameter, ReceiptRequested=Yes
$x   = SendSMS('https://sample.smshosts.com/', 'username', 'password', '+44999999999', 'Test Message with delivery report', 'ReceiptRequested', 'Yes');
echo $x;

?>

NowSMS Modem Android App – Installation

2021-03-04T15:39:23Z

This document provides an overview of installation options for the NowSMS Modem App for Android. The NowSMS Modem App allows an Android phone to be used by a NowSMS server as a type of GSM modem. This allows NowSMS to send and receive SMS and MMS messages through one or more Android phones.

Detailed Quick Start Guides are available here.

The NowSMS Modem App can be downloaded directly from the NowSMS website.

Installation via NowSMS Website

Step 1: It is necessary to configure the Android Device to allow applications from unknown sources. This allows the application to be downloaded directly from the NowSMS web site.

The location of this setting varies depending on the Android version and a variety of user interface differentiations from different device manufacturers. We recommend searching in the Settings app for Unknown. This setting is usually found as Unknown Sources or Install Unknown Apps.

On older Android devices, it is usually found as Unknown Sources under Security Settings.

Android will display a caution message about the security implications of installing applications that have not been verified by Google. This setting must be accepted to enable the setting.

We recommend that the Android phone running the NowSMS Modem software should be dedicated to that task and not be used for other applications, to minimize the risk of enabling this setting. This setting may be disabled after the NowSMS Modem application is installed.

More recent versions of Android show this setting as Install Unknown Apps. Here you must give permission to another app, such as a web browser, to allow it to Install Unknown Apps. For the example shown here, we will download the app from the NowSMS website using Chrome as the web browser, so we must give this permission to Chrome.

Step 2:

Open the web browser or Chrome on the device, and enter the direct download URL for the app: https://nowsms.com/app, or go to the NowSMS website at https://nowsms.com, where the menu on the mobile website includes a link to download the app.

Some versions of Android will warn that this type of file may be harmful and require you to select OK before downloading the application.

The NowSMS Modem App is contained in a file named NowSMSModem.apk.

Most recent versions of Android will display a link to open this file.

If the open link does not work, or no option to open the app is displayed, the easiest way to locate the download is to swipe down from the top of the screen where it will be shown in system notifications. Press on the notification to begin the install.

If the download does not appear as a notification, go to Applications and use the Downloads app to locate NowSMSModem.apk.

Step 3: Complete the installation of NowSMSModem.apk by allowing the requested privileges.

It may be necessary to press Next or scroll down before the Install option is presented.

Open the App after it is installed.

Step 4: Refer to the Quick Start Guide for the NowSMS product edition that you are using for information about configuring the link between the app and your NowSMS server.

NowSMS Cloud – Quick Start Guide

2021-03-04T16:06:22Z

The NowSMS Cloud Edition is a quick and efficient way to create SMS and/or MMS applications. As a hosted service, we provision a separate NowSMS server with a unique secure web address for each customer. An app is installed on one or more Android phones to connect the phone(s) to your NowSMS cloud server. All SMS and MMS messages sent or received by your cloud server are routed through your Android phone(s). All Android phones require a standard SIM card that has been activated with a messaging plan appropriate for your messaging requirements.

This is a quick and efficient way to create SMS and/or MMS applications.

NowSMS controls the modem to send and receive SMS and MMS messages.

NowSMS allows end users to send and receive SMS and MMS messages via a web interface or via e-mail.

NowSMS enables applications to send and receive SMS and MMS messages using standard protocols such as HTTP, SMTP, SMPP, or using API examples for Java, PHP, ASP.NET, VB.NET or C#.NET.

System Requirements

1.) Android Phone running version 2.3 or higher.

2.) WiFi or Cellular Data Connectivity for Android Device

3.) The NowSMS server software must be installed on a supported platform, such as Microsoft Windows, Linux, macOS or Raspberry Pi.

Supported SMS and MMS Message Types

SMS text message formats supported include all standard text formats, including long messages, Unicode characters and emoticons. (Other binary SMS formats, such as WAP Push, are not supported at this time, and can only be supported by dedicated GSM modem devices. Message class attributes such as Flash are also not supported by the Android interface.)

MMS support may be limited by content types and size restrictions imposed by the mobile operator.

Important Notes About NowSMS & the Android Phone

Please note that after the NowSMS Modem software is installed on the Android Device, received SMS and MMS messages will be processed by NowSMS instead of the built-in messaging client.

It is possible to configure NowSMS in a send only mode to prevent this, but it is important to note that the NowSMS software assumes that in most configurations, NowSMS will be the only application processing SMS and MMS messages on the device.

Of course, the NowSMS Modem software can be easily removed or temporarily stopped to allow other standard applications to again process messages.

It is also important to note that the NowSMS Modem software may cause the battery of the Android device to be used more quickly. This is because NowSMS keeps a data connection active so that the device is available when messages need to be sent out. In most configurations it is expected that the Android phone will be connected to a power source at all times.

Creating a NowSMS Cloud Account

Step 1: If you do not already have a NowSMS Cloud account, go to https://nowsms.com/cloud and request a free 14-day trial.

When your account is activated, you will receive an email that contains a link to the NowSMS Cloud account, and an activation code. Click on the link in the email to begin the activation process.

The Activation Code should be pre-filled. You will be prompted to provide a User Name and Password for your account. The user name defaults to your email address, but can be changed. After activation, it will be possible to define additional accounts, if needed.

You will then be prompted to connect an Android device.

To continue setup, it is necessary to install the NowSMS Modem App on Android device, and configure this app to connect to the displayed Cloud Server ID.

Installing NowSMS Modem on the Android Phone

Step 2: It is necessary to configure the Android Device to allow applications from unknown sources. This allows the application to be downloaded directly from the NowSMS web site.

More detailed information on this configuration setting is available in the following article: NowSMS Modem Android App – Installation Options.

Step 3: Open the web browser or Chrome on the device, and enter the direct download URL for the app: https://nowsms.com/app, or go to the NowSMS website at https://nowsms.com, where the menu on the mobile website includes a link to download the app.

Some versions of Android will warn that this type of file may be harmful and require you to select OK before downloading the application.

The NowSMS Modem App is contained in a file named NowSMSModem.apk.

Most recent versions of Android will display a link to open this file.

If the download does not appear as a notification, go to Applications and use the Downloads app to locate NowSMSModem.apk.

Step 4: Complete the installation of NowSMSModem.apk by allowing the requested privileges.

It may be necessary to press Next or scroll down before the Install option is presented.

Open the App after it is installed.

Step 5: On most Android devices (4.4/KitKat and later), an extra settings button will be displayed: Hide Messages from SMS App.

By default, on these versions of Android, SMS messages sent or received by NowSMS modem will be logged in the messaging database on the device. This may cause performance or storage issues. This button installs NowSMS Modem as the default messaging application and disables this logging.

Step 6: On the Android Device, under Settings, configure this Cloud Server ID to match the ID that was displayed in the NowSMS Cloud login. Configure the same Device Name and Shared Secret in both locations, and press the Save button in the Android app.

Step 7: When the NowSMS server confirms that it has connected with the device, it will display a confirmation message.

Next, the device connection properties will be displayed.

Press Save to complete the modem configuration.

Step 8: To verify the connection is working, use the menu to navigate to the Send Text Message page, and attempt to send a message.

NowSMS Spring 2017 Update

2017-04-11T21:09:55Z

New releases of the Now SMS/MMS Gateway and NowSMS Lite are now available (Version 2017.04.07). Downloads are available at https://nowsms.com/download-free-trial. Customers with an active Maintenance Agreement can download the 30-day trial version to update a licensed installation. If you have questions about update eligibility or maintenance agreements, please contact us.

Highlights of the new features and enhancements in this release include:

New & Improved Connectivity for Android Modems

NowSMS now supports connecting to an Android phone as a modem using either WiFi or cellular data, providing connectivity options for remote devices and geographic distribution.

There are 3 ways to configure this connectivity:

1.) Local WiFi Mode – The Android device is connected to WiFi and is on the same network as the NowSMS PC. When running on the same local network, the NowSMS PC and Android device can find each other without requiring manual IP address configuration.

2.) Remote Direct Mode – The Android device is configured to maintain a constant connection to the NowSMS server, using WiFi or cellular data. The NowSMS PC must be accessible via a static/fixed IP address or internet host name. If using WiFi on the Android device, the NowSMS PC can use a static IP on the same LAN. If using cellular data, the NowSMS PC must be accessible over the internet (or via a VPN, which is beyond the scope of this guide).

3.) Remote via Cloud – This is the easiest option if you are not familiar with, or do not wish to be concerned with networking requirements. The Android device and NowSMS PC both maintain a connection to a secure cloud service which establishes a secure and encrypted tunnel for communication.

IPv6 Support

IPv6 is now supported for all product functionality with two very minor exceptions:

1.) Sending MMS via USB/serial GSM modem only supports IPv4 APNs (if IPv6 APN support is required, use an Android device as a modem

2.) The local WiFi interface for Android devices as modems requires IPv4.

Blacklist/Blocked Number List

System-wide Blacklist/Blocked Number support is accessible via the following interfaces:

1.) Web Interface under Admin/Blocked Numbers

2.) Text file Blacklist.TXT in the DLISTS directory

3.) Public distribution list named Blacklist can be updated via DList APIs.

USB GSM Modem Improvements

We understand that some of our customers are uncomfortable with the reliability of using Android devices as modems.

In this release, we have implemented support for simultaneous MMS transmission with multiple USB or serial GSM modems. In previous releases, simultaneous MMS trannsmssion could not occur when multiple USB/serial GSM modems were connected to the same mobile operator.

MMS sending and receiving is now supported for mobile operator settings that do not use a WAP gateway or proxy.

SSL/TLS Updates

We have recently completed an extensive review of current best practices for SSL/TLS, and web browser compatibility issues. The SSL/TLS driver has been updated to be based on OpenSSL 1.0.2k, and implements best practices to enable an “A” grade from sslLabs.com.

Key changes:

SSL 3 has serious vulnerabilities and is no longer supported (Microsoft Internet Explorer 6 and earlier no longer supported).
TLS 1.0 thru 1.2 are supported, with options available to disable TLS 1.0 and/or TLS 1.1. Disabling TLS 1.0/1.1 is recommended for most installations. TLS 1.2 has the following minimum client version requirements: IE 11, iOS 6, OS X 10.9 or Android 4.4/KitKat.
Known weak ciphers, including RC4 and 3DES, have been disabled. (Supported ciphers can be manually configured if desired.)
Session caching and session tickets enabled
ECDH key reuse disabled
Forward secrecy enabled

To disable TLS 1.0 and 1.1, create a CIPHER.INI file with the following content:

[Cipher]
DisableTLS1.0=Yes
DisableTLS1.1=Yes

To modify supported ciphers, use an OpenSSL format cipher string in a Cipher= parameter setting of this same file. Use care when modifying cipher support, as proper configuration can be complex. As a starting point, the default cipher string for NowSMS 2017 is:

Cipher=!ECDHE-RSA-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:DHE-RSA-DES-CBC3-SHA:DES-CBC3-SHA:!aNULL:!eNULL:!RC4:!LOW:!MD5:!EXP:!PSK:!SRP:!DSS

Real World MM4 Interoperability Issues

This release addresses an issue where some operator MMSCs were not complaining that they were not receiving delivery reports from our MMSC. This issue was caused because the other MMSC was using the MM4 “X-Mms-Originator-R/S-Delivery-Report:Yes” header to request a delivery report independent of whether or not one was requested by the message originator. These delivery report requests are now supported.

A time conversion error was found that could occur when processing expiry dates on inbound MM4 messages. If an absolute expiration date is specified in the inbound MM4, in some cases, NowSMS would translate this as one hour earlier than intended. In one customer installation, an interconnect partner was setting the expiration date in MM4 messages to one hour ahead of the current time. As a result, the MMS notification to devices would contain an expiration date of the current time, or a time that had just passed, causing the device to ignore the notification as expired. (Note that these expiration times apply to how long delivery attempts should occur, they do not affect retention time on the receiving device.)

MMSC Denial Of Service Issue

This release fixes a denial of service issue that could be triggered by submission of an extremely large MMS message.

Customers who have not updated to this release are urged to apply the setting MmsMessageSizeLimit=4096 under the [MMSC] header of MMSC.INI. This sets a systemwide MMS size limit of 4MB (4096KB). Most MMS clients have limits of 1MB or 2MB.

Now SMS/MMS Android Modem – Quick Start Guide

2021-03-04T16:06:13Z

This document is intended to provide a quick start for setting up the Now SMS/MMS Gateway to use an Android modem for sending and/or receiving SMS and/or MMS messages. The configuration steps are similar in NowSMS Editions, however there are separate Quick Start Guides available for NowSMS Lite and NowSMS Cloud Edition that contain instructions specific to those products.

GSM Modems are a quick and efficient way to prototype and develop SMS and/or MMS applications. No special service provider subscriptions are required, just a GSM modem a standard SIM card that has been activated for use with a mobile operator.

NowSMS controls the modem to send and receive SMS and MMS messages.

NowSMS allows end users to send and receive SMS and MMS messages via a web interface or e-mail.

NowSMS enables applications to send and receive SMS and MMS messages using standard protocols such as HTTP, SMTP/POP3/IMAP, SMPP or MM7, or using API examples for Java, PHP, VB.NET, C#.NET, ASP.NET or command-line interfaces.

NowSMS supports the ability to use Android phones as GSM modem devices for both sending and receiving SMS and MMS messages. To facilitate messaging volume growth, additional modems can be added, or NowSMS can be reconfigured to use service provider connections.

For most customers, using an Android phone as a modem is preferable to using a dedicated GSM modem device. These reasons include:

LTE Support – LTE based Android devices can provide higher speed support for MMS sending and receiving.
Network Compatibility – Some mobile operators (and modem device manufacturers) assume that modems are used for internet access only and disable SMS and/or MMS support for modems. This is not an issue for Android phones.
CDMA Support – For years, US based customers have asked us about modems that can support Verizon and Sprint. Android phone support allows us to support those network operators using both CDMA and high speed LTE.
Broad Device Availability – For customers interested in trying NowSMS, it is far easier to locate or acquire an Android device than a conventional modem.
MMS Performance – With conventional GSM modems, MMS performance is limited by the mode switching required to switch between data and SMS channels. There are no mode switching delays mixing SMS and MMS traffic on Android devices.
Multiple Modems – USB connectivity (and driver quality or lack thereof) is a major limitation for systems with multiple conventional GSM modems. For Android phones, the NowSMS server connects to the Android phones over WiFi or cellular data, providing far greater performance for NowSMS to simultaneously control multiple modems. Modems can even be located in different physical locations to maximize signal strength. (The NowSMS server communicates over WiFi or cellular data to an app running on the Android phone.)

System Requirements

1.) Android Phone running version 2.3 or higher.

2.) WiFi or Cellular Data Connectivity for Android Device

3.) The NowSMS server software must be installed on a supported platform, such as Microsoft Windows, Linux, macOS or Raspberry Pi.

Supported SMS and MMS Message Types

MMS support may be limited by content types and size restrictions imposed by the mobile operator.

Connectivity Options

The NowSMS server software will communicate with the Android device using TCP/IP.

There are 3 ways to configure this connectivity:

1.) Remote Direct Mode – The Android device is configured to maintain a constant connection to the NowSMS server, using WiFi or cellular data. The NowSMS PC must be accessible via a static/fixed IP address or internet host name. If using WiFi on the Android device, the NowSMS PC can use a static IP on the same LAN. If using cellular data, the NowSMS PC must be accessible over the internet (or via a VPN, which is beyond the scope of this guide).

2.) Remote via Cloud – This is the easiest option if you are not familiar with, or do not wish to be concerned with networking requirements. The Android device and NowSMS PC both maintain a connection to a secure cloud service which establishes a secure and encrypted tunnel for communication.

3.) Local WiFi Mode – This option is only supported by the Windows version of NowSMS, and is not recommended because of troubleshooting difficulties in some environments. The Android device is connected to WiFi and is on the same network as the NowSMS PC. When running on the same local network, the NowSMS PC and Android device can find each other without requiring manual IP address configuration.

Important Notes About NowSMS & the Android Phone

Please note that after the NowSMS Modem software is installed on the Android Device, received SMS and MMS messages will be processed by NowSMS instead of the built-in messaging client.

Of course, the NowSMS Modem software can be easily removed or temporarily stopped to allow other standard applications to again process messages.

It is also important to note that the NowSMS Modem software will cause the battery of the Android device to be used more quickly. This is because NowSMS keeps WiFi active so that the device is available when messages need to be sent out. In most configurations it is expected that the Android phone will be connected to a power source at all times.

Installing NowSMS Modem on the Android Phone

Step 1: It is necessary to configure the Android Device to allow applications from unknown sources. This allows the application to be downloaded directly from the NowSMS web site.

More detailed information on this configuration setting is available in the following article: NowSMS Modem Android App – Installation Options.

Step 2: Open the web browser or Chrome on the device, and enter the direct download URL for the app: https://nowsms.com/app, or go to the NowSMS website at https://nowsms.com, where the menu on the mobile website includes a link to download the app.

Some versions of Android will warn that this type of file may be harmful and require you to select OK before downloading the application.

The NowSMS Modem App is contained in a file named NowSMSModem.apk.

Most recent versions of Android will display a link to open this file.

If the download does not appear as a notification, go to Applications and use the Downloads app to locate NowSMSModem.apk.

Step 3: Complete the installation of NowSMSModem.apk by allowing the requested privileges.

It may be necessary to press Next or scroll down before the Install option is presented.

Open the App after it is installed.

Step 4: Configure NowSMS Modem by opening the application.

The default settings assume the device is using WiFi to connect to NowSMS on the same Local Area Network. This connectivity setting is only available under Windows. In Linux/Mac environments, you must use Remote Direct or Remote Via Cloud.

Other connectivity options require additional setup on the NowSMS server, and are discussed later in this document.

We recommend configuring the Device Name setting to a name appropriate for your installation. The default Device Name is the phone number, if it is available from the network. Some networks do not allow the phone number to be read by applications. In those instances, the Device Name will default to an Android unique device identifier.

Press Settings to change the Device Name, and then press Save.

Step 5: On most Android devices (4.4/KitKat and later), an additional settings button will be displayed: Hide Messages from SMS App.

Step 6: The Android phone can now be accessed from a NowSMS installation. Note that the messages received counter will display “(not enabled)”until a PC running NowSMS has been configured to receive messages from this modem.

Installing NowSMS on a Windows PC

A fully functional, but time limited, trial version of NowSMS can be downloaded from the NowSMS web site at https://nowsms.com/download-free-trial.

Run nowsms.exe to install or update the Now SMS/MMS Gateway software.

The installation requires administrative privileges on the Windows system and Windows will display a warning about administrative privileges before installing the application.

The default installation settings are acceptable for most installations, and the sequence of installation prompts should resemble the following. The button that must be pressed to continue is highlighted in the following images.

When the installation is finished, NowSMS may again display a prompt about the number of days remaining in the trial license. Press OK to continue.

Configuring NowSMS

Configure NowSMS to use the Android device as an SMSC connection.

There are 3 ways to configure the connectivity between NowSMS and the Android device:

1.) Local WiFi – The Android device is connected to WiFi and is on the same network as the NowSMS PC. When running on the same local network, the NowSMS PC and Android device can find each other without requiring manual IP address configuration.

2.) Remote Direct – The Android device is configured to maintain a constant connection to the NowSMS server, using WiFi or cellular data. The NowSMS PC must be accessible via a static/fixed IP address or internet host name. If using WiFi on the Android device, the NowSMS PC can use a static IP on the same LAN. If using cellular data, the NowSMS PC must be accessible over the internet (or via a VPN, which is beyond the scope of this guide).

Local WiFi Mode

In Local WiFi Mode, the Android device is connected to WiFi and is on the same network as the NowSMS PC. NowSMS will query the local network to locate Android devices with the NowSMS Modem application loaded, and they will be displayed in a list. It may take up to 60 seconds for NowSMS to locate the device.

Select the device and press Add Modem.

In some cases, NowSMS may not be able to find the Android device. Possible reasons for this include:

1.) NowSMS and the Android device might be connected to different access points which create separate networks and are not bridged.

2.) The wireless access point may have isolation mode enabled (very common on guest networks), which prevents devices from communicating with each other.

In situations where the devices cannot communicate locally, Remote via Cloud connectivity should be considered as an alternative.

When the NowSMS server confirms that it has connected with the device, it will display the device connection properties. Press OK to save the configuration.

NowSMS will prompt to ask if a test message should be sent via the modem. Select Yes and enter a phone number to receive the test message when prompted.

Remote Direct Mode

In Remote Direct Mode, the Android device is configured to maintain a constant connection to the NowSMS server, using WiFi or cellular data. The NowSMS PC must be accessible via a static/fixed IP address or internet host name. If using WiFi on the Android device, the NowSMS PC can use a static IP on the same LAN. If using cellular data, the NowSMS PC must be accessible over the internet (or via a VPN, which is beyond the scope of this guide).

To configure this mode, assign a device name and secret to be used by the device.

When you press Add Modem, NowSMS will begin waiting for the device to connect on TCP port 8990.

NowSMS might prompt to confirm starting service processes with the following prompt:

On the Android Device, under Settings, configure the matching Device Name and Shared Secret. For NowSMS Server, provide an IP Address or Internet host name for the device to use when connecting to the server.

When the NowSMS server confirms that it has connected with the device, it will display the device connection properties. Press OK to save the configuration.

NowSMS will prompt to ask if a test message should be sent via the modem. Select Yes and enter a phone number to receive the test message when prompted.

Remote via Cloud Mode

Remote via Cloud mode is the easiest option if you are not familiar with, or do not wish to be concerned with networking requirements. The Android device and NowSMS PC both maintain a connection to a secure cloud service which establishes a secure and encrypted tunnel for communication.

To configure this mode, first assign a device name and secret to be used by the device.

When you press Add Modem, NowSMS might prompt to confirm starting service processes with the following prompt:

NowSMS will connect to the cloud service to acquire a unique Cloud Server ID.

On the Android Device, under Settings, configure this Cloud Server ID, along with the Device Name and Shared Secret.

When the NowSMS server confirms that it has connected with the device, it will display the device connection properties. Press OK to save the configuration.

NowSMS will prompt to ask if a test message should be sent via the modem. Select Yes and enter a phone number to receive the test message when prompted.

NowSMS Web Interface

To access the NowSMS web interface, it is necessary to define account credentials. This is done by creating an SMS user account in the NowSMS configuration (under SMS Users). These account credentials can be entered when accessing the web interface at http://localhost:8800 or http://127.0.0.1:8800 from a web browser on the same system.

NowSMS Lite Android Modem – Quick Start Guide

2021-03-04T16:06:18Z

This document is intended to provide a quick start for setting up NowSMS Lite to use an Android modem for sending and/or receiving SMS and/or MMS messages. The configuration steps are similar in NowSMS Editions, however there are separate Quick Start Guides available for Now SMS/MMS Gateway and NowSMS Cloud Edition that contain instructions specific to those products.

NowSMS controls the modem to send and receive SMS and MMS messages.

NowSMS allows end users to send and receive SMS and MMS messages via a web interface or e-mail.

For most customers, using an Android phone as a modem is preferable to using a dedicated GSM modem device. These reasons include:

LTE Support – LTE based Android devices can provide higher speed support for MMS sending and receiving.
Network Compatibility – Some mobile operators (and modem device manufacturers) assume that modems are used for internet access only and disable SMS and/or MMS support for modems. This is not an issue for Android phones.
CDMA Support – For years, US based customers have asked us about modems that can support Verizon and Sprint. Android phone support allows us to support those network operators using both CDMA and high speed LTE.
Broad Device Availability – For customers interested in trying NowSMS, it is far easier to locate or acquire an Android device than a conventional modem.
MMS Performance – With conventional GSM modems, MMS performance is limited by the mode switching required to switch between data and SMS channels. There are no mode switching delays mixing SMS and MMS traffic on Android devices.
Multiple Modems – USB connectivity (and driver quality or lack thereof) is a major limitation for systems with multiple conventional GSM modems. For Android phones, the NowSMS server connects to the Android phones over WiFi or cellular data, providing far greater performance for NowSMS to simultaneously control multiple modems. Modems can even be located in different physical locations to maximize signal strength. (The NowSMS server communicates over WiFi or cellular data to an app running on the Android phone.)

System Requirements

1.) Android Phone running version 2.3 or higher.

2.) WiFi or Cellular Data Connectivity for Android Device

3.) The NowSMS server software must be installed on a supported platform, such as Microsoft Windows, Linux, macOS or Raspberry Pi.

Supported SMS and MMS Message Types

MMS support may be limited by content types and size restrictions imposed by the mobile operator.

Connectivity Options

The Android phone should be running an Android version between Gingerbread (2.3) and Nougat (7.x).

The NowSMS software runs on a Windows PC and will communicate with the Android device using TCP/IP.

There are 2 ways to configure this connectivity in NowSMS Lite:

1.) Remote via Cloud – This is the easiest option if you are not familiar with, or do not wish to be concerned with networking requirements. The Android device and NowSMS PC both maintain a connection to a secure cloud service which establishes a secure and encrypted tunnel for communication.

2.) Local WiFi Mode – The Android device is connected to WiFi and is on the same network as the NowSMS PC. When running on the same local network, the NowSMS PC and Android device can find each other without requiring manual IP address configuration.

Important Notes About NowSMS & the Android Phone

Please note that after the NowSMS Modem software is installed on the Android Device, received SMS and MMS messages will be processed by NowSMS instead of the built-in messaging client.

Of course, the NowSMS Modem software can be easily removed or temporarily stopped to allow other standard applications to again process messages.

Installing NowSMS Modem on the Android Phone

Step 1: It is necessary to configure the Android Device to allow applications from unknown sources. This allows the application to be downloaded directly from the NowSMS web site.

More detailed information on this configuration setting is available in the following article: NowSMS Modem Android App – Installation Options.

Some versions of Android will warn that this type of file may be harmful and require you to select OK before downloading the application.

The NowSMS Modem App is contained in a file named NowSMSModem.apk.

Most recent versions of Android will display a link to open this file.

If the download does not appear as a notification, go to Applications and use the Downloads app to locate NowSMSModem.apk.

Step 3: Complete the installation of NowSMSModem.apk by allowing the requested privileges.

It may be necessary to press Next or scroll down before the Install option is presented.

Open the App after it is installed.

Step 4: Configure NowSMS Modem by opening the application.

The default settings assume the device is using WiFi to connect to NowSMS on the same Local Area Network.

Other connectivity options require additional setup on the NowSMS server, and are discussed later in this document.

Press Settings to change the Device Name, and then press Save.

Step 5: On most Android devices (4.4/KitKat and later), an additional settings button will be displayed: Hide Messages from SMS App.

Installing NowSMS Lite on a Windows PC

A fully functional, but time limited, trial version of NowSMS Lite can be downloaded from the NowSMS web site at https://nowsms.com/download-free-trial.

Run nowsmslite.exe to install the NowSMS Lite software.

The installation requires administrative privileges on the Windows system and Windows will display a warning about administrative privileges before installing the application.

When the installation is finished, NowSMS Lite may again display a prompt about the number of days remaining in the trial license. Press OK to continue.

NowSMS Lite is now loading and querying your local network to look for Android modems. This may take 30 to 45 seconds without any visible notification. If NowSMS Lite does not start within 2 minutes, double click on the NowSMS Lite icon to begin setup.

Configuring NowSMS Lite

There are 2 ways to configure the connectivity between NowSMS Lite and the Android device.

Local WiFi – The Android device is connected to WiFi and is on the same network as the NowSMS PC. When running on the same local network, the NowSMS PC and Android device can find each other without requiring manual IP address configuration.
Remote via Cloud – This is the easiest option if you are not familiar with, or do not wish to be concerned with networking requirements. The Android device and NowSMS PC both maintain a connection to a secure cloud service which establishes a secure and encrypted tunnel for communication.

For Local WiFi Mode, NowSMS Lite will query the local network to locate Android devices with the NowSMS Modem application loaded, and display a list. Select the device and press Next.

In some cases, NowSMS may not be able to find the Android device. Possible reasons for this include:

NowSMS and the Android device might be connected to different access points which create separate networks and are not bridged.
The wireless access point may have isolation mode enabled (very common on guest networks), which prevents devices from communicating with each other.

In situations where the devices cannot communicate locally, Remote via Cloud connectivity should be considered as an alternative. To configure this mode, first assign a device name and secret to be used by the device.

When you press Next, NowSMS might prompt to confirm starting service processes with the following prompt:

NowSMS will connect to the cloud service to acquire a unique Cloud Server ID.

On the Android Device, under Settings, configure this Cloud Server ID, along with the Device Name and Shared Secret.

When the NowSMS server confirms that it has connected with the device, it will display the device connection properties.

MMS messaging may require additional configuration. NowSMS Lite will attempt to read the MMS settings from the device, however in some instances this is not possible or incorrect. This is why we suggest testing MMS sending and receiving on the device before installing the Android app.

If Use Default MMS Settings is checked, this means that NowSMS Lite believes that it has the correct MMS settings for your mobile operator. We recommend pressing Next to continue and use those settings.

If Use Default MMS Settings is not checked, this means that NowSMS Lite cannot determine the correct MMS settings for your mobile operator. In this case the MMS Proxy Address and MMS Server URL settings must be manually configured in NowSMS Lite, and the MMS APN must be configured in the Android device settings.

We recommend using the default settings for ports and protocols during initial configuration. It is not necessary to install the service as this action will be performed automatically when you press Next.

The final installation step is to send test messages to verify that everything is configured correctly. Select Yes and press Next.

Enter a phone number and use the Send Test SMS and Send Test MMS buttons to send test messages.

NowSMS Web Interface

MMSC Interconnection Protocol (MM4)

2017-04-10T17:28:59Z

Download presentation slides

Phone To MMSC Protocol (MM1)

2017-04-10T17:26:22Z

Download presentation slides

MMS Protocol Overview

2017-04-10T17:21:34Z

Download presentation slides

NowSMS Spring 2016 Update

2016-04-12T21:59:13Z

New releases of the Now SMS/MMS Gateway and NowSMS Lite are now available (Version 2016.03.28). Downloads are available at https://nowsms.com/download-free-trial. Customers with an active Maintenance Agreement can download the 30-day trial version to update a licensed installation.

The primary enhancements in this release are performance improvements and a new web user interface. There are also numerous enhancements based on customer feedback, especially from MMSC Customers. Additionally, there are reliability improvements for Android modem configurations.

Performance Improvements

While NowSMS performs well for bulk message processing, we realized that there were a number of areas that we could improve, especially in the case of an idle system waking up to process a new message. When a client submits an SMS message, it may take 1 second before the message is allocated for posting to an outbound connection. Similarly, a received message may have a 1 second wait for the 2-way command processor, and another second waiting for a reply to be posted.

These delays have been removed, so that NowSMS begins immediately processing these messages.

Performance improvements have also been implemented for multiserver configurations where NowSMS is using network storage. We observed one site that experienced sporadic 2-3 second delays with the server accepting some messages from clients. Performance enhancements were implemented to resolve the situation that caused the sporadic delays.

New Web User Interface

The NowSMS web interface has been updated to a modern style that works well on desktop, tablet, and mobile browsers. The new interface simplifies access to features such as address books and distribution lists, and better integrates access to some administrative functionality. (Hint: Only SMS User accounts defined with “Admin Access” have access to the administrative features.)

The admin interface provides access to statistics, message queues, logs, and user account provisioning. Access to configuration settings is not supported at this time.

Private and public address book and distribution lists are supported. Private address book entries are accessible only to the user account that is currently logged in. Public address book entries are accessible to all user accounts, and can be created an/or edited only by user accounts with admin access.

By default, the web interface does not display advanced messaging options that are typically used only by developers. These developer options can be enabled and disabled via the Settings menu.

To completely remove access to these developer options, when defining the user account set “Web Menu Options” to any value other than “All Options Enabled”.

MMSC Enhancements

The performance enhancements in this release are significant for MMSC configurations, but not as significant as for SMS-based configurations. End users expect SMS and MMS message delivery to be instantaneous, but MMS messages have a lag due to data connection establishment and data transmission, which generally take at least a few seconds. In previous releases, when a client submits an MMS message, it may take 1 second before the MMS notification messages are allocated for posting to an SMSC connection, or before an MM4 connection is initiated. This 1 second delay has been removed, which offers a small but notable improvement in MMS delivery time, as data connection establishment and transmission is a more significant time factor.

For multiserver configurations where NowSMS is using network storage, the performance enhancements may be more significant. We observed one site that experienced sporadic 2-3 second delays with the server accepting some messages from clients. Performance enhancements were implemented to resolve the situation that caused the sporadic delays.

The DIAMETER/MM9 integration has seen multiple enhancements based upon customer feedback:

The 3GPP-User-Location-Info AVP is supported for systems that require this value to detect roaming (RedKnee).
Response AVP values checking now also checks for response status embedded inside a Multiple Services Credit Control AVP group to support more complex billing scenarios.
Previous versions only supported a server initiated “device watchdog” check, where the MMSC would respond to watchdog checks received from the server, but would not initiate sending watchdog requests to the DIAMETER server. Beginning with this version, a timer can be set for client initiated “device watchdog” checks when the connection is idle.
Add @@VASPID@@ parameter to template variables for messages submitted by a VASP.

Improvements have been implemented for configurations where the MMSC routes MMS notifications via an existing Push Proxy Gateway instead of using SMS including a compatibility fix and implementation of support for retrying MMS notifications.

Android Modem Enhancements

A number of changes have focused on ensuring that the Android modem interface is reliable.

The Android app has been updated to address an issue observed in Android 6.0 and some HTC devices, where the modem app does not automatically reload at startup. This is important, as some Android phones have been known to occasionally restart to recover from error conditions.

By default, NowSMS now polls Android modem devices every 3 minutes (a configurable setting) to verify that they are still active. In previous versions, this default was 10 minutes. If the new version of the Android app does not see activity within that period, it asssumes there is a problem and begins to take corrective action to recover from problems that have been observed at various installations.

A setting has been added to prevent NowSMS from keeping the screen on when an Android device is plugged in. This setting should be used with caution, as keeping the screen on improves performance and reliability of many Android devices.

Detailed Change Log

Details of additional changes and enhancements can be found in our change log at https://nowsms.com/download/changes.txt.

NowSMS and Windows 10 Information

2015-07-29T19:05:41Z

We have been testing NowSMS and NowSMS Lite with preview editions of Windows 10 for months.

However, today’s release version of Windows 10 presents two issues that we did not encounter with the preview releases.

For a new installation, NowSMS and NowSMS Lite 2014 and 2015 versions will both function correctly under Windows 10. There are no special considerations.

Existing NowSMS installations upgrading from earlier versions of Windows to Windows 10 may encounter two issues. (We even encountered these issues upgrading from a Windows 10 Preview Release to the official release.)

Issue #1 – For trial versions only, upgrading an existing NowSMS trial installation to Windows 10 may cause the trial to expire early.

New trial installations on Windows 10 will encounter no problems, it is only trials running on a system that is being upgraded which may be affected.

Purchased licenses are also not affected.

For customers affected by this issue, please use the form at https://nowsms.com/contact to request a trial period extension. You must include the “Installation Reference Code” reported by NowSMS on the “Serial #” page. If you are planning to upgrade a NowSMS trial installation to Windows 10, this extension may be requested in advance as early as 48 hours in advance.

Issue #2 – After upgrading to the official release version of Windows 10, the NowSMS services may appear stuck. NowSMS configuration will report that the services are active, however web access is not available. Attempts to stop or remove the NowSMS services may hang.

This appears to be caused by a problem in the services registry caused by the Windows 10 upgrade, which prevents the NowSMS services from loading correctly. The problem is easily resolved by removing and reinstalling the NowSMS services. However, some extra steps must be followed to remove the stuck services.

The process differs slightly depending on whether you are running NowSMS Lite or one of the other full featured NowSMS Editions. We will first describe the process for the full versions of NowSMS. Scroll down for the NowSMS Lite specific procedure.

To verify that the NowSMS services are stuck, use the Windows Services app.

NowSMS uses two services, as shown above. If the “Status” of either service is “Starting” or “Stopping” (instead of “Running”) or the “Startup Type” is “Disabled”, then there is a problem.

The first step is to remove the services using the NowSMS configuration program.

To avoid excessive confirmation prompts, we recommend launching NowSMS with administrator rights. Locate the NowSMS app, and right click to “Run as administrator”.

Confirm this when prompted by User Account Control.

On the NowSMS configuration “Service” page, locate the “Run as a service” checkbox next to “SMS Gateway Service” and uncheck this option.

When prompted, confirm that you wish to remove the service.

At this point, NowSMS may appear to hang because the service controller is stuck.

To fix this, load the Windows Task Manager.

Initially, the Task Manager will display limited information. Click “More details” to display more information.

Under the “Background processes” list, locate smsgwnt.exe.

Highlight smsgwnt.exe and press the “End task” button.

NowSMS should wake up and report that the service has been removed.

Return to the NowSMS configuration “Service” page, locate the “Run as a service” checkbox next to “MMSC Service” and uncheck this option, and confirm the service should be removed when prompted.

At this point, NowSMS may appear to hang again because the service controller is stuck.

Return to the Task Manager and under the “Background processes” list, locate mmscnt.exe

Highlight mmscnt.exe and press the “End task” button.

NowSMS should wake up and report that the service has been removed.

At this point, both “Run as a service” checkboxes should be unchecked, with indications that the services are not installed.

Check the “Run as a service” checkboxes to reinstall the NowSMS services.

NowSMS should now respond as expected.

NowSMS Lite Instructions

To verify that the NowSMS services are stuck, use the Windows Services app.

NowSMS Lite uses two services, as shown above. If the “Status” of either service is “Starting” or “Stopping” (instead of “Running”) or the “Startup Type” is “Disabled”, then there is a problem.

The first step is to remove the services using the NowSMS Lite configuration program.

To avoid excessive confirmation prompts, we recommend launching NowSMS Lite with administrator rights. Locate the NowSMS Lite configuration app, and right click to “Run as administrator”.

Confirm this when prompted by User Account Control. (Note that the program name will be smslite.exe instead of smsgw.exe.

On the NowSMS Lite configuration “Status” page, locate the “Run as a service” checkbox next to “NowSMS Lite Service” and uncheck this option.

When prompted, confirm that you wish to remove the service.

At this point, NowSMS may appear to hang because the service controller is stuck.

To fix this, load the Windows Task Manager.

Initially, the Task Manager will display limited information. Click “More details” to display more information.

Under the “Background processes” list, locate smsgwnt.exe.

Highlight smsgwnt.exe and press the “End task” button.

In the same list, locate mmscnt.exe.

Highlight mmscnt.exe and press the “End task” button.

NowSMS Lite should wake up and indicate that the service is not installed.

Check the “Run as a service” checkbox to reinstall the NowSMS services.

NowSMS Lite should now respond as expected.

2-way SMS access to Microsoft Office, Excel and VBScript

2015-07-29T16:02:21Z

NowSMS 2-way applications are usually built on web technologies, using PHP or ASP.Net scripting. But we do get a fair number of support questions from customers who want to use VBScript.

The advantage of VBScript is that there are numerous examples available for interfacing with Microsoft Office, especially Excel, and no extra programming tools or environments are required.

As a starting point for VBScript, we often refer to this example shared by one of our customers 13 years ago: http://support.nowsms.com/discus/messages/1/333.html

That example VBScript accepts received messages and writes them to a text file log.

If you want to return an SMS reply when processing a received SMS, from within your VBScript, use WScript.Echo to output your SMS reply. When processing a 2-way command, anything that the script writes to the display console is instead sent as an SMS reply.

For example, here is a simple script that echoes back the same text back to the message sender:

Set Args = WScript.Arguments 
For I = 0 to Args.Count - 1 
   if (I > 0) Then 
      LogTxt = LogTxt & " " 
   End if 
   LogTxt = LogTxt & Args(I) 
 Next 
Set Args = nothing 
 
Wscript.Echo "Echo " & LogTxt

The above script loops through all of its command line parameters and stores them as a combined string of text, then uses Wscript.Echo to deliver the reply. Assuming the script is named echo.vs and saved in the folder c:\temp, the following 2-way command can be defined in NowSMS:

c:\windows\system32\cscript.exe //Nologo c:\temp\echo.vbs @@FULLSMS@@

Use * as the Keyword to route all received messages to this 2-way command.

We recommend testing the script from a command prompt window before attempting to deploy as a 2-way command.

From a command prompt window, type that same command, substituting a simulated text message for @@FULLSMS@@. For example:

c:\windows\system32\cscript.exe //Nologo c:\temp\echo.vbs Test Message

The above should display:

Echo Test Message

Interfacing with Microsoft Office applications such as Excel is slightly more difficult.

Below is an example 2-way script that writes received SMS to an existing Excel spreadsheet:

https://nowsms.com/download/2way-excel.vbs.txt

filename = "c:\temp\test.xlsx" 
 
'Parse command line arguments 
 
CmdLine = "" 
 
Set Args = WScript.Arguments  
    For I = 0 to Args.Count - 1  
       if (I > 0) Then  
         CmdLine = CmdLine & " "  
       End if  
       CmdLine = CmdLine & Args(I)  
    Next  
Set Args = nothing  
   
Set xlApp = CreateObject("Excel.Application") 
set xlBook = xlApp.WorkBooks.Open(filename) 
set xlSht = xlApp.activesheet 
 
xlApp.DisplayAlerts = False 
 
'write data into the spreadsheet 
xlSht.Cells(xlSht.UsedRange.Rows.Count+1, 1) = CmdLine 
 
xlBook.Save 
xlBook.Close SaveChanges=True 
xlApp.Quit

This script parses the command line, expecting received SMS messages, and appends them to an Excel spreadsheet.

The spreadsheet must already exist before the script is run the first time.

To test it, add the following 2-way command to NowSMS:

c:\windows\system32\cscript.exe c:\temp\2way-excel.vbs //Nologo @@SENDER@@ @@FULLSMS@@

Unfortunately, you may encounter errors trying to interface with Microsoft Office applications from VBScript using a NowSMS 2-way command. This is because SMS sending and receiving in NowSMS runs in the context of a Windows service, not as a desktop application.

In my case, testing with the above VBScript, I consistently encountered the following error, but only when the VBScript was run by NowSMS as a 2-way command:

c:\temp\2way.vbs(20, 2) Microsoft Excel: Microsoft Excel cannot access the file 'c:\temp\test.xlsx'.

There are several possible reasons:
 - The file name or path does not exist.
 - The file is being used by another program.
 - The workbook you are trying to save has the same name as a currently open workbook.

There is a work-around for this described here: https://social.msdn.microsoft.com/Forums/en-US/b81a3c4e-62db-488b-af06-44421818e f91/excel-2007-automation-on-top-of-a-windows-server-2008-x64?forum=innovateonoffice

The short solution is …

For Windows x64 versions, create this folder:

C:\Windows\SysWOW64\config\systemprofile\Desktop

For Windows x86 versions, create this folder:

C:\Windows\System32\config\systemprofile\Desktop

Once the missing folder is created, the script should be able to access the Office application.

As a further example, it is also possible to extract a range from the spreadsheet to return as an SMS reply. As an example, the following would return the content of cell A1 as a reply. Be sure to perform this command before closing the workbook.

Wscript.Echo xlSht.Range("A1").Value

Additional detail and discussion can be found at our support forum: http://support.nowsms.com/discus/messages/1/73332.html

SSL/TLS – SHA-1 deprecation and SHA-256 Support

2015-07-27T00:17:23Z

This post is for the information of any customers using SSL/TLS server functionality in NowSMS.

The industry has deprecated the use of SHA-1 signed server certificates, in favor of a more secure algorithm known as SHA-256. SHA is a popular hashing algorithm used by the majority of SSL certificates. As computing power has increased the feasibility of breaking the SHA-1 hash has increased. Plans within the industry have been made to transition from SHA-1 to SHA-256. However with recent announcements from Microsoft and Google about depreciating support for SHA-1 in browsers this transition has been accelerated.

For more information on this issue, please refer to the following links:

Some older web browsers do not support SHA-256 and will only support SHA-1. A list that shows which browsers and operating systems support SHA-256 can be found here: https://support.servertastic.com/sha2-sha256-compatibility/ Infer that versions older than those in that list will not support SHA-256. (Windows XP users who have not upgraded to SP3 are the majority of those without support.)

Which SHA algorithm is used is decided by the certificate signing request (CSR). An update for NowSMS to generate SHA-256 CSR can be downloaded at https://nowsms.com/download/smsssl-sha256.zip

This update is only compatible with 2014 and 2015 versions of NowSMS.

To install the update, stop the NowSMS services and exit NowSMS.

Replace the existing SMSSSL.DLL in the Program Files\NowSMS directory with this version.
If you have not previously requested a signed certificate from a certificate authority, simply go to the SSL/TLS page of the NowSMS configuration, and select “Generate Server Certificate”.
Unfortunately, the change to 2048 bit key requirements will cause problems for renewals for customers that already have an SSL certificate signed by a certificate authority (CA).
When your renewal time comes up, many CAs will not renew your certificate until you switch to a SHA-256 signed CSR.
However, if you generate a new server certificate request with NowSMS, this forces the existing certificate to be immediately invalidated, which may cause problems for existing clients during the certificate renewal process. (This problem is not specific to NowSMS … many web server administrators are facing similar problems.)
If you face this renewal issue with NowSMS, follow this procedure:
Locate and backup the following NowSMS files (in either Program Files\NowSMS or ProgramData\NowSMS):
SSL.CRT
SSL.CSR
SSL.CA
SSL.INI
SSL.KEY
On the “SSL/TLS” page of NowSMS, select the option to “Generate Server Certificate”.
You will be warned that doing this will invalidate your existing certificate. If you have backed up the files that are mentioned above, select “Yes” to continue.
After the new certificate signing request has been generated, copy the new versions of SSL.CRT, SSL.CSR, SSL.INI and SSL.KEY to a different location for backup. (Note: There will not be an SSL.CA file as this file will not exist until you get your signed certificate back from the CA.)
Put the old backup copies of these files, including SSL.CA, back in the appropriate NowSMS directory.
Use the new SSL.CSR to request a signed certificate from your CA. When you get the signed certificate back from the CA, save it as SSL.CA.
Copy the new version of these files, including SSL.CA to the appropriate NowSMS directory and restart the NowSMS services.

Operator MMSC without a WAP Gateway (ICAP)

2015-07-22T16:45:33Z

When implementing an MMSC for a mobile operator network, one of the most confusing concepts is how user authentication is usually performed in conjunction with a WAP Gateway.

MMS uses the MM1 Protocol (OMA MMS Encapsulation) for transactions between a mobile device and the MMSC. This protocol does not define how the MMSC identifies and authenticates the subscriber when the MMS client on a mobile device sends or receives a message.

The MMSC is expected to interface with other operator network components to identify and authenticate the subscriber.

When a mobile device connects to a mobile network for TCP/IP-based services, such as MMS, the mobile device is assigned an IP address when it connects to the GGSN. This IP address is dynamically assigned and usually changes between sessions.

When the MMSC receives an MMS request via TCP/IP, it needs to be able to identify the MSISDN associated with the requesting IP Address.

Traditionally, this identification has been facilitated by a WAP Gateway. A mobile operator WAP gateway proxies MMS requests and inserts an HTTP header that contains MSISDN information. This configuration is described in more detail in the following link: Operator MMSC Considerations – User Authentication

As mobile networks have evolved more toward providing direct internet access, there has been increased interest in deploying MMSC services without a WAP Gateway.

The NowSMS MMSC Edition facilitates this by implementing the ICAP protocol. The Internet Content Adaptation Protocol (ICAP) is a lightweight HTTP-like protocol specified in RFC 3507 which is used to extend transparent proxy servers, and in some cases avoid the need for proxy servers.

The NowSMS MMSC Edition includes an ICAP client interface. This interface allows the MMSC to request HTTP header enrichment from an ICAP-based service. The ICAP service inserts an HTTP header that contains MSISDN information, just as would be done if the request were proxied by a WAP Gateway.

The NowSMS MMSC Edition also includes a special license for the NowWAP Proxy to provide the ICAP server interface. NowWAP must be configured to receive a RADIUS accounting feed from the GGSN. Every time a device connects or disconnects from the GGSN, a RADIUS accounting packet reports this activity to NowWAP, so that NowWAP always knows which IP Address has been allocated to which MSISDN.

Details on configuring ICAP settings for user identification can be found in the following link: Operator MMSC Considerations – User Authentication.

Note that this ICAP interface is not limited to user identification. NowWAP can also forward information that is relevant to detecting roaming subscribers as detailed in the following link: Operator MMSC Accounting – Detecting Roaming Subscribers

To facilitate networks that are currently using a WAP gateway but wish to transition to ICAP, note the following considerations:

1.) The “MSISDNHeaderGateways” configuration setting specifies a list of one or more IP addresses from which the MMSC will accept the MSISDN HTTP Header. These requests will be processed by the MMSC without ICAP. Requests from any other IP address will use an ICAP lookup. This means that devices configured with settings to use the WAP gateway will continue to do so, while new devices can be configured with gateway-less settings.

2.) For MMS only device APN settings which include a gateway IP address, it is possible at the network level to route that IP address and port directly to the MMSC. The MMSC will reject any requests for other services, and process any MMS requests normally (assuming an ICAP interface is configured).

Please note that it is not necessary to use ICAP. For many customers, the WAP Gateway configuration is essential as it provides user identification and authentication for other services.

Android Modem – Problems Receiving SMS with 2-way commands

2015-07-21T17:38:33Z

We have recently encountered 2 different scenarios where SMS and MMS messages could be sent, but not received for 2-way command processing.

A key indicator of this problem is when the “SMS Received” counter in the Android app increases, but the “SMS Received” status at the NowSMS server remains blank.

There are two types of configurations that may experience this problem.

If NowSMS was not able to discover the modem automatically, because the modem is on a network, it is possible to manually configure the modem by providing its IP address.

When NowSMS sends an SMS or MMS message, it needs to be able to connect to TCP/IP port 8990 on the Android device.

When the Android device receives an SMS or MMS message, the Android device needs to be able to connect back to port 8990 on the NowSMS server. The Android app uses the NowSMS IP from which it received its most recent request (with “Receive SMS” enabled in the configuration on the NowSMS side). At this time, there is no way to set this IP manually. If you want to use a port other than 8990 on the NowSMS server side, add NowsmsModemPort=#### under the [SMSGW] section of SMSGW.INI. (And restart the SMS service.)

The second type of configuration issue can occur even if NowSMS was able to discover the Android modem automatically.

NowSMS and the Android app both use TCP/IP port 8990 to talk to each other. This port may need to be opened for inbound connections in any firewall software that is running on the NowSMS server.

If you are using only the built-in Windows firewall, check the Windows “Network and Sharing Center” to make sure your network is NOT marked as “Public”. Either “Home” or “Work” is ok, but on some systems the “Public” network settings will block received messages from the Android app.

Here is a screen capture that shows this:

If the PC is connected to a Domain Controller, there may be an additional consideration.

In the Windows Control Panel, look for the Windows Firewall and select “Allow a program through the Windows Firewall. Depending on the version of NowSMS installed, the following entries may be present in the list:

NowSMS Configuration
Now SMS/MMS Gateway
NowSMS MMSC
Now SMS Gateway Lite Edition
Now MMS Gateway Lite Edition

By default, firewall exceptions for these entries might not be enabled for all network types. It may be necessary to enable the exception for both “Domain” and “Private” networks.

New Now SMS/MMS Product Editions

2015-07-20T18:37:50Z

In response to a recent customer survey, we have restructured the Now SMS/MMS Gateway product line to offer additional functionality and pricing options that better match customer needs, and now offer multiple purchase options, including monthly payment options.

Key NowSMS product functionality includes:

Mobile Operator MMSC
Multi-protocol SMS & MMS Message Switch
High Performance SMS Gateway
High Performance MMS Gateway
2-way SMS & MMS Application Enabler
SMS & MMS Gateway for GSM Modems

The following product editions are now available:

NowSMS MMSC Edition: This edition is designed for use as an operator MMSC, and supports full SMS and MMS functionality, including support for automatic provisioning of MMS subscribers. A new ICAP client and server removes the need for purchasing a separate WAP Gateway when customers want to deploy a proxy-less configuration.

NowSMS Gateway Edition: This edition is designed for service providers, corporate customers, developers and testing services. All types of SMS and MMS connectivity are supported. MMS functionality does not support automatic provisioning of MMS subscribers as required in a mobile operator environment. Burst mode support provides higher throughput during peak hours.

NowSMS Modem Edition: This edition is designed for sending and receiving SMS and MMS messages via multiple GSM modems or Android phones only. All developer APIs, including SMPP, HTTP, SMTP, and MM7 are supported for client connections only.

NowSMS Lite (Single Modem Edition): This edition is designed for simplified installation and setup. This edition supports sending and receiving SMS and MMS messages via a single GSM modem or Android phone only. NowSMS Lite can be updated to other editions by purchasing a license upgrade.

The trial version of the Now SMS/MMS Gateway provides the full functionality of all product editions.

For the Gateway and MMSC Editions: Licenses are based upon message throughput expressed in either messages per minute (MPM) or messages per second (MPS).

For the Modem Editions: Licenses are based on the number of modems. Message throughput is dependent on device and network capabilities and restrictions.

We have restructured the pricing for all of the above versions, excluding NowSMS Lite, and now offer multiple purchase options, including monthly payment options. Please contact our sales team (nowsms@nowsms.com or +44 1883 621100) if you require the revised pricing or further information on the version required.

Send WAP Push and Binary SMS with Android phone as modem

2014-09-11T12:18:28Z

We’ve posted an interim release of Now SMS/MMS with some additional features requested by customers using Android phones as modems. It should be noted that most Android modems do not support special binary SMS message types such as WAP Push. This update adds support for binary SMS message types with Android modems, but only for HTC phones, or rooted phones, as described below.

Version 2014.06.30 includes the following changes:

Android modem auto-discovery performance improvements.
Android modem – Implement work-arounds required for sending MMS on Virgin Mobile USA/Sprint/Boost (also requires 2014.06.15 or later app version).
Configuration program: Fix for crash that would occur when adding an Android modem when running on Windows XP.
Android app updated to request the display to remain on (but allowed to dim) while the app is active, only if the device is connected to power. This improves performance and ensures that the device is always available on WiFi. The power button can be used to turn off the screen, but depending on the device, it may take NowSMS several seconds or longer to wake the device when there is a message to be sent. Confirmation added to “Stop” button to prevent the modem service from being accidentally deactivated.
Android modem updated to support sending binary message types when sending via HTC Android phones supporting HTC Sense (includes most HTC phones, excludes CDMA versions, Google Play edition, or custom ROMs). This support requires 2014.06.30 version or later of both Android app and NowSMS server.
Android modem support updated to support binary message types using the Xposed framework on rooted phones. NowSMS can be configured to submit messages requiring PDU mode support in text format with a special prefix, allowing an Xposed framework module to intercept the message and send it out in PDU format. To enable this support, edit SMSGW.INI, and under the [NowSMSModem – devicename] header, add PDUModePrefix=xxxxxxx to specify the prefix to be used when a message needs to be sent out using PDU format. For example, see the following Xposed module: https://github.com/johnzweng/XposedSendRawSMS. To use that module for sending binary messages, add PDUModePrefix=sendSmsByRawPDU|00| to the appropriate NowSMSModem section header in SMSGW.INI. When NowSMS has a binary message to be sent, it will submit the message in text format, starting with this prefix, followed by the PDU.

Update download links can be found at the bottom of the download page: https://nowsms.com/download-free-trial

NowSMS Compatibility with Verizon & Sprint

2014-06-14T17:50:20Z

One of the major benefits of supporting Android modems is compatibility with CDMA and LTE based networks. For years, US based customers have asked us about modems that can support Verizon and Sprint.

NowSMS has long supported GSM modems. GSM modems are specialized devices that accept a SIM card, and connect to a GSM-based mobile network, but are designed to be used by applications and other devices that require mobile network access. NowSMS can send and receive SMS + MMS messages over a GSM modem connection to allow for the development of interactive applications or services, and facilitate store-and-forward M2M (machine-to-machine) communications over a mobile network. Applications can use HTTP, SMPP, MM7, PHP, Java or other interfaces to send and receive these messages via NowSMS.

Of course, NowSMS also supports service provider connections for higher volume messing throughput. But, modems are good for prototyping or applications with lower volume messaging requirements.

With the 2014.05.30 release of NowSMS and NowSMS Lite, we added support for using Android phones as an alternative to GSM modems. One of the major benefits of Android phones is compatibility with CDMA and LTE based networks. In most of the world, GSM is the major mobile phone network technology, and LTE is essentially an upgrade for GSM. However, in the US, Verizon and Sprint use CDMA network technology (and are adding LTE for high speed data).

NowSMS is compatible with Android devices that run on GSM, CDMA and/or LTE.

The 2014.05.30 release was tested with a variety of Android devices running on the Verizon network.

However, it was not tested on the Sprint network. We have identified some quirks with how MMS is implemented on the Sprint network, and an update is required to support Sprint or Sprint-based MVNOs including Virgin Mobile USA and Boost.

An interim release, version 2014.06.15, adds support for Sprint. We will be building this support into the future releases of NowSMS. For now, a separate install of tis version can be downloaded here:

NowSMS/MMS Gateway Version 2014.06.15 with Sprint Support
NowSMS Lite Version 2014.06.15 with Sprint Support

An updated version of the NowSMS Modem app is also required on the Android device, which also identifies itself as Version 2014.06.15. From an Android device, download https://nowsms.com/apkdev for this version.

NowSMS / NowMMS Update 2014.05.30

2014-06-09T16:02:01Z

The focus of this release is enhancements for SMS and MMS gateway functionality, with a particular focus on GSM modem configurations (including support for Android phones as modems), e-mail gateway functionality, and automated application processing of both SMS and MMS messages.

2-Way Commands for SMS and MMS Processing (New 2014 Features)

2014-06-11T13:54:01Z

The 2-Way command feature in NowSMS can be used to build automated SMS and MMS applications. When an SMS or MMS message is received, NowSMS will evaluate the content of the message, and can either execute a program, or connect to an HTTP URL, based upon the content of the message. The program or script can perform actions based upon the message content, and optionally return a reply.

For the NowSMS 2014 release, we have made it easier for 2-Way commands to process both SMS and MMS messages.

Examples of tasks that might be implemented by a 2-way command include:

Database queries and updates
Processing an image or video submission
Keyword based retrieval of relevant content or images (for example real estate or product information)
Allowing end-users to sign up for mobile alert
Forwarding received messages to an email address

The “2-Way” configuration dialog contains settings relevant to the creation of 2-way applications.

The “Process Received SMS Messages” checkbox must be checked in order to enable the gateway to receive and process SMS messages (and optionally MMS messages).

The “Received SMS Command Table” lists all defined commands. Use the “Add” button to add a new 2-way command, or use the “Edit” or “Remove” buttons to manipulate a previously defined command.

The decision of how to process a received message is based upon the first word of the received SMS message, which is referred to as a “Keyword”. (Previous versions of NowSMS referred to this keyword as the “SMS Command Prefix”.) Based upon this keyword, NowSMS will execute a command associated with the keyword. If the received message does not match any defined keyword, then it is considered to be a match for a special wildcard keyword, denoted as *

The 2-way command processor also looks at the phone number to which the message is addressed, or in other words, the receiving (or recipient) phone number. For example, if the message was received by a GSM modem connected to the NowSMS server, the “Receive Phone Number” would be the phone number associated with that modem. Or if connected to an SMS service provider, this may be a short code number associated with your service. This way different 2-way commands can be defined for processing messages that arrive via different SMSC connections. The “Receive Phone Number” can be left blank if a command applies to all phone numbers.

One or more of the following actions can be taken to process the received message:

“Send Text Reply” – Use this option to send a simple automated response when the message is processed.

“Include Image with Reply” – Use this option to send a GIF, PNG or JPEG format image with the response. This will force the response to be sent out as an MMS message instead of as an SMS message.

“Forward To E-Mail Address” – Use this option to forward the received message to an e-mail address. Note that for this setting to work properly, e-mail settings must be configured. For more information on e-mail configuration, refer to https://nowsms.com/tag/e-mail.

“Add To Distribution List” – Use this option to cause the sender address to be added to the public distribution list specified. (If the distribution list does not exist, it will be added when the first request is processed.)

“Remove From Distribution List” – Use this option to cause the sender address to be removed from the public distribution list specified. (If the distribution list is empty after removal, it will be deleted.)

“Run HTTP or Local Command” – Use this option to run a local program (EXE) or connect to an HTTP URL to process the message content.

When a command is executed based upon the receipt of an inbound message, the command line for the program or HTTP request can include replaceable parameters from the contents of the SMS message. The following replaceable parameters are supported:

@@SENDER@@	The phone number of the sender of the SMS Message.
@@SMSPREFIX@@	The first word of the SMS message.
@@SMS@@	The content of the SMS message, except the first word of the message.
@@FULLSMS@@	The complete content of the SMS message.
@@RECIP@@	If available, the phone number that is intended to receive (or did receive, if the message was received via a GSM modem connection) this message.
@@MESSAGEID@@	The local, NowSMS defined ID of the message file in the SMS-IN directory.
@@RECEIPTMESSAGEID@@	If this message is a delivery receipt, this is the message id of the originally sent message. Otherwise, this parameter is blank.
@@SERVICETYPE@@	If this message was received via SMPP, this will contain the service_type value associated with the message. Otherwise, this parameter is blank.
@@SMSCROUTE@@	Identifies the SMSC connection from which this message was received. This will either be the name of the SMSC connection (e.g., Bluetooth Modem or SMPP – a.b.c.d:xyz), or if the SMSC specific section of the SMSGW.INI has a RouteName= setting associated with the SMSC, this parameter will have the value of the RouteName= setting.
@@MSGDATE@@	Date on which the message was received by NowSMS in YYYYMMDD format.
@@MSGTIME@@	Time at which the message was received by NowSMS in HHMMSS format. Note: When SMS messages are received via a dedicated (non-Android) GSM modem, NowSMS preserves the SMSC time stamp, and returns this time value for the 2-way command place holders @@MSGDATE@@ and @@MSGTIME@@.
@@BINARY@@	Set to “1” if the message is in binary format, “0” otherwise. (Note: Binary messages will only be routed to a 2-way command if the “Command to Execute” is HTTP based, and @@BINARY@@ is present in the “Command to Execute” field.)
@@UDH@@	User Data Header of the received message. (Only for binary messages, see @@BINARY@@ parameter definition.)
@@PID@@	Protocol ID field (PID) of the received message. (Only for binary messages, see @@BINARY@@ parameter definition.)
@@DCS@@	Data Coding Scheme (DCS) of the received message. (Only for binary messages, see @@BINARY@@ parameter definition.)

To return results back to the user, the command can either return a simple text response directly to the gateway (“Reply to sender with command output” is checked), or the command can generate a more complex response to the gateway via a separate HTTP request to the gateway. An executable program returns a simple text response to the gateway by printing results to the screen, where the gateway captures the screen output, and generates an SMS response to send the screen output text back to the sender via SMS. An HTTP request returns a simple text response to the gateway by returning content of the MIME type “text/plain”.

An example 2-way command that runs a local VBScript that creates a log file of received messages can be found at https://nowsms.com/discus/messages/1/333.html.

To specify an HTTP command, the command should start with the prefix http:// … for example, http://server:port/path?sender=@@SENDER@@&message=@@FULLSMS@@.

NowSMS will issue an HTTP GET request using the variable names specified in the command definition. NowSMS can also use a standard URL encoded HTTP POST format. Specify httppost:// instead of http:// and the variables after the ? will be net using HTTP POST instead of HTTP GET.

When an HTTP command is used, if the command is to return a response to the sender directly, the HTTP response must be of the MIME content type “text/plain”.

Some useful examples can be found at https://nowsms.com/discus/messages/1/4520.html.

If the wildcard SMS keyword is not associated with any command, any inbound SMS messages that do not match a keyword will be saved to the SMS-IN directory with a file extension of “.SMS”, and they may be processed by another application independent of NowSMS.

2-Way Commands and MMS

MMS messages are more difficult to process with 2-way commands, because they can contain image, video, or other additional content types.

NowSMS supports using an HTTP file upload format, where the entire MMS message content is posted to an application using HTTP POST. A PHP script that demonstrates this interface can be found in the following article: Receiving MMS Messages with a PHP Script.

Based upon customer feedback, starting with the 2014.05.30 release of NowSMS, an additional option is available which allows MMS messages to be processed together with SMS messages using the same 2-way commands. This option is enabled when “Process Received MMS Messages” and “Use SMS 2-Way Commands” are both checked.

URL references to retrieve any images or other content objects will be added to the 2-way command automatically using variables AttachFile1, AttachFile2, AttachFile3, etc. The URL reference for the file attachment will contain a path only.

This is best explained with an example. Consider the following 2-way command:

http://nowsmslocal/php/log.php?sender=@@SENDER@@&text=@@FULLSMS@@

When an MMS message that includes an image is received, the resulting 2-way command will be similar to this:

http://nowsmslocal/php/log.php?sender=%2B447777777777&text=Test%20Message&AttachFile1=/SMSAttachFile/534E8AEE/IMG_6815.jpg

To retrieve this object, connect to the NowSMS web interface port, including the IP address or host name, such as:

http://127.0.0.1:8800/SMSAttachFile/534E8AEE/IMG_6815.jpg

If multiple files are attached, additional URL parameters will be added using the sequence AttachFile2, AttachFile3, etc.

Using PHP Scripts Without A Separate Web Server

PHP scripts are often used for 2-way SMS or MMS processing, providing a convenient mechanism for processing the received message content in an application, and optionally replying back to the received message, updating or querying a database, or taking other action upon the message which could involve sending one or more messages to other parties.

NowSMS interfaces with PHP scripts via an HTTP interface, which usually requires a separate HTTP web server with PHP installed. NowSMS also features the ability to interface locally with PHP without requiring a separate web server. More information on this capability can be found in the following article: https://nowsms.com/now-sms-native-php-scripts

EMail to SMS & MMS Gateway with NowSMS

2014-05-22T21:05:40Z

E-Mail to SMS & MMS Gateway with NowSMS
Quick Start Guide

One of the typical usage cases for NowSMS is as an E-Mail to SMS & MMS Gateway.

E-Mail users can send an SMS or MMS message by sending an e-mail message to the NowSMS Gateway.
NowSMS converts the message to SMS or MMS format to deliver the message to a mobile phone.
If the mobile phone subscriber replies back with an SMS or MMS, NowSMS can deliver the reply back via e-mail to the original e-mail sender.

NowSMS supports two different configurations for e-mail functionality:

Shared Mailbox Configuration: E-mail users send to a special e-mail address, and specify the recipient phone number at the start of the subject line. (Note: Instead of a phone number, an address book name or distribution list name can be specified in the subject line, making it easier to send messages.)

The Shared Mailbox Configuration is the easiest to configure, as it only requires a normal POP3 or IMAP mailbox. From an internet e-mail architecture perspective, the NowSMS server functions as a POP3 or IMAP client.

SMS Domain Name Configuration: E-mail users specify the recipient phone number as part of the e-mail address (for example, 447777777777@sms.company.com).

The SMS Domain Name Configuration is more complex, because in this configuration, the NowSMS server functions as an SMTP mail server. From a novice perspective, this means that the NowSMS server must be able to accept SMTP connections from the open internet, and an MX record must be defined for the domain name part of the e-mail address (e.g. sms.company.com) that points to the internet address of the NowSMS server.

For most customers, we recommend the Shared Mailbox Configuration. The SMS Domain Name Configuration is powerful, but unless your organization manages its own dedicated e-mail servers, you will likely not have the experience or resources to deploy it. In other words, if your existing e-mail account is with Gmail or another cloud based provider, we strongly recommend the Shared Mailbox Configuration.

For improved readability, a PDF version of this document is available at https://nowsms.com/download/nowsms-email-gateway-quickstart.pdf.

NowSMS Lite only supports the Shared Mailbox Configuration. NowSMS Lite specific functions can be found at https://nowsms.com/email-to-sms-mms-gateway-with-nowsms-lite.

Prerequisites

NowSMS must be installed and able to send SMS and/or MMS Messages.
For the Shared Mailbox Configuration: A POP3 or IMAP4 e-mail account must be created exclusively for use by NowSMS. NowSMS will automatically delete all e-mail messages from the mailbox as they are processed, so this account should be used only for NowSMS.
For the SMS Domain Name Configuration (unless deployed privately as part of an enterprise e-mail system):
1. An internet DNS hostname (A or CNAME) record must exist and resolve to an IP address that allows external connections to the SMTP Port (TCP Port 25) on the NowSMS server.
2. If the NowSMS server is behind a router or firewall, a port forward entry may need to be defined in the router or firewall to allow external connections.
3. An internet DNS MX (Mail eXchange) record must exist for the domain name portion of the SMS e-mail address, pointing to the A or CNAME record that points to the NowSMS server.

Step 1a: (Shared Mailbox Configuration) Connect the E-mail Account

On the “E-Mail” page of the NowSMS configuration, select “Use External IMAP or POP3 Mailbox”. Then press the “SMS Mailbox Settings” button.

E-Mail Address is the e-mail address associated with the account.

Full Name is a descriptive name to be included in the “From” field when e-mail messages are sent by NowSMS.

The remaining settings define how to connect to the mail server for this account. The mail server should support IMAP or POP3 for inbound e-mail, and SMTP for outbound e-mail. The same User Account and Password will be used for both inbound and outbound e-mail connections.

The inbound mail server must support either IMAP or POP3. The IMAP IDLE command is automatically used if available, allowing NowSMS to maintain an “always active” connection to the mail server and receive “push” e-mail. For POP3 connections, or if IMAP IDLE is not supported, NowSMS will check the mail server for new messages periodically based upon the number of seconds configured for the Poll Interval.

(Hint: Gmail supports IMAP IDLE.)

If SSL/TLS is enabled, NowSMS will use encryption for both inbound and outbound connections.

Server addresses can be either a host name or IP address, followed by a port number.

The default POP3 port is 110, or 995 when SSL/TLS is enabled.

The default IMAP port is 143, or 993 when SSL/TLS is enabled.

The default SMTP port is 25, or 587 when SSL/TLS is enabled.

When the OK button is pressed, NowSMS will verify that it can connect to the mailbox, and if successful, return to the E-Mail settings configuration screen.

If an error is reported, the error message should provide more details on the cause of the problem.

Error messages that start with the text “Connection Failed” are basic connectivity failures, indicating that a TCP/IP connection to the specified server was not possible. In these cases, check that the host name and port number are correct. In some environments, a network firewall may need to be reconfigured to allow the connection.

Step 1b: (SMS Domain Name Configuration) Enable the SMTP Server

On the “E-Mail” page of the NowSMS configuration, select “Function as an SMTP Server”. For standard SMTP configurations, the “SMTP Port Number” should be set to 25.

“Enable E-Mail to SMS Support” should be enabled.

NowSMS will only accept email to SMS or MMS messages if they are configured for the domain name specified for “Domain Name for SMS E-Mail”. This is the domain name or subdomain that has been allocated to NowSMS. For example, if NowSMS will be using the e-mail address format number@sms.company.com, this setting should specify sms.company.com as the domain name.

(If you need to accept mail using multiple domain names, there are advanced settings to add additional aliases for this domain name.)

Press the Apply button to save configuration changes.

With these settings, NowSMS is now configured as an SMTP server, waiting for other SMTP mail servers to connect on TCP port number 25 when there are messages to be delivered.

In order for this to happen, other SMTP servers need to know how to connect to your server when they have a message to deliver to your domain.

Within an enterprise mail system, another SMTP server may be configured to relay messages for your SMS domain name. Otherwise the following steps must be taken:

An internet DNS hostname (A or CNAME) record must exist and resolve to an IP address that allows external connections to the SMTP Port (TCP Port 25) on the NowSMS server.
If the NowSMS server is behind a router or firewall, a port forward entry may need to be defined in the router or firewall to allow external connections.
An internet DNS MX (Mail eXchange) record must exist for the domain name portion of the SMS e-mail address, pointing to the A or CNAME record that points to the NowSMS server.

DNS considerations such as the above are not specific to NowSMS, they are basic considerations for any SMTP server.

The MMSC Service must be enabled for the SMTP server to function. For troubleshooting, details of SMTP connections will be logged to the MMSCDEBUG.LOG.

When NowSMS receives an SMS or MMS to route back to e-mail, NowSMS can either function as an “SMTP Smart Mailer” or relay all outbound mail through another SMTP server that acts as an “SMTP Relay Host”. When acting as a smart mailer, NowSMS performs DNS MX record lookups and connects directly to destination SMTP servers to deliver e-mail messages. Some SMTP servers may consider your e-mail messages to be SPAM if you are connected to an ISP with a consumer (not business) account. Some SMTP servers will also reject your e-mail if there is no reverse DNS record (in-addr.arpa PTR record) associated with the IP address of your NowSMS server.

These DNS considerations are very complex. If you are unfamiliar with these DNS terms and considerations, we strongly recommend the Shared Mailbox Configuration for the NowSMS E-Mail Gateway.

Further information on these DNS concepts can be found in the following Wikipedia articles:

http://en.wikipedia.org/wiki/Domain_Name_System

http://en.wikipedia.org/wiki/List_of_DNS_record_types

http://en.wikipedia.org/wiki/MX_record

http://en.wikipedia.org/wiki/Reverse_DNS_lookup

Step 2: Define Which E-Mail Users can send to SMS/MMS

The “Authorised E-Mail to SMS/MMS Senders” button is used to define what e-mail users are allowed to send SMS and/or MMS messages through your gateway.

This Authorised list can specify individual e-mail addresses such as user1@domain.com, or to specify that all e-mail users in a domain should have access, use the wildcard format *@domain.com.

Step 3: Send an E-Mail Message to SMS

From an e-mail client, try sending a message to the e-mail account we configured in the previous step.

The subject line of your e-mail address should start with the phone number that should receive the SMS. The body of the email message should contain the text that should be sent.

It may take several minutes for the message to be routed, depending on the polling interval setting and whether or not the mail server supports IMAP IDLE push e-mail.

If the SMS message is not received, it may be necessary to enable the MMSCDBUG.LOG for further troubleshooting. Or, for the SMS Domain Name Configuration, use tools such as mxlookup to verify DNS is configured correctly, and telnet to verify that SMTP port 25 is externally accessible.

If further assistance is required, please open a support thread on our technical support forum at https://nowsms.com/messages.

Step 4: Routing SMS/MMS Replies Back to E-Mail

If the recipient of the text message replies back, NowSMS can automatically route the reply back to the original e-mail sender if “Automatically Route SMS Replies to E-Mail” is enabled. (Hint: Press the Apply button to activate a changed setting.)

Note that when, “Automatically Route SMS Replies to E-Mail” is enabled, if an SMS or MMS message is received from a phone number that has previously been sent to via the E-Mail gateway, any 2-way commands will not be processed, and the content of the message will be sent back as a reply to the last e-mail address that sent a message to that phone number.

For further clarification, consider the following scenarios where multiple agents or workers share the same NowSMS e-mail gateway.

Send and Reply Scenario 1:

Agent1@domain.com sends a message to Joe at +441234567890.
Joe receives a text message from the phone number associated with the modem attached to NowSMS. If using the default configuration settings in NowSMS, the text message will start with the e-mail address that sent the message, in this case Agent1@domain.com.
Agent2@domain.com sends a message to Tom at +447777777777.
Tom receives a text message from the phone number associated with the modem attached to NowSMS. If using the default configuration settings in NowSMS, the text message will start with the e-mail address that sent the message, in this case Agent2@domain.com.
If Joe replies to the text message, the reply will be sent to Agent1@domain.com. If Tom replies to the text message, the reply will be sent to Agent2@domain.com.

Send and Reply Scenario 2:

Agent1@domain.com sends a message to Joe at +441234567890.
Joe receives a text message from the phone number associated with the modem attached to NowSMS. If using the default configuration settings in NowSMS, the text message will start with the e-mail address that sent the message, in this case Agent1@domain.com.
Agent2@domain.com sends a message to Joe at +441234567890.
Joe receives a text message from the phone number associated with the modem attached to NowSMS. If using the default configuration settings in NowSMS, the text message will start with the e-mail address that sent the message, in this case Agent2@domain.com.
If Joe replies to the text message, the reply will be sent to Agent2@domain.com. It is not possible for Joe to reply to Agent1@domain.com.

In Scenario 2, because modern smart phones display threaded SMS and MMS conversations, and because the e-mail address of the sender is shown at the start of the text message, it should be clear which e-mail address will receive the reply.

To avoid potential problems with Scenario 2, the full version of the Now SMS/MMS Gateway can use multiple modems and/or multiple phone numbers with a service provider. When there is a potential issue with a recipient phone number being contacted by multiple e-mail senders, NowSMS can choose a different modem or sender phone number and maintain multiple conversations.

Step 5: Additional Advanced Settings

There are several other advanced settings available for e-mail gateway processing.

SMS messages have size constraints. For most Latin based languages in Europe and the Americas, it is possible for a single SMS text message to contain up to 160 characters. Longer messages can be sent, but they are sent in separate segmented messages of up to 153 characters each. These segmented messages contain special headers that allow the receiving device to reassemble the message and show it as a single long message.

For other languages, the size restriction is 70 Unicode characters in a single message, or 67 characters per segment for long messages.

“Max SMS messages per e-mail” specifies that if an e-mail message is longer than this number of segments, the e-mail message will be truncated when it reaches the maximum number of SMS segments.

“Use MMS if SMS E-Mail includes image or exceeds text length for SMS” specifies that if an e-mail message exceeds the maximum number of SMS segments, or if the message contains an image attachment, the email should be converted into MMS instead of SMS for delivery.

“Use MMS for all messages from E-Mail” forces the use of MMS for all converted e-mail messages, instead of SMS.

“Automatically Route SMS Replies to E-Mail” was described in the previous section.

“Sender Phone Number(s) for E-mail to SMS” is used to specify which modem or sender phone numbers should be used for e-mail gateway functionality. This can be a single phone number, a comma delimited list of phone numbers, or a range of consecutive phone numbers or short codes.

For example:

+447777777777

+447777777777,+441234567890

+447777777700-+447777777799

88000-88999

To understand why it may be desirable to allocate multiple sender addresses, please refer to the Send and Reply Scenarios in the previous step.

For modem connections, any sender phone number listed here should be defined as the “Phone Number” for the modem under “Properties” for the modem in the “SMSC” configuration.

“Request Delivery Reports when sending from E-Mail” sets a request for delivery reports when an e-mail message is converted to SMS or MMS. Not all mobile operator networks support delivery reports, but where supported, an e-mail reply will be generated back to the sender to provide confirmation of message delivery. (Advanced note: It is also possible to configure NowSMS to generate an interim delivery report when it has posted the message to the mobile operator. For details on this interim report setting, please visit the support forum of our web site at https://nowsms.com/messages.)

“SMS E-Mail Template” specifies a formatting option for how the e-mail message is converted to a text message. For example, some configurations have asked not to include the e-mail sender address in the text message.

Press the Apply button to save configuration changes.

Step 6: Route Other SMS/MMS to E-Mail

Thus far, we have focused on E-Mail to SMS & MMS with support for routing mobile originated replies. It is also possible to forward any received SMS or MMS message to an e-mail address. This is done for SMS messages on the 2-Way configuration page.

“Process received SMS Messages” should be enabled.

“Use 2-way command processor” should be enabled.

Add or Edit the 2-way command table with a command to forward received SMS messages to an e-mail address.

Use * as a Keyword to match any received SMS message.

Check “Forward to E-Mail Address” and specify the e-mail address to which received SMS messages should be sent.

To forward received MMS messages to an e-mail address, it is necessary to apply settings individually for each modem or inbound MMSC VASP connection.

To configure MMS forwarding for MMS messages received via a modem, go to the “SMSC” page of the NowSMS configuration. Highlight a modem and press the “Properties” button.

Press the “MMS Receive Settings” to access the e-mail forwarding option.

After setting the “Forward to E-Mail Address” value, press the “OK” button to save the setting. Press “OK” again to return to the “SMSC” list.

Step 7: Distribution Lists and Address Books

To avoid remembering phone numbers, distribution lists and address books can be created in the NowSMS web interface.

Note: Only distribution lists are supported for the SMS Domain Name Configuration at this time. The Shared Mailbox Configuration supports both distribution lists and address book entries.

All authorized e-mail senders have access to send to public distribution lists or public address book entries. To add or edit public entries, it is necessary to login to the NowSMS web interface with credentials of an SMS User account with “Admin Access”.

APIs are also available for creating and updating these entries using HTTP or direct access to text files.

It is also possible for individual e-mail users to have their own address book and distribution lists. To access this functionality, create an SMS User account where the user name matches the full e-mail address of the e-mail user.

EMail to SMS & MMS Gateway with NowSMS Lite

2014-05-22T20:40:08Z

E-Mail to SMS & MMS Gateway with NowSMS Lite:
Quick Start Guide

One of the typical usage cases for NowSMS is as an E-Mail to SMS & MMS Gateway.

E-Mail users can send an SMS or MMS message by sending an e-mail message to a special e-mail address and specifying the recipient phone number at the start of the subject line.

Or, instead of a phone number, an address book name or distribution list name can be specified in the subject line, making it easier to send messages.

If the recipient replies back with an SMS or MMS, NowSMS can deliver the reply back to the original e-mail sender.

This quick start guide will explain how to quickly setup NowSMS Lite for this type of configuration.

(Note: The full Now SMS/MMS Gateway also supports an alternate e-mail configuration where an entire e-mail domain name is allocated to the gateway, providing the ability to send to phonenumber@domain.com instead of specifying the phone number in the subject.)

For improved readability, a PDF version of this document is available at https://nowsms.com/download/nowsmslite-email-gateway-quickstart.pdf.

Prerequisites

NowSMS Lite must be installed and able to send SMS and/or MMS Messages.
A POP3 or IMAP4 e-mail account must be created exclusively for use by NowSMS. NowSMS will automatically delete all e-mail messages from the mailbox as they are processed, so this account should be used only for NowSMS.

Step1: Connect the E-mail Account

On the “E-Mail” page of the NowSMS Lite configuration, press the “SMS Mailbox Settings” button.