> 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/configuration-of-layer.md).

# Configuration of layer

The configuration of the [ISUP](/telecom-references/ss7-and-signalling/isup.md) layer (or addition of new elements to an existing layer) must follow a specific sequence. The following sections will detailed the different resources configuration, their parameters and their use.

General guidelines for the configuration of ISUP for a proper operation include the following:

1. The ISUP general allocation\* must precede all other messages (other configuration ISUP allocation, get, states and stats). The response of this message is an ISUP handle.
2. The ISUP Network allocation must be made (with the ISUP handle from step 1) for a particular network. The response of this message is an ISUP network handle.
3. The ISUP userpart allocation must be made (with the ISUP handle from step 1) for a particular switch variant. The response of this message is an ISUP userpart handle.
4. The ISUP interface allocation must be made (with the ISUP handle from step 1, network handle from step 2 and the userpart handle from step 3) for a particular [OPC](/telecom-references/ss7-and-signalling/ss7/opc.md)/[DPC](/telecom-references/ss7-and-signalling/ss7/dpc.md). The response of this message is an ISUP interface handle.
5. The ISUP circuit allocation must be made (with the ISUP handle from step 1 and the interface handle from step 4). The response of this message is an ISUP circuit handle associated with a host-provided handle called the “circuit ID”.

**NOTE:** For any reconfiguration with an ISUP message, all reconfigurable parameters must be filled appropriately even if the intention is to modify a single parameter, unless specified otherwise.

**NOTE:** When a reconfiguration is requested through a ISUP API, the effect may not be observed immediately. This is especially true for timers and thresholds as the targeted event might already be active when the reconfiguration occurs. All fields of a configuration (allocation) message must be filled unless explicitly optional or not defined for certain variants.


---

# 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/configuration-of-layer.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.