LIDB Query Service Clause Samples

LIDB Query Service. 9.15.3.1 Description - LIDB Query Service 9.15.3.1.1 LIDB Query Service provides information to query originators for use in processing Alternately Billed Services (ABS) calls. ABS call types include calling card, billed to third number, and collect calls. 9.15.3.1.2 On behalf of CLEC, Qwest will process LIDB queries from query originators (Telecommunications Carriers) requesting CLEC telephone line number data. Qwest allows LIDB query access through Qwest regional STPs. 9.15.3.2 Terms and Conditions - LIDB Query Service 9.15.3.2.1 All LIDB queries and responses from operator services systems and end offices are transmitted over a CCS network using a Signaling System 7 (SS7) protocol (TR-NWT-000246, ▇▇▇▇ Communications Research Specification of Signaling System 7). 9.15.3.2.2 The application data needed for processing LIDB data are formatted as Transaction Capabilities Application Part (TCAP) messages. TCAP messages may be carried as an application level protocol using SS7 protocols for basic message transport. 9.15.3.2.3 The SCP node provides all protocol and interface support. CLEC SS7 connections will be required to meet Telcordia’s GR905, TR954 and Qwest’s Technical Publication 77342 specifications. 9.15.3.2.4 Qwest will include CLEC-provided data in Qwest’s LIDB in accordance with section 9.15.1 (LIDB Storage), and allow access to the data subject to Qwest negotiated agreements with Telecommunications Carriers, allowing CLEC's End Users the same benefits of said agreements as enjoyed by Qwest End Users. Qwest will update CLEC data, as requested by CLEC. Qwest will perform services provided hereunder and determine the applicable standard for the data, in accordance with operating methods, practices and standards in effect. Qwest shall exercise reasonable efforts to provide accurate and complete LIDB information in Qwest’s LIDB.
View SourceView Similar (2)
LIDB Query Service 
View Source

Related to LIDB Query Service

  • Our Service The services that you have selected and the charges for those services are confirmed in Section 9 - Your Consent at the end of this agreement. We agree to provide the services selected and you agree to pay us for those services. Any advice or recommendation that we offer to you, will only be given after we have assessed your needs and considered your financial objectives and attitude to any risks that may be involved. We will also take into account any restrictions that you wish to place on the type of products you would be willing to consider.

  • Internet Service In the event that internet is required during your stay, please verify that the Property selected provides the service. Rules of the House: In the event there are rules specific to your Property either required by the Owner or if applicable from an HOA, they will be posted at the home and your compliance is necessary. Rental Unit for Sale: Occasionally a Property may go on the market for sale. In such cases Agent reserves the right to show the Property to potential buyers. Agent will make every effort to schedule the showing at a time that is convenient for Tenant, so as not to interrupt your vacation. Tenant’s cooperation is appreciated. Consumable Products: Paper products, laundry/dish detergent, personal toiletry items and food staples are not included in the Properties. Linens: Linens are included with all Properties for reservations up to 2 days or more. If linens and towels are damaged or missing there will be an added fee to replace and/or clean those items. Linens and towels should only be used for sleeping in and drying off. Damaged or missing bath towels are $25, hand towels are $15, wash cloths are $10, sheets are $30, pillow cases are $15, and bath mats are $20. Damaged items might include makeup, blood stains, excessive dirt, tanning lotion, and human waste.

  • CLOUD SERVICE The Cloud Service offering, is described below and is specified in an Order Document for the selected entitled offerings. The Order Document will consist of the Quotation that is provided and the Proof of Entitlement (▇▇▇) you will receive confirming the start date and term of the Cloud Services and when invoicing will commence.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, 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.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.