NowSMS Release – 2007.06.27

Posted by on Jun 27, 2007 in Software Updates

This document provides release history information for the current release version of the Now SMS & MMS Gateway, which can be downloaded at http://www.nowsms.com/download-free-trial.

This document covers changes between the last major 2006 release and version 2007.06.27.  An interim update may be available at the following link:   http://www.nowsms.com/nowsms-update.

The release history information provides additional information on configuration settings that have been added to address unusual configuration requirements.

A high level summary of new features/capabilities can be found at the following link:  http://www.nowsms.com/newsletter/nowsms2007.htm

2007-06-27:

* MMSC: No longer use quoted-printable encoding for MM7 message encoding. In some situations, previous versions of NowSMS would use quoted-printable encoding, particularly for some SMIL message parts when the SMIL did not contain any line breaks. This was because the same MIME message encoder was used for both MM7 and MM4/SMTP encoding, and MM4/SMTP has encoding restrictions based upon legacy SMTP restrictions that are not a consideration for MM7. (If this change causes a problem in a particular environment, edit MMSC.INI, and under the [MMSC] header, add MM7QuotedPrintableOK=Yes)

* SMS Gateway/MMS/Multimedia WAP Push Submission: Fix for an error that could cause the SMS service to restart if an “MMSFILE” parameter contained a filename that included a “%” character.

* SMS Gateway: Improved handling of PIN codes. NowSMS had problems initialising some modems when a PIN code is active.

* SMS Gateway: Add configuration display to show connected SMPP clients on “Service” (Status) page of configuration dialog.

* SMS Gateway: Add additional features to the web administration interface, such as the “Server Statistics” display and log file viewing.

* SMS Gateway: Additional configuration options added for HTTP SMSCs. By default, when sending a long text message (or any message that includes UDH), NowSMS will encode the text as 7-bit binary. Some HTTP SMSCs do not like this behaviour, so NowSMS now includes an option “Use 7-bit binary encoding for long text messages” that controls whether NowSMS will send the text in 7-bit binary encoding, or as standard text. Similarly, by default, when sending a Unicode message, NowSMS will enocde the text as binary hex. Some HTTP SMSCs do not like this behaviour, so NowSMS now includes an option “Use hex encoding for Unicode messages” that controls whether NowSMS will use binary hex encoding or standard text. An additional configuration setting allows the character set to be specified (NowSMS defaults to “UTF-8”).

* SMS Gateway/SMPP: Add a special configuration setting for customers connecting to Movistar Peru. This provider requires that each SMPP message submission include an incrementing user_message_reference value. To enable this behaviour, edit SMSGW.INI, and add GenerateUserMessageReference=Yes under the [SMPP – server:port] section header for the SMPP connection in the SMSGW.INI.

2007-05-26:

* SMS Gateway: Add new URL parameter for delayed message delivery. This allows messages to be submitted and queued for later processing. To use this feature, including the URL parameter “&DelayUntil=YYYYMMDDHHMM” to specify the date and time until which the message should be delayed, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24 hour format), and MM is the minutes. The “Send Text Message” web interface page has also been updated to support this parameter. The parameter is supported for other types of SMS message submissions via direct URL submission.

* MM7 Message ID Tracking implemented, similar to the existing tracking of SMPP Message IDs. When a message is submitted to an upstream MMSC, that MMSC will assign a new Message ID. NowSMS now tracks the upstream Message ID assignments, so that if it receives a delivery receipt or read receipt from the upstream connection, it can remap the Message ID to the one originally assigned by NowSMS. NowSMS also tracks when messages were submitted by an “MMSC VASP” account, so that any delivery receipts or read receipts are routed back to that same account (actually they will be routed to an “MMSC Routing” account with the same name as the “MMSC VASP”). Improvements have also been implemented to allow delivery receipts and read receipts received via an MM1/GSM/GPRS modem connection to be routed back to a VASP. This means that an MM7 application could submit a message that is sent via MM1 over GPRS, and then receive back MM7 delivery reports and read reports, if supported by the mobile operator network.

* MMSC: Add base support for MMS 1.3 with support for application routing for MMS messages, using either the MMS 1.3 application-id headers, or the content-type extensions for application-id as defined in JSR-205. The MMSC now supports the “X-Mms-Applic-Id” and “X-Mms-Reply-Applic-Id” headers which are used for specifying recipient (destination) and sender (source) application-IDs, allowing MMS messages to be routed directly to a phone-based application. (Note for MM7 applications, you must use the REL-6-MM7-1-4 or later MM7 schema to receive application ID headers.) When sending an MMS message via the NowSMS web interface, it is possible to specify a sender and/or recipient application ID by including the application ID as part of a phone number using the format “PhoneNumber:xxxxxxxxxx”, where “xxxxxxxxx” is the application ID. This ability to specify the application ID as part of a phone number is available only for messages submitted via the NowSMS web interface or using the proprietary URL submission format, it is NOT available for submissions using MM1, EAIF, MM4 or MM7. Other protocols must use the appropriate headers defined for the protocol. When MM7 and MM4 applications submit a message with application id headers, the MMSC will encode these values using both the MMS 1.3 application-id headers and the JSR-205 content-type extensions.

* Web Interface/Send MMS Message: Add an “Additional Headers” field to allow more flexibility in generating MMS messages for testing. Text versions of any of the MMS PDU headers for versions 1.0 thru 1.3 can be included in the “Additional Headers” field to supplement or replace the default headers generated by NowSMS when sending an MMS Message. For example, add the following to set the MMS Version to 1.3 and to set a replacement message id value:

X-Mms-MMS-Version: 1.3
X-Mms-Replace-ID: 20070524/12/ABCDEF01@mmsc

* Web Interface/Send MMS Notification: Add an “Additional Headers” field to allow more flexibility in generating MMS notification messages for testing. Text versions of any of the MMS PDU headers for MMS versions 1.0 thru 1.3 can be included in the “Additional Headers” field to supplement or replace the default headers generated by NowSMS when sending an MMS notification. For example, add the following to set the MMS version to 1.3 and the recipient application ID to “TestApplication”:

X-Mms-MMS-Version: 1.3
X-Mms-Applic-ID: TestApplication

This interface can also be used to send MMS PDU types other than m-notification-ind. If “X-Mms-Message-Type:” is included in the “Additional Headers”, then it is possible to leave the “MMS URL” field empty. This allows other types of MMS PDUs to be sent, including “m-delivery-ind”, “m-read-rec-ind”, and “m-cancel-req”.

* MMSC/MM4: Remove “X-Mms-Originator-System:” header from “MM4_delivery_report.REQ” and “MM4_read_reply_report.REQ”, as this header is not explicitly defined for those requests. The “Sender:” header should contain the orignator system address for these requests. Previously NowSMS did set the originator system address in both the “Sender:” and “X-Mms-Originator-System:” headers. Now it will only set the “Sender:” header, and “X-Mms-Orignator-System:” is only used for “MM4_forward.REQ”.

