> 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/ss7-and-signalling/sccp/interworking.md).

# Interworking

[SCCP](/telecom-references/ss7-and-signalling/sccp.md) supports interworking between various ITU-T variants (1988, 1992, and 1996) as described in the Q.715 ITU-T Specification.

From the point of view of the SCCP user, there is only one SCCP. It is the responsibility of the SCCP to take all the necessary measures to select the correct message types to be sent out and to segment messages, if necessary. Hence, at certain interworking nodes, a capability needs to be provided that allows conversion of the new message types (LUDT7, LUDTS7) to XUDT, XUDTS message types provided in the 1993 edition, therefore allowing the segmenting of a LUDT message into multiple XUDT messages (or possibly multiple LUDT messages if the destination understands them), or truncating a long LUDTS to fit into a single XUDTS message, if necessary.

**NOTE:** As of August 2009, LUDT and LUDTS are not supported.


---

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