BLV/BLVI Traffic Sample Clauses

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.
Sample 1Sample 2Sample 3See All (35)
AutoNDA by SimpleDocs
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.
Sample 1Sample 2Sample 3See All (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.
Sample 1Sample 2Sample 3See All (14)
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.
Sample 1Sample 2Sample 3See All (10)
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.
Sample 1
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).
Sample 1
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.
Sample 1
AutoNDA by SimpleDocs
BLV/BLVI Traffic. Each party shall charge the other for BLV/BLVI Services on a xxxx and keep basis.
Sample 1
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.
Sample 1

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.

  • 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.

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Mail Order Catalog Warnings In the event that, the Settling Entity prints new catalogs and sells units of the Products via mail order through such catalogs to California consumers or through its customers, the Settling Entity shall provide a warning for each unit of such Product both on the label in accordance with subsection 2.4 above, and in the catalog in a manner that clearly associates the warning with the specific Product being purchased. Any warning provided in a mail order catalog shall be in the same type size or larger than other consumer information conveyed for such Product within the catalog and shall be located on the same display page of the item. The catalog warning may use the Short-Form Warning content described in subsection 2.3(b) if the language provided on the Product label also uses the Short-Form Warning.

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