VNXX Traffic Sample Clauses

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.

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

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.

VNXX Traffic. The Parties will not pay reciprocal compensation on traffic 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. The 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 as local traffic. Bandwidth’s agreement to the terms in this paragraph is without waiver or prejudice to Bandwidth’s position that internet Protocol (“IP”) technology is inherently devoid of traditional geographic limitations and that imposing geographic limitations artificially is not technically or legally necessary.

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.

VNXX Traffic. 3.2.1. VNXX, as defined in this Agreement in 3.2.3, is not Local Traffic. The Parties agree that due to the mass availability and portability of IP-based CPE, some of the traffic sent between the Parties for termination may be Nomadic Traffic. Nomadic Traffic is traffic originating from an Internet Protocol (“IP”) device other than at the End User’s service location. The Parties understand and agree that some small amount of Nomadic Traffic is likely to be exchanged and wish to ensure that both Parties are properly compensated for such traffic. As a result, the Parties will initially assume that 2% of Local Traffic exchanged is Nomadic Traffic and each Party will bill its applicable interstate switched access rate for 2% of the Local Traffic sent by each Party for termination. If either Party believes that the majority of the other Party’s traffic is Nomadic Traffic, then the Parties can conduct audits or take other commercially reasonable steps to verify that the other Party is not provisioning any of its services to intentionally circumvent applicable switched access service charges. If either Party intends to send primarily Nomadic Traffic, then such Party shall notify the other Party in writing within sixty (60) days to amend the Agreement. 3.2.2. Both Parties shall adhere to the North American Numbering Plan (NANP) guidelines. Both Parties agree to only assign telephone numbers from an NPA- NXX Code(s) to an End User Customer at an End User Customer Location located inside the Rate Center with which the NPA-NXX Code(s) is assigned or its associated local calling area. Numbers shall not be used to aggregate traffic to originate or terminate to either Party. 3.2.3. Virtual NXX or VNXX is service whereby an End User Customer is assigned a telephone number associated with a Local Calling Area (defined as the local exchange calling area including any mandatory local calling areas established and defined by the Commission), that is different from the Local Calling Area in which the Customer is physically located. 3.2.4. Neither Party shall route un-translated traffic to service codes (e.g., 8YY, 900) over the Local Interconnection Trunks. 3.2.5. N11 Codes: Neither Party shall route un-translated N11 codes (e.g., 411, 611, 711, 811 and 911) to the other party over Interconnection Facilities.