> 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/mtp3-userpart-configuration.md). # MTP3 Userpart Configuration * **MTP3 user part unique ID** is used to configure identical [MTP3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp3/README.md) userparts in each MTP3 module and to connect [ISUP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isup/README.md) networks. *** * The **Connection mode** parameter specifies the different modes of connection for an MTP3 userpart. The following values are allowed: | Connection mode | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | SCCP | MPT3 userpart is used in conjunction with an above local SCCP layer and cannot be controlled by the host application | | SCCP with alarms | MPT3 userpart is used in conjunction with an above local SCCP layer and cannot be controlled by the host application but the host application will receive ALARM notifications | | ISUP | MTP3 userpart is used in conjunction with an above local ISUP layer and cannot be controlled by the host application | | ISUP with alarms | MPT3 userpart is used in conjunction with an above local ISUP layer and cannot be controlled by the host application but the host application will receive ALARM notifications | | Host SCCP | MTP3 userpart is used as a standalone and communicates with remote SCCP layer (host application) | | Host TUP 5 | MTP3 userpart is used as a standalone and communicates with remote TUP layer (host application) | | Host ISUP | MTP3 userpart is used as a standalone and communicates with remote ISUP layer (host application) | *** * The **Sub-service field** specifies the type of network. If validation is activated in the general MTP3 configuration, all userpart messages will be compared to this sub-service field type. All non-matching messages will be discarded. The following values are allowed: | Sub-service field | Description | | ----------------- | ------------------------------------------------------------- | | International | Messages sent by the layer will concern international traffic | | National | Messages sent by the layer will concern national traffic | | Reserved | Reserved for national use | **NOTE:** For all national networks (including TTC and NTT), the 'Sub-service' field is configured with 'National'. For international networks, the 'Sub-service' field is configured with 'International'. **NOTE:** For international networks you must have the same values for Prior Message Queue Length 1 to Prior Message Queue Length 1 in a MTP3 Link Configuration. *** * The **Link type** field specifies the MTP3 protocol variant required to provide service to the userpart connected through this upper Service Access Point (SAP). The following values are allowed: | Link type | Description | | --------- | ------------------------------------------------------ | | ANSI | Used for ANSI88 and ANSI92 | | ITU | Used for ITU88, ITU92, ITU97, Q767, SINGAPORE and ETSI | | CHINA | Used for CHINA | | ANSI96 | Used for ANSI96 and TELCORDIA | | TTC | Link type not available yet | | NTT | Link type not available yet | *** * The **DPC length** field specifies the length of the DPC for messages communicated through this SAP. For allowable values, see [MTP2:Destination Point Code](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/point-code-length/README.md). * The **Switch ID** parameter specifies a value to regroup linksets and user parts together. Allowable values are from 10 to 255. For further configuration information see [Protocol Stack Settings](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks/README.md) --- # 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/mtp3-userpart-configuration.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.