Ozeki NG SMS Gateway V4.16.4

[Donnell Simon]

1. Improvement: Multiple keywords can be set in case of response parsing of HTTP Client service provider (e.g. error1;error2;error3).
2. Bugfix in SQL Logging: The name of the backup service provider is inserted into database from now.
3. Bugfix in Database user: The gateway checks the ozekimessageout in the given seconds.

1. Modification (Database user): Native MySQL support was removed due to licensing issues. If you want to connect your Ozeki NG SMS gateway to MySQL, please download the MyODBC driver from www.mysql.com.

Ozeki NG SMS Gateway v4.16.4

Download File → https://t.co/pMdcb1pgmm

1. New feature (CIMD2 connection, tariff class): The CIMD2 connection allows the adjustment of the tariff class parameter. To provide a custom tariff class, in an SQL to SMS configuration, simply add a new column called tariffclass to the ozekimessageout table, and adjust the SQL select template to include this column in the Database user configuration form.

1. New feature (SQL logging): The update SQL statement that is executed after a message is accepted by the SMSC for delivery, can be extended with a new keyword called $route. This keyword will hold the value, that shows which route was used to select the service provider connection. This keyword is useful to be able to tell if the message was sent through a backup route.
2. New feature (HTTP server user, SMPP user): A new checkbox was added to the configuration form. This checkbox makes it possible to decide if the user is allowed to access the web based graphical user interface of the SMS gateway.
3. Bug fix (UCP service provider connection): Alphanumeric sender ID did not support space. Now it supports it.

1. New feature (GSM modem connection, GPRS SMS support): Some GSM networks support GPRS SMS to provide better performance for SMS transfer. If your network support GPRS SMS, you can enable the "GPRS SMS Sending" feature on the "Message handling" tab of the GSM Modem configuration form.
2. Improvement (GSM modem connection): Asynchronous status reports and incoming messages are handled better. Originally if an SMS message or a delivery report came in asynchronously through the CMT or CDS method, while another SMS was being sent, the send attempt failed. Thanks to this improvement, this will not happen in this and future releases.
3. Improvement (Graphical user interface): Some unnecessary menu items were removed from the GUI of non-admin users, to simplify the user interface.
4. Improvement (SMPP service provider connection): The servicetype field can be freely defined for each submitted message. (Hint: If you want to use this option in an SQL to SMS gateway configuration, add a servicetype column to the SELECT SQL template, and specify the value of the service type field as a hex string when you insert the message into the ozekimessageout database table.)
5. Bug fix (SQL logging): Delivery reports with status codes reflecting unsuccessful delivery were not logged into the SQL logging database. This bug is fixed.

1. New feature (GSM modem, MMS sending): You can define a port number in the WAP gateway field if you use custom MMS settings
2. Improvement (SMTP service provider connection): If you define a full e-mail address for sender or receiver or both, the system will not use the templates defined in the configuration form.

1. New feature (Built in SMTP server): The built in SMTP server can be configured to forward the e-mail subject, the e-mail body or both as SMS. In the previous versions both the subject and the body was forwarded.
2. New feature (GUI): very large message queues can be viewed in the message browser
3. New feature (GUI): the server time is displazyed in the bottom of the message composer form
4. Improvement (GSM Modem connection, MM1 MMS Sending): The modem timeout period has been increase for MMS transfers, because in some networks it takes more then 30 seconds to log onto the GPRS connection.
5. Improvement (HTTP SMS API): Scheduled SMS submission became possible. A new parameter, called sendondate was introduced to make it possible to submit messages on a predefined date and time.
6. Improvement (Service monitor): A shortcut is added to the user startup folder to start the service monitor automatically when the user logs in
7. Improvement (Service monitor): If the default port number of the GUI webserver is changed from 9501, in the "Edit/Server preferences" form, the "Manage/Configure" menu item of the service monitor will notice the change and will opten the configuration form with the new port number.
8. Improvement (Database user): Some browsers change the space character to non breakable space during configuration. This has resulted in a warning message (WARNING 2010) while the SQL templates were processed. The software was updated to handle this issue. The default behavior now, is that non breakable spaces are replaced to normal spaces before the SQL command is executed.
9. Improvement (Delivery reports, CIMD2 and UCP): The delivery report matching for CIMD2 and UCP connections was improved. The delivery reports are matched to the corresponding message regardless of the + sign in front of the telephone number.
10. Improvement (GUI, message submission): Alternative message types can be submitted as a text message. If the first word in the message contains an Ozeki Message Type identifier, the message will be converted to the appropriate type. This is useful for e-mail to SMS gateway configurations.
11. Improvement (SMPP User): Chinese character set support was added
12. Bug fix (UCP service provider connection): The UCP connection did not handle message class (flash sms) settings properly for incoming messages. This bug was fixed.
13. Bug fix (E-mail to SMS, SMTP): The built in SMTP server processes e-mail messages with empty subject line properly
14. Bug fix (Delivery report handling): Entries older then one week are deleted from the message reference table
15. Bug fix (Sonofon service provider connection): Some special Danish characters were not encoded properly. This bug is fixed.

