Below are attributes for configuring an SGC Stack instance and the entire cluster.
Atribute modification restrictions
|
node
The node
configuration object is for configuring an SGC Stack instance. Every SGC instance that is to be a part of cluster must be represented by a node configuration object. During startup, the SGC instance property ss7.instance
is matched against the oname
of existing nodes. If a match is found, the SGC instance will connect to the cluster, acting as that matching node.
Attribute name | Attribute description | Default |
---|---|---|
|
object name |
|
|
number of items which depend on this object |
|
|
is object enabled |
|
|
is object active |
|
local address for CommSwitch to bind to |
||
local port for CommSwitch to bind to |
|
|
|
interface where stack can connect for data connection The TCAP Stack that is bundled with CGIN RA will use this connection to originate and receive TCAP messages. |
value of |
|
port where stack can connect for data connection The TCAP Stack that is bundled with CGIN RA will use this connection to originate and receive TCAP messages. |
|
|
interface where stack can get balancing information The TCAP Stack that is bundled with CGIN RA will use this connection to to register with the SGC node. |
value of |
|
port where stack can get balancing information The TCAP Stack that is bundled with CGIN RA will use this connection to to register with the SGC node. |
|
|
node configuration Specifies values of properties that can be defined in the SGC.properties file. |
The JMX Object name for node is SGC:type=general,category=node
|
parameters
The parameters
category specifies cluster-wide configuration (for a single cluster).
Attribute name | Attribute description | Default |
---|---|---|
|
SCCP variant to be used: The following conditions must be met in order to reconfigure this property:
|
|
|
delay (in milliseconds) before a class1 message is re-sent when route failure is detected |
|
|
local signalling pointcode; format dependent on sccp-variant configuration
|
|
|
local signalling point state ( |
|
|
network indicator used in M3UA messages sent by this node ( |
|
|
the national indicator bit in the address indicator octet of SCCP management messages sent by this node
( The meaning of
|
|
|
interval (in milliseconds) between sent SST messages |
|
|
decay timer (in milliseconds) for SCCP congestion procedure |
|
|
attack timer (in milliseconds) for SCCP congestion procedure |
|
|
maximum restriction sublevel per restriction level (Q.714 section 5.2.8 SCCP management congestion reports procedure) |
|
|
maximum restriction level for each affected SP |
|
|
timer (in milliseconds) for congestion abatement |
|
|
time interval (in seconds) between successive notifications sent |
|
|
time interval (in seconds) between successive notifications sent |
|
|
time interval (in seconds) between successive notifications sent |
|
|
reassembly timeout for SCCP reassembly procedure in milliseconds |
|
|
maximum number of concurrent SCCP reassembly processes that may be active. |
|
|
ANSI TCAP version to assume where this cannot be derived from the the dialog’s initial Query or Uni message. See also the OCSS7 TCAP stack configuration property: |
|
The JMX Object name for parameters is SGC:type=general,category=parameters .
|