Requirements for LNP. 3.1.1 The Parties shall provide to each other, on a reciprocal basis, number portability in accordance with requirements of the Act and FCC Rules and Orders.
Requirements for LNP. 3.1.1 The Parties shall provide to each other, on a reciprocal basis, number portability in accordance with requirements of the Act and FCC Rules and Orders.
3.1.2 Telephone numbers assigned to mass calling events shall be handled in compliance with the industry’s non- LRN recommendation (NANC’s High Volume Call-in Network dated February 18, 1998). The Parties agree that if any of these guidelines change, the Parties will use commercially reasonable efforts to comply with such changes.
3.1.3 Each Party shall be an End User’s service provider for all of the End User’s Telecommunications-related services and features, including but not limited to, industry notifications, Directory Listings, E911, Line Information Database (LIDB), and Operator Services), once the End User’s telephone number has been ported to that Party’s network.
3.1.4 Should WSP purchase and/or access the SPNP Database Query service from AT&T-21STATE, the Parties agree the purchase and/or access will be pursuant to the applicable AT&T-21STATE tariff or Guidebook and nothing in this Attachment addresses such service.
3.1.5 Unless a separate agreement is negotiated by the Parties, neither Party can order Directory Listings with LNP.
3.1.6 If a Party queries an LNP database, that Party will change the Forward Call Identifier (FCI) field’s entry from
3.1.7 Where technically feasible, the Parties shall populate the Jurisdiction Information Parameter (JIP) field with the first six (6) digits (NPA NXX format) of the appropriate LRN of the originating switch.
3.1.8 The Parties shall not charge each other for the porting of telephone numbers as a means for the other to recover the costs associated with LNP.
Requirements for LNP. 3.1.1 The Parties shall provide to each other, on a reciprocal basis, number portability in accordance with requirements of the Act and FCC Rules and Orders.
3.1.2 The Parties shall follow industry guidelines, including but not limited to North American Numbering Council (NANC) Inter Service Provider Operations Flows, located on the Number Portability Administration Center's (NPAC) website, regarding LNP for all aspects of number portability, including the time frames for providing porting services to one another.
3.1.3 Either Party shall be permitted to block default-routed calls to protect the public switched telephone network from overload, congestion, or failure propagation.
3.1.4 When a ported telephone number becomes vacant, e.g., the telephone number is no longer in service with the original End User; the ported telephone number will be released back to the carrier owning the switch (after aging if any) in which the telephone number’s NXX-X is native.
3.1.5 Each Party shall be responsible for their own End User’s other Telecommunications related services and features, e.g. E911, Directory Listings, Operator Services, once that Party has ported the End User’s telephone number to the Party’s switch.
3.1.6 When purchasing the SPNP Database Query, WSP will access AT&T-22STATE Facilities via an SS7 link.
Requirements for LNP. 3.1.1 The Parties shall provide to each other, on a reciprocal basis, number portability in accordance with requirements of the Act and FCC Rules and Orders.
3.1.2 The Parties shall follow industry guidelines, including but not limited to North American Numbering Council (NANC) Inter Service Provider Operations Flows, located on the Number Portability Administration Center's (NPAC) website, regarding LNP for all aspects of number portability, including the time frames for providing porting services to one another.
3.1.3 Either Party shall be permitted to block default-routed calls to protect the public switched telephone network from overload, congestion, or failure propagation.
3.1.4 When a ported telephone number becomes vacant (e.g., the telephone number is no longer in service with the original End User), the ported telephone number will be released back to the carrier owning the switch (after aging if any) in which the telephone number’s NXX-X is native.
3.1.5 Each Party shall be responsible for the End User’s other Telecommunications related services and features, (e.g., Directory Listings, E911, Line Information Database (LIDB), Operator Services), once that Party has ported the End User’s telephone number to the Party’s switch.
3.1.6 When purchasing the SPNP Database Query, CLEC will access AT&T-21STATE facilities via an SS7 link.
3.1.7 Where triggers are not set, the Parties shall coordinate the porting of the number between service providers so as to minimize service interruptions to the End User.
Requirements for LNP. 3.1.1 The Parties shall provide to each other, on a reciprocal basis, number portability in accordance with requirements of the Act and FCC Rules and Orders.
3.1.2 The Parties shall follow industry guidelines, including but not limited to North American Numbering Council (NANC) Inter Service Provider Operations Flows, located on the Number Portability Administration Center’s (NPAC) website, regarding LNP for all aspects of number portability, including the time frames for providing porting services to one another. Page 68 of 247 365 WIRELESS, LLC
3.1.3 Either Party shall be permitted to block default-routed calls to protect the public switched telephone network from overload, congestion, or failure propagation.
3.1.4 When a ported telephone number becomes vacant (e.g., the telephone number is no longer in service with the original End User); the ported telephone number will be released back to the carrier owning the switch (after aging if any) in which the telephone number’s NXX-X is native.
Requirements for LNP. (1) The Parties shall provide to each other number portability (LNP) on a reciprocal basis and in accordance with FCC orders, rules and regulations, and North American Numbering Council (NANC) guidelines and recommendations adopted by the FCC.
(2) The Parties shall follow industry guidelines, including but not limited to North American Numbering Council (NANC) Inter Service Provider Operations Flows, located on the Number Portability Administration Center’s (NPAC) website, regarding LNP for all aspects of number portability, including the time frames for providing porting services to one another.
(3) The Parties will work cooperatively to implement any additional FCC ordered portability rules in the timeline outlined in any such order. If a Party acts as a numbering partner that Party is fully responsible for compliance with porting rules as defined in this Section 10.A.1 and 10.A.2
(4) If either Party’s operations procedures conflict with the FCC’s rules and orders, the FCC’s rules and orders will prevail.
(5) This Agreement does not allow portability where the End User Customer moves outside the rate center.
(6) When a ported telephone number becomes vacant (e.g., the telephone number is no longer in service with the original End User); the ported telephone number will be released back to the carrier owning the switch (after aging and including applicable transfer of calls recording, if any) in which the telephone number’s NXX-X is native.
(7) Each Party shall be responsible for their own End User’s other Telecommunications related services and features (e.g. E911, Directory Listings, Operator Services), once that Party has ported the End User’s telephone number to the Party’s switch.
Requirements for LNP
