Use Cases:TMG Performing M2UA Signaling Relay

From TBwiki
(Difference between revisions)
Jump to: navigation, search
m
 
(29 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.jpg|800px]]
+
[[File:Diagram_M2UA_Replay_TBwiki.jpg|800px]]
 
<br /><br />
 
<br /><br />
 
<br />
 
<br />
This is the callflow of such a scenario. A 302 Moved temporarily is returned from the SIP redirect server and the contact information is returned to the incoming leg. for example in ISDN, the contact number will be included in the redirection number of the RELEASE message.<br />
+
Note: This implementation, although based on standards, is proprietary.  
<br />
+
Normally, one end is the SG and the other is the MGC.  
[[File:SIP_Redirect_callflow_(stop).png|800px|link=]]
+
 
<br />
+
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 Reason Cause
+
! 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 Routes
+
! 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 -> Note 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 -> Note 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
+
 
|}
 
|}
  
Also make sure these settings are applied:
+
== References ==
  SIP -> Header Parameters -> Allow Recurse [unchecked]
+
*[[Toolpack:Protocol_Stack_Settings_B#M2UA.3C-.3EMTP2_Relay|Configuring MTP2 to M2UA relay]]
 
+
[[Category:Revise on Major]]
Please note that all contributions to TBwiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
+
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see TBwiki:Copyrights for details). Do not submit copyrighted work without permission!
+
Summary:
+
This is a minor edit  Watch this page
+
Save page Show preview  Show changes Cancel | Editing help (opens in new window)
+
Page Discussion Edit History Move Watch
+
Nicole Tan my talk my preferences my watchlist my contributions log out
+
Navigation
+
Main Page
+
Glossary
+
Frequently Asked Questions
+
Recent changes
+
Random page
+
Help
+
Search
+
 
+
Go  Search
+
Toolbox
+
What links here
+
Related changes
+
Upload file
+
Special pages
+
Powered by MediaWiki  Search Powered by Sphinx
+
Privacy policy About TBwiki Disclaimers
+

Latest revision as of 11:13, 23 August 2019

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.

Diagram M2UA Replay TBwiki.jpg


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 -> 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

References

Personal tools