Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom Reconex decides to market its services, Verizon will be largely dependent on Reconex to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter provide the same number of trunks to terminate Local Traffic to Reconex as Reconex provides to terminate Local Traffic to Verizon. At Verizon’s discretion, when Reconex expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks Reconex suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to Reconex is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Reconex’s previous forecasts have proven to be reliable and accurate.
Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom Talk Unlimited decides to market its services, Verizon will be largely dependent on Talk Unlimited to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to Talk Unlimited as Talk Unlimited provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when Talk Unlimited expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks Talk Unlimited suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to Talk Unlimited is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Talk Unlimited’s previous forecasts have proven to be reliable and accurate.
Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom ATI decides to market its services, Verizon will be largely dependent on ATI to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to ATI as ATI provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when ATI expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks ATI suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to ATI is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and ATI’s previous forecasts have proven to be reliable and accurate.
Initial Forecasts/Trunking Requirements. Because BA’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom NorthPoint decides to market its services, BA will be largely dependent on NorthPoint to provide accurate trunk forecasts for both inbound (from BA) and outbound (from NorthPoint) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate Local Traffic to NorthPoint as NorthPoint provides to terminate Local Traffic to BA, unless NorthPoint expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks NorthPoint suggests; provided, however, that in all cases BA’s provision of the forecasted number of trunks to NorthPoint is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and NorthPoint’s previous forecasts have proven to be reliable and accurate.
Initial Forecasts/Trunking Requirements. Because BA’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom MFN decides to market its services, BA will be largely dependent on MFN to provide accurate trunk forecasts for both inbound (from BA) and outbound (from MFN) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate Local Traffic to MFN as MFN provides to terminate Local Traffic to BA, unless MFN expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks MFN suggests; provided, however, that in all cases BA’s provision of the forecasted number of trunks to MFN is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and MFN’s previous forecasts have proven to be reliable and accurate.
Initial Forecasts/Trunking Requirements. Because BA's --------------------------------------- trunking requirements will, at least during an initial period, be dependent on the customer segments and service segments within customer segments to whom MFS decides to market its services. BA will be largely dependent on MFS to provide accurate trunk forecasts for both inbound (from BA) and outbound (from MFS) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate local traffic to MFS as MFS provides to terminate local traffic to BA, unless MFS expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks MFS suggests. Upon the establishment of any new set of trunks for traffic from BA to MFS, BA will monitor traffic for ninety (90) days, and will, as necessary at the end of that period, either augment trunks or disconnect trunks, based on the application of reasonable engineering criteria to the actual traffic volume experienced. If, after such 90-day period, BA has determined that the trunks are not warranted by actual traffic volumes, then, on ten (10) days' written notice, BA may hold MFS financially responsible for such trunks retroactive to the start of the 90-day period until such time as they are justified by actual traffic volumes, based on the application of reasonable engineering criteria. To the extent that BA requires MFS to install trunks for delivery of traffic to BA. MFS may apply the same procedures with respect to BA's trunking requirements.
Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom ICG decides to market its services, Verizon will be largely dependent on ICG to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon may, as an initial matter provide the same number of trunks to terminate Reciprocal Compensation Traffic to ICG as ICG provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when ICG expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks ICG suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to ICG is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and ICG’s previous forecasts have proven to be reliable and accurate. Utilization of existing trunk groups, compared against the target utilization levels provided in Section 2.4.11, will be the criteria that Verizon will use to assess whether ICG’s previous forecasts were reliable and accurate. If, based on reasonable engineering criteria and capacity constraints, Verizon determines that any trunks in a trunk group are not warranted, Verizon may disconnect such trunks.
Initial Forecasts/Trunking Requirements. Because BA’s trunking requirements will, at least during an initial period, be dependent on the customer segments and service segments within customer segments to whom TCG decides to market its services, BA will be largely dependent on TCG to provide accurate trunk forecasts for both inbound (from BA) and outbound (from TCG) traffic. BA will, as an initial matter and upon request, provide the same number of trunks to terminate local traffic to TCG as TCG provides to terminate local traffic to BA, unless TCG expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, in which case BA will provide the number of trunks TCG suggests. Upon the establishment of any new set of trunks for traffic from BA to TCG, BA will monitor traffic for ninety (90) days, and will, as necessary at the end of that period, either augment trunks or disconnect trunks, based on the application of reasonable engineering criteria to the actual traffic volume experienced. If, after such initial 90-day period, BA has determined that any trunks in excess of four (4) T-1s are not warranted by actual traffic volumes, then, on ten (10) days’ written notice, BA may hold TCG financially responsible for such trunks (up to the Tariffed recurring and non-recurring rates therefor) in excess of four (4) T-1s retroactive to the start of the 90-day period until such time as they are justified by actual traffic volumes, based on the application of reasonable engineering criteria. Similarly, in the event TCG’s subsequent forecasts result in BA’s provision of trunks that are not warranted by actual traffic volumes over the 90-day period immediately following such forecast, BA may hold TCG financially responsible for all such unwarranted trunks (up to the Tariffed recurring and non-recurring rates therefor) retroactive to the start of the 90-day period until such time as they are justified by actual traffic volumes, based on the application of reasonable engineering criteria. In the event, however, BA establishes trunks that are fewer than the number of trunks suggested by TCG in the relevant and timely quarterly forecast and such failure results in a shortage of trunk capacity to handle the ensuing traffic from BA to TCG, BA shall not hold TCG financially responsible for any unwarranted trunks in the following quarter up to the number of forecasted but non-provisioned trunks that were warranted by actual traffi...
Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom Teleconex decides to market its services, Verizon will be largely dependent on Teleconex to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter provide the same number of trunks to terminate Local Traffic to Teleconex as Teleconex provides to terminate Local Traffic to Verizon. At Verizon’s discretion, when Teleconex expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks Teleconex suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to Teleconex is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Teleconex’s previous forecasts have proven to be reliable and accurate.
Initial Forecasts/Trunking Requirements. Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom Excel decides to market its services, Verizon will be largely dependent on Excel to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to Excel as Excel provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when Excel expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks Excel suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to Excel is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and Excel’s previous forecasts have proven to be reliable and accurate.
