VNXX Traffic Sample Clauses

VNXX Traffic. The Parties will not pay reciprocal compensation on traffic, including Information Access Traffic, when the traffic does not originate and terminate within the same Frontier Local Calling Area, regardless of the calling and called NPA-NXXs and, specifically, regardless of whether an End User Customer is assigned an NPA-NXX associated with a rate center that is different from the rate center where the End User Customer is physically located. This traffic is also known as “VNXX traffic.” Frontier’s agreement to the terms in this paragraph is without waiver or prejudice to Frontier’s position is that it has never agreed to exchange VNXX traffic with Carrier.
Sample 1Sample 2Sample 3See All (24)
AutoNDA by SimpleDocs
VNXX Traffic. If CD assigns NPA/NXXs to a customer physically located outside of the CenturyTel Local Calling Area containing the rate center with which the NPA/NXX is associated, traffic originating from CenturyTel customers within that CenturyTel Local Calling Area to CD customer physically located outside of the CenturyTel Local Calling Area, shall not be deemed Local Traffic, and shall be subject to applicable access charges established in CenturyTel’s Access Service Tariffs.
Sample 1Sample 2Sample 3
VNXX Traffic. If CD assigns NPA/NXXs to a customer physically located outside of the Spectra Local Calling Area containing the rate center with which the NPA/NXX is associated, traffic originating from Spectra customers within that Spectra Local Calling Area to CD customer physically located outside of the Spectra Local Calling Area, shall not be deemed Local Traffic, and shall be subject to applicable access charges established in Spectra’s Access Service Tariffs.
Sample 1Sample 2
VNXX Traffic. 56.4.1 VNXX Traffic is not Local Traffic for purposes of intercarrier compensation. On or after the Effective Date of the Agreement, neither Party shall provide VNXX Services unless the Party providing such VNXX Service first provides thirty (30) Days advance written notice to the other Party during which time, the Parties agree to negotiate percentage factors to reflect the amount of traffic that will be presumed to be originating or terminating VNXX Traffic and appropriate jurisdictional factors (subject to verification and modification, as necessary); provided however, that such factor shall not be implemented unless the amount of such traffic exchanged over local interconnection trunks exceeds (i) at least 50,000 minutes of use (MOU) per month or (ii) one-half of one percent (0.5%) of all the voice traffic of the Party providing the VNXX Service exchanged over such local interconnection trunks, whichever is greater. In the absence of a written agreement between the Parties stating otherwise, the Party that originates or terminates such VNXX Traffic (including any VNXX Traffic which is ISP-Bound Traffic), shall be entitled to recover originating or terminating access charges except that the Party that provides the VNXX Service that enables such VNXX Traffic shall not be entitled to recover access charges for such VNXX Traffic. 56.4.2 Either Party may perform traffic studies at any time, but no more frequently than twice during any twelve (12) month period, to determine if VNXX Traffic is being exchanged, and/or to verify the originating or terminating percentages of such traffic as set forth above, including jurisdictional use factors. The Parties will cooperate in connection with such traffic studies to determine the geographic location associated with telephone number(s) assigned using a VNXX Service. Should the traffic study indicate that VNXX factors (and appropriate jurisdictional factors) should be established or adjusted, the Parties agree to implement the correct percentage on a prospective basis (i.e., from the date of the traffic study) pursuant to advance written notice, without amending the agreement, but not covering any period prior to the implementation of a previous factor by the Parties. Any dispute arising from this Section 56 shall be resolved pursuant to the Dispute Resolution provisions of Section 25. 56.4.3 Notwithstanding references to VNXX Traffic in this section, the parties recognize that the Oregon PUC currently prohibits VNXX...
Sample 1Sample 2
VNXX Traffic. VNXX Traffic is not Local Traffic for purposes of intercarrier compensation. On or after the Effective Date of the Agreement, neither Party shall provide VNXX Services unless the Party providing such VNXX Service first provides thirty (30) Days advance written notice to the other Party during which time, the Parties agree to negotiate percentage factors to reflect the amount of traffic that will be presumed to be originating or terminating VNXX Traffic and appropriate jurisdictional factors (subject to verification and modification, as necessary); provided however, that such factor shall not be implemented unless the amount of such traffic exchanged over local interconnection trunks exceeds (i) at least 50,000 minutes of use (MOU) per month or (ii) one-half of one percent (0.5%) of all the voice traffic of the Party providing the VNXX Service exchanged over such local interconnection trunks, whichever is greater. In the absence of a written agreement between the Parties stating otherwise, the Party that originates or terminates such VNXX Traffic (including any VNXX Traffic which is ISP-Bound Traffic), shall be entitled to recover originating or terminating access charges except that the Party that provides the VNXX Service that enables such VNXX Traffic shall not be entitled to recover access charges for such VNXX Traffic.
Sample 1

Related to VNXX 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.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • Third Party Websites The Service may contain or reference links to websites operated by third parties ("Third Party Websites"). These links are provided as a convenience only. Such Third Party Websites are not under our control. We are not responsible for the content of any Third Party Website or any link contained in a Third Party Website. We do not review, approve, monitor, endorse, warrant, or make any representations with respect to Third Party Websites, and the inclusion of any link in the Service, Debit Rewards Offers or any other services provided in connection with them is not and does not imply an affiliation, sponsorship, endorsement, approval, investigation, verification or monitoring by us of any information contained in any Third Party Website. In no event will we be responsible for the information contained in such Third Party Website or for your use of or inability to use such website. Access to any Third Party Website is at your own risk, and you acknowledge and understand that linked Third Party Websites may contain terms and privacy policies that are different from ours. We are not responsible for such provisions, and expressly disclaim any liability for them.

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