Measuring Calls as Local Traffic Sample Clauses

Measuring Calls as Local Traffic. In order to determine whether traffic is Local Traffic for purposes of calculating Reciprocal Compensation, the Parties agree as follows: for ALLTEL, the origination or termination point of a call shall be the end office that serves, respectively, the calling or called party. For CMRS-P, the origination or termination point of a call shall be the cell site that serves, respectively, the calling or called party at the beginning of the call.
Sample 1See All (5)
AutoNDA by SimpleDocs
Measuring Calls as Local Traffic. 3.3.3.1 In order to measure whether traffic comes within the definition of Local Traffic for the purposes of calculating reciprocal compensation, the Parties agree to the following: 3.3.3.1.1 For Land to Mobile traffic, the origination point of a call shall be the SBC-13STATE Central End Office Switch that serves the calling party at the beginning of the call, and the termination point shall be Carrier’s cell site/base station, which serves the called party at the beginning of the call. 3.3.3.1.2 For Mobile to Land traffic, the origination point of a call shall be the Carriers’ cell site/base station that serves the calling party at the beginning of the call, and the termination point shall be SBC-13STATE Central End Office Switch, which serves the called party at the beginning of the call.
Sample 1Sample 2Sample 3See All (4)
Measuring Calls as Local Traffic. 5.4.1 In order to measure for purposes of calculating Reciprocal Compensation, the Parties agree as follows: For BEEHIVE, the origination or termination point of a call shall be BEEHIVE’s end office which serves, respectively, the calling or called End User. For T-MOBILE, the origination or termination point of a call shall be the cell site location which serves, respectively, the calling or called End User. 5.4.2 Each Party intends to utilize measured traffic for the purposes of (a) determining Reciprocal Compensation and (b) apportioning shared facilities charges. Where either Party or both Parties are unable to measure traffic, the Parties agree to use the most recent default percentages during the period the data is unavailable for the application of charges pursuant to this Agreement. A non-measuring Party may choose to submit invoices for Reciprocal Compensation based on the measuring Party’s representations of Local Traffic originated by the measuring Party. In either event, either Party may request to revise the default percentages no more than once every six (6) months thereafter, based on the previous six (6) months average of actual usage. At the written request of either Party to revise the default percentages for reciprocal compensation, the default percentages will be adjusted based on the Parties’ respective percentages of Local Traffic subject to reciprocal compensation. At the written request of either Party to revise the default percentages for shared facilities, the default percentages will be adjusted based on the Parties’ respective percentages of all IntraMTA Traffic exchanged by the Parties. Any adjustments to the default percentages that is agreed upon by the Parties or otherwise resolved pursuant to Section 12 (Dispute Resolution), will be effective the next billing cycle thirty (30) days after the receipt of the written request. In the event of a dispute regarding the adjustment, if any, to the factors, the dispute will be resolved pursuant to the provisions of Section 12.
Sample 1

Related to Measuring Calls as Local Traffic

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

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