ATT_PS_Svcs_US_StofWI_Intrado_ERS_GBS37010 CONTRACT_ID_2741063_Signed.pdf

eSign F a x C o v e r S h e e t

To:

AT&T Automated Fax Handling Service

From:

Fax:

Total Pages:

(Excluding Fax Cover Sheet)

Or with Copiers / Scanners w/ email, Send To:

To sign via fax:

1. Sign, Title and Date the document where applicable,

2. Fax back documents in the following order:

I. eSign Fax Cover Sheet for II. All Pages stamped with

3. If there are additional documents, use the corresponding eSign Fax Cover Sheet(s) as separator(s) and Fax back as in 2.I and 2.II.

(see Picture below)

Sales Contact Information

BENKO; THERESA

262-617-1004 tb9275@att.com

Contract Id: 2741063

877-374-4632 or 877-eSignFax esign@att.com

Contract Id: 2741063 Contract Id: 2741063

Request Id: 2703351 Contract Id: 2741063

DocuSign Envelope ID: AECE7E6A-7D5B-4A5B-B720-4EFE3507B7AD

WISCONSIN DEPARTMENT OF ADMINISTRATION

DIVISION OF ENTERPRISE OPERATIONS

DOA-3051 (R 04/2019)

S. 51.01(5) WIS. STATS.; AND

S. 111.32(13M) WIS. STATS

STATE BUREAU OF PROCUREMENT

101 EAST WILSON STREET, 6TH FLOOR

POST OFFICE BOX 7867

MADISON, WI 53707-7867

FAX (608) 267-0600

TTY (608) 267-9629

HTTP://VENDORNET.STATE.WI.US

Contract Amendment

Contract No.: 505ENT-M11-HICAPATT-01 Amendment No.: 10

Contract Title: IT - High Capacity Voice Trunking (AT&T)

This Amendment is entered into by and between the State of Wisconsin, Department of Administration, and the Contractor, whose name, address and principal officer appears below.

Contractor Name AT&T Corp

Contractor Address 204 S Akard

City: Dallas State: TX Zip: 75202

Principal Officer:

The parties wish to change the terms of the above-referenced Contract in the following manner:

The parties agree to incorporate the AT&T Pricing Schedule for Network Integration Services as set forth within the attached Amendment 10 to 505ENT-M11-HICAPATT-01 (the "Contract").

Except as expressly modified by this Amendment 10, the terms, conditions and respective rights and obligations of the

Parties as set forth in the Contract are hereby ratified, confirmed and approved.

Except as expressly changed by this Amendment, the terms, conditions, rights and obligations of Contract No.:

505ENT-M11-HICAPATT-01 shall remain in effect unchanged. In the event of any inconsistency or conflict in the Contract and this Amendment, the provision of this Amendment shall control.

To Be Completed by Contractor

For State of Wisconsin Department of Administration Cheryl Edgington Director State Bureau of Procurement

For

Company Name

Address

City State Zip

Signature By

Printed Name

Date

Signature

Title

Date

This document can be made available in alternate formats to individuals with disabilities upon request.

Contract Id: 2741063

201203210055UA

rp091v eSigned - Veronica Danao

Contract Specialist, as signatory for AT&T

11 Nov 2022

12/1/2022 | 7:36 PM CST

Pricing Schedule AT&T Network Integration Services

Services U.S.

AT&T and Customer Proprietary Page 1 of 19

Do not disclose or duplicate

Agreement No.: 20120321-0055UA AT&T Network Integration Tracking ID: GBS370101

Document Version#:1 11-7-22

CUSTOMER Legal Name (“Customer”)

AT&T Corp. ("AT&T") (designate other entity if signing entity other than AT&T Corp)

AT&T Branch Sales Contact Name

State of Wisconsin Department of Administration

AT&T Name: Theresa Benko

CUSTOMER Address AT&T Corp. Address and Contact AT&T Branch Sales Contact Information

Street Address: 101 E. Wilson St City: Madison State / Province: WI Country: USA Domestic / Intl / Zip Code: 53703

One AT&T Way Bedminster

NJ

07921-0752 Contact: Master Agreement Support Team Email : mast@att.com

Address: 316 W. Washington Ave City: Madison State / Province:WI Country: USA Domestic / Intl / Zip Code: 53703 Email: theresa.benko@att.com Sales/Branch Mgr: Robert Klein SCVP Name: Joe Drygas

CUSTOMER Contact AT&T Address and Contact AT&T NI Contact Information

Name: Connie Bandt Title: Section Chief – IT Investment Mgmt Telephone: (608) 267-7355 Email:connie.bandt@wisconsin.gov

Name:

Title:

Telephone:

Street Address:

City:

State / Province:

Country:

Domestic / Intl / Zip Code:

Name: Michael Reckley Address: 11760 US Hwy 1 City: North Palm Beach State / Province: FL Country: USA Domestic / Intl / Zip Code: 33408 Telephone: 248-892-2292 Email: mr5231@att.com

CUSTOMER Billing Address

Street Address: 101 E. Wilson St City: Madison State / Province: WI Country: USA Domestic / Intl / Zip Code: 53703

Upon mutual execution hereof, this Pricing Schedule for AT&T Network Integration Services (“NI Pricing Schedule”) becomes part of the Master Agreement between AT&T and Customer referenced above (the “Agreement”). C

Customer has requested that AT&T sign this Agreement first, and AT&T has agreed to do so. This Agreement as signed by AT&T shall be binding upon Customer from the time of Customer’s signature, and AT&T will begin implementing the agreement when a fully signed copy is returned by Customer, provided such fully signed copy is returned to AT&T not more than forty-five (45) days after AT&T delivered a signed copy to Customer. Further, any and all changes made to the Agreement after signature by AT&T shall be void and of no effect, unless and until incorporated into a written amendment to this Agreement signed by both Parties, except for changes expressly authorized by the terms of this Agreement.

