Use Cases:M3UA A: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Use Cases: M3UA Configuration}} | {{DISPLAYTITLE:Use Cases: M3UA Configuration}} | ||
==Applies to== | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Latest revision as of 14:18, 23 June 2024
Applies to
| This article applies to: | Product | Version |
| Tmedia | 3.0, 3.2, 3.3 |
The following uses cases provide guidance for some specific M3UA configurations.
Select a use case to learn about its configuration.
This configuration is a standard signaling gateway from MTP2/MTP3 to M3UA Application Server Process (ASP)
|
|
This configuration is a standard M3UA Application Server Process (ASP)
|
|
Configuring Tmedia Gateways for M3UA SGP with IP Point Code
This configuration allows you act as a signaling gateway towards an M3UA ASP
There needs to be a point code defined for the SGP, but is not used externally
|
|
Configuring Tmedia and TSG Gateways for M3UA SGSG Passthrough
This configuration allows you to pass transparently all packets destined to the service provider network represented by a Signaling gateway (SGP).
Note that the Point code is shared between the SGSG and the SGP device
|
|



