Common use of Obligations of Parties Clause in Contracts

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. Xxxxxxx 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). DATE: (date of request) TO: (name of service provider) FROM: (requester/service provider name/ID) SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 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. 2 Enter associated Rate Center information from LERG, including: Rate Center Name and Associated V&H Terminating Point Master Coordinates; Source of the LERG information: Destination Code Record (DRD) Screen. 3 Circle or highlight Y if requesting all eligible NPA-NXX codes in that specific switch to be opened. Circle or highlight N if only certain NPA NXX codes are being requested. Then provide list of desired NPA NXX(s). Note: Targeting of specific NPA-NXX codes should be carefully considered. A traditional ILEC may serve a single rate center with multiple switches (CLLIs and NXX codes) while Carrier may serve multiple rate centers with a single switch. In the latter case, use of a specific NXX code will determine the rate center. EXHIBIT B CLLI Accepted LNP Effective Date or Modified Effective Date Ineligible NPA-NXXs (CLLI 4)

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. Xxxxxxx 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). DATE: (date of request) TO: (name of service provider) FROM: (requester/service provider name/ID) SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 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. 2 Enter associated Rate Center information from LERG, including: Rate Center Name and Associated V&H Terminating Point Master Coordinates; Source of the LERG information: Destination Code Record (DRD) Screen. 3 Circle or highlight Y if requesting all eligible NPA-NXX codes in that specific switch to be opened. Circle or highlight N if only certain NPA NXX codes are being requested. Then provide list of desired NPA NXX(s). Note: Targeting of specific NPA-NXX codes should be carefully considered. A traditional ILEC may serve a single rate center with multiple switches (CLLIs and NXX codes) while Carrier may serve multiple rate centers with a single switch. In the latter case, use of a specific NXX code will determine the rate center. EXHIBIT B TO: (requester/Carrier name/ID) FROM: (name of service provider) CLLI Accepted LNP Effective Date or Modified Effective Date Ineligible NPA-NXXs (CLLI 4)

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. Xxxxxxx 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). DATE: (date of request) TO: (name of service provider) FROM: (requester/service provider name/ID) SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 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. 2 Enter associated Rate Center information from LERG, including: Rate Center Name and Associated V&H Terminating Point Master Coordinates; Source of the LERG information: Destination Code Record (DRD) Screen. 3 Circle or highlight Y if requesting all eligible NPA-NXX codes in that specific switch to be opened. Circle or highlight N if only certain NPA NXX codes are being requested. Then provide list of desired NPA NXX(s). Note: Targeting of specific NPA-NXX codes should be carefully considered. A traditional ILEC may serve a single rate center with multiple switches (CLLIs and NXX codes) while Carrier may serve multiple rate centers with a single switch. In the latter case, use of a specific NXX code will determine the rate center. EXHIBIT B CLLI Accepted LNP Effective Date or Modified Effective Date Ineligible NPA-NXXs (CLLI 4)