AGREED: AGREED:

CUSTOMER: State of Wisconsin Department of Administration

AT&T

By:_________________________________________ (Authorized Agent or Representative)

By:__________________________________________

(Typed or Printed Name)

(Title)

(Date)

ATTUID: mr5231

GBS370101

201203210055UA

20221110-4470 rp091v

PCS ID : 20221111-040

eSigned - Veronica Danao

Contract Specialist, as signatory for AT&T

11 Nov 2022

DocuSign Envelope ID: AECE7E6A-7D5B-4A5B-B720-4EFE3507B7AD

Cheryl Edgington

Director, State Bureau of Procurement

12/1/2022 | 7:36 PM CST

mailto:mast@att.com mailto:connie.bandt@wisconsin.gov

Services U.S.

AT&T and Customer Proprietary Page 2 of 19

Do not disclose or duplicate

1. SERVICES

This NI Pricing Schedule states the terms and conditions governing SOW’s for AT&T services (“Services”). Attached to this NI Pricing Schedule is an SOW detailing the types of Services provided as well as commensurate charges which become effective and incorporated herein upon the Effective Date. AT&T may subcontract work to be performed hereunder but shall retain responsibility for all such work.

2. STATEMENT(s) OF WORK A. Unless earlier terminated as described below, an SOW is deemed terminated when the parties’ respective obligations have been fully performed or when it is otherwise terminated according to its terms.

B. In the event of an inconsistency among terms, the order of priority is: (i) the applicable SOW; (ii) the NI Pricing

Schedule and (iii) the Agreement.

3. INTELLECTUAL PROPERTY RIGHTS

A. All intellectual property and proprietary rights arising by virtue of AT&T’s performance of the Services are and will remain the sole and exclusive property of AT&T, and neither ownership nor title to any such property will pass to Customer.

B. Customer shall retain those copies of any reports produced and furnished to Customer by AT&T (“Reports”), and Customer is hereby granted, under AT&T’s copyrights, the perpetual, non-exclusive, personal and non-transferable right to reproduce and modify Reports for Customer’s own internal business purposes. For avoidance of doubt and to the extent permissible by law, “internal business purposes” exclude public distribution, resale to third parties and revenue generation purposes.

C. AT&T hereby grants to Customer the non-exclusive, personal, and non-transferable right to use any items other than Reports produced and furnished to Customer by AT&T under this NI Pricing Schedule, solely for Customer's own internal business purposes during the term of this NI Pricing Schedule, or for such other purposes as may be mutually agreed in writing by the parties.

D. Except as otherwise specified herein, no other right or license to or under any of AT&T's intellectual property rights is either granted or implied under this NI Pricing Schedule.

4. WARRANTY

The provision of Services hereunder shall be performed in a workmanlike manner that would meet commercial industry standards in the field to which the work pertains as well as any standards set forth in the applicable

SOW

5. TERM AND TERMINATION

This NI Pricing Schedule shall remain in effect until terminated by either party on not less than thirty (30) days’ prior written notice to the other party; provided that, the terms and conditions of this NI Pricing Schedule shall continue to govern, through completion of performance (or earlier termination), all SOWs in effect on this NI Pricing Schedule’s termination date. Termination charges, if any, shall be as specified in the applicable Attachment.

6. MANUFACTURER’S OR THIRD PARTY MAINTENANCE

Maintenance, if any, resold to Customer hereunder may have additional license terms and/or other requirements or restrictions imposed by the manufacturer, AT&T or publisher. Customer is solely responsible for ensuring its adherence to any and all such license terms and other requirements or restrictions and is deemed to accept them upon commencement of the maintenance services.

7. LIMITATION OF LIABILITY

For purposes of this NI Pricing Schedule and SOW’s placed hereunder, any limit or cap on liability contained in the “Limitations of Liability” article 6.1(a) (v) of the Agreement is superseded by the following: EACH PARTY’S LIABILITY UNDER THIS NI PRICING SCHEDULE SHALL BE LIMITED TO PROVEN DIRECT DAMAGES NOT TO EXCEED THE NET PURCHASE PRICE PAID BY CUSTOMER FOR SERVICES UNDER THE SOW THAT GAVE RISE TO THE LIABILITY. This shall not limit Customer’s responsibility for the payment of all charges properly due under the NI Pricing Schedule.

Contract Id: 2741063DocuSign Envelope ID: AECE7E6A-7D5B-4A5B-B720-4EFE3507B7AD

Services U.S.

AT&T and Customer Proprietary Page 3 of 19

Do not disclose or duplicate

EXHIBIT 1: STATEMENT OF WORK

1. Introduction

This SOW between AT&T Corp. (“AT&T”) and State of Wisconsin Department of Administration is attached to the NI Pricing Schedule and made a part thereof upon the Effective Date.

AT&T reserves the right to withdraw this SOW if the engagement does not commence within 120 calendar days of the Effective Date.

1.1 Definitions

“ALI” means Automatic Location Identification.

“APCO” means Association of Public-Safety Communication Officials-International.

“API” means Application Interface.

“ATP” means Acceptance Test Plan.

“AVPN” means AT&T Virtual Private Network utilizing MPLS technology “CAMA” means Centralized Automated Message Accounting.

“Customer PBX Equipment” means Legacy TDM PBX or an IP enabled PBX.

“DID” means Direct Inward Dial “ECRC” means Emergency Call Relay Center with functionality outlined in Section 2.3 of Exhibit 1 attached to this NI

Pricing Schedule.

“ERSDB” or “DB” means Emergency Routing Service Database with functionality outlined in Section 2.3 of Exhibit 1 attached to this NI Pricing Schedule.

“ERS” means Emergency Routing Service, a secure, web-based service that ensures 911 calls are routed to the appropriate Public Safety Answering Point (PSAP) based on the caller's location.

“Endpoint” means a hardware device or software instance that can make and receive voice calls.