* MMSC: Add configuration option for setting the “MMS Version” associated with different user accounts. This setting is automatically tracked and updated by the MMSC, and under normal circumstances, it is not necessary to change this setting. By default, when a user account is first registered with the MMSC, the MMSC assumes that the user is compatible with MMS 1.0 (unless DefaultMMSVersion=x.x is set under the [MMSC] header of MMSC.INI to indicate a different default MMS version assumption). Each time a user sends a message via the MMSC, the MMSC checks the MMS version of the message and will automatically change the “MMS Version” associated with the user account to match the version number indicated in the message submission. The setting to allow the “MMS Version” associated with the user account to be changed is provided as a testing aid only.

* SMS Gateway: Fix for invalid message that was generated if “Send EMS Text Message” was used, but the message was text only and contained no EMS attributes.

2007-05-14:

* DRM: When sending an object with DRM restrictions, add a configuration option to specify whether the “DRM Rights Format” is “Binary WBXML” or “Text XML”. Newer Nokia phones seem to only support the “Text XML” format for DRM “Combined Delivery”. (“Binary WBXML” is supported for “Separate Delivery” on the affected Nokia phones, which is only possible using DRMCOMP, but not for “Combined Delivery”.) DRMCOMP updated to add support for “-textXML” command line parameter to specify that the “DRM Rights Format” should be “Text XML” instead of the default “Binary WBXML”.

* SMS Gateway/WAP Push: Add new HTML template for “Send WAP Push Message Advanced”. This template allows greater flexibility for sending custom WAP push messages by supporting custom content types, as well as the ability to insert custom headers. The “Content-Type” field should contain the content type of the push content. The “Content” field should contain the content of the push. The content can either be encoded as plain text, or for binary content types the content can be represented as a string of hexadecimal characters. The “Content Encoding” field specifies whether the content is plain text or a string of hexadecimal characters. If you are sending one of the content types supported by “Send XML Settings”, but wish to include extra headers, it is also possible for NowSMS to perform XML to WBXML conversion for any of the XML content types supported by “Send XML Settings”. If you wish to have NowSMS perform XML to WBXML conversion, select this conversion option for “Content Encoding”. The “X-WAP-Application-ID:” field can contain a numeric identifier or text string to indicate a destination application id. The “Additional Headers” field can contain a list of additional headers to be included in the WAP Push WSP header. Each header should be on a separate line, with a format of Header-Name: Header-Value. “OTA PIN” and “OTA PIN Type” can also be optionally specified to allow the push message to be signed.

* SMS Gateway: “Send Text Message” template updated to include a “Destination Port” setting, which can be used when sending text messages to a port number corresponding to a Java application on a phone. To specify a port number when submitting a text message via URL submission, include the parameter “&DestPort=####”, where #### is the destination port number value. Additional, URL submission has added support for “&SourcePort=####” to specify the source port. Alternatively, it is possible to include the port number as part of a sender or recipient phone number using the format “PhoneNumber:####”. Please note that if a message is addressed to multiple recipients, it is not possible to specify differnet destination port numbers for different recipients.

* OTA: Old-style Nokia/SonyEricsson OTA templates updated to allow support for WAP2/HTTP port settings. Also, for some SonyEricsson phones (circa 2004 models), to configure an internet profile without a proxy, it is necessary to send a “WAP OTA” with the “WAP Gateway IP Address” field left blank, and the “WAP Gateway Connection Type” set to port “80”.

* MMSC Routing/MM1 over GPRS: Add configuration setting to specify the MMS/MM1 Version to use when communicating with the MMSC.

2007-05-09:

* MMSC: Add support for generating MMS non-delivery notifications when a message expires without being delivered/retrieved by the recipient. To enable this, edit MMSC.INI, and under the [MMSC] header, add NonDeliveryNotificationTimeout=####, where #### is the number of minutes after which to consider a message as being expired.

* MMSC: Add support for additional MMSC.INI setting, under [MMSC] header – SMTPExtraHeader=xxxx allows an extra header to be added to MMS messages that are routed to an e-mail address. (For example, “SMTPExtraHeader=X-Mms: True”)

2007-05-03:

* SMPP Receipt Tracking: Performance enhancements in tracking SMPP message IDs for proper routing of delivery receipts. The message IDs are now tracked in a more efficient database, offering improved performance (especially for 10mps and higher licenses) and decreased disk space utilisation.

* MMSC: Performance enhancements for mid-size (100,000+ users) and large (1,000,000+ users) operator MMSC configurations. Also, performance improvements for the MMSUSER command line utility.

* SMS Gateway: HTTP interface now supports “&LocalUser=” parameter. If this parameter is specified, the message submitted via HTTP is routed to a local “SMS Users” account instead of for outbound routing. All other HTTP parameters (except “MMSFILE” for sending MMS) are supported.

* SMS Gateway: Increase size limit for XML settings documents. Previous binary size limit of 2KB increased to 16KB.

* MMSC: Additional configuration parameter added to force all submitted MMS messages to be automatically BCC’d to an additional recipient. Usually this recipient would be a special short code routed to a VASP or to an e-mail address, where another application is processing the messages for archival, tracking, and/or regulatory requirements. To add an automatic BCC recipient, edit MMSC.INI, and under the [MMSC] header, add AutoBCC=xxxxxxxxxxxx, where xxxxxxxxxxxx is the address that should be added as an additional BCC recipient.

2007-04-12:

* MMSC/MM4: When routing messages via MM4, if there are multiple recipients, NowSMS prefers to submit them one at a time over MM4, as this offers better error handling when dealing with inconsistencies in different MM4 implementations. Some MMSCs do not like the fact that multiple submissions may have the same message ID (as they are the same message, just different recipients), so the MM4 message id is now altered to be unique per recipient instance.

* SMPP Client Configuration: Update edit control in configuration program to allow longer username and password strings.

2007-04-11:

* MMSC/MM4: Because of problems with some MMSCs refusing to accept the “/” character in MMS message-id and transaction-id values for MM4 connections, NowSMS has changed its message id format for MM4 connections to replace the “/” character with a “.” character. The previously added MessageIDPatch=Yes parameter is no longer necessary.

* Receiving MMS over GPRS modem: If NowSMS is configured to route received SMS messages for a modem to a local SMPP user account, and it is also configured to process received MMS messages for that modem, it will no longer route MMS notifications (or any other WAP Push messages) to the local SMPP user account, so that the MMS notifications can be processed to allow retrieval of the MMS message content.

