In this section:


The purpose of this feature is to allow the Ribbon Signaling Gateway (SG) to support license-dependant proprietary M3UA Media Gateway (MG) links. These links are provisioned at MTP3.

MG links may be provisioned for loadshare across four routes of equal cost (refer to Configuring Four Equal Cost Routes).

The messages, as defined in the M3UA RFC, are in M3UA format on the M3UA MG links and are transmitted using Stream Control Transmission Protocol (SCTP, RFC 4960). Each Routing VM (Routing CPU) supports 500 SCTP Associations. The Linkset SCTP Client attribute (refer to Configuring Linkset Details) must be enabled as M3UA MG links only support SCTP client deployments. A linkset that contains M3UA MG links cannot contain any other link type.

The Web UI provides link state status information for Level 2 and Level 3 link states. Level 2 link state can be In Service (IS) or Out-of-service (OOS) which also pertains to the underlying SCTP association for this link. The Link 3 state for links can also be IS or OOS which also pertains to the M3UA level. IS at MTP3 means the link has been activated and is ready to receive traffic.

M3UA MG links can be used as a combined linkset within a routeset. In this instance, a combined linkset is a routeset that contains two or more routes with the same cost.

M3UA MG linksets can also be configured as Shared Point Codes (SPCs) by enabling the M3UA MG Shared PC attribute. This attribute is configurable at the linkset level through the Web UI. A shared PC is used when an Application Point Code (APC) has the same point code as the Local Point Code (LPC) of the signaling gateway (SG). To avoid MTP3 routing issues, an internal PC is used. This PC is user-configurable and must not be used by any other node on the network. There can only be one SPC route per each routeset. An SPC linkset cannot be a member of a combined linkset.

Click to read more...

Click to read more...

Click to read more...

Click to read more...


  • No labels