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.
Local Number Portability. Number Portability Generic Switching and Signaling Requirements for Number Portability, Issue 1.00, February 12, 1996 (Editor – Lucent Technologies, Inc.); Generic Requirements for SCP Application and GTT Function for Number Portability, Issue 0.95, Final Draft, September 4, 1996 (Editor – Ameritech Inc.); Generic Operator Services Switching Requirements for Number Portability, Issue 1.00, Final Draft, April 12, 1996 (Editor – Nortel); ATIS, TRQ No. 1, Technical Requirements for Number Portability Operator Services Switching Systems, April 1999; ATIS, TRQ No. 2, Technical Requirements for Number Portability Switching Systems, April 1999; ATIS, TRQ No. 3, Technical Requirements for Number Portability Database and Global Title Translation, April 1999; FCC First Report and Order and Further Notice of Proposed Rulemaking; FCC 96-286; CC Docket 95-116, RM 8535; Released July 2, 1996; FCC First Memorandum Opinion and Order on Reconsideration; XXX 00-00; XX Xxxxxx 00-000, XX 0000; Released March 11, 1997. FCC Second Report and Order, FCC 97-298; CC Docket 95-116, RM 8535; Released August 18, 1997.
Local Number Portability. In the event you are transferring an existing phone number that currently is subscribed to another carrier, the following terms and conditions apply:
Local Number Portability. Normal porting hours are Monday-Friday, 8AM-4PM. Any ports requested outside of this window can be accommodated in most cases but will be billed a one-time charge of $150. We do not honor port requests for any voice services on Fridays unless otherwise approved by Telesystem management and the Customer.
Local Number Portability. If you are transferring your existing phone number from another service provider for use with the Service, the following terms and conditions also shall apply:
Local Number Portability. Customer is solely responsible for compliance with all applicable FCC rules and policies regarding LNP and telephone numbering resources, and shall, on a timely basis, provide to Peak Unified Communications, upon Peak Unified Communications’s request, with any and all requested utilization information, including copies of the Customer’s FCC Form 502s, for all telephone numbers provided by Peak Unified Communications to Customer pursuant to this Agreement. Upon request by Peak Unified Communications or a New Local Service Provider (“NLSP”), Customer shall, on a timely basis, provide Peak Unified Communications and the NLSP with the Customer Service Record (“CSR”) for any telephone number provided by Peak Unified Communications to Customer pursuant to this Agreement. Upon receipt of a Local Service Request (“LSR”) from a NLSP or a New Network Service Provider (“NNSP”), or from Peak Unified Communications on behalf of a NLSP or NNSP, Customer shall return a Firm Order Confirmation (“FOC”) or, in the event the LSR contains any error, a rejection and error notification to Peak Unified Communications and the NLSP or NNSP within 24 hours unless the Customer receives the request on Friday, Saturday, Sunday or a national holiday, in which case Customer shall return the FOC or rejection and error notification to Peak Unified Communications and the NLSP or NNSP within 24 hours of 9:00 am the next business day. Upon receipt of a LSR from a NLSP or NNSP for any telephone number provided by Peak Unified Communications to Customer pursuant to this Agreement, Peak Unified Communications shall forward the LSR to the Customer. If Customer receives an LSR from a NLSP, NNSP or Peak Unified Communications on behalf of a NLSP or NNSP but fails, on a timely basis, to return a FOC or rejection and error notification to the NLSP or NNSP and Peak Unified Communications, Peak Unified Communications may, at its sole discretion, return a FOC to the NLSP or NNSP on behalf of Customer.
Local Number Portability. Customer is solely responsible for compliance with all applicable FCC rules and policies regarding LNP and telephone numbering resources, and shall, on a timely basis, provide to SimpleCom, upon SimpleCom’s request, with any and all requested utilization information, including copies of the Customer’s FCC Form 502s, for all telephone numbers provided by SimpleCom to Customer pursuant to this Agreement. Upon request by SimpleCom or a New Local Service Provider (“NLSP”), Customer shall, on a timely basis, provide SimpleCom and the NLSP with the Customer Service Record (“CSR”) for any telephone number provided by SimpleCom to Customer pursuant to this Agreement. Upon receipt of a Local Service Request (“LSR”) from a NLSP or a New Network Service Provider (“NNSP”), or from SimpleCom on behalf of a NLSP or NNSP, Customer shall return a Firm Order Confirmation (“FOC”) or, in the event the LSR contains any error, a rejection and error notification to SimpleCom and the NLSP or NNSP within 24 hours unless the Customer receives the request on Friday, Saturday, Sunday or a national holiday, in which case Customer shall return the FOC or rejection and error notification to SimpleCom and the NLSP or NNSP within 24 hours of 9:00 am the next business day. Upon receipt of a LSR from a NLSP or NNSP for any telephone number provided by SimpleCom to Customer pursuant to this Agreement, SimpleCom shall forward the LSR to the Customer. If Customer receives an LSR from a NLSP, NNSP or SimpleCom on behalf of a NLSP or NNSP but fails, on a timely basis, to return a FOC or rejection and error notification to the NLSP or NNSP and SimpleCom, SimpleCom may, at its sole discretion, return a FOC to the NLSP or NNSP on behalf of Customer.
Local Number Portability. 2.4.1 Ameritech's provision of LNP will utilize LRN switch software based on requirements developed by the workshop participants and concurred in by the Commission. These requirements are fully compliant with the principles adopted by the FCC in its First Report and Order, CC Docket No. 95-116 (the Number Portability Order). The detailed description and technical specifications for the planned LRN implementation can be found in various documents produced by the FCC Local Number Portability workshop.
2.4.2 Ameritech is fully prepared to provide LNP database access to CLEC. However, in adopting its Number Portability Order, the FCC referred certain technical and other issues to the North American Numbering Council (NANC) and issued a further notice addressing the recovery of costs associated with LNP implementation. Until these activities are concluded, Ameritech cannot finalize product descriptions and rates for access to its LNP database. Nonetheless, Ameritech is willing to begin discussions with CLEC to discuss CLEC's access to Ameritech's LNP databases in lieu of constructing CLEC's own.
Local Number Portability. Both Parties shall abide by the rules and regulations of the Federal Communications Commission and applicable state public utility commission rules and regulations to port numbers from and to each other.
Local Number Portability. 11.1 The Telecommunications Numbering Plan sets out the framework for the numbering of carriage services in Australia and the use of numbers in connection with the supply of such services.
11.2 You expressly acknowledge and agree that:
(a) you do not own or receive any legal interest or goodwill in any telephone number that is provided to you in connection with this Service; and
(b) you are entitled to use any telephone number that is provided to you in connection with this Service (subject to the terms and conditions of this Contract and any right that we may have under the Telecommunications Numbering Plan to recover that telephone number from you).