“Endpoint Data” means information on the specific location of an Endpoint, including GPS coordinates, municipal address, building name, floor number and/or suite number.

“ERL” means Emergency Response Location.

“FCC” means Federal Communication Commission of the United States of America.

“Interface” means AT&T web-based management interface for administration on the ERS and for the provisioning of Endpoints and Endpoint Data. This Interface is a SOAP/XML application utilizing SSL 256-bit encryption.

“IP” means Internet Protocol.

“IP Flex Reach” means AT&T IP Flex Reach SIP Service provided by AT&T that needs to be independently contracted with AT&T for the ERS to be provisioned and enabled.

“IPSec” means Internet Protocol Security, used to authenticate and encrypt data packets to provide a secure encrypted communication between two devices.

“ISDN” means Integrated Services Digital Network.

“MPLS” means Multi-Protocol Label Switching.

“nALI” means National ALI Database.

“NENA” means National Emergency Number Association “NNI” means Network to Network Interface.

“POTS” means Plain Old Telephone Service.

“PBX” means Private Branch Exchange.

“PIDF-LO” means Presence Information Data Format-Location Object, used to identify the physical dispatchable location of a Microsoft Teams user.

“Project Country” means a country, specified in a Statement of Work (“SOW”), where AT&T performs Services and/or where Customer may enjoy the benefit of those Services.

“PRI” means ISDN Primary Rate Interface “PSAP” means a public safety answering point that has been designated to receive 9-1-1 calls and dispatch appropriate emergency services.

“PSTN” means Public Switched Telephone Network.

“RTP” means Real Time Protocol.

“SBC” means Session Boarder Controller.

“SIP” means Session Initiated Protocol.

“Site(s)” means Customer location as defined in Appendix C of Exhibit 1 attached to this NI Pricing Schedule.

“SOAP” means Simple Object Access Protocol.

Services U.S.

AT&T and Customer Proprietary Page 4 of 19

Do not disclose or duplicate

“SSL” means Secure Sockets Layer.

“Subscriber” means a Microsoft Teams user with a valid 10-digit DID number.

“TCP” means Transmission Control Protocol.

“TDM” means Time Division Multiplexing.

“Territory” means the United States of America exclusive of Puerto Rico.

“UDP” means User Datagram Protocol.

“Users” means Customer’s and its Affiliates’ personnel, employees, visitors and other users of the ERS.

“VoIP” means Voice over IP.

“VPN” means Virtual Private Network.

All other capitalized terms used but not defined in this SOW have the meaning given them in the Agreement.

2. Scope of Work

Supplier will provide the ERS for Customer’s use in conjunction with AT&T IP Flex Reach. For avoidance of doubt, Customer is responsible to contract with AT&T independently of this SOW for the IP Flex Reach service.

The deployment of the ERS detailed herein will be referred to as the project (“Project”). Supplier shall provide all Services in Territory. This SOW is based on information known as of its Effective Date and is subject to change, upon written mutual agreement, as new information may be discovered over the course of the engagement. The Project and all Services to be provided hereunder shall be rendered in accordance with and shall be deemed rendered pursuant to the terms and conditions of the Agreement and this SOW.

The ERS provides E-9-1-1 call routing and enhanced location delivery to over 6,000 PSAPs across the United States. In addition, it provides basic 9-1-1 connectivity to PSAPs in NENA i1 coverage areas. The ERS is delivered via direct SIP connectivity to Supplier’s 9-1-1 SBCs in two (2) geo-redundant datacenters, from the Customer’s on-premise PBX or SBC. 9-1-1 calls will be routed to the ECRC for verbal validation if Customer does not provision the Endpoint Data or for Microsoft Teams teleworkers as required by Microsoft. For administrative functions Customer will be provided access to the Interface to manage Endpoint Data within the ERS. For Microsoft Teams, Customer will be provided with a PowerShell script to download their subscriber’s 10-digit DID phone numbers from the Microsoft Teams tenant and upload them into the ERS via SOAP API.

E9-1-1 calling via the ERS supports the ability to place 9-1-1 calls from all telephones at a Site terminated in Customer PBX Equipment that terminate IP Flex Reach. The ERS must be able to recognize the caller’s identity and determine their location based on the data provisioned in the ERS and the information received at call-time.

The ERS serves as a provisioning and validation hub to store and manage the validity of each caller’s identification and location data, which is then used to route 911 calls to the proper PSAP. In the routed 911 call, the ERS includes the caller’s validated identification and location details. This means all the individuals in your organization must be provisioned as subscribers in the ERS, and the locations as ERLs, so that ERS recognizes and correctly identifies them for accurate call routing to the proper PSAP. For Microsoft Teams, user information as well as ERL and ERL validation will be done in the Microsoft Teams tenant. Only the subscriber’s 10-digit DID will be provisioned in the ERS. In addition to the ERS Service,. Prior to turn up of the ERS for Customer, Supplier will undertake tests of the E9-1-1 functionality in support of the ERS. In the event that Supplier cannot, through the exercise of commercially reasonable efforts, successfully complete testing for all E9-1-1 functionality as per the mutually agreed to ATP, AT&T may terminate the ERS and associated Order for the affected Customer, and except for reimbursement of all funds paid by Customer up to the date of termination, shall have no liability or further obligation with respect thereto.

2.2 SOW Term

The term of the ERS shall commence on the date ATP is executed and signed-off by Customer and shall continue, unless terminated in accordance with the Termination specified in this SOW for a term of thirty-six (36) months (“Term”). Customer will be invoiced for the SOW monthly recurring items as defined based upon full deployment (11,000 endpoints).

2.3 ERS Components

The following diagram illustrates how the ERS routes an E911 call, assuming Customer has provided valid subscriber data beforehand AT&T call termination components will use NENA standard interfaces where applicable (NENA i1, i2).

Services U.S.

AT&T and Customer Proprietary Page 5 of 19

