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 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 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 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 <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.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
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> ITC^DeltaCom the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> 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) calendar days prior to <customer_short_name>ITC^DeltaCom’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>ITC^DeltaCom’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 ITC^DeltaCom’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 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 service 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 ITC^DeltaCom’s End User. ITC^DeltaCom shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an ITC^DeltaCom End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, 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 ITC^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 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 ITC^DeltaCom’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
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> PLI the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> 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 <customer_short_name>PLI’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>PLI’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> PLI requires interconnection from <customer_short_name> 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, <customer_short_name> PLI shall provide its own CNAM SSP. <customer_short_name>PLI’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements".
7.6.5 If <customer_short_name> 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 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> PLI desires to query.
7.6.6 If <customer_short_name> 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-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> 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 <customer_short_name> PLI 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> 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 <customer_short_name> PLI 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.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
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> AFN the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> 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 <customer_short_name>AFN’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>AFN’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> AFN requires interconnection from <customer_short_name> 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, <customer_short_name> AFN shall provide its own CNAM SSP. <customer_short_name>AFN’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements".
7.6.5 If <customer_short_name> 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 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> AFN desires to query.
7.6.6 If <customer_short_name> 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-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> 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 <customer_short_name> AFN 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> 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 <customer_short_name> AFN 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.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
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> MRC the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> 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) calendar days prior to <customer_short_name>MRC’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>MRC’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 MRC’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 service 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 be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent 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 state and/or federal regulationthe Caller ID feature.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
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 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 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 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 <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.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
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> Covad the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Covad 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>Covad’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Covad’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Covad’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Covad 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 service 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 Covad’s End User. Covad shall be provided by pay the rates set forth in Exhibit C of Attachment 2 of the Agreement, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an Covad End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Covad 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 Covad’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall xxxx Covad at the applicable rates set forth in Exhibit C of Attachment 2 of the Agreement based on a surrogate of two hundred and fifty-six (256) database queries per month per Covad’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> U-Dial the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> U-Dial 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>U-Dial’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>U-Dial’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 U-Dial’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 U-Dial 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 service 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 U-Dial’s End User. U-Dial shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an U-Dial End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, U-Dial 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 U-Dial’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall bill U- Dial 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 U-Dial’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> NGTelecom the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> NGTelecom 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>NGTelecom’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>NGTelecom’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 NGTelecom’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 NGTelecom 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 service 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 NGTelecom’s End User. NGTelecom shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent with state and/or federal regulationquery to the BellSouth CNAM database made on behalf of an NGTelecom End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, NGTelecom 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 NGTelecom’s End Users.
Appears in 1 contract
Samples: Interconnection Agreement
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> Cinergy the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Cinergy 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>Cinergy’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Cinergy’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Cinergy’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Cinergy 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 service 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 Cinergy’s End User. Cinergy shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an Cinergy End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Cinergy 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 Cinergy’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 Cinergy 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 Cinergy’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> Level 3 the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Xxxxx 0 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>Level 3’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Level 3’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Level 3’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Xxxxx 0 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 service 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 Level 3’s End User. Level 3 shall be provided by pay the rates set forth in Exhibit A of Attachment 2 of the Agreement, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an Level 3 End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Xxxxx 0 xxxxx xxxxxxxxx BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of Level 3’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall xxxx Level 3 at the applicable rates set forth in Exhibit A of Attachment 2 of the Agreement based on a surrogate of two hundred and fifty-six (256) database queries per month per Level 3’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> Grande the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Grande 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>Grande’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Grande’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Grande’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Grande 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 service 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 Grande’s End User. Grande shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent with state and/or federal regulationquery to the BellSouth CNAM database made on behalf of an CUSTOMER End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Grande 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 Grande’s End Users.
Appears in 1 contract
Samples: Interconnection Agreement
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> NationNET the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> NationNET 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>NationNET’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>NationNET’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 NationNET’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 NationNET 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 service 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 NationNET’s End User. NationNET shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of a NationNET End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, NationNET 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 NationNET’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall xxxx NationNET 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 NationNET’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> Aero the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Aero 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>Aero’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Aero’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Aero’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Aero 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 service 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 Aero’s End User. Aero shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent with state and/or federal regulationquery to the BellSouth CNAM database made on behalf of an Aero End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Aero 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 Aero’s End Users.
Appears in 1 contract
Samples: Interconnection Agreement
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> US South the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> US South 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>US South’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>US South’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 US South’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 US South 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 service 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 US South’s End User. US South shall be provided by pay the rates set forth in Exhibit B of Attachment 2 of the Agreement, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an US South End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, US South 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 US South’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall xxxx US South at the applicable rates set forth in Exhibit B of Attachment 2 of the Agreement based on a surrogate of two hundred and fifty-six (256) database queries per month per US South’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> Nexus the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Nexus 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>Nexus’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Nexus’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Nexus’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Nexus 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 service 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 Nexus’s End User. Nexus shall be provided by pay the rates set forth in Exhibit A of Attachment 2 of the Agreement, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an Nexus End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Nexus 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 Nexus’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall bill Nexus at the applicable rates set forth in Exhibit A of Attachment 2 of the Agreement based on a surrogate of two hundred and fifty-six (256) database queries per month per Nexus’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> Kinetix the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Kinetix 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>Kinetix’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Kinetix’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Kinetix’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Kinetix 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 service 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 Kinetix’s End User. Kinetix shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an Kinetix End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Kinetix 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 Kinetix’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 Kinetix 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 Kinetix’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> PBT the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> PBT 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>PBT’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>PBT’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 PBT’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 PBT 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 service 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 PBT’s End User. PBT shall be provided by pay the rates set forth in Exhibit B of Attachment 2 of the Agreement, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an PBT End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, PBT 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 PBT’s End Users.
7.6.3 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall xxxx PBT at the applicable rates set forth in Exhibit B of Attachment 2 of the Agreement based on a surrogate of two hundred and fifty-six (256) database queries per month per PBT’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
CNAM Database Service. 7.6.1 16.7.5.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> Nexus the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> 16.7.5.2 Nexus 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>Nexus’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Nexus’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 16.7.5.3 Nexus’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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.
16.7.5.4 For each Nexus 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 service database, or, subject to Section 18.7.5.3 above, to a third party calling name database, to provide calling name information, if available, to Nexus’s End User. Nexus shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent query to the BellSouth CNAM database made on behalf of an Nexus End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Nexus 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 Nexus’s End Users.
16.7.5.5 BellSouth currently does not have a billing mechanism for CNAM queries. Until a mechanized billing solution is available for CNAM queries, BellSouth shall xxxx Nexus 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 Nexus’s End Users with state and/or federal regulationthe Caller ID feature.
Appears in 1 contract
Samples: Interconnection Agreement
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> Clearwave Communications the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> Clearwave 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>Clearwave Communications’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>Clearwave Communications’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 Clearwave Communications’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 Clearwave Communications 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 service 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 Clearwave Communications’s End User. Clearwave Communications shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent with state and/or federal regulationquery to the BellSouth CNAM database made on behalf of an Clearwave Communications End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, Clearwave Communications 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 Clearwave Communications’s End Users.
Appears in 1 contract
Samples: Interconnection Agreement
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> GSC the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
7.6.2 <customer_short_name> GSC 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>GSC’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>GSC’s Local Contract Manager.
7.6.3 BellSouth's provision of CNAM Database 7.6.2.1 GSC’s End Users’ names and numbers related to UNE-P Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections and 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 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 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 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 <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 stored in the BellSouth CNAM SCP database, and shall be available, on a SCP per query basis only, to all Parties querying entities that launch queries to the BellSouth CNAM SCPdatabase. FurtherBellSouth, 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 GSC 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 service 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 GSC’s End User. GSC shall be provided by pay the rates set forth in Exhibit A, on a per query basis, for each Party consistent with state and/or federal regulationquery to the BellSouth CNAM database made on behalf of an GSC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, GSC 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 GSC’s End Users.
Appears in 1 contract
Samples: Interconnection Agreement
