Toll Free Number Database. 51.6.1. The Toll Free Number Database provides functionality necessary for toll free (e.g., 800 and 888) number services by providing routing information and additional vertical features (i.e., time of day routing by location, by carrier and routing to multiple geographic locations) during call setup in response to queries from STPs. The Toll Free records stored in Sprint’s database are downloaded from the SMS/800. Sprint shall provide the Toll Free Number Database in accordance with the following: 51.6.1.1. Sprint shall make the Sprint Toll Free Number Database available for CLEC to query in the same manner, and via the same signaling links, as Sprint where CLEC purchases unbundled local circuit switching, to the extent that that local circuit switching is required to be unbundled by the Commission or FCC. 51.6.1.2. The Toll Free Number Database shall return CLEC identification and, where applicable, the queried toll free number, translated numbers and instructions as it would in response to a query from a Sprint switch. 51.6.1.3. Sprint will provide access to its Toll Free Number Database for purpose of receiving and responding to queries, where CLEC purchases unbundled local circuit switching for a particular end user, at no additional charge.

Toll Free Number Database. 52.5.1 The Toll Free Number Database provides functionality necessary for toll free (e.g., 800 and 888) number services by providing routing information and additional vertical features (i.e., time of day routing by location, by carrier and routing to multiple geographic locations) during call setup in response to queries from STPs. The Toll Free records stored in Sprint’s database are downloaded from the SMS/800. Sprint shall provide the Toll Free Number Database in accordance with the following:

See All (6)

Toll Free Number Database. The Toll Free Number Database is a SCP that provides functionality necessary for toll free (e.g., 800 and 888) number services by providing routing information and additional so-called vertical features during call set-up in response to queries from SSPs. GTE shall provide the Toll Free Number Database in accordance with the following: 11.4.1. Technical References (subject to Section 23.19 of the General Terms and Conditions of this Agreement): 11.4.1.1. GTE shall make the GTE Toll Free Number Database available for AT&T to query with a toll-free number and originating information. 11.4.1.2. The Toll Free Number Database shall return carrier identification and, where applicable, the queried toll free number, translated numbers and instructions as it would in response to a query from a GTE switch. 11.4.2. Signaling Interface References (subject to Section 23.19 of the General Terms and Conditions of this Agreement): The signaling interface between the AT&T or other local switch and the Toll-Free Number database shall use the TCAP protocol as specified in the technical reference listed in Appendix A to this Attachment 2, at paragraph 10.1, together with the signaling network interface as specified in the technical reference listed in Appendix A to this Attachment 2, at paragraphs 10.2. and 10.6.

Toll Free Number Database. The "Toll Free Number Database" is an SCP that provides functionality necessary for toll free (e.g., 800 and 888) number services by providing routing information and additional features during call set-up in response to queries from SSPs. This Section 11.6 supplements the other requirements of Section 11. Verizon shall provide the Toll Free Number Database in accordance with the following: Verizon shall make the Verizon Toll Free Number Database available for MCIm to query, from MCIm’s designated switch including Local Switching, with a toll-free number and originating information. The Toll Free Number Database shall return carrier identification and, where applicable, the queried toll free number, translated numbers and instructions as it would in response to a query from a Verizon switch.

Related to Toll Free Number Database

Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.
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.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification. 2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length. 2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A. 2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties. 2.5.5 Rates for ULM are as set forth in Exhibit A. 2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered. 2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned. 2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition. 2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:
Number, etc Words importing the singular number include the plural and vice versa, words importing the use of any gender include all genders, and words importing persons include firms and corporations and vice versa.

Toll Free Number Database Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Sub-Clauses

Related to Toll Free Number Database