1. A 9-1-1 call is placed within the organization’s network from a Microsoft Teams Client into the O365 Cloud PBX or from the enterprise phone or softphone into the 3rd party PBX

2. Microsoft Teams, O365 will trigger its notifications and bridge-in any security desk/facility personnel and sends the call to the ATT/Customer SBC. The 3rd party PBX will send the call to the ATT/Customer SBC.

3. ATT/Customer SBC sends the call to Intrado ERS over the internet (VPN recommended). The MS Teams call will include the user location in the SIP message PIDF-LO section

4. The ERS parses the Microsoft Teams PIDF-LO location information. For the 3rd party PBX, the ERS will match the caller information with a provisioned record in the database, triggers its call notifications and bridge-in any security desk/facility personnel

5. The ERS determines the correct PSAP from the caller’s provided location and delivers the call to it

6. PSAP queries the regional ALI database to obtain the caller’s location information and callback number

7. The regional ALI database queries the ERS national ALI database for the caller’s location and callback number and delivers this data to the PSAP display so emergency responders can be dispatched.

8. Non-emergency calls will be sent to the IP-Flex Reach cloud

ERS is composed of the following components with functionality as described below:

“ERS Portal” The ERS Portal is a web-based dashboard with administrator access to the ERS account for configuration, record provisioning and reporting.

“ERS API” The ERS API enables enterprises to automatically add, modify and delete locations and users through integration with enterprise subscriber management tools.

“Provisioning Server”

The Provisioning Server geocodes and validates locations for insertion into the National ALI Database.

“National ALI Database” (“nALI”)

The 9-1-1 Call Server receives 9-1-1 calls and determines the appropriate routing actions based on the location of the caller and relevant call routing configurations.

“9-1-1 Call Server” The 9-1-1 Call Server receives 9-1-1 calls and determines the appropriate routing actions based on the location of the caller and relevant call routing configurations.

“9-1-1 Call Routing Network”

The 9-1-1 Call Routing Network receives and routes the 9-1-1 call from the ERS to the terminating 9-1-1 infrastructure and PSAP throughout the US.

“ECRC” ECRC handles un-provisioned and failover 9-1-1 calls, as well as Microsoft Teams teleworkers calls. The ECRC is staffed by APCO-certified dispatchers, who verbally confirm the caller’s location and transfer the call via the selective router network to the appropriate

PSAP.

“IP Flexible Reach” An AT&T SIP trunking service that delivers integrated access for IP PBX, TDM PBX or Key System environments

Services U.S.

AT&T and Customer Proprietary Page 6 of 19

Do not disclose or duplicate

3. AT&T Responsibilities AT&T will be responsible for executing the following activities. Activities not expressly included in this SOW are outside the scope.

3.1 AT&T Project Management

In support of the Services provided to Customer, AT&T will:

(a) Assign a designated AT&T Project Manager (“AT&T PM”) to interface directly with Customer Project

Manager and serve as the primary interface to Customer organization.

(b) Conduct a formal project kick-off meeting.

(c) Provide a draft Project Plan summarizing the Project, respective roles and responsibilities of the Parties, and timeline for performance draft for Customer’s review. The draft and final document will reflect Customer’s priorities and timeframes. AT&T and Customer will mutually agree to the Project Plan.

(d) Participate and provide status and project planning meetings as mutually agreed. The audience for such status meetings may be either AT&T, third party or Customer determined team members.

(e) Coordinate with Customer or AT&T Project Managers to manage and track Installation and Project performance regarding the installation of AT&T Services against the Project Plan and schedules. Track all Change Control events, which relate to AT&T Services.

(f) Develop and maintain any contact list and communication plan. Track and monitor prioritized action items and issues lists as needed.

(g) Coordinate scheduling, including Site access and change performance windows with Customer.

3.2 AT&T Installation and Configuration Services.

(a) Provide Customer with remote installation and start-up assistance to effectively operate ERS. An experienced deployment engineer will work with Customer, via phone and Internet connection, to advise, configure, and test ERS, including:

i. Provide recommendations for Service deployment and configuration best practices,

ii. Site preparation requirements

iii. Compatibility requirements

iv. Network and IP address requirements, including firewall port access.

v. Create an ERS test account

(b) Assist Customer with ERS configuration and integration with the telephony and data network.

(c) Assist Customer with ERL data validation and provisioning.

(d) Provide recommendations for product deployment and configuration as per best practices.

(e) Assist Customer with configuration of e-mail alerts for 9-1-1 call notification.

(f) Assist Customer with configuration of 9-1-1 call monitoring for a single Customer recipient.

(g) Configure the solution as per Customer’s technical and business requirements.

3.3 AT&T Test and Turn-up Services.

(a) Assist in running ERS ATP which may include the following:

i. IP connectivity between the various solution components

ii. Feature configuration

iii. Fallback scenarios

iv. System performance

v. Readiness to go live

(b) Assist Customer with troubleshooting and correct any deficiencies if applicable.

(c) Upon acceptance of the ATP by Customer, set the ERS account to Live mode.

3.4 Deliverables

AT&T shall complete all tasks defined above with the goal of driving towards the completion of the ATP.

Minimum requirements for completion of the ATP are a single endpoint, deployed into a single location that is proven to be capable of completing a call to the ERS. Prior to the completion of the ATP, AT&T will provide the following documentation to Customer:

(a) ERS Documentation

(b) ERS Networking Interface Description

3.5 Service Hours

The Services provided hereunder associated with the initial turn-up of the ERS shall be performed Monday through Friday, 8:00 a.m. to 4:00 p.m., Central Standard time, excluding designated AT&T holidays (“Normal Business Hours” or “NBH”), unless otherwise noted herein.

Services U.S.

AT&T and Customer Proprietary Page 7 of 19

Do not disclose or duplicate

