Switching System Generic Requirements Sample Clauses

Switching System Generic Requirements. Issue 1, August 1992, and Bulletin 1, March 1993. Bellcore GR-1298-CORE, AINGR: Switching System, Issue 3, July 1996, and Revision 1, November 1996. Bellcore GR-1299-CORE, AINGR: Switch Service Control Point (“SCP”) Adjunct Interface, Issue 3, July 1996, and revision 1, November 1996. Bellcore GR-2863-CORE, CCS Network Interface Specification Supporting Advanced Intelligent Network (“AIN”), Issue 2, December 1995. Bellcore GR-2902-CORE, CCS Network Interface Specification (“CCSNIS”) Supporting Toll-Free Service Using AIN, Issue 1, May 1995. Dedicated and Shared Transport ANSI T1.101-1994, American National Standard for Telecommunications - Synchronization Interface Standard Performance and Availability. ANSI T1.102-1993, American National Standard for Telecommunications - Digital Hierarchy - Electrical Interfaces. ANSI T1.105-1995, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Basic Description including Multiplex Structure, Rates and Formats. ANSI T1.105.01-1995, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Automatic Protection Switching. ANSI T1.105.02-1995, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Payload Mappings. ANSI T1.105.03-1994, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Jitter at Network Interfaces. ANSI T1.105.03a-1995, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”): Jitter at Network Interfaces - DS1 Supplement. ANSI T1.105.04-1995, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Data Communication Channel Protocols and Architectures. ANSI T1.105.05-1994, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Tandem Connection. ANSI T1.105.06-1996, American National Standard for Telecommunications - Synchronous Optical Network (“SONET”) - Physical Layer Specifications. ANSI T1.106-1988, American National Standard for Telecommunications - Digital Hierarchy - Optical Interface Specifications (Single Mode). ANSI T1.107-1988, American National Standard for Telecommunications - Digital Hierarchy - Formats Specifications. ANSI T1.107a-1990, American National Standard for Telecommunications - Digital Hierarchy - Supplement to Formats Specifications (DS3 Format Applications). ANSI T1.107b-1991, American National Standard for Telecommunicati...
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Switching System Generic Requirements. Telcordia (formerly BellCore) SR-NWT-002247, AIN Release 1 Update.
Sample 1Sample 2
Switching System Generic Requirements. Issue 1, August 1992, and Bulletin 1, March 1993.
Sample 1
Switching System Generic Requirements. SR‑NWT‑002247, AIN Release 1 Update ANSI standards Q.931, Q.932 Bellcore TR‑NWT‑00 Xxxxxxxx XX‑NWT‑303 TR‑NWT‑000393, January 1991, Generic Requirements for ISDN Basic Access Digital Subscriber Lines
Sample 1

Related to Switching System Generic Requirements

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • System for Award Management (XXX) Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a XXX.xxx proof of registration and Commercial and Government Entity (CAGE) number. Grantee will continue to maintain an active XXX registration with current information at all times during which it has an active award under this Agreement.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • SPECIALIZED SERVICE REQUIREMENTS In the event that the Participating Entity requires service or specialized performance requirements not addressed in this Contract (such as e- commerce specifications, specialized delivery requirements, or other specifications and requirements), the Participating Entity and the Supplier may enter into a separate, standalone agreement, apart from this Contract. Sourcewell, including its agents and employees, will not be made a party to a claim for breach of such agreement.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation 35.5.1. The charges that CLEC shall pay to Sprint for Collocation are set forth in Table Two of this Agreement. 35.6. Call Related Databases 6.1. The charges that CLEC shall pay to Sprint for Call Related Databases purchased pursuant to Part J are set forth in Table One of this Agreement.

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

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