Technical Requirements. 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following:
4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection;
4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth;
4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN 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;
4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database;
4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and
4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers.
4.5.3.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 <<customer_short_name>>.
4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner.
4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch.
4.5.3.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.
Technical Requirements. Signaling Link Transport shall consist of full duplex mode 56 kbps transmission paths and shall perform in the following two ways:
Technical Requirements. 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.
5.6.2 BellSouth shall offer the following interface transmission rates for Dedicated Transport:
5.6.2.1 DS0 Equivalent;
5.6.2.2 DS1;
5.6.2.3 DS3;
5.6.2.4 STS-1; and
5.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.
5.6.3 BellSouth shall design Dedicated Transport according to its network infrastructure. NewPhone shall specify the termination points for Dedicated Transport.
5.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;
5.6.4.1 Telcordia TR-TSY-000191 Alarm Indication Signals Requirements and Objectives, Issue 1, May 1986.
5.6.4.2 BellSouth’s TR73501 LightGateService Interface and Performance Specifications, Issue D, June 1995.
5.6.4.3 BellSouth’s TR73525 MegaLinkService, MegaLink Channel Service and MegaLink Plus Service Interface and Performance Specifications, Issue C, May 1996.
Technical Requirements. 6.2.1 BellSouth’s 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’s 911 database vendor directly to request interface. NewPhone shall provide updates directly to BellSouth’s 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’s 911 database vendor.
6.2.2 It is NewPhone’s responsibility to retrieve and confirm statistical data and to correct errors obtained from BellSouth’s 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.
6.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 xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/xxxxxx.
6.2.4 Stranded Unlocks are defined as end user records in BellSouth’s 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 “unlocked” by the previous local exchange carrier that provided service to the end user and are open for NewPhone to assume responsibility for such records.
6.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’s database vendor imposes on BellSouth for the deletion of NewPhone’s records.
Technical Requirements. 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.
4.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.
4.1.4.3 When applicable, BellSouth shall route calls to the appropriate trunk or lines for call origination or termination.
4.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.
4.1.4.5 BellSouth shall provide unbranded recorded announcements and call progress tones to alert callers of call progress and disposition.
4.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’s services to <<customer_name>>’s services without loss of switch feature functionality as defined in this Agreement.
4.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.
4.1.4.8 BellSouth shall repair and restore any equipment or any other maintainable component that may adversely impact Local Switching.
4.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.
4.1.4.10 BellSouth shall perform manual call trace and permit customer originated call trace.
4.1.4.11 Special Services provided by BellSouth will include the following:
Technical Requirements. STPs provide interconnection to the functions of signaling networks or to third party SS7 networks connected to the Embarq SS7 network. These functions include:
57.6.1. Embarq local switching or Tandem Switching;
57.6.2. Embarq Service Control Points (SCPs)/Databases if arranged for under separate agreements;
57.6.3. Third-party local or Tandem Switching systems subject to any additional conditions or terms of the Third Party and
57.6.4. Third party provider STPs subject to any additional conditions or terms of the Third Party.
Technical Requirements. 9.3.2.1 Signaling Transfer Point s shall provide access to BellSouth Local Switching or Tandem Switching and to BellSouth Service Control Points/Databases connected to XxxxXxxxx XX0 network. Signaling Transfer Point also provide access to third- party local or tandem switching and Third-party-provided Signaling Transfer Points.
9.3.2.2 The connectivity provided by Signaling Transfer Points shall fully support the functions of all other Network Elements connected to the XxxxXxxxx XX0 network. This includes the use of the XxxxXxxxx XX0 network to convey messages that neither originate nor terminate at a signaling end point directly connected to the XxxxXxxxx XX0 network (i.e., transit messages). When the XxxxXxxxx XX0 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.
9.3.2.3 If a BellSouth tandem switch routes traffic, based on dialed or translated digits, on SS7 trunks between a Global Connection local switch and third party local switch, the XxxxXxxxx XX0 network shall convey the TCAP messages that are necessary to provide Call Management features (Automatic Callback, Automatic Recall, and Screening List Editing) between Global Connection 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.
9.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 Global Title Translation (GTT) and SCCP Management procedures, as specified in ANSI T1.112.
Technical Requirements. Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Xxxx 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:
4.2.2.1 Tandem Switching shall provide signaling to establish a tandem connection;
4.2.2.2 Tandem Switching will provide screening as jointly agreed to by <<customer_name>> and BellSouth;
4.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;
4.2.2.4 Tandem Switching shall provide access to Toll Free number portability database as designated by <<customer_name>>;
4.2.2.5 Tandem Switching shall provide all trunk interconnections discussed under the “Network Interconnection” section (e.g., SS7, MF, DTMF, DialPulse, PRI-ISDN, DID, and CAMA-ANI (if appropriate for 911));
4.2.2.6 Tandem Switching shall provide connectivity to PSAPs where 911 solutions are deployed and the tandem is used for 911; and
4.2.2.7 Where appropriate, Tandem Switching shall provide connectivity to transit traffic to and from other carriers.
Technical Requirements. 2.1.22.1 To the extent available within BellSouth’s 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 Mpower’s request.
2.1.22.2 Mpower 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.
2.1.22.3 The loop will support the transmission, signaling, performance and interface requirements of the services described in 2.
Technical Requirements. 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.
2.7.4.2 If an existing NID is accessed, it shall be capable of transferring electrical analog or digital signals between the End User’s customer premises and the distribution media and/or cross-connect to AFN’s NID.
2.7.4.3 Existing BellSouth NIDs will be operational and provided in “as is” condition. AFN may request BellSouth to do additional work to the NID on a time and material basis. When AFN deploys its own local loops in a multiple-line termination device, AFN shall specify the quantity of NID connections that it requires within such device.
