This section of the manual covers upgrading the SGC and the TCAP stack.
Upgrading the SGC
Up to four upgrade options are available depending on the SGC releases being upgraded from and to. The options provide differing levels of automation, service continuity and implementation complexity.
-
Automated Online Upgrade — automated upgrade using a single point code
-
Manual 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 2.2.0.x to OCSS7 3.0.0.x
Notable Changes
-
Support for manual and automated online upgrades from OCSS7 3.0.0.x to a newer version has been added.
-
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.
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.
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-variantandnationalconfiguration parameters to 'General Configuration'. -
Default values for
mssandmussin thecreate-dpcMML 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.
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.
