OCSS7 Changelog

Update the netty libraries to 4.1.103.Final

Corrected a defect that could cause the DPC status information displayed by the display-info-dpcinfo CLI command and dpcinfo SNMP statistics to be incorrect. (#430474)

Improved load time of MML batch files passed in to the SGC CLI by delaying the saving of config changes until a short time after config changes have ceased occurring. While this does dramatically increase the load time of very large configurations, it does mean that configuration changes may be lost (and therefore will need to be reapplied) if the SGC cluster fails during or immediately after the reconfiguration. (#728006)

All open source libraries (except Hazelcast) have been updated to the latest available release.

SNMPv3 usernames are no longer incorrectly prefixed with sC. The optional SGC property snmp.v3.unprefixed_username introduced in OCSS7 4.0.0.3 to enable an optional fix is no longer required. See the OCSS7 Installation and Administration Guide for additional steps that may be required when upgrading from a previous release. (SSSVN-1544)

Fixed an issue which would cause the SGC to throw an AssertionError and restart. (#272687)

Fixed an issue that could cause GC CMS cycles to become increasingly frequent over time under certain conditions (#230156)

The SNMP agent now logs its own name when starting up, instead of the SGC node name. (#359618)

The SNMPv3 engine ID may now optionally be specified when creating an SNMP node. (SSSVN-1547)

SNMPv3 now correctly supports USM users configured with authPriv and noAuthNoPriv in addition to the already working authNoPriv. (SSSVN-1543)

The snmp.v3.unprefixed_username SGC property has been added. Setting this property to true activates a correction for a defect that caused SNMPv3 usernames to be prefixed with the letters sC. Omit this property (i.e. do nothing) if you do not require this correction. (SSSVN-1544)

Fixed a race condition which could incorrectly leave nodeFailure alarms active despite the entire cluster being operational if the alarm was raised while the missing node was starting up. (SSSVN-1533)

If the SGC receives DAVA/DUNA/SCON that does not contain a routing context and no routes are configured for that connection with a null routing context and only one route is available that otherwise matches the received message it will apply the DAVA/DUNA/SCON action to that route. (SSSVN-1514)

If the SGC receives DAVA/DUNA/SCON that does not contain a network appearance parameter and no routes are configured for that connection with a null network appearance and only one route is available that otherwise matches the received message it will apply the DAVA/DUNA/SCON action to that route. (SSSVN-1514)

The CLI now logs all executed commands and their arguments to the CLI log. (SSSVN-1520)

The SGC now logs remove and disable management operations in addition to the already-logged enable, modify and create operations. (SSSVN-1521)

The associationPathDown alarm is now cleared on any good paths after association establishment. This prevents stale alarms lingering around from a previous boot of the SGC that terminated unexpectedly. For example, due to hard server restart. (SSSVN-1523)

Association info statistics will be correctly reset after an association goes down. (SSSVN-1522)

Association info statistics associated with a node will be correctly reset after that node leaves the cluster. (SSSVN-1522)

Association info statistics will be correctly restarted following reestablishment of an association. (SSSVN-1522)

This release is built on and requires JDK 11.

The SGC’s new generation size can now be configured via the NEW_SIZE configuration property in config/sgcenv. (OPT-1859)

The SGC’s main logs are now rotated when they reach 100MB, and a maximum of 10 files will be kept in rotation. (OPT-910)

The SGC garbage collection log gc.log is now rotated every time it reaches 100 MB and a maximum of 100 files will be kept in rotation. (VOLTE-9076)

AS precond rules will now be correctly applied to all nodes in the cluster when a local SSN becomes available via at least one cluster member or is no longer available via any cluster member. (SSSVN-1491)

AS precond rules are now correctly applied when initially created. (SSSVN-1492)

Management connection JMX TLS helper sgckeygen JMX TLS setup tool:

The SGC now supports online upgrade from SGC 3.0.0.x to selected newer SGC versions. See Upgrade from one 3.x release to another 3.x release for more details. (SSSVN-1253)

The SGC’s memory requirements are no longer linked to the number of connected TCAP peers. Consequently the sgc.tcap.maxPeers and sgc.tcap.maxMigratedPrefixes configuration properties have been removed. The javaHeapTooSmall alarm has also been removed. There is now a sgc.tcap.maxTransactions configuration property that governs the number of concurrent transactions that each SGC node may service. See the OCSS7 Installation and Administration Guide for the effect that this property has on the Java heap requirements. (SSSVN-1197)

Added new longDescription, cause, effect and action fields to the alarms raised by the SGC. The existing description field (previously exposed only by the CLI) is now also exposed via JMX and SNMP. The alarm timestamp has been moved out of the additionalInfo field into its own field. (SSSVN-1234)

Added new longDescription field to the notifications generated by the SGC. The existing description field (previously exposed only by the CLI) is now also exposed via JMX and SNMP. The notification timestamp has been moved out of the additionalInfo field into its own field. (SSSVN-1234)

When emitting SNMP traps for alarms or notifications the SGC will, by default, generate extended traps containing all fields applicable to the alarm or notification. If smaller traps are required, the SNMP node may be configured for basic traps in create-snmp-node. Smaller traps omit the longDescription field, and in the case of alarm-sourced traps, also omit the cause, effect and action fields. (SSSVN-1234)

Updated the SGC’s system object identifier to 1.3.6.1.4.1.19808.10.3.0.0 (SSSVN-1187)

The SGC CLI prompt now includes the name of the connected SGC node. (SSSVN-579)

The CLI will now inform the user if it detects that it is connected to an SGC of a different version. (SSSVN-1184)

The CLI display-local command now returns the SGC version. (SSSVN-1215)

Improved the compliance of SNMP MIBs. See OCSS7 MIB Changes for the full set of SNMP MIB changes. (SSSVN-1395)

Corrected a defect where transaction ID reuse could result in a TC-BEGIN being sent to an incorrect destination. (SSSVN-1247)

The SNMP subsystem now correctly supports SNMP over TCP as well as SNMP over UDP (see transport-type parameter in snmp-node configuration). Additionally, unsupported transportDomain values have been removed from target-address configuration. (SSSVN-1226)

The minimum time between SCCP SNMP error notifications is now configured via the ntfy-sccp-err parameter and not the ntfy-tcap-err parameter. (SSSVN-1362)

The minimum time between TCAP SNMP error notifications is now configured via the ntfy-tcap-err parameter and not the ntfy-sccp-err parameter. (SSSVN-1394)

Corrected an issue where NullPointerException could be encountered during SGC startup if outbound GTT configuration completed prior to SCCP initialization finishing. (SSSVN-468)

Corrected the encoding and decoding of ANSI TCAP error codes. (CGIN-2088)

ANSI TCAP support has been added. ANSI TCAP may be carried over either ITU SCCP or ANSI SCCP.

Updated the SGC’s system object identifier to 1.3.6.1.4.1.19808.10.2.2.0 (SSSVN-895)

The SGC will raise a javaHeapTooSmall alarm if the configured MAX_HEAP_SIZE is considered to be far too small for the maximum number of concurrent TCAP peers and migrated prefixes. (SSSVN-1025)

The SGC’s documentation has been updated to further assist selecting an appropriate value for MAX_HEAP_SIZE.

The OCSS7 TCAP stack now inteprets setting the ocss7.sgcs configuration property to an empty string in conjunction with ocss7.urlList also being an empty string to mean 'use the meshed connection manager, with no active connections'. This is intended for use with in place TCAP stack upgrades. (SSSVN-1100)

Added alarm distributedDataInconsistency which is raised when a distributed data inconsistency is detected. (SSSVN-1063)

The SGC CLI now exits with exit code '1' if it fails to connect to the SGC. (SSSVN-1049)

All CLI display-* commands now have pre-defined default column order that will be used if not overridden by the user. (SSSVN-1072)

Improved the consistency of the CLI’s help text. (SSSVN-1089)

Added documentation on how to use the included generate-report.sh script to collect data for support requests. (SSSVN-1102)

Improved the robustness of the SGC’s handling of TCAP stack connect and disconnects. (SSSVN-1068)

Corrected a spelling error in the SGC’s "SGC raised alarm" ERROR logging messages. (SSSVN-1085)

Correct a defect where a misconfigured SCTP association could hang connecting forever. (SSSVN-1093)

Adding or removing a conn-ip configuration to an active connection will now raise or clear the associationPathDown alarm as appropriate. (SSSVN-1094)

Corrected a defect that could result in a NullPointerException in DpcInfoHelper.rebuild() after routes were removed via remove-route. (SSSVN-1113)

Corrected syntax errors in CTS-SGC-MIB SNMP MIB. (SSSVN-1124)

Added OPENCLOUD-OCSS7-MIB containing system OID entries for the SGC. (SSSVN-945)

Receipt of TC-CONTINUE with a non-derivable destination transaction ID and a derivable originating transaction ID should now result in a TC-ABORT being sent to the sender. (SSSVN-1042)

A local provider abort will now be generated if a malformatted TCAP message is received with a derivable destination transaction ID. (SSSVN-1016)

SCTP association remote addresses will be resolved whenever a connect attempt is made, not at configuration loading time. This prevents an issue where name resolution failure at config load time would prevent that SCTP association ever connecting to the target, even after the name resolution failure cause has been resolved. Additionally, if a remote address cannot be resolved an associationUnresolvable alarm will also be raised. (SSSVN-932)

Improved the clarity of some SCCP DEBUG messages generated when M3UA returns messages as undeliverable. (SSSVN-957)

Fixed a defect that could result in a (harmless) NullPointerException being logged by the SGC if a malicious TCAP peer were to send a message containing no SCCP user data. (SSSVN-992)

The dpcUnavailable alarm should no longer linger after startup if daud-on-asp-ac is set to false. (SSSVN-1005)

The SGC’s configSaveFailed alarm will now re-raise itself if it was manually cleared and a subsequent save fails. (SSSVN-1015)

Improved a log message that could be emitted during failure to save configuration. (SSSVN-1020)

Fixed a cosmetic ConcurrentAccessException in the AlarmingFactory implementation. (SSSVN-1022)

Corrected a defect where a stack disconnect could hang for an indefinite period of time when the SGC was under heavy load. (SSSVN-1026)

Corrected a defect where reuse of ActivityHandles could result in leaked dialogs. (SSSVN-1038)

Passing an invalid column name to the CLI’s display-* commands will now return a useful error message instead of throwing an ArrayOutOfBoundsException. (SSSVN-1078)

If the configured stack-http-address and stack-http-port combination cannot be bound for the legacy URLList Connection Manager the alarm nodeManagerBindFailure will be raised and the SGC will continue trying to bind it periodically until it succeeds. (SSSVN-1092)

A dpcUnavailable alarm is now raised whenever that DPC cannot be reached through the configured association. This includes where the association has failed, or where the AS on the association is not in the active state. (SSSVN-1097)

Corrected a defect that could result in a ConcurrentModificationException being thrown if DEBUG logging was enabled in the M3UA TrafficManager. (SSSVN-1141)

The SGC now applies the sgc.tcap.maxPeers property to all TCAP peer connections rather than just those in the ACTIVE state. (SSSVN-1153)

ANSI TCAP support has been added.

Corrected a case where receiving a malformed TCAP component could result in an Abort being sent instead of a Reject. (SSSVN-1036)

Fixed a cosmetic NullPointerException that could occur when the OCSS7 TCAP stack was stopping. (SSSVN-1002)

The OCSS7 TCAP stack now honours the value of the national indicator bit when the address type is C7/ITU. (SSSVN-910)

The OCSS7 TCAP stack now correctly reports provider abort cause incorrectTransactionPortion when it encounters an unknown (but correctly formed) tag in a message. (SSSVN-1037)

The OCSS7 TCAP stack should now correctly generate a Reject component with no InvokeID in response to receipt of a malformed component with no derivable Invoke ID. (SSSVN-1031)

ANSI SCCP support has been introduced. ITU TCAP protocols can be carried over ANSI SCCP + M3UA networks.

System OID has been updated to 1.3.6.1.4.1.19808.10.2.1.0 (SSSVN-894)

A configSaveFailed alarm will now be raised if the SGC could not save its configuration file. Additionally, improved the resilience of the SGC configuration saving process. (SSSVN-918)

Added an mtpCongestion alarm, which is raised whenever an M3UA/MTP congestion notification is received by M3UA. (SSSVN-941)

The SGC now sets SSN=0 in any outbound SCCP messages that are routeOnGT without a user-specified SSN in accordance with ITU-T and ANSI SCCP specifications. (SSSVN-947)

The SGC will now accept malformed M3UA messages that are missing their final parameter padding octets. (SSSVN-787)

Fixed SNMP’s misreporting of the following stats, which could appear with a higher value than the actual count when read. This affected the SNMP interface only, CLI display of these stats was always correct. The fixed stats are, for SCCP: segmentationFailureCount, unitdataIndCount, reassembledUnitdataCount, reassemblyFailureCount; and for Health: forceAllocatedReqTasks. (SSSVN-789)

Improved the log message emitted when the SGC receives an M3UA message of an invalid size. (SSSVN-788)

The CLI will now attempt to find an appropriate Java binary to execute even if JAVA_HOME is not set. It will check JAVA_HOME first, then SGC_HOME/config/sgcenv, and finally look for a java executable in PATH. (SSSVN-429)

Improved generate-report.sh script. (SSSVN-432)

Corrected an issue where failure to deliver a reassembled N-UNITDATA indication could ignore the value of returnOnError set in the first segment received. This resulted in no notification of delivery failure being sent to the sender. (SSSVN-901)

Corrected a defect in the handling of the M3UA affected point code list that could result in valid point codes not matching entries beyond the first. (SSSVN-884)

Corrected a defect in the ITU-T SCCP Status Test procedure that could result in the procedure being incorrectly discontinued. (SSSVN-953)

Corrected a defect in the ITU-T SCCP Status Test procedure that would result in the procedure running even if the remote DPC was already marked prohibited. (SSSVN-956)

Multiple outbound GTT rules with a replace-gt specifying route-on=SSN and an SSN no longer trigger excessive SSTs when multiple rules resolve to the same DPC and SSN. (SSSVN-931)

The SGC now honours the value of the national indicator bit when the address type is C7/ITU. Note that for C7/ITU addresses CGIN 1.5.4 with OCSS7 does not honour the national indicator for C7/ITU addresses, and will never send a 'true' value to the SGC/network and will never report a 'false' value to the SLEE for C7/ITU addresses. CGIN versions with OCSS7 ANSI support will always honour the national indicator. (SSSVN-910, SSSVN-1056)

Corrected a NullPointerException when clearing path failure alarms during M3UA shutdown. (SSSVN-890)

Corrected an issue that could result in an AccessControlException if finest logging was enabled in the OCSS7 TCAP stack. (SSSVN-889)

replace-gt rules now use the correct ranges for validating encoding scheme, nature of address, numbering plan and global title indicator parameters. (SSSVN-937)

Fixed an issue that could cause the SGC to restart if more than 1 million transactions were being concurrently handled by a single TCAP stack connection. (SSSVN-868)

Corrected a defect where receipt of a malformed SCCP message from a TCAP stack could cause the SGC to restart. (SSSVN-991)

ANSI SCCP support has been introduced. ITU TCAP protocols can be carried over ANSI SCCP + M3UA networks.

Fixed an issue where decoding of a TCMessage encoded with indefinite length could fail if the component portion was absent. (SSSVN-921)

Fixed a double-free in the TCAP stack which caused transactions to be reallocated whilst still alive, resulting in permanent entries in CGIN’s internal dialog maps. (SSSVN-1035)

Fixed defect where TCAP stack could hang if stopped while dialogs were still active. (SSSVN-779)

Fixed a deadlock that could occur during TCAP stack deactivation. (SSSVN-780)

Fixed a defect that prevented sending TC-ABORT in response in incoming TC-BEGINs while the TCAP stack was deactivating. (SSSVN-781)

Upgraded Hazelcast to version 3.7. (SSSVN-350)

The SGC is now able to detect when distributed Hazelcast data has been irrevocably lost and will restart the node in order to load configuration from file. (SSSVN-357)

Added more statistics: TcapStats, SccpStats, TcapErrorStats, SccpErrorStats. These are accessible via the command line client, JMX and SNMP. Some statistics previously in LocalSsnInfo are now recorded in SccpStats instead. (SSSVN-668)

The SGC will now detect and apply log4j.xml changes in real-time. (SSSVN-163)

Added a status field to display-info-tcapconninfo to display connection state. (SSSVN-426)

An alarm will be raised if the SGC detects that its default map backup-count configuration is considered too small for the size of cluster. (SSSVN-683)

SGC version information is now logged in the startup log and also on rollover in the main ss7.log. (SSSVN-737)

The SGC’s SNMP system OID is now 1.3.6.1.4.1.19808.10.2. (SSSVN-445)

Heartbeat is now enabled by default on all TCAP stack to SGC connections. (SSSVN-486)

The SGC now raises an alarm at MINOR if one or more paths in an association go down. The existing alarm for the whole association going down is now raised at MAJOR instead of MINOR. (SSSVN-715)

Memory requirements to support prefix migration have been drastically reduced in both the SGC and the TCAP stack. (SSSVN-732, SSSVN-733)

Local SSN prohibited alarm is now raised at MAJOR level. (SSSVN-738)

Demoted "Route routeId=x is DOWN - sending message back to SCCP" message from WARN to DEBUG. (SSSVN-143)

Fixed statistics problem where messages could be incorrectly recorded against SSN 0. (SSSVN-144)

Fixed issue that could generate a spurious "peer FSM exists in state: CLOSED will be replaced" message. (SSSVN-166)

Fixed NullPointerExceptions that could be generated if a SNMP node was configured with an invalid host name. (SSSVN-173)

Fix NullPointerException seen after disabling a local endpoint. (SSSVN-219)

Tab completion for 'display-info-ogtinfo' no longer suggests a non- existent 'ssn' column. (SSSVN-221)

Improved the error message displayed when the CLI batch mode cannot parse the provided batch file. (SSSVN-224)

TCAP stack connection loss no longer logs stack traces at WARN. (SSSVN-225)

Fixed an IllegalArgumentException seen when SNMP alarm IDs wrapped around. (SSSVN-356)

Fixed an AssertionError in Transport$ClientInitializer.initChannel() that occurred when an SGC was unable to connect to other cluster members via the comm switch interface. (SSSVN-362)

Fixed defect in decoder for SCCP importance field that could result in the wrong value being decoded. (SSSVN-385)

The CLI will no longer generate a "java.util.ArrayList cannot be cast to javax.management.Attribute" message when an unknown argument is passed to a display-info-xxx command. (SSSVN-394)

The SGC’s default minimum heap size is now equal to its default maximum heap size. The default minimum perm gen size is now the same as the default max perm gen size. (SSSVN-404)

STANDALONE hazelcast group name generation is now less prone to collisions when starting multiple standalone SGCs simultaneously. (SSSVN-425)

The SGC node manager now binds its listen socket with SO_REUSEADDR. (SSSVN-434)

The SGC no longer generates a NullPointerException if asked to send to a null destination SCCP address. (SSSVN-448)

The SGC will now attempt to restart if it exits with code 78. There is now a 30s wait between restart attempts. (SSSVN-514)

The CLI batch mode should now be significantly faster. (SSSVN-628)

Fixed an AssertionError in TcapRouter.globalRouteSelector that could occur if the SCCP reassembly timer raced with an incoming XUDT message. (SSSVN-660)

The Comm Switch will no longer be left in a zombie state if it fails to connect to other cluster members on startup. (SSSVN-681)

Fixed a NullPointerException in nodeLeft that could be generated when a cluster member left the cluster while another node was starting up. (SSSVN-682)

Fixed a defect where the TCAP stack would stop allocating new dialog ID following prefix wraparound. (SSSVN-691)

Fixed a prefix leak in the SGC that could result in the SGCs returning "out of prefixes" when a TCAP stack connected. (SSSVN-701)

Corrected an issue where a TCAP to SGC connection could end up not being used for any messages at all. (SSSVN-703)

Fixed a hard to trigger meshed connection manager deadlock. (SSSVN-704)

Under certain prefix migration conditions data structures associated with migrations would not be freed, resulting in an OutOfMemoryError. This has been corrected. (SSSVN-705)

Fixed TCAP stack leak that could occur if invoke timeouts expired while there were no connections available to any SGC. (SSSVN-712)

Corrected an issue where the TCAP stack could get its internal state confused during prefix migration. (SSSVN-713)

Corrected tab completion for display-info-tcapconninfo migratedPrefixes and tcapStackID columns. (SSSVN-734)

Installed a sensible default column display order for display-info- tcapconninfo. (SSSVN-735)

Added ability to connect to multiple SGCs simultaneously in a mesh style using new ocss7.sgcs TCAP stack property. (SSSVN-388)

SGCs now support failover of dialogs between connections to the same TCAP stack when using the new ocss7.sgcs TCAP stack property. (SSSVN-258)

sgc-cli.sh script now attempts to auto-detect SGC JMX host and port if those parameters are not set on the command line (-h -p) (SSSVN-292)

DAUD should no longer be slow to happen when many ASes are configured. (SSSVN-8)

Fixed an issue where IPv6 addreses in host:port format could not be parsed in the ocss7.urlList TCAP stack configuration property. (SSSVN-133)

"We should never have invoke timeout in UNUSED or ALLOCATED state" TCAP stack message has been downgraded from SEVERE to DEBUG. (SSSVN-182)

Segmentation configuration parameters MSS and MUSS will no longer permit unacceptable combinations. (SSSVN-209)

The CLI now reports a connection error rather than an unknown error when unable to communicate with the SGC. (SSSVN-228)

Fixed a ConcurrentModificationException that could be thrown in TcapRouter. This also fixes an issue where the TcapRouter could prevent graceful shutdown from completing. (SSSVN-315)

Fixed issue where "releasing begin prefix which has apparently been not assigned - no prefix at all" could be erroneously logged. (SSSVN-316)

Fixed very small thread local leak seen when rebuilding outbound translation data. (SSSVN-338)

Fixed an issue where SctpManagementMessages that were queued for transmission when a socket was closed were not released properly. (SSSVN-353)

sgcd script now creates /var/lock/subsys/sgcd entry. (SSSVN-365)

If the SGC fails to start up due to an Exception the stack trace from that Exception will now be logged at WARN (used to be logged at DEBUG). (SSSVN-376)

Made some usability fixes to the display-event-history command. (SSSVN-383)

SCCP defers registering to handle distributed tasks until after ReqCtx pools have been initialized. This prevents a NullPointerException at SccpManagement.sendSCMGMessage. (SSSVN-457)

Fix NullPointerException if an unknown alarm is raised via Hazelcast. (SSSVN-464)

Unexpected exceptions thrown while processing SGCTopics will now cause the SGC to attempt a graceful shutdown, similar to uncaught exceptions thrown elsewhere. (SSSVN-513)

Fixed NullPointerException in NodeObjectManager.nodeLeft when a node without configuration (create-node) leaves the cluster. (SSSVN-538)

Updated documentation to include Hazelcast configuration recommendations for clusters with more than 2 members. (SSSVN-550)

Applied a workaround for Hazelcast issue where a lock owned by an SGC could be unlocked underneath it during exit of another cluster member, generating "java.lang.IllegalMonitorStateException: Current thread is not owner of the lock!" messages. (SSSVN-604)

Fixed NullPointerException during config save. (SSSVN-626)

Fixed case where create-XXX could return before XXX had completed creation, resulting in subsequent enable-XXX or remove-XXX commands failing to notice that XXX was created. (SSSVN-626)

Decoder now correctly decodes Reject components that have no argument when received with component length in indefinite length form. (SSSVN-638)

Added -XX:+PrintGCDateStamps JVM flag to SGC startup script. (SSSVN-407)

Added documentation suggesting appropriate ulimit settings for user processes. (SSSVN-575)

Changed some default ports so that they’re no longer in the emphemeral range: SGC’s JMX port, Hazelcast multicast UDP discovery port. (SSSVN-618)

Fixed issue that could result in the SGC’s routing taking longer than expected to be available. (SSSVN-608)

Prevent NullPointerException during alarm unregistration while an SGC cluster split/merge is in progress from restarting the SGC. (SSSVN-553)

Failure of the comm switch to bind its listen port will now raise an alarm at critical level and attempt to rebind that port at regular intervals until successful. (SSSVN-531)

Corrected issue where global title translation tables were only updated on a single node after a local SSN status change. (SSSVN-536)

Fixed a ConcurrentModificationException that could occur when multiple threads attempted to modify the same configuration object simultaneously. (SSSVN-511)

Fix NullPointerException that could occur if global title rules were created and deleted very quickly. (SSSVN-420)

Corrected issue where display-info-remotessninfo was not updated cluster-wide on a local SSN state change. (SSSVN-517)

Fixed an issue which caused the SGC to leave gracefully disconnected TCAP stack connections in CLOSE_WAIT state indefinitely. (SSSVN-488)

Unexpected exceptions thrown while processing SGCTopics will now cause the SGC to attempt a graceful shutdown, similar to uncaught exceptions thrown elsewhere. (SSSVN-513)

Fixed an error where certain DPCs in SST/SSA/SSP messages would be incorrectly decoded. (SSSVN-314)

Fixed a race condition that could result in the SGC shutting down due to an unchecked IllegalStateException during task data pool exhaustion. (SSSVN-395)

Fixed an issue where segments could arrive out of order if sent while the task pool was exhausted. (SSSVN-397)

Fixed NullPointerExceptions that could sometimes be thrown when requesting SNMP counters for OGT and DPC info. (SSSVN-398)

Fixed an issue where under certain conditions all worker threads could be hanging around waiting to be allowed to send, resulting in no worker threads available to process incoming messages (such as heartbeats required to maintain connectivity). (SSSVN-400)

Fixed an issue where segments received split across multiple stream IDs could result in the SGC exiting due to an uncaught exception. (SSSVN-406)

Fixed an issue which could prevent the SGC from successfully restarting. (SSSVN-364)

Fixed an issue with SCCP decoding when the Data part comes after the Optional Parameters part in the received message. (SSSVN-372)

Fixed a NullPointerException caused by insufficient tasks being available in the task pool. (SSSVN-201)

Fixed AssertionError: Empty buffer: Cannot decode message when transferring messages internally from one SGC to another. (SSSVN-352)

Fixed an issue which could cause the SGC not to restart automatically following a graceful shutdown caused by an uncaught exception. (SSSVN-249)

Fixed an issue causing the CLI and MBeans to display stale status information for asinfo, associationinfo, dpcinfo, and pcinfo on failed SGCs. (SSSVN-202)

Fixed a race condition that could cause the SGC to attempt to register the same MBean twice. (SSSVN-159)

Handled the failure to deliver NOTICE to TCAP stack in an edge case. (SSSVN-165)

The uncaught exception handler is now initialized earlier. (SSSVN-248)

The example hazelcast.xml.sample file now matches the in-jar default hazelcast configuration. (SSSVN-235)

Disabled the hazelcast SystemLogService by default as it has a small memory leak. (SSSVN-192)

Fixed a NullPointerException in OgtInfoHelper.compare, which resulted in display-info-ogtinfo, snmpwalk and retrieving snmp stats to fail under certain conditions. (SSSVN-363)

Fixed the SGC system OID to be the correct OID. (SSSVN-371)

The SGC no longer spams stdout (or the startup log) with state info. (SSSVN-146)

Outbound global title translation errors are now logged at WARN level. (SSSVN-43)

Added generate-report.sh script for easy log gathering. (SSSVN-191)

The default Hazelcast configuration has been changed so that the SGC now detects cluster member failure more quickly. (SSSVN-295/SSSVN-280)

Changed the default values of ocss7.trdpCapacity , ocss7.schNodeListSize, ocss7.taskdpCapacity, ocss7.wgQueuesSize, and ocss7.senderQueueSize; this provides a more coherent default configuration. (SSSVN-274)

Fixed an issue which caused the SGC not to raise alarms for certain configuration items (ASes, associations, etc) if it was unable to activate them after starting up. (SSSVN-129)

Fixed a issue which would cause the SGC to throw an AssertionError and exit abnormally after receiving a TC-BEGIN which could not be handled because of insufficient resources. (SSSVN-302)

Fixed an issue which could cause the SGC to crash under certain M3UA failure conditions. (SSSVN-196)

Fixed an issue which could cause DPC configuration changes for segmentation not to be applied when changed. (SSSVN-211)

An error is now returned to the CGIN user when attempting to initiate a dialog to a global title longer than the supported maximum. (SSSVN-53)

Fixed a SGC crash that could occur when unregistering alarms. (SSSVN-255)

display-info-associationinfo no longer intermittently displays out of date information following disabling of an active association. (SSSVN-285/SSSVN-279)

Fixed an issue with the CLI which caused it to report unknown command errors when the connection to the SGC was lost. (SSSVN-99)

SCCP XUDT support extended to include reassembly of incoming segments, segmentation of outgoing messages, and configuration of segmentation parameters and preferred message type per destination Point Code. (SSSVN-79)

Added SGC startup option --seed, which can be used to provide an alternative entropy source to the SGC’s encryption facilities. (SSSVN-116)

When deactivating an M3UA connection to a peer the SGC now sends ASP-INACTIVE and ASP_DOWN rather than simply using the SCTP Shutdown procedure. (SSSVN-123)

SGC local port configuration validation prevents the use of ports below 1,024. (SSSVN-124)

The SGC will now restart correctly if terminated by an uncaught Exception or Error. (SSSVN-157)

Fixed an issue causing SCTP association down alarms to be removed and replaced periodically while the association remained down. (SSSVN-120)

Fixed MIB syntax errors which prevented some SNMP clients from accepting the OCSS7 MIB. (SSSVN-1)

Fixed timestamps sent by SNMP, which now send the day of the month, but used to send the day of the year. (SSSVN-2)

Corrected the spelling of CLI configuration parameter table.format.maxCellContentLength. (SSSVN-51)

Input is now validated when changing boolean configuration attributes. (SSSVN-61)

Fixed an SCCP handling bug which could cause the SGC to exit if an unrecognised optional parameter was received. (SSSVN-126)

Fixed an issue allowing overly long GTs to be placed in inbound-gtt configuration. (SSSVN-152)

Fixed in issue allowing overly long GTs to be placed in replace-gt configuration. (SSSVN-54)

The SGC’s SNMP MIB description strings have been improved. (SSSVN-58)

If both global title and point code are absent on an incoming SCCP message, set the SCCP OPC to that of the L3MTP OPC, in order that we’re able to route responses to this message. (SSSVN-104)

Support A, D and E sccp address global title digits (defined as spare in Q.713). (SSSVN-42)

Inbound GTT rules may omit the SSN, allowing the CdPA SSN to be retained. (SSSVN-4)

Inbound GTT rules with duplicate NAI/NP/TT/digits can no longer be created. (SSSVN-5)

Fixed incorrect outbound GTT for messages with: GT present, PC present, SSN absent. (SSSVN-11)

Initial release.