Appendix Lidb - As

LIDB & CNAM - AS (NON-UNE)/AT&T-12STATE

PAGE 1 OF 25

AT&T-12STATE/«CLECLegalName»

062907

LIDB AND CNAM – AS

(NON-UNE)

TABLE OF CONTENTS

INTRODUCTION...... 1

DEFINITIONS...... 2

GENERAL DESCRIPTION......

SERVICE DESCRIPTION...... 4

MANNER OF PROVISIONING...... 5

BILLING...... 6

PRICE AND PAYMENT...... 7

COMMUNICATION AND NOTICES........ 8

TERM AND TERMINATION...... 9

CONFIDENTIALITY...... 10

LIMITATIN OF LIABILITY...... 11

DISCLAIMER OF WARRANTIES...... 12

RELATIONSHIP OF THE PARTIES...... 13

DISPUTE RESOLUTION...... 14

ASSIGNMENT...... 15

CHOICE OF LAW...... 16

SEVERABILITY...... 17

FORCE MAJEURE...... 18

INTERVENING LAW...... 19

NON-WAIVER...... 20

TAXES...... 21

ENTIRE AGREEMENT...... 22

LIDB and CNAM – AS AGREEMENT

This LIDB and CNAM - AS Agreement (“Agreement”), dated ______,200X, is entered between AT&T Operations, Inc., as authorized agent for Southwestern Bell Telephone Company d/b/a AT&T Arkansas, AT&T Kansas, AT&T Missouri, AT&T Oklahoma and/or AT&T Texas (collectively, “AT&T SOUTHWEST REGION 5-STATE”), Pacific Bell Telephone Company d/b/a AT&T California, Illinois Bell Telephone Company d/b/a AT&T Illinois, Indiana Bell Telephone Company Incorporated d/b/a AT&T Indiana, Michigan Bell Telephone Company, d/b/a AT&T Michigan, The Ohio Bell Telephone Company d/b/a AT&T Ohio and Wisconsin Bell, Inc. d/b/a AT&T Wisconsin (collectively, “AT&T MIDWEST REGION 5-STATE”), and The Southern New England Telephone Company d/b/a AT&T Connecticut, (with AT&T SOUTHWEST REGION 5-STATE, AT&T CALIFORNIA, AT&T MIDWEST REGION 5-STATE and AT&T CONNECTICUT collectively referred to herein as AT&T-12STATE) and «CLECLegalName», a ______corporation (“Customer”). AT&T-12STATE and Customer are collectively referred to herein as the “Parties” and individually as a “Party.”

1.INTRODUCTION

1.1This Agreement sets forth the terms and conditions for storage and administration of data in the Line Information Data Base (LIDB) and/or the CNAM Database provided by the applicable AT&T Inc. (AT&T)-owned Incumbent Local Exchange Carrier (ILEC) and Customer.

1.2AT&T MIDWEST REGION 5-STATE, AT&T CONNECTICUT and AT&T NEVADA do not own a LIDB. Additionally, AT&T NEVADA and AT&T CONNECTICUT do not own a CNAM Database. Each of these companies obtain their LIDB and/or CNAM Database services as follows:

1.2.1AT&T MIDWEST REGION 5-STATE stores and administers its LIDB information on SNET DG's LIDB. AT&T MIDWEST REGION 5-STATE stores and administers its CNAM information both on its CNAM Database and on SNET DG's LIDB.

1.2.2AT&T CONNECTICUT stores and administers its LIDB and CNAM information on SNET DG's LIDB.

1.2.3AT&T NEVADA stores and administers its LIDB and CNAM information on AT&T CALIFORNIA's LIDB.

1.3Both AT&T CALIFORNIA and SNET DG also provide LIDB and/or CNAM data storage and administration for LIDB and/or CNAM information for other carriers not a party to this Agreement. Any use of the possessive in this Agreement as applied to AT&T MIDWEST REGION 5-STATE, AT&T CONNECTICUT and AT&T NEVADA will not indicate ownership but shall indicate the relationship described in paragraph 1.2.

