Two-Way Trunk Group Architecture Sample Clauses

Two-Way Trunk Group Architecture. The two-way trunk group Architecture establishes one (1) two-way trunk group to provide Intratandem Access for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between ComSouth and BellSouth. In addition, a separate two-way transit trunk group must be established for ComSouth’s originating and terminating Transit Traffic. This trunk group carries Transit Traffic between ComSouth and ICOs, IXCs, other CLECs, CMRS providers that have a Meet Point Billing arrangement with BellSouth, and other network providers with which ComSouth exchanges traffic. This trunk group also carries ComSouth originated Transit Traffic transiting a single BellSouth Access Tandem destined to third party tandems such as an ICO tandem or other CLEC tandem. BellSouth originated traffic may, in order to prevent or remedy traffic blocking situations, be transported on a separate single one-way trunk group terminating to ComSouth. However, where ComSouth is responsive in a timely manner to BellSouth’s transport needs for its originated traffic, BellSouth originating traffic will be placed on the two-way Local Traffic trunk group carrying ISP-Bound Traffic and IntraLATA Toll Traffic. The LERG contains current routing and tandem serving arrangements. The two-way trunk group architecture is illustrated in Exhibit D.
Sample 1Sample 2
AutoNDA by SimpleDocs
Two-Way Trunk Group Architecture. The two-way trunk group Architecture establishes one two-way trunk group to provide Intratandem Access for the exchange of Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic between PBT and BellSouth. In addition, a separate two-way transit trunk group must be established for PBT’s originating and terminating Transit Traffic. This trunk group carries Transit Traffic between PBT and Independent Companies, Interexchange Carriers, other CLECs, CMRS providers that have a Meet Point Billing arrangement with BellSouth, and other network providers with which PBT desires to exchange traffic. This trunk group also carries PBT originated Transit Traffic transiting a single BellSouth access tandem destined to third party tandems such as an Independent Company tandem or other CLEC tandem. BellSouth originated traffic may, in order to prevent or remedy traffic blocking situations, be transported on a separate single one-way trunk group terminating to PBT. However, where PBT is responsive in a timely Version 3Q03: 11/12/2003 manner to BellSouth’s transport needs for its originated traffic, BellSouth originating traffic will be placed on the two-way Local Traffic trunk group carrying ISP-bound Traffic and IntraLATA Toll Traffic. Other trunk groups for operator services, directory assistance, emergency services and intercept must be established pursuant to the applicable BellSouth tariff if service is requested. The LERG contains current routing and tandem serving arrangements. The two-way trunk group architecture is illustrated in Exhibit D.
Sample 1
Two-Way Trunk Group Architecture. 2.6.2.4.1 The Two-Way Trunk Group Architecture establishes one two-way trunk group to carry local and intraLATA toll traffic between Knology and BellSouth. In addition, a two-way transit trunk group must be established for Knology's originating and terminating Transit Traffic. This group carries intratandem Transit Traffic between Knology and Independent Companies, Interexchange Carriers, other CLECs and other network providers with which Knology desires interconnection and has the proper contractual arrangements. This group also carries Knology originated intertandem traffic transiting a single BellSouth access tandem destined to third party tandems such as an Independent Company tandem or other CLEC tandem. Other trunk groups for operator services, directory assistance, emergency services and intercept may be established if required. The LERG should be referenced for current routing and tandem serving arrangements. The Two-Way Trunk Group Architecture is illustrated in Exhibit D.
Sample 1
Two-Way Trunk Group Architecture. The two-way trunk group Architecture establishes one two-way trunk group to provide Intratandem Access for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between TWTC and BellSouth. In addition, a separate two-way transit trunk group must be established for TWTC’s originating and terminating Transit Traffic. This trunk group carries Transit Traffic between TWTC and Independent Companies, Interexchange Carriers, other CLECs, CMRS providers that have a Meet Point Billing arrangement with BellSouth, and other network providers with which TWTC exchanges traffic. This trunk group also carries TWTC originated Transit Traffic transiting a single BellSouth access tandem destined to third party tandems such as an Independent Company tandem or other CLEC tandem. BellSouth originated traffic may, in order to prevent or remedy traffic blocking situations, be transported on a separate single one-way trunk group terminating to TWTC. However, where TWTC is responsive in a timely manner to BellSouth’s transport needs for its originated traffic, BellSouth originating traffic will be placed on the two-way Local Traffic trunk group carrying ISP-Bound Traffic and IntraLATA Toll Traffic. The LERG contains current routing and tandem serving arrangements. The two-way trunk group architecture is illustrated in Exhibit D.
Sample 1

Related to Two-Way Trunk Group Architecture

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!