Actions

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

No edit summary
No edit summary
Line 19: Line 19:
|-
|-
|  
|  
*[[Toolpack:Creating_M2UA_Links_C]]. You need to modify the default behavior or some reason causes:  
*[[Toolpack:Creating_M2UA_Links_C]]
 
You need to modify the default behavior or some reason causes:  
**'''Profiles''' -> Edit Reason Cause Mapping
**'''Profiles''' -> Edit Reason Cause Mapping
***'''300 Multiple Choices'''-> Route retry action -> Stop Call
***'''300 Multiple Choices'''-> Route retry action -> Stop Call
Do this for all Reason Cause that will be used
Do this for all Reason Cause that will be used
|  
|  
*Create normal routes to the redirect server: [[Toolpack:Toolpack:Creating_M2UA_Links_C]]:
*[[Toolpack:Creating_M2UA_Links_C]]
**'''Routes''' -> Create New Static Route
**'''Routes''' -> Create New Static Route
***'''Name''' -> To_SIP_Redirect_Server
***'''Name''' -> To_SIP_Redirect_Server

Revision as of 16:52, 28 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
You need to modify the default behavior or some reason causes: 
    • Profiles -> Edit Reason Cause Mapping
      • 300 Multiple Choices-> Route retry action -> Stop Call

Do this for all Reason Cause that will be used