| NowSMS 2008 Updates |  Search
|
|
NowSMS Support Forums ⬆ Now SMS/MMS Product Announcements ⬆ |
◄ ► |
| Author | Message | |||
| Keith Norris Moderator Username: Admin Post Number: 34 Registered: 05-2003 |
An update for NowSMS 2008 has been released. The following describes the changes in this release since 2008.02.22. 2008-06-03: * Add configuration parameters to simplify support for running NowSMS in fault tolerant redundant load-balanced environments. For more information, see http://www.nowsms.com/download/nowsms-ft.pdf 2008-05-27: * Fix for trial version not working on some Windows Vista systems, reporting immediately after installation that the trial period had expired. 2008-05-22: * MMSC: When messages are routed to the MMS-IN directory via a routing definition in an "MMSC VASP" account, include an X-NowMMS-Received-From-VASP: header to record the routing information. 2008-05-21: * SMS Gateway/SMPP: When async mode is NOT enabled, allow messages to continue to be received without delay, even when throttling conditions exist. 2008-05-15: * MMSC/MM4: Fix for MM4 acknowledgment responses being rejected if the default outbound route for the MMSC is "Block/Reject Message". Users of previous versions who experience this problem can work-around it by applying the following settings: Go to the "MMSC Routing" page. Add a new route ... for the "Account Name" specify "system-user". For "Route messages to this account for recipient phone number", specify "system-user". For "Route messages to VASP via", specify "Direct Delivery (internal MMSC)". This will allow the MM4 ack messages to be processed correctly. * SMS Gateway/SMPP: Fix timing issue for enquire link command which caused timing of the sending of the enquire link to occur as many as 10 seconds later than configured. * SMS Gateway/MMSC: Add configuration parameter to allow debug log files to be stored in a directory other than the NowSMS program directory. Edit SMSGw.INI, and under the [SMSGW] header, add DebugLogDirectory=d:\path\ (Note: Previously this setting was available only in MMSC.INI for the MMSCDEBUG.LOG. That setting is still available, but if it is not set in MMSC.INI, the MMSCDEBUG.LOG will be stored in the directory pointed to by the setting in SMSGW.INI.) * SMS Gateway/SMPP Client: Add configuration parameter to allow the "users" directory to be moved to another location other than beneath the NowSMS program directory. This directory contains queues of received messages waiting for SMPP or POP3 clients. Under the [SMSGW] header in SMSGW.INI, use UsersDir=d:\path\ or UsersDir=\Server\Volume\path\ to specify the location of the SMS "users" directory. When this parameter is set, the "SMS Users" database files (SMSUSERS.D2A and SMSUSERS.D2I) will also be located in this directory (by default, when this parameter is not set, these files are in the NowSMS program directory). * MMSC: Add configuration parameter to allow the "MMSCUsers" directory and user database to be moved to another location other than beneath the NowSMS program directory. This directory contains statistical information regarding MMSC user transactions. Under [MMSC] header in MMSC.INI, use MMSCUsersDir=d:\path\ or MMSCUsersDir=\Server\Volume\path\ to specify the location of the "MMSCUsers" directory and user database. When this parameter is set, the "MMSC Users" database file (MMSCUSERS.DB) will also be located in this directory (by default, when this parameter is not set, this file is in the NowSMS program directory). 2008-05-07: * GSM Modem handling - Various fixes to improve compatibility with recent Nokia phone GSM modem implementations, and bugs in Nokia's implementation of the AT+CMGS command that is used to send SMS messages. This fixes an issue that caused NowSMS to repeatedly send the same SMS message and report "Error waiting for response from modem (2)", until the retry counter was exceeded. 2008-05-05: * SMPP - Improved handling of throttling errors when SMPP async mode is enabled. 2008-04-21: * SMPP - Fix for a problem where recent versions have not properly passed the "Bind TON" or "Bind NPI" parameter in SMPP connection tests from the configuration dialog. 2008-04-16: * CIMD: Add preliminary support for delivery receipts in CIMD environments. To enable this support, edit SMSGW.INI, and under the [SMSGW] header, add TrackCIMDReceipts=Yes. NowSMS will convert these delivery receipts into SMPP format. Experimental setting. Please enable SMSDEBUG.LOG for troubleshooting. (Enabling SMSDEBUG.LOG will also enable CIMDDEBUG.LOG) 2008-04-10: * SMS Gateway: The SMSGW.INI SMSCSendLimit=x/y setting, which can limit the speed at which messages are sent via a specific SMSC connection, does not function well at speeds higher than 50 messages per second. The setting has been reworked to support throttling at higher speeds. * MM7/EAIF: Keep-alive connections are now enabled by default when connecting to "MMSC Routing" definitions using the MM7 or EAIF protocols. "Keep-alive" support is automatically disabled if the service provider indicates that keep-alive is not supported (e.g., HTTP/1.0 protocol or "Connection: close" header). However, if this support causes problems for a particular MMSC connection, keep-alive support can be disabled for a specific "MMSC Routing" by editing the VASPOUT\routename\VASP.INI file, and adding UseKeepAlive=No under the [VASP] header. By default, if there are no further messages to transmit over the connection, NowSMS will keep the connection open for approximately 90 seconds waiting for additional messages to transmit before closing the connection. To change this timeout, edit VASPOUT\routename\VASP.INI, and add KeepAliveTimeout=### to specify the number of seconds for which the keep-alive connection should be kept open. * MM4: When routing messages via MM4, NowSMS will now keep the SMTP connection active after transmitting a message, allowing multiple messages to be transmitted over the same connection. This "Keep-Alive" support can be disabled for a specific "MMSC Routing" by editing the VASPOUT\routename\VASP.INI file, and adding UseKeepAlive=No under the [VASP] header. By default, if there are no further messages to transmit over the connection, NowSMS will keep the connection open for approximately 90 seconds waiting for additional messages to transmit before closing the connection. To change this timeout, edit VASPOUT\routename\VASP.INI, and add KeepAliveTimeout=### to specify the number of seconds for which the SMTP connection should be kept open. * SMPP: Additional logic added to detect SMPP connections that have been abruptly terminated by the service provider, so that NowSMS does not try to send any additional data once NowSMS has received a signal that the connection has been terminated. * MMSC Routing: NowSMS now logs information about all MMS message delivery attempts for messages being routed via an "MMSC Routing" definition in the MMSC-yyyymmdd.LOG file, so that information about transmission retries and failures can be found in the logs. * MMSC Routing: Connectivity error conditions for external "MMSC Routing" definitions is now displayed along with the SMSC connectivity error conditions on the "Service" page of the NowSMS configuration dialog. Additionally, the XML Status Query includes information regarding the connectivity status of these MMSC Routes, and the number of messages transmitted in a new "MMSCRouteStatus" section of the XML document. * MMSC VASP Message Routing: The previous setting to allow received messages from a particular "MMSC VASP" account to be routed to a specific external MM7 "MMSC Routing" has been enhanced to support forced routings for all messages from a particular VASP to be routed via any specific MM7, MM4, MM1 or EAIF "MMSC Routing" definition. * SMS/SMPP Receipt Message ID Tracking: Allow database files that are used for tracking SMPP receipt message IDs to be stored in a directory other than the default SMPPDATA directory. Under the [SMSGW] header of SMSGW.INI, it is possible to specify MessageIDTrackingDir=d:\path or MessageIDTrackingDir=\server\volume\path 2008-03-23: * MMSC/MM1 over GPRS Modem: Fix for encoding problem when transmitting UTF-8 subjects over an MM1 connection. 2008-03-22: * SMS Gateway/2-way: @@SMSCROUTE@@ parameter was not properly supported for 2-way commands. This replaceable parameter should contain the inbound route from which the SMS message was received. * SMS Gateway/2-way: New configuration parameter added for [SMSGW] section of SMSGW.INI. 2WayReplySameServer=Yes specifies that replies from all 2-way commands should be routed back via the same SMSC connection as which the original message was received. 2008-03-14: * SMS Gateway/SMPP: If SMPP connection has been terminated unexpectedly by the provider, do not attempt to send an unbind request before terminating our side of the connection. (Shouldn't be necessary, but may be required for acceptance testing by some operators.) * SMS Gateway/SMPP: If SMPP connection has been terminated unexpectedly by the provider, use retry logic before attempting to re-establish the connection. (Previously, retry logic would only be applied only after an unsuccessful connection attempt, meaning that the retry attempt after an unexpectedly terminated connection was immediate.) 2008-03-05: * SMS Gateway/SMPP: When NowSMS is bound to a service provider via SMPP with separate sender and receiver connections, if the SMPP connection fails, the retry logic for re-establishing the receiver connection is different from that of the sender connection. This causes problems, primarily for testing environments connecting to a SMPP server simulator, where the simulator won't send delivery receipts if a receiver connection is not bound simultaneously with the sender connection. 2008-02-22: For additional information about changes introduced in the 2008-02-22 version, please see http://support.nowsms.com/discus/messages/53/23641.html | |||
