Keith Norris
Moderator
Username: Admin
Post Number: 29
Registered: 05-2003
| | Posted on Tuesday, October 24, 2006 - 04:18 pm: | |
An update for NowSMS 2006 (v2006.10.16) has been posted at the following location:
http://www.nowsms.com/download/patch2006.zip
In addition to the other changes/enhancements mentioned elsewhere in this message thread, the following changes/enhancements have been implemented:
- 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.
- 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.
- 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.
- MMSC: Fix for content adaptation problem (pictures would not display on some handsets) when two NowSMS servers are connected via MM4.
- 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.
- 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".
- 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://support.nowsms.com/discus/messages/485/16752.html
- 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.
- 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.
- 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)
- 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://support.nowsms.com/discus/messages/1/14481.html (Partial implementation in 2006-04-26 release, however that release only addressed the SMS routing.)
- 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.
- 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.)
- 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.
- Modem initialisation changes to support newer Multitech CDMA modems.
- 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)
- 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.
|
Keith Norris
Moderator
Username: Admin
Post Number: 28
Registered: 05-2003
| | Posted on Friday, June 23, 2006 - 07:37 pm: | |
An update for NowSMS 2006 (v2006.06.23) has been posted at the following location:
http://www.nowsms.com/download/patch2006.zip
In addition to the other changes/enhancements mentioned elsewhere in this message thread, the following changes/enhancements have been implemented:
- 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.)
- 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.
- 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).
- PAP/PPG: Push to an IP address was limited to 2000 bytes. Limit increased to 64000 bytes.
- 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://support.nowsms.com/discus/messages/1/15186.html (Updated SMSGWS.EXE)
|
Keith Norris
Moderator
Username: Admin
Post Number: 27
Registered: 05-2003
| | Posted on Thursday, April 27, 2006 - 07:45 pm: | |
This thread contains information on updates to NowSMS 2006.
The current update to NowSMS 2006 can be downloaded from http://www.nowsms.com/download/patch2006.zip.
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: 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://support.nowsms.com/discus/messages/1/14481.html (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://support.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 > and <). (Updated MMSC.EXE)
- Fix for a brand new "fresh" installation of NowSMS only transmitting 1 message every 30 seconds. (Updated SMSGWS.EXE)
- "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)
- "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)
- "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)
|
Search
