Actions

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

No edit summary
(Added link to new page: M2UA Satellite)
 
(25 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Editing Use Cases:TMG Performing M2UA Signaling Relay
{{DISPLAYTITLE:TMG Performing MTP2 Signaling Relay over M2UA}}
WikitextPreviewChanges
BoldItalicEmbedded fileSignature and timestampLinkReferenceAdvancedSpecial charactersHelp
 
{{DISPLAYTITLE:TMG Performing M2UA Signaling Relay}}
=== '''''Applies to version(s): v2.9 and above''''' ===
=== '''''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 <br />
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. <br />


[[File:Diagram_M2UA_Replay_N.jpg|800px]]
[[File:Diagram_M2UA_Replay_TBwiki.jpg|800px]]
<br /><br />
<br /><br />
<br />
<br />
Note: This implementation, although based on standards, is proprietary.  
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.<br />
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.<br />
 


{| 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="400" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Configure TMG: M2UA Relay
! width="250" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Configure TMG: U2UA SG
! width="400" style="background: none repeat scroll 0% 0% rgb(0, 83, 139);" | Configure TMG: M2UA SG
|-
|-
|  
|  
*[[Toolpack:Modify_NAP_profile_D]]. You need to modify the default behavior or some reason causes:
*[[Toolpack:Protocol_Stack_Settings_B#M2UA-MTP3-ISUP|MTP2-M2UA Configuration]]
**'''Profiles''' -> Edit Reason Cause Mapping
**M2UA Configuration -> Node Type: M2UA-MTP2 Relay
***'''300 Multiple Choices'''-> Route retry action -> Stop Call
**M2UA Link -> Bind the configured MTP2 link
Do this for all Reason Cause that will be used
**No need to configure MTP3 part
|  
|
*Create normal routes to the redirect server: [[Toolpack:Call_Routes_Settings_B#Static_Route|Configure Routes]]:
*[[Toolpack:Protocol_Stack_Settings_B#M2UA-MTP3-ISUP|MTP2-M2UA Configuration]]
**'''Routes''' -> Create New Static Route
**M2UA Configuration -> Node Type: SG
***'''Name''' -> To_SIP_Redirect_Server
**M2UA Link -> Bind the configured MTP2 link
***'''NAP''' -> any
**No need to configure MTP3 part
***'''Remapped_NAP''' -> NAP_SIP_REDIRECT
|}
|}
== References ==
*[[Toolpack:Protocol_Stack_Settings_B#M2UA.3C-.3EMTP2_Relay|Configuring MTP2 to M2UA relay]]
*[[M2UA_Satellite|M2UA Satellite Setings]]
[[Category:Revise on Major]]

Latest revision as of 14:09, 26 September 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