Common use of Obligations of Both Parties Clause in Contracts

Obligations of Both Parties. 2.2.1 The Parties shall: 2.2.1.1 disclose, upon request, any technical limitations that would prevent LNP implementation in a particular switching office; and 2.2.1.2 provide LNP services and facilities only where technically feasible, subject to the availability of facilities, and only from properly equipped central office. 2.2.2 Each Party shall deploy LNP software in all switches within the 100 largest Metropolitan Statistical Areas (MSAs) as per FCC CC Docket 95-116 (i.e. the First Report and Order and subsequent Orders issued to the date this Agreement was signed). Additionally, those areas identified as within the 100 largest MSAs as a result of the last Census Bureau report shall also be included within this mandatory group of number portable switches. 2.2.3 When a ported telephone number becomes vacant, e.g., the telephone number is no longer in service by the original End User, the ported telephone number will be released back to the carrier owning the switch in which the telephone number’s NXX is native within the time frames set forth in FCC CC Docket 95-116. 2.2.4 Each Party has the right to block default routed call entering a network in order to protect the public switched network from overload, congestion, or failure propagation. 2.2.5 Industry guidelines shall be followed regarding all aspects of porting numbers from one carrier to another, including but not limited to NANC Local Number Portability (LNP) Interservice Provider Operation Flows. 2.2.6 Intracompany testing shall be performed prior to the scheduling of intercompany testing. 2.2.7 Each Party will designate a single point of contact (SPOC) to schedule and perform required testing. These tests will be performed during a mutually agreed time frame and must meet the criteria set forth by the Wireless Testing Sub-Committee (WTSC). 2.2.8 When a Party ports an End User’s telephone number to its switch, that Party shall become responsible for the End User’s E911 record and other related telecommunication items. 2.2.9 Each Party is responsible for advising the Number Portability Administration Center (NPAC) of telephone numbers that it imports and the associated data as identified in industry forums as being required for LNP. 2.2.10 All porting involving WSP will be handled via subscription versions submitted to the existing NPAC with downloads to Local SMS (LSMS). 2.2.11 The Parties agree that porting between wireless and wireline service providers will use existing wireline defined LNP porting intervals, including intervals for Firm Order Commitment (FOC) as set forth in the “North American Numbering Council, Local Number Portability (LNP), Inter Service Provider Operations Flows”. Each Party is responsible for meeting the FOC intervals. 2.2.12 As part of the pre-ordering process, after receiving notification from the Party placing the porting request (“Requesting Party”), the other Party shall provide the Customer Service Record of the End User whose number is being ported upon request. 2.2.13 When either Party requests that an NXX in an LNP capable switch become portable, Parties shall follow the industry standard Local Exchange Routing Guide (LERG) procedure. 2.2.14 Consistent with Inter-Service Provider Local Number Portability (LNP) Operations Flows developed by the National Number Portability Operations (NNPO)/Wireless Number Portability Operations teams and as approved by the North American Numbering Council (NANC), the Local Service Request (LSR) will be the means of communication for all Local Number Portability (LNP) requests between Wireline and Wireless Carriers. Business rules supporting LNP ordering are to be based upon Ordering and Billing Forum (OBF) standards; for requests coming to AT&T, the AT&T 13-state Local Service Ordering Requirements (LSOR) shall be used. Parties agree that Number Portability LSRs will be submitted in one of the current supported versions of the AT&T 13-state LSOR consistent with LSR versioning rules supported by AT&T. 2.2.15 All NPA-NXXs within the top 100 MSAs will be marked portable in the LERG. 2.2.16 An LRN must be provided for all switches marked as LNP capable. The appropriate Party must be the LERG assigned code owner of the LRN’s NPA/NXX. The operating company number (OCN) associated with this NPA/NXX will identify the provider. The LRN must be in the same Local Access and Transport Area (LATA) as the ported number. At minimum, there will be at least one (1) LRN per LATA per switch as documented in the Industry Numbering Committee (“INC”) LRN guidelines. 2.2.17 If either Party operates as both local exchange carrier and wireless service provider, such party shall l have an unique OCN and service provider identification number (SPID) assignments for each entity. 2.2.18 Prior to actual ordering, WSPs will move telephone numbers associated with their Type 1 trunks to the WSP’s switch. Due to technical constraints, port in to Type 1 interconnection trunks will not be permitted. Type 1 trunks that are used exclusively for ancillary services (such as 911 Telecommunication Services, Directory Assistance, etc.) are exempt from this process. Parties agree to cooperate with the migration of telephone numbers associated with their Type 1 trunks to the WSP switch. This may include LERG reassignment, transfer of ownership of a block, or porting of individual numbers. 2.2.19 Both Parties will mark all Type 2 trunks to reflect the Common Language Location Identifier (CLLI) code of their host switch. 2.2.20 Both Parties shall be certified by the Regional NPAC prior to scheduling Intercompany testing of LNP. 2.2.21 Both Parties agree to complete and provide to the other Party a profile that contains information necessary for processing LSRs and for porting. The profile will request carrier name, carrier OCN, SPID, contact information, etc., necessary for the provisioning of all WSP porting requests.

