Actions

Use Cases:TMG Performing M2UA Signaling Relay: Difference between revisions

mNo edit summary
mNo edit summary
Line 19: Line 19:
|  
|  
*[[Toolpack:Protocol_Stack_Settings_B#M2UA-MTP3-ISUP|MTP2-M2UA Configuration]]
*[[Toolpack:Protocol_Stack_Settings_B#M2UA-MTP3-ISUP|MTP2-M2UA Configuration]]
**M2UA Configuration -> Note Type: M2UA-MTP2 Relay
**M2UA Configuration -> Node Type: M2UA-MTP2 Relay
**M2UA Link -> Bind the configured MTP2 link
**M2UA Link -> Bind the configured MTP2 link
**No need to configure MTP3 part
**No need to configure MTP3 part
|
|
*[[Toolpack:Protocol_Stack_Settings_B#M2UA-MTP3-ISUP|MTP2-M2UA Configuration]]
*[[Toolpack:Protocol_Stack_Settings_B#M2UA-MTP3-ISUP|MTP2-M2UA Configuration]]
**M2UA Configuration -> Note Type: SG
**M2UA Configuration -> Node Type: SG
**M2UA Link -> Bind the configured MTP2 link
**M2UA Link -> Bind the configured MTP2 link
**No need to configure MTP3 part
**No need to configure MTP3 part

Revision as of 11:27, 6 July 2022

Applies to version(s): v2.9 and above

In this scenario, all messages from TDM network are relayed to the IP network via Sigtran: M2UA. This can be used on a satellite link.




Note: This implementation, although based on standards, is proprietary. Normally, one end is the SG and the other is the MGC.

So in this use case, one of the TMGs simulates the MGC. All of this is transparent to the TDM devices interconnected over IP.


Configure TMG: M2UA Relay Configure TMG: M2UA SG
  • MTP2-M2UA Configuration
    • M2UA Configuration -> Node Type: M2UA-MTP2 Relay
    • M2UA Link -> Bind the configured MTP2 link
    • No need to configure MTP3 part
  • MTP2-M2UA Configuration
    • M2UA Configuration -> Node Type: SG
    • M2UA Link -> Bind the configured MTP2 link
    • No need to configure MTP3 part

References