Common use of Trunk Design Blocking Criteria Clause in Contracts

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon average busy season bouncing busy hour twenty(20) day averaged loads applied to industry standard Erlang-B Trunk Group Capacity algorithms (use Medium day- to-day Variation and 1.0 Peakedness factor until actual traffic data is available).

Appears in 6 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

Trunk Design Blocking Criteria. 7.1 Trunk 3.6.1 In accordance with industry traffic engineering standards, trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon time consistent average busy season bouncing busy hour twenty(20twenty-one (21) day averaged loads applied to industry standard ErlangXxxx-B Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- medium day-to-day Variation variation and 1.0 Peakedness peakedness factor until actual traffic data is available)) or equivalent Erlang B or Poisson factors.

Appears in 5 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

Trunk Design Blocking Criteria. 7.1 Trunk 3.6.1 In accordance with industry traffic engineering standards, trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon time consistent average busy season bouncing busy hour twenty(20twenty- one (21) day averaged loads applied to industry standard Erlang-B Xxxx- Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- tomedium day-to- day Variation variation and 1.0 Peakedness peakedness factor until actual traffic data is available)) or equivalent Erlang B or Poisson factors.

Appears in 4 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon time consistent average busy season bouncing busy hour twenty(20twenty-one (21) day averaged loads applied to industry standard ErlangXxxx-B Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available).. Local Direct End Office (Primary High) as mutually agreed upon Local Direct End Office (Final) 1%

Appears in 4 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1, below. Trunk requirements shall be based upon time consistent average busy season bouncing season, busy hour twenty(20twenty (20) day averaged loads applied to industry standard ErlangXxxx-B Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available).

Appears in 3 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon average busy season bouncing busy hour twenty(20) day averaged loads applied to industry standard Erlang-B Trunk Group Capacity algorithms (use Medium day- to-day Variation and 1.0 Peakedness factor until actual traffic data is available).. Local Direct End Office (Primary High) as mutually agreed upon Local Direct End Office (Final) 1%

Appears in 2 contracts

Samples: Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon time consistent average busy season bouncing season, busy hour twenty(20twenty (20) day averaged loads applied to industry standard ErlangXxxx-B Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available).

Appears in 2 contracts

Samples: Interconnection Agreement, Interconnection Agreement

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon time consistent average busy season bouncing busy hour twenty(20twenty (20) day averaged loads applied to industry standard ErlangNxxx-B Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available).

Appears in 1 contract

Samples: Interconnection Agreement (Pac-West Telecomm Inc)

Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1, below. Trunk requirements shall be based upon time consistent average busy season bouncing season, busy hour twenty(20twenty (20) day averaged loads applied to industry standard ErlangXxxx-B Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day- day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available).. 11-13-03

Appears in 1 contract

Samples: Interconnection Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!