One-Way Trunk Group Architecture Sample Clauses

One-Way Trunk Group Architecture. 2.13.1 In this architecture, the Parties interconnect using two one-way trunk groups. One one-way trunk group carries SouthEast-originated local and intraLATA toll traffic destined for AT&T end-users. The other one-way trunk group carries AT&T-originated local and intraLATA toll traffic destined for SouthEast end-users. A third two-way trunk group is established for SouthEast’s originating and terminating Transit Traffic. This group carries intratandem Transit Traffic between SouthEast and Independent Companies, Interexchange Carriers, other CLECs and other network providers with which SouthEast desires interconnection and has the proper contractual arrangements. This group also carries SouthEast originated intertandem traffic transiting a single AT&T 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 One-Way Trunk Group Architecture is illustrated in Exhibit C.
Sample 1
AutoNDA by SimpleDocs
One-Way Trunk Group Architecture. In one-way trunk group architecture, the Parties interconnect using three separate trunk groups. A one-way trunk group provides Intratandem Access for PBT- originated Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic destined for BellSouth End Users. A second one-way trunk group carries BellSouth- originated Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic destined for PBT End-Users. A two-way trunk group provides Intratandem Access 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 Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic is transported on a separate single one-way trunk group terminating to PBT. 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 one-way trunk group architecture is illustrated in Exhibit C.
Sample 1
One-Way Trunk Group Architecture. In one-way trunk group architecture, the Parties interconnect using three separate trunk groups. A one-way trunk group provides Intratandem Access for TWTC-originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic destined for BellSouth End Users. A second one-way trunk group carries BellSouth-originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic destined for TWTC End-Users. A two-way trunk group provides Intratandem Access 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 Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic is transported on a separate single one-way trunk group terminating to TWTC. The LERG contains current routing and tandem serving arrangements. The one-way trunk group architecture is illustrated in Exhibit C. Version: 4Q04 Standard ICA 06/15/05
Sample 1
One-Way Trunk Group Architecture. In one-way trunk group architecture, the Parties interconnect using three (3) separate trunk groups. A one-way trunk group provides Intratandem Access for ComSouth-originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic destined for BellSouth end users. A second one-way trunk group carries BellSouth-originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic destined for ComSouth end users. A two-way trunk group provides Intratandem Access 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 Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic is transported on a separate single one-way trunk group terminating to ComSouth. The LERG contains current routing and tandem serving arrangements. The one-way trunk group architecture is illustrated in Exhibit C.
Sample 1

Related to One-Way Trunk Group Architecture

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Monitoring System In each case in which the Custodian has exercised delegated authority to place Assets with a Foreign Custodian, the Custodian shall establish a system, to re-assess or re-evaluate selected Foreign Custodians, at least annually in accordance with Rule 17f-5(c)(3).

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

  • Reverse Engineering The Customer must not reverse assemble or reverse compile or directly or indirectly allow or cause a third party to reverse assemble or reverse compile the whole or any part of the software or any products supplied as a part of the Licensed System.

  • Virus Management Transfer Agent shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within the Transfer Agent environment.

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

Time is Money Join Law Insider Premium to draft better contracts faster.