CNAM Query Sample Clauses

CNAM Query. 12.2.3 The Parties understand that CLEC’s queries launched from SBC MISSOURI’s switches or other SBC MISSOURI’s Service Platforms contain an SBC MISSOURI’s Originating Point Code and, therefore, such Queries will identify SBC MISSOURI as the Query originator. The Parties further understand that all SBC UNEs and all interconnecting networks will respond to such Queries as though these Queries are SBC MISSOURI’s Queries. 12.2.4 SBC MISSOURI employs certain automatic and/or manual overload controls to protect SBC MISSOURI’s CCS/SS7 network. Network management controls found necessary to protect LIDB and/or CNAM Database from an overload condition will be applied based on non-discriminatory guidelines and procedures. Such management controls will be applied to the specific problem source to the extent technically feasible. 12.2.5 SBC MISSOURI’s LIDB contains a record for every SBC MISSOURI’s working line number and Special Billing Number. Other telecommunications companies, including CLEC, may also store their data in SBC MISSOURI’s LIDB. SBC MISSOURI will request such telecommunications companies to also provide a record for every working line number and Special Billing Number served by those companies. 12.2.6 SBC MISSOURI’s LIDB will provide the following functions on a per query basis: for Validation Queries: validation of a telecommunications calling card account number stored in LIDB; determination of whether the billed line has decided in advance to reject certain calls billed as collect or to a third number; and determination of billed line as a public (including those classified as semi public) or nonworking telephone number. 12.2.7 SBC MISSOURI provides LIDB as set forth in this Attachment only as such service is used for CLEC’s LSP activities on behalf of its MISSOURI local service customers where CLEC provides service to such end users from SBC MISSOURI’s UNE local switch ports or other SBC Service Platform. Any other use of SBC MISSOURI’s LIDB by CLEC will be pursuant to the terms, conditions, rates, and charges of a separate agreement, including effective tariffs, as revised. 12.2.7.1 In the event that CLEC is using SBC MISSOURI’s Service Platform, until otherwise agreed, no charge is made for LIDB Queries (e.g. Validation, OLNS, CNAM) other than applicable charges for the Service Platform under Appendix Pricing UNE – Schedule of Prices, unless the Commission determines in a subsequent proceeding that such costs are not recovered. 12.2.8 Telecommu...
AutoNDA by SimpleDocs
CNAM Query. 12.5.1 The parties acknowledge that each Calling Name database limits the Calling Name information length to fifteen (15) characters. As a result, the Calling Name information provided in a response to a Query may not reflect a subscriber’s full name. Name records of residential local telephone subscribers will generally be stored in the form of last name followed by first name (separated by a comma or space) to a maximum of fifteen (15) characters. Name records of business local telephone subscribers will generally be stored in the form of the first fifteen (15) characters of the listed business name that in some cases may include abbreviations. The Parties also acknowledge that certain local telephone service subscribers may require their name information to be restricted, altered, or rendered unavailable. 12.5.2 The Parties acknowledge that certain federal and/or state regulations require that local exchange telephone companies make available to their subscribers the ability to block the delivery of their telephone number and/or name information to the terminating telephone when the subscriber originates a telephone call. This blocking can either be on a call-by-call basis or on an every call basis. Similarly, a party utilizing blocking services can unblock on a call-by-call or every call basis. CLEC will abide by information received in SS7 protocol during call set-up that the calling telephone service subscriber wishes to block or unblock the delivery of telephone number and/or name information to a CNDS subscriber. XXXX agrees not to attempt to obtain the caller’s name information by originating a query to SBC MISSOURI’s Calling Name database where the subscriber had attempted to block such information, nor will CLEC block information a subscriber has attempted to unblock.
CNAM Query. With the exception of AT&T SOUTHWEST REGION 5-STATE and AT&T MIDWEST REGION 5-STATE, GetData and OLNS Query access to SNET DG’s LIDB will be pursuant to a separate agreement between Customer and SNET DG.
CNAM Query. 2.1.1 Per Query $.008

Related to CNAM Query

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

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Customer List The Administrative Agent shall have received a true and complete customer list for each Borrower and its Domestic Subsidiaries, which list shall state the customer’s name, mailing address and phone number and shall be certified as true and correct in all material respects by a Financial Officer of the Borrower Representative.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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