Local Number Portability Local Routing Query Service Sample Clauses

Local Number Portability Local Routing Query Service. TCAP messages originated by CLEC’s SSPs and received by Embarq’s database will be provided a response upon completion of a database lookup to determine the LRN. This information will be populated in industry standard format and returned to CLEC so that it can then terminate the call in progress to the telephone number now residing in the switch designated by the LRN. (a) CLEC agrees to obtain, prior to the initiation of any LNP query, a NPAC/SMS User Agreement with Neustar. CLEC will maintain the NPAC/SMS User Agreement with Neustar, or its successor, as long as it continues to make LNP queries to the Embarq database. Failure to obtain and maintain the NPAC/SMS User Agreement is considered a breach of this Agreement and is cause for immediate termination of service. Embarq shall not be liable for any direct or consequential damages due to termination because of lack of a NPAC/SMS User Agreement. (b) Embarq's LNP Database service offering does not include the cost of any charges or assessments by Number Portability Administrative Centers, whether under the NPAC/SMS User Agreement with Lockheed, or otherwise, or any charges assessed directly against CLEC as the result of the FCC LNP Orders or otherwise by any third-party. These costs include the costs assessed against telecommunications carriers to pay for NPAC functions as permitted by the FCC and applicable legal or regulatory bodies. Embarq shall have no liability to CLEC or the NPAC for any of these fees or charges applicable to CLEC, even though it may pay such charges for other Embarq companies.
Sample 1Sample 2Sample 3See All (57)
Local Number Portability Local Routing Query Service. 52.6.1. TCAP messages originated by CLEC’s SSPs and received by Sprint’s database will be provided a response upon completion of a database lookup to determine the LRN. This information will be populated in industry standard format and returned to CLEC so that it can then terminate the call in progress to the telephone number now residing in the switch designated by the LRN. Sprint shall provide the LNP Query Service in accordance with the following:
Sample 1Sample 2Sample 3See All (11)
Local Number Portability Local Routing Query Service. TCAP messages originated by CLEC’s SSPs and received by Sprint’s database will be provided a response upon completion of a database lookup to determine the LRN. This information will be populated in industry standard format and returned to CLEC so that it can then terminate the call in progress to the telephone number now residing in the switch designated by the LRN. 69.1.3.1. CLEC agrees to obtain, prior to the initiation of any LNP query, a NPAC/SMS User Agreement with Neustar. CLEC will maintain the NPAC/SMS User Agreement with Neustar, or its successor, as long as it continues to make LNP queries to the Sprint database. Failure to obtain and maintain the NPAC/SMS User Agreement is considered a breach of this Agreement and is cause for immediate termination of service. Sprint shall not be liable for any direct or consequential damages due to termination because of lack of a NPAC/SMS User Agreement. 69.1.3.2. Sprint's LNP Database service offering does not include the cost of any charges or assessments by Number Portability
Sample 1Sample 2Sample 3See All (4)
Local Number Portability Local Routing Query Service. TCAP messages originated by Level 3’s SSPs and received by Embarq’s database will be provided a response upon completion of a database lookup to determine the LRN. This information will be populated in industry standard format and returned to Level 3 so that it can then terminate the call in progress to the telephone number now residing in the switch designated by the LRN.
Sample 1
Local Number Portability Local Routing Query Service. TCAP messages originated by AT&T’s SSPs and received by Sprint’s database will be provided a response upon completion of a database lookup to determine the LRN. This information will be populated in industry standard format and returned to AT&T so that it can then terminate the call in progress to the telephone number now residing in the switch designated by the LRN. 69.1.3.1. AT&T agrees to obtain, prior to the initiation of any LNP query, a NPAC/SMS User Agreement with Neustar. AT&T will maintain the NPAC/SMS User Agreement with Neustar, or its successor, as long as it continues to make LNP queries to the Sprint database. Failure to obtain and maintain the NPAC/SMS User Agreement is considered a breach of this Agreement and is cause for immediate termination of service. Sprint shall not be liable for any direct or consequential damages due to termination because of lack of a NPAC/SMS User Agreement. 69.1.3.2. Sprint's LNP Database service offering does not include the cost of any charges or assessments by Number Portability Administrative Centers, whether under the NPAC/SMS User Agreement with Lockheed, or otherwise, or any charges assessed directly against AT&T as the result of the FCC LNP Orders or otherwise by any third-party. These costs include the costs assessed against telecommunications carriers to pay for NPAC functions as permitted by the FCC and applicable legal or regulatory bodies. Sprint shall have no liability to AT&T or the NPAC for any of these fees or charges applicable to AT&T, even though it may pay such charges for other Sprint companies.
Sample 1
Local Number Portability Local Routing Query Service. TCAP messages originated by CLEC’s SSPs and received by Embarq ILEC’s database will be provided a response upon completion of a database lookup to determine the LRN. This information will be populated in industry standard format and returned to CLEC so that it can then terminate the call in progress to the telephone number now residing in the switch designated by the LRN. 68.1.3.1. CLEC agrees to obtain, prior to the initiation of any LNP query, a NPAC/SMS User Agreement with Neustar. CLEC will maintain the NPAC/SMS User Agreement with Neustar, or its successor, as long as it continues to make LNP queries to the Embarq ILEC database. Failure to obtain and maintain the NPAC/SMS User Agreement is considered a breach of this Agreement and is cause for immediate termination of
Sample 1

Related to Local Number Portability Local Routing Query Service

  • Local Number Portability The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. PNP is currently being worked in industry forums. The results of these forums will dictate the industry direction of PNP. BellSouth will provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • Number Portability Each Party shall adopt or maintain measures to ensure that suppliers of public telecommunications networks or services in its territory provide number portability on a timely basis, and on reasonable terms and conditions for mobile services and any other services as designated by that Party.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to Reconex for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent, that such Verizon Telecommunications Service is provided to Verizon’s Customers. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw, Verizon Telecommunications Services at any time, without the consent of Reconex. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to Reconex for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by Reconex.

  • Transmission and Routing of Telephone Exchange Service Traffic 50.4.1 The Appendix Reciprocal Compensation, which is/are attached hereto and incorporated herein by reference, prescribe traffic routing parameters for Local Interconnection Trunk Group(s) the Parties shall establish over the Interconnections specified in the Appendix ITR, which is/are attached hereto and incorporated herein by reference.

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • Switching System Hierarchy and Trunking Requirements For purposes of routing PNG traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to PNG, the subtending arrangements between PNG Tandem Switches and PNG End Office Switches shall be the same as the Tandem/End Office subtending arrangements that PNG maintains for the routing of its own or other carriers’ traffic.