DS3 interfaces - Revision history

Luc Morissette at 20:31, 11 August 2016

2016-08-11T20:31:17Z

Luc Morissette: Updated page

2016-08-11T20:30:50Z

Updated page

Cbilodeau: add category

2011-02-04T14:18:32Z

add category

Allyntree at 21:11, 18 November 2009

2009-11-18T21:11:01Z

Ktrueman: initial content

2009-07-10T18:09:00Z

initial content

New page

The Tmedia [[TMG3200]] and Tdev [[TMP6400]] TDM hardware adapter provides an interface of up to 3 DS3 lines.

For each DS3 line that the Tmedia or Tdev device will use, a line interface with related line services are configured. The DS3 interface can be configured in a one-to-one relationship with DS3 line services; however, unlike a T1/E1/J1 interface, the DS3 line service can be configured to contain subordinate child line services carrying lower bandwidth payload. A conceptual image is shown below:

[[Image:Schematic-DS3-interfaces.jpg|575px]]

← Older revision		Revision as of 20:31, 11 August 2016
Line 1:		Line 1:
−	The Tmedia [[TMG3200]] and Tdev [[TMP6400]] TDM hardware adapter provides an interface of up to 3 DS3 lines.	+	The Tmedia [[TMG3200]], [[TMG7800]] and Tdev [[TMP6400]] TDM hardware adapter provides an interface of up to 3 DS3 lines.

	For each DS3 line that the Tmedia or Tdev device will use, a line interface with related line services are configured. The DS3 interface can be configured in a one-to-one relationship with DS3 line services; however, unlike a T1/E1/J1 interface, the DS3 line service can be configured to contain subordinate child line services carrying lower bandwidth payload. A conceptual image is shown below:		For each DS3 line that the Tmedia or Tdev device will use, a line interface with related line services are configured. The DS3 interface can be configured in a one-to-one relationship with DS3 line services; however, unlike a T1/E1/J1 interface, the DS3 line service can be configured to contain subordinate child line services carrying lower bandwidth payload. A conceptual image is shown below:

@@ Line 8: / Line 8: @@
 == 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]], with indices of 1 and 0 respectively, in order to recover a channel on the primary DS3 connection.
 [[Category:RevisionV2]]

← Older revision		Revision as of 14:18, 4 February 2011
Line 9:		Line 9:
	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 DS3 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 DS3 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]]

← Older revision		Revision as of 21:11, 18 November 2009
Line 5:		Line 5:

	[[Image:Schematic-DS3-interfaces.jpg\|575px]]		[[Image:Schematic-DS3-interfaces.jpg\|575px]]
		+
		+	== 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]], with indices of 1 and 0 respectively, in order to recover a channel on the primary DS3 connection.
		+	However, the converted ports will be used as trunks, and not as clocking sources.