Obligations of Both Parties. 2.2.1 2.3.1 The Parties shall: 2.2.1.1 disclose, upon request, any technical limitations that would prevent LNP implementation shall cooperate in a particular switching office; and 2.2.1.2 provide LNP services and facilities only where technically feasible, subject performing activities required to port Customer telephone number(s). The primary responsibility for the availability coordination of facilities, and only from properly equipped central officesuch activities will be assumed by the Party acquiring the End User Customer (porting in the Customer telephone number(s)). 2.2.2 Each 2.3.2 Either Party shall deploy LNP software in all switches may request a Customer Service Record (CSR) prior to placing a porting order. Where requested and available, the Parties will make commercially reasonable efforts to return CSRs within the 100 largest Metropolitan Statistical Areas (MSAs) as per FCC CC Docket 95-116 (i.e. the First Report 24 hours, excluding weekends and Order and subsequent Orders issued to the date this Agreement was signed). Additionally, those areas identified as within the 100 largest MSAs as a result of the last Census Bureau report shall also be included within this mandatory group of number portable switchesholidays. 2.2.3 2.3.3 When a ported telephone number becomes vacant, e.g., the telephone number is no longer in service by the original End User, the ported telephone number will be released back to the carrier owning the switch in which the telephone number’s NXX is native within the after appropriate time frames set forth in FCC CC Docket 95-116has elapsed for intercept notification. 2.2.4 2.3.4 Each Party has the right to block default routed call calls from entering a network in order to protect the public switched network from overload, congestion, or failure propagation. 2.2.5 Industry guidelines 2.3.5 NANC Inter-Service Provider LNP Operations Flows approved and adopted by the FCC shall be followed regarding all aspects of porting numbers from one carrier network to another, including but not limited to NANC Local Number Portability (LNP) Interservice Provider Operation Flows. 2.2.6 Intracompany 2.3.6 Intercompany testing shall be performed upon request prior to the scheduling submission of intercompany testingactual porting orders. 2.2.7 2.3.7 Each Party will designate a single point of contact (SPOC) to schedule and perform required testing. These tests will be performed during a mutually agreed time frame and must meet the criteria set forth by the Wireless Testing Sub-Committee (WTSC)frame. 2.2.8 When a Party ports an End User’s telephone number to its switch, that 2.3.8 Each Party shall become responsible for the End User’s E911 record and other telecommunications related telecommunication items. 2.2.9 Each Party is responsible for advising the Number Portability Administration Center , e.g. E911, Directory Listings, Operator Services, Line Information Database (NPAC) of telephone numbers that it imports and the associated data as identified in industry forums as being required for LNP. 2.2.10 All porting involving WSP will be handled via subscription versions submitted to the existing NPAC with downloads to Local SMS (LSMS). 2.2.11 The Parties agree that porting between wireless and wireline service providers will use existing wireline defined LNP porting intervals, including intervals for Firm Order Commitment (FOC) as set forth in the “North American Numbering Council, Local Number Portability (LNPLIDB), Inter Service Provider Operations Flows”. Each Party is responsible for meeting the FOC intervals. 2.2.12 As part of the pre-ordering process, after receiving notification from the Party placing the porting request (“Requesting Party”), the other Party shall provide the Customer Service Record of when they port the End User whose User’s telephone number is being ported upon request. 2.2.13 When either Party requests that an NXX in an LNP capable switch become portable, Parties shall follow the industry standard Local Exchange Routing Guide (LERG) procedure. 2.2.14 Consistent with Inter-Service Provider Local Number Portability (LNP) Operations Flows developed by the National Number Portability Operations (NNPO)/Wireless Number Portability Operations teams and as approved by the North American Numbering Council (NANC), the Local Service Request (LSR) will be the means of communication for all Local Number Portability (LNP) requests between Wireline and Wireless Carriers. Business rules supporting LNP ordering are to be based upon Ordering and Billing Forum (OBF) standards; for requests coming to AT&T, the AT&T 13-state Local Service Ordering Requirements (LSOR) shall be used. Parties agree that Number Portability LSRs will be submitted in one of the current supported versions of the AT&T 13-state LSOR consistent with LSR versioning rules supported by AT&T. 2.2.15 All NPA-NXXs within the top 100 MSAs will be marked portable in the LERG. 2.2.16 An LRN must be provided for all switches marked as LNP capable. The appropriate Party must be the LERG assigned code owner of the LRN’s NPA/NXX. The operating company number (OCN) associated with this NPA/NXX will identify the provider. The LRN must be in the same Local Access and Transport Area (LATA) as the ported number. At minimum, there will be at least one (1) LRN per LATA per switch as documented in the Industry Numbering Committee (“INC”) LRN guidelines. 2.2.17 If either Party operates as both local exchange carrier and wireless service provider, such party shall l have an unique OCN and service provider identification number (SPID) assignments for each entity. 2.2.18 Prior to actual ordering, WSPs will move telephone numbers associated with their Type 1 trunks to the WSP’s switch. Due to technical constraints, port in to Type 1 interconnection trunks will not be permitted. Type 1 trunks that are used exclusively for ancillary services (such as 911 Telecommunication Services, Directory Assistance, etc.) are exempt from this process. Parties agree to cooperate with the migration of telephone numbers associated with their Type 1 trunks to the WSP switch. This may include LERG reassignment, transfer of ownership of a block, or porting of individual numbers. 2.2.19 Both Parties will mark all Type 2 trunks to reflect the Common Language Location Identifier (CLLI) code of their host switch. 2.2.20 Both 2.3.9 The Parties shall be certified by will provide a 10-digit trigger on all LNP orders, where technically feasible, unless a coordinated conversion of numbers is requested on the Regional NPAC prior to scheduling Intercompany testing of LNPLNP order. 2.2.21 Both Parties agree to complete and provide to the other Party a profile that contains information necessary for processing LSRs and for porting. The profile will request carrier name, carrier OCN, SPID, contact information, etc., necessary for the provisioning of all WSP porting requests.

