NowSMS v5.51 Patch Available (v5.51a)

NowSMS v5.51 Patch Available (v5.51a) SearchSearch

SMS & MMS Technical Forum » Now SMS/MMS Product Announcements » NowSMS v5.51 Patch Available (v5.51a) « Previous || Next »
Author Message
Keith Norris
Moderator
Username: Admin

Post Number: 9
Registered: 05-2003
Posted on Friday, December 31, 2004 - 04:06 pm:   

A patch has been released for the Now SMS/MMS Gateway v5.51.

The patch is available for download at http://www.nowsms.com/download/20041230.zip.

This patch addresses specific problems encountered in the v5.51 release, which are detailed below.

To install the patch, please stop the NowSMS services. Exit the NowSMS configuration program. Then unzip the files from the ZIP file into the NowSMS directory structure. (Note that some updated files go into subdirectories of NowSMS so be sure to preserve the directory structure during the unzip process.)

v5.51a (b20041230)
  • MMSC: Various fixes for improper encoding/decoding of date headers relative to GMT time.
  • MMSC: Additional setting for processing MSISDN header from a WAP proxy.
    MSISDNHeaderPrefixConvert=xxx:yyy allows you to convert all MSISDN values reported by the WAP proxy which start with "xxx" so that they start with "yyy" instead. Multiple conversion entries can be specified by including them in the header, separated by a comma (e.g., xxxx:yyyy,aa:bb).
  • MM4/MM7 Decoding: Fix MIME header parsing errors that would occur if header lines were terminated by only LF, instead of CRLF. This would cause some headers not to be processed. (Most frequent problem would be base64 attachments not properly decoded, and/or file names missing.)
  • A new option has been added which allows an "MMSC Routing" to be defined where MMS messages are converted to an SMS message that includes a link to a web page where the recipient can go to retrieve the content of the MMS message.
    For example, when sending an MMS message to a recipient that does not have an MMS compatible phone, or to an international recipient to which there is no available MMS interconnection, the recipient can instead receive an SMS message similar to the following:
    Multimedia message from +4477777777. To view, go to http://mms.domain.com:8080, and enter code number 1234.
    The recipient can then navigate to the web link using a WAP browser on a mobile phone, or a web browser on a PC. They will be prompted for their phone number and the code number that was supplied in the SMS message. After entering that information, the message content will be displayed in the browser.
    This functionality is available only in NowSMS licenses of 1 message per second or higher. (It is also enabled in the evaluation version.)
    When that setting is available, an additional configuration option will be available when defining an "MMSC Routing". This option is titled "Convert to SMS with Web Link", and it can be configured similar to other "MMSC Routing" definitions. For example, it could be configured as the default route, which would mean that this route would be used if a recipient was not in the "MMSC Users" list, and was not covered by another "MMSC Routing" definition.
  • The following configuration settings are required for this type of routing:
    "Local Server Port" specifies an available port number on the PC running NowSMS which will be used to accept connections from recipients who are attempting to connect in to retrieve MMS messages over the web interface. This port number must be different from other port numbers configured for use by NowSMS. This port must be unique, because the only functionality provided through this interface is MMS message retrieval over the web interface. Other NowSMS ports will likely have restricted access via a firewall, however this port needs to be open to the outside world to allow these types of messages to be retrieved.
    "Local Server URL" specifies the externally accessible URL that recipients will access to connect to the "Local Server Port" on the MMSC. This setting will default to the "Local Host Name or IP Address" configured for the MMSC, and the "Local Server Port". However, if you are remapping the address and port via a firewall, you should specify the external host name (and port if required) in this field. Keep in mind that some users may be restricted from retrieving content from non-standard web server ports.
    "SMS Message Text" is a template for the SMS text message that will be sent out to recipients. This text should consist only of characters that are part of the default GSM character set. And it should include the following replaceable text parameters:
    @@PhoneNumber@@ will be replaced with the phone number of the message sender.
    @@Server@@ will be replaced with the value configured for "Local Server URL".
    @@Code@@ will be replaced with a code number that the recipient must enter in order to retrieve the MMS message content.
    The default text for this message is:
    "Multimedia message from @@PhoneNumber@@. To view, go to @@Server@@ and enter code number @@Code@@."
    HTML and WML template files are used to construct the login page and message files generated by this facility.
    These template files must be located in a subdirectory of NowSMS named "MMSSMS".
    The templates for the login page are LOGIN.WML and LOGIN.HTM.
    The templates for message file creation are MSGTEMPLATE.WML and MSGTEMPLATE.HTM.
    These templates can also reference GIF or JPEG files that are located in the same "MMSSMS" directory. The default templates make use of two GIF files, CLOSE.GIF and OK.GIF, which are included in this update.
  • SyncML OTA Settings: Add web form support for the Task and Notes database. (Note that for the Task database, phones seem to expect to see "?TODO" at the end of the URI.)
  • MMSC Routing: Allow the "Route messages to this account for recipient phone number(s)" field to accept more data, up to 32,000 characters.
  • MMSC Routing: Fix for statistics counter not working.
  • Push Proxy Gateway: Support "X-Wap-Application-ID:" headers that are not well-known, encoding them in text format. (Previously only well-known text headers, or numeric values, were encoded. Other values were ignored.)
  • Push Proxy Gateway: Support routing push messages to an IP address. (Example: <address address-value="wappush=1.2.3.4/type=IPV4"/> or <address address-value="1.2.3.4"/>)
  • MMSC: MM7 Connections: Add configuration setting to remove all white space (e.g., new line characters and extra spaces) from MM7 XML submissions.
  • MMSC: MM7 Connections: Add configuration settings to set the MM7 Version and XML Schema to be used. Previously this capability was only available through editing the appropriate VASP.INI file. Compatibility with REL-5-MM7-1-0 and REL-5-MM7-1-1 improved, where those versions were more strict on characters allowed in ID fields.
  • Prevent MMSC from restarting with corrupt message in the outbound VASPQ. (Could occur with a truncated MMS submission that arrived to the MMSC via MM1 or EAIF.)
  • MMSCOMP/Sending MMS message from Web Interface: MMSCOMP now looks for the standard signature to see if a text file that is included in a message submission is in UTF-8 or Unicode format. If it is, the proper character set is automatically assigned in the resulting MMS message.
  • MMSC: HTTP/1.1 Keep-alive sockets enabled on the MMSC. This seems to prevent problems when the SonyEricsson Z1010 is connected without a proxy server. To disable keep-alive sockets, edit MMSC.INI, and under the [MMSC] header, add EnableKeepAlive=No.
  • MM4/MMS Outbound Routing: Add configuration option for "Message Format" when routing externally to an MM4/SMTP connection. The "MM4" option is used for true MM4 connections, while the "Generic E-Mail" option is used for more general SMTP links (e.g., MM3). When the "Generic E-Mail" option is selected, address formats in the message headers will always include a domain name, and MM4 specific headers will not be included in messages.
  • PAP (Push Access Protocol): Fix for content type encoding problems with some content types (such as application/vnd.wv.csp.cir).
  • Web Interface: Send Text Message form updated because it would incorrectly report that Unicode encoding was required if a message included the pound or yen currency symbols. The NowSMS server would correctly handle the message, however the character counter in the web interface would incorrectly state that the message had to be sent using Unicode encoding.
  • HTTP SMSC Problem that could occur under Japanese (and possibly also Chinese) versions of Windows where extra text from a previous message could be included in at the end of a message. See http://support.nowsms.com/discus/messages/1/7204.html
  • SMPP Client: Allow for an SMPP SMSC definition to connect as a receiver only. This will be done if the following settings are specified:: "Receive SMS Messages" = checked; "Support any outbound message traffic" = not checked; "Preferred SMSC Connection for" = blank list; "Advanced Settings/Send and Receive Messages over the same connection" = not checked.
  • WAP Push / OTA Settings: Some Samsung phones display a date/time associated with received WAP Push messages, where the date/time displayed is inaccurate. An SMSGW.INI file setting has been added to force NowSMS to insert a date/time stamp when generating a WAP Push message. To enable this behaviour, edit SMSGW.INI, and under the [SMSGW] header, add WAPPushIncludeDate=Yes. This setting has not been tested against a wide range of other phones.
  • Web user Interface: Fix for submit button and address book pop-up window not working on the "Send WAP Push" message form for "SI" messages when using the Firefox browser.
  • SMS Gateway: Support additional parameter for HTTP submissions, "&ServiceType=" can be used to specify the service type parameter to be sent when the message is routed via an SMPP server. The service type parameter is also now supported when received from SMPP client connections, and will be preserved if the message is routed externally via SMPP.
  • SMS Gateway: Improved handling of configurations where there are multiple connections to the same SMSC. It is no longer necessary to use HOSTS file entries to fool NowSMS into seeing different SMSCs. Now, NowSMS will automatically append "#x" to the IP address or host name when you add an additional connection to an SMSC.
  • MMSC: New MMSC.INI setting added. Under [MMSC] header, DisableMMSDirectDelivery=Yes will stop NowSMS from performing MMS direct delivery for accounts that are defined in the "MMSC Users" list. By default, NowSMS will always perform MMS direct delivery to accounts that are defined in the "MMSC Users" list. When NowSMS is being used for e-mail to MMS, this setting allows those recipients to be routed via an external MMSC connection.
  • MMSC: A particular phone was adding linefeed characters to the end of e-mail addresses when sending MMS messages to e-mail addresses. This would cause delivery problems for the resulting e-mail. When an MMS message is submitted by an MMS client for e-mail delivery, any non-printable characters at the end of an e-mail recipient address will be discarded.
  • MMSC: Add retry logic when processing messages in the SMTP OUT queue. If a message cannot be sent for 24 hours, it will be removed from the queue and an error sent back to the message sender.
  • MMSC: Fix for MMSC issues caching "UAProf" files when the URL includes a "=" character, such as for many Siemens phones. Each time a phone with one of these UAProf URLs connects to the MMSC to retrieve a message, an additional copy of the UAProf file is cached in the UAProf subdirectory.
  • MMSC Routing - EAIF Connections - Add "Connection Type" attribute to specify whether the connection is "To VASP" or "To MMSC". When connecting to a VASP, the following headers will be included: "x-nokia-mmsc-from:", "x-nokia-mmsc-message-id:", "x-nokia-mmsc-to:" and "x-nokia-mmsc-version:". These headers are not included when routing a message to an MMSC (the MMSC will parse the values from the actual message).
  • SMSGW.INI setting added to prevent SMS message details (text) from being included in the standard log files. Under the [SMSGW] header, include ExcludeSmsDetailsFromLog=Yes to prevent SMS message details from being included in the standard log files.
  • SMSGW: Include Sender address in log file entries (SMSOUT & USERS).
  • Push Proxy Gateway: "X-wap-Application-ID:" header was not always being included in the resulting push message when present with the push content. Added support for X-Wap-Application-ID to be specified in hex format (e.g., X-Wap-Application-ID: 0x07).
  • MMSC: Support for receiving HTTP POST when chunked encoding is used (SonyEricsson Z1010).
  • SMPP: Add support for setting the priority_flag when submitting messages. This flag will apply to all messages submitted via a specific SMSC link. Under the [SMPP - server:port] section of SMSGW.INI, add PriorityFlag=#, where "#" is the numeric value to be specified as the priority flag in the submitted message.
  • SMS Users: The "Forced Sender Address" can now contain a comma delimited list of allowed sender addresses for the specified account. If the account submits a message with a sender address that is not in this list, the first address in the list will automatically be applied as the sender.
  • SMS Users: Throttling limits can now be applied for how quickly individual accounts are allowed to submit messages into NowSMS over SMPP.
  • SMSGW: On message submission, the default submitok.htm response now reports the message id assigned to a submitted message.
  • New configuration settings are defined to limit particular outbound "SMSC" connections to use by selected "SMS Users" accounts. These settings cannot yet be configured via the user interface, but can be configured by direct edits of the SMSGW.INI file. Under the SMSC section (e.g., [Modem - modem driver name] or [SMPP - ip:port]) header, the following configuration settings can be applied:
    AllowedUserOnly=Yes -- This setting specifies that the SMSC connection can only be used by users that are specifically authorised to use this SMSC. When routing messages from users that are not specifically authorised for this connection, NowSMS will not use this SMSC and route messages as if this SMSC definition did not exist.
    AllowedUser1=username -- This setting can be repeated with sequentially assigned numbers (e.g., AllowedUser2=xxx; AllowedUser3=yyyy). This entry is used to specify specific "SMS Users" accounts that are allowed to use the SMSC connection when AllowedUserOnly=Yes.
    Note: It is NOT necessary to restart NowSMS when making updates to the AllowedUserOnly or AllowedUser1 settings in SMSGW.INI. These changes will be detected dynamically by NowSMS.

Topics Topics Search Last 30 Days Login Login / Register Logout Logout