Toolpack:Creating an M3UA Peer Server (SGP) A
From TBwiki
(Difference between revisions)
Nicole Tan (Talk | contribs) |
(→List of Parameters) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=== '''''Applies to version(s): v2.5, v2.6., v2.7''''' === | === '''''Applies to version(s): v2.5, v2.6., v2.7''''' === | ||
{{DISPLAYTITLE:Creating an M3UA Peer Server (SGP)}} | {{DISPLAYTITLE:Creating an M3UA Peer Server (SGP)}} | ||
| − | Now that you have | + | Now that you have created an M3UA peer signaling process (PSP), you must create a new Peer server. |
A peer server is a logical entity on the IP network that is served by one or more PSPs. | A peer server is a logical entity on the IP network that is served by one or more PSPs. | ||
| Line 14: | Line 14: | ||
* Enter a '''name''' for the peer server | * Enter a '''name''' for the peer server | ||
| − | * Create a remote PSRV with a RC value representing the remote side； Take the RC value from ASP configuration. | + | * Create a remote Peer Server (PSRV) with a Routing Context (RC) value representing the remote side； Take the RC value from ASP configuration. |
| − | '''Note''': 1) For SG/ASP this value is mandatory to be the same as the ASP local PSRV RC value | + | '''Note''': |
| − | + | 1) For SG/ASP this value is mandatory to be the same as the ASP local PSRV RC value | |
| + | 2) SG uses only remote peer servers, so local peer server (OPC) is NOT needed | ||
* Select the '''Traffic Mode Type'''. For remote peer server, this field is used in '''ASPAC'''. | * Select the '''Traffic Mode Type'''. For remote peer server, this field is used in '''ASPAC'''. | ||
| Line 33: | Line 34: | ||
[[Image:Toolpack_v2.5_M3UA_Peer_Server_PSP.png]] | [[Image:Toolpack_v2.5_M3UA_Peer_Server_PSP.png]] | ||
| − | |||
==List of Parameters== | ==List of Parameters== | ||
| Line 39: | Line 39: | ||
* [[Parameter: Name|Name]] | * [[Parameter: Name|Name]] | ||
* [[Parameter: Local|Local]] | * [[Parameter: Local|Local]] | ||
| − | * [[Parameter: Routing Context|Routing Context]] | + | * [[Parameter: Routing Context|Routing Context (RC)]] |
* [[Parameter: Traffic Mode Type|Traffic Mode Type]] | * [[Parameter: Traffic Mode Type|Traffic Mode Type]] | ||
Latest revision as of 09:39, 8 July 2014
Applies to version(s): v2.5, v2.6., v2.7
Now that you have created an M3UA peer signaling process (PSP), you must create a new Peer server. A peer server is a logical entity on the IP network that is served by one or more PSPs.
To create an M3UA peer server:
1- Click Create New M3ua Peer Server in the M3UA network configuration window
2- Configure the new M3UA peer server:
- Enter a name for the peer server
- Create a remote Peer Server (PSRV) with a Routing Context (RC) value representing the remote side； Take the RC value from ASP configuration.
Note: 1) For SG/ASP this value is mandatory to be the same as the ASP local PSRV RC value 2) SG uses only remote peer servers, so local peer server (OPC) is NOT needed
- Select the Traffic Mode Type. For remote peer server, this field is used in ASPAC.
- Click Create
3- Verify that the "M3ua Peer server was successfully created" message appears
4- Associate the newly created peer server with a peer signaling process (PSP):
- Select a PSP from the list of available PSPs
- Click the "<<" button to associate the PSP with the peer server
