DIRECTORY LISTINGS AND DISTRIBUTION SERVICES Sample Clauses

DIRECTORY LISTINGS AND DISTRIBUTION SERVICES. 1.1 Carrier agrees to provide to Frontier or its publisher, as specified by Frontier, all subscriber list information (including additions, changes and deletions) for Carrier’s End Users and those of any resellers of Carrier services, located within Frontier’s operating areas. It is the responsibility of the Carrier to submit directory listings in the prescribed manner to Frontier prior to the directory listing publication cut- off date, which is posted at xxx.Xxxxxxxx.xxx under Carrier Services then Directory Services.
AutoNDA by SimpleDocs
DIRECTORY LISTINGS AND DISTRIBUTION SERVICES. 1.1 CLC agrees to provide to Frontier or its publisher, as specified by Frontier, all subscriber list information (including additions, changes and deletions) for CLC ’s End Users and those of any resellers of CLC services, located within Frontier’s operating areas. It is the responsibility of CLC to submit directory listings in the prescribed manner to Frontier prior to the directory listing publication cut-off date, which is posted at xxx.Xxxxxxxx.xxx under CLC Services then Directory Services.
DIRECTORY LISTINGS AND DISTRIBUTION SERVICES. 1.1 MetTel agrees to provide to Frontier or its publisher, as specified by Frontier, all subscriber list information (including additions, changes and deletions) for MetTel’s End Users and those of any resellers of MetTel services, located within Frontier’s operating areas. It is the responsibility of the MetTel to submit directory listings in the prescribed manner to Frontier prior to the directory listing publication cut- off date, which is posted at xxx.Xxxxxxxx.xxx under MetTel Services then Directory Services.
DIRECTORY LISTINGS AND DISTRIBUTION SERVICES. 1.1 CC agrees to provide to Frontier or its publisher, as specified by Frontier, all subscriber list information (including additions, changes and deletions) for CC’s End Users and those of any resellers of CC services, located within Frontier’s operating areas. It is the responsibility of CC to submit directory listings in the prescribed manner to Frontier prior to the directory listing publication cut-off date, which is posted at xxx.Xxxxxxxx.xxx under CC Services then Directory Services.
DIRECTORY LISTINGS AND DISTRIBUTION SERVICES. 1.1 BUB agrees to provide to Frontier or its publisher, as specified by Frontier, all subscriber list information (including additions, changes and deletions) for BUB’s End Users and those of any resellers of BUB services, located within Frontier’s operating areas. It is the responsibility of BUB to submit directory listings in the prescribed manner to Frontier prior to the directory listing publication cut-off date, which is posted at xxx.Xxxxxxxx.xxx under carrier Services then Directory Services.
DIRECTORY LISTINGS AND DISTRIBUTION SERVICES. 1.1 Carrier agrees to provide to Citizens, as specified by Citizens, all subscriber list information (including additions, changes and deletions) for Carrier’s End User and those of any resellers of Carrier services, located within Citizens operating areas. All Frontier and Citizens area listing information can be entered into the Citizens GUI system. It is the responsibility of the Carrier to submit directory listings in the prescribed manner to Citizens prior to the directory listing publication cut-off date, which is posted at xxx.xxxxxxxxxxxxxx.xxx under Carrier Services then Directory Services.

Related to DIRECTORY LISTINGS AND DISTRIBUTION SERVICES

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

  • Routing for Operator Services and Directory Assistance Traffic For a Verizon Telecommunications Service dial tone line purchased by Ygnition for resale pursuant to the Resale Attachment, upon request by Ygnition, Verizon will establish an arrangement that will permit Ygnition to route the Ygnition Customer’s calls for operator and directory assistance services to a provider of operator and directory assistance services selected by Ygnition. Verizon will provide this routing arrangement in accordance with, but only to the extent required by, Applicable Law. Verizon will provide this routing arrangement pursuant to an appropriate written request submitted by Ygnition and a mutually agreed-upon schedule. This routing arrangement will be implemented at Ygnition's expense, with charges determined on an individual case basis. In addition to charges for initially establishing the routing arrangement, Ygnition will be responsible for ongoing monthly and/or usage charges for the routing arrangement. Ygnition shall arrange, at its own expense, the trunking and other facilities required to transport traffic to Ygnition’s selected provider of operator and directory assistance services.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Network Upgrades and Distribution Upgrades The Participating TO shall design, procure, construct, install, and own the Network Upgrades and Distribution Upgrades described in Appendix A. The Interconnection Customer shall be responsible for all costs related to Distribution Upgrades. Unless the Participating TO elects to fund the capital for the Distribution Upgrades and Network Upgrades, they shall be solely funded by the Interconnection Customer.

  • Support Services HP’s support services will be described in the applicable Supporting Material, which will cover the description of HP’s offering, eligibility requirements, service limitations and Customer responsibilities, as well as the Customer systems supported.

  • Online Services Microsoft warrants that each Online Service will perform in accordance with the applicable SLA during Customer’s use. Customer’s remedies for breach of this warranty are in the SLA. The remedies above are Customer’s sole remedies for breach of the warranties in this section. Customer waives any breach of warranty claims not made during the warranty period.

Time is Money Join Law Insider Premium to draft better contracts faster.