Trunk Data Exchange Clause Samples

Trunk Data Exchange. 65.9.1 Each Party agrees to service trunk groups to the blocking criteria in Section 59.2.3 in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty-one (21) Day study period. The Parties agree that twenty-one (21) Days is the study period duration objective unless mutually agreed otherwise. The study period will not include a holiday.
View SourceView Similar (123)
Trunk Data Exchange. 3.11.1 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty-one (21) day study period. The Parties agree that twenty-one (21) days is the study period duration objective. However, a study period on occasion may be less than twenty-one (21) days but at minimum must be at least three (3) business days to be utilized for engineering purposes, although with less statistical confidence. 3.11.2 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds) on a seven (7) day per week, twenty-four (24) hour per day, fifty-two (52) weeks per year basis. These reports shall be made available on a semi-annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management
View SourceView Similar (22)
Trunk Data Exchange. 7.1 A Trunk Group utilization report (TIKI) is available upon request. The report is provided in MS-Excel format.
View SourceView Similar (21)
Trunk Data Exchange. 9.1 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average bouncing busy hour for a twenty (20) day study period. The Parties agree that twenty (20) days is the study period duration objective. However, a study period on occasion may be less than twenty (20) days but at minimum must be at least three (3) business days to be utilized for engineering purposes, although with less statistical confidence. 9.2 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to exchange of traffic data upon request. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds) on a seven (7) day per week, twenty-four (24) hour per day, fifty-two
View SourceView Similar (11)
Trunk Data Exchange. 74.13.1. Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty-one (21) day study period. The Parties agree that twenty-one (21) days is the study period duration objective. However, a study period on occasion may be less than twenty-one (21) days but at minimum must be at least three (3) business days to be utilized for engineering purposes, although with less statistical confidence. 74.13.2. Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds) on a seven (7) day per week, twenty-four
View SourceView Similar (4)
Trunk Data Exchange. 3.11.1 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty-one (21) day study period. The Parties agree that twenty-one (21) days is the study period duration objective. However, a study period on occasion may be less than twenty-one (21) days but at minimum must be at least three (3) business days to be utilized for engineering purposes, although with less statistical confidence. 3.11.2 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Upon request of either Party the Parties agree to establish a timeline for implementing an exchange of traffic data. Implementation shall be such date as agreed upon, after the trunk groups begin passing live traffic. The traffic data to be exchanged will be as agreed by the Parties. These reports shall be made available on a semi-annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management
View SourceView Similar (2)
Trunk Data Exchange. 20.1 AT&T MICHIGAN shall provide Data Interexchange Carrier (DIXC) traffic data for all trunk groups terminating in Climax’s network. 20.2 The Parties agree to exchange traffic data on trunks and to implement such an exchange within three
View Source
Trunk Data Exchange. 20.1 MCIm has requested and AT&T ILLINOIS shall provide Data Interexchange Carrier (DIXC) traffic data for all trunk groups terminating in MCIm’s network. A trunk group utilization report (TIKI) is also available, upon request. The TIKI report is provided in a MS-Excel format. 20.2 The Parties agree to exchange traffic data on trunks and to implement such an exchange within three (3) months of the date that trunking is established and the trunk groups begin passing live traffic, or another date as agreed to by the Parties. Exchange of traffic data will permit each company to have knowledge of the offered and overflow load at each end of the two-way trunk group, and thereby enable accurate and independent determination of performance levels and trunk requirements. The Parties agree to the electronic exchange of data. Parties agree to establish a timeline for implementing an exchange of traffic data utilitizing the DIXC process via network data mover (NDM)/FTP computer to computer File Transfer Process (FTP). 20.3 DIXC traffic data will include, but not be limited to, the following: 20.3.1 Usage (total usage measured in centum call seconds) 20.3.2 Peg Count (Peg count of originating call attempts including overflow) 20.3.3 Overflow (Peg count of originating call attempts failing to find an idle trunk) 20.3.4 Maintenance Usage (total maintenance usage measured in centum call seconds) 20.3.5 Maintenance Busy Counts (total count of trunks made maintenance busy) 20.4 DIXC traffic data shall be collected as follows: 20.4.1 Hourly on the clock hour 20.4.2 Twenty-four (24) hours per day (0000-2400) 20.4.3 Seven (7) days per week (including holidays) 20.4.4 Fifty-two (52) weeks per year
View Source
Trunk Data Exchange 
View Source

Related to Trunk Data Exchange

  • Data Encryption 2.1. For all COUNTY data, The CONTRACTOR shall encrypt all non-public data in transit regardless of the transit mechanism. 2.2. For all COUNTY data, if the CONTRACTOR stores sensitive personally identifiable or otherwise confidential information, this data shall be encrypted at rest. Examples are social security number, date of birth, driver’s license number, financial data, federal/state tax information, and hashed passwords. 2.3. For all COUNTY data, the CONTRACTOR’S encryption shall be consistent with validated cryptography standards as specified in National Institute of Standards and Technology Security Requirements as outlined at ▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇.▇▇▇/nistpubs/Legacy/SP/nistspecialpublication800-111.pdf

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Access Toll Connecting Trunk Group Architecture 8.2.1 If Reconex chooses to subtend a Verizon access Tandem, Reconex’s NPA/NXX must be assigned by Reconex to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center subtends as identified in the LERG. 8.2.2 Reconex shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from Reconex’s Customers. 8.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office Reconex utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the Tandem Verizon utilizes to provide Exchange Access in such LATA. 8.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow Reconex’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access tandem.

  • Internet Connection Certain Solutions may require an active and stable connection to the Internet in order to function. It is therefore your responsibility to ensure that you have at all times an active and stable Internet connection.