1.4The terms, conditions, and prices for LIDB and/or CNAM data storage and administration in this Agreement will apply to data storage and administration of Customer's data for accounts that are not provided through an AT&T-13STATE switching unbundled network element (UNE) under an interconnection agreement between a CLEC and AT&T-13STATE or applicable tariff. Data storage and administration on SNET DG's LIDB for Validation Information and CNAM information in AT&T MIDWEST REGION 5-STATE AND AT&TCONNECTICUT regions will be pursuant to this Agreement. Data storage and administration for GetData, Originating Line Number Screening (OLNS), and LIDB Data Screening will be pursuant to an agreement between Customer and SNET DG. Additionally, Customer can obtain the full suite of LIDB and/or CNAM data storage and administration capabilities through a single agreement with SNET DG.

1.5Any use of the possessive in this Agreement as applied to AT&T MIDWEST REGION 5-STATE, AT&T CONNECTICUT and AT&T NEVADA will not indicate ownership but shall have the relationship described in Section 1.2.

1.6AT&T Inc. (AT&T) means the holding company which directly or indirectly owns the following ILECs: Illinois Bell Telephone Company d/b/a AT&T Illinois, Indiana Bell Telephone Company Incorporated d/b/a AT&T Indiana, Michigan Bell Telephone Company d/b/a AT&T Michigan, Nevada Bell Telephone Company d/b/a AT&TNevada, The Ohio Bell Telephone Company d/b/a AT&T Ohio, Pacific Bell Telephone Company d/b/a AT&TCalifornia, The Southern New England Telephone Companyd/b/a AT&T Connecticut, Southwestern Bell Telephone Company d/b/a AT&T Arkansas, AT&T Kansas, AT&T Missouri, AT&T Oklahoma and/or AT&T Texas and/or Wisconsin Bell, Inc. d/b/a AT&T Wisconsin.

1.7AT&T-12STATE - As used herein, AT&T-12STATE means AT&T SOUTHWEST REGION 5-STATE,AT&T MIDWEST REGION 5-STATE,AT&T CALIFONRIA and AT&T CONNECTICUT(and previously referred to as “SBC-12STATE”), the applicable AT&T-owned ILEC(s) doing business in Arkansas, California, Connecticut, Illinois, Indiana, Kansas, Michigan, Missouri, Ohio, Oklahoma, Texas and Wisconsin.

1.8AT&T-13STATE - As used herein, AT&T-13STATE means AT&T SOUTHWEST REGION 5-STATE,AT&T MIDWEST REGION 5-STATE, AT&T CALIFORNIA, AT&T NEVADAandAT&T CONNECTICUT(and previously referred to as “SBC-13STATE”), the applicable AT&T-owned ILEC(s) doing business in Arkansas, California, Connecticut, Illinois, Indiana, Kansas, Michigan, Missouri, Nevada, Ohio, Oklahoma, Texas and Wisconsin.

1.9AT&T ARKANSAS- As used herein, AT&T ARKANSAS means Southwestern Bell Telephone Company d/b/a AT&T Arkansas (and previously referred to as “SBC Arkansas”), the applicable AT&T-owned ILEC doing business in Arkansas.

1.10AT&T CALIFORNIA- As used herein, AT&T CALIFORNIA means Pacific Bell Telephone Company d/b/a AT&T California (and previously referred to as “SBC California”), the applicable AT&T-owned ILEC doing business in California.

1.11AT&TCONNECTICUT- As used herein, AT&T CONNECTICUT means The Southern New England Telephone Company d/b/a AT&T Connecticut (and previously referred to as “SBC Connecticut”), the applicable above listed ILEC doing business in Connecticut.

1.12 AT&T KANSAS - As used herein, AT&T KANSAS means Southwestern Bell Telephone Company d/b/a AT&T Kansas (and previously referred to as “SBC Kansas”), the applicable AT&T-owned ILEC doing business in Kansas.

1.13AT&T ILLINOIS -As used herein, AT&T ILLINOISmeans Illinois Bell Telephone Company d/b/a AT&T Illinois (and previously referred to as “SBC Illinois”), the applicable AT&T-owned ILEC doing business in Illinois.

1.14AT&T INDIANA -As used herein, AT&T INDIANAmeans Indiana Bell Telephone Company, Incorporated d/b/a AT&T Indiana (and previously referred to as “SBC Indiana”), the applicable AT&T-owned ILEC doing business in Indiana.

