CNAM Database Service for Facility Based Customers Sample Clauses

CNAM Database Service for Facility Based Customers. 7.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 CommuniGroup the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs. 7.2 CommuniGroup 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 CommuniGroup’s access to BellSouth’s CNAM Database Services and shall be addressed to CommuniGroup’s Local Contract Manager. 7.3 BellSouth's provision of CNAM Database Services to CommuniGroup requires interconnection from CommuniGroup to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement. 7.4 In order to formulate a CNAM query to be sent to the BellSouth CNAM SCP, CommuniGroup shall provide its own CNAM SSP. CommuniGroup’s CNAM SSPs must be compliant with TR-NWT-001188, "CLASS Calling Name Delivery Generic Requirements". 7.5 If CommuniGroup 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 CommuniGroup desires to query. 7.6 If CommuniGroup 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.7 The mechanism to be used by CommuniGroup for ini...
Sample 1See All (7)
AutoNDA by SimpleDocs
CNAM Database Service for Facility Based Customers. 7.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 Your Communication Connection Group the opportunity to load and store its subscriber names in the BellSouth CNAM SCPs.
Sample 1
CNAM Database Service for Facility Based Customers. XxxxXxxxx's provision of CNAM Database Services to Clearwave Communications requires interconnection from Clearwave Communications to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement.
Sample 1
CNAM Database Service for Facility Based Customers. BellSouth's provision of CNAM Database Services to NGTelecom requires interconnection from NGTelecom to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement.
Sample 1
CNAM Database Service for Facility Based Customers. BellSouth's provision of CNAM Database Services to Grande requires interconnection from Grande to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement.
Sample 1
CNAM Database Service for Facility Based Customers. BellSouth's provision of CNAM Database Services to GSC requires interconnection from GSC to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement.
Sample 1
CNAM Database Service for Facility Based Customers. BellSouth's provision of CNAM Database Services to Aero requires interconnection from Aero to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement.
Sample 1
AutoNDA by SimpleDocs
CNAM Database Service for Facility Based Customers. BellSouth's provision of CNAM Database Services to Southern Telcom requires interconnection from Southern Telcom to BellSouth CNAM SCPs. Such interconnections shall be established pursuant to Attachment 3 of this Agreement.
Sample 1

Related to CNAM Database Service for Facility Based Customers

  • Processing of Customer Personal Data 3.1 UKG will: 3.1.1 comply with all applicable Data Protection Laws in the Processing of Customer Personal Data; and 3.1.2 not Process Customer Personal Data other than for the purpose, and in accordance with, the relevant Customer’s instructions as documented in the Agreement and this DPA, unless Processing is required by the Data Protection Laws to which the relevant UKG Processor is subject, in which case UKG to the extent permitted by the Data Protection Laws, will inform Customer of that legal requirement before the Processing of that Customer Personal Data. 3.2 Customer hereby: 3.2.1 instructs UKG (and authorizes UKG to instruct each Subprocessor) to: (a) Process Customer Personal Data; and (b) in particular, transfer Customer Personal Data to any country or territory subject to the provisions of this DPA, in each case as reasonably necessary for the provision of the Services and consistent with the Agreement. 3.2.2 warrants and represents that it is and will at all relevant times remain duly and effectively authorized to give the instructions set out in Section 3.2.1 on behalf of each relevant Customer Affiliate; and 3.2.3 warrants and represents that it has all necessary rights in relation to the Customer Personal Data and/or has collected all necessary consents from Data Subjects to Process Customer Personal Data to the extent required by Applicable Law. 3.3 Schedule 1 to this DPA sets out certain information regarding UKG’s Processing of Customer Personal Data as required by Article 28(3) of the GDPR (and equivalent requirements of other Data Protection Laws).

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • END USER AGREEMENTS (“EUA GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.

  • Competitive Supplier’s Standard Credit Policy The Competitive Supplier will not require a credit review for any consumer participating in the Program, nor does Competitive Supplier require any consumer to post any security deposit as a condition for participation in the Program. The Competitive Supplier may terminate service to a Participating Consumer and return such consumer to Basic Service in the event that the consumer fails to pay to Competitive Supplier amounts past-due greater than sixty (60) days.

  • Return of Customer Data Okta shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and time periods specified in the Trust & Compliance Documentation, unless the retention of the data is requested from Okta according to mandatory statutory laws.

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