Common use of Technical Requirements for Interconnection Clause in Contracts

Technical Requirements for Interconnection. 1. Interconnection with LHTC's end office switch (INHDPAXIDS1) in Indian Head, Pennsylvania will provide Teleport Communications America, LLC with local interconnection for Local Traffic to the LHTC WO (codes served by LHTC’s End Office and any LHTC remotes that subtend the End Office). 2. The Parties will comply with all applicable requirements regarding Toll Dialing Parity and Local Dialing Parity. Nothing in this Agreement shall be construed to alter or otherwise affect in any manner the local calling areas offered or the rates charged by either Party to its End Users. 3. The Parties agree to work cooperatively to establish trunk requirements for the exchange or delivery of traffic between the Parties. 4. The Parties shall utilize the common channel out-of-band signaling (CCS) protocol developed by the Consultative Committee for International Telephone and Telegraph (CCITT) and the American National Standards Institute (ANSI). The Parties agree to exchange traffic using SS7 signaling parameters including, but not limited to ISDN User Part (ISUP), Signaling Points including STPs, SSPs, and SCPs, and any other SS7 parameters necessary for the exchange of traffic. The Parties agree to cooperate on the exchange of all appropriate S S7 messages for call set-up, including Integrated Services Digital Network User Part (ISUP) and Transaction Capability User Part (TCAP) messages, to facilitate full interoperability of all CLASS features and functions between their respective networks. The parties shall also include the Jurisdiction Information Parameter (.11P) in the Initial Address Message (IIAM) containing a Local Exchange Routing Guide-assigned NPA-NXX (6 digits) identifying the originating switch on calls that they originate. The Parties understand that HP may be used to identify the carrier of traffic, but does not in and of itself establish the jurisdiction of such traffic for billing. All CCS signaling parameters, including, but not limited to the originating end user telephone number, will be provided by each Party in conjunction with all traffic it exchanges. 5. Neither Party shall intentionally substitute or generate incorrect ANT, CPN or 5S7 parameters on traffic exchanged pursuant to this Agreement. Upon determination that a Party has intentionally substituted or generated such incorrect parameters on traffic exchanged pursuant to this Agreement, the offending Party shall pay the other Party the difference between compensation paid (if any) and applicable access charges, plus interest due under the terms of the applicable access tariff from the date the traffic would have been billed if such parameters had been passed unaltered. In addition, the Parties acknowledge that a violation of this paragraph would constitute a default of this Agreement.

Technical Requirements for Interconnection. 1. Interconnection with LHTCLTSI's end office switch (INHDPAXIDS1WYMRPAXWDS0) in Indian HeadWaymart, Pennsylvania will provide Teleport Communications America, LLC with local interconnection for Local Traffic to the LHTC LTSI WO (codes served by LHTCLTSI’s End Office and any LHTC LTSI remotes that subtend the End Office). 2. The Parties will comply with all applicable requirements regarding Toll Dialing Parity and Local Dialing Parity. Nothing in this Agreement shall be construed to alter or otherwise affect in any manner the local calling areas offered or the rates charged by either Party to its End Users. 3. The Parties agree to work cooperatively to establish trunk requirements for the exchange or delivery of traffic between the Parties. 4. The Parties shall utilize the common channel out-of-band signaling (CCS) protocol developed by the Consultative Committee for International Telephone and Telegraph (CCITT) and the American National Standards Institute (ANSI). The Parties agree to exchange traffic using SS7 signaling parameters including, but not limited to ISDN User Part (ISUP), Signaling Points including STPs, SSPs, and SCPs, and any other SS7 parameters necessary for the exchange of traffic. The Parties agree to cooperate on the exchange of all appropriate S S7 messages for call set-up, including Integrated Services Digital Network User Part (ISUP) and Transaction Capability User Part (TCAP) messages, to facilitate full interoperability of all CLASS features and functions between their respective networks. The parties shall also include the Jurisdiction Information Parameter (.11P) in the Initial Address Message (IIAM) containing a Local Exchange Routing Guide-assigned NPA-NXX (6 digits) identifying the originating switch on calls that they originate. The Parties understand that HP may be used to identify the carrier of traffic, but does not in and of itself establish the jurisdiction of such traffic for billing. All CCS signaling parameters, including, but not limited to the originating end user telephone number, will be provided by each Party in conjunction with all traffic it exchanges. 5. Neither Party shall intentionally substitute or generate incorrect ANT, CPN or 5S7 parameters on traffic exchanged pursuant to this Agreement. Upon determination that a Party has intentionally substituted or generated such incorrect parameters on traffic exchanged pursuant to this Agreement, the offending Party shall pay the other Party the difference between compensation paid (if any) and applicable access charges, plus interest due under the terms of the applicable access tariff from the date the traffic would have been billed if such parameters had been passed unaltered. In addition, the Parties acknowledge that a violation of this paragraph would constitute a default of this Agreement.