Trunking Requirements. The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.
Trunking Requirements. The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards, state requirements and standards provided for in the ROC and incorporated herein by reference.
Trunking Requirements. In accordance with Article III, Section 12, it will be necessary for the Parties to have met and agreed on trunking availability and requirements in order for the Parties to begin exchange of traffic.
4.3.1. The Parties agree to establish trunk groups of sufficient capacity from the interconnecting facilities such that trunking is available to any switching center designated by either Party, including end offices, tandems, 911 routing switches, and directory assistance/operator service switches. The Parties will mutually agree where one-way or two-way trunking will be available. The Parties may use two-way trunks for delivery of Local Traffic or either Party may elect to provision its own one-way trunks for delivery of Local Traffic to the other Party. If a Party elects to provision its own one-way trunks, that Party will be responsible for its own expenses associated with the trunks.
4.3.2. NEN shall make available to GTE trunks over which GTE shall terminate to end- users of NEN-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-users of GTE-provided Exchange Service.
4.3.3. NEN and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN and GTE will support the provisioning of trunk groups that carry combined or separate Local Traffic and intraLATA toll and optional EAS traffic. GTE requires separate trunk groups from NEN to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN desires to have any IXCs originate or terminate switched access traffic to or from NEN, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN to arrange for such IXC to issue an ASR to GTE to direct GTE to route the traffic. If GTE does not receive an ASR from the IXC, GTE will initially route the switched access traffic between the IXC and NEN. If the IXC subsequently indicates that it does not want the traffic routed to or from NEN, GTE will not route the traffic.
4.3.3.1 Each Party agrees to route traffic only over the proper jurisdictional trunk group.
4.3.3.2 Each Party shall only deliver traffic over the local interconnection trunk groups to the other Party's access tandem for those publicly-dialable NXX Codes served by end offices that directly subtend the access tandem or to those wireless service providers that direct...
Trunking Requirements. 4.3.1 The Parties shall establish and maintain trunks over which each Party shall terminate to its end users the Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated by the end users of the other Party.
4.3.2 The Parties agree to establish trunk groups of sufficient capacity from the interconnecting facilities such that trunking is available to any switching center designated by either Party, including end offices, tandems, 911 routing switches, and directory assistance/operator service switches. The Parties will mutually agree where one-way or two-way trunking will be available. The Parties may use two-way trunks for delivery of local traffic or either Party may elect to provision its own one-way trunks for delivery of local traffic to the other Party. If a Party elects to provision its own one-way trunks, that Party will be responsible for its own expenses associated with the trunks.
4.3.3 XXX and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. XXX and GTE will support the provisioning of trunk groups that carry combined or separate Local Traffic and intraLATA toll and optional EAS traffic. The Parties shall establish and maintain separate trunk groups for the following: (1) to originate and terminate interLATA calls when either Party is acting as an IXC and ordering switched access service from the other Party; (2) to provide joint Switched Access Service to IXCs; and (3) for other types of traffic as the Parties mutually agree. To the extent XXX desires to have any IXC originate or terminate traffic to XXX using jointly provided switched access facilities routed through a GTE tandem, it is the responsibility of XXX to arrange for such IXC to issue an ASR to GTE to direct GTE to route the traffic. If GTE does not receive an ASR from the IXC, GTE will initially route the switched access traffic between the IXC and XXX. If the IXC subsequently indicates that it does not want the traffic routed to or from XXX, GTE will not route the traffic to or from XXX.
4.3.3.1 Each Party agrees to route traffic only over the proper jurisdictional trunk group.
4.3.3.2 Each Party shall only deliver traffic over the local interconnection trunk groups to the other Party's tandem or switch performing a tandem function for those publicly-dialable NXX Codes served by end offices that directly subtend the tandem or switch or to those LECs or wireless se...
Trunking Requirements. To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below.
3.1 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates.
3.1.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA only, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch.
3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call.
3.2 The Parties’ general preference would be to establish an OS/DA demarcation point at the AT&T OS/DA switch in that LATA , but the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of engineering and location-specific factors which include, but are not limited to,
3.2.1 The size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic
3.2.2 Whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA
3.2.3 Whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms.
3.3 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation point.
3.4 General OS/DA Trunking Requirements
3.4.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk g...
Trunking Requirements. IV-4 4.5
Trunking Requirements. 4.2.1 The Parties shall meet and agree on trunking availability and requirements in order for the Parties to begin exchange of traffic. Special Access and/or CLEC Dedicated Transport: CenturyTel will charge special access and/or switched access rates from the applicable CenturyTel access tariff. Charges will be reduced to reflect the proportionate share of the facility that is used for transport of local traffic originated by CenturyTel. The Parties will negotiate an initial factor representative of the proportionate share of the facilities as set forth in Section 3 of Appendix A. This factor will be updated quarterly in like manner or as the Parties otherwise agree. The Parties agree to establish trunk groups of sufficient capacity from the interconnecting facilities such that trunking is available to the switching center in the local calling area/EAS where Sprint does business, including end office, tandem, and 911 routing switches. The Parties will mutually agree where one-way or two-way trunking will be available. The Parties may use two-way trunks for delivery of Local Traffic or either Party may elect to provision its own one-way trunks for delivery of Local Traffic to the other Party. The Parties will mutually share the cost of the two-way trunking network arrangement unless a Party elects to provision its own one-way trunks for Local Traffic, then that Party will be responsible for its own expenses associated with the trunks.
4.2.2 Sprint and CenturyTel shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. Sprint and CenturyTel will support the provisioning of trunk groups that carry combined or separate Local Traffic. CenturyTel requires separate trunk groups from Sprint to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent Sprint desires to have any IXCs originate or terminate switched access traffic to or from Sprint, using jointly provided switched access facilities routed through a CenturyTel access tandem, it is the responsibility of Sprint to arrange for such IXC to issue an ASR to CenturyTel to direct CenturyTel to route the traffic. If CenturyTel does not receive an ASR from the IXC, CenturyTel will initially route the switched access traffic between the IXC and Sprint. If the IXC subsequently indicates that it does not want the traffic routed to or from Sprint, CenturyTel will not route the traffic.
4.2.2.1 ...
Trunking Requirements. In accordance with Article I, Section 3.4, it will be necessary for the Parties to have met and agreed on trunking availability and requirements in order for the Parties to begin exchange of traffic.
Trunking Requirements. IV-5 4.4 Network Redesigns Initiated by GTE . . . . . . . . . . . . . . . . . . . . . . . . . IV-6
Trunking Requirements. 7.2.2.9.1 The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards, state requirements and standards provided for in the ROC and incorporated herein by reference.
7.2.2.9.1.1 Qwest shall provide to CLEC monthly reports on all Interconnection trunk groups and quarterly reports on all interoffice trunk groups carrying EAS/local traffic between Qwest tandem switches and Qwest end office switches. The reports will contain busy hour traffic data, including but not limited to, overflow and the number of trunks in each trunk group.
