Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59
Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). 2.4.2.2 A UCL-D will be 18,000 feet or less in length and is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 Ohms of resistance. 2.4.2.3 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Telepak Networks. 2.4.2.4 These Loops are not intended to support any particular services and may be utilized by Telepak Networks to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire. 2.4.2.5 Upon the Effective Date of this Agreement, Unbundled Copper Loop – Long (UCL-L) elements will no longer be offered by BellSouth and no new orders for UCL-L will be accepted. Any existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to the Effective Date of this Agreement. Existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement may remain connected, maintained and repaired according to BellSouth’s TR73600 and may remain connected until such time as they are disconnected by Telepak Networks or BellSouth provides ninety
Directory Listings 15.1.1 CBT, as publisher of its White Pages, will include Primary Listings of CLEC’s resale directory customers in its White Pages, and shall cause its publisher to include primary listings of CLEC’s directory customers in its Publisher’s Yellow Pages Directories under the following terms and conditions: 15.1.1.1 CBT will publish the Primary Listing of CLEC Directory Customers located within the geographic scope of its White Pages directory and will recover costs for both resale and facility based Customers in accordance with the Act.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
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.
The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.
