2024-02-05: EMG 7.2.26 is now released.
These are the changes in EMG 7.2.25 as compared to EMG 7.2.24.
- The connector option CSM, added in version 7.2.0, cannot be changed in runtime. If this was done anyway, the error message logged when reloading the configuration, was previously a bit confusing. This message is now clearer.
- If a connector had the CSM option set, and the number of instances was later increased at runtime, the new instances would ignore this option. This has now been corrected.
- The character encoding logic has been rewritten, and is now more logical.
- The global DEFAULT_CHARCODE_TEXT option is no longer used.
- In the GSM7 character set, there are a couple of capital Greek letters between 0x10 and 0x1A. When sent on a connector using UTF8, these were previously incorrectly replaced by the space character.
- Perl plugins which set the CHARCODE option can now also use names (“LATIN1” etc) just as in the configuration files, instead of having to use numbers.
- Outgoing SMTP connectors now only use Latin-1 and UTF-8.
- EBE connectors now use UTF-8 instead of UCS-2, for contents that don’t fit in neither Latin-1 nor GSM-7.
- CIMD2 connectors can now use both GSM-7 and Latin-1 and tag them correctly. They will use the values from the connector options DCS_FOR_GSM7 and DCS_FOR_LATIN1, if set.
- The connector option DEFAULT_CHARCODE, used as the default encoding for outgoing messages, is now obsolete as all messages will have a defined encoding.
- The connector option UCS2MAPPING, introduced in EMG 5, is no longer supported. If you are actually still using this option, please contact us.
- The connector option CHARCODE_CONVERT is now always set, so it can be removed from your configuration files.
- The new connector option ENABLE_UCS2_UPGRADE allows connectors to use UCS2 when sending a message that was previously received as Latin-1 or GSM-7. This is useful if the message was received as GSM-7, the outgoing connector only supports Latin-1, and the message contains characters not available in Latin-1 (for example those Greek letters mentioned earlier). Or, vice versa, of course. EMG might then use multiple pdus on the way out, but this would then be shown in the routelog.npdus columns, so the client can be billed correctly. Without this option, characters missing from the outgoing encoding are replaced by a space character, just as before.
- The connector option PARSEMESSAGE now always processes the Latin-1 version of the message body.
- The message id management has been cleaned up and made more consistent.
- The routelog.msgid column now always contains the numeric EMG message id. When using the MERGE_IN connector option, this field previously got the UUID returned to the sender, which required that the column type in the database was changed to be a string.
- The message id returned to the client, which is a UUID string when using MERGE_IN, a timestamp when using UCP, and the EMG message id otherwise, is now logged in the connector log file as option 163 (MESSAGEIDIN), and stored in the messageoption table.
- The message id returned by the downstream system is logged with option 64 (SMSCID) and stored in the routelog.smscid column.
- For a delivery report, the EMG message id of the original message is stored in the routelog.origid column, just as before.
- The profiling log will now contain entries for the time spent fetching an item from the database connection pool. Seeing high values here is typically an indication of too few instances in the DB section.
The downloads are password-protected. To obtain the username and password required, please use our license request form. If you already have an existing installation, you should download just the new binaries.