Legacy Network Gateway – Arizona Specific Sample Clauses

Legacy Network Gateway – Arizona Specific. As customer PSAPs migrate to an ESInet solution, there will continue to be the need for these NG9-1-1 enabled PSAPs to receive wireless and wireline calls from legacy TDM networks and from legacy PSAPs. In compliance with the NENA i3 defined solution for interconnecting legacy networks and the Emergency Services Information Network (ESInet), CENTURYLINK will deploy two Legacy Network Gateways (LNG)s in Arizona at the following data centers: At each LNG, CENTURYLINK will install Gateways where calls originating on the legacy network will be converted to IP for transport over the ESInet to the West Emergency Call Management Center and then on to the i3 enabled, or NG PSAP. As a PSAP is migrated to a NG PSAP, CENTURYLINK will replace the existing EM trunks from the Legacy Selective Router (LSR) to the PSAP with SR trunks from the LSR to the LNG Gateways. CENTURYLINK’s recommended design will be a ratio of (1.3) ES trunks for every (1) legacy EM trunk. Additionally, trunks from the LNG to the LSR are needed to support call transfers from NG PSAPs to Legacy PSAPs or vice versa, which may also impact the required ratio. During the migration of PSAPs from the legacy network to the ESInet, CENTURYLINK will monitor the traffic volumes and may adjust the number of ES and LSR transfer trunks up or down, as needed. CENTURYLINK ES trunks are configured in a Primary / Secondary overflow pattern (never load shared). In the solution for Arizona, half the ES trunks from the LSR are honed to one of two LNGs, while the other half is honed to the second LNG. In the event that a LNG is lost, an Arizona NG PSAP will still maintain full service levels similar to how all Arizona PSAPs are currently provisioned with N+1 redundancy through dual tandems. As the PSAP is migrated to a NG PSAP, CENTURYLINK will update the routing in its LSR and based on ESN, deliver the call over the EM trunks to a legacy PSAP or over the SR ES trunks to the LNG and then over the ESInet to a NG PSAP. Call setup times are dramatically improved when processed through the LNG to the IPSR with an average call setup time of 600ms.
AutoNDA by SimpleDocs

Related to Legacy Network Gateway – Arizona Specific

  • Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.

  • NON-NETWORK PROVIDER is a provider that has not entered into a contract with us or any other Blue Cross and Blue Shield plan. For pediatric dental care services, non-network provider is a dentist that has not entered into a contract with us or does not participate in the Dental Coast to Coast Network. For pediatric vision hardware services, a non-network provider is a provider that has not entered into a contract with EyeMed, our vision care service manager.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses 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 Xxxx. 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 Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • System and Data Access Services a. System. Subject to the terms and conditions of this Addendum and solely for the purpose of providing access to Fund Data as set forth herein, State Street hereby agrees to provide the Fund, or certain third parties approved by State Street that serve as the Fund`s investment advisors, investment managers or fund accountants (the "Fund Accountants") or as the Fund`s independent auditors (the "Auditor"), with access to State Street`s Multicurrency HORIZONR Accounting System and the other information systems described in Attachment A (collectively, the "System") on a remote basis solely on the computer hardware, system software and telecommunication links described in Attachment B (the "Designated Configuration") or on any designated substitute or back-up equipment configuration consented to in writing by State Street, such consent not to be unreasonably withheld.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Service Description 2.1 General

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!