Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, CBB shall provide a new or revised traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide when CBB develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) CBB plans to deploy a new switch; (b) CBB plans to implement a new POI or network architecture;
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, Carrier shall provide a new or revised traffic forecast when Carrier develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Carrier plans to deploy a new switch; (b) Carrier plans to implement a new POI or network architecture; (c) Carrier plans to rearrange its network; (d) Carrier expects a significant change in interconnection traffic volume; or (e) other activities that are reflected by a significant increase or decrease in trunking demand. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, DISH Wireless shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when DISH Wireless develops plans or becomes aware of information that will materially a new or revised forecast include, but are not limited to: (i) DISH Wireless plans to deploy a new switch; (ii) DISH Wireless plans to implement a new POI or network architecture; (iii) DISH Wireless plans to rearrange its network; (iv) DISH Wireless plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (v) DISH Wireless expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks and/or Interconnection Trunk groups.
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, ENT shall provide a new or revised traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide when ENT develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) ENT plans to deploy a new switch; (b) ENT plans to implement a new POI or network architecture;
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, Emergency shall provide a new or revised traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide when Emergency develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (i) Emergency plans to deploy a new switch; (ii) Emergency plans to implement a new POI or network architecture; (iii) Emergency plans to rearrange its network;
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, PBX shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when PBX develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) PBX plans to deploy a new switch; (b) PBX plans to implement a new POI or network architecture;
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, API shall provide a new or revised traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide when API develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) API plans to deploy a new switch; (b) API plans to implement a new POI or network architecture;
Ongoing Trunk Forecast Requirements. Since the Parties have a longstanding traffic history, on an as needed basis but no less frequently than semi-annually, the Parties shall meet and provide to each other a good faith trunk forecast of the number of End Office and Tandem Interconnection Trunks that will be needed during the ensuing two (2) year period for the exchange of traffic between FairPoint and Verizon. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks and/or Interconnection Trunk groups.
Ongoing Trunk Forecast Requirements. Where the Parties have already established interconnection in a LATA, ADSC shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when ADSC develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) ADSC plans to deploy a new switch; (b) ADSC plans to implement a new POI or network architecture; (c) ADSC plans to rearrange its network; (d) ADSC plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group;