1.15AT&T MICHIGAN -As used herein, AT&T MICHIGANmeans Michigan Bell Telephone Company d/b/a AT&T Michigan (and previously referred to as “SBC Arkansas”), the applicable AT&T-owned ILEC doing business in Michigan.

1.16AT&T MIDWEST REGION 5-STATE - As used herein, AT&T MIDWEST REGION 5-STATE means Illinois Bell Telephone Company d/b/a AT&T Illinois, Indiana Bell Telephone Company Incorporated d/b/a AT&T Indiana, Michigan Bell Telephone Company d/b/a AT&T Michigan, The Ohio Bell Telephone Company d/b/a AT&T Ohio, and/or Wisconsin Bell, Inc. d/b/a AT&T Wisconsin (and previously referred to as “SBC MIDWEST REGION 5-STATE”), the applicable AT&T-owned ILEC(s) doing business in Illinois, Indiana, Michigan, Ohio and Wisconsin.

1.17AT&T MISSOURI-As used herein, AT&T MISSOURI means Southwestern Bell Telephone Company d/b/a AT&T Missouri (and previously referred to as “SBC Missouri”), the applicable AT&T-owned ILEC doing business in Missouri.

1.18AT&T NEVADA -As used herein, AT&T NEVADA means Nevada Bell Telephone Company d/b/a AT&T Nevada (and previously referred to as “SBC Nevada”), the applicable AT&T-owned ILEC doing business in Nevada.

1.19AT&T OHIO -As used herein, AT&T OHIO means The Ohio Bell Telephone Company d/b/a AT&T Ohio (and previously referred to as “SBC Ohio”), the applicable AT&T-owned ILEC doing business in Ohio.

1.20AT&T OKLAHOMA- As used herein, AT&T OKLAHOMA means Southwestern Bell Telephone Company d/b/a AT&T Oklahoma (and previously referred to as “SBC Oklahoma”), the applicable AT&T-owned ILEC doing business in Oklahoma.

1.21AT&T SOUTHWEST REGION 5-STATE - As used herein, AT&T SOUTHWEST REGION 5-STATE means Southwestern Bell Telephone Company d/b/a AT&T Arkansas, AT&T Kansas, AT&T Missouri, AT&T Oklahoma and/or AT&T Texas (and previously referred to as “SBC SOUTHWEST REGION 5-STATE”), the applicable above listed ILEC(s) doing business in Arkansas, Kansas, Missouri, Oklahoma and Texas.

1.22AT&T TEXAS - As used herein, AT&T TEXAS means Southwestern Bell Telephone Company d/b/a AT&T Texas (and previously referred to as “SBC Texas”), the applicable AT&T-owned ILEC doing business in Texas.

1.23AT&T WISCONSIN -As used herein, AT&T WISCONSINmeans Wisconsin Bell, Inc. d/b/a AT&T Wisconsin (and previously referred to as “SBC Wisconsin”), the applicable AT&T-owned ILEC doing business in Wisconsin.

1.24SNET DG- As used herein, SNET DG means SNET Diversified Group, Inc., a Connecticut corporation.

2.DEFINITIONS

2.1 “Account Owner” means a telecommunications company, including AT&T-13STATE that provides an End User’s local service and such company stores and/or administers the End User’s associated line record information and/or Group Record Information in a Party’s LIDB and/or Calling Name Database.

2.2“Act” means the Communications Act of 1934 [47 U.S.C. 153(R)], as amended by the Telecommunications Act of 1996, Public Law 104-104, 110 Stat. 56 (1996) codified throughout 47 U.S.C..

2.3“Administer or Administration” means, for the purpose of this Agreement, the ability of an Account Owner to create, modify, update, or delete its line record information in LIDB through interfaces agreed to between the Parties.

2.4"Alternate Billing Service (ABS)" means a service that allows a caller to bill calls to an account that might not be associated with the originating line. The three types of ABC calls are collect, calling card, and billed to a third party.

2.5“Assignment Authority” means a nine- to thirty-digit code-set that identifies an authorization hierarchy (also known as an object identifier). The format of the nine-digit code set is A-B-CCCC-DDD where “A” represents an international standards body, “B” represents a national standards body, “CCCC” represents a network operator, and “DDD” represents a local assignment. For code-sets from ten to thirty digits, the “DDD” section of the code is expanded to include the extra digits. An Assignment Authority plus a Custom ID comprise the unique identifier of a LIDB Custom Data Element.