* SMS Gateway: More functions adapted to support sending WAP Push content to IP addresses. “IPNotify” mappings can be defined in MMSC.INI to route virtual phone numbers to IP addresses. Previously this functionality only supported MMS messages, however it has been extended to support other WAP Push content types including “Service Indication”, “Service Load”, and “OMA OTA”, and “XML Settings Documents”. In the MMSC.INI file, it is possible to create an [IPNotify] section. Under this section header, specify PhoneNumber=IP.Address (e.g., +9999999=192.168.1.200), to have MMS notifications and WAP push messages for the specified phone number get routed to the specified IP address. (This feature is intended primarily for testing environments.)

* MM1 over GPRS modem: Fix for timeout problems when sending larger MMS messages (approx > 200KB). Note that many mobile operators have limits on the size of MMS message that they will accept.

* SMPP: Add support for another type of “SMPPOptions” setting when defining optional “TLV” parameters. The “HexString” type is used when it is necessary to define a binary value for a parameter. The SMPPOptions parameter value is specified as a string of hex characters. NowSMS converts the hex characters to binary for insertion into the SMPP request. This support is necessary for unusual data types, such as the source_subaddress and dest_subaddress parameters.

2007-03-15:

* MMS/PHP Script (HTTP Multipart Upload): Convert all text components to UTF-8 character set for consistency. (Most handsets send text in UTF-8 format, but some use 16-bit Unicode.) http://www.nowsms.com/discus/messages/485/18694.html

* SMPP Server: Implement a maximum number of SMPP connections allowed from a single client user account. The default limit is 4 connections. This default can be changed via the updated user interface, or by editing SMSGW.INI, and under the [SMSGW] header, adding SMPPServerMaxConnectionsPerUser=##, where ## is the default number of connections to allow from any one SMPP client account. It is also possible to override this connection limit on a per-account basis. To override the limit for a specific client account, it is necessary to define a limit for the speed at which messages will be received from the account. In the “# Messages/# Seconds” field, enter a value of xxx/yyy/zzz, where “xxx” is the number of messages allowed per “yyy” seconds, and “zzz” is the connection limit to be applied for this account. To disable message speed limits, but define a connection limit, use a value of 0/0/zzz, which indicates no limits, but specifies “zzz” as the connection limit for this account.

* SMPP Server: Add configuration option for using TLV parameters for port numbers and segmentation when delivering messages to an SMPP client. This configuration option can be set via the “SMPP Options” button on the “Web” page of the NowSMS configuration dialog.

2007-03-09:

* GSM Modem Handler: Fix for inability to initialise some modems when running as a service, and the modem is inserted or activated after the service starts. (Problem noticed with internal GRPS/EDGE modems in some Sony laptops, where NowSMS would consistently fail to find the modem if the service starts at boot-up, presumably because the software to install the modem does not complete until after the NowSMS service has already initialised.) If modem initialisation problems are experienced in this version, edit SMSGW.INI, and under [SMSGW], add UseGlobalTAPI=Yes to go back to the old modem handler.

* SMPP: Fix for 2006-10-13 change that caused NowSMS to improperly assume that some received messages were binary instead of text. (In one notable situation, this only affected return receipts for binary messages. Invalid text characters in the return receipt triggered the logic that treated the message as binary.)

* MMSC: Undo 2006-11-16 change to use keep-alive sockets for accounting callbacks. Keep-alive sockets for accounting callbacks are still supported, but are not enabled by default. To enable, set AccountingKeepAlive=Yes under the [SMSGW] header of SMSGW.INI. When keep-alive sockets are enabled, NowSMS will serialise access to the SMS and MMS accounting callbacks, which may cause delays on some systems.

* MMSC: Fix logging so that “read report” messages are distinguished from “delivery report” messages. Also, update the logging so that the “read report” messages report the correct format of the message id to which the report refers (previously the host name was included in the message id reported in the log, whereas it is not included in other log entries).

2007-03-07:

* MMSC: Recipient address conversion/internationalisation – Improve support for MMSC installations supporting clients from more than one country code. Different countries may have different conventions for local phone numbers. Some use a local dialing prefix such as “0”, “8” or “9”, while others do not use a local dialing prefix. NowSMS uses the country code of the sender, and the “MSISDNHeaderLocalPrefix” setting, to convert MMS recipient phone numbers from national to international format. However, different countries may use different local dialing prefixes. NowSMS now allows the local prefix to be configured on a per country code basis, supporting MSISDNHeaderLocalPrefix configuration settings per country code. For example, “MSISDNHeaderLocalPrefix370=8” indicates that “8” is the local dialing prefix for country code “+370”. “MSISDNHeaderLocalPrefix44=0” indicates that “0” is the local dialing prefix for country code “+44”. “MSISDNHeaderLocalPrefix371=” indicates that there is no local dialing prefix for country code “+371”.

2007-03-06:

* MMSC/MM4: Add configuration parameter to avoid the use of the “/” character in MMS message-id and transaction-id values for MM4 connections. The “/” character is a valid character for these parameter values, however a customer has encountered an MM4 partner that could not support the “/” character for these values. To avoid the use of the “/” character in these parameter values, it is necessary to edit VASPOUT/accountname/VASP.INI (where “accountname” is the name of the “MMSC Routing” entry defined in NowSMS), and under the [VASP] header, add MessageIDPatch=Yes.

* SMS Gateway: Extension for sender based routing. When NowSMS routes an SMS message, it first looks to see if a sender address has been specified for the message submission (via HTTP this would be specified with the optional “&Sender=” parameter). If a sender address was specified, NowSMS checks to see if the sender address matches the “Default Sender Address” that is configured for any of the SMSC links (or “the “Phone Number” associated with GSM modem links). If NowSMS finds a match, then it will route the message only via an SMSC connection with a matching sender address. This update adds support for multiple sender addresses to be associated with a single SMSC connection for sender-based routing. To configure this, multiple sender addresses can be specified in the “Default Sender Address” field, separated by a comma (example: 1111,1112,1113). NowSMS will still use the first entry as the “Default Sender Address” for messages that are sent via the connection that do not have a sender address. However, other listed sender addresses can be used to facilitate sender based routing.

If “Allow Sender Address Override” is not checked, and multiple phone numbers are specified in the “Default Sender Address” field, NowSMS will check the sender address to see if it matches one of the values listed in the “Default Sender Address” field. If it does not, the sender address will automatically be switched to the first sender address in the list.

2007-02-27:

* SMS Gateway: Performance optimisations for handling of large bulk submissions via the web interface, affecting when a message is submitted to more than 10,000 recipients. (To disable, add EnableBulkQ=No under the [SMSGW] section of SMSGW.INI.)

* SMPP: When a message is received with optional TLV parameters for port addressing or segmentation, NowSMS would not properly understand the data_coding=3 parameter for indicating that the text was encoded using ISO-8859-1. Instead, NowSMS would assume GSM text encoding.

* SMS Gateway: See http://www.nowsms.com/discus/messages/1/20068.html (fix relating to user account specific HTML templates).

