BLV/BLVI Traffic Clause Samples

BLV/BLVI Traffic. 7.2.1 Busy Line Verification (“BLV”) is performed when one Party's Customer requests assistance from the operator bureau to determine if the called line is in use; provided, however, the operator bureau will not complete the call for the Customer initiating the BLV inquiry. Only one BLV attempt will be made per Customer operator bureau call. 7.2.2 Busy Line Verification Interrupt (“BLVI”) is performed when one Party's operator bureau interrupts a telephone call in progress after BLV has occurred. The operator bureau will interrupt the busy line and inform the called party that there is a call waiting. The operator bureau will only interrupt the call and will not complete the telephone call of the Customer initiating the BLVI request. The operator bureau will make only one BLVI attempt per Customer operator telephone call and the applicable charge applies whether or not the called party releases the line. 7.2.3 Each Party's operator bureau shall accept BLV and BLVI inquiries from the operator bureau of the other Party in order to allow transparent provision of BLV/BLVI Traffic between the Parties' networks. Each Party shall route BLV/BLVI Traffic inquiries over separate direct trunks (and not the Local/IntraLATA Trunks) established between the Parties' respective operator bureaus. Unless otherwise mutually agreed, the Parties shall configure BLV/BLVI trunks over the Interconnection architecture defined in Article III, consistent with the Plan. 7.2.4 Each Party shall compensate the other Party for BLV/BLVI Traffic as set forth in the Pricing Schedule. 7.2.5 CLEC may provide its own Operator Services, including BLV/BLVI or use the Operator Services of SBC-AMERITECH or a third party vendor.
View SourceView Similar (38)
BLV/BLVI Traffic. Each Party's operator bureau shall accept BLV and BLVI inquiries from the operator bureau of the other Party in order to allow transparent provision of BLV/BLVI Traffic between the Parties' networks. Each Party shall route BLV/BLVI Traffic inquiries over separate direct trunks (and not the Local/IntraLATA Trunks) established between the Parties' respective operator bureaus. Unless otherwise mutually agreed, the Parties shall configure BLV/BLVI trunks over the Interconnection architecture defined in Article III.
View SourceView Similar (33)
BLV/BLVI Traffic. VII.2.1 Busy Line Verification (“BLV”) is performed when one Party’s Customer requests assistance from the operator bureau to determine if the called line is in use. VII.2.2 Busy Line Verification Interrupt (“BLVI”) is performed when one Party’s operator bureau interrupts a telephone call in progress after BLV has occurred. The operator bureau will interrupt the busy line and inform the called party that there is a call waiting. VII.2.3 Each Party’s operator bureau shall accept BLV and BLVI inquiries from the operator bureau of the other Party in order to allow transparent provision of BLV/BLVI Traffic between the Parties’ networks. When Requesting Carrier does not use Ameritech’s operator bureau, each Party shall route BLV/BLVI Traffic inquiries over separate direct trunks (and not the Local/IntraLATA Trunks) established between the Parties’ respective operator bureaus. Unless otherwise mutually agreed, the Parties shall configure BLV/BLVI trunks over the Interconnection architecture defined in Article III, consistent with the Plan. VII.2.4 Each Party shall compensate the other Party for BLV/BLVI Traffic as set forth at Item IV of the Pricing Schedule.
View SourceView Similar (15)
BLV/BLVI Traffic. 7.2.1 If Party A decides or is required by a regulatory body of competent jurisdiction to offer BLV and BLVI services to enable its Customers to verify and/or interrupt calls of Party B’s Customers, Party B shall accept and respond to BLV and BLVI requests from the operator bureau of Party A. Each Party shall compensate the other Party for BLV and BLVI inquiries in accordance with the other Party’s Tariffed rates, the terms of the Directory Assistance and Call Completion Agreement appended hereto as Exhibit C, or as may be agreed to by the Parties. 7.2.2 The Party B operator shall only verify the status of the line (BLV) or interrupt the line to inform the called party that there is a call waiting (BLVI). The Party B operator will not complete the telephone call of the Customer initiating the BLV/BLVI request. The Party B operator will only make one BLV/BLVI attempt per Customer operator bureau telephone call, and the applicable charges apply whether or not the called party releases the line. 7.2.3 Each Party’s operator bureau shall accept BLV and BLVI inquiries from the operator bureau of the other Party in order to allow transparent provision of BLV/BLVI traffic between the Parties’ networks. 7.2.4 Each Party shall route BLV/BLVI Traffic inquiries over separate direct trunks (and not the Local/IntraLATA/InterLATA Trunks) established between the Parties’ respective operator bureaus. Each Party shall offer Interconnection for BLV/BLVI traffic at its operator services Tandem Office or other mutually agreed point in the LATA. Unless otherwise mutually agreed, the Parties shall configure BLV/BLVI trunks over the Interconnection architectures in accordance with the terms of Section 4, consistent with the Joint Implementation and Grooming Process. Party A shall outpulse the appropriate NPA, ATC Code, and Routing Code (operator code) to Party B.
View SourceView Similar (10)
BLV/BLVI Traffic. VIII.2.1 Each Party shall establish procedures whereby its operator bureau shall coordinate with the operator bureau of the other Party to provide Busy Line Verification (ΑBLV≅) and Busy Line Verification Interrupt (ΑBLVI≅) services on calls between their respective Customers. VIII.2.2 BLV and BLVI inquiries between operator bureaus shall be routed using network-routable access codes published in the LERG over the Local Interconnection Trunks. VIII.2.3 Each Party shall charge the other Party BLV/BLVI Traffic at the rates contained in their respective tariffs.
View SourceView Similar (2)
BLV/BLVI Traffic. 7.1 Busy Line Verification. Busy Line Verification (“BLV”) is performed when one Party's Customer requests assistance from the operator bureau to determine if the called line is in use; provided, however, the operator bureau will not complete the call for the Customer initiating the BLV inquiry. Only one BLV attempt will be made per Customer operator bureau call. 7.2 Busy Line Verification Interrupt. Busy Line Verification Interrupt (“BLVI”) is performed when one Party's operator bureau interrupts a telephone call in progress after BLV has occurred. The operator bureau will interrupt the busy line and inform the called party that there is a call waiting. The operator bureau will only interrupt the call and will not complete the telephone call of the Customer initiating the BLVI request. The operator bureau will make only one BLVI attempt per Customer operator telephone call, and the applicable charge applies whether or not the called party releases the line.
View Source
BLV/BLVI Traffic. Busy Line Verification (“BLV”) is performed when one Party's Customer requests assistance from the operator bureau to determine if the called line is in use; provided, however, the operator bureau will not complete the call for the Customer initiating the BLV inquiry. Only one BLV attempt will be made per Customer operator bureau call.
View Source
BLV/BLVI Traffic. 7.3.1 CLEC may provide its own Operator Services, including BLV/BLVI or use the Operator Services of SBC ILLINOIS or a third party vendor. Each Party shall establish procedures whereby its operator bureau will coordinate with the operator bureau of the other Party in order to provide BLV/BLVI services on calls between their respective line side end users. These services are provided in Article 19 (Inward).
View Source
BLV/BLVI Traffic. Each party shall charge the other for BLV/BLVI Services on a ▇▇▇▇ and keep basis.
View Source

Related to BLV/BLVI Traffic

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that ▇▇▇▇▇ has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.