2.6"Billed Number Screening (BNS) Query" means a request to validate a request to bill a call collect to the called party or to a third number that is neither the calling or the called party.

2.7“Billing Clearinghouse” means a billing and collection service bureau for Interexchange Carriers and other telecommunication companies which become members and wish to arrange for the billing and collection of services provided to End Users.

2.8"Calling Card Query" means a request to validate the use of a calling card account.

2.9"Calling Name Database and/or CNAM Database" means an AT&T MIDWEST REGION 5-STATE's Database containing Calling Name information that is separate from a LIDB.

2.10“Calling Name Information and/or CNAM Information” means a telecommunications company’s records of its subscriber’s names associated with one or more customer-assigned ten-digit telephone numbers.

2.11“Complete Screen” means that the Query-originator was denied access to all of the information it requested in its Query.

2.12“Custom Data Element” means a Data Element that applies to a specific LIDB or to a specific Account Owner on a specific LIDB. Custom Data Elements do not have a Transaction Capabilities Application Part (TCAP) ID. Instead, they have a unique combination of Assignment Authority and Custom ID. Custom Data Elements are not defined by Telcordia Technologies’ Generic Requirements. Validation, Originating Line Number Screening (OLNS), and CNAM Queries cannot retrieve custom Data Elements.

2.13“Custom ID” means a unique two- to five-digit code-set assigned by a LIDB owner to each Custom Data Element stored in a LIDB. A Custom ID plus an Assignment Authority comprise the unique identifier of a LIDB Custom Data Element.

2.14"Customer" means an Account Owner or other entity or an agent acting on behalf of such entities, who contracts with AT&T-12STATE to store and administer data on and AT&T-12STATE LIDB and/or CNAM Database.

2.15“Data Clearinghouse” means a service bureau for companies that arrange for the collection of data from various sources to arrange for the billing and/or provisioning of services that require data from multiple sources, including LIDB.

2.16“Data Element” means a line record informational component that has a unique identifier. Data Elements are identified either as Custom Data Elements or as Standard Elements depending on the type of unique identifier.

2.17“Data Screening” (or LIDB Data Screening) means a security capability administered by a LIDB owner that gives LIDB the ability to allow, deny, or limit the information returned to a Query-originator.

2.18“Database” (or Data Base) means an integrated collection of related data. In the case of LIDB, the database is the line number and related line information as well as the service logic that provides the transactional processing capability.

2.19"ENUM" means a protocol developed in the Internet Engineering Task Force (IETF) Request for Comment (RFC) 2916 for fetching (searching and retrieving) Universal Resource Identifiers (URIs) given an International Telecommunications Union (ITU) E.164 number. ENUM translates an E.164 domestic or international telephone number into a series of Internet addresses or Universal Resource Identifiers (URIs)

2.20“GetData” means the capability of a LIDB owner to process and respond to GetData Queries as well as to create Custom Data Elements and Standard Data Elements accessible via GetData Query processing logic.

2.21“GetData Query” means a specific LIDB Query-type transmitted over the CCS/SS7 network that allows a Query-originator to invoke LIDB GetData query processing logic and thereby extract data from LIDB.

2.22“Level 1 Data Screening” means a security capability administered by a LIDB owner that gives LIDB the ability to allow, deny, or limit the information it returns to a Query-originator on a per Data Element, per Query-Type, and per LIDB basis.

2.23“Level 2 Data Screening” means a security capability that is Administered by a LIDB owner at the direction or request of an Account Owner or Query Originator. This capability gives LIDB the ability to allow, deny, or limit the information it returns to a Query-originator on a per Data Element, per Query-Type, per Account Owner, and per LIDB basis.

2.24“Local Service Request Process or LSR Process” means a process available to telecommunications companies that use an AT&T-12STATElocal switching element that is not compatible with unbundled electronic interfaces for the purposes of data storage and administration of information on a LIDB and/or CNAM Database