Obligations of Both Parties. 2.2.1 The Parties shall: 2.2.1.1 disclose, upon request, any technical limitations that would prevent LNP implementation in a particular switching office; and 2.2.1.2 provide LNP services and facilities only where technically feasible, subject to the availability of facilities, and only from properly equipped central office. 2.2.2 Each Party shall deploy LNP software in all switches within the 100 largest Metropolitan Statistical Areas (MSAs) as per FCC CC Docket 95-116 (i.e. the First Report and Order and subsequent Orders issued to the date this Agreement was signed). Additionally, those areas identified as within the 100 largest MSAs as a result of the last Census Bureau report shall also be included within this mandatory group of number portable switches. 2.2.3 When a ported telephone number becomes vacant, e.g., the telephone number is no longer in service by the original End User, the ported telephone number will be released back to the carrier owning the switch in which the telephone number’s NXX is native within the time frames set forth in FCC CC Docket 95-116. 2.2.4 Each Party has the right to block default routed call entering a network in order to protect the public switched network from overload, congestion, or failure propagation. 2.2.5 Industry guidelines shall be followed regarding all aspects of porting numbers from one carrier to another, including but not limited to NANC Local Number Portability (LNP) Interservice Provider Operation Flows. 2.2.6 Intracompany testing shall be performed prior to the scheduling of intercompany testing. 2.2.7 Each Party will designate a single point of contact (SPOC) to schedule and perform required testing. These tests will be performed during a mutually agreed time frame and must meet the criteria set forth by the Wireless Testing Sub-Committee (WTSC). 2.2.8 When a Party ports an End User’s telephone number to its switch, that Party shall become responsible for the End User’s E911 record and other related telecommunication items. 2.2.9 Each Party is responsible for advising the Number Portability Administration Center (NPAC) of telephone numbers that it imports and the associated data as identified in industry forums as being required for LNP. 2.2.10 All porting involving WSP will be handled via subscription versions submitted to the existing NPAC with downloads to Local SMS (LSMS). 2.2.11 The Parties agree that porting between wireless and wireline service providers will use existing wireline defined LNP porting intervals, including intervals for Firm Order Commitment (FOC) as set forth in the “North American Numbering Council, Local Number Portability (LNP), Inter Service Provider Operations Flows”. Each Party is responsible for meeting the FOC intervals. 2.2.12 As part of the pre-ordering process, after receiving notification from the Party placing the porting request (“Requesting Party”), the other Party shall provide the Customer Service Record of the End User whose number is being ported upon request. 2.2.13 When either Party requests that an NXX in an LNP capable switch become portable, Parties shall follow the industry standard Local Exchange Routing Guide (LERG) procedure. 2.2.14 Consistent with Inter-Service Provider Local Number Portability (LNP) Operations Flows developed by the National Number Portability Operations (NNPO)/Wireless Number Portability Operations teams and as approved by the North American Numbering Council (NANC), the Local Service Request (LSR) will be the means of communication for all Local Number Portability (LNP) requests between Wireline and Wireless Carriers. Business rules supporting LNP ordering are to be based upon Ordering and Billing Forum (OBF) standards; for requests coming to AT&T, the AT&T 13-state Local Service Ordering Requirements (LSOR) shall be used. Parties agree that Number Portability LSRs will be submitted in one of the current supported versions of the AT&T 13-state LSOR consistent with LSR versioning rules supported by AT&T. 2.2.15 All NPA-NXXs within the top 100 MSAs will be marked portable in the LERG. 2.2.16 An LRN must be provided for all switches marked as LNP capable. The appropriate Party must be the LERG assigned code owner of the LRN’s NPA/NXX. The operating company number (OCN) associated with this NPA/NXX will identify the provider. The LRN must be in the same Local Access and Transport Area (LATA) as the ported number. At minimum, there will be at least one (1) LRN per LATA per switch as documented in the Industry Numbering Committee (“INC”) LRN guidelines. 2.2.17 If either Party operates as both local exchange carrier and wireless service provider, such party shall l have an unique OCN and service provider identification number (SPID) assignments for each entity. 2.2.18 Prior to actual ordering, WSPs will move telephone numbers associated with their Type 1 trunks to the WSP’s switch. Due to technical constraints, port in to Type 1 interconnection trunks will not be permitted. Type 1 trunks that are used exclusively for ancillary services (such as 911 Telecommunication Services, Directory Assistance, etc.) are exempt from this process. Parties agree to cooperate with the migration of telephone numbers associated with their Type 1 trunks to the WSP switch. This may include LERG reassignment, transfer of ownership of a block, or porting of individual numbers. 2.2.19 Both Parties will mark all Type 2 trunks to reflect the Common Language Location Identifier (CLLI) code of their host switch. 2.2.20 Both Parties shall be certified by the Regional NPAC prior to scheduling Intercompany testing of LNP. 2.2.21 Both Parties agree to complete and provide to the other Party a profile that contains information necessary for processing LSRs and for porting. The profile will request carrier name, carrier OCN, SPID, contact information, etc., necessary for the provisioning of all WSP porting requests.

