Obligations of Parties. Nothing herein shall relieve a Party of its obligations under the Federal Rules, the Bankruptcy Rules, the Federal Rules of Evidence, and the Local Rules, or under any future stipulations and orders, regarding the production of documents or the making of timely responses to Discovery Requests in connection with the Cases.
Obligations of Parties. Both Parties will participate in LNP testing in accordance with North American Numbering Council (NANC) standards. Both Parties will follow recommended National Emergency Number Association (NENA) standards for LNP until such time the standards are superceded by federal, state, or local legislation. CLC is required to send to Frontier a completed Bona Fide Request Form for LNP deployment in non LNP capable offices. See Exhibit A. CLC is responsible to coordinate with the local E911 and Public Services Answering Point (PSAP) coordinators to insure a seamless transfer of End User emergency services. CLC is required to meet all mutually agreed upon testing dates and implementation schedules. Both Parties will perform testing as specified in industry guidelines and cooperate in conducting any additional testing to ensure interoperability between networks and systems. Each party shall inform the other Party of any system updates that may affect the other Party’s network and each Party shall, at the other Party’s request perform tests to validate the operation of the network. Each Party is responsible for the following: Adhere to all Number Portability Administration Center (NPAC) and North American Numbering Council (NANC) requirements and in providing its own access to regional NPAC. For providing its own access to the Service Order Administration (SOA). ATTACHMENT 5 UNBUNDLED NETWORK ELEMENTS ATTACHMENT 5 – UNBUNDLED NETWORK ELEMENTS
Obligations of Parties. Both Parties will participate in LNP testing in accordance with North American Numbering Council (NANC) standards. Both Parties will follow recommended National Emergency Number Association (NENA) standards for LNP until such time the standards are superceded by federal, state, or local legislation. Carrier is required to send to Frontier a completed Bona Fide Request Form for LNP deployment in non LNP capable offices. See Exhibit A. Carrier is responsible to coordinate with the local E911 and Public Services Answering Point (PSAP) coordinators to insure a seamless transfer of End User emergency services. Carrier is required to meet all mutually agreed upon testing dates and implementation schedules. Both Parties will perform testing as specified in industry guidelines and cooperate in conducting any additional testing to ensure interoperability between networks and systems. Each party shall inform the other Party of any system updates that may affect the other Party’s network and each Party shall, at the other Party’s request perform tests to validate the operation of the network. Each Party is responsible for the following: Adhere to all Number Portability Administration Center (NPAC) and North American Numbering Council (NANC) requirements and in providing its own access to regional NPAC. For providing its own access to the Service Order Administration (SOA). EXHIBIT A LOCAL NUMBER PORTABILITY (LNP) BONA FIDE REQUEST (BFR) DATE: (date of request) TO: (name of service provider) (address of service provider) (contact name /number) FROM: (requester/service provider name/ID) (requester/operating company number (OCN)) (requester switch(es)/CLLI) (authorized by name) (authorized by title) (contact name/address/number) Affidavit attesting requester as authorized agent should accompany request. SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 All: Y or N All: Y or N All: Y or N All: Y or N All: Y or N Please provide Requestor’s information below: CARRIER/REQUESTOR: CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 DATES: Requested date switch(es) should be LNP capable: (mm/dd/yy) Requested code opening date: (mm/dd/yy) Notes: See following page. Acknowledgment of BFR is to be sent to the requester within ten business days. EXHIBIT A LOCAL NUMBER PORTABILITY (LNP) BONA FIDE REQUEST (BFR) (Continued) Notes: 1 List each switch targeted for LNP by its specific CLLI code. 2 Enter associated Rate Center information from LERG, including: Rate Ce...
Obligations of Parties. 1. Both parties will share in the education process.
Obligations of Parties. (A) The Local Government agrees as follows:
Obligations of Parties. Each obligation of a Provider hereunder to take (or refrain from taking) any action hereunder shall be deemed to include an undertaking (a) if the Provider is not the Company or any of its Affiliates, by MSS to, and to cause such Provider to, take (or refrain from taking) such action and (b) if the Provider is not MSS or any of its Affiliates, by the Company to, and to cause such Provider to, take (or refrain from taking) such action. Each obligation of a Recipient or any of its Affiliates hereunder to take (or refrain from taking) any action hereunder shall be deemed to include an undertaking (i) if the Recipient is not MSS or any of its Affiliates, by the Company to, and to cause such Recipient or such Affiliate to, take (or refrain from taking) such action, and (ii) if the Recipient is not the Company or any of its Affiliates, by MSS to, and to cause such Recipient or such Affiliates to, take (or refrain from taking) such action.
Obligations of Parties. 3.1 Each Party must offer proof of its certification with applicable regional Number Portability Administration Center (NPAC) prior to requesting SPNP from the other Party.
Obligations of Parties. 4.1. The Operator undertakes the following obligations:
Obligations of Parties. Each Party must:
Obligations of Parties. The obligations of each Party to this MOU shall be as follows: a City of Oakland. During the term of this MOU, Oakland shall designate one primary individual and one alternate as a full voting Member of the Approval Authority.
