Local Traffic Exchange Clause Samples

Local Traffic Exchange. Local Traffic is defined as any telephone call that originates and terminates in the same LATA and is billed by the originating party as a local call. The Parties have been unable to agree upon whether, pursuant to the FCC’s Declaratory Ruling in Docket CC-99-98, Enhanced Service Provider (“ESP”) and Information Service Provider (“ISP”) traffic should be considered Local Traffic for purposes of this Agreement. Therefore, without prejudice to either Party’s position concerning the nature of ESP and ISP traffic, the Parties agree that for purposes of this Agreement only, ESP and ISP traffic shall not be deemed Local Traffic in determining compensation to be exchanged between the Parties pursuant to Attachment 3, Section 8 of this Agreement.
View SourceView Similar (3)
Local Traffic Exchange. A. Exchange of Traffic ------------------- The Parties agree for the purpose of this Agreement only that local interconnection is defined as the delivery of local traffic to be terminated on each party's local network so that customers of either party have the ability to reach customers of the other party, without the use of any access code or delay in the processing of the call. Local traffic for these purposes shall include any telephone call that originates and terminates in the same LATA and is billed by the originating exchange outside of BellSouth's service area with respect to which BellSouth has a local interconnection arrangement with an independent LEC, with which DeltaCom is not directly connected. The Parties further agree that the exchange of traffic on BellSouth's Extended Area Service (EAS) shall be considered local traffic and compensation for the termination of such traffic shall be pursuant to the terms of this section. EAS routes are those exchanges within an exchange's Basic Local Calling Area, as defined in Section A3 of BellSouth's General Subscriber Services Tariff.
View Source
Local Traffic Exchange. Exchange of local exchange traffic will occur at Tel USA’s Rice Lake Tandem (RCLKWIXB51T) for local traffic listed below: Tel USA OCN 1155 Lakeland OCN 0769 Centuria (CENTWIXARS0) 715 646 Centuria 715 Local Balsam Lake (BLLKWIXARS0) 715 485 Centuria ▇▇▇ ▇▇▇ ▇▇. ▇▇▇▇▇ ▇▇▇▇▇ 715 483 Centuria 715 EAS Balsam Lake 715 485 Balsam Lake ▇▇▇ ▇▇▇▇▇ ▇▇. ▇▇▇▇▇ ▇▇▇▇▇ 715 483 Balsam Lake 715 EAS The local calling definition will be updated with any new NPA/NXX established in the LERG by either Party. APPENDIX G SERVICE QUALITY STANDARDS The Service Quality Standards are in addition to and not in place of satisfaction of specific performance standards elsewhere in this agreement. Servi ces, facilities, and features provided by Tel USA under this Agreement shall be equal to quality to those provided to itself, its affiliates, or any other Party to which Tel USA provides interconnection.
View Source
Local Traffic Exchange 
View SourceView Similar (24)

Related to Local Traffic Exchange

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

  • Shift Exchange The Employer and the Union agree that shift exchanges are a useful process to allow employees more flexibility and improved work/life balance. Employees within an institution who have the same job classification will be allowed to exchange full shifts for positions in which they are qualified. The shift exchange process will not be used to circumvent the bid system or the supervisory chain of command. Shift exchanges will be in accordance with the following: A. Request for shift exchanges will be submitted seven (7) calendar days in advance of the exchange, when practicable. B. Requests for shift exchanges will be considered on a case-by-case basis. The requested shift exchange is voluntary, and is agreed to in writing by both employees, and approved in writing by the supervisor(s). Requests for shift exchanges will be submitted to the appropriate Appointing Authority or designee for approval. ▇. ▇▇▇▇▇ exchanges may be denied. If denied, the employee will be provided the reason(s) in writing. D. Employees will not submit requests for shift exchanges which would result in overtime. Each employee will be considered to have worked their regular schedule. E. For shift exchanges that occur on an employee’s designated holiday, the employee who is regularly scheduled to work on that holiday will receive the holiday compensation, regardless of who physically worked on that day. F. The failure of an employee who has exchanged shifts to work the agreed upon shift without appropriate cause may be a basis for disciplinary action.

  • Manual Transactions If the parties choose not to use Fund/SERV, if there are technical problems with Fund/SERV, or if the parties are not able to transmit or receive information through Fund/SERV, any corrections to a Portfolio’s prices should be communicated by facsimile or by electronic transmission, and will include for each day on which an adjustment has occurred the incorrect Portfolio price, the correct price, and, to the extent communicated to Portfolio shareholders, the reason for the adjustment. The Company may send this notification or a derivation thereof to Contract owners whose Contracts are affected by the adjustment.

  • Shift Exchanges In no event shall any overtime be payable as a result of employees voluntarily exchanging shifts.

  • Data Exchange Except where prohibited by law or regulation, MCP and MHP must share the minimum necessary data and information to facilitate referrals and coordinate care under this MOU. The Parties must have policies and procedures for supporting the timely and frequent exchange of Member information and data, including behavioral health and physical health data; for ensuring the confidentiality of exchanged information and data; and, if necessary, for obtaining Member consent, when required. The minimum necessary information and data elements to be shared as agreed upon by the Parties, are set forth in Exhibit C of this MOU. To the extent permitted under applicable law, the Parties must share, at a minimum, Member demographic information, behavioral and physical health information, diagnoses, assessments, medications prescribed, laboratory results, referrals/discharges to/from inpatient or crisis services and known changes in condition that may adversely impact the Member’s health and/or welfare. The Parties must annually review and, if appropriate, update Exhibit C of this MOU to facilitate sharing of information and data. MHP and MCP must 4 CalAIM Data Sharing Authorization Guidance VERSION 2.0 June 2023 available at: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇.▇▇▇/Documents/MCQMD/CalAIM-Data-Sharing-Authorization- Guidance-Version-2- Draft-Public-Comment.pdf. establish policies and procedures to implement the following with regard to information sharing: i. A process for timely exchanging information about Members eligible for ECM, regardless of whether the Specialty Mental Health provider is serving as an ECM provider; ii. A process for MHP to send regular, frequent batches of referrals to ECM and Community Supports to MCP in as close to real time as possible; iii. A process for MHP to send admission, discharge, and transfer data to MCP when Members are admitted to, discharged from, or transferred from facilities contracted by MHP (e.g., psychiatric inpatient hospitals, psychiatric health facilities, residential mental health facilities), and for MCP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3); iv. A process to implement mechanisms to alert the other Party of behavioral health crises (e.g., MHP alerts MCP of Members’ uses of mobile health, psych inpatient, and crisis stabilization and MCP alerts MHP of Members’ visits to emergency departments and hospitals); and v. A process for MCP to send admission, discharge, and transfer data to MHP when Members are admitted to, discharged from, or transferred from facilities contracted by MCP (e.g., emergency department, inpatient hospitals, nursing facilities), and for MHP to receive this data. This process may incorporate notification requirements as described in Section 8(a)(v)(3).