> 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/transmission-and-lines/signaling-ports.md). # Signaling Ports This release of Toolpack, when used with a Tdev or Tmedia device equipped with DS3/STM-1 connections, enables you to convert the BITS ports on the Tmedia or Tdev DS3/STM-1 expansion boards in to E1/T1/J1 signaling ports, allowing you to make even greater use of your DS-3/STM-1 communications capacity. Once configured as such, the BITS port behaves just like any other signaling trunk or line interface. Therefore you can use the full capacity of the DS3 or STM-1 links for calls while signaling is handled via the former BITS ports. It is important to note that the two BITS ports can be used either for BITS interfaces or for normal T1/E1/J1 trunks; one cannot have one port in signaling mode and the other in BITS mode. This enhancement enables you to forgo the use a multiplexer (MUX) device in front of the TelcoBridges hardware to separate the signaling links from the DS-3/STM-1 interface. Configuration and monitoring of this new feature is performed through Toolpack Web Portal.' ### Prerequisites This feature only works with DS-3 or STM-1 expansion boards for the Tdev [TMP6400](https://telcobridges.com/products/development-platforms-tdev/tmp6400-tdev-voip-gateway-development-platform/) or Tmedia [TMG3200](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg3200/) devices. If you do not have one of these expansion boards, you do not have any ports to configure. The BITS ports can be connected via any standard E1/T1 cable using a RJ48 interface. ### Steps You access the Signaling ports function via the Toolpack web portal. After logging into the Toolpack web portal with your web browser, do the following steps to convert both BITS ports for signaling purposes.*'*' * The first step is to configure the new trunks as signaling ports. To do this, go to **Global > Configurations > Hardware > TDM Interfaces > Line Interfaces**. See figure 3 for a sample. * Select **Create New Line Interface**. * Select type as E1/T1 (not DS3 or STM-1) * Select Local Index 0 (for port 1) or 1 (for port 2) **Figure 3: Line interfaces (sample)** ![signaling ports sub menu](https://docs.telcobridges.com/w/images/f/f0/Signaling-ports-sub-menu.jpg) * The next step is to configure SS7 (MTP2) signaling just as you would do for any interface. Go to **Global > Configurations > Hardware > Signaling > MTP2**. There you can add the MTP2 link to the MTP3 configuration and so on. * Finally, you need to configure and validate the clocking on those two new trunks. Clocking can be set on any line service, be it the signaling ports or the trunks on the DS3 / STM-1 link. You configure this via **Global > Configurations > Hardware > Clocking**. --- # 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/transmission-and-lines/signaling-ports.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.