> 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/telecom-references/ss7-and-signalling/ss7/sls.md).

# SLS

## Signaling Link Selector

### Description

The **signaling link selection** (or *SLS*) is a field in the Message Transfer Part level 3 (MTP3) frame of [SS7](/telecom-references/ss7-and-signalling/ss7.md).

The SLS is used as a label to route MTP level 3 messages in the SS7 network.

SLS can also be used in reference to the algorithm that an SS7 node uses for selection of the appropriate signaling link to use for communicating with an adjacent SS7 node. Factors such as load balancing and link availability are used to determine the appropriate link.

| SLS lenght | Variants      | Description                                 |
| ---------- | ------------- | ------------------------------------------- |
| 4 bits     | ITU,TTC,CHINA | The SLS is 4 bits wide                      |
| 5 bits     | ANSI          | Prior to ANSI96, this bit is 5 bits wide    |
| 8 bits     | ANSI96        | This field was extended to 8 bits in ANSI96 |

### Example

#### ITU MTP3 SLS field

![SCCP MTP3 SLS](https://docs.telcobridges.com/w/images/2/22/SCCP_MTP3_SLS.png)

### Reference

[Ref: SLS on Wikipedia](http://en.wikipedia.org/wiki/Signaling_Link_Selection)


---

# 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/telecom-references/ss7-and-signalling/ss7/sls.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.