CNAM Database Service Clause Samples

The CNAM Database Service clause defines the terms under which a party provides access to or use of the Calling Name (CNAM) database, which associates telephone numbers with caller names for display on recipient devices. This clause typically outlines the scope of the service, any usage restrictions, and the responsibilities of both the service provider and the customer, such as data accuracy and update frequency. Its core function is to ensure that both parties understand their obligations regarding the provision and use of CNAM data, thereby facilitating accurate caller identification and reducing the risk of miscommunication or fraud.
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 AFN the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 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 AFN’s access to BellSouth’s CNAM Database Services and shall be addressed to AFN’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to AFN requires interconnection from AFN to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, AFN shall provide its own CNAM SSP. AFN’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If AFN elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 AFN desires to query. 7.6.6 If AFN queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ 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 AFN for initial CNAM record load and/or updates shall be determined by mutual agreement. The initial load...
CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides <customer_short_name> the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 <customer_short_name> shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to <customer_short_name>’s access to BellSouth’s CNAM Database Services and shall be addressed to <customer_short_name>’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to <customer_short_name> requires interconnection from <customer_short_name> to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, <customer_short_name> shall provide its own CNAM SSP. <customer_short_name>’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If <customer_short_name> elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia's TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish CCS7 interconnection at the BellSouth Local Signal Transfer Points (LSTPs) serving the BellSouth CNAM SCPs that <customer_short_name> desires to query. 7.6.6 If <customer_short_name> queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the ▇▇▇▇▇▇▇▇▇ ▇▇▇▇ network according to BellSouth's Common Channel Signaling Interconnection Guidelines and Telcordia’s TR-TSV-000905 CCS Network Interface Specification. In addition, the third party provider shall establish SS7 interconnection at one or more of the BellSouth Gateway STPs. The payment of all costs associated with the transport of SS7 signals via a third party will be established by mutual agreement of the Parties and this Agreement shall be amended in accordance with modification of the General T...
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 CBX One-Stop the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
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 BTI the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 BTI shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) days prior to BTI’s access to BellSouth’s CNAM Database Services and shall be addressed to BTI’s Local Contract Manager. 7.6.2.1 BTI’s End Users’ names and numbers related to UNE-P Services and shall be stored in the BellSouth CNAM database, and shall be available, on a per query basis only, to all entities that launch queries to the BellSouth CNAM database. BellSouth, at its sole discretion, may opt to interconnect with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailable. 7.6.2.2 For each BTI End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section

Related to CNAM Database Service

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/E-Verify.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.