> 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/telecom-references/protocols/sccp-configuration-of-layer.md). # SCCP Configuration of layer General guidelines for configuration of SCCP for proper operation include the following steps: 1. The SCCP [general allocation](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/create-a-sccp-stack/README.md) (see Note below) (TB640\_MSG\_ID\_SS7\_SCCP\_OP\_ALLOC) must precede all other messages (other configuration SCCP alloc, get, states and stats). The response of this message is a SCCP handle. 2. The SCCP [network allocation](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/create-a-sccp-network/README.md) must be made (with the SCCP handle from step 1) for a particular network identifier with a particular variant, self point code and subservice field type. The response of this message is a SCCP Network handle. 3. The SCCP [LSAP allocation](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/create-an-sccp-lsap/README.md) must be made (with the SCCP handle from step 1, network handle from step 2 and the unique identifier of the MTP3 userpart) to connect with the MTP3 userpart 4. The SCCP route allocation must be made (with the SCCP handle from step 1 and the lsap handle from step 3 for a particular variant, replicated mode and DPC 5. The SCCP [userpart allocation](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/create-a-sccp-userpart/README.md) must be made (with the SCCP handle from step 1 and the network handle from step 2 for a particular subsystem number 6. The SCCP [GTT association allocation](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-association-configuration/README.md) must be made (with the SCCP handle from step 1) for a particular global title association 7. The SCCP [GTT address map allocation](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-address-map-configuration/README.md) must be made (with the SCCP handle from step 1 and the Gtt asso handle from step 6) for a particular global title address map ### Configuration notes * Step 2 can be done for 1 to the maximum number of configured Networks * Step 3 can be done for 1 to the maximum number of configured LSAPs * Step 4 can be done for 1 to the maximum number of configured Routes * Step 5 must be done for 1 to the maximum number of configured Userparts * Step 6 must be done for 1 to the maximum number of configured GTT Asso * Step 7 must be done for 1 to the maximum number of configured GTT Addrmap --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/protocols/sccp-configuration-of-layer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.