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.
Appears in 2 contracts
Samples: Telecommunications, Telecommunications
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 Peering Hub Inc.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.
Appears in 1 contract
Samples: Peering Agreement
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.. CN:04072021-10285 000069
Appears in 1 contract
Samples: Telecommunications