Common use of CNAM Database Service Clause in Contracts

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) days prior to MRC’s access to BellSouth’s CNAM Database Services and shall be addressed to MRC’s Local Contract Manager. 7.6.2.1 MRC’s End Users’ names and numbers related to UNE-P Services and shall be stored in the BellSouth CNAM database, and shall be available, on a per query basis only, to all entities that launch queries to the BellSouth CNAM database. BellSouth, at its sole discretion, may opt to interconnect with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailable. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC AFN the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC AFN shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCAFN’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCAFN’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to AFN requires interconnection from AFN to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, AFN shall provide its own CNAM SSP. AFN’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If AFN elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that AFN desires to UNEquery. 7.6.6 If AFN queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by AFN for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by AFN in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of AFN to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 AFN CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC ITC^DeltaCom the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC ITC^DeltaCom shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) days prior to MRCITC^DeltaCom’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCITC^DeltaCom’s Local Contract Manager. 7.6.2.1 MRCITC^DeltaCom’s End Users’ names and numbers related to UNE-P Services and shall be stored in the BellSouth CNAM database, and shall be available, on a per query basis only, to all entities that launch queries to the BellSouth CNAM database. BellSouth, at its sole discretion, may opt to interconnect with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailable. 7.6.2.2 For each MRC ITC^DeltaCom End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRCITC^DeltaCom’s End User. MRC ITC^DeltaCom shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC ITC^DeltaCom End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC ITC^DeltaCom shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRCITC^DeltaCom’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC ITC^DeltaCom at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRCITC^DeltaCom’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC PLI the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC PLI shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCPLI’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCPLI’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to PLI requires interconnection from PLI to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, PLI shall provide its own CNAM SSP. PLI’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If PLI elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that PLI desires to UNEquery. 7.6.6 If PLI queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by PLI for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by PLI in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of PLI to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 PLI CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC <customer_short_name> the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC <customer_short_name> shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRC<customer_short_name>’s access to BellSouth’s CNAM Database Services and shall be addressed to MRC<customer_short_name>’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, <customer_short_name> shall provide its own CNAM SSP. <customer_short_name>’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> desires to UNEquery. 7.6.6 If <customer_short_name> queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by <customer_short_name> for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by <customer_short_name> in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 <customer_short_name> CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC CCI the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC CCI shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCCCI’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCCCI’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to CCI requires interconnection from CCI to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, CCI shall provide its own CNAM SSP. CCI’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If CCI elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that CCI desires to UNEquery. 7.6.6 If CCI queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by CCI for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by CCI in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of CCI to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 CCI CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC FLATEL the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC FLATEL shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCFLATEL’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCFLATEL’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to FLATEL requires interconnection from FLATEL to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, FLATEL shall provide its own CNAM SSP. FLATEL’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If FLATEL elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that FLATEL desires to UNEquery. 7.6.6 If FLATEL queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by FLATEL for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by FLATEL in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of FLATEL to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 FLATEL CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC Think 12 the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC Think 12 shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCThink 12’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCThink 12’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to Think 12 requires interconnection from Think 12 to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, Think 12 shall provide its own CNAM SSP. Think 12’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If Think 12 elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that Think 12 desires to UNEquery. 7.6.6 If Think 12 queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by Think 12 for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by Think 12 in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of Think 12 to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 Think 12 CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC Excel PCHP the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC Excel PCHP shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCExcel PCHP’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCExcel PCHP’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to Excel PCHP requires interconnection from Excel PCHP to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, Excel PCHP shall provide its own CNAM SSP. Excel PCHP’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If Excel PCHP elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that Excel PCHP desires to UNEquery. 7.6.6 If Excel PCHP queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by Excel PCHP for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by Excel PCHP in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of Excel PCHP to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 Excel PCHP CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC FeroNetworks the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC FeroNetworks shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCFeroNetworks’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCFeroNetworks’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to FeroNetworks requires interconnection from FeroNetworks to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, FeroNetworks shall provide its own CNAM SSP. FeroNetworks’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If FeroNetworks elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that FeroNetworks desires to UNEquery. 7.6.6 If FeroNetworks queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by FeroNetworks for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by FeroNetworks in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of FeroNetworks to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 FeroNetworks CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC Preferred the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC Preferred shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCPreferred’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCPreferred’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to Preferred requires interconnection from Preferred to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, Preferred shall provide its own CNAM SSP. Preferred’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If Preferred elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that Preferred desires to UNEquery. 7.6.6 If Preferred queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by Preferred for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by Preferred in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of Preferred to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 Preferred CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC OnePoint the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC OnePoint shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCOnePoint’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCOnePoint’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to OnePoint requires interconnection from OnePoint to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, OnePoint shall provide its own CNAM SSP. OnePoint’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If OnePoint elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that OnePoint desires to UNEquery. 7.6.6 If OnePoint queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by OnePoint for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by OnePoint in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of OnePoint to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 OnePoint CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC FPB the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC FPB shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCFPB’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCFPB’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to FPB requires interconnection from FPB to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, FPB shall provide its own CNAM SSP. FPB’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If FPB elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that FPB desires to UNEquery. 7.6.6 If FPB queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-P Services TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by FPB for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by FPB in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of FPB to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 FPB CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC Nex-Phon the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC Nex-Phon shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to MRCNex-Phon’s access to BellSouth’s CNAM Database Services and shall be addressed to MRCNex-Phon’s Local Contract Manager. 7.6.2.1 MRC7.6.3 BellSouth's provision of CNAM Database Services to Nex-Phon requires interconnection from Nex-Phon to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, Nex-Phon shall provide its own CNAM SSP. Nex-Phon’s End Users’ names CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If Nex-Phon elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and numbers related Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that Nex-Phon desires to UNEquery. 7.6.6 If Nex-P Services Phon queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the XxxxXxxxx XXX0 network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General Terms and Conditions incorporated herein by this reference. 7.6.7 The mechanism to be used by Nex-Phon for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load and all updates shall be provided by Nex-Phon in the BellSouth specified format and shall be stored contain records for every working telephone number that can originate phone calls. It is the responsibility of Nex-Phon to provide accurate information to BellSouth on a current basis. 7.6.8 Updates to the SMS shall occur no less than once a week, reflect service order activity affecting either name or telephone number, and involve only record additions, deletions or changes. 7.6.9 Nex-Phon CNAM records provided for storage in the BellSouth CNAM database, and SCP shall be available, on a per SCP query basis only, to all entities that launch queries to Parties querying the BellSouth CNAM databaseSCP. BellSouthFurther, at its sole discretion, may opt to interconnect CNAM service shall be provided by each Party consistent with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailablestate and/or federal regulation. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred and fifty-six (256) database queries per month per MRC’s End Users with the Caller ID feature.