Upgrading the SGC

Up to three upgrade options are available depending on the SGC releases being upgraded from and to. The options provide differing levels of service continuity and implementation complexity.

  • Online Upgrade — manually upgrade using a single point code

  • STP Redirection — manual upgrade method requiring two point codes and support from the network

  • Offline Upgrade — manual upgrade method requiring a single point code plus either an alternate site that traffic may be routed to, or a tolerance of complete loss of service during the upgrade window

Upgrading from OCSS7 4.0.0.x to OCSS7 4.1.x

Notable Changes

  • Releases prior to OCSS7 4.1.x contained a defect that caused SNMPv3 usernames to be prefixed with sC, both for incoming SNMPv3 query authentication and for outbound SNMPv3 notifications. See SNMPv3 Configuration Migration for more details and how to ensure that SNMPv3 is configured as desired in this release.

Upgrade Options

Upgrading from OCSS7 3.0.0.x to OCSS7 4.0.0.x

Notable Changes

  • OCSS7 now requires Java 11.

Upgrade Options

Upgrading from OCSS7 3.0.0.x to OCSS7 3.0.0.x

Notable Changes

None — no patch release is available yet.

Upgrade Options

Upgrading from OCSS7 2.2.0.x to OCSS7 3.0.0.x

Notable Changes

  • The SGC’s MAX_HEAP_SIZE requirements are significantly lower.

  • Significant changes have been made to the CTS-SGC-MIB, see OCSS7 MIB Changes for details.

Upgrade Options

Upgrading from OCSS7 2.1.0.x to OCSS7 2.2.0.x

Notable Changes

Support for ANSI T1.114 TCAP has been added:

  • Existing configurations will continue to work as previously.

  • No configuration changes are required to the SGC to use ANSI TCAP.

  • The TCAP stack must be reconfigured if ANSI TCAP is required. See ANSI TCAP for further information.

Upgrade Options

Upgrading from OCSS7 2.0.0.x to OCSS7 2.1.0.x

Notable Changes

Support for ATIS 1000112 (formerly ANSI T1.112) SCCP has been added:

  • Existing configurations will continue to work as previously.

  • Added sccp-variant and national configuration parameters to 'General Configuration'.

  • Default values for mss and muss in the create-dpc MML command have changed. See DPC configuration for details.

The TCAP stack may be configured to use ANSI SCCP by configuring an SCCP address of type A7 instead of C7. Both the SGC and the TCAP stack must be configured for the same SCCP variant. See ANSI SCCP for further information.

Upgrade Options

Upgrading from OCSS7 1.1.0.x to OCSS7 2.0.0.x

Notable Changes

Hazelcast has been upgraded from version 2.6.5 to version 3.7. This fixes a number of cluster stability issues. Members of a Hazelcast 3.7 cluster are unable to communicate with members of a Hazelcast 2.6.x cluster, therefore it is necessary to ensure that all cluster members are running either SGC 2.0.0.x or 1.1.0.x, not a mix of the two.

The configuration file hazelcast.xml has changed substantially. The configuration should be reviewed, particularly for clusters with more than two members - see Hazelcast cluster configuration for details.

New SCCP and TCAP message statistics are available. Some statistics from the LocalSsnInfo JMX MBean (and associated display-info-localssninfo command line client command and SNMP counters) have been moved to the new SccpStats JMX MBean. See Statistics for details.

Upgrade Options

Previous page Next page