In this section:
Note
The terms CPU and VM may be used interchangeably.
For detailed information about the appropriate description of the various supported CPUs and VMs, refer to Terminology.
The Signaling Gateway (SG) allows the provisioning of up to 32 SUA SCTP Servers on each Routing VM to accept SCTP associations initiated by Application Server Processes (ASPs) to route SUA messages between the SG and user applications.
The SUA SCTP servers are configured using the SG SUA SCTP Server screens (see To configure an SUA SCTP Server). You must configure an SUA SCTP server before ASPs can connect to the SG on a specific Routing VM. If multiple VMs are used for SUA traffic, then each of these VMs requires its own SCTP servers(s) for SUA.
When creating or modifying an SUA SCTP Server, at least one of the two IP Address attributes is required. The two IP Address attributes accept either IPv4 addresses, IPv6 addresses, or hostnames. The hostnames must resolve to either IPv4 or IPv6 addresses, or a combination of both address types.
When IP Address 1 is configured using a hostname and the SG cannot resolve that hostname, alarm 7358 is raised (see 7358 SUASCTPServerUnresolvedHost1).
When IP Address 2 is configured using a hostname and the SG cannot resolve that hostname, alarm 7360 is raised (see 7360 SUASCTPServerUnresolvedHost2 ).
When the SG is only able to listen on a subset of the configured/resolved addresses, alarm 7364 is raised (see 7364 SUASCTPServerAddrListMismatch).
When the SG is unable to establish a server on the Port for any of the configured addresses, alarm 7356 is raised (see 7356 SUASCTPServerDown).
Care should be taken to not configure the server with a Port in use elsewhere on the Routing VM.
Each SCTP server is assigned a unique ID on a per slot basis. The ASP Configuration screen in the Web UI shows the Slot and Server ID attributes which may be used to associated ASPs to specific SCTP server.
ASP associations are automatically updated with their corresponding SCTP server attributes when these attributes are modified.
The SUA SCTP configuration provides a single top level SCTP attribute set with default values. These values are applied to the configuration of all SCTP servers across all slots. However, each SUA SCTP server also has its own set of SCTP attributes providing the means to tailor individual SCTP servers for varying network stability across which ASPs may connect. Therefore, the ability to individually modify the SCTP parameters of a given server through the Web UI and have these changes restricted to this server is supported.
When the SCTP servers are configured, they must be activated. This action allows the SG to accept ASP connections. Deactivating an SUA SCTP server stops the SG from listening on the port. The server will no longer accept new connections at this point. ASPs currently connected via the server port are unaffected.
Note
The server attributes can be changed if required; however, it is recommended you do not change the default attributes.
Note
On creation or modification of an SUA SCTP server using IPv4 and/or IPv6 addresses, if a conflict with an existing M3UA/SUA server or an existing M3UA ASP Association is detected, an error message indicating a conflict appears and the server is not created or modified. For more information about object conflicts, refer to Signaling Gateway Object Conflicts.
To configure the SUA SCTP Servers
To activate or deactivate all SUA SCTP Servers
To create an SUA SCTP Server
To configure an SUA SCTP Server
To configure SUA SCTP Server SCTP configuration
To activate or deactivate an SUA SCTP Server
Overview
Content Tools