Common use of Interface Requirements Clause in Contracts

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast's IDS’ switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s IDS’ request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s IDS’ traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastMpower's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastMpower’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastMpower’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastNOW's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastNOW’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastNOW’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastBTI's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastBTI’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastBTI’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastDSL Telecom's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastDSL Telecom’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastDSL Telecom’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastChoctaw's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastChoctaw’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastChoctaw’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastAPI's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastAPI’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastAPI’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastCLEC-1's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastCLEC-1’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastCLEC-1’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastArrow's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastArrow’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastArrow’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastGlobal Crossing's switch, using two-two- way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastGlobal Crossing’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastGlobal Crossing’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastE-Z Access's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastE-Z Access’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastE-Z Access’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastNewSouth's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastNewSouth’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastNewSouth’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastLS-One's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastLS-One’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastLS-One’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastWorld Access's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastWorld Access’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastWorld Access’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast's Momentum Business Solutions’ switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s Momentum Business Solutions’ request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s Momentum Business Solutions’ traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast's EPB Telecommunications' switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s EPB Telecommunications' request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s EPB Telecommunications' traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastZNC's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastZNC’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastZNC’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastXspedius's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastXspedius’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastXspedius’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastUSA Digital's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastUSA Digital’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastUSA Digital’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable following technical references.:

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastKnology's switch, using two-way trunks, for traffic that is transiting via BellSouth’s 's network to interLATA or intraLATA carriers. At SouthEast’s Knology's request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s Knology's traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastAlliance's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastAlliance’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastAlliance’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast▇▇▇▇▇'s switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastWakul’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastWakul’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastMRC's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastMRC’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastMRC’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastLINEDRIVE's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastLINEDRIVE’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastLINEDRIVE’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastCCI's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastCCI’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastCCI’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastPilgrim's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastPilgrim’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastPilgrim’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastEPB's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastEPB’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastEPB’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastaXessa's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastaXessa’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastaXessa’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastECI's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastECI’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastECI’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastVELOCITY's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastVELOCITY’s request, Tandem ▇▇▇▇▇▇ Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastVELOCITY’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastAccess One's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastAccess One’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastAccess One’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastLightyear's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastLightyear’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastLightyear’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastLCT's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastLCT’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastLCT’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastCTES's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastCTES’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastCTES’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast1-800 RECONEX, Inc.'s switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast1-800 RECONEX, Inc.’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast1-800 RECONEX, Inc.’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastNAS's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastNAS’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastNAS’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastLightyear's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastLightyear’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastLightyear’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastPreferred's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastPreferred’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastPreferred’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastETS's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastETS’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastETS’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastDV2's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastDV2’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastDV2’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastEdge Connections's switch, using two-two- way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastEdge Connections’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastEdge Connections’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEast's ▇▇▇▇▇▇▇'▇ switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s ▇▇▇▇▇▇▇’▇ request, Tandem ▇▇▇▇▇▇ Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s ▇▇▇▇▇▇▇’▇ traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast▇▇▇▇ Communications's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast▇▇▇▇ Communications’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast▇▇▇▇ Communications’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastNavigator's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastNavigator’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastNavigator’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast's Rhythms’ switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s Rhythms’ request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s Rhythms’ traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastPowerNet's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastPowerNet’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastPowerNet’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastE-Tel's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastE-Tel’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastE-Tel’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEast's New Access’ switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEast’s New Access’ request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEast’s New Access’ traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 Tandem Switching shall interconnect with SouthEastActel's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastActel’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastActel’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastTLX's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastTLX’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastTLX’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.

Interface Requirements. 4.2.13.1 3.3.2.2.1 Tandem Switching shall provide interconnection to the E911 PSAP where the underlying Tandem is acting as the E911 Tandem. 4.2.13.2 3.3.2.2.2 Tandem Switching shall interconnect, with direct trunks, to all carriers with which BellSouth interconnects. 4.2.13.3 3.3.2.2.3 BellSouth shall provide all signaling necessary to provide Tandem Switching with no loss of feature functionality. 4.2.13.4 3.3.2.2.4 Tandem Switching shall interconnect with SouthEastLevel 3's switch, using two-way trunks, for traffic that is transiting via BellSouth’s network to interLATA or intraLATA carriers. At SouthEastLevel 3’s request, Tandem Switching shall record and keep records of traffic for billing. 4.2.13.5 3.3.2.2.5 Tandem Switching shall provide an alternate final routing pattern for SouthEastLevel 3’s traffic overflowing from direct end office high usage trunk groups. 4.2.13.6 3.3.2.2.6 Tandem Switching shall be equal to or better than the requirements for Tandem Switching set forth in the applicable technical references.