> 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/host-application-requirements.md). # Host application requirements The Tmedia signaling architecture is built for high performance throughput in terms of “calls per second”. To achieve these goals, the [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) stack located on the Tmedia hardware processes the MTP1-3/ISUP protocol layers and provides alarm and event notifications to the host application for multiple calls in parallel. For ISUP, each call is attached to a specific circuit ID handle (which is in turn related to a specific network/[OPC](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/opc/README.md)/[DPC](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/dpc/README.md)/variant/[CIC](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/circuit-identification-code/README.md)). This ID (provided by the application upon circuit allocation) is included in every call-related event to allow the user application to know to which call it refers to. Thus, the application will receive thousands of events, each referring to different calls. Since a complete ISUP call is achieved by processing multiple SS7 messages (IAM, ACM, ANM, REL, RLC, etc), multiple messages are required for a call to reach the active state and then to be released. These message flows, explained here, need to be controlled by the host application. Only the application possesses the information to accept/route calls according to call information (numbers, characteristics, billing, etc). Therefore, the application plays an important role in the performance of the stack. If the application is not optimized or poorly designed (e.g. synchronous), decent performance will not be achieved. --- # 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/host-application-requirements.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.