CNAM Database Service Sample Clauses

CNAM Database Service. 7.6.1 CNAM is the ability to associate a name with the calling party number, allowing the End User (to which a call is being terminated) to view the calling party's name before the call is answered. The calling party’s information is accessed by queries launched to the CNAM database. This service also provides MRC the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 MRC shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) days prior to MRC’s access to BellSouth’s CNAM Database Services and shall be addressed to MRC’s Local Contract Manager. 7.6.2.1 MRC’s End Users’ names and numbers related to UNE-P Services and shall be stored in the BellSouth CNAM database, and shall be available, on a per query basis only, to all entities that launch queries to the BellSouth CNAM database. BellSouth, at its sole discretion, may opt to interconnect with and query other calling name databases. In the event BellSouth does not query a third party calling name database that stores the calling party’s information, BellSouth cannot deliver the calling party’s information to a called End User. In addition, BellSouth cannot deliver the calling party’s information where the calling party subscribes to any service that would block or otherwise cause the information to be unavailable. 7.6.2.2 For each MRC End User that subscribes to a switch based vertical feature providing calling name information to that End User for calls received, BellSouth will launch a query on a per call basis to the BellSouth CNAM database, or, subject to Section 7.6.2.1 above, to a third party calling name database, to provide calling name information, if available, to MRC’s End User. MRC shall pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an MRC End User that subscribes to the appropriate vertical features that support Caller ID or a variation thereof. In addition, MRC shall reimburse BellSouth for any charges BellSouth pays to third party calling name database providers for queries launched to such database providers for the benefit of MRC’s End Users. 7.6.3 BellSouth shall xxxx for CNAM queries the rate set forth in Exhibit A. In the event BellSouth is unable to xxxx per query, BellSouth shall xxxx MRC at the applicable rates set forth in Exhibit A based on a surrogate of two hundred a...
AutoNDA by SimpleDocs
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 Clearwave Communications the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 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) days prior to Clearwave Communications’s access to BellSouth’s CNAM Database Services and shall be addressed to Clearwave Communications’s Local Contract Manager. 7.6.2.1 Clearwave Communications’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 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 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 pay the rates set forth in Exhibit A, on a per query basis, for each query to the BellSouth CNAM database made on behalf of an 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.
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 Latin American Telephone the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.6.2 Latin American Telephone shall submit to BellSouth a notice of its intent to access and utilize BellSouth CNAM Database Services. Said notice shall be in writing no less than sixty (60) calendar days prior to Latin American Telephone’s access to BellSouth’s CNAM Database Services and shall be addressed to Latin American Telephone’s Local Contract Manager. 7.6.3 BellSouth's provision of CNAM Database Services to Latin American Telephone requires interconnection from Latin American Telephone to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.6.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, Latin American Telephone shall provide its own CNAM SSP. Latin American Telephone’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.6.5 If Latin American Telephone elects to access the BellSouth CNAM SCP via a third party CCS7 transport provider, the third party CCS7 provider shall interconnect with the 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 Latin American Telephone desires to query. 7.6.6 If Latin American Telephone queries the BellSouth CNAM SCP via a third party national SS7 transport provider, the third party SS7 provider shall interconnect with the 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 w...
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

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!