{"component": "clause", "props": {"groups": [{"snippet": "4.3.2.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, 6/1/90. The requirements for Tandem Switching include, but are not limited to the following:\n4.3.2.1.1 Tandem Switching shall provide signaling to establish a tandem connection;\n4.3.2.1.2 Tandem Switching will provide screening as jointly agreed to by Talk America and BellSouth;\n4.3.2.1.3 Tandem Switching shall provide Advanced Intelligent Network triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability;\n4.3.2.1.4 Tandem Switching shall provide access to Toll Free number database;\n4.3.2.1.5 Tandem Switching shall provide connectivity to PSAPs where 911 solutions are deployed and the tandem is used for 911; and\n4.3.2.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers.\n4.3.2.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to Talk America.\n4.3.2.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner.\n4.3.2.4 Tandem Switching shall process originating toll-free traffic received from Talk America\u2019s local switch.\n4.3.2.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element, to the extent such Tandem Switch has such capability.", "size": 217, "snippet_links": [{"key": "tandem-switching", "type": "clause", "offset": [8, 24]}, {"key": "or-equivalent", "type": "definition", "offset": [58, 71]}, {"key": "requirements-for", "type": "clause", "offset": [173, 189]}, {"key": "not-limited", "type": "clause", "offset": [224, 235]}, {"key": "to-establish", "type": "clause", "offset": [305, 317]}, {"key": "will-provide", "type": "clause", "offset": [366, 378]}, {"key": "agreed-to-by", "type": "definition", "offset": [400, 412]}, {"key": "talk-america", "type": "definition", "offset": [413, 425]}, {"key": "advanced-intelligent-network", "type": "clause", "offset": [482, 510]}, {"key": "not-available", "type": "clause", "offset": [566, 579]}, {"key": "end-office-switch", "type": "clause", "offset": [601, 618]}, {"key": "to-the-extent", "type": "clause", "offset": [620, 633]}, {"key": "access-to", "type": "clause", "offset": [715, 724]}, {"key": "toll-free-number-database", "type": "clause", "offset": [725, 750]}, {"key": "where-appropriate", "type": "clause", "offset": [894, 911]}, {"key": "for-the-purpose-of", "type": "definition", "offset": [957, 975]}, {"key": "transit-traffic", "type": "definition", "offset": [984, 999]}, {"key": "other-carriers", "type": "definition", "offset": [1012, 1026]}, {"key": "performed-by", "type": "clause", "offset": [1187, 1199]}, {"key": "reports-of", "type": "clause", "offset": [1227, 1237]}, {"key": "the-testing", "type": "definition", "offset": [1238, 1249]}, {"key": "available-to", "type": "definition", "offset": [1264, 1276]}, {"key": "a-non", "type": "clause", "offset": [1402, 1407]}, {"key": "local-switching", "type": "definition", "offset": [1691, 1706]}, {"key": "network-element", "type": "definition", "offset": [1707, 1722]}], "samples": [{"hash": "luf4n0ZrHxr", "uri": "/contracts/luf4n0ZrHxr#technical-requirements", "label": "Telecommunications", "score": 21.0, "published": true}, {"hash": "lNiGo8nA7tz", "uri": "/contracts/lNiGo8nA7tz#technical-requirements", "label": "Bellsouth\u00ae / Clec Agreement", "score": 21.0, "published": true}, {"hash": "azMoDQ0Ir6", "uri": "/contracts/azMoDQ0Ir6#technical-requirements", "label": "Clec Agreement", "score": 21.0, "published": true}], "hash": "2b76a79040c82807cf19e91151c1f9a2", "id": 1}, {"snippet": "7.3.2.1 BellSouth will offer to <customer_short_name> any additional capabilities that are developed for LIDB during the life of this Agreement.\n7.3.2.2 BellSouth shall process <customer_short_name>\u2019s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to <customer_short_name> what additional functions (if any) are performed by LIDB in the BellSouth network.\n7.3.2.3 Within two (2) weeks after a request by <customer_short_name>, BellSouth shall provide <customer_short_name> with a list of the customer data items, which <customer_short_name> would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values.\n7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year.\n7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year.\n7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year.\n7.3.2.7 All additions, updates and deletions of <customer_short_name> data to the LIDB shall be solely at the direction of <customer_short_name>. Such direction from <customer_short_name> will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation).\n7.3.2.8 BellSouth shall provide priority updates to LIDB for <customer_short_name> data upon <customer_short_name>\u2019s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact.\n7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of <customer_short_name> customer records will be missing from LIDB, as measured by <customer_short_name> audits. BellSouth will audit <customer_short_name> records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated <customer_short_name> contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to <customer_short_name> within one (1) business day of audit. Once reconciled records are received back from <customer_short_name>, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact <customer_short_name> to negotiate a time frame for the updates, not to exceed three (3) business days.\n7.3.2.10 BellSouth shall perform backup and recovery of all of <customer_short_name>\u2019s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release.\n7.3.2.11 BellSouth shall provide <customer_short_name> with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between <customer_short_name> and BellSouth.\n7.3.2.12 BellSouth shall prevent any access to or use of <customer_short_name> data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by <customer_short_name> in writing.\n7.3.2.13 BellSouth shall provide <customer_short_name> performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or \u2587\u2587\u2587-0/1XX wholly or partially owned by <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from <customer_short_name> the screening information associated with LIDB Data Screening of <customer_short_name> data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to <customer_short_name> under the BFR/NBR Process as set forth in Attachment 11.\n7.3.2.14 BellSouth shall accept queries to LIDB associated with <customer_short_name> customer records and shall return responses in accordance with industry standards.\n7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards.\n7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.", "size": 131, "snippet_links": [{"key": "life-of-this-agreement", "type": "definition", "offset": [121, 143]}, {"key": "customer-records", "type": "definition", "offset": [201, 217]}, {"key": "with-respect-to", "type": "clause", "offset": [278, 293]}, {"key": "additional-functions", "type": "clause", "offset": [371, 391]}, {"key": "performed-by", "type": "clause", "offset": [405, 417]}, {"key": "a-list", "type": "definition", "offset": [571, 577]}, {"key": "the-customer-data", "type": "definition", "offset": [581, 598]}, {"key": "to-provide", "type": "definition", "offset": [645, 655]}, {"key": "in-order-to", "type": "clause", "offset": [656, 667]}, {"key": "certain-services", "type": "clause", "offset": [816, 832]}, {"key": "data-formats", "type": "clause", "offset": [878, 890]}, {"key": "acceptable-values", "type": "clause", "offset": [896, 913]}, {"key": "meaning-of", "type": "definition", "offset": [939, 949]}, {"key": "per-year", "type": "definition", "offset": [1120, 1128]}, {"key": "control-measures", "type": "definition", "offset": [1720, 1736]}, {"key": "calling-card", "type": "definition", "offset": [1744, 1756]}, {"key": "fraud-detection", "type": "clause", "offset": [1920, 1935]}, {"key": "electronic-mail", "type": "clause", "offset": [1991, 2006]}, {"key": "one-hour", "type": "definition", "offset": [2014, 2022]}, {"key": "data-base", "type": "clause", "offset": [2328, 2337]}, {"key": "administration-system", "type": "definition", "offset": [2338, 2359]}, {"key": "a-designated", "type": "clause", "offset": [2422, 2434]}, {"key": "contact-person", "type": "clause", "offset": [2457, 2471]}, {"key": "the-records", "type": "clause", "offset": [2497, 2508]}, {"key": "record-of", "type": "clause", "offset": [2578, 2587]}, {"key": "day-of", "type": "clause", "offset": [2648, 2654]}, {"key": "same-business", "type": "definition", "offset": [2763, 2776]}, {"key": "central-time", "type": "definition", "offset": [2836, 2848]}, {"key": "to-negotiate", "type": "definition", "offset": [2934, 2946]}, {"key": "time-frame", "type": "clause", "offset": [2949, 2959]}, {"key": "not-to-exceed", "type": "definition", "offset": [2977, 2990]}, {"key": "business-days", "type": "clause", "offset": [3001, 3014]}, {"key": "recovery-of", "type": "clause", "offset": [3060, 3071]}, {"key": "date-of", "type": "clause", "offset": [3169, 3176]}, {"key": "most-recent", "type": "definition", "offset": [3181, 3192]}, {"key": "backup-copy", "type": "clause", "offset": [3193, 3204]}, {"key": "weekly-basis", "type": "clause", "offset": [3381, 3393]}, {"key": "software-release", "type": "definition", "offset": [3410, 3426]}, {"key": "prior-to", "type": "definition", "offset": [3463, 3471]}, {"key": "new-release", "type": "definition", "offset": [3484, 3495]}, {"key": "reports-of", "type": "clause", "offset": [3562, 3572]}, {"key": "time-period", "type": "definition", "offset": [3668, 3679]}, {"key": "access-to", "type": "clause", "offset": [3776, 3785]}, {"key": "other-party", "type": "definition", "offset": [3940, 3951]}, {"key": "authorized-by", "type": "clause", "offset": [3964, 3977]}, {"key": "in-writing", "type": "definition", "offset": [4000, 4010]}, {"key": "data-screening", "type": "definition", "offset": [4091, 4105]}, {"key": "owned-by", "type": "definition", "offset": [4215, 4223]}, {"key": "specific-data", "type": "clause", "offset": [4224, 4237]}, {"key": "for-customer", "type": "clause", "offset": [4246, 4258]}, {"key": "obtain-from", "type": "clause", "offset": [4420, 4431]}, {"key": "associated-with", "type": "definition", "offset": [4480, 4495]}, {"key": "in-accordance-with", "type": "definition", "offset": [4546, 4564]}, {"key": "industry-standards", "type": "definition", "offset": [4942, 4960]}, {"key": "processing-time", "type": "definition", "offset": [5000, 5015]}, {"key": "normal-conditions", "type": "definition", "offset": [5054, 5071]}, {"key": "nine-percent", "type": "definition", "offset": [5194, 5206]}], "samples": [{"hash": "luB9G9A9DjR", "uri": "/contracts/luB9G9A9DjR#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "iBYLr7z06Rd", "uri": "/contracts/iBYLr7z06Rd#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}], "hash": "c391d04d8b5144cacf037b3aaec6fab1", "id": 2}, {"snippet": "Signaling Link Transport shall consist of full duplex mode 56 kbps transmission paths and shall perform in the following two ways:", "size": 130, "snippet_links": [{"key": "signaling-link-transport", "type": "clause", "offset": [0, 24]}, {"key": "consist-of", "type": "clause", "offset": [31, 41]}], "samples": [{"hash": "lsqjwpwPGhM", "uri": "/contracts/lsqjwpwPGhM#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "lWGJogFk2CW", "uri": "/contracts/lWGJogFk2CW#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "l5W7CSmnXsk", "uri": "/contracts/l5W7CSmnXsk#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}], "hash": "8ee1e79efa523d39f8e04db07b1af91c", "id": 3}, {"snippet": "5.6.1 BellSouth shall offer DS0 equivalent interface transmission rates for DS0 or voice grade Dedicated Transport. For DS1 or DS3 circuits, Dedicated Transport shall at a minimum meet the performance, availability, jitter, and delay requirements specified for Customer Interface to Central Office (CI to CO) connections in the applicable industry standards.\n5.6.2 BellSouth shall offer the following interface transmission rates for Dedicated Transport:\n5.6.2.1 DS0 Equivalent;\n5.6.2.2 DS1;\n5.6.2.3 DS3;\n5.6.2.4 STS-1; and\n5.6.2.5 SDH (Synchronous Digital Hierarchy) Standard interface rates are in accordance with International Telecommunications Union (ITU) Recommendation G.707 and Plesiochronous Digital Hierarchy (PDH) rates per ITU Recommendation G.704.\n5.6.3 BellSouth shall design Dedicated Transport according to its network infrastructure. NewPhone shall specify the termination points for Dedicated Transport.\n5.6.4 At a minimum, Dedicated Transport shall meet each of the requirements set forth in the applicable industry technical references and BellSouth Technical References;\n5.6.4.1 Telcordia TR-TSY-000191 Alarm Indication Signals Requirements and Objectives, Issue 1, May 1986.\n5.6.4.2 BellSouth\u2019s TR73501 LightGate\uf8e8Service Interface and Performance Specifications, Issue D, June 1995.\n5.6.4.3 BellSouth\u2019s TR73525 MegaLink\uf8e8Service, MegaLink Channel Service and MegaLink Plus Service Interface and Performance Specifications, Issue C, May 1996.", "size": 92, "snippet_links": [{"key": "transmission-rates", "type": "definition", "offset": [53, 71]}, {"key": "voice-grade", "type": "definition", "offset": [83, 94]}, {"key": "dedicated-transport", "type": "clause", "offset": [95, 114]}, {"key": "the-performance", "type": "clause", "offset": [185, 200]}, {"key": "customer-interface", "type": "clause", "offset": [261, 279]}, {"key": "central-office", "type": "clause", "offset": [283, 297]}, {"key": "the-applicable", "type": "clause", "offset": [324, 338]}, {"key": "industry-standards", "type": "definition", "offset": [339, 357]}, {"key": "standard-interface", "type": "definition", "offset": [568, 586]}, {"key": "in-accordance-with", "type": "definition", "offset": [597, 615]}, {"key": "international-telecommunications-union", "type": "definition", "offset": [616, 654]}, {"key": "according-to", "type": "definition", "offset": [810, 822]}, {"key": "network-infrastructure", "type": "definition", "offset": [827, 849]}, {"key": "termination-points", "type": "clause", "offset": [878, 896]}, {"key": "the-requirements", "type": "clause", "offset": [981, 997]}, {"key": "bellsouth-technical-references", "type": "clause", "offset": [1060, 1090]}, {"key": "issue-1", "type": "clause", "offset": [1178, 1185]}, {"key": "service-interface", "type": "definition", "offset": [1235, 1252]}, {"key": "performance-specifications", "type": "definition", "offset": [1257, 1283]}], "samples": [{"hash": "khpsaK6mZoS", "uri": "/contracts/khpsaK6mZoS#technical-requirements", "label": "MFN Agreement", "score": 19.7281398773, "published": true}, {"hash": "21RkbYxS8Cm", "uri": "/contracts/21RkbYxS8Cm#technical-requirements", "label": "MFN Agreement", "score": 19.6365509033, "published": true}, {"hash": "7krmqjjoooC", "uri": "/contracts/7krmqjjoooC#technical-requirements", "label": "MFN Agreement", "score": 19.5037651062, "published": true}], "hash": "54e27916aaef77ecb33e80ba17e26b05", "id": 4}, {"snippet": "6.2.1 BellSouth\u2019s 911 database vendor shall provide NewPhone the capability of providing updates to the ALI/DMS database through a specified electronic interface. NewPhone shall contact BellSouth\u2019s 911 database vendor directly to request interface. NewPhone shall provide updates directly to BellSouth\u2019s 911 database vendor on a daily basis. Updates shall be the responsibility of NewPhone and BellSouth shall not be liable for the transactions between NewPhone and BellSouth\u2019s 911 database vendor.\n6.2.2 It is NewPhone\u2019s responsibility to retrieve and confirm statistical data and to correct errors obtained from BellSouth\u2019s 911 database vendor on a daily basis. All errors will be assigned a unique error code and the description of the error and the corrective action is described in the CLEC Users Guide for Facility Based Providers that is found on the BellSouth Interconnection Web site.\n6.2.3 NewPhone shall conform to the BellSouth standards as described in the CLEC Users Guide to E911 for Facilities Based Providers that is located on the BellSouth Interconnection Web site at \u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/\u2587\u2587\u2587\u2587\u2587\u2587.\n6.2.4 Stranded Unlocks are defined as end user records in BellSouth\u2019s ALI/DMS database that have not been migrated for over ninety (90) days to NewPhone, as a new provider of local service to the end user. Stranded Unlocks are those end user records that have been \u201cunlocked\u201d by the previous local exchange carrier that provided service to the end user and are open for NewPhone to assume responsibility for such records.\n6.2.5 Based upon end user record ownership information available in the NPAC database, BellSouth shall provide a Stranded Unlock annual report to NewPhone that reflects all Stranded Unlocks that remain in the ALI/DMS database for over ninety (90) days. NewPhone shall review the Stranded Unlock report, identify its end user records and request to either delete such records or migrate the records to NewPhone within two (2) months following the date of the Stranded Unlock report provided by BellSouth. NewPhone shall reimburse BellSouth for any charges BellSouth\u2019s database vendor imposes on BellSouth for the deletion of NewPhone\u2019s records.", "size": 92, "snippet_links": [{"key": "vendor-shall-provide", "type": "clause", "offset": [31, 51]}, {"key": "electronic-interface", "type": "definition", "offset": [141, 161]}, {"key": "to-request", "type": "clause", "offset": [227, 237]}, {"key": "daily-basis", "type": "clause", "offset": [329, 340]}, {"key": "responsibility-of", "type": "clause", "offset": [363, 380]}, {"key": "the-transactions", "type": "clause", "offset": [428, 444]}, {"key": "statistical-data", "type": "clause", "offset": [561, 577]}, {"key": "error-code", "type": "definition", "offset": [701, 711]}, {"key": "description-of-the", "type": "clause", "offset": [720, 738]}, {"key": "corrective-action", "type": "definition", "offset": [753, 770]}, {"key": "web-site", "type": "definition", "offset": [884, 892]}, {"key": "end-user-records", "type": "definition", "offset": [1167, 1183]}, {"key": "new-provider", "type": "definition", "offset": [1288, 1300]}, {"key": "local-service", "type": "definition", "offset": [1304, 1317]}, {"key": "the-end-user", "type": "clause", "offset": [1321, 1333]}, {"key": "local-exchange-carrier", "type": "definition", "offset": [1421, 1443]}, {"key": "responsibility-for", "type": "clause", "offset": [1518, 1536]}, {"key": "information-available", "type": "clause", "offset": [1594, 1615]}, {"key": "provide-a", "type": "definition", "offset": [1654, 1663]}, {"key": "report-to", "type": "clause", "offset": [1687, 1696]}, {"key": "the-records", "type": "clause", "offset": [1937, 1948]}, {"key": "following-the", "type": "definition", "offset": [1983, 1996]}, {"key": "date-of", "type": "clause", "offset": [1997, 2004]}, {"key": "deletion-of", "type": "clause", "offset": [2163, 2174]}], "samples": [{"hash": "khpsaK6mZoS", "uri": "/contracts/khpsaK6mZoS#technical-requirements", "label": "MFN Agreement", "score": 19.7281398773, "published": true}, {"hash": "21RkbYxS8Cm", "uri": "/contracts/21RkbYxS8Cm#technical-requirements", "label": "MFN Agreement", "score": 19.6365509033, "published": true}, {"hash": "7krmqjjoooC", "uri": "/contracts/7krmqjjoooC#technical-requirements", "label": "MFN Agreement", "score": 19.5037651062, "published": true}], "hash": "92182f4b543b126b6fcfae91201776a5", "id": 5}, {"snippet": "STPs provide interconnection to the functions of signaling networks or to third party SS7 networks connected to the Embarq SS7 network. These functions include:\n57.6.1. Embarq local switching or Tandem Switching;\n57.6.2. Embarq Service Control Points (SCPs)/Databases if arranged for under separate agreements;\n57.6.3. Third-party local or Tandem Switching systems subject to any additional conditions or terms of the Third Party and\n57.6.4. Third party provider STPs subject to any additional conditions or terms of the Third Party.", "size": 83, "snippet_links": [{"key": "interconnection-to", "type": "clause", "offset": [13, 31]}, {"key": "functions-of", "type": "clause", "offset": [36, 48]}, {"key": "signaling-networks", "type": "clause", "offset": [49, 67]}, {"key": "local-switching", "type": "definition", "offset": [176, 191]}, {"key": "tandem-switching", "type": "clause", "offset": [195, 211]}, {"key": "control-points", "type": "clause", "offset": [236, 250]}, {"key": "separate-agreements", "type": "definition", "offset": [290, 309]}, {"key": "subject-to", "type": "definition", "offset": [365, 375]}, {"key": "additional-conditions", "type": "clause", "offset": [380, 401]}, {"key": "the-third-party", "type": "definition", "offset": [414, 429]}, {"key": "third-party-provider", "type": "clause", "offset": [442, 462]}], "samples": [{"hash": "cv6y965xYYv", "uri": "/contracts/cv6y965xYYv#technical-requirements", "label": "Interconnection, Collocation and Resale Agreement", "score": 33.9805984497, "published": true}, {"hash": "7TKHIaISAqi", "uri": "/contracts/7TKHIaISAqi#technical-requirements", "label": "Interconnection, Collocation and Resale Agreement", "score": 32.721408844, "published": true}, {"hash": "zzy9cR7OGY", "uri": "/contracts/zzy9cR7OGY#technical-requirements", "label": "Interconnection, Collocation and Resale Agreement", "score": 32.2861671448, "published": true}], "hash": "7c2be0fa7258c2a6f5e194c269474729", "id": 6}, {"snippet": "4.1.4.1 The requirements set forth in this Section apply to Local Switching, but not to the Data Switching function of Local Switching.\n4.1.4.2 Local Switching shall be equal to or better than the requirements for Local Switching set forth in the applicable industry standard technical references.\n4.1.4.3 When applicable, BellSouth shall route calls to the appropriate trunk or lines for call origination or termination.\n4.1.4.4 Subject to this section, BellSouth shall route calls on a per line or per screening class basis to (1) BellSouth platforms providing Network Elements or additional requirements (2) Operator Services platforms, (3) Directory Assistance platforms, and (4) Repair Centers. Any other routing requests by <<customer_name>> will be made pursuant to the BFR/NBR Process as set forth in General Terms and Conditions.\n4.1.4.5 BellSouth shall provide unbranded recorded announcements and call progress tones to alert callers of call progress and disposition.\n4.1.4.6 BellSouth shall activate service for <<customer_name>> customer or network interconnection on any of the Local Switching interfaces. This includes provisioning changes to change a customer from BellSouth\u2019s services to <<customer_name>>\u2019s services without loss of switch feature functionality as defined in this Agreement.\n4.1.4.7 BellSouth shall perform routine testing (e.g., Mechanized Loop Tests (MLT) and test calls such as 105, 107 and 108 type calls) and fault isolation on a mutually agreed upon schedule.\n4.1.4.8 BellSouth shall repair and restore any equipment or any other maintainable component that may adversely impact Local Switching.\n4.1.4.9 BellSouth shall control congestion points such as those caused by radio station call-ins, and network routing abnormalities. All traffic shall be restricted in a non-discriminatory manner.\n4.1.4.10 BellSouth shall perform manual call trace and permit customer originated call trace.\n4.1.4.11 Special Services provided by BellSouth will include the following:", "size": 83, "snippet_links": [{"key": "the-requirements", "type": "clause", "offset": [8, 24]}, {"key": "data-switching", "type": "clause", "offset": [92, 106]}, {"key": "equal-to", "type": "definition", "offset": [169, 177]}, {"key": "requirements-for", "type": "clause", "offset": [197, 213]}, {"key": "the-applicable", "type": "clause", "offset": [243, 257]}, {"key": "industry-standard", "type": "clause", "offset": [258, 275]}, {"key": "technical-references", "type": "clause", "offset": [276, 296]}, {"key": "when-applicable", "type": "clause", "offset": [306, 321]}, {"key": "call-origination", "type": "clause", "offset": [389, 405]}, {"key": "subject-to", "type": "definition", "offset": [430, 440]}, {"key": "network-elements", "type": "clause", "offset": [563, 579]}, {"key": "additional-requirements", "type": "clause", "offset": [583, 606]}, {"key": "operator-services", "type": "definition", "offset": [611, 628]}, {"key": "directory-assistance", "type": "definition", "offset": [644, 664]}, {"key": "pursuant-to-the", "type": "definition", "offset": [761, 776]}, {"key": "general-terms-and-conditions", "type": "clause", "offset": [809, 837]}, {"key": "network-interconnection", "type": "definition", "offset": [1054, 1077]}, {"key": "local-switching-interfaces", "type": "clause", "offset": [1092, 1118]}, {"key": "changes-to", "type": "clause", "offset": [1147, 1157]}, {"key": "loss-of", "type": "clause", "offset": [1242, 1249]}, {"key": "in-this-agreement", "type": "clause", "offset": [1290, 1307]}, {"key": "routine-testing", "type": "definition", "offset": [1341, 1356]}, {"key": "mutually-agreed", "type": "definition", "offset": [1469, 1484]}, {"key": "caused-by", "type": "clause", "offset": [1700, 1709]}, {"key": "station-call", "type": "clause", "offset": [1716, 1728]}, {"key": "a-non", "type": "clause", "offset": [1804, 1809]}, {"key": "call-trace", "type": "clause", "offset": [1873, 1883]}, {"key": "services-provided-by", "type": "clause", "offset": [1944, 1964]}], "samples": [{"hash": "gG7A5OPcNww", "uri": "/contracts/gG7A5OPcNww#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "dODIqzHcJLd", "uri": "/contracts/dODIqzHcJLd#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "bPTkv679U0S", "uri": "/contracts/bPTkv679U0S#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}], "hash": "635328a1eac6df4ad11caff570e1ca30", "id": 7}, {"snippet": "Tandem Switching shall have the same capabilities or equivalent capabilities as those described in \u2587\u2587\u2587\u2587 Communications Research TR-TSY-000540 Issue 2R2, Tandem Supplement, 6/1/90. The requirements for Tandem Switching include, but are not limited to the following:\n4.2.2.1 Tandem Switching shall provide signaling to establish a tandem connection;\n4.2.2.2 Tandem Switching will provide screening as jointly agreed to by <<customer_name>> and BellSouth;\n4.2.2.3 Tandem Switching shall provide Advanced Intelligent Network triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability;\n4.2.2.4 Tandem Switching shall provide access to Toll Free number portability database as designated by <<customer_name>>;\n4.2.2.5 Tandem Switching shall provide all trunk interconnections discussed under the \u201cNetwork Interconnection\u201d section (e.g., SS7, MF, DTMF, DialPulse, PRI-ISDN, DID, and CAMA-ANI (if appropriate for 911));\n4.2.2.6 Tandem Switching shall provide connectivity to PSAPs where 911 solutions are deployed and the tandem is used for 911; and\n4.2.2.7 Where appropriate, Tandem Switching shall provide connectivity to transit traffic to and from other carriers.", "size": 74, "snippet_links": [{"key": "tandem-switching", "type": "clause", "offset": [0, 16]}, {"key": "or-equivalent", "type": "definition", "offset": [50, 63]}, {"key": "in-\u2587", "type": "clause", "offset": [96, 100]}, {"key": "requirements-for", "type": "clause", "offset": [184, 200]}, {"key": "not-limited", "type": "clause", "offset": [235, 246]}, {"key": "to-establish", "type": "clause", "offset": [314, 326]}, {"key": "will-provide", "type": "clause", "offset": [373, 385]}, {"key": "agreed-to-by", "type": "definition", "offset": [407, 419]}, {"key": "advanced-intelligent-network", "type": "clause", "offset": [492, 520]}, {"key": "not-available", "type": "clause", "offset": [576, 589]}, {"key": "end-office-switch", "type": "clause", "offset": [611, 628]}, {"key": "to-the-extent", "type": "clause", "offset": [630, 643]}, {"key": "access-to", "type": "clause", "offset": [723, 732]}, {"key": "number-portability", "type": "definition", "offset": [743, 761]}, {"key": "as-designated", "type": "definition", "offset": [771, 784]}, {"key": "network-interconnection", "type": "definition", "offset": [894, 917]}, {"key": "where-appropriate", "type": "clause", "offset": [1153, 1170]}, {"key": "transit-traffic", "type": "definition", "offset": [1219, 1234]}, {"key": "other-carriers", "type": "definition", "offset": [1247, 1261]}], "samples": [{"hash": "gG7A5OPcNww", "uri": "/contracts/gG7A5OPcNww#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "dODIqzHcJLd", "uri": "/contracts/dODIqzHcJLd#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "bPTkv679U0S", "uri": "/contracts/bPTkv679U0S#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}], "hash": "bf641ae8773a62d216695e5061bf5466", "id": 8}, {"snippet": "2.1.22.1 To the extent available within BellSouth\u2019s Network at a particular location, BellSouth will offer loops capable of supporting telecommunications services such as: POTS, Centrex, basic rate ISDN, analog PBX, voice grade private line, ADSL, HDSL, DS1 and digital data (up to 64 kb/s). If a requested loop type is not available, then the CLEC can use the Special Construction process to request that BellSouth place facilities or otherwise modify facilities in order to meet IDS\u2019 request.\n2.1.22.2 IDS will be responsible for providing BellSouth with a Service Profile Identifier (SPID) associated with a particular ISDN-capable loop and end user. With the SPID, BellSouth will be able to adequately test the circuit and ensure that it properly supports ISDN service.\n2.1.22.3 The loop will support the transmission, signaling, performance and interface requirements of the services described in 2.", "size": 64, "snippet_links": [{"key": "to-the-extent", "type": "clause", "offset": [9, 22]}, {"key": "capable-of", "type": "definition", "offset": [113, 123]}, {"key": "telecommunications-services", "type": "definition", "offset": [135, 162]}, {"key": "basic-rate-isdn", "type": "definition", "offset": [187, 202]}, {"key": "voice-grade", "type": "definition", "offset": [216, 227]}, {"key": "private-line", "type": "clause", "offset": [228, 240]}, {"key": "digital-data", "type": "definition", "offset": [262, 274]}, {"key": "not-available", "type": "clause", "offset": [320, 333]}, {"key": "construction-process", "type": "clause", "offset": [369, 389]}, {"key": "to-request", "type": "clause", "offset": [390, 400]}, {"key": "in-order-to", "type": "clause", "offset": [464, 475]}, {"key": "responsible-for", "type": "clause", "offset": [516, 531]}, {"key": "service-profile", "type": "clause", "offset": [559, 574]}, {"key": "associated-with", "type": "definition", "offset": [593, 608]}, {"key": "capable-loop", "type": "definition", "offset": [627, 639]}, {"key": "end-user", "type": "definition", "offset": [644, 652]}, {"key": "isdn-service", "type": "definition", "offset": [760, 772]}, {"key": "the-transmission", "type": "clause", "offset": [805, 821]}, {"key": "the-services", "type": "definition", "offset": [876, 888]}], "samples": [{"hash": "hraH7HTmsLF", "uri": "/contracts/hraH7HTmsLF#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}, {"hash": "hph9Z4GSUf6", "uri": "/contracts/hph9Z4GSUf6#technical-requirements", "label": "Clec Agreement", "score": 21.0, "published": true}, {"hash": "fNiOfIkJJ7t", "uri": "/contracts/fNiOfIkJJ7t#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}], "hash": "c01b2b300d52ff4dc749dc6b48b420a8", "id": 9}, {"snippet": "10.3.2.1 STPs shall provide access to BellSouth Local Switching or Tandem Switching and to BellSouth Service Control Points/Databases connected to \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587 network. STPs also provide access to third-party local or tandem switching and third-party-provided STPs.\n10.3.2.2 The connectivity provided by STPs shall fully support the functions of all other Network Elements connected to the \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587 network. This includes the use of the \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587 network to convey messages that neither originate nor terminate at a signaling end point directly connected to the \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587 network (i.e., transit messages). When the \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587 network is used to convey transit messages, there shall be no alteration of the Integrated Services Digital Network User Part or Transaction Capabilities Application Part (TCAP) user data that constitutes the content of the message.\n10.3.2.3 If a BellSouth tandem switch routes traffic, based on dialed or translated digits, on SS7 trunks between a BSE local switch and third party local switch, the \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587 network shall convey the TCAP messages that are necessary to provide Call Management features (Automatic Callback, Automatic Recall, and Screening List Editing) between BSE local STPs and the STPs that provide connectivity with the third party local switch, even if the third party local switch is not directly connected to BellSouth STPs.\n10.3.2.4 STPs shall provide all functions of the SCCP necessary for Class 0 (basic connectionless) service as defined in Telcordia ANSI Interconnection Requirements. This includes GTT and SCCP Management procedures, as specified in ANSI T1.112.", "size": 61, "snippet_links": [{"key": "access-to", "type": "clause", "offset": [28, 37]}, {"key": "local-switching", "type": "definition", "offset": [48, 63]}, {"key": "tandem-switching", "type": "clause", "offset": [67, 83]}, {"key": "control-points", "type": "clause", "offset": [109, 123]}, {"key": "the-functions", "type": "definition", "offset": [330, 343]}, {"key": "network-elements", "type": "clause", "offset": [357, 373]}, {"key": "the-\u2587", "type": "clause", "offset": [387, 392]}, {"key": "signaling-end-point", "type": "definition", "offset": [526, 545]}, {"key": "no-alteration", "type": "clause", "offset": [702, 715]}, {"key": "network-user", "type": "definition", "offset": [751, 763]}, {"key": "user-data", "type": "definition", "offset": [821, 830]}, {"key": "content-of-the", "type": "clause", "offset": [852, 866]}, {"key": "based-on", "type": "definition", "offset": [930, 938]}, {"key": "to-provide", "type": "definition", "offset": [1115, 1125]}, {"key": "call-management", "type": "clause", "offset": [1126, 1141]}, {"key": "the-third-party", "type": "definition", "offset": [1285, 1300]}, {"key": "functions-of-the", "type": "clause", "offset": [1429, 1445]}, {"key": "class-0", "type": "definition", "offset": [1465, 1472]}, {"key": "interconnection-requirements", "type": "definition", "offset": [1533, 1561]}, {"key": "management-procedures", "type": "definition", "offset": [1590, 1611]}, {"key": "as-specified", "type": "clause", "offset": [1613, 1625]}], "samples": [{"hash": "4vTQ8AWvUWx", "uri": "/contracts/4vTQ8AWvUWx#technical-requirements", "label": "Interconnection Agreement", "score": 21.0, "published": true}], "hash": "8252be0f274b9184d3f71cb85751b0bb", "id": 10}], "next_curs": "Cl8SWWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjsLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ih90ZWNobmljYWwtcmVxdWlyZW1lbnRzIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"children": [["", ""], ["telephone-service-prioritization", "Telephone Service Prioritization;"], ["bellsouth-technical-references", "BellSouth Technical References"], ["requirements", "Requirements"], ["interface-requirements", "Interface Requirements"]], "parents": [["network-interface-device", "Network Interface Device"], ["tandem-switching", "Tandem Switching"], ["entire-agreement", "Entire Agreement"], ["unbundled-channelization-multiplexing", "Unbundled Channelization (Multiplexing)"], ["rates", "Rates"]], "title": "Technical Requirements", "size": 2490, "id": "technical-requirements", "related": [["functional-requirements", "Functional Requirements", "Functional Requirements"], ["operational-requirements", "Operational Requirements", "Operational Requirements"], ["general-requirements", "General Requirements", "General Requirements"], ["closet-i-urinal-requirements", "Closet I Urinal Requirements", "Closet I Urinal Requirements"], ["software-requirements", "Software Requirements", "Software Requirements"]], "related_snippets": [], "updated": "2026-05-03T06:08:52+00:00", "also_ask": ["What are the essential technical standards that must be explicitly defined to avoid ambiguity?", "How can we structure this clause to allocate risk for non-compliance or technological change?", "What negotiation leverage exists around performance benchmarks and testing protocols?", "How do courts typically interpret vague or evolving technical requirements in disputes?", "Are there industry-specific legal precedents or regulations that should inform our drafting?"], "drafting_tip": "Specify performance standards and metrics to ensure measurable compliance; define technical terms to avoid ambiguity; require documentation of requirements to facilitate verification.", "explanation": "The Technical Requirements clause defines the specific technical standards, specifications, and criteria that products, services, or deliverables must meet under the agreement. It typically outlines measurable benchmarks such as performance metrics, compatibility standards, or compliance with industry regulations, and may reference detailed documentation or standards bodies. By clearly establishing these requirements, the clause ensures that both parties have a mutual understanding of the expected technical quality and functionality, reducing the risk of disputes over whether contractual obligations have been met."}, "json": true, "cursor": ""}}