Actions

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

No edit summary
 
Line 16: Line 16:
|  
|  
*[[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
|
|
*[[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: ASP
**M2UA Configuration -> Node Type: ASP
**M2UA Link -> Bind the configured MTP2 link
**M2UA Link -> Bind the configured MTP2 link
**Need to configure MTP3 part
**Need to configure MTP3 part

Latest revision as of 11:28, 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.





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

References