Paid Calls Sample Clauses

Paid Calls. 6.2.1 Microsoft shall use [****] to release a new version of the MSN Messenger Service with capabilities for making paid PC-to-Phone voice transmissions using the N2P Deliverables ("PAID CALL CAPABILITY") on or before [****]. Upon such a new release of the MSN Messenger Service with Paid Call Capability and for the [****] thereafter, Microsoft shall cause [****] of the paid PC-to-Phone voice traffic generated by such MSN Messenger Service to be directed to Net2Phone's transmission and delivery services; provided, that Net2Phone is able to provide such transmission and delivery services in accordance with the terms and conditions set forth in Article 7. 6.2.2 In the event that Microsoft does not release a new version of the MSN Messenger Service with Paid Call Capability on or before [****], then, beginning on [****] and on the first day of each month thereafter during such time as a new version of the MSN Messenger Service with Paid Call Capability has not been released by Microsoft, (a) the number of months termination notice required to be given by (i) Microsoft pursuant to Section 18.2.1 shall be increased by [****]; provided, that the notice period for Microsoft may not be increased to a period greater than [****]; and (ii) the number of months termination notice required to be given by Net2Phone pursuant to Section 18.3.1 shall be decreased by [****]; provided, that the notice period for Net2Phone may not be decreased to a period of less than [****]; and (b) the number of months of dedicated paid PC-to-Phone traffic specified in Section 6.2.1 shall be increased by [****]. The provisions of the preceding sentence shall not apply in the event that the release of the MSN Messenger Service with Paid Call Capability results from Net2Phone's inability to deliver in a timely manner any development assistance, software, modifications and/or services which may be necessary to release the MSN Messenger Service with Paid Call Capability in conformance with such specifications and standards as may be required by Microsoft, except where such inability to deliver results from Microsoft's failure to notify Net2Phone of such requirements on or before [****]. At such time as Microsoft releases a new version of the MSN Messenger Service with Paid Call Capability, the notice periods required under Sections 18.2.1 and 18.3.1 shall revert back to the original periods set forth in this Agreement. 6.2.3 [****]
AutoNDA by SimpleDocs

Related to Paid Calls

  • End User This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.

  • Alternate Billed Calls 1.1 The Parties will engage in settlements of intraLATA intrastate alternate-billed calls (e.g., collect, calling card, and third-party billed calls) originated or authorized by their respective Customers in accordance with an arrangement mutually agreed to by the Parties.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • End Users Customer will control access to and use of the Products by End Users and is responsible for any use of the Products that does not comply with this Agreement.

  • Product Testing No later than [**] prior to a scheduled Delivery ARIAD US shall send to ARIAD SWISSCO the Delivery Documents for review. Following such review, unless within [**] of receipt of the Delivery Documents ARIAD SWISSCO gives written notice of rejection of the Product to be delivered, stating the reasons for such rejection, the Delivery shall proceed, and both Parties shall organize the same. Upon arrival at ARIAD SWISSCO nominated site it shall visually inspect the shipment of the Product to identify any damage to the external packaging. ARIAD SWISSCO may reject any shipment (or portion thereof) of the Product that is damaged by providing to ARIAD US reasonable evidence of damage within [**] after Delivery of such Product. If ARIAD SWISSCO does not so reject any shipment (or portion thereof) of the Product within [**] of Delivery of such Product, ARIAD SWISSCO shall be deemed to have accepted such shipment of the Product; provided, however, that in the case of the Product having any Latent Defect, ARIAD SWISSCO shall notify ARIAD US promptly once it becomes aware that a Product contains a Latent Defect and subsequently may reject such Product by giving written notice to ARIAD US of ARIAD SWISSCO’s rejection of such Product and shipping a representative sample of such Product or other evidence of Non-Conformance to ARIAD US within [**] after becoming aware of such Latent Defect, which notice shall include a description of the Latent Defect.

  • Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Teaching Load 11-1 The parties recognize that the number of students, the number of preparations, and the amount of planning time are related to student performance. 11-2 CLASS SIZE 11-2-1 The parties recognize that class size is related to economics and that reduction of class size is faced with fiscal constraints. The parties further recognize that it is not feasible at this time to set general numerical limitations upon class size because of physical space available, special programs, special student needs, attendance area variances, differences in scheduling systems, busing, and because of other variable causes affecting class size. Nevertheless, the parties shall make reasonable effort to maintain class size at reasonable, workable, and educationally effective levels in all situations. 11-3 TEACHER LOAD 11-3-1 Teaching load shall be defined as the number of separate class preparations that a teacher has per school day as delineated in the course description guide.

  • TEACHING HOURS AND TEACHING LOAD Section 1 Work Day For the applicable agreement period, the normal work day will be seven and one-quarter (7 ¼) hours including arrival time fifteen (15) minutes before and departure time (15) minutes after the students’ school day. The normal work day will include uninterrupted prep time. The Building Principal, as authorized by the Superintendent, upon request of a teacher or group of teachers, may waive the requirement to remain fifteen (15) minutes after the school day for a specific day or days. It is recognized; however, that the proper performance of their duties may, on occasion, require these persons to work longer than the normal work day, i.e. for conferences, faculty meetings, department meetings, etc. Therefore, “mandatory meetings will occur two times per month and be no longer than 90 minutes in length, inclusive of the additional 15 minutes beyond the scheduled student school day. A schedule of the meetings will be distributed by June 30th of the previous school year, but may be changed at the discretion of the Principal with 48 hours’ notice.” Teachers will also remain at school after the fifteen (15) minutes described above, during one (1) day each calendar week for such periods of time as is necessary to provide students extra help, and/or to meet with parents or guardians, concerning the progress of their children or wards. No teacher shall be required to work more than a normal seven and one- quarter (7 ¼) hour day, including fifteen (15) minutes before and (15) minutes after the students’ school day, which will include uninterrupted prep time; this provision does not apply to other contractually agreed upon time and meetings. Should state law require a longer instructional day, or more days, the teachers shall work the added time and the parties shall immediately commence impact bargaining on the issue. This article does not purport to cover the arrival and departure time of teachers involved in special assignments. Section 2 Other Personnel Personnel other than classroom teachers will work at their assigned tasks for the length of the regular teachers' work day. The exact daily schedule will be worked out on an individual basis between the Administration and the employee with notification to the Association. Instructional Coaches are required to work an additional five (5) days at their per diem rate, beyond the work year for a total of 189 days. These days will be determined prior to the start of the new school year and at the discretion of the Superintendent and the Chief Academic Officer.

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