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 M3UA SCTP Servers on each Routing CPU to accept SCTP associations initiated by Application Server Processes (ASPs) to route M3UA messages between the SG and user applications.
Note
Multi-Association ASPs can be defined to amalgamate the multiple SCTP associations under a single ASP (refer to Configuring an M3UA Multi Association ASP). Multi-Association ASPs also enable the SCTP setup to be either a server or a client.
You must configure an M3UA SCTP servers before Single Association ASPs can connect to the SG on a specific Routing VM. If multiple VMs are used for M3UA traffic, then each of these VMs requires its own SCTP server(s) for M3UA.
When creating or modifying an M3UA 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 7352 is raised (refer to 7352 M3UASCTPServerUnresolvedHost1).
When IP Address 2 is configured using a hostname and the SG cannot resolve that hostname, alarm 7354 is raised (refer to 7354 M3UASCTPServerUnresolvedHost2).
When the SG is only able to listen on a subset of the configured/resolved addresses, alarm 7362 is raised (refer to 7362 M3UASCTPServerAddrListMismatch).
When the SG is unable to establish a server on the Port for any of the configured addresses, alarm 7350 is raised (refer to 7350 M3UASCTPServerDown).
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 (see the image under To configure the M3UA SCTP Servers) in the Web UI shows the Slot and Server ID attributes which may be used to associate ASPs to a specific SCTP server.
ASP associations are automatically updated with their corresponding SCTP server attributes when these attributes are modified.
The M3UA SCTP configuration provides a single top level SCTP attribute set with default values. These values are applied to the configuration of all SCTP server across all slots. However, each SCTP server also has its own set of SCTP parameters providing the means to tailor the servers for different 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 M3UA 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 M3UA 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 M3UA SCTP Servers
To activate or deactivate all M3UA SCTP Servers
To create an M3UA SCTP Server
To configure an M3UA SCTP Server
To configure M3UA SCTP Server SCTP configuration
To activate or deactivate an M3UA SCTP Server
Overview
Content Tools