Use Cases:Configuring Tmedia Gateways for M3UA SGSG Passthrough: Difference between revisions
(Formatting changes) |
No edit summary |
||
Line 61: | Line 61: | ||
*[[Toolpack:M3UA_Use_Case_A:Creating an M3UA Route (IPSP) C|Create an M3UA Route]] | *[[Toolpack:M3UA_Use_Case_A:Creating an M3UA Route (IPSP) C|Create an M3UA Route]] | ||
** In this use case, two M3UA routes are needed: | ** In this use case, two M3UA routes are needed: | ||
***Route towards SGP: Psrv, PC_Mask (0.0.0), M3UA peer server | ***Route towards SGP: Psrv, PC_Mask (0.0.0), M3UA peer server above, M3UA Userpart=NONE, subservice=NONE | ||
***Route towards Customer switch: MTP3, PC:0.0.0 mask, M3UA Userpart | ***Route towards Customer switch: MTP3, PC:0.0.0 mask, M3UA Userpart, subservice=NONE | ||
|} | |} |
Revision as of 16:39, 14 July 2021
Applies to version(s): v3.0 and above
This configuration allows you to pass transparently all packets destined to the service provider network represented by a Signaling gateway (SGP).
Note that the Point code is shared between the SGSG and the SGP device
Configure MTP2 | Configure MTP3 | Configure IP Interface | Configure M3UA |
---|---|---|---|
|
|
|
|