Two-Way Trunk Group Architecture Sample Clauses

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
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 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
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 (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 1

Related to Two-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)

  • 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.

  • 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.

  • 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).

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • 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.

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