AT&T Designated Holiday Date Observed New Year’s Day January 1st Easter Monday Monday after Easter Sunday Victoria Day Monday preceding May 25th Memorial Day Last Monday in May Independence Day July 4th Labor Day 1st Monday in September Canadian Thanksgiving Day (Second Monday in October) Thanksgiving Day 4th Thursday in November Day after Thanksgiving 4th Friday in November Christmas Day December 25th

Boxing Day December 26th

Hourly rates for Services provided outside of NBH if applicable are set forth below in Section 6.1; AT&T will invoice Customer at this rate for any such Services requested in writing by Customer.

4. AT&T’s SOW with Customer will include the Following Customer Responsibilities To manage the activities outlined herein on time and within the pricing provided, Customer assigned roles and responsibilities must be fulfilled effectively. Customer is responsible for the following:

4.1 General Responsibilities

(a) Assign resources and prepare procedures for installation, administration, testing, operation, and support.

(b) Provide a project manager to liaise with AT&T personnel for all aspects of this deployment.

(c) Provide AT&T with configuration details on the current data and telephony network configuration, topology, and any other reasonable information requested by AT&T.

(d) Ensure that all site preparation, compatibility requirements, circuits, and other specified service prerequisites are met.

(e) Configure all Customer premise equipment components.

(f) Contact the appropriate vendor(s) to obtain technical assistance for third-party products not supplied or supported by AT&T.

4.2 System Planning

(a) Collect the information specified and complete the configuration worksheet supplied by AT&T.

(b) Survey the Site(s) and determine the ERLs. Determine the source of the ERL data (authoritative database).

(c) Assign resources and prepare procedures for 9-1-1 administration, automation, third party database integration and support.

(d) Order, install, and configure circuits and/or network interfaces utilized for connecting to the ERS cloud.

These connections can be made via public Internet, VPN over public Internet, NNI connectivity between Customer’s Network and the ERS Cloud utilizing AVPN or other private transport. These IP connections will be comprised of SIP/TCP and RTP/UDP utilizing G.711 codec.

4.3 System Configuration

(a) Configure Customer PBX Equipment or O365 Cloud PBX with a test dial plan (i.e. 811) to facilitate testing and overall connectivity to the ERS.

(b) Configure Customer SBCs, firewalls, and other security devices to allow application connectivity between

Customer PBX Equipment or O365 Cloud PBX and the ERS.

4.4 Endpoint Data

(a) AT&T will provide to Customer an Interface. The Interface will allow Customer to provision Endpoint Data into the National Automatic Location Identifier database. The Interface shall allow Customer to update the Endpoint Data using only Customer premises or equipment necessary to access its VoIP telephone service. For Microsoft Teams, AT&T will provide a script that will be used to provision Endpoint Data into the ERS National Automatic Location Identifier database. The script will download the O365 user information using PowerShell and upload the users 10-digit DID phone numbers into the ERS using SOAP API. If the Endpoint Data is not provisioned by Customer, then the Endpoint Data must be provided with the E9-1-1 call.

(b) CUSTOMER EXPRESSLY ACKNOWLEDGES THAT IT IS SOLELY CUSTOMER’S OBLIGATION

AND RESPONSIBILITY TO ENSURE THAT CORRECT, ACCURATE AND CURRENT ENDPOINT DATA

IS ENTERED INTO THE INTERFACE FOR EACH ENDPOINT OR VIA THE SUPPLIED SCRIPT FOR

MICROSOFT TEAMS, OR THAT ENDPOINT DATA IS PROVIDED AT THE TIME OF THE CALL.

Services U.S.

AT&T and Customer Proprietary Page 8 of 19

Do not disclose or duplicate

(c) If required by applicable telecommunications carriers or applicable law, Customer shall provide AT&T with a letter of agency which authorizes AT&T, as a limited agent for Customer, to work with the telecommunications provider on Customer’s behalf for the purpose of establishing interconnections between AT&T, Customer and/or the telecommunications carrier that are necessary to enable AT&T to provide the

ERS.

4.5 9-1-1 Provisioning and Testing

(a) Define ERL with-in Customer’s physical floor plan of the Site(s).

(b) Assign subnets to ERLs (subnet discovery) to Location IDs. (MS Teams only)

(c) Assign switch and switch ports (Layer 2 discovery – LLDP-MED) to Location IDs. (MS Teams only)

(d) Assign wireless BSSIDs to Location IDs. (MS Teams only)

(e) Perform Initial batch upload of Endpoints and Endpoint Data via the Interface or via the supplied script for

MS Teams.

(f) AT&T will assist Customer in testing between Customer PBX or O365 Cloud PBX and the ERS, fallback 9-1-

1 call paths, voice quality.

(g) Perform live 9-1-1 calls from each ERL to confirm that applicable PSAP(s) are receiving the correct information.

(h) Sign off on the ATP for 9-1-1 Production call routing.

(i) Switch test pattern in Customer PBX or O365 Cloud PBX dial plan to route 9-1-1 calls to the ERS.

5. Project Governance

5.1 Change Control Process

Either Party must submit change requests to contractual documents in writing via the sample at Appendix A to this SOW. The party requesting the change must submit a written request to the other party and the receiving party shall issue a written response within five (5) business days of the receipt of the request, including whether the receiving party accepts or rejects the request and/or any changes to the Terms and Conditions. Once agreed both parties must execute the document in Appendix A.

5.2 Contacts:

AT&T Contacts

Account Management Project Management Support

Theresa Benko Contact Number (262)617-1004 Email: theresa.benko@att.com

Project management contact will be assigned at project kick-off support@911.west.com

888 908‐4167 https://support.911.west.com

AT&T Network Integration Contact

Name: Michael Reckley Title: Engagement Manager Contact Number: 248-892-2292 Email: mr5231@att.com

6. Charges AT&T shall provide the Services for the Fees stated below. All Charges are shown in US Dollars (“USD”). All fees, costs and expenses charged by AT&T to Customer will be as set forth in the SOW, and not the Agreement. Except as set forth herein, no other fees, costs and expenses may be charged by AT&T to Customer for this SOW.

