> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/protocol-stacks-general/creating-a-service-access-point-sap.md).

# Creating a Service Access Point (SAP)

#### ***Applies to version(s): v2.7.***

Now that you have created a [SIP](https://tmediadocs.telcobridges.com/telecom-references/sip-and-voip/sip) stack and a transport server, you must must create a new service access point ([SAP](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7/sap)) for your configuration. The Service Access Point is used to bind the SIP stack with a transport server. Depending on the system configuration, multiple SAPs can be configured.

To create a new SIP SAP:

1- Click **SIP** in the navigation panel

![Sip A 0](https://docs.telcobridges.com/w/images/c/ca/Sip_A_0.png)

2- Click **Edit** next to the SIP stack for which you wish to create a SAP

![Toolpack v2.5 Edit SIP](https://docs.telcobridges.com/w/images/d/d6/Toolpack_v2.5_Edit_SIP.png)

3- Click **Create New Sap** under the **Service Access Points** menu

![Toolpack v2.5 Create SAP](https://docs.telcobridges.com/w/images/2/2a/Toolpack_v2.5_Create_SAP.png)

4- Create the new service access point:

* Enter a **name** for the SAP
* Click **Create**

![Toolpack v2.5 Creating SAP](https://docs.telcobridges.com/w/images/6/6e/Toolpack_v2.5_Creating_SAP.png)

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

![Toolpack v2.5 SAP Created](https://docs.telcobridges.com/w/images/2/20/Toolpack_v2.5_SAP_Created.png)

6- Associate the previously created SIP transport server with your new configuration:

* Select a transport server from the list of available servers
* Associate this configuration by clicking the **"<<"** button
* The transport server will now appear in the list to the left

![Toolpack v2.5 Associate Server](https://docs.telcobridges.com/w/images/4/46/Toolpack_v2.5_Associate_Server.png)

### List of Parameters

* [Name](https://tmediadocs.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://tmediadocs.telcobridges.com/other-pages/protocol-stacks-general/creating-a-service-access-point-sap.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.