Incompatibility with Certain Facsimile Devices Sample Clauses

Incompatibility with Certain Facsimile Devices. If Your business requires the use of Facsimile device(s) (“Fax devices”) You should be aware that both the ISP and/or the Fax device itself may not be capable of delivering satisfactory Fax operation with VoIP. Some older fax devices are incompatible due to delay sensitivity and therefore Voice Telco Services recommends the use of Fax devices no older than two years. Some ISP services deliver inadequate quality of service to allow for reliable Fax transmission. Voice Telco Services recommends that You always check with Your fax machine manufacturer and ISP service provider to determine their level of support for fax over VoIP.
View SourceView Similar (2)
Incompatibility with Certain Facsimile Devices. Fax adapters acquired from or through Voice Telco Services provide a port for connection to facsimile devices (“Fax Devices”). However, You should be aware that in some cases the Fax Device’s configuration may need to be modified by You to optimize its performance with VoIP. You should also be aware that some Fax Devices, some Internet Service Providers (ISPs) and some broadband data connections may not be capable of delivering satisfactory fax operation with VoIP. Some older Fax Devices are incompatible due to delay sensitivity, and therefore Voice Telco Services recommends the use of Fax Devices that are no older than two (2) years. Some ISP services deliver inadequate quality of service to allow for reliable fax transmission. Voice Telco Services recommends that You always check with Your Fax Device manufacturer and ISP to determine their level of support for fax over VoIP.
View Source

Related to Incompatibility with Certain Facsimile Devices

  • Transmission Delivery Service Implications Under ER Interconnection Service, Interconnection Customer will be eligible to inject power from the Generating Facility into and deliver power across the Transmission System on an “as available” basis up to the amount of MW identified in the applicable stability and steady state studies to the extent the upgrades initially required to qualify for ER Interconnection Service have been constructed. After that date FERC makes effective MISO’s Energy Market Tariff filed in Docket No. ER04-691-000, Interconnection Customer may place a bid to sell into the market up to the maximum identified Generating Facility output, subject to any conditions specified in the Interconnection Service approval, and the Generating Facility will be dispatched to the extent the Interconnection Customer’s bid clears. In all other instances, no transmission or other delivery service from the Generating Facility is assured, but Interconnection Customer may obtain Point-To-Point Transmission Service, Network Integration Transmission Service or be used for secondary network transmission service, pursuant to the Tariff, up to the maximum output identified in the stability and steady state studies. In those instances, in order for Interconnection Customer to obtain the right to deliver or inject energy beyond the Point of Interconnection or to improve its ability to do so, transmission delivery service must be obtained pursuant to the provisions of the Tariff. The Interconnection Customer’s ability to inject its Generating Facility output beyond the Point of Interconnection, therefore, will depend on the existing capacity of the Transmission or Distribution System as applicable, at such time as a Transmission Service request is made that would accommodate such delivery. The provision of Firm Point-To-Point Transmission Service or Network Integration Transmission Service may require the construction of additional Network or Distribution Upgrades.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

  • Electronic Monitoring All observations shall be conducted openly. Mechanical or electronic devices shall not be used to listen to or record the procedures of any class without the prior knowledge and consent of the teacher.