The SCCP layer can be configured to support multiple OPCs to both single networks or multiple networks. The SCCP layer receives SCCP messages, both connectionless and connection-oriented, addressed to any of the configured OPC values. SCCP subsystem management messages for each OPC are also supported.
The MTP layer must be configured correctly for multiple OPC emulation. For more information and examples for emulating multiple OPCs to a single network and to multiple networks, refer to Configuring multiple OPC emulation.
The SCCP layer can be configured to emulate two different OPCs to a single destination.
In this example, the SCCP layer emulates OPC 0.0.2 to the DPC 0.0.1, and emulates OPC 0.0.4 to the same DPC 0.0.1. An ALT_OPC section (ALT_OPC through the END statement) must be added to the USAP section for each emulated OPC:
USER_SAP 0 # Sap number start at 0
SWITCH_TYPE ITU92 # one of ITU92, ITU88, ANSI92, ANSI88
ADDR_MASK FFF0000000 # match on only 1st 3 digits of GT
MAX_HOPS 10 # maximum network hops
INACT_CONTROL TRUE # app inactivity timing
# ALT_OPC section must be placed at end of USER_SAP section
ALT_OPC 0.0.2 # Alternate Originating Point Code
CONC_PC 0.0.1 # Concerned point code
END
ALT_OPC 0.0.4 # Alternate Originating Point Code
CONC_PC 0.0.1 # Concerned point code
END
END # User application 0
An ALT_OPC field must be added to the ROUTE section for each emulated OPC:
ROUTE 0.0.1 # destination point code
SWITCH_TYPE ITU # one of ITU, ANSI
ADJACENT TRUE # this dest directly adjacent
TRANSLATOR FALSE # not a translator node
ALT_OPC 0.0.2
ALT_OPC 0.0.4
#define all subsystems of interest at 0.1.2 (up to 8)
SSN 3 # first subsystem
SSN_SNR TRUE # normal routed
SSN_ACC TRUE # initially accessable
END # SSN 3
SSN 254 # another subsystem
SSN_SNR TRUE # normal routed
SSN_ACC TRUE # initially accessable
END # SSN 254
END # of route 0.1.2
The SCCP layer can be configured to emulate a different OPC to each of two different networks.
In this example, the SCCP layer emulates OPC 0.0.2 to the DPC 0.0.1, and emulates OPC 0.0.4 to the DPC 0.0.3. An ALT_OPC section (ALT_OPC through the END statement) must be added to the USAP section for each emulated OPC:
USER_SAP 0 # Sap number start at 0
SWITCH_TYPE ITU92 # one of ITU92, ITU88, ANSI92, ANSI88
#CONC_PC 0.0.1 # Concerned point code
ADDR_MASK FFF0000000 # match on only 1st 3 digits of GT
MAX_HOPS 10 # maximum network hops
INACT_CONTROL TRUE # app inactivity timing
# ALT_OPC section must be placed at end of USER_SAP section
ALT_OPC 0.0.2 # Alternate Originating Point Code
CONC_PC 0.0.1 # Concerned point code
END
ALT_OPC 0.0.4 # Alternate Originating Point Code
CONC_PC 0.0.3 # Concerned point code
END
END # User application 0
An ALT_OPC field must be added to each ROUTE section for each emulated OPC:
ROUTE 0.0.1 # destination point code
SWITCH_TYPE ITU # one of ITU, ANSI
ADJACENT TRUE # this dest directly adjacent
TRANSLATOR FALSE # not a translator node
ALT_OPC 0.0.2
#define all subsystems of interest at 0.1.1 (up to 8)
SSN 3 # first subsystem
SSN_SNR TRUE # normal routed
SSN_ACC TRUE # initially accessable
END # SSN 3
SSN 254 # another subsystem
SSN_SNR TRUE # normal routed
SSN_ACC TRUE # initially accessable
END # SSN 254
END # of route 0.1.1
#
ROUTE 0.0.3 # destination point code
SWITCH_TYPE ITU # one of ITU, ANSI
ADJACENT TRUE # this dest directly adjacent
TRANSLATOR FALSE # not a translator node
ALT_OPC 0.0.4
#define all subsystems of interest at 0.1.1 (up to 8)
SSN 3 # first subsystem
SSN_SNR TRUE # normal routed
SSN_ACC TRUE # initially accessable
END # SSN 3
SSN 254 # another subsystem
SSN_SNR TRUE # normal routed
SSN_ACC TRUE # initially accessable
END # SSN 254
END # of route 0.1.1