SBC-13 STATE Clause Samples

The SBC-13 STATE clause defines the governing law or jurisdiction that will apply to the interpretation and enforcement of the contract. In practice, this means that any disputes arising from the agreement will be resolved according to the laws of the specified state, such as New York or California, regardless of where the parties are located. This clause provides certainty and predictability for both parties by clarifying which state's legal rules will govern their relationship, thereby reducing the risk of legal ambiguity or forum shopping.
SBC-13 STATE shall not be liable to CLEC, its End User or any other Person for any Loss alleged to arise out of the provision of access to 911 service or any errors, interruptions, defects, failures or malfunctions of 911 service.
View SourceView Similar (7)
SBC-13 STATE s ALI database shall accept electronically transmitted files that are based upon NENA Standards.
View SourceView Similar (4)
SBC-13 STATE will provide CLEC a specific Daily Usage File (“DUF” or “Usage Extract”) for Resale Services and Network Element usage sensitive services provided hereunder (“Customer Usage Data”). Such Customer Usage Data shall be provided by SBC-13STATE in accordance with Exchange Message Interface (EMI) guidelines supported by OBF. Any exceptions to the supported formats will be noted in the DUF implementation requirements documentation for each ILEC. The DUF shall include (i) specific daily usage, including both Local Traffic (if and where applicable) and LEC- carried IntraLATA Toll Traffic, in EMI format for usage sensitive services furnished in connection with each Resale Service and Network Element to the extent that similar usage sensitive information is provided to retail End Users of SBC-13STATE within that state, (ii) with sufficient detail to enable CLEC to bill its End Users for usage sensitive services furnished by SBC-13STATE in connection with Resale Services and Network Elements provided by SBC- 13STATE. Procedures and processes for implementing the interfaces with SBC-AMERITECH, PACIFIC, NEVADA, SNET, and SBC-SWBT will be included in implementation requirements documentation.
View SourceView Similar (3)
SBC-13 STATE will provide CLEC a specific Daily Usage File (“DUF” or “Usage Extract”) for Resale Services and Network Element usage sensitive services provided hereunder (“Customer Usage Data”). Such Customer Usage Data shall be provided by SBC-13STATE in accordance with Exchange Message Interface (EMI) guidelines supported by OBF. Any exceptions to the supported formats will be noted in the DUF implementation requirements documentation for each ILEC. The DUF shall include (i) specific daily usage, including both Local Traffic (if and where applicable) and LEC-carried IntraLATA Toll Traffic, in EMI format for usage sensitive services furnished in connection with each Resale Service and Network Element to the extent that similar usage sensitive information is provided to retail End Users of SBC-13STATE within that state, (ii) with sufficient detail to enable CLEC to bill its End Users for usage sensitive services furnished by SBC-13STATE in connection with Resale Services and Network Elements provided by SBC- 13STATE. Procedures and processes for implementing the interfaces with SBC-AMERITECH, PACIFIC, NEVADA, SNET, and SBC-SWBT will be included in implementation requirements documentation. 8.13.1.1 This section is intended to entitle CLEC to continue to receive ACDRS records in accordance with current operating procedures between SBC-AMERITECH and CLEC under the prior Resale Agreements.
View SourceView Similar (3)
SBC-13 STATE will provide a copy of the static MSAG received from the appropriate E911 Authority, to be utilized for the development of Shell ALI Records.
View Source

Related to SBC-13 STATE

  • SBC-12STATE 47.1.1 The terms contained in this Agreement and any Appendices, Attachments, Exhibits, Schedules, and Addenda constitute the entire agreement between the Parties with respect to the subject matter hereof, superseding all prior understandings, proposals and other communications, oral or written between the Parties during the negotiations of this Agreement and through the execution and/or Effective Date of this Agreement. This Agreement shall not operate as or constitute a novation of any agreement or contract between the Parties that predates the execution and/or Effective Date of this Agreement.

  • AT&T-21STATE communicates official information to CLECs via its Accessible Letter, or other applicable, notification processes. These processes involve electronic transmission and/or posting to the AT&T CLEC Online website, inclusive of a variety of subjects including declaration of a force majeure, changes on business processes and policies, and other product/service related notices not requiring an amendment to this Agreement.

  • SBC-13STATE shall provide to CLEC Interconnection of the Parties’ facilities and equipment for the transmission and routing of Telephone Exchange Service traffic and Exchange Access traffic pursuant to the applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. Methods for Interconnection and Physical Architecture shall be as defined in the applicable Appendix NIM, which is/are attached hereto and incorporated herein by reference.

  • Official Records The resolutions of Transferor's Board of Directors approving each of the Transaction Documents and all documents relating thereto are and shall be continuously reflected in the minutes of Transferor's Board of Directors. Each of the Transaction Documents and all documents relating thereto are and shall, continuously from the time of their respective execution by Transferor, be official records of Transferor.

  • AT&T-12STATE acknowledges that CLEC may have an embedded base of one-way trunks ordered and installed prior to the Effective Date of this Agreement that were used for termination of CLEC’s Section 251(b)(5)/IntraLATA Toll Traffic to AT&T-12STATE (Embedded Base). To the extent that CLEC has such an Embedded Base, CLEC shall only augment trunk groups in the Embedded Base with the mutual agreement of the Parties. CLEC shall not order any new one-way trunk groups following the Effective Date of this Agreement. Moreover, the Parties agree that the Embedded Base will be converted to two-way trunk groups under the following circumstances: 4.2.1.1 With reasonable notification from AT&T-12STATE and upon AT&T-12STATE’s request, CLEC shall convert all of its Embedded Base to two-way trunks. 4.2.1.2 At any time an Embedded Base trunk group (either originating or terminating) requires augmentation, AT&T-12STATE can require the associated originating and terminating trunks to be converted to a single two-way trunk group prior to the augmentation. 4.2.1.3 When any network changes are to be performed on a project basis (i.e., central office conversions, tandem re-homes, etc.), upon request and reasonable notice by AT&T-12STATE, CLEC will convert all of its Embedded Base affected by the project within the intervals and due dates required by the project parameters. 4.2.1.4 In addition to the foregoing, CLEC may choose, at any time, to convert its Embedded Base to two-way trunk groups. 4.2.1.5 The Parties will coordinate any trunk group migration, trunk group prioritization and implementation schedule. AT&T-12STATE agrees to develop a cutover plan within thirty (30) days of notification to CLEC of the need to convert pursuant to Section 4.2.1.1 above and Section 4.2.1.3 above.