Actions

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

No edit summary
No edit summary
Line 16: Line 16:


{| colspan="4" border="1" class="wikitable"
{| colspan="4" border="1" class="wikitable"
! width="250" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Configure TMG: M2UA Replay
! width="250" style="background: none repeat scroll 0% 0% rgb(0, 83, 155);" | Configure TMG: M2UA Replay
! width="250" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Configure TMG: M2UA SG
! width="250" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Configure TMG: M2UA SG
|-
|-

Revision as of 10:12, 29 July 2016

Editing Use Cases:TMG Performing M2UA Signaling Relay WikitextPreviewChanges BoldItalicEmbedded fileSignature and timestampLinkReferenceAdvancedSpecial charactersHelp


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




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 Replay Configure TMG: M2UA SG
  • MTP2-M2UA Configuration
    • M2UA Configuration -> Note Type: M2UA-MTP2 Relay
    • M2UA Link -> Bind the configured MTP2 link
    • No need to configure MTP3 part
  • MTP2-M2UA Configuration
    • M2UA Configuration -> Note Type: SG
    • M2UA Link -> Bind the configured MTP2 link
    • No need to configure MTP3 part