TRAFFIC EXCHANGE Sample Clauses

The TRAFFIC EXCHANGE clause establishes the terms under which two parties agree to exchange website or network traffic for mutual benefit. Typically, this involves each party displaying the other's content, advertisements, or links, thereby driving visitors to each other's platforms. The clause outlines the metrics for measuring traffic, the duration of the exchange, and any limitations or quality standards that must be met. Its core function is to formalize the arrangement, ensuring both parties receive fair value and clear expectations, while minimizing misunderstandings about the nature and volume of traffic exchanged.
TRAFFIC EXCHANGE. 3.1 Each Party shall be responsible for provisioning its traffic, if any, exchanged under this Agreement. Each Party shall be responsible for establishing appropriate contractual or tariff relationships with the third-party LEC(s), if any, that Party selects for transiting traffic to the other Party. Each Party shall be responsible for providing the trunks from its network to the point of interconnection with the network(s) of any such third-party LEC(s), and for paying such third-party LEC(s) for the costs of transiting calls that the Party originates.
View SourceView Similar (5)
TRAFFIC EXCHANGE. TDS TELECOM and LEVEL 3 will interconnect, exchange traffic and maintain compensation for traffic originated by or destined to an IVP.
View SourceView Similar (4)
TRAFFIC EXCHANGE. 4.1 The Parties shall exchange Local Traffic under this Agreement by each Party physically connecting its network to a third-party LEC(s) or an IXC, which shall transit the traffic between the two Parties. Each Party shall be responsible for establishing appropriate contractual relationships with this third-party LEC(s) or IXC for interconnecting with its network and transiting traffic over that network to the other Party. Each Party shall be responsible for providing the trunks from its network to the point of interconnection with the third-party LEC(s) or IXC network and for paying or collecting from the third-party LEC(s) or IXC network provider for the costs of transiting calls that the Party originates. 4.2 An NPA/NXX assigned to VERIZON WIRELESS shall be included in any extended area service (“EAS”) calling scope or similar program to the same extent as any other ILECs NPA/NXX in the same rate center; provided that VERIZON WIRELESS assigns numbers from such NPA/NXX to customers within the Local Service Area or EAS scope of ILEC and VERIZON WIRELESS has radio frequency coverage to serve such customers.
View SourceView Similar (2)
TRAFFIC EXCHANGE. In return for consideration contained in Sections 4 and 6 of this Addendum, ▇▇▇▇▇▇▇ agrees to exchange the Subject Traffic as Local Traffic. In particular, ▇▇▇▇▇▇▇ agrees to the following treatment of traffic associated with telephone numbers that CD has assigned or will assign to customers, including ISP customers, that are rated to Spectra rate centers or to rate centers that share a local calling area with Spectra rate centers (“ISP Numbers”). Spectra agrees to translate all CD ISP Numbers in its switches such that traffic dialed to the ISP Numbers will be treated as Local Traffic, regardless of the physical location of the customer. Spectra agrees that it will not seek “interexchange” or access treatment of traffic dialed to the ISP Numbers.
View Source
TRAFFIC EXCHANGE. 4.1 Each Party agrees to query the LNP Call Routing Database on each of its originated Voice Calls, and to route a Voice Call over the Direct Interconnection Facilities only to the extent the LRN returned from such query belongs to the other Party. Each Party shall bear any and all costs associated with LNP queries and associated routing of its originating Voice Calls under this Agreement. 4.2 The Parties agree to route IntraMTA Voice Calls in accordance with the LERG. 4.3 The Parties shall provide each other with dialing parity in accordance with Applicable Law. 4.4 Indianhead shall classify Voice Calls as local or toll based solely upon the Rate Center associated with the NXX Code of the dialed CTN. For the avoidance of any doubt, Indianhead shall not rate a Voice Call from a particular Customer as a toll call unless it would rate as a toll call any other call from that same Customer to a third party’s customer with a CTN associated with the same Rate Center as the Voice Call. 4.5 Each Party is solely responsible for the services it provides to its Customers. 4.6 Each Party is responsible for managing its assigned NXX Codes and thousand blocks within NXX Codes. 4.7 Each Party shall use the LERG or its successor to obtain routing information and shall provide to the LERG publisher in a timely manner all information required to maintain the accuracy of the LERG for routing traffic to such Party. 4.8 Neither Party shall route 911/E911 traffic to the other Party. Each Party shall be responsible for delivering its Customers’ 911/E911 calls to the 911/E911 service provider.
View Source
TRAFFIC EXCHANGE. 3.1 The Parties shall exchange traffic under this Agreement by each Party physically connecting its network to a third-party LEC(s) network(s), which shall transit transports the traffic between the two Parties. Each Party shall be responsible for establishing appropriate contractual relationships with this third-party LEC(s) network(s) for interconnecting with its network and transiting traffic over that network to the other Party. Each Party shall be responsible for providing the trunks from its network to the point of interconnection with the third-party network and for paying the third-party LEC(s) network provider for the costs of transiting calls that the Party originates. 3.2 The Party terminating traffic is not responsible for the costs incurred in transporting that traffic from the originating carrier’s network to the terminating carrier’s network.
View Source
TRAFFIC EXCHANGE. In return for consideration contained in Sections 4 and 6 of this Addendum, CenturyTel agrees to exchange the Subject Traffic as Local Traffic. In particular, CenturyTel agrees to the following treatment of traffic associated with telephone numbers that CD has assigned or will assign to customers, including ISP customers, that are rated to CenturyTel rate centers or to rate centers that share a local calling area with CenturyTel rate centers (“ISP Numbers”). CenturyTel agrees to translate all CD ISP Numbers in its switches such that traffic dialed to the ISP Numbers will be treated as Local Traffic, regardless of the physical location of the customer. CenturyTel agrees that it will not seek “interexchange” or access treatment of traffic dialed to the ISP Numbers.
View Source

Related to TRAFFIC EXCHANGE

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

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