mailto:support@911.west.com https://support.911.west.com/

Services U.S.

AT&T and Customer Proprietary Page 9 of 19

Table1 – Fee and Charges

Minimum Monthly Recurring Charges

Part # Description Unit Price Unit Qty Extended Price Monthly Term

EN911-EPOMRC

ERS and LM EndPoint $ 0.35 11000 $ 3,850.00 $ 3,850.00 $ 138,600.00

EN911-NETSER VPN Tunnel (Pair) $ 250.00 1 $ 250.00 $ 250.00 $ 9,000.00

Totals $ 4,100.00 $ 147,600.00

One-Time Charges

Part # Description Unit Price Unit Qty Extended Price Monthly Term

EN911-ERSSEF ERS Setup Fee $ 6,845.00 1 $ 6,845.00

Term Totals One Time Monthly Term

$ 6,845.00 $ 4,100.00 $ 154,445.00

Calls from devices with records un-defined on the ERS will be routed to the Emergency Call Relay Center (ECRC).

These calls will be invoiced at a rate of $100.00 per call (RE911-UNPRRC). ERS set up (EN911-ERSSEF) is a fixed fee that includes 10 professional implementation service hours. If the effort required exceeds the time allotment included in the one-time fee, additional hours will be quoted at the hourly rate of $250.00 (PROSR-PIPPSH).

Invoice Schedule and Terms (As Applicable)

Invoice Milestone

ERS One-Time Charge Start of Term

ERS Recurring Charges Start of Term and monthly thereafter

ERS Connectivity Option Start of Term and monthly thereafter

Professional Services Monthly as Professional Service Hours are expended

7. Engagement Assumptions This SOW is based on the following assumptions. If any of these assumptions are found to be inaccurate or invalid, AT&T shall provide Customer with the changes to the scope, tasks, deliverables or terms and conditions of this SOW via the Change Control Process described in this SOW.

(a) Customer will provide AT&T with requested information in a timely manner and takes full responsibility and liability for the accuracy of all information supplied to AT&T by Customer and which AT&T relies upon in its performance hereunder.

(b) During this engagement, Customer will provide reasonable access to personnel who will participate in meetings to answer questions or resolve issues as they arise.

(c) If security restrictions apply to any or all Customer systems, Customer may be required to assume additional responsibilities for maintaining the system and/or software because of its interface with the ERS.

(d) The ability of AT&T to provide the Services is dependent upon Customer’s local resources and their timely cooperation with AT&T, as well as the accuracy and completeness of any information/data Customer may provide AT&T.

(e) The following are out of scope for this SOW:

i. Modifications to the commercially available AT&T software or hardware

ii. Deployment services outside of the standard hours of coverage

iii. Resolution of problems encountered due to third party equipment and/or software

iv. As related to Customer use of APIs and scripts, code, code examples, commands, sample commands or modifications to code or commands are excluded beyond those provided in the standard AT&T documentation

v. Any onsite Services

(f) In the event of a potential overrun in terms of estimated installation charges, AT&T will contact Customer as soon as such potential is detected to arrange a Change Order per Section 5.1 of this SOW.

Services U.S.

AT&T and Customer Proprietary Page 10 of 19

Do not disclose or duplicate

(g) This SOW is not inclusive of the Emergency Gateway (“EGW”) appliance that provides the ability to dynamically track Endpoints with-in Customer defined ERL.

8. Termination

Customer may terminate this SOW for its convenience on three (3) business days’ written notice and without termination fee or additional liability, provided, however, that (i) no annual maintenance fees will be refunded for the current maintenance period of the Term; (ii) Customer shall be invoiced for professional services completed up to and including the termination date; and (iii) ERS invoices will not be prorated in the month of termination.

Services U.S.

AT&T and Customer Proprietary Page 11 of 19

APPENDIX A: SAMPLE Change Request Form

Type of Request:

Initiator (Company):

Change Request Received by:

Price Impact:

AT&T Additional Resources Req’d:

Task Description:

Other information related to Change:

Impact of Change Provide a description of the impact of the change (increase in duration, delay in start, cut-over date change, added dependency, additional resources required change to design, change to baseline solution, other).

AGREED and ACCEPTED: AGREED and ACCEPTED:

AT&T: AT&T

By:______________________________________ (Authorized Agent or Representative)

By:___________________________________________

Services U.S.

AT&T and Customer Proprietary Page 12 of 19

APPENDIX B: SAMPLE ACCEPTANCE TEST PLAN

Overview This includes a series of test cases that cover the functionalities of the Service. Test cases are grouped by functionality. Depending on the system deployment and Customer environment, certain test cases may or may not be applicable, while others may be added where applicable.

Test Cases

The test plan is divided into 4 series of test suites, each targeting a specific category of functionality of the ERS service:

1. ERS Connectivity (Open Internet, VPN, or NNI)

2. Provisioning Validation

3. 911 Test Calls

4. SIP Redundancy

Note: Test cases that have “N/A” as a possible result are dependent on Customer’s configuration.

All other test cases MUST be completed successfully.

1.0 ERS Connectivity

Test Case Number 1.0

Test Case Title VPN Connectivity

Test Purpose Verifies that VPN connections are established (if configured)

Test Case Procedure 1. Customer and SUPPLIER verify VPN is established

2. Customer and SUPPLIER verify traffic is routing through tunnel

Checks VPN tunnel is up and stable

Expected Results Both Customer and SUPPLIER show the VPN tunnel as complete

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Result Test Result

Remarks

Test Case Number 1.1

Test Case Title SIP Connectivity

Test Purpose Verifies that Customer IPs can successfully connect via SIP on port 5060 to both ERS SBCs.

Test Case Procedure 1. Verify that SIP options are received by SUPPLIER SBCs

2. Verify that SIP 200 OK response is received by Customer SBC

Checks 5. Two-way connectivity is properly established

