DATABASES AND SIGNALING. 17.1 Each Party shall provide the other Party with access to databases, including LIDB and toll-free service access codes (i.e. 800/888), and associated signaling necessary for call routing and completion of Covad's traffic through the provision of SS7 Common Channel Signaling (CCIS) under its applicable tariffs. Alternatively, either Party may secure CCS Interconnection from a commercial SS7 hub provider, and in that case the other Party will permit the purchasing Party to access the same databases as would have been accessible if the purchasing party had connected directly to the other Party's CCISnetwork.
17.2 The Parties will provide CCIS Signaling to each other, where and as available, in conjunction with all Local Traffic, Toll Traffic, Meet Point Billing Traffic, and Transit Traffic. The Parties will cooperate on the exchange of TCAP messages to facilitate interoperability of CCIS-based features between their respective networks, including all CLASS features and functions, to the extent each Party offers such features and functions to its Customers. All CCIS Signaling parameters will be provided upon request (where available), including called party number, calling party number, originating line information, calling party category, and charge number. All privacy indicators will be honored. The Parties will follow all Ordering and Billing Forum-adopted standards pertaining to CIC/OZZ codes. Where CCIS Signaling is not available, in-band multi-frequency (MF) wink start signaling will be provided. Any such MF arrangement will require a separate local trunk circuit between the Parties' respective switches in those instances where the Parties have established End Office to End Office high usage trunk groups. In such an arrangement, each Party will outpulse the full ten-digit telephone number of the called party to the other Party.
17.3 Each Party shall provide trunk groups, where available and upon reasonable request, that are configured utilizing the B8ZS ESF protocol for 64 kbps clear channel transmission to allow for ISDN interoperability between the Parties' respective networks.
17.4 The following publications describe the practices, procedures and specifications generally utilized by BA for signaling purposes and is listed herein to assist the Parties in meeting their respective Interconnection responsibilities related to Signaling:
(a) Bellcore Generic Requirements, GR-905-CORE, Issue 1, March, 1995, and subsequent issues and amendments; and
(b) Xx...
DATABASES AND SIGNALING. Subject to the conditions set forth in Section 1.7 of this Part II, VERIZON shall provide SPRINT with access to databases and associated signaling necessary for call routing and completion by providing SS7 Common Channel Signaling (“CCS”) Interconnection, and Interconnection and access to toll-free service access code (e.g., 800/888/877) databases, LIDB, and any other necessary databases, in accordance with Part IV and VERIZON’s DTE MA No. 17 Tariff, as amended from time to time. SPRINT shall provide VERIZON with CCS Interconnection required for call routing and completion, and the billing of calls which involve SPRINT’s Customers, at non-discriminatory rates, terms and conditions in accordance with Section 24.11 of the General Terms and Conditions, provided further that if the SPRINT information VERIZON requires to provide such call-related functionalities is resident in a database, SPRINT will provide VERIZON with the access and authorization to query SPRINT’s information in the databases within which it is stored. Alternatively, either Party may secure CCS Interconnection from a commercial SS7 hub provider, and in that case the other Party will permit the purchasing Party to access the same databases as would have been accessible if the purchasing Party had connected directly to the other Party’s CCS network. In either case, SPRINT shall comply with VERIZON’s SS7 certification process prior to establishing CCS Interconnection with VERIZON
DATABASES AND SIGNALING. Subject to Section 11.0, BA shall provide NorthPoint with interfaces to access BA's databases, including LIDB and toll-free service access codes (e.g., 800/888/877), and associated signaling necessary for the routing and completion of NorthPoint’s traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. NYNEX shall provide NEFC with interfaces to access NYNEX's databases, including LIDB and 800/888, as well as DCAS for ordering and provisioning purposes, and associated signaling necessary for the routing and completion of NEFC's traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. Subject to Section 11.0, BA shall provide Compass with interfaces to access BA's databases, including LIDB and toll-free service access codes (e.g., 800/888/877), and associated signaling necessary for the routing and completion of Compass’s traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. BA shall provide Covad with interfaces to access BA's databases, including LIDB and toll-free service access codes (i.e.; 800/888), and associated signaling necessary for the routing and completion of Covad’s traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. Subject to Section 11.0, BA shall provide MFN with interfaces to access BA's databases, including LIDB and toll-free service access codes (e.g., 800/888/877), and associated signaling necessary for the routing and completion of MFN’s traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. BA shall provide MGC with interfaces to access BA's databases, including LIDB and toll-free service access codes (i.e.; 800/888), and associated signaling necessary for the routing and completion of MGC's traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. NYNEX shall provide XXXXXX FIBER with interfaces to access NYNEX's databases, including LIDB and 800/888, as well as DCAS for ordering and provisioning purposes, and associated signaling necessary for the routing and completion of XXXXXX FIBER's traffic through the provision of SS7 under its applicable tariffs.
DATABASES AND SIGNALING. 14.1 Each Party shall provide the other Party with access to databases and associated signaling necessary for call routing and completion, including but not limited to calling name information as required, by providing SS7 Common Channel Signaling (CCS) Interconnection in accordance with existing Tariffs, and Interconnection and access to 800/888 databases, LIDB, and any other necessary databases in accordance with existing Tariffs and/or agreements with other unaffiliated carriers, with compensation terms in accordance with Section 14.3 below. Alternatively, either Party may secure CCS Interconnection from a commercial SS7 hub provider, and in that case the other Party will permit the purchasing Party to access the same databases as would have been accessible if the purchasing party had connected directly to the other Party's CCS network.
14.2 The Parties will provide CCS Signaling to one another in all direct or indirect Interconnection trunking arrangements. The Parties will cooperate on the exchange of TCAP messages to facilitate interoperability of all CCS-based features and services, including but not limited to CLASS and Calling Name Delivery, to the extent each Party offers such features and functions to its Customers. All CCS Signaling parameters will be provided upon request (where such parameters are available and support signaling features and functions deployed within both Parties' networks), including called party number, Calling Party Number, calling party category, and charge number. All privacy indicators will be honored.
14.3 The Parties agree that their respective CCS signaling costs shall offset each other, and no explicit compensation between the Parties shall apply.
