> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-m3ua-peer-signalling-process-sgp.md).

# Creating an M3UA Peer Signalling Process (SGP)

> **Applies to:** Tmedia 3.0, 3.2, 3.3

After you create an M3UA user part, you must create a new M3UA peer signaling process (PSP), which is used to describe a remote ASP that is accessible through the M3UA system.

To create an M3UA Peer Signaling Process (PSP) on IPSP:

1- Click **M3UA** in the navigation panel:

![CreateM3ua 0](https://docs.telcobridges.com/w/images/7/7b/CreateM3ua_0.png)

2- Select an M3ua Network:

![SelectNetwork SGP 0](https://docs.telcobridges.com/w/images/2/2e/SelectNetwork_SGP_0.png)

3- Click **Create New M3ua Peer Signaling Process** in the M3UA network configuration window:

![Create M3UA PSP SGP 0](https://docs.telcobridges.com/w/images/c/cb/Create_M3UA_PSP_SGP_0.png)

4- Configure the new M3UA PSP:

* Enter a **name** for the PSP
* Select **Application Server Process (ASP)** as the PSP type
* Enter a **destination port** (as configured in the destination element)
* Click **Create**

![Create M3UA PSP SGP 1](https://docs.telcobridges.com/w/images/4/4c/Create_M3UA_PSP_SGP_1.png)

5- Verify that the **"M3ua PSP was successfully created"** message appears

![Create M3UA PSP SGP 2](https://docs.telcobridges.com/w/images/5/57/Create_M3UA_PSP_SGP_2.png)

6- Associate a SAP with the new PSP:

* Select a **SAP** from the list of available SAPs
* Click the **"<<"** button to associate it with the PSP

![Create M3UA PSP SGP 3](https://docs.telcobridges.com/w/images/3/3c/Create_M3UA_PSP_SGP_3.png)

7- Enter a destination address for the PSP:

* Enter a **destination address**
* Click **"<<"** to add the destination address to the PSP

![Create M3UA PSP SGP 4](https://docs.telcobridges.com/w/images/3/31/Create_M3UA_PSP_SGP_4.png)

8- Verify that the **"*****(your address)*****&#x20;was successfully added"** message appears

![Create M3UA PSP SGP 5](https://docs.telcobridges.com/w/images/9/9d/Create_M3UA_PSP_SGP_5.png)

**Path**

```
configurations/@[configuration_name]/m3ua_stacks/@[m3ua_name]/m3ua_networks/@[m3ua_network]/m3ua_psps/@[m3ua_psp]
```

**Parameters (text)**

```
/configurations/@[configuration_name]/m3ua_stacks/@[m3ua_name]/m3ua_networks/@[m3ua_network]/m3ua_psps/@[m3ua_psp]
dst_port            = 2905
ip_dsts             = [  ]
name                = "@[m3ua_psp]"
nb_of_sctp_streams  = 5
saps                = [ "@[m3ua_sap]" ]
type                = "Application Server Process (ASP)"

configurations/@[configuration_name]/m3ua_stacks/@[m3ua_name]/m3ua_networks/@[m3ua_network]/m3ua_psps/@[m3ua_psp]/advanced_parameters
allow_re_register               = false
asp_id_mode                     = "None"
configure_for_all_local_ips     = false
include_routing_ctx             = true
initiate_sctp_association       = true
ip_header_tos                   = 0
ipsp_double_ended               = false
load_sharing_mode               = "SLS"
network_appearance              = false
network_appearance_value        = 0
rk_dynamic_registration_allowed = false
rk_registration_request_send    = false
routing_ctx_mandatory           = false
self_asp_id                     = 0
sg_id                           = 0

configurations/@[configuration_name]/m3ua_stacks/@[m3ua_name]/m3ua_networks/@[m3ua_network]/m3ua_psps/@[m3ua_psp]/state
inhibited    = false
target_state = "Default"
```

**Parameters (json)**

```
{
  "advanced_parameters" : {
    "allow_re_register" : false,
    "asp_id_mode" : "None",
    "configure_for_all_local_ips" : false,
    "include_routing_ctx" : true,
    "initiate_sctp_association" : true,
    "ip_header_tos" : 0,
    "ipsp_double_ended" : false,
    "load_sharing_mode" : "SLS",
    "network_appearance" : false,
    "network_appearance_value" : 0,
    "rk_dynamic_registration_allowed" : false,
    "rk_registration_request_send" : false,
    "routing_ctx_mandatory" : false,
    "self_asp_id" : 0,
    "sg_id" : 0
  },
  "dst_port" : 2905,
  "ip_dsts" : [
  ],
  "name" : "@[m3ua_psp]",
  "nb_of_sctp_streams" : 5,
  "saps" : [
    "@[m3ua_sap]"
  ],
  "state" : {
    "inhibited" : false,
    "target_state" : "Default"
  },
  "type" : "Application Server Process (ASP)"
}
```

### List of Parameters

* [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [PSP Type](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#p)
* [Destination Port](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#d)
* [Number of SCTP Streams](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-m3ua-peer-signalling-process-sgp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