2007-02-21: (Note: Only MMSC.EXE and MMSCDLL.DLL are updated in this patch. Other modules still report 2007-02-14.)

* MM4: Fixes for delivery report and read report routing over MM4 connections.

* MM4: Fix for MM4 acknowledgments not being routed with appropriate authentication credentials when SMTP authentication is configured for an MM4 connection.

* MM4: Add support for non-delivery notifications when X-Mms-Ack-Request: Yes is enabled (AckRequest=Yes in VASPOUT\vaspname\VASP.INI), and the message is rejected.

2007-02-14:

* GSM Modem handling updates to improve “Direct to Modem” message receiving performance. Two different “Direct to Modem” options are now available in the configuration. The standard “Direct to Modem” option configures the modem to route received SMS messages directly over the modem interface without storing them on the modem, where the modem automatically generates receive acknowledgments. The “Direct to Modem – Phase 2+” works just like “Direct to Modem” except that NowSMS generates the receive acknowledgments back to the network to prevent message loss. “Direct to Modem” uses “AT+CSMS=0” and “Direct to Modem – Phase 2+” uses “AT+CSMS=1” (if available, otherwise it falls back to Phase 2/AT+CSMS=0). Some modems that support Phase 2+ can get confused when sending and receiving messages simultaneously, preventing NowSMS from properly generating receive acknowledgments. If you experience problems receiving duplicate copies of messages, or other strangeness, do not use the Phase 2+ setting.

2007-02-13:

* SMPP Delivery Receipts: Fix several problems where upstream delivery receipt ids could not be properly translated back to the NowSMS ID (especially non-delivery notifications that occur after 72 hours).

* SMPP Performance Optimisations for higher speed connections (especially 200+ mps).

* Performance optimisations for web interface when submitting a message to a large number of recipients (especially if multipart text, or Unicode text).

* Performance note: When processing large volumes of multipart SMS messages, we recommend disabling automatic short filename (8.3) support in Windows. The naming convention that NowSMS uses for multipart SMS message parts can trigger slow performance in the NTFS file system unless this support is disabled. To disable automatic short filename support in Windows, open a command prompt window and type “fsutil behavior set disable8dot3 1”, and then reboot the system for this setting to take effect. To see the current value of this setting, type “fsutil behavior query disable8dot3” in a command prompt window (1 indicates that this feature is disabled). Note that disabling this support could cause problems for either very old applications, or any software applications that expect all files to have a short filename. We recommend setting this option only if NowSMS is the primary application running on a computer. This setting can offer very significant performance benefits if processing large volumes of multipart messages, especially at speeds of 50mps or higher.

2007-02-02:

* SMS/GSM Modem Delivery Receipts: If a status report indicates a “temporary error” condition, do not generate any delivery report. http://www.nowsms.com/discus/messages/1/19887.html

2007-01-30:

* Windows Vista compatibility updates. Updates to allow NowSMS to be run without administrative rights, and to address various Vista compatibility issues.

* SMPP Async Mode: Fix for a bug where if the SMSC unexpectedly dropped the connection, NowSMS would increment the retry counter for all messages that are currently in the otubound message queue.

* SMS Gateway: When a delivery (or non-delivery) receipt is requested, and the message is rejected at the SMSC submission level, NowSMS generates a delivery failure receipt. Fix for a problem with this feature where if the submitting user was using HTTP, NowSMS may try to route the delivery failure receipt externally to an SMSC connection instead of routing via 2-way SMS.

2007-01-24:

* MMSC/Ericsson MM7: Add support for “Connection type” = “To VASP (deliver format)” for “MMSC Routing” definitions using the Ericsson MM7 format. This will cause the MMSC to use the Ericsson MultiMediaDeliver format instead of the default MultiMediaSubmit format.

* SMS Unicode Text Messages: When sending a Unicode message longer than 70 characters, NowSMS would segment messages with 63 Unicode characters per SMS message segment, instead of 67. See http://www.nowsms.com/discus/messages/1/19788.html

* SMS Gateway: Add support for configuration where NowSMS can transparently route SMS messages between 2 or more outbind SMPP connections. Configuration allows for SMS messages received via one outbind SMPP connection to be routed out via another outbind SMPP connection. (Outbind SMPP connections are SMPP connections where NowSMS initiates the connection, i.e., SMPP connections defined in the “SMSC” list.) Configuration of this type of setup requires manual editing of the SMSGw.INI file. For an SMPP connection that is receiving SMPP messages, under the [SMPP – host:port] header, add ReRouteReceived=xxxxx, where RouteName=xxxxx is defined under the [SMPP – host:port] header for the SMPP connection through which the received messages should be routed. (Note: To route received messages via any outbound route, specify ReRouteReceived=any.) (Feature previously added 2006-06-23, but was not working as intended until this release.)

2007-01-11:

* DRMCOMP: Fix for -limitEndDate command line parameter not working properly.

* Windows Vista compatibility without requring the executable to be flagged as requiring Administrative Rights.

* SMS Gateway: Fix for a bug where when sending a long text message that includes user data header (such as destination port), NowSMS would not properly encode the text. See http://www.nowsms.com/discus/messages/1/19585.html.

2006-12-11:

* MMSC/MM4/SMTP: By default, when receiving MMS messages via SMTP or MM4, the MMSC will only accept content types that are listed in the MMSCTYPE.INI file. Objects of other content types will be skipped. A new MMSC.INI parameter setting will disable the content type check to allow all content types to be transparently accepted: [MMSC] SMTPAllowAllContentTypes=Yes

2006-12-05:

* MMSC/MM4: When receiving messages via MM4, the MM4 receiver would not properly encode “Content-ID” headers for individual components of an MMS message. This could cause messages to be received where pictures were present in the message, but would not be displayed by the handset because the pictures were not referenced by the SMIL file.

* MM7: Use lower case “true” and “false” instead of “True” and “False” for Boolean values in MM7 XML (such as “ReadReply” and “DeliveryReport” values). The datatypes.dtd for XML defines boolean values as all lower case, but Release 5 editions of the 3GPP MMS specification (TS 23.140) includes examples with the first letter capitalised.

2006-11-16:

* MMSC/MM7 Receiver: Updated to support HTTP 1.1 and keep alive connections. To disable support for keep alive connections, edit MMSC.INI, and under the [MMSC] header, add EnableKeepAlive=No. (Note: Disabling keep alive sockets for the MM7 receiver will also disable keep alive sockets for the MM1 receiver that processes MMS client connections.)

* Accounting Callbacks: Enable keep-alive socket support for accounting callbacks. NowSMS will now attempt to use keep-alive sockets when processing accounting callbacks (reduces the overhead involved in processing the accounting callbacks), unless they are disabled with the SMSGW.INI setting AccountingKeepAlive=No under the [SMSGW] header. (Note: 2007-03-09 – Default setting changed to “No”. Use AccountingKeepAlive=Yes to enable keep-alive sockets for accounting callbacks.)