Expected Results 6. Customer shows ERS SBCs as available / reachable

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Remarks <Repeat for each Customer IP address>

Test Case Number 1.2

Test Case Title PSTN Connectivity (PSTN Handoff Only)

Test Purpose Verifies that the Host can connect thru the PSTN Handoff number provided by SUPPLIER to the ERS SBCs.

Test Case Procedure 1. Place a test emergency call to SUPPLIER.

Checks 1. Emergency dialed number correctly translated to PSTN handoff

2. Call successfully received by deployment engineer.

Expected Results 1. Two audio way established with SUPPLIER deployment engineer

2. Subscriber DID received as CallerID

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Services U.S.

AT&T and Customer Proprietary Page 13 of 19

Test Case Number 1.3

Test Case Title Voice Quality

Test Purpose Verifies voice quality of link to the ERS

Test Case Procedure 1. Customers places a test call (711) to SUPPLIER.

2. Customer records a short message

Checks 7. Recorded message is played back to Customer

Expected Results 8. Playback audio quality is satisfactory

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Result Test Result

2.0 Provisioning Validation

Test Case Number 2.0

Test Case Title Manual Provisioning of Location and subscriber Information

Test Purpose Verifies that manual provisioning and validation of ERLs and subscribers is working correctly

Test Case Procedure 1. From the 911 dashboard, Customer provisions a couple valid ERLs with subscribers that will be used for testing purposes.

Checks 1. Customer provisions an ERL

2. Customer provisions a subscriber to the ERL

Expected Results 1. Location validates against SUPPLIER system

2. Location is saved

3. Provisioned subscriber to ERL

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 2.1

Test Case Title Batch Provisioning of Location and Subscriber Information

Test Purpose Verifies that batch provisioning and validation of ERLs and subscribers through the Customer portal is working correctly

Test Case Procedure 1. Export ERL batch template from 911 dashboard

2. Edit template file and insert a couple of valid ERLs

3. Import completed ERL batch template from 911 dashboard

4. Validate imported batch ERL file

5. Provision validated batch ERL file

6. Verify batch results and make corrections as needed

7. Export subscriber batch template

8. Edit template file and insert a couple of valid subscribers

9. Import completed subscriber batch template from 911 dashboard

10. Validate imported batch subscriber file

11. Provision validated batch subscriber file

Checks 1. ERLs and subscribers successfully provisioned.

2. Invalid ERLs or subscribers were identified

Expected Results 9. ERLs and subscribers are now available in the 911 dashboard

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Services U.S.

AT&T and Customer Proprietary Page 14 of 19

Test Case Number 2.2

Test Case Title SOAP Provisioning of Location or Subscriber Information

Test Purpose Verifies that provisioning and validation of ERLs or subscribers via SOAP is working correctly

Test Case Procedure 1. Customer executes a SOAP provisioning call

2. Verify that provided SOAP credentials are working

3. Verify that SOAP Web Services are available for provisioning

Checks Customer receives 200 OK response from 911 Web Services (i.e. does not receive 401

Unauthorized)

Expected Results 10. Provisioning web services are available

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

3.0 9-1-1 Test Calls

Test Case Number 3.0

Test Case Title 911 Call from Subscriber In Demo Mode

Test Purpose Verifies 911 calls are routed to the ERS and two-way audio is working

Test Case Procedure 1. Customer configures applicable 911 routing

2. Customer places a test emergency call to SUPPLIER from provisioned subscriber.

3. Engineer answers call using VPSAP

Checks 1. Call is received by SUPPLIER

2. Two-way voice path established between Customer and SUPPLIER

3. Codec=G.711u

4. Emergency location received

5. Account ID is identified using ADP method

6. Subscriber ID identified using LDP method

7. Callback Number is identified using Callback SIP field

Expected Results Call established between Customer and SUPPLIER

Test Date Click here to enter a date

Tested By Customer: Tested by:

Test Case Number 3.1

Test Case Title Location Determination Header Verification

Test Purpose Verify Header Format (FROM or CONTACT)

Test Case Procedure 1. Customer places a test emergency call to SUPPLIER from provisioned subscriber.

2. Record header from Call Detail Records (“CDR”)

Checks Header matches location determination preference

Expected Results Call establishes to SUPPLIER and headers can be parsed

Test Date Click here to enter a date

Tested By Customer: Tested by:

Remarks <Paste recorder header here >

Services U.S.

AT&T and Customer Proprietary Page 15 of 19

Test Case Number 3.2

Test Case Title Four (4) Minute Call Timer

Test Purpose Verifies that an average emergency call of 4 minutes can complete

Test Case Procedure 1. Customer places a test emergency call to SUPPLIER

2. Leave call established for four (4) minutes (average call length)

Checks Call quality is acceptable, and call remained established during the entire call duration.

Expected Results Call is not disconnected at any time

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 3.3

Test Case Title Extension Bind 911 Callback

Test Purpose Verifies that the provisioned extension can be called back VIA SIP

Test Case Procedure 1. Subscriber places a test emergency call to SUPPLIER from provisioned subscriber with and extension or non 10 digits DID.

2. Engineer receives call and verifies call back number

3. Customer and Engineer hang-up

4. Engineer places a call to the received callback number

5. Subscriber receives callback from engineer

Checks Call connects to correct subscriber within fifteen (15) minutes of callback

Expected Results Callback succeeds

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 3.4

Test Case Title Crisis Email Alert Notifications

Test Purpose Verifies that an emergency call from location with crisis alert notification enabled correctly sends the crisis email alert.

Test Case Procedure 1. Provision ERL with crisis email alert notification enabled

2. Customer places a test emergency call from subscriber associated with ERL

3. Verify email inbox of crisis email alert notification recipient

Checks Crisis Email Alert received with correct location information

Expected Results Email received by Customer

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 3.5

Test Case Title Direct Call Delivery

Test Purpose Verifies that emergency calls are routed to the correct security desk and two-way audio is working

