The SS7 SGC Stack acts as one or more Application Servers when connected to the Signalling Gateway or another Application Server (in IPSP mode). M3UA configuration can be separated in two related domains:
Attribute modification restrictions
Only attributes that are "Reconfigurable" can be modified after a configuration object is created.
Attributes that do not support "Active Reconfiguration" can be changed only when the configuration object is disabled (the value of its |
Application Server and routes
After an SCTP association with SG is established, the as-connection that maps connections to Application Servers is checked. This allows for the SGC to inform SG which routing contexts should be active for that SCTP association. Also, with mapping internally, SGC decides which Point Codes are reachable through the SCTP association (the chain of dependencies is: connection
- as-connection
- as
- route
- pc
).
as
Represents an Application Server — a logical entity serving a specific Routing Key. Defines the Application Server that the SGC Stack will represent after the connection to SG/IPSP peer is established.
Attribute name |
Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
is object enabled |
|
Reconfigurable using active reconfiguration |
|
what kind of AS this is; whether it should handle |
|
|
|
routing context
NOTE: This attribute is optional, but only one |
||
|
State of the AS ( |
Read-only |
|
|
maximum number of pending messages, per node Applicable only to |
|
Reconfigurable |
|
maximum pending time (in milliseconds) Applicable only to AS mode. |
|
Reconfigurable |
The JMX Object name for as is SGC:type=m3ua,category=as .
|
route
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
reference to DPC |
||
|
reference to AS |
||
|
priority of the route (larger value is higher priority) |
|
The JMX Object name for route is SGC:type=m3ua,category=route .
|
dpc
A DPC defines a remote point code which is accessible from this SGC cluster. DPCs are used to define routes (route
) which bind DPCs to specific Applications Server (as
) definitions and SCTP associations (connections
).
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
destination point code; a 14-bit integer; |
Reconfigurable |
|
|
network appearance Attribute is optional |
Reconfigurable |
|
|
maximum user data length per segment to send to this destination, supported values: 0-247 (0=do not segment) |
|
Reconfigurable |
|
maximum unsegmented SCCP message size to send to this destination as a single unsegmented message, supported values: 160-254 inclusive |
|
Reconfigurable |
|
SCCP message type that this destination prefers to receive when there is a choice available, supported values: UDT, XUDT |
|
Reconfigurable |
The JMX Object name for dpc is SGC:type=m3ua,category=dpc .
|
as-precond
Before the Application Server (as
) becomes active, the SGC Stack may require certain TCAP Stacks representing some SSN (CGIN RAs) to register with SGC. The Application Server will be activated after ALL defined preconditions (as-precond
) are satisfied.
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
affected AS name |
||
|
subsystem number which must be connected |
The JMX Object name for as-precond is SGC:type=m3ua,category=as-precond .
|
as-connection
Mapping of Application Server (as
) to SCTP association (connection
), defining which Application Servers should be active on a particular connection.
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
reference to AS |
||
|
reference to SGConnection |
||
|
sending DAUD on |
|
Reconfigurable |
The JMX Object name for as-connection is SGC:type=m3ua,category=as-connection .
|
Listening for and establishing SCTP associations
Below are attributes for configuration directly related to establishing SCTP associations to M3UA peers.
local-endpoint
local-endpoint
, together with local-endpoint-ip
, defines the IP address where the SGC Node should listen for incoming SCTP associations.local-endpoint
configuration is also used as the source address for outgoing SCTP associations. local-endpoint
by itself defines the port and M3UA configuration for all connections that are associated with it.
Each SGC Node can use multiple local endpoints. |
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
is object enabled |
|
Reconfigurable using active reconfiguration |
|
is object active |
Read-only |
|
|
SGC Node where the object is used |
||
|
local SCTP port |
Reconfigurable |
|
|
maximum number of input streams requested by the local endpoint |
OS default |
Reconfigurable |
|
maximum number of output streams requested by the local endpoint |
OS default |
Reconfigurable |
|
size of the socket send buffer |
OS default |
Reconfigurable |
|
size of the socket receive buffer |
OS default |
Reconfigurable |
|
maximum |
|
Reconfigurable |
|
maximum |
|
Reconfigurable |
|
maximum |
|
Reconfigurable |
|
maximum |
|
Reconfigurable |
|
enables or disables a Nagle-like algorithm |
|
Reconfigurable |
|
linger on close if data is present |
OS default |
Reconfigurable |
The JMX Object name for local-endpoint is SGC:type=m3ua,category=local-endpoint .
|
local-endpoint-ip
Configuration of IPs for local-endpoint
, to make use of SCTP multi-homed, feature-defined, multiple IPs for a single local endpoint.
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
IPv4 or IPv6 address |
||
|
name of the referenced local endpoint |
The JMX Object name for local-endpoint-ip is SGC:type=m3ua,category=local-endpoint-ip .
|
IPv6 considerations
When using IPv6 addressing, remember to configure the |
connection
connection
, together with conn-ip
, defines the remote IP address of the SCTP association. The SGC Node will either try to establish that association (CLIENT
mode) or expect a connection attempt from a remote peer (SERVER
mode).
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
is object enabled |
|
Reconfigurable using active reconfiguration |
|
is object active |
Read-only |
|
|
remote SCTP port |
Reconfigurable |
|
|
reference name to local endpoint |
||
|
specifies if acts as server for SCTP connect ( |
Reconfigurable |
|
|
specifies how often ASP attempts to send |
|
Reconfigurable using active reconfiguration |
|
specifies how often ASP attempts to send |
|
Reconfigurable using active reconfiguration |
|
specifies time interval (in seconds) between connection attempts |
|
Reconfigurable using active reconfiguration |
|
Specifies if SGC on this associations sends |
|
Reconfigurable |
|
asp identifier Attribute is optional |
Reconfigurable |
|
|
specifies whether connection works in IPSP mode |
|
|
|
maximum number of messages waiting to be written into the SCTP association |
|
Reconfigurable |
The JMX Object name for connection is SGC:type=m3ua,category=connection .
|
conn-ip
Configuration of IPs for connection
, to make use of SCTP multi-homed, feature-defined,multiple IPs for a single connection.
Attribute name | Attribute description | Default | Modification |
---|---|---|---|
|
object name |
||
|
number of items which depend on this object |
Read-only |
|
|
IPv4 or IPv6 address |
||
|
name of the referenced connection |
The JMX Object name for conn-ip is SGC:type=m3ua,category=conn-ip .
|
IPv6 considerations
When using IPv6 addressing, remember to configure the |