CHANGES IN END USER LOCAL EXCHANGE SERVICE Sample Clauses

CHANGES IN END USER LOCAL EXCHANGE SERVICE. PROVIDER SELECTION
Sample 1Sample 2Sample 3See All (29)
AutoNDA by SimpleDocs
CHANGES IN END USER LOCAL EXCHANGE SERVICE. PROVIDER SELECTION 24.1 SBC-ILEC (Excluding SNET) 24.1.1 Each Party will abide by applicable federal and state laws and regulations in obtaining End User authorization prior to changing an End User’s Local Exchange Carrier to itself and in assuming responsibility for any applicable charges as specified in Section 258(b) of the Telecommunications Act of 1996. Each Party shall deliver to the other Party a representation of authorization that applies to all orders submitted by a Party under this Agreement requiring a LEC change. A Party's representation of authorization shall be delivered to the other Party prior to the first order submitted to the other Party. Each Party shall retain on file all applicable letters and other documentation of authorization relating to its End User’s selection of such Party as its LEC, which documentation shall be available for inspection by the other Party at its request during normal business hours and at no charge. 24.1.2 Only an End User can initiate a challenge to a change in its LEC. If an End User notifies one Party that the End User requests local exchange service, and the other Party is such End User’s LEC, then the Party receiving such request shall be free to immediately access such End User’s CPNI subject to the requirements of the applicable Appendix OSS restricting access to CPNI in order to immediately provide service to such End User. 24.1.3 When an End User changes or withdraws authorization from its LEC, each Party shall release End User-specific facilities belonging to the ILEC in accordance with the End User’s direction or that of the End User’s authorized agent. Further, when an End User abandons its premise (that is, its place of business or domicile), SBC-ILEC is free to reclaim the unbundled Network Element facilities for use by another End User and is free to issue service orders required to reclaim such facilities.
Sample 1Sample 2See All (8)
CHANGES IN END USER LOCAL EXCHANGE SERVICE. PROVIDER SELECTION 24.1 Applies to SBC-12STATE only
Sample 1
CHANGES IN END USER LOCAL EXCHANGE SERVICE. PROVIDER SELECTION 24.1 Applies to SBC-12STATE only 1.1 Each Party will abide by applicable federal and state laws and regulations in obtaining End User authorization prior to changing an End User’s Local Exchange Carrier to itself and in assuming responsibility for any applicable charges as specified in the FCC’s rules regarding Subscriber Carrier Selection Changes (47 CFR 64.1100 through 64.1170) and any applicable state regulation. Each Party shall deliver to the other Party a representation of authorization that applies to all orders submitted by a Party under this Agreement requiring a LEC change. A Party's representation of authorization shall be delivered to the other Party prior to the first order submitted to the other Party. Each Party shall retain on file all applicable letters and other documentation of authorization relating to its End User’s selection of such Party as its LEC, which documentation shall be available for inspection by the other Party at its request during normal business hours and at no charge.
Sample 1
CHANGES IN END USER LOCAL EXCHANGE SERVICE. PROVIDER SELECTION ------------------------------------------------------------- Each Party will abide by applicable state or federal laws and regulations in obtaining End User authorization prior to changing End User's local service provider to itself and in assuming responsibility for any applicable charges as specified in Section 258(b) of the Telecommunications Act of 1996. CLEC shall make authorization available to PACIFIC upon request and at no charge. Only an End User can initiate a challenge to a change in its local exchange service provider. If an End User notifies PACIFIC or CLEC that the End User requests local exchange service, the Party receiving such request shall be free to immediately provide service to such End User. When an End User changes or withdraws authorization, each Party shall release customer-specific facilities in accordance with the End User's direction or the End User's authorized agent. Further, when an End User abandons the premise, PACIFIC is free to reclaim the unbundled network element facilities for use by another customer and is free to issue service orders required to reclaim such facilities. GENERAL AND CONDITIONS PAGE 26 OF 48 PACIFIC/PAC-WEST TELECOM 022499
Sample 1

Related to CHANGES IN END USER LOCAL EXCHANGE SERVICE

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

  • 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!