Test Case Procedure 1. Customer configures direct call delivery for a specific ERL

2. Customer places an emergency call from subscriber assigned to the ERL.

3. Appropriate security personal receives call

Checks 1. Call is received by security desk

2. 2-way voice path established between Customer and security desk

3. Calling party (ANI) is correctly displayed at security desk phone

Expected Results Call established between Customer and security desk

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Result Test Result

Services U.S.

AT&T and Customer Proprietary Page 16 of 19

Test Case Number 3.6

Test Case Title Direct Call Delivery Dial Plan

Test Purpose Verifies that emergency calls made to the security desk dial plan are routed to the correct security desk

Test Case Procedure 1. Customer configures new security desk dial plan

2. Customer places a test emergency call using security desk dial from subscriber assigned to an ERL with direct call delivery.

3. Appropriate security personal receives call

Checks 1. Call is received by security desk

2. 2-way voice path established between Customer and security desk

3. Calling party (ANI) is correctly displayed at security desk phone

Expected Results Call established between Customer, SUPPLIER and security desk

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 3.7

Test Case Title Three-Way Conference Calling

Test Purpose Verifies that emergency calls are routed to SUPPLIER and the correct security desk and two-way audio is working

Test Case Procedure 1. Customer configures three-way conference for a specific ERL

2. Customer places a test emergency call from subscriber assigned the ERL.

3. Engineer answers call using VPSAP and appropriate security personal receives call

Checks 1. Call is received by SUPPLIER and by security desk

2. 2-way voice path established between Customer and security desk

3. Codec=G.711u

4. Calling party (ANI) is correctly displayed at security desk phone and VPSAP

Expected Results Call established between Customer, SUPPLIER and security desk

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

4.0 SIP Redundancy

(The following test cases are to be performed for SIP Connectivity Customers only)

Test Case Number 4.0

Test Case Title ERS Primary SBC IP Address Is Unreachable

Test Purpose Verifies that emergency calls are routed to the alternate ERS SBC

Test Case Procedure 1. Engineer blocks access to the ERS Primary SBCs (via firewalls)

2. Customer verifies that the ERS Primary SBCs are determined to be unreachable (By loss of

SIP OPTIONS connectivity)

3. Customer places a test emergency call

Checks Call is routed correctly to ERS Secondary SBC IP address

Expected Results Connectivity failure results in Customer selecting alternate route and 911 call routing capabilities are maintained

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Services U.S.

AT&T and Customer Proprietary Page 17 of 19

Test Case Number 4.1

Test Case Title Both ERS SBC IP Addresses Are Unreachable

Test Purpose Verifies that 911 calls are routed to the ECRC

Test Case Procedure 1. Engineer blocks access to both Primary and Secondary ERS SBCs (via firewalls)

2. Customer places a test emergency call

Checks Call is routed correctly to ECRC via contingency routing number over PSTN.

Expected Results 1. Connectivity failure results in Customer selecting alternate route and 911 call routing capabilities are maintained.

2. Location data may not be available while routing over PSTN

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 4.2

Test Case Title Re-Activate SBC IP Addresses

Test Purpose Verifies that 911 calls are routed to the Primary ERS SBC IP address after connectivity is re-established

Test Case Procedure 1. Engineer re-activates both Primary and Secondary ERS SBCs (via firewalls)

2. Customer places a test emergency call

Checks 1. Call is received by SUPPLIER

2. 2-way voice path established between Customer and SUPPLIER

3. Codec=G.711

4. Emergency location received

5. Subscriber ID identified

Expected Results Call established between Customer and SUPPLIER

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Test Case Number 4.3

Test Case Title ERS SBC Call Rejection

Test Purpose Verifies that 911 calls are alternate routed when ERS SBC responds “503 Service unavailable”

Test Case Procedure 1. Engineer configures account for maintenance mode

2. Customer places a test emergency call

Checks 1. Primary ERS SBC responds with “503”

2. Customer attempts to connect to secondary ERS SBC

3. Secondary ERS SBC responds with “503”

4. Customer attempts to alternate route via contingency routing number

Expected Results 1. Call is routed correctly to ECRC via contingency routing number over PSTN

2. Subscriber Caller ID is passed in the CRN call.

3. If subscriber does not have a DID, main BTN is provided as Caller ID

Test Date Click here to enter a date

Tested By Customer: SUPPLIER:

Services U.S.

AT&T and Customer Proprietary Page 18 of 19

Do not disclose or duplicate

APPENDIX C: Acceptance Testing Sign-Off

Intent

11. The intent of the Acceptance Testing sign-off is to confirm that members of both parties, Supplier and Customer, mutually agree that all contractual obligations have been fulfilled and delivered.

12.

13. Services Tested: ☐ Emergency Routing Service (ERS)

Testing Summary

14. A total of ____ test cases were successfully executed in the ATP.

15.

16. There was a total of ____ failed test cases while _____ were not applicable (N/A) as per Customer’s configuration.

17.

18. The overall status of this ATP is a PASS.

19.

20. For complete details of the test case results, please refer to the ___________________________ document.

Acknowledgement

21. By signing this document, Customer acknowledges the following:

a. The Supplier product and services have met all acceptance criteria and are ready to go LIVE.

b. Customer understands the provisioning and ongoing maintenance responsibilities of the system.

c. Once the ERS account is LIVE, billing commences, and minimum billing charges will apply.

d. Unless otherwise indicated, the ERS account will be activated upon reception of the ATP sign-off.

22.

AGREED and ACCEPTED: AGREED and ACCEPTED:

CUSTOMER: SUPPLIER

By:______________________________________ (Authorized Agent or Representative)

By:___________________________________________ eSigned - Veronica Danao

Contract Specialist, as signatory for AT&T

11 Nov 2022

Services U.S.

AT&T and Customer Proprietary Page 19 of 19

APPENDIX D: Microsoft Direct Routing Configuration Guide &…