2.25“Originating Line Number Screening” (OLNS) means a specific LIDB Query-type that requests the originating call processing, billing, and service profiles of an telephone number.

2.26“Originating Point Code” (OPC) means a 9-digit code that identifies the Service Platform from which a Query originates and to which a Response is returned.

2.27“Partial Screen” means that the Query-originator, as identified in the appropriate layer of the query/message, is denied access to some of the information it requested in its Query.

2.28“Personal Identification Number” (PIN) means a confidential four-digit code number provided to a calling card customer to prevent unauthorized use of his/her calling card number. LIDB and/or the LIDB administrative system can store a PIN for those line numbers that have an associated calling card.

2.29“Query” means a message that represents a request to a Database for information.

2.30“Query Transport Rate” means a per-query usage rate that applies to certain Queries transported from an AT&T-12STATE STP to the SCP where LIDB resides and back.

2.31“Response” means a message that, when appropriately interpreted, represents an answer to a Query.

2.32“Standard Data Element” means a data element in LIDB that has a unique Transaction Capabilities Application Part (TCAP) ID and is defined in Telcordia Technologies’ Generic Requirements documentation.

2.33“Terminating Point Code” means a 9-digit code that identifies the network node that will receive a Query or a Response.

2.34“Service Platform” means the physical platform that generates GetData Queries and is identified to LIDB by an Originating Point Code contained in the Query. A service platform may be a telephony switch, an SCP, or any other platform capable of correctly formatting and launching GetData Queries and receiving the associated Response.

2.35“Validation Information” means an Account Owner’s records of all of its Calling Card Service and Toll Billing Exception Service.

2.36“Validation Query” means collectively both Calling Card Query and Billed Number Screening (BNS) Query.

3.GENERAL DESCRIPTION

3.1The Line Information Data Base (LIDB) and CNAM Database are transaction-oriented databases that function as a centralized repository for data storage and retrieval. LIDB and CNAM Database are accessible through Common Channel Signaling (CCS) networks. LIDB contains records associated with customer telephone Numbers and Special Billing Numbers (which includes CNAM data). CNAM Database contains name information associated with customer telephone numbers. LIDB and CNAM Databases accept Queries from other network elements and provide return result, return error, and return reject responses as appropriate. In AT&T SOUTHWEST REGION 5-STATE, AT&T CALIFORNIA, AT&T NEVADA, and AT&T CONNECTICUT, LIDB and CNAM are not separated; instead, CNAM information is contained in LIDB. AT&T MIDWEST REGION 5-STATE's CNAM information also resides on the LIDB used by AT&T MIDWEST REGION 5-STATE; however, CNAM Queries are currently processed in the AT&T MIDWEST REGION 5-STATE's CNAM Database

3.2All CNAM information is currently administered through a LIDB SMS.

3.3AT&T-12STATE’s LIDB is connected directly to a Service Management System (SMS) and a database editor (i.e., LIDB Editor) that provide AT&T-12STATE with the capability of creating, modifying, changing, or deleting, line record in LIDB. AT&T-12STATE’s LIDB is also connected directly to an adjunct fraud monitoring system.

3.4From time-to-time, AT&T-12STATE enhances its LIDB to create new services and/or LIDB capabilities. Such enhancements may involve the creation of new line-level or group-level Data Elements in LIDB. Both Parties understand and agree that some LIDB enhancements will require Customer to update its line records with new or different information. Nothing herein shall require AT&T-12STATE to make any enhancements to its LIDB except at its sole discretion.

3.5Customer will submit all requests to create, modify, and delete, line records in LIDB and/or CNAM Database through the interfaces described in section 4 as appropriate. AT&T-12STATE will not accept, and Customer will not send, manual update requests for data Administration (e.g., faxes and emails).

4.SERVICE DESCRIPTION

4.1Unbundled electronic access to the LIDB SMS provides Customer with the capability to access and Administer Customer's line record information in LIDB.

4.2Customer cannot use any of the unbundled, electronic interfaces AT&T-12STATE provides under this Agreement to access and/or Administer any line records that are Administered by another Account Owner or company. Customer is also unable to use any of the unbundled electronic interfaces to access and/or Administer any data for which Customer may be the Account Owner but for which Customer Administers such data through the LSR Process Customer may have obtained through another Agreement..