Obligations of Both Parties. 2.2.1 The Parties shall: 2.2.1.1 disclose, upon request, any technical limitations that would prevent LNP implementation in a particular switching office; and 2.2.1.2 provide LNP services and facilities only where technically feasible, subject to the availability of facilities, and only from properly equipped central office. 2.2.2 Each Party shall deploy LNP software in all switches within the 100 largest Metropolitan Statistical Areas (MSAs) as per FCC CC Docket 95-116 (i.e. the First Report and Order and subsequent Orders issued to the date this Agreement was signed). Additionally, those areas identified as within the 100 largest MSAs as a result of the last Census Bureau report shall also be included within this mandatory group of number portable switches.. Page 82 of 127 2.2.3 When a ported telephone number becomes vacant, e.g., the telephone number is no longer in service by the original End User, the ported telephone number will be released back to the carrier owning the switch in which the telephone number’s NXX is native within the time frames set forth in FCC CC Docket 95-116. 2.2.4 Each Party has the right to block default routed call entering a network in order to protect the public switched network from overload, congestion, or failure propagation. 2.2.5 Industry guidelines shall be followed regarding all aspects of porting numbers from one carrier to another, including but not limited to NANC Local Number Portability (LNP) Interservice Provider Operation Flows. 2.2.6 Intracompany testing shall be performed prior to the scheduling of intercompany testing. 2.2.7 Each Party will designate a single point of contact (SPOC) to schedule and perform required testing. These tests will be performed during a mutually agreed time frame and must meet the criteria set forth by the Wireless Testing Sub-Committee (WTSC). 2.2.8 When a Party ports an End User’s telephone number to its switch, that Party shall become responsible for the End User’s E911 record and other related telecommunication items. 2.2.9 Each Party is responsible for advising the Number Portability Administration Center (NPAC) of telephone numbers that it imports and the associated data as identified in industry forums as being required for LNP. 2.2.10 All porting involving WSP will be handled via subscription versions submitted to the existing NPAC with downloads to Local SMS (LSMS). 2.2.11 The Parties agree that porting between wireless and wireline service providers will use existing wireline defined LNP porting intervals, including intervals for Firm Order Commitment (FOC) as set forth in the “North American Numbering Council, Local Number Portability (LNP), Inter Service Provider Operations Flows”. Each Party is responsible for meeting the FOC intervals. 2.2.12 As part of the pre-ordering process, after receiving notification from the Party placing the porting request (“Requesting Party”), the other Party shall provide the Customer Service Record of the End User whose number is being ported upon request. 2.2.13 When either Party requests that an NXX in an LNP capable switch become portable, Parties shall follow the industry standard Local Exchange Routing Guide (LERG) procedure. 2.2.14 Consistent with Inter-Service Provider Local Number Portability (LNP) Operations Flows developed by the National Number Portability Operations (NNPO)/Wireless Number Portability Operations teams and as approved by the North American Numbering Council (NANC), the Local Service Request (LSR) will be the means of communication for all Local Number Portability (LNP) requests between Wireline and Wireless Carriers. Business rules supporting LNP ordering are to be based upon Ordering and Billing Forum (OBF) standards; for requests coming to AT&T, the AT&T 13-state Local Service Ordering Requirements (LSOR) shall be used. Parties agree that Number Portability LSRs will be submitted in one of the current supported versions of the AT&T 13-state LSOR consistent with LSR versioning rules supported by AT&T. 2.2.15 All NPA-NXXs within the top 100 MSAs will be marked portable in the LERG. 2.2.16 An LRN must be provided for all switches marked as LNP capable. The appropriate Party must be the LERG assigned code owner of the LRN’s NPA/NXX. The operating company number (OCN) associated with this NPA/NXX will identify the provider. The LRN must be in the same Local Access and Transport Area (LATA) as the ported number. At minimum, there will be at least one (1) LRN per LATA per switch as documented in the Industry Numbering Committee (“INC”) LRN guidelines. 2.2.17 If either Party operates as both local exchange carrier and wireless service provider, such party shall l have an unique OCN and service provider identification number (SPID) assignments for each entity.. Page 83 of 127 2.2.18 Prior to actual ordering, WSPs will move telephone numbers associated with their Type 1 trunks to the WSP’s switch. Due to technical constraints, port in to Type 1 interconnection trunks will not be permitted. Type 1 trunks that are used exclusively for ancillary services (such as 911 Telecommunication Services, Directory Assistance, etc.) are exempt from this process. Parties agree to cooperate with the migration of telephone numbers associated with their Type 1 trunks to the WSP switch. This may include LERG reassignment, transfer of ownership of a block, or porting of individual numbers. 2.2.19 Both Parties will mark all Type 2 trunks to reflect the Common Language Location Identifier (CLLI) code of their host switch. 2.2.20 Both Parties shall be certified by the Regional NPAC prior to scheduling Intercompany testing of LNP. 2.2.21 Both Parties agree to complete and provide to the other Party a profile that contains information necessary for processing LSRs and for porting. The profile will request carrier name, carrier OCN, SPID, contact information, etc., necessary for the provisioning of all WSP porting requests.