Obligations of Parties. 1.2.1 Both Parties will participate in LNP testing in accordance with North American Numbering Council (NANC) standards. . 1.2.2 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. . 1.2.3 Carrier is required to send to Frontier Citizens a completed Bona Fide Request Form for LNP deployment in non LNP capable offices. See Exhibit A. Xxxxxxx A.. 1.2.4 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. . 1.2.5 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. . 1.2.6 Each Party is responsible for the following: : a) Adhere to all Number Portability Administration Center (NPAC) and North American Numbering Council (NANC) requirements and in providing its own access to regional NPAC. . b) For providing its own access to the Service Order Administration (SOA). c) Meeting all the Industry requirements for LNP. DATE: (date of request) TO: (name of service provider) FROM: (requester/service provider name/ID) SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 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. 2 Enter associated Rate Center information from LERG, including: Rate Center Name and Associated V&H Terminating Point Master Coordinates; Source of the LERG information: Destination Code Record (DRD) Screen. 3 Circle or highlight Y if requesting all eligible NPA-NXX codes in that specific switch to be opened. Circle or highlight N if only certain NPA NXX codes are being requested. Then provide list of desired NPA NXX(s). Note: Targeting of specific NPA-NXX codes should be carefully considered. A traditional ILEC may serve a single rate center with multiple switches (CLLIs and NXX codes) while Carrier may serve multiple rate centers with a single switch. In the latter case, use of a specific NXX code will determine the rate center. EXHIBIT B TO: (requester/Carrier name/ID) FROM: (name of service provider) CLLI Accepted LNP Effective Date or Modified Effective Date Ineligible NPA-NXXs (CLLI 4)) ATTACHMENT 3 – PRICING MCImetro Access Transmission Services LLC August 16, 2005 in Docket No. C-3443

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 MetTel is required to send to Frontier a completed Bona Fide Request Form for LNP deployment in non LNP capable offices. See Exhibit A. Xxxxxxx X. XxxXxx 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 MetTel 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). DATE: (date of request) TO: (name of service provider) FROM: (requester/service provider name/ID) SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 Please provide Requestor’s information below: CARRIERMETTEL/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. 2 Enter associated Rate Center information from LERG, including: Rate Center Name and Associated V&H Terminating Point Master Coordinates; Source of the LERG information: Destination Code Record (DRD) Screen. 3 Circle or highlight Y if requesting all eligible NPA-NXX codes in that specific switch to be opened. Circle or highlight N if only certain NPA NXX codes are being requested. Then provide list of desired NPA NXX(s). Note: Targeting of specific NPA-NXX codes should be carefully considered. A traditional ILEC may serve a single rate center with multiple switches (CLLIs and NXX codes) while Carrier MetTel may serve multiple rate centers with a single switch. In the latter case, use of a specific NXX code will determine the rate center. EXHIBIT B CLLI Accepted LNP Effective Date or Modified Effective Date Ineligible NPA-NXXs (CLLI 4)NXXs

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. Frontier will implement long-term database LNP in accordance with FCC rules. Xxxxxxx is responsible to coordinate with the local E911 and Public Services Answering Point (PSAP) coordinators in Oregon to insure a seamless transfer of End User emergency services. Prior to ordering 911 trunks Carrier will provide written confirmation to Frontier that Carrier has: (1.) arranged with each PSAP in the county(s) where Carrier will provide service that (a.) PSAP can accept Xxxxxxx’s 911 calls and (b.) PSAP agrees to dip and route calls as required for successful call completion, and (2.) Carrier has established a process to provide accurate updates on a regular basis to the ALI database of each PSAP in the county(s) where Carrier provides service. Prior to submitting porting requests (LSR’s ) to Frontier, Carrier will provide written confirmation to Frontier that LNP test calls to each PSAP in the county(s) where Carrier provides service are completing successfully. 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). Upon implementation of LNP, both Parties agree to conform and provide LNP in accordance with FCC requirements. DATE: (date of request) TO: (name of service provider) FROM: (requester/service provider name/ID) SWITCH(ES): CLLI1 Rate Center Rate Center NPA-NXX(s)3 Name2 VC/HC2 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. 2 Enter associated Rate Center information from LERG, including: Rate Center Name and Associated V&H Terminating Point Master Coordinates; Source of the LERG information: Destination Code Record (DRD) Screen. 3 Circle or highlight Y if requesting all eligible NPA-NXX codes in that specific switch to be opened. Circle or highlight N if only certain NPA NXX codes are being requested. Then provide list of desired NPA NXX(s). Note: Targeting of specific NPA-NXX codes should be carefully considered. A traditional ILEC may serve a single rate center with multiple switches (CLLIs and NXX codes) while Carrier may serve multiple rate centers with a single switch. In the latter case, use of a specific NXX code will determine the rate center. EXHIBIT B TO: (requester/Carrier name/ID) FROM: (name of service provider) CLLI Accepted LNP Effective Date or Modified Effective Date Ineligible NPA-NXXs (CLLI 4)NXXs