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 <customer_short_name> the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <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 <customer_short_name>’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>’s Local Contract Manager. 7.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 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 ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> desires to query. 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 ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <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 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 SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> CCI the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>CCI’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>CCI’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> CCI requires interconnection from <customer_short_name> 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, <customer_short_name> CCI shall provide its own CNAM SSP. <customer_short_name>CCI’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> CCI elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> CCI desires to query. 7.6.6 If <customer_short_name> CCI queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> CCI in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> CCI CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> FPB the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>FPB’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>FPB’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> FPB requires interconnection from <customer_short_name> 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, <customer_short_name> FPB shall provide its own CNAM SSP. <customer_short_name>FPB’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> FPB elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> FPB desires to query. 7.6.6 If <customer_short_name> FPB queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> FPB in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> FPB CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Think 12 the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>Think 12’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Think 12’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Think 12 requires interconnection from <customer_short_name> 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, <customer_short_name> Think 12 shall provide its own CNAM SSP. <customer_short_name>Think 12’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> 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 ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ BellSouth CCS7 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Think 12 desires to query. 7.6.6 If <customer_short_name> Think 12 queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ BellSouth CCS7 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 <customer_short_name> 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 <customer_short_name> Think 12 in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> Think 12 CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Telstar Communications the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> Telstar Communications 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 <customer_short_name>Telstar Communications’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Telstar Communications’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Telstar Communications requires interconnection from <customer_short_name> Telstar Communications 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> Telstar Communications shall provide its own CNAM SSP. <customer_short_name>Telstar Communications’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> Telstar Communications elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ BellSouth CCS7 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Telstar Communications desires to query. 7.6.6 If <customer_short_name> Telstar Communications queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ BellSouth CCS7 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 <customer_short_name> Telstar Communications 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> Telstar Communications in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> Telstar Communications 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> Telstar Communications CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> BCFL the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> BCFL 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 <customer_short_name>BCFL’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>BCFL’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> BCFL requires interconnection from <customer_short_name> BCFL 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> BCFL shall provide its own CNAM SSP. <customer_short_name>BCFL’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> BCFL elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> BCFL desires to query. 7.6.6 If <customer_short_name> BCFL queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> BCFL 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> BCFL in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> BCFL 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> BCFL CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Nex-Phon the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>Nex-Phon’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Nex-Phon’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Nex-Phon requires interconnection from <customer_short_name> 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, <customer_short_name> Nex-Phon shall provide its own CNAM SSP. <customer_short_name>Nex-Phon’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> 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 ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Nex-Phon desires to query. 7.6.6 If <customer_short_name> Nex-Phon queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> Nex-Phon in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> Nex-Phon CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Starlink the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> Starlink 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 <customer_short_name>Starlink’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Starlink’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Starlink requires interconnection from <customer_short_name> Starlink 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> Starlink shall provide its own CNAM SSP. <customer_short_name>Starlink’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> Starlink elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Starlink desires to query. 7.6.6 If <customer_short_name> Starlink queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> Starlink 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> Starlink in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> Starlink 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> Starlink CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> South Carolina Net the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> South Carolina Net 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 <customer_short_name>South Carolina Net’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>South Carolina Net’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> South Carolina Net requires interconnection from <customer_short_name> South Carolina Net 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> South Carolina Net shall provide its own CNAM SSP. <customer_short_name>South Carolina Net’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> South Carolina Net elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ BellSouth CCS7 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> South Carolina Net desires to query. 7.6.6 If <customer_short_name> South Carolina Net queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ BellSouth CCS7 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 <customer_short_name> South Carolina Net 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> South Carolina Net in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> South Carolina Net 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> South Carolina Net CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> OnePoint the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>OnePoint’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>OnePoint’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> OnePoint requires interconnection from <customer_short_name> 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, <customer_short_name> OnePoint shall provide its own CNAM SSP. <customer_short_name>OnePoint’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> OnePoint elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> OnePoint desires to query. 7.6.6 If <customer_short_name> OnePoint queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> OnePoint in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> OnePoint CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Preferred the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>Preferred’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Preferred’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Preferred requires interconnection from <customer_short_name> 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, <customer_short_name> Preferred shall provide its own CNAM SSP. <customer_short_name>Preferred’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> Preferred elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Preferred desires to query. 7.6.6 If <customer_short_name> Preferred queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> Preferred in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> Preferred CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> FeroNetworks the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>FeroNetworks’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>FeroNetworks’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> FeroNetworks requires interconnection from <customer_short_name> 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, <customer_short_name> FeroNetworks shall provide its own CNAM SSP. <customer_short_name>FeroNetworks’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> FeroNetworks elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> FeroNetworks desires to query. 7.6.6 If <customer_short_name> FeroNetworks queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> FeroNetworks in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> FeroNetworks CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Excel PCHP the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>Excel PCHP’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Excel PCHP’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Excel PCHP requires interconnection from <customer_short_name> 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, <customer_short_name> Excel PCHP shall provide its own CNAM SSP. <customer_short_name>Excel PCHP’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> 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 ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Excel PCHP desires to query. 7.6.6 If <customer_short_name> Excel PCHP queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> Excel PCHP in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> Excel PCHP CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Seven Bridges the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> Seven Bridges 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 <customer_short_name>’s Seven ▇▇▇▇▇▇▇’▇ access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Seven Bridges’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Seven Bridges requires interconnection from <customer_short_name> Seven Bridges 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> Seven Bridges shall provide its own CNAM SSP. <customer_short_name>Seven Bridges’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> Seven Bridges elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Seven Bridges desires to query. 7.6.6 If <customer_short_name> Seven Bridges queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> Seven Bridges 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> Seven Bridges in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> Seven Bridges 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> Seven Bridges CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> FLATEL the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> 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 <customer_short_name>FLATEL’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>FLATEL’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> FLATEL requires interconnection from <customer_short_name> 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, <customer_short_name> FLATEL shall provide its own CNAM SSP. <customer_short_name>FLATEL’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> FLATEL elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> FLATEL desires to query. 7.6.6 If <customer_short_name> FLATEL queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> 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 <customer_short_name> FLATEL in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> 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 <customer_short_name> FLATEL CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> ONS the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> ONS 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 <customer_short_name>ONS’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>ONS’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> ONS requires interconnection from <customer_short_name> ONS 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> ONS shall provide its own CNAM SSP. <customer_short_name>ONS’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> ONS elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> ONS desires to query. 7.6.6 If <customer_short_name> ONS queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> ONS 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> ONS in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> ONS 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> ONS CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> ProNet the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> ProNet 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 <customer_short_name>ProNet’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>ProNet’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> ProNet requires interconnection from <customer_short_name> ProNet 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> ProNet shall provide its own CNAM SSP. <customer_short_name>ProNet’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> ProNet elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> ProNet desires to query. 7.6.6 If <customer_short_name> ProNet queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> ProNet 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> ProNet in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> ProNet 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> ProNet CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.

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 <customer_short_name> Latin American Telephone the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> Latin American Telephone 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 <customer_short_name>Latin American Telephone’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Latin American Telephone’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> Latin American Telephone requires interconnection from <customer_short_name> Latin American Telephone 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> Latin American Telephone shall provide its own CNAM SSP. <customer_short_name>Latin American Telephone’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> Latin American Telephone elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> Latin American Telephone desires to query. 7.6.6 If <customer_short_name> Latin American Telephone queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 <customer_short_name> Latin American Telephone 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> Latin American Telephone in the BellSouth specified format and shall contain records for every working telephone number that can originate phone calls. It is the responsibility of <customer_short_name> Latin American Telephone 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> Latin American Telephone CNAM records provided for storage in the BellSouth CNAM SCP shall be available, on a SCP query basis only, to all Parties querying the BellSouth CNAM SCP. Further, CNAM service shall be provided by each Party consistent with state and/or federal regulation.