> 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/other-pages/use-cases/use-case-configuring-tmedia-m3ua-asp-for-shared-point-code.md). # Use Case: Configuring Tmedia M3UA ASP for Shared Point Code #### ***Applies to version(s): v3.0 and above*** This configuration is a standard M3UA Application Server Process (ASP) | ![M3UA ASP](https://docs.telcobridges.com/w/images/5/52/M3UA_ASP.png) | | --------------------------------------------------------------------- | | Configure IP Interface | Configure SCTP | Configure MTP3 Point Codes | Configure M3UA | Configure ISUP | Configure NAP | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | \*[Configure IP Interface](/configuration/web-portal-3-3/hardware/ip-network/configuring-voip-interfaces.md) \* In this use case, configured as: \*\*IP Address: 192.168.0.99 \*\*Netmask: 255.255.255.0 \*\*Gateway: 192.168.0.1 | \*[Configure SCTP](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-the-sctp-configuration.md) | \*[Configure MTP3 Point Codes](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-ss7-point-codes.md) \*\*In this use case, the following point code names are assigned: \*\*\*destination point code: dpc333 \*\*\*origination point code: opc111 | \*[Configure M3UA](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-configuration.md) \*\* M3UA Mode: ASP \*\*[Create an M3UA SAP](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-sap.md) \*\*[Create an M3UA Network](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-network.md) \*\*[Create an M3UA User Part](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-user-part.md) \*\*[Create an M3UA Peer Signaling Process](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-peer-signalling-process.md) \*\* Remote type: SGP \*\*\*Remote IP/Port for M3UA of SGP \*\*[Create an M3UA Peer Server](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-peer-server.md) \*\* In this use case, Two peer servers are needed: one local and one remote \*\*[Create an M3UA Route](/configuration/web-portal-3-3/protocol-stack/sccp-tcap/creating-an-m3ua-route.md) \*\* In this use case, two M3UA routes are needed: \*\*\*Local Route: Psrv, opc111, Local peer server, M3UA Userpart, subservice=NONE \*\*\*Route towards SGP: Psrv, Remote peer server, dpc333, M3UA Userpart=NONE, subservice=NONE | \*[Configure an ISUP Stack](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-isup-stack.md) \*[Create an ISUP Network](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-isup-network.md) \*[Create an ISUP User Part](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-isup-user-part.md) \*[Create an ISUP Interface](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-isup-interface.md) \*[Create ISUP CIC Groups](/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-isup-cic-groups.md) | \*[Configure NAP](/other-pages/protocol-stacks-ss7/creating-a-nap-isup.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 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/other-pages/use-cases/use-case-configuring-tmedia-m3ua-asp-for-shared-point-code.md?ask=&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.