* MMS/MM1 over GPRS: Update for MMSWAP.DLL and “Error connecting to WAP Gateway” that was occurring at a customer site. Customer was able to move the GRPS modem to another PC and it would work properly, but could not get the modem to work properly on a specific server. For some reason, MMSWAP.DLL was unable to detect the IP addresses associated with the new GPRS connection, and could not properly route the IP traffic over the modem connection. This update does a more complete scan which resolved problems for this specific customer. (See http://www.nowsms.com/discus/messages/485/18253.html)

2006-10-30:

* 2-way SMS: 2-way SMS “Character Set” setting (ReceiveSMSCharSet) was previously used only by NowSMS for converting the received SMS message into the specified character set. This setting now is also used to specify the character set that is used if the command returns a text response directly to the 2-way command (previously any direct text response from the 2-way command was assumed to be in UTF-8).

2006-10-16:

* Receive MMS over MM1/GPRS Modem: Add a timeout value to control how often the modem switches between GPRS and SMS modes for MMS message download. After receiving an MMS notification message, by default, NowSMS will not initiate a GPRS connection to retrieve the MMS message content unless 15 seconds have passed with no more SMS messages received. To modify this timeout, edit SMSGW.INI, and under the [Modem – Driver Name] section header, add MMSModeSwitchTimeout=###, where ### is a value in seconds.

* MMSC: Add a new routing option for MMS messages, particularly received MMS messages. When defining an MM7 routing, there is a new non-standard variant defined, called “PHP Multipart File Upload”. This setting performs an HTTP File Upload of the MMS message content in a format compatible with the NowSMS Proprietary URL format, and designed to work with PHP scripting. PHP examples will be provided at a future date.

* MMSC: Add support for configurations where an MMSC is serving customers in multiple city (or area) codes within a country. Users within a particular city code can send a message to another user in the same city and country code by addressing the message to the local part of the phone number only. This is a common configuration in the United States. To enable this setting, all sender phone numbers must be in international format. This can be done by defining the MSISDNHeaderCountryCode setting (e.g., MSISDNHeaderCountryCode=1 for the US) under the [MMSC] header of MMSC.INI. Also under the [MMSC] header, add LocalNumberMaxLength=# and CityCodeLength=# to indicate the number of digits in a local phone number (e.g., 7 in the US), and city/area code (e.g., 3 in the US) components of a phone number.

2006-10-13:

* SMS Gateway – SMPP/GSM Modem Delivery Receipt Tracking: Delivery receipt tracking did not work properly for modem drivers that included a “#” in the modem driver name, for example if multiple instances of the same modem were installed on a PC. Delivery receipts would indicate “unknown” as the message id.

* MMSC/MM7: Add support for maintaining To/Cc “display only” recipients when routing to external MM7 connections (standard MM7 and Logica PAP MM7 only). To disable this feature, edit VASPOUT\accountName\VASP.INI, and add SupportCC=No under the [VASP] header. When SupportCC=No is specified, the only recipients listed in the MM7 message header will be recipients of this instance of the message. (It may be necessary to disable this feature if connecting to an MMSC that does not support “display only” recipients.)

* MMSC/MM7: The MMS standard for MM7 results in an HTTP POST that includes multiple levels of multipart content. The HTTP POST itself is mutlipart/related, with the first part being the MM7 XML document, and the second part being another multipart object (the SOAP attachment) that contains the MMS content. We have encountered at least one braindead operator MMSC that does not expect the second part of the MM7 request to be a multipart object. Instead, this MMSC expects that the HTTP POST is multipart/related, with the first part being the MM7 XML document, and subsequent parts being the various pieces of MMS content. To enable this “single level multipart” encoding for an MM7 connection, edit VASPOUT\accountName\VASP.INI, and under the [VASP] header, add SingleLevelMultipart=Yes.

* MMSC/MM4: Outbound MM4 connections will now include “X-Mms-Ack-Request:” and “X-Mms-Originator-System:” headers. By default, these headers will have the values: “X-Mms-Ack-Request: No” and “X-Mms-Originator-System: system-user@domain.name.for.mms” (where “domain.name.for.mms” is the “Domain Name for MMS E-Mail” as configured on the MMSC page of the configuration dialog). It is possible to change these values with the following settings under the [VASP] header in the VASPOUT\accountName\VASP.INI file for the MM4 connection: RequestAck=Yes and/or MMSOriginatorSystem=user@domain.com. If the user name portion of the “MMSOriginatorSystem” address is a value other than “system-user”, you must also configure the MMSC to recognise this user name as a system user account. To register a user name as a system user account, edit MMSC.INI, and under the [MMSC] header, add SystemUser1=user. (To define additional aliases for the system user account add SystemUser2=user, SystemUser3=user, etc.) The “MMSOriginatorSystem” value (or default value “system-user@domain.name.for.mms”) will also be applied as the “Sender:” address for all “MM4_delivery_report.REQ”, “MM4_read_reply_report.REQ” and “MM4_*.RES” messages.

* SMS/CIMD: By default, submit long text and EMS messages as text with UDH, instead of using binary 7-bit encoding of text. To enable the behaviour of earlier versions (binary 7-bit encoding of long text and EMS messages), add LongSMSBinary=Yes under the [CIMD – server:port] section header of SMSGW.INI.

2006-10-04:

* SMPP Server: Add configuration option for using iso-8859-1 as the default character set for SMPP clients when NowSMS is used as an SMPP server (previously NowSMS would only deliver messages to an SMPP client using the GSM character set). The NowSMS default behaviour is to use the GSM character set for text messages, and to indicate “default” for the data_coding value. To use iso-8859-1 as the character set instead, edit SMSGW.INI, and under the [SMPP] header, add SMSCCharset=iso-8859-1 … when this option is set, NowSMS will indicate “iso-8859-1” (1) for the data_coding value. It is also possible to specify SMSCCharset=IA5 … when this option is set, NowSMS will use the GSM (IA5) character set, but will indicate “IA5” (3) for the data_coding value.

* 2-way commands: @@SMSCROUTE@@ parameter was previously available only to HTTP based commands, now also available to local executable commands.

* SMPP: When “Encode text messages with 7-bit encoding” is enabled for an SMPP connection, there is some encoding ambiguity if the length of a message in characters is one less than a multiple of 8 characters (e.g., 7 characters, 15 characters, 23 characters, 31 characters, etc.). This ambiguity may cause some SMSCs to add a “@” character to the end of the message. To prevent the extra “@” character, NowSMS now adds a space character to the end of such messages when 7-bit encoding is used for an SMPP connection.

* SMPP: When “Encode text messages with 7-bit encoding” is enabled for an SMPP connection, NowSMS still assumes that text messages received from the SMSC will be encoded with 8-bit encoding, instead of the same packed 7-bit encoding that NowSMS uses to submit. This assumption is illogical, but it is the way that many SMSCs that require 7-bit encoding work. NowSMS will now attempt to auto-determine whether a received message is in 8-bit encoding or packed 7-bit encoding. However, if it is known that the SMSC uses packed 7-bit encoding when delivering messages to NowSMS, edit SMSGW.INI, and under the [SMPP – host:port] section, add GsmPackReceive=Yes (there should also be a GsmPack=Yes entry that is configured when 7-bit packed encoding is enabled for an SMPP SMSC).

* MM1 over GPRS: Increase WSP request timeout to approximately 2-1/2 minutes instead of 60 seconds. (This idle timeout is used when retrieving MMS messages from an operator MMSC. A longer timeout seems to be sometimes necessary on Cingular.)

* SMPP: Process larger SMPP requests.

2006-09-12:

* MMSC: Fix for content adaptation problem (pictures would not display on some handsets) when two NowSMS servers are connected via MM4.

2006-08-29:

* SMS Gateway: Additional controls added to keep multipart messages together when submitting to an SMSC to prevent large time delays between transmission of multiple parts of segmented message, particularly for SMPP connections with async mode enabled.

2006-08-24:

* OMA OTA: Add support for connection settings without a proxy for newer SonyEricsson and Motorola phones. For most phones, leaving the “Proxy Settings Section” of the OMA OTA web form blank will allow you to define connection settings without a proxy. However, SonyEricsson and Motorola do not support the TO-NAPID parameter for browser or MMS settings. To send connection settings without a proxy to these phones, use (blank), literal text including the parentheses, as the “WAP Proxy IP Address” value, which will enable a work-around for these phones. For Motorola phones, you must set the “WAP Proxy Port & Connection Type” to “Other” and “8080” (other values might also work) … but for SonyEricsson phones, this setting should be left at its default value.

This appears to be necessary because of a bug in these phones, as Section 4.6.11 of the OMA Provisioning Content specification states the following when describing the TO-NAPID parameter: “This parameter MUST be supported by the WAP client, if it is able to communicate without a proxy.” Unfortunately, settings generated with the “(blank)” work-around do not appear to work with Nokia (and possibly other) phones, necessitating that different settings must be sent for proxy-less settings depending on phone type.

* SMPP Server: Add configuration setting to enable delivery or non-delivery receipts by default for messages submitted by SMPP clients. Under normal circumstances, NowSMS (or an upstream SMSC) will only generate a non-delivery notification if a message delivery fails and the originally submitted message requested either a delivery or non-delivery receipt (registered_delivery flag set to 1 or 2 in SMPP environments). If DefaultNonDelReceipt=Yes is set under the [SMPP] section of SMSGW.INI, then NowSMS will enable the non-delivery notification flag (registered_delivery = 2) by default for all messages received from SMPP clients. (SMPP clients can still set registered_delivery = 1 to request a delivery or non-delivery notification. However, if this flag is set, registered_delivery = 0 will be automatically converted to registered_delivery = 2.) Please note that the [SMPP] section of SMSGW.INI is not created by default, and may need to be created within the SMSGw.INI file. (This section is distinct and different from any [SMPP – server.name:port] section which defines parameters related to an outbound SMPP connection.) If DefaultDelReceipt=Yes is set under the [SMPP] section of SMSGW.INI, then NowSMS will enable the delivery notification flag (registered_delivery = 1) by default for all messages received from SMPP clients. (SMPP clients can still set registered_delivery = 2 to request only non-delivery notification.)

* SMS User Account Provisioning via HTTP URL: Add additional parameter support for setting the “Web Menu Options” account attribute. This attribute is set via a new “WebOptions” variable. Valid values for the “WebOptions” variable include “All”, “TextOnly”, “SMSMMS”, “SMSWAPMM”, and “SMSMMSWAPMM”.

2006-08-15:

* SMPP: Fix for encoding error when sending long text messages with “Use WDP Adaptation” enabled. When this setting is enabled, NowSMS will send all long messages for this SMPP connection in a single request instead of multiple segmented messages. However, previously, NowSMS would always submit text messages using the short_message parameter, which is invalid for long messages. The optional TLV message_payload parameter is now used.

* Sending MMS from web interface: Fix for a strange problem where an installation was unable to send any MMS messages from the NowSMS web interface. Further investigation revealed that an error in communication was occurring between the SMS gateway and the MMSC … and pointed to a failure in a particular Windows API call. Logic reworked so that the SMS gateway to MMSC connection does not use this API call, and the problem was resolved for the customer in question. Problem could not be duplicated elsewhere. http://www.nowsms.com/discus/messages/485/16752.html

2006-08-11:

* MMS over MM1 (operator MMSC with GPRS modem): Fix for “HeaderUserAgent” and “HeaderProfile” MMSC.INI settings having problems if these included longer strings. This would result in the WSP Connect PDU being formed invalid when retrieving MMS messages (sending was ok), and prevent MMS messages from being received.

* MMS over MM1 (operator MMSC with GPRS modem): MMS message retrieval from an operator MMSC now allocates one thread per modem, so that messages can be simultaneously downloaded on systems with multiple modems. Previously, MMS retrieval was only allowed on one modem at a time (although sending over GPRS was multithreaded).

* MMS over MM1 (operator MMSC with GPRS modem): If an MMS message is not downloaded in a timely fashion, an operator MMSC will typically retry the notification. Previously, this could cause NowSMS to try to retrieve the same MMS message multiple times (and as many operator MMSCs only allow a single retrieval, attempts past the first would fail and cause excessive retries to be attempted). NowSMS now detects and ignores duplicate MMS notifications.

* Routing received MMS messages to a local user account for POP3 retrieval: Fix for a bug where this type of configuration would not work if the “Require AUTH” setting were checked for SMTP on the MMSC.

2006-08-01:

* SMPP Server: While SMPP clients are connected, periodically check to see if user account is still valid. If the account is no longer valid (has been deleted), terminate the SMPP connection.

2006-07-31:

* Configuration program: In routing options for SMPP, UCP/EMI, CIMD2 and HTTP connections, increase the maximum number of entries in the preferred routing list to 5000.

* Receive MMS over MM1/GPRS: Fix for a problem downloading MMS from some operator MMSCs (noticed on Telstra 3G network) caused by improper parsing of WSP option TPI headers. (Updated MMSWAP.DLL)

2006-07-28:

* MMSC: For E-mail to MMS and e-mail to SMS configurations, provide a mechanism for outbound messages to be routed via a particular SMSC or MMSC connection. When defining e-mail addresses that are allowed to send SMS or MMS messages in the “Authorised E-Mail to SMS/MMS Senders” list, it is now possible to follow an e-mail address in the list with a phone number to be used as the sender address for any messages submitted by this sender (example: *@nowsms.com,+447777777777 means that any addresses submitted by a nowsms.com e-mail address will be sent out with an SMS sender address of +447777777777). http://www.nowsms.com/discus/messages/1/14481.html (Partial implementation in 2006-04-26 release, however that release only addressed the SMS routing.)

2006-07-27:

* CIMD2: Fix for sequence number problems which prevented messages from being delivered properly when multiple CIMD2 server connections are active.

* Web Administration: Fix for “Create” user function for “MMSC Users” not working.

* Message Waiting/Voice Mail Notifications: Fix for problems on some GSM modems, where voice mail notifications would not be sent unless a text message was included with the notification.

2006-07-25:

* SMPP: Add configuration setting to enable non-delivery receipts by default. Under normal circumstances, NowSMS (or an upstream SMSC) will only generate a non-delivery notification if a message delivery fails and the originally submitted message requested either a delivery or non-delivery receipt (registered_delivery flag set to 1 or 2 in SMPP environments). If DefaultNonDelReceipt=Yes is set under the [SMPP] section of SMSGW.INI, then NowSMS will enable the non-delivery notification flag (registered_delivery = 2) by default for all messages received from SMPP clients. (SMPP clients can still set registered_delivery = 1 to request a delivery or non-delivery notification. However, if this flag is set, registered_delivery = 0 will be automatically converted to registered_delivery = 2.) Please note that the [SMPP] section of SMSGW.INI is not created by default, and may need to be created within the SMSGw.INI file. (This section is distinct and different from any [SMPP – server.name:port] section which defines parameters related to an outbound SMPP connection.)

2006-07-13:

* MM7 receiver did not properly handle UTF-8 subjects.

* OMA OTA: Add support for Proxy IP value to be either a host name or an IP address. A host name is usually only valid when the connection settings are for a WAP2/HTTP proxy. This type of proxy setting may not be supported by all devices that support WAP2/HTTP proxies.

* OMA OTA: Add support for connection settings without a proxy for newer SonyEricsson phones. For most phones, leaving the “Proxy Settings Section” of the OMA OTA web form blank will allow you to define connection settings without a proxy. However, SonyEricsson does not support the TO-NAPID parameter for browser or MMS settings. To send connection settings without a proxy to a SonyEricsson phone, use (blank), literal text including the parentheses, as the “WAP Proxy IP Address” value, which will enable a work-around for these phones. This appears to be necessary because of a bug in these phones, as Section 4.6.11 of the OMA Provisioning Content specification states the following when describing the TO-NAPID parameter: “This parameter MUST be supported by the WAP client, if it is able to communicate without a proxy.” Unfortunately, settings generated with the “(blank)” work-around do not appear to work with Nokia (and possibly other) phones, necessitating that different settings must be sent for proxy-less settings depending on phone type.

2006-07-06:

* Modem initialisation changes to support newer Multitech CDMA modems.

2006-06-27:

* UCP/EMI: Experimental – Add SMSGW.INI, [SMSGW], TrackUCPReceipts=Yes setting. When this parameter is present, delivery receipts will be supported over UCP/EMI connections. NowSMS will convert these delivery receipts into SMPP format. Experimental setting. Please enable SMSDEBUG.LOG for troubleshooting. (Enabling SMSDEBUG.LOG will also enable UCPDEBUG.LOG)

2006-06-26:

* OTA Provisioning – Some Nokia Series 40 phones did not like NowSMS using the e-mail address as the “PROVIDER-ID” value when sending e-mail configuration settings. The value of the settings name input is now used for this value.

2006-06-23:

* MM7 Delivery Reports: Previous versions included a “Timestamp” element in MM7 delivery reports. The “Timestamp” header is defined only in MM7 Release 5 – 1.4 and Release 6 – 1.1. All other versions of MM7 include a “Date” element instead of the “Timestamp” header. NowSMS now includes the appropriate element depending on the schema version configured.

* SMPP Server: When receiving SMS messages via a GSM modem, if the received SMS message contained message class information, this could result in a message being routed to an SMPP client with an invalid “data_coding” value. Appropriate DCS to data_coding conversions are now applied for configurations where messages received via a GSM modem are being routed to an SMPP client.

* MM7/EAIF: Add support for configurable HTTP timeout support for external MM7 and EAIF connections to an MMSC. This is the length of time that NowSMS will wait for a response from the MMSC. The default timeout is 120 seconds of inactivity. To increase this timeout, edit the VASP.INI file in the VASPOUT\accountname subdirectory, adding HttpTimeout=#### under the [VASP] header, where #### is the number of seconds to wait for a response before timing out the request.

* HTTP SMSC: Add SMSGW.INI setting, under [HTTP – host:port] section header, LongTextAsText=Yes will cause NowSMS to submit long text and EMS messages to the HTTP SMSC with the text of the message in standard text format with UDH, instead of converting the text to GSM 7-bit text encoding.

* MMSC: Fix for conversion of phone numbers to international format when “MSISDNHeaderLocalPrefix” is a value other than “0”.

* MMSC: Fix for problem with “X-MSISDN” header parsing error when the number appears in complete international format, including a “+” in front of the phone number.

* Inbound SMS: When routing a received SMS to a local “SMS Users” account, also record this in the SMSOUT log file with the SMSC name listed as the submitting user.

* MMSC Accounting Callbacks: Add additional callbacks to indicate when a message has been routed to an external MMSC connection. The “Type=MMSOut” transaction is triggered when a message has been successfully submitted to an external MMSC connection. The “Type=MMSOutFailed” transaction is triggered when a message cannot be transmitted to an external MMSC connection. To prevent problems with scripts that do not expect this callback, this callback is not enabled by default. To enable this callback, edit MMSC.INI, and under the [MMSC] header, add MMSAccountingEnableMMSOut=Yes.

2006-06-01:

* OMA OTA: Implement string table support so that repeated strings in an OTA message only need to be included in their entirety once. This results in shorter OMA OTA messages (fewer segments). To disable this behaviour, edit SMSGW.INI, and under the [SMSGW] header, add OTAUseWBXMLStringTable=No.

* OMA OTA: Implement draft specification of OMA Provisioning Content v1.2. By default, v1.2 encoding is only used if the <wap-provisioningdoc> element includes a version=”1.2″ parameter (e.g., <wap-provisioningdoc version=”1.2″>). The only difference between v1.1 and v1.2 is the addition of some new binary token definitions, so you can generally just change this version number parameter to use the v1.2 encoding which seems to be required by newer Nokia phones for some WLAN and VOIP related settings. If for some reason you want to use v1.2 binary encoding, but still specify v1.1 in the header, edit SMSGW.INI, and under the [SMSGW] header, add UseOMAProvCont12=Yes.

* 2-way SMS: Fix for 2-way SMS URLs that use https:// not working unless port 443 is appended to the host name (e.g., https://server:443/path).

2006-05-16:

* PAP/PPG: Push to an IP address was limited to 2000 bytes. Limit increased to 64000 bytes.

2006-05-10:

* HTTP SMSC: Improve performance by supporting multiple concurrent outbound connections to a single upstream HTTP SMSC. (Updated SMSGW.EXE, SMSGWS.EXE)

* HTTP SMSC: Add support for @@SubmitUser@@ and @@SubmitPassword@@ replacement parameters. These parameters can contain the original user id/password of the account that submitted the message to NowSMS. (Updated SMSGWS.EXE)

* HTTP SMSC: Add support for @@MessageID@@ replacement parameters. This parameter contains the message id assigned to the message by NowSMS (Updated SMSGWS.EXE)

* HTTP SMSC: Receipt tracking updates for HTTP SMSC connections. Additional details in discussion board thread: http://www.nowsms.com/discus/messages/1/15186.html (Updated SMSGWS.EXE)

2006-04-26:

* MMSC: Improve MM7/MM4/EAIF performance by supporting multiple concurrent outbound connections to a single upstream MMSC. (Updated MMSC.EXE, MMSCDLL.DLL)

* MMSC: Fix for problem where MMSRoutingURL callback rejects a message recipient received over MM4. If the sending system requested MM4 acknowledgments, error acknowledgments will be posted in an infinite loop. See http://www.nowsms.com/discus/messages/485/14797.html (Updated MMSC.EXE)

* MMSC: Add support for optional MMS 1.2 PDU: m-forward-req (forward message without downloading). (Updated MMSC.EXE)

* UCP/EMI: If a text message is submitted in binary 7-bit format, convert it back to text for submission via UCP/EMI. (Updated SMSUCP.DLL)

* EMS Ringtone: Add option for sending ringtone in Nokia Smart Messaging SCKL text format. (Updated SMSGWS.EXE and Send EMS Ringtone.htm)

2006-04-18:

* Alerts: Message queue size alert feature was not working. (Updated SMSGWS.EXE)

2006-04-03:

* Send EMS Text option did not handle Unicode text properly. (Updated SMSGWS.EXE)

* MMSC: Outbound MM7, change order of elements so that Priority is after DeliveryReport and ReadReply. (Updated MMSC.EXE)

2006-03-28:

* GSM Modem PINs: When adding/editing/testing a modem, report any PIN related errors. Make sure that when adding/testing a modem that a possibly invalid PIN is only sent once (previous versions may send the PIN multiple times while trying to “wake up” the modem). (Updated SMSGW.EXE & SMSGWS.EXE)

* MMSC: Fix for MMSRoutingURL callback conflicting with any “default route” settings. If the callback returned “Direct”, the MMSC would still apply the “default route”. (Updated MMSC.EXE)

2006-03-27:

* 2-way SMS would not reassemble long SMS messages where the SMS sender used an alphanumeric sender address that included a “-” character. This caused problems receiving MMS messages from an operator MMSC if the operator MMSC used an alphanumeric sender address that included a “-” character. (Updated SMSGWS.EXE)

* SMPP delivery receipts for messages routed via a GSM modem did not have the esm_class parameter set to indicate that the message was a receipt. (Updated SMSGWS.EXE)

* Change TransactionID header in MM7 submissions and delivery responses. Instead of <mm7:TransactionID xmlns:mm7=”…”>, we now omit the “mm7″ namespace prefix <TransactionID xmlns=”…”> for compatibility with the Comverse MMSC. (Updated MMSC.EXE)

* Auto-generated SMIL for MMS messages sent via the web interface did not specify a character set for the SMIL. This causes problems for Orange UK’s MM7 connector. (Updated SMSGWS.EXE)

2006-03-09:

* Fix for NowSMS Proprietary URL submission for MMS and Multimedia WAP Push truncating message subject and message text if the “?” or “&” character is present. (Updated SMSGWS.EXE)

* Fix for MM7 handler not properly converting or using well-known XML entities (especially &gt; and &lt;). (Updated MMSC.EXE)

2006-03-08:

* Fix for a brand new “fresh” installation of NowSMS only transmitting 1 message every 30 seconds. (Updated SMSGWS.EXE)

2006-03-07:

* “Help” button was not properly enabled for displaying the NowSMS 2006 PDF. If a previous version of NowSMS was installed, the Help button would display the help file from that version. If there was no previous version of NowSMS installed, the Help button would not be enabled. (Updated SMSGW.EXE)

* Fix error messages related to “EMS Send Picture Message”. In some cases, a generic “Picture Conversion Failed” error was returned, when it should have indicated “Picture is too large for selected output format”. Larger pictures can be sent by setting MaxRingToneFragmentCount=## under the [SMSGW] header of SMSGW.INI. The default value of this setting is 6. This setting applies to both the “EMS Send Ring Tone” and “EMS Send Picture Message” functionality. An image or ring tone that would require more than this number of SMS messages to be sent is rejected with an error. Internal changes have been made in this version to better support larger values for this setting. Increasing the value of this setting is only recommended for specialised environments and testing labs. (Updated SMSGWS.EXE)

2006-03-06:

* “Retry MMS Delivery Notifications” options were cut-off on the “MMSC” configuration dialog when running on Japanese versions of Windows. Dialog window was too small for Japanese fonts. (Updated SMSGW.EXE)

* If NowSMS configuration program is already active, don’t load a second copy if it is run again. (Updated SMSGW.EXE)

* Modify “Send EMS Text” handling to generate UDH that is compatible with EMS Release 4. (No longer use the text formatting length = 0 to keep changing the “default” font at the current offset. Also further optimisations to reduce the amount of UDH generated for attribute changes.) (Updated SMSGWS.EXE)

* Add “Text” parameter to “Send Voice Mail Notification” option to allow a text message to be included with an update to any of the supported message waiting indicators (MWI). When a text parameter is present, NowSMS will use a DCS value for “Message Waiting Indication Group: Store Message” instead of “Message Waiting Indication Group: Discard Message”. (Updated SMSGWS.EXE and Send Voice Mail Notification.htm)

* Routing MMS messages to a particular outbound “MMSC Routing” definition does not work properly for messages submitted through the NowSMS Proprietary URL submission method or through some VASP submissions. (Updated MMSC.EXE)

2006-03-03:

* “Send EMS Picture Message” did not work with “Text input (hex string format)”. (Updated SMSGWS.EXE)

* Bounds check on “Message Waiting Count” for “Send Voice Mail Notification”. If the value is larger than 255, it is set to 255. (Updated SMSGWS.EXE.)

* Add support for “VoiceMail=VideoOn” and “VoiceMail=VideoOff” parameters to turn on and off the video message waiting indicator. (Updated SMSGWS.EXE and Send Voice Mail Notification.htm)

2006-02-02:

* Major rewrite of previous release.  The change history is already too long …

For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...