Tandem Transit Traffic 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on CBB's network, and is transported through Verizon’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Verizon, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Verizon. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). Switched Exchange Access Service traffic is not Tandem Transit Traffic.
Transit Traffic The following rates will apply:
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):
Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.
DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.
Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.
Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.
One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from CBB to Verizon, CBB, at CBB’s own expense, shall:
Transit Service is the delivery of certain traffic between Carrier and a third party ILEC, CLEC or CMRS provider by Frontier over a separate trunk group between Carrier and Frontier where appropriate trunks exist between Carrier and third party through Frontier’s tandem. The following traffic types will be delivered: (I) Local Traffic originated from Carrier to such third-party and (ii) Local Traffic originated from such third-party to Frontier’s tandem and terminated to Carrier.
Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures for the transferred Personal Data are mutually agreed upon and made part of the relevant agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP-controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center).
