T1, E1, and J1 interfaces
m (add category) |
|||
| (3 intermediate revisions by one user not shown) | |||
| Line 7: | Line 7: | ||
== Using BITS ports for signaling == | == Using BITS ports for signaling == | ||
| − | Starting with release 2.3 of [[Toolpack]], it is possible to convert unused BITS ports into [[Signaling_Ports|signaling ports]] in order to recover a channel on the primary STM-1 connection. | + | Starting with release 2.3 of [[Toolpack]], it is possible to convert unused BITS ports into [[Signaling_Ports|signaling ports]], with indices of 1 and 0 respectively, in order to recover a channel on the primary STM-1 connection. |
However, the converted ports will be used as trunks, and not as clocking sources. | However, the converted ports will be used as trunks, and not as clocking sources. | ||
| + | |||
| + | [[Category:RevisionV2]] | ||
Latest revision as of 09:18, 4 February 2011
The Tmedia TMG3200 and Tdev TMP6400 TDM hardware adapters for T1, E1, and J1 lines provide for up to 64 lines. It is important that you verify the TDM module installed in your Tmedia unit.
For each T1/E1/J1 line that the Tmedia unit will use, a line interface with a related line service is configured in a one-to-one relationship. The configuring of the line interface activates the hardware and the line service is configured to transport traffic and signaling payload. A conceptual image is shown below:
Using BITS ports for signaling
Starting with release 2.3 of Toolpack, it is possible to convert unused BITS ports into signaling ports, with indices of 1 and 0 respectively, in order to recover a channel on the primary STM-1 connection. However, the converted ports will be used as trunks, and not as clocking sources.