1. Improvement (Delivery report matching): For CIMD2 and UCP connections, the delivery report reference ID is converted to include only the last 7 digits of the phone number. This gives us better error rate while match delivery reports to submitted messages. If the full number would be included, matching would not work in case the returned delivery repot contins a different network prefix in the phone number.
2. Improvement (Message submission): Alternative message types can be submitted as a text message. If the first word in the message contains an Ozeki Message Type identifier, the message will be converted to the appropriate type. This is useful for e-mail to SMS gateway configurations.

1. Improvement (HTTP API): The DTD header was removed from the XML format, because it caused problems in some environments (e.g.: when HTTP clients were behind a firewall)
2. Bug fix (C# API): The C# API was not working properly, because there was a bug related to backward compatibility checking in the gateway. This bug is fixed.

1. New feature: The O2 M2M protocol was added to support the O2/Eurotel M2M service provider connection
2. New feature: SMTP (E-mail to SMS) service provider connection was added. This makes it possible to connect the software to e-mail to SMS gateways offered by GSM network providers.
3. New feature: MMS:BARCODE:EAN13 message type was added.This message is sent as an MMS.
4. Improvement (Installer): The Installer was improved to support installation on Windows 2003 R2 SP2
5. Improvement (SMPP user): SMPP v3.3 connections are accepted with independent transmitter and receiver connections. (previously SMPP v3.4 was supported only)
6. Improvement (MMS sending and receiving): MMS status reports are displayed in human readable format in the log
7. Improvement (Binary message types): Incoming binary messages are displayed in human readable format in the log
8. Bug fix (SQL logging, reporting): The reporting interface was not working if a password was specified on MySQL database connections. This bug is fixed
9. Bug fix (Addressbook): All contacts can be selected
10. Bug fix (MMS encoding): On some networks, the MMSC returned a character sequence that was not decoded properly, causing the software to go into a loop.

1. New feature (Backup routing). Backup routes can be setup in the outbound routing table. If a message cannot be sent through a route specified by the user it will be sent through the backup route.
2. Improvement (Autoreply user): Interactive login has been added to the autoreply user to make it possible to setup SMS newsgroups.
3. Improvement (Autoreply user): Group names and contact names from the addressbook can be used in the autoreply user as recipient addresses.
4. Improvement (SQL user): If a query execution fails, Ozeki NG and disconnect and reconnect to the database and will try to execute the query again. This feature was added to improve reliability on unreliable database connections (e.g.: if the database is in a different location on the Internet, the connection can seamlessly fail).
5. Improvement (HTTP Client connection): The HTTP submit timeout can be configured on the "General tab" of the HTTP client service provider connection configuration form.
6. Improvement (SMPP connection): A workaround was added to support Wataniya Telecom SMPP service. Their SMPP service does not return delivery reports in a standard way.
7. Improvement (Security): Password encryption was improved. The user interface logs out the user after the browser window is closed.
8. Bug fix (GSM modem connection): On some GSM modems if an SMS was received with empty text the message was not processed by the SMS gateway.
9. Bug fix (Web interface, Windows 2000): The graphical user interface on Windows 2000 installations was not working properly in all cases. On some systems the pictures were not displayed properly.

e2b47a7662