One-Way Trunk Group Architecture Sample Clauses
The One-Way Trunk Group Architecture clause defines the structure and operational rules for telecommunications trunk groups that carry traffic in only one direction between two points. In practice, this means that calls or data transmissions are routed from an originating location to a terminating location, but not vice versa on the same trunk group; separate trunk groups are established for each direction. This arrangement is commonly used to manage network traffic efficiently and to simplify troubleshooting by clearly delineating the flow of communications. The core function of this clause is to ensure organized and predictable routing of telecommunications traffic, thereby reducing confusion and potential congestion in network operations.
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.
One-Way Trunk Group Architecture. 2.6.2.3.1 In this architecture, the Parties interconnect using two one-way trunk groups. One one-way trunk group carries Knology-originated local and intraLATA toll traffic destined for BellSouth end-users. The other one-way trunk group carries BellSouth-originated local and intraLATA toll traffic destined for Knology end-users. A third two-way trunk group is 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 One-Way Trunk Group Architecture is illustrated in Exhibit C.
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.
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