When you wish to submit any type of SMS message, including MMS notifications or WAP push messages, you must submit the request via the gateway’s web interface. The “Web” configuration dialog contains settings relevant to this web interface.
“Port number for web interface” – Configure the gateway to listen for web/HTTP requests on a particular TCP/IP port number. The standard web port on the internet is 80, however you will most likely want to use a non-standard port for this service. The service defaults to the non-standard port 8800.
The PC that is running the gateway might have other web services installed. For this reason, the gateway allows you to specify which of the available IP addresses on the current PC should be used by the gateway. The “IP Address for web interface” prompt displays the available IP addresses on the current PC. To make the gateway service available via any address on the current PC, select “(all available)”, otherwise select a specific IP address.
“Enable menu driven web interface” specifies whether or not an HTML menu will be displayed when a user connects to the gateway via the web interface. This menu interface can be helpful when you are first exploring the features of the gateway. If this menu setting is disabled, then the gateway will require the appropriate URL parameters to perform any tasks. These URL parameters are defined elsewhere in this document in the section titled Submitting SMS Messages – URL Parameters.
Checking “Enable SMPP Server” enables the SMPP Server module of the gateway. While the gateway has the ability to act as an SMPP client, sending and receiving messages through an external SMPP server, it also has the ability to act as an SMPP server to provide message sending and receiving services to other SMPP clients. When you enable the SMPP server, you must specify a TCP/IP “Port number for SMPP Server”. This is a local port number on the gateway PC, which must not be in use by any other applications. The gateway will listen for SMPP clients to connect to the gateway on the port specified. User accounts for SMPP clients are defined on the “SMS Users“ configuration dialog.
The “SMPP Options” button displays some configuration options for the SMPP Server, and is described at the end of this section.
To prevent unauthorized access to the gateway, access should be limited. For most applications, it is recommended that this gateway be installed inside of your firewall, to help ensure that users on external computers cannot access the gateway. As further authorization measures, the gateway can also limit access by restricting address to a limited range of IP addresses, and by requiring a username and password for access.
To define that a username and password be required for access to the gateway, check “Require Authentication for web interface”. HTTP requests must include this username and password in order to issue requests to the gateway. (Note: A standard web browser will prompt for the username and password.) The “SMS Users“ configuration dialog defines user accounts that can access the gateway.
To restrict access to the gateway to a limited range of IP addresses, “Allowed” and “Blocked” lists may be defined. When the gateway receives a new web request, it consults the “Allowed” and “Blocked” lists to determine if web access is allowed from the IP address of the machine that issued the request.
If an address is listed on the “Blocked” list, access will be denied, and the web interface cannot be used to submit an SMS message from that address.
If an address is not listed on the “Blocked” list, and an “Allowed” list is not defined, the web interface can be used to submit an SMS message from that address.
If an address is not listed on the “Blocked” list, and an “Allowed” list is defined, access will be denied if the address is not included in the “Allowed” list.
To add addresses to either list, enter an address in the appropriate text edit area and press the “Add” button. To remove an address from either list, highlight the appropriate address in the list, and press the “Remove” button. Wildcards can be used in a defined IP address to specify that any value in that portion of the IP address will be considered a match. (For example, 192.168.1.* would be considered a match with both 192.168.1.1 and 192.168.1.100.)
It is also possible to define IP address restrictions for individual “SMS Users” accounts.
Checking “Enable Web Account Administration” enables a web-based administration interface that allows for adding, modifying and deleting user accounts that are defined to the NowSMS server. Both “SMS Users” and “MMSC Users” can be edited via this web interface.
To enable this interface, you must define both an “Admin User Name” and “Admin Password”. This user name and password must be supplied upon attempts to enter the admin interface.
It is also possible to restrict access to the web-based administration interface, so that it can only be access from a list of well-known IP addresses, by entering a comma delimited list of IP addresses in the “IP Address Restrictions” field. These IP Address Restrictions apply only to the web-based administration interface. Wildcards can be used in a defined IP address to specify that any value in that portion of the IP address will be considered a match. (For example, 192.168.1.* would be considered a match with both 192.168.1.1 and 192.168.1.100.)
When the Web Account Administration interface is enabled, it is accessible by connecting to the “Port number for web interface” with a relative URI of “/ADMIN”. For example, http://127.0.0.1:8800/ADMIN.
The Web Account Administration interface allows for the creating, editing and deleting of “SMS Users” and “MMSC Users” accounts. It also displays statistical information about the server, and provides remote access to NowSMS log files.
The “SMPP Options” button displays some configuration options for the SMPP Server.
SMPP Server Options
When delivering long text messages that must be segmented over multiple SMS messages, or when delivering messages that include port numbers such as for WAP push, NowSMS encodes the message with the appropriate GSM User Data Header (UDH) fields. When the “Use TLV parameters for port numbers and segmentation” option is enabled, NowSMS will instead use optional TLV parameters in the SMPP header for port numbers and segmentation. Specifically port numbers will be encoded in the source_port and destination_port parameters, and segmentation will be encoded in the sar_msg_ref_num, sar_total_segments, and sar_segment_seqnum parameters. Regardless of the setting of this parameter, SMPP clients can either encode messages for submission to NowSMS using either GSM UDH or TLV parameters. This setting only controls which format NowSMS uses when delivering messages back to SMPP clients.
SMSC Character Set – By default, NowSMS uses the GSM character set when delivering SMS messages via SMPP, and it indicates via the data_coding parameter that the default encoding is used. If you experience a problem where @ symbols and other characters do not appear correctly in received messages, your SMSC client might be expecting a different character set. Assuming that you are working in a GSM environment primarily, first try changing this setting to “IA5 (GSM)”. When this setting is applied, NowSMS will still use the GSM character set, but it will set a flag in the header to indicate this. If the character problems persist, change this setting to “iso-8859-1 (Latin)”, which is the standard character set used in Western Europe.
Enquire Link Timeout – SMPP clients are expected to periodically send enquire_link commands when connected to an SMSC. These commands are used to tell the SMSC that the client is still alive and functioning properly. If NowSMS does not receive an enquire_link command, or some other activity, from a connected SMPP client within this timeout period, NowSMS will automatically disconnect and release the client connection. It is not recommended to set a value for this parameter less than 60 seconds. However, a special setting of 0 can be used to disable this timeout, allowing clients to remain connected without sending the enquire_link command.
Max Connections Per Client – This specifies the maximum number of simultaneous connections allowed from any one SMPP client account (although it is possible to override this value on a per account basis). Note that many SMPP clients create two separate connections, 1 for sending and 1 for receiving, so a value of 1 may cause problems.