High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group Sample Clauses

The High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group clause establishes special telecommunications arrangements to manage situations where a large number of calls are expected to a specific number or service. In practice, this involves designating certain trunk groups—dedicated lines or circuits—that can handle sudden surges in call volume, such as during radio contests, emergency hotlines, or televised voting events. By isolating and controlling these high-traffic call flows, the clause helps prevent network congestion and ensures that regular telephone services remain unaffected for other users.
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. 5.6.1 If TCAL should acquire a HVCI/Mass Calling customer, i.e. a radio station, TCAL shall provide written notification to TDS TELECOM. TDS TELECOM reserves the option to provide either a physical or “virtual” trunk group, with a virtual group preferred where technically feasible, for HVCI/Mass Calling Trunking.
View SourceView Similar (6)
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. 5.7.1 If LEVEL 3 should acquire a HVCI/Mass Calling customer, i.e. a radio station, LEVEL 3 shall provide written notification to TDS TELECOM. TDS TELECOM reserves the option to provide either a physical or “virtual” trunk group, with a virtual group preferred where technically feasible, for HVCI/Mass Calling Trunking.
View SourceView Similar (4)
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. SBC- 13STATE 2.1.6.1 Separate high-volume Trunk Groups (HVCI) will be required for high-volume customer calls (e.g., radio contest lines). If the need for HVCI is identified by either Party, that party may initiate a meeting where the parties will negotiate where HVCI Trunk Groups need to be provisioned to ensure network protection from HVCI traffic.
View SourceView Similar (2)
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. SBC-12STATE 3.5.1 A dedicated Trunk Group shall be required to the designated Public Response HVCI/Mass Calling Network Access Tandem in each serving area. This Trunk Group shall be one-way outgoing only and shall utilize MF signaling. As the HVCI/Mass Calling Trunk Group is designed to block all excessive attempts toward HVCI/Mass Calling NXXs, it is necessarily exempt from the one percent blocking standard described elsewhere for other final local Interconnection Trunk Groups. WSP will have administrative control for the purpose of issuing ASRs on this one-way Trunk Group. The Parties will not exchange live traffic until successful testing is completed by both Parties. 3.5.1.1 This Trunk Group shall be sized as follows: 3.5.2 If WSP should acquire a HVCI/Mass Calling End User (e.g., a radio station), WSP shall notify SBC-12STATE at least sixty (60) Days in advance of the need to establish a one-way outgoing SS7 or MF Trunk Group from the SBC-12STATE HVCI/Mass Calling Serving Office to the WSP End User’s serving office. WSP will have administrative control for the purpose of issuing ASRs on this one-way Trunk Group. 3.5.2.1 If WSP finds it necessary to issue a new choke telephone number to a new or existing HVCI/Mass Calling End User, the WSP may request a meeting to coordinate with SBC- 12STATE the assignment of HVCI/Mass Calling telephone number from the existing choke NXX. In the event that the WSP establishes a new choke NXX, WSP must notify SBC-12STATE a minimum of ninety (90) Days prior to deployment of the new HVCI/Mass Calling NXX. SBC-12STATE will perform the necessary translations in its end offices and Tandem(s) and issue ASR’s to establish a one-way outgoing SS7 or MF trunk group from the SBC-12STATE Public Response HVCI/Mass Calling Network Access Tandem to the WSP’s choke serving office. 3.5.3 In SBC CONNECTICUT , where HVCI/Mass Calling NXXs have not been established, the Parties agree to utilize “call gapping” as the method to control high volumes of calls, where technically feasible in the originating switch, to specific high volume End Users or in situations such as those described in Section 28, "Network Maintenance and Management" of the General Terms and Conditions.
View SourceView Similar (2)
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. SBC-12STATE 5.7.1 A dedicated trunk group shall be required to the designated Public Response HVCI/Mass Calling Network Access Tandem in each serving area. This trunk group shall be one-way outgoing only and shall utilize MF signaling. As the HVCI/Mass Calling trunk group is designed to block all excessive attempts toward HVCI/Mass Calling NXXs, it is necessarily exempt from the one percent blocking standard described elsewhere for other final Local Interconnection trunk groups. LEVEL 3 will have administrative control for the purpose of issuing ASRs on this trunk group. The Parties will not exchange live traffic until successful testing is completed by both Parties. 5.7.2 This group shall be sized as follows Number of Access Lines Served Number of Mass Calling Trunks 5.7.3 If ▇▇▇▇▇ ▇ should acquire an HVCI/Mass Calling customer, e.g., a radio station, LEVEL 3 shall notify SBC-12STATE at least sixty (60) days in advance of the need to establish a one-way outgoing SS7 or MF trunk group from the SBC-12STATE HVCI/Mass Calling Serving Office to LEVEL 3’s customer’s serving office. LEVEL 3 will have administrative control for the purpose of issuing ASRs on this one-way trunk group.
View Source
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. The Parties will cooperate to establish separate choke trunk groups for the completion of calls such as radio contest lines, etc., unless this is determined to be unnecessary by both parties because they have implemented "Call Gapping" software, or other call control measures. When completing a new interconnection in an existing LATA or a new interconnection in a new LATA, CLEC will establish a MF based choke trunk group if SBC ILLINOIS has a Choke NPA in that LATA.
View Source
High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group. 5.7.1 If CLEC should acquire a HVCI/Mass Calling customer, i.e. a radio station, CLEC shall provide written notification to UNION. UNION reserves the option to provide either a physical or “virtual” trunk group, with a virtual group preferred where technically feasible, for HVCI/Mass Calling Trunking.
View Source

Related to High Volume Call In (HVCI) / Mass Calling (Choke) Trunk Group

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center. 2.4.3 On a semi-annual basis, Teleconex shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.‌‌‌‌‌‌‌ 2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5). 2.4.7 Two-Way Local Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards. 2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.