Common use of Trunking Requirements Clause in Contracts

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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 4.3.2 Pathnet shall make available to GTE trunks over which GTE shall terminate to end- users of NENPathnet-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 4.3.3 Pathnet and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Pathnet 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 Pathnet to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Pathnet desires to have any IXCs originate or terminate switched access traffic to or from NENPathnet, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Pathnet 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 NENPathnet. If the IXC subsequently indicates that it does not want the traffic routed to or from NENPathnet, GTE will not route the traffic. 4.3.3.1 4.3.3.1. Each Party agrees to route traffic only over the proper jurisdictional trunk group. 4.3.3.2 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 directly subtend the access tandem. 4.3.3.3 4.3.3.3. Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 local traffic or either Party may elect to provision its own one-way trunks for delivery of Local Traffic 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 4.3.2 DTI shall make available to GTE trunks over which GTE shall terminate to end- end users of NENDTI-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 DTI and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN DTI 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 DTI to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN DTI desires to have any IXCs Interexchange Carriers (IC) originate or terminate switched access traffic to or from NENDTI, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN to DTI will arrange for such IXC IC to issue an ASR to GTE to direct instructing GTE to route such traffic over the trafficappropriate IC trunk group. If Until GTE does not receive an ASR from the IXCreceives and processes such ASR, 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 trafficbe routed. 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic local traffic over Switched Access Service trunks. 4.3.4 DTI and GTE will reciprocally provide Percent Local Usage (PLU) factors to each other on a quarterly basis to identify the proper jurisdiction of each call type that is carried over the required trunks. 4.3.5 Reciprocal traffic exchange arrangement trunk connections shall be made at a DS-1 or multiple DS-1 xxxxx, XX-0, (XONET where technically available) and shall be jointly-engineered to an objective P.01 grade of service. 4.3.6 DTI and GTE agree to use diligent efforts to develop and agree on a Joint Interconnection Grooming Plan prescribing standards to ensure that the reciprocal traffic exchange arrangement trunk groups are maintained at consistent P.01 or better grades of service. Such plan shall also include mutually-agreed upon default standards for the configuration of all segregated trunk groups. 4.3.7 Signaling System 7 (SS7) Common Channel Signaling will be used to the extent that such technology is available. 4.3.8 The Parties agree to offer and provide to each other B8ZS Extended Superframe Format ("ESF") facilities, where available, capable of voice and data traffic transmission. 4.3.9 The Parties will support intercompany 64kbps clear channel where available.

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 NEWSOUTH shall make available to GTE trunks over which GTE shall terminate to end- end-users of NENNEWSOUTH-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 NEWSOUTH and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN NEWSOUTH 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 NEWSOUTH to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN NEWSOUTH desires to have any IXCs originate or terminate switched access traffic to or from NENNEWSOUTH, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN NEWSOUTH 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 NENNEWSOUTH. If the IXC subsequently indicates that it does not want the traffic routed to or from NENNEWSOUTH, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 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 4.3.2 Spectrum shall make available to GTE trunks over which GTE shall terminate to end- end users of NENSpectrum-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 Spectrum and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Spectrum 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 Spectrum to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Spectrum desires to have any IXCs IXC originate or terminate switched access traffic to or from NENSpectrum, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Spectrum to arrange for such IXC to issue an ASR a Letter of Authorization (LOA) to GTE to direct GTE to route the traffic. If GTE does not receive an ASR LOA from the IXC, GTE will initially route the switched access traffic between the IXC and NENSpectrum. If the IXC subsequently indicates that it does not want the traffic routed to or from NENSpectrum, 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 switch for those publicly-dialable NXX Codes served by that switch or, when delivered to a GTE tandem, end offices that directly subtend the access interconnect with that tandem or to those wireless service providers other Local Providers that directly subtend the access interconnect with that tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic local traffic over Switched Access Service trunks. 4.3.4 The Parties will work together to establish high usage end-office trunk groups sufficient to handle the greater of the actual or reasonably forecasted traffic volumes between Spectrum end office and a GTE end office. 4.3.5 Spectrum will provide PLU factors on a quarterly basis to identify the proper jurisdiction (local or non-local) of each call type that is carried over the local interconnection trunks. If these percentages are not received quarterly, the Parties shall use the last previous reported percentages. The PLU factor is identified on Appendix C. 4.3.6 Reciprocal traffic exchange arrangement trunk connections shall be made at a DS-1 or multiple XX-0 xxxxx, XX-0, (SONET where technically available) and shall be jointly- engineered to an objective P.01 grade of service. 4.3.7 Spectrum and GTE agree to use diligent efforts to develop and agree on a Joint Interconnection Grooming Plan prescribing standards to ensure that the reciprocal traffic exchange arrangement trunk groups are maintained at consistent P.01 or better grades of service. Such plan shall also include mutually-agreed upon default standards for the configuration of all segregated trunk groups. 4.3.8 SS7 Common Channel Signaling will be used to the extent that such technology is available. If SS7 is not available, Multi-Frequency Signaling (MF) will be used as specified. 4.3.9 The Parties agree to offer and provide to each other B8ZS Extended Superframe Format ("ESF") facilities, where available, capable of voice and data traffic transmission. 4.3.10 The Parties will support intercompany 64kbps clear channel where available.

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. 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/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-one- way trunks, that Party will be responsible for its own expenses associated with the trunks. 4.3.2. NEN 4.3.2 DSL shall make available to GTE trunks over which GTE shall terminate to end- end users of NENDSL-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 DSL and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN DSL 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 DSL to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN DSL desires to have any IXCs originate or terminate switched access traffic to or from NENDSL, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN DSL 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 NENDSL. If the IXC subsequently indicates that it does not want the traffic routed to or from NENDSL, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 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 4.3.2 Nextel shall make available to GTE trunks over which GTE shall terminate to end- end users of NENNextel-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 Nextel and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Nextel 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 Nextel to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Nextel desires to have any IXCs IXC originate or terminate switched access traffic to or from NENNextel, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Nextel to arrange for such IXC to issue an ASR a Letter of Authorization (LOA) to GTE to direct GTE to route the traffic. If GTE does not receive an ASR LOA from the IXC, GTE will initially route the switched access traffic between the IXC and NENNextel. If the IXC subsequently indicates that it does not want the traffic routed to or from NENNextel, 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 other Local Providers that directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic local traffic over Switched Access Service trunks. 4.3.4 The Parties will work together to establish high usage end-office trunk groups sufficient to handle the greater of the actual or reasonably forecasted traffic volumes between Nextel end office and a GTE end office. 4.3.5 Nextel will provide PLU factors on a quarterly basis to identify the proper jurisdiction (local or non-local) of each call type that is carried over the local interconnection trunks. If these percentages are not received quarterly, the Parties shall use the last previous reported percentages. The PLU factor is identified on Appendix C . 4.3.6 Reciprocal traffic exchange arrangement trunk connections shall be made at a DS-1 or multiple XX-0 xxxxx, XX-0, (SONET where technically available) and shall be jointly- engineered to an objective P.01 grade of service. 4.3.7 Nextel and GTE agree to use diligent efforts to develop and agree on a Joint Interconnection Grooming Plan prescribing standards to ensure that the reciprocal traffic exchange arrangement trunk groups are maintained at consistent P.01 or better grades of service. Such plan shall also include mutually-agreed upon default standards for the configuration of all segregated trunk groups. 4.3.8 SS7 Common Channel Signaling will be used to the extent that such technology is available. If SS7 is not available, Multi-Frequency Signaling (MF) will be used as specified. 4.3.9 The Parties agree to offer and provide to each other B8ZS Extended Superframe Format ("ESF") facilities, where available, capable of voice and data traffic transmission. 4.3.10 The Parties will support intercompany 64kbps clear channel where available.

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-one- way trunks, that Party will be responsible for its own expenses associated with the trunks. 4.3.2. NEN US Dial Tone shall make available to GTE trunks over which GTE shall terminate to end- end-users of NENUS Dial Tone-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 US Dial Tone and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN US Dial Tone 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 US Dial Tone to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN US Dial Tone desires to have any IXCs originate or terminate switched access traffic to or from NENUS Dial Tone, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN US Dial Tone 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 NENUS Dial Tone. If the IXC subsequently indicates that it does not want the traffic routed to or from NENUS Dial Tone, 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-publicly- dialable NXX Codes served by end offices that directly subtend the access tandem or to those wireless service providers that directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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 TOUCHTONE shall make available to GTE trunks over which GTE shall terminate to end- end-users of NENTOUCHTONE-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 TOUCHTONE and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN TOUCHTONE 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 TOUCHTONE to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN TOUCHTONE desires to have any IXCs originate or terminate switched access traffic to or from NENTOUCHTONE, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN TOUCHTONE 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 NENTOUCHTONE. If the IXC subsequently indicates that it does not want the traffic routed to or from NENTOUCHTONE, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 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 4.3.2 Mountaineer shall make available to GTE trunks over which GTE shall terminate to end- end users of NENMountaineer-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 Mountaineer and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Mountaineer 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 Mountaineer to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Mountaineer desires to have any IXCs Interexchange Carriers (IXC) originate or terminate switched access traffic to or from NENMountaineer, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Mountaineer to arrange for such IXC to issue an ASR a Letter of Authorization (LOA) to GTE to direct GTE to route the traffic. If GTE does not receive an ASR LOA from the IXC, GTE will initially route the switched access traffic between the IXC and NENMountaineer. If the IXC subsequently indicates that it does not want the traffic routed to or from NENMountaineer, 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 other Local Providers that directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic local traffic over Switched Access Service trunks. 4.3.4 Mountaineer will provide PLU factors on a quarterly basis to identify the proper jurisdiction (local or non-local) of each call type that is carried over the local interconnection trunks. If these percentages are not received quarterly, the Parties shall use the last previous reported percentages. The PLU factor is identified on Appendix C. 4.3.5 Reciprocal traffic exchange arrangement trunk connections shall be made at a DS-1 or multiple XX-0 xxxxx, XX-0, (SONET where technically available) and shall be jointly- engineered to an objective P.01 grade of service. 4.3.6 Mountaineer and GTE agree to use diligent efforts to develop and agree on a Joint Interconnection Grooming Plan prescribing standards to ensure that the reciprocal traffic exchange arrangement trunk groups are maintained at consistent P.01 or better grades of service. Such plan shall also include mutually-agreed upon default standards for the configuration of all segregated trunk groups. 4.3.7 Signaling System 7 (SS7) Common Channel Signaling will be used to the extent that such technology is available. SS7 Common Channel Signaling will be used to the extent that such technology is available. If SS7 is not available, Multi-Frequency Signaling (MF) will be used as specified. 4.3.8 The Parties agree to offer and provide to each other B8ZS Extended Superframe Format ("ESF") facilities, where available, capable of voice and data traffic transmission. 4.3.9 The Parties will support intercompany 64kbps clear channel where available.

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 Omniplex shall make available to GTE trunks over which GTE shall terminate to end- end-users of NENOmniplex-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 Omniplex and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Omniplex 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 Omniplex to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Omniplex desires to have any IXCs originate or terminate switched access traffic to or from NENOmniplex, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Omniplex 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 NENOmniplex. If the IXC subsequently indicates that it does not want the traffic routed to or from NENOmniplex, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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-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 MFN shall make available to GTE trunks over which GTE shall terminate to end- end-users of NENMFN-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 MFN and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN MFN 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 MFN to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN MFN desires to have any IXCs originate or terminate switched access traffic to or from NENMFN, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN MFN 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 NENMFN. If the IXC subsequently indicates that it does not want the traffic routed to or from NENMFN, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 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 4.3.2 Nextel shall make available to GTE trunks over which GTE shall terminate to end- end users of NENNextel-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 Nextel and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Nextel 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 Nextel to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Nextel desires to have any IXCs IXC originate or terminate switched access traffic to or from NENNextel, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Nextel to arrange for such IXC to issue an ASR a Letter of Authorization (LOA) to GTE to direct GTE to route the traffic. If GTE does not receive an ASR LOA from the IXC, GTE will initially route the switched access traffic between the IXC and NENNextel. If the IXC subsequently indicates that it does not want the traffic routed to or from NENNextel, 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 other Local Providers that directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic local traffic over Switched Access Service trunks. 4.3.4 The Parties will work together to establish high usage end-office trunk groups sufficient to handle the greater of the actual or reasonably forecasted traffic volumes between Nextel end office and a GTE end office. 4.3.5 Nextel will provide PLU factors on a quarterly basis to identify the proper jurisdiction (local or non-local) of each call type that is carried over the local interconnection trunks. If these percentages are not received quarterly, the Parties shall use the last previous reported percentages. The PLU factor is identified on Appendix C. 4.3.6 Reciprocal traffic exchange arrangement trunk connections shall be made at a DS-1 or multiple XX-0 xxxxx, XX-0, (SONET where technically available) and shall be jointly- engineered to an objective P.01 grade of service. 4.3.7 Nextel and GTE agree to use diligent efforts to develop and agree on a Joint Interconnection Grooming Plan prescribing standards to ensure that the reciprocal traffic exchange arrangement trunk groups are maintained at consistent P.01 or better grades of service. Such plan shall also include mutually-agreed upon default standards for the configuration of all segregated trunk groups. 4.3.8 SS7 Common Channel Signaling will be used to the extent that such technology is available. If SS7 is not available, Multi-Frequency Signaling (MF) will be used as specified. 4.3.9 The Parties agree to offer and provide to each other B8ZS Extended Superframe Format ("ESF") facilities, where available, capable of voice and data traffic transmission. 4.3.10 The Parties will support intercompany 64kbps clear channel where available.

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. 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 4.3.2 USX shall make available to GTE trunks over which GTE shall terminate to end- end users of NENUSX-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 USX and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN USX 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 USX to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN USX desires to have any IXCs originate or terminate switched access traffic to or from NENUSX, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN USX 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 NENUSX. If the IXC subsequently indicates that it does not want the traffic routed to or from NENUSX, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 4.3.2 NorthPoint shall make available to GTE trunks over which GTE shall terminate to end- end-users of NENNorthPoint-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 4.3.3 NorthPoint and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN NorthPoint 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 NorthPoint to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN NorthPoint desires to have any IXCs originate or terminate switched access traffic to or from NENNorthPoint, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN NorthPoint 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 NENNorthPoint. If the IXC subsequently indicates that it does not want the traffic routed to or from NENNorthPoint, GTE will not route the traffic. 4.3.3.1 i. Each Party agrees to route traffic only over the proper jurisdictional trunk group. 4.3.3.2 ii. 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 directly subtend the access tandem. 4.3.3.3 iii. Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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 NAS shall make available to GTE trunks over which GTE shall terminate to end- users of NENNAS-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 NAS and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN NAS 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 NAS to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN NAS desires to have any IXCs originate or terminate switched access traffic to or from NENNAS, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN NAS 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 NENNAS. If the IXC subsequently indicates that it does not want the traffic routed to or from NENNAS, 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 directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic over Switched Access Service trunks.

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. 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 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 4.3.2 Nextel shall make available to GTE trunks over which GTE shall terminate to end- end users of NENNextel-provided Exchange Services, Local Traffic and intraLATA toll or optional EAS traffic originated from end-end users of GTE-provided Exchange Service. 4.3.3. NEN 4.3.3 Nextel and GTE shall, where applicable, make reciprocally available, by mutual agreement, the required trunk groups to handle different traffic types. NEN Nextel 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 Nextel to originate and terminate interLATA calls and to provide Switched Access Service to IXCs. To the extent NEN Nextel desires to have any IXCs IXC originate or terminate switched access traffic to or from NENNextel, using jointly provided switched access facilities routed through a GTE access tandem, it is the responsibility of NEN Nextel to arrange for such IXC to issue an ASR a Letter of Authorization (LOA) to GTE to direct GTE to route the traffic. If GTE does not receive an ASR LOA from the IXC, GTE will initially route the switched access traffic between the IXC and NENNextel. If the IXC subsequently indicates that it does not want the traffic routed to or from NENNextel, 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 other Local Providers that directly subtend the access tandem. 4.3.3.3 Neither party shall route Switched Access Service traffic over local interconnection trunks, or Local Traffic local traffic over Switched Access Service trunks. 4.3.4 The Parties will work together to establish high usage end-office trunk groups sufficient to handle the greater of the actual or reasonably forecasted traffic volumes between Nextel end office and a GTE end office. 4.3.5 Nextel will provide PLU factors on a quarterly basis to identify the proper jurisdiction (local or non-local) of each call type that is carried over the local interconnection trunks. If these percentages are not received quarterly, the Parties shall use the last previous reported percentages. The PLU factor is identified on Appendix C. 4.3.6 Reciprocal traffic exchange arrangement trunk connections shall be made at a DS-1 or multiple DS-1 level, DS-3, (SONET where technically available) and shall be jointly- engineered to an objective P.01 grade of service. 4.3.7 Nextel and GTE agree to use diligent efforts to develop and agree on a Joint Interconnection Grooming Plan prescribing standards to ensure that the reciprocal traffic exchange arrangement trunk groups are maintained at consistent P.01 or better grades of service. Such plan shall also include mutually-agreed upon default standards for the configuration of all segregated trunk groups. 4.3.8 SS7 Common Channel Signaling will be used to the extent that such technology is available. If SS7 is not available, Multi-Frequency Signaling (MF) will be used as specified. 4.3.9 The Parties agree to offer and provide to each other B8ZS Extended Superframe Format ("ESF") facilities, where available, capable of voice and data traffic transmission. 4.3.10 The Parties will support intercompany 64kbps clear channel where available.