Obligations of Both Parties. 2.2.1 The Parties shall: 2.2.1.1 disclose, upon request, any technical limitations that would prevent LNP implementation in a particular switching office; and 2.2.1.2 provide LNP services and facilities only where technically feasible, subject to the availability of facilities, and only from properly equipped central office. 2.2.2 Each Party shall deploy LNP software in all switches within the 100 largest Metropolitan Statistical Areas (MSAs) as per FCC CC Docket 95-116 (i.e. the First Report and Order and subsequent Orders issued to the date this Agreement was signed). Additionally, those areas identified as within the 100 largest MSAs as a result of the last Census Bureau report shall also be included within this mandatory group of number portable switches. 2.2.3 When a ported telephone number becomes vacant, e.g., the telephone number is no longer in service by the original End User, the ported telephone number will be released back to the carrier owning the switch in which the telephone number’s NXX is native within the time frames set forth in FCC CC Docket 95-116. 2.2.4 Each Party has the right to block default routed call entering a network in order to protect the public switched network from overload, congestion, or failure propagation. 2.2.5 Industry guidelines shall be followed regarding all aspects of porting numbers from one carrier to another, including but not limited to NANC Local Number Portability (LNP) Interservice Provider Operation Flows. 2.2.6 Intracompany testing shall be performed prior to the scheduling of intercompany testing. 2.2.7 Each Party will designate a single point of contact (SPOC) to schedule and perform required testing. These tests will be performed during a mutually agreed time frame and must meet the criteria set forth by the Wireless Testing Sub-Committee (WTSC). 2.2.8 When a Party ports an End User’s telephone number to its switch, that Party shall become responsible for the End User’s E911 record and other related telecommunication items. 2.2.9 Each Party is responsible for advising the Number Portability Administration Center (NPAC) of telephone numbers that it imports and the associated data as identified in industry forums as being required for LNP. 2.2.10 All porting involving WSP will be handled via subscription versions submitted to the existing NPAC with downloads to Local SMS (LSMS). 2.2.11 The Parties agree that porting between wireless and wireline service providers will use existing wireline defined LNP porting intervals, including intervals for Firm Order Commitment (FOC) as set forth in the “North American Numbering Council, Local Number Portability (LNP), Inter Service Provider Operations Flows”. Each Party is responsible for meeting the FOC intervals. 2.2.12 As part of the pre-ordering process, after receiving notification from the Party placing the porting request (“Requesting Party”), the other Party shall provide the Customer Service Record of the End User whose number is being ported upon request. 2.2.13 When either Party requests that an NXX in an LNP capable switch become portable, Parties shall follow the industry standard Local Exchange Routing Guide (LERG) procedure. 2.2.14 Consistent with Inter-Service Provider Local Number Portability (LNP) Operations Flows developed by the National Number Portability Operations (NNPO)/Wireless Number Portability Operations teams and as approved by the North American Numbering Council (NANC), the Local Service Request (LSR) will be the means of communication for all Local Number Portability (LNP) requests between Wireline and Wireless Carriers. Business rules supporting LNP ordering are to be based upon Ordering and Billing Forum (OBF) standards; for requests coming to AT&TSBC, the AT&T SBC 13-state Local Service Ordering Requirements (LSOR) shall be used. Parties agree that Number Portability LSRs will be submitted in one of the current supported versions of the AT&T SBC 13-state LSOR consistent with LSR versioning rules supported by AT&T.SBC. 2.2.15 All NPA-NXXs within the top 100 MSAs will be marked portable in the LERG. 2.2.16 An LRN must be provided for all switches marked as LNP capable. The appropriate Party must be the LERG assigned code owner of the LRN’s NPA/NXX. The operating company number (OCN) associated with this NPA/NXX will identify the provider. The LRN must be in the same Local Access and Transport Area (LATA) as the ported number. At minimum, there will be at least one one (1) LRN per LATA per switch as documented in the Industry Numbering Committee (“INC”) LRN guidelines. 2.2.17 If either Party operates as both local exchange carrier and wireless service provider, such party shall l have an unique OCN and service provider identification number (SPID) assignments for each entity. 2.2.18 Prior to actual ordering, WSPs will move telephone numbers associated with their Type 1 trunks to the WSP’s switch. Due to technical constraints, port in to Type 1 interconnection trunks will not be permitted. Type 1 trunks that are used exclusively for ancillary services (such as 911 Telecommunication Services, Directory Assistance, etc.) are exempt from this process. Parties agree to cooperate with the migration of telephone numbers associated with their Type 1 trunks to the WSP switch. This may include LERG reassignment, transfer of ownership of a block, or porting of individual numbers. 2.2.19 Both Parties will mark all Type 2 trunks to reflect the Common Language Location Identifier (CLLI) code of their host switch. 2.2.20 Both Parties shall be certified by the Regional NPAC prior to scheduling Intercompany testing of LNP. 2.2.21 Both Parties agree to complete and provide to the other Party a profile that contains information necessary for processing LSRs and for porting. The profile will request carrier name, carrier OCN, SPID, contact information, etc., necessary for the provisioning of all WSP porting requests.