DeKalb County_Mod.pdf - Illinois ... - Illinois State Police County_Mod.pdfDeKalb County plans to implement a Next Generation 91-1 System county--wide with t he primary objective to

9-1-1 General Information August 2017

1

County: DeKalb 911 GENERAL INFORMATION

DATE: August 2017 Type of Change: Long Form Modification Short Form Modification Current System Name Population Served Land in Square Miles DeKalb County ETSB 105,160 638 List PSAPs: Primary Secondary

DeKalb Sheriff Dept. DeKalb PD DeKalb Sheriff

DeKalb Police Dept. DeKalb Sheriff DeKalb Sheriff Dept.

911 System Contact: Glenna Johnson

Street Address: 150 N. Main St.

City, State and Zip Code: Sycamore, IL 60178

Office Telephone: (815) 899-4559

Cellular Telephone: (815) 761-6798 Email: [email protected]

Wireless Coverage for Consolidated System: 100% Phase II compliant 100% Phase I compliant

Please check if applicable: X NG9-1-1 capable X Receive 9-1-1 Text __ Receive 9-1-1 Video

VERIFICATION

I, Glenna Johnson, first being duly sworn upon oath, depose and say that I am 911 Coordinator, of DeKalb County Illinois ETSB; that I have read the foregoing plan by me subscribed and know the contents thereof; that said contents are true in substance and in fact, except as to those matters stated upon information and belief, and as to those, I believe same to be true.

Subscribed and sworn to before me

this_£_ day of---'-llh-'--'---'-1----' 20 a.

NOT�C�f-

2

r OF,-�-� s·. L •• ''.1EN o RUBECK � NOTARY PUBLIC· STATE OF ILL1NOIS l MY COMMISSION EXPIRES:04/06/19 ' ,_. ,vv.,_..,_,.,._vv,,.--vv,,.,v

April 14, 2017

Michael Ramsey NG-911, Inc. 815 South Highland Williamsburg, IA 52361

Dear: Mr. Ramsey

9-1-1 SYSTEM PROVIDER

LETTER OF INTENT

This letter is to confirm our intent to modify our 9-1-1 System. Enclosed is your copy of our modification plan to be filed with the Department of the Illinois State Police for approval. Thank you for your assistance in this matter.

Sincerely,

.

,,-. .

�')vCJ v-0\.1'\�...,,

Glenna Johnson 911 Coordinator

enclosure: Modification Plan

3

Page 1 of 41

Plan Narrative

DeKalb County Modified Plan

August 2017

Plan Narrative: DeKalb County Illinois ETSB

Page 2 of 41

Contents ` 1.0 Overview .................................................................................................................................. 4

Executive Overview ..................................................................................................................... 4

PSAPs ......................................................................................................................................... 4

Radio / Telecommunications ........................................................................................................ 5

Dispatch to Participating and Adjacent Agencies ......................................................................... 6

Adjacent Counties: ....................................................................................................................... 6

Territory Covered by the 9-1-1 System: ....................................................................................... 6

Carriers Providing Service to DeKalb County ............................................................................... 6

Intergovernmental Agreements: ................................................................................................... 7

Public Information including Text to 9-1-1: ................................................................................... 7

Training: ....................................................................................................................................... 7

New system configuration and technological architecture (i.e., network and routing); .................. 8

NG9-1-1 ESInet Infrastructure for NINGA – Refer to Exhibit B (For readability purposes this diagram will be submitted separately on large paper) ................................................................ 12

2.0 Part 1325, Section 1325.205 (f) .............................................................................................. 19

2.1 Identify the 9-1-1 system providers. If multiple providers are being used, provide a detailed description of each provider's role; ............................................................................................. 19

2.2 Explain what national standards, protocols, and/or operating measures will be followed; 19

2.3 Explain what measures have been taken to create a robust, reliable and diverse/redundant network; and whether other 9-1-1 Authorities will be sharing the equipment. 19

2.4 Explain how the existing 9-1-1 traditional legacy wireline, wireless and VoIP network, along with the databases, will interface and/or be transitioned into the NG9-1-1 system. ........... 21

2.5 Explain how split exchanges will be handled. .................................................................. 24

2.6 Explain how these databases will be maintained and how address errors will be corrected and updated on a continuing basis; ............................................................................................ 28

2.7 Explain who will be responsible for updating and maintaining the data, at a minimum on a daily basis Monday through Friday. ............................................................................................ 30

2.8 Explain what security measures will be placed on the IP 9-1-1 network and equipment to safeguard it from malicious attacks or threats to the system operation and what level of confidentiality will be placed on the system in order to keep unauthorized individuals from accessing it. ............................................................................................................................... 30

Quality of Service Standards ...................................................................................................... 32


Page 3 of 41

Test Plans. ................................................................................................................................. 32

Initial Cutover Strategy ............................................................................................................... 32

Disaster Recovery ...................................................................................................................... 33

Exhibit A............................................................................................................................................ 35

Exhibit B............................................................................................................................................ 36

Exhibit C ........................................................................................................................................... 37


Page 4 of 41

1.0 Overview Executive Overview

The DeKalb County ETSB is filing its modified plan to implement a Next Generation 911 system. The Emergency Telephone System Boards (ETSBs) for Boone, Bureau, Carroll, DeKalb, Jo Daviess, Lee, McHenry, Ogle, Stephenson, Whiteside and Winnebago counties, have joined together into a unified planning effort to migrate to Next Generation 9-1-1 (NG9-1-1). This group is called 9-1-1 Northern Illinois Next Generation Alliance (NINGA).

The overall regional project involves eighteen (18) primary PSAPs and one (1) unmanned backup PSAP (Boone County) with ninety-eight (98) fixed workstation positions that will be fully integrated with multi-agency, multi-jurisdictional, mapping. There will be five (5) to seven (7) portable Workstations across the NINGA footprint. The DeKalb ETSB will have two (2) portable workstations.

The system is IP-based and is fully compliant with all current NENA i3 standards; it is geographically diverse and has a redundant configuration and design to avoid any single points of failure (SPOF). The system architecture is designed and provisioned so that the failure of any one component will not result in a total system failure. All essential system components are protected through the use of redundant components to limit a SPOF.

The system will provide service parity for all potential 9-1-1 callers, and being IP based, can be administered, monitored and managed both locally and remotely. The system will host multiple remote PSAPs in multiple jurisdictions. Each PSAP will be composed of a number of positions plus security appliances and software necessary to prevent intrusion by unauthorized personnel. Each individual PSAP will have a diverse IP transport network between the remote PSAPs and the system cores. The system has varying levels of security and administration privileges for managing, configuring, monitoring, maintenance and diagnostic activities.

NG-911, Inc. is the 9-1-1 System Provider. NG-911, Inc. is a certificated 9-1-1 Service Provider in Illinois (See Order, August 22, 2012, Illinois Commerce Commission (ICC) Docket No. 12-0093.)

PSAPs

DeKalb County plans to implement a Next Generation 9-1-1 System county-wide with the primary objective to provide the citizens of DeKalb County Illinois with a high quality of 9-1-1 services.

DeKalb County’s Public Safety Answering Points (PSAPs) will collectively answer, process and direct all calls and texts placed to 9-1-1 within their jurisdictional boundaries. DeKalb County has two (2) PSAPs, the DeKalb County Sheriff PSAP with seven (7) positions, and the DeKalb Police Department PSAP with six (6) positions, and two (2) portable Workstations. Portable workstations are heavy duty laptops in a hard case that can be transported anywhere very easily. The portable workstations can be used as Command Post workstations or deployed in various situations. Since the system is Internet Protocol (IP) based, these fully functional portable workstations can connect to the


Page 5 of 41

Emergency Services Information Network (ESInet) and receive calls. (iFiber will be the Term of Art used hereafter to refer to the underlying ESInet transport network provider.) Each NINGA County retains its own ETSB and decision making capabilities in how these portable workstations are utilized. DeKalb County may deploy the two (2) workstations in a mobile command center or at a specific location for example, portable workstations in DeKalb could be deployed to the NIU campus should an onsite situation occur which requires the unit.

Both DeKalb PSAPs backup each other. Refer to the General Information document and the Table 1 below. DeKalb County will have two (2) PSAPs in operation in their present location using trained, qualified, and experienced personnel.

PSAP Backup

DeKalb County Sheriff’s Office DeKalb Police Department

DeKalb Police Department DeKalb County Sheriff’s Office

Table 1

There are two (2) geographically diverse, fully redundant NG-911, Inc. operated Data Centers (Data Centers will be used as Term of Art) which house the NG9-1-1 Next Generation Core Services (NGCSs). The two (2) Data Centers are: (1) the NIU Wellness and Literary Data Center in DeKalb, Illinois, and (2) the TriRivers Data Center in Rockford, Illinois.

Carriers may connect to the ESInet at various points on the Fiber Ring. These points of interface (POI) locations will be mutually agreeable to NG-911, Inc., iFiber and the Access Carrier. iFiber may also provide points of interface (POI) for Access Carriers. These POI’s specific locations are documented on the Network Diagrams and in the Access Test Plan document.

The Next Generation 9-1-1 system will increase functionality, redundancy, diversity, and scalability. The system will have automatic failover capability between the two Data Centers. Having two Data Centers to serve the PSAPs on the ESInet will increase reliability 100%. The new NG9-1-1 system by design has redundancy built in at every point practical to eliminate all SPOF.

The NG9-1-1 system will handle calls from all Carriers that are answered today. The NG9-1-1 ESInet will enable a wide spectrum of users to utilize emergency support services, such as hearing impaired, deaf, speech impaired, and non-English speaking callers (Text to 911 and TTY technology).

DeKalb County is currently handling Phase II wireless calls and this system will be as accurate in locating wireless callers as the current system.

Radio / Telecommunications

All emergency services within DeKalb County, Illinois have the capability to be linked either by radio or telephonically. Details on both primary and secondary communication procedures are contained in the Call Handling Intergovernmental Agreements. The Participating Agency Forms include the Radio and other Dispatch capabilities.


Page 6 of 41

Dispatch to Participating and Adjacent Agencies

Details of the elaborate dispatch system utilized by the PSAPs are included in the Call Handling Agreements plus the Participating Agency and the Adjacent Agency documents.

In DeKalb County, there are a total of thirty-seven (37) Participating Agencies. There are seventeen (17) Adjacent Agencies in eight (8) Counties surrounding DeKalb.

Adjacent Counties:

NINGA Counties adjacent to DeKalb: Boone, Lee, McHenry, Ogle and Winnebago. As each NINGA county is approved to be on the network, the calls will be handled via the NG9-1-1 network architecture. Interim and ongoing transfers are detailed in the Participating and Adjacent Agency documents.

Counties listed as adjacent to DeKalb outside NINGA: Kane, Kendall, LaSalle, [includes the State Police Districts 2 (Kane) and 15 (DuPage)]

Territory Covered by the 9-1-1 System:

The DeKalb County enhanced 9-1-1 system provides service to all residents of the geographic area covered by DeKalb County. Communities Served are listed on the Communities Served document.

Carriers Providing Service to DeKalb County

Each Carrier in the DeKalb footprint is participating in meetings as needed for connection decisions, data exchange and signaling. Carrier presentations have been provided to all Access Carriers, underlying VPC and MPC Carriers, ESInet Providers, SS7, SIP and Text Control Center (TCC) providers.

To see a full list of each Access Carrier in the DeKalb footprint, please refer to the Carrier Listings Document. The Network Diagrams show directly connected carriers. VoIP Carriers and Resellers are not included on the network diagrams by name.


Page 7 of 41

Intergovernmental Agreements:

The DeKalb County ETSB has entered into thirty-seven (37) separate intergovernmental agreements for call handling and system procedures with emergency service providers within DeKalb County and seventeen (17) separate agreements with eight (8) adjacent counties to DeKalb County. The agreements form the basis for linkage, cooperation, and communication between both inter-county and intra-county agencies. The DeKalb County ETSB has been extremely fortunate in building a strong relationship with the area emergency services providers. Numerous informational meetings have been held and a strong spirit of cooperation and problem solving has emerged. Copies of new agreements are contained and attached to this modification as exhibits under the heading Call Handling Agreements. There are no new agreements for DeKalb as of the filing.

The Next Generation 911 system has capabilities and functions for call handling that are not possible in existing E-911 technology. Routing policy rules can intelligently route calls depending on conditions with member PSAPS. This can range from simple overflow of calls where all the workstations in each PSAP or county are all busy handling 911 calls, the additional calls can overflow to designated PSAP(s) until workstations become available to the long-term abandonment or isolation of a PSAP and call routing would be more long term.

An agreement for default routing is another part of the NG9-1-1 decision making that will be identified in the appropriate IGAs. This agreement theoretically could extend to default routing, routing where insufficient or no location information arrives with the calls, and typically the call just has the ANI. Although receiving only the ANI is a rare event, it can and does occasionally happen. An example of default routing where only the ANI is received is where the service order update has not arrived for the wireline database and service has been turned on. This situation will be mitigated by building NPA/NXX tables to “more intelligently” route these calls with only an ANI to the best choice of PSAP; the wireline example could be used for only a matter of hours. DeKalb County is the first NINGA ETSB to cutover; all default routed calls automatically go to DeKalb. NINGA agreed that Lee will become the primary PSAP for all default calls with Ogle PSAPs as backup. As Lee and Ogle are cutover they assume the responsibilities. Existing IGAs are documented between the members to utilize the flexibility of the new system in routing overflow calls.

Public Information including Text to 9-1-1:

The DeKalb County ETSB continues to provide public awareness and information by means of several local media outlets, public presentations and school programs, signage, etc. The DeKalb County ETSB plans for increased publicity once the Modification is approved.

Training:

Detailed training will be provided to all persons staffing the PSAP location. The initial PSAP operators will be existing employees of the communications centers where the PSAP is located and all have had previous training in emergency call handling and dispatch. NG-911, Inc. will provide extensive training on all aspects of the equipment.


Page 8 of 41

Miscellaneous Operations: The PSAPs in the DeKalb County 9-1-1 System meet the following requirements:

• Twenty-four hour a day operation, three hundred sixty-five days a year. • A call logging recorder capable of recording, and date and time stamping of all 9-1-1

position/calls, texts and radio frequencies which are used to dispatch the assignments. • An alternate power source, generator, capable of sustaining full operation of the PSAP

including communications, should a commercial power outage occur. The PSAP also has UPS to allow continued operation during switch over from commercial power to alternate power. Detailed power and grounding surveys have been provided by each ETSB to the 9-1-1 SSP. Each PSAP has been verified to have a properly engineered building ground in place, appropriate heating and cooling, physical and logical security and equipment synchronization to ensure the clocks for the time stamps are accurate.

• TDD service is available at each PSAP to allow the hearing-impaired citizen the same access and availability to call 9-1-1 as all other citizens. TDD calls are delivered to the workstation and do not require a separate device.

• The PSAPs will maintain an electronic log of the 911 calls and texts. • The DeKalb County ETSB PSAPs have adopted a set of standard operating guidelines that

include PSAP security.

New system configuration and technological architecture (i.e., network and routing);

The NG9-1-1 architecture is comprised of an Emergency Services Internet Protocol Network (ESInet) to connect the PSAP using IP signaling and aggregation points of interface (POIs). Direct Access Carriers connect to the Data Centers. Each Carrier will choose from Legacy (SS7/ISDN) and newer Protocols for trunk signaling (SIP). Where the ESInet appears in a Carrier or Private Switched ALI (PS/ALI) Switch Location, the Carrier or PS/ALI customer may connect to the fiber at that location, thus including a zero-mile access solution. Note: For DeKalb, NIU will be the only directly connected PS/ALI customer for Phase I at cutover. All other PS/ALI customers will be routed from the existing DKLBILXA4ED Legacy Selective Router to the NG-911, Inc. two (2) IP Selective Router equivalent equipment in each of the two (2) Data Centers. Phase II, remaining PS/ALI customers will establish direct interfaces to the two (2) Data Centers as required, once existing Carrier customer contracts have been reviewed and databases, routes and signaling are established. Refer to the Network Access Diagrams and the Test Plans for specific Carrier and PS/ALI access configurations.

Planning for direct PS/ALI customers is handled the same way as a small direct Carrier to the network.

Session Border Controllers (SBCs) provide the access control for protection from unwarranted Cyber Attacks, Denial of Service Attacks and/or focused Network Overloads. The design is in accordance with the NENA i3 Standards; the Data Centers or designated points on the fiber ring are the destination points for all inbound emergency 9-1-1 traffic in the areas served. The two (2) Data Centers are also the egress points for all traffic outbound from the ESInet such as outbound calls


Page 9 of 41

from one of the PSAPs serving the area to an adjacent PSAP, not yet on an ESInet. Each Data Center comes with a fully duplicated set of NG9-1-1 equipment called NGCS

Carriers using Legacy Signaling are accommodated through two (2) sets of Legacy Network Gateways (LNGs), one in each Data Center. The LNGs convert SS7, ISDN PRI and MF, as needed, to SIP before the calls are handed off to the NGCS. Refer to the NENA Call Flow Diagram Figure 1 (see Exhibit A) which reflects the typical NGCS architecture; for readability purposes print include Exhibit A with landscape orientation.

Where a PS/ALI customer direct connects to the Legacy Selective Router (SR) and wishes to connect to the NG-911, Inc. SR, those customers will be cut over to the NGCS in a Phase II of the NINGA project. A PS/ALI customer is similar to a small carrier in terms of connecting to the NG-911, Inc. SR.

NG9-1-1 Call Flow

Reference Figure 1 NENA Call Flow Diagram above. The Network has the same NGCS in both Data Centers for redundancy. The acronyms are explained in the text. The blue boxes represent additional NGCS within the i3 NENA Standard architecture and design

Emergency Services IP Network (ESInet) is an IP (Internet Protocol) network. The ESInet is a private, managed IP network, not on the open Internet. The key to network reliability is redundancy. The NGCS listed below are redundant in the NG9-1-1 Design.

LIS – the Location Information Server stores information against a key. Keys are IP addresses, Media Access Control (MAC) addresses or telephone numbers, for legacy wireline customers. The LIS uses DHCP (Dynamic Host Configuration Protocol), the protocol that provides the IP address or HELD (a protocol identified by the Internet Engineering Task Force (IETF) to deliver HTTP (Hypertext Translation Protocol) based location protocol. The LIS is queried. The LIS returns a PIDF (Presence Information Data Format,) the new form of location. A PIDF can contain a civic (street) address or geo (X Y) coordinates. Location may be obtained by value or by reference. Location by value means the actual location is sent in the signaling. Location by reference supplies a Uniform Resource Identifier (URI) with a SIP or HELD protocol.

ECRF – the Emergency Call Routing Function (a.k.a. IP Selective Router database instructions for call routing) is the heart of the NG9-1-1 routing database used for ALL calls. It is queried using the LoST (Location to Server Translation) protocol. It sends location (PIDF) in, plus a service Uniform Resource Name (URN) and gets a URI, typically a SIP URI of where to send the call. Conceptually the ECRF geocodes a civic addresses to a geo, and uses a point-in-polygon algorithm against a set of service boundary polygons that represent the area served by a PSAP. ECRF replaces the MSAG (Master Street Address Guide) and ESN (Emergency Service Number) codes. The External ECRF (sometimes called the Public LoST server) routes to the correct ESInet and the originating ESRP (Emergency Services Routing Proxy) within it. Inside the ESInet, the Internal ECRF (sometimes called the Private LoST server) routes calls to the correct PSAP.


Page 10 of 41

ESRP – the Emergency Services Routing Proxy (a.k.a. IP Selective Routing). The ESRP is the call routing engine. The ESRP uses the ECRF to choose a nominal next hop in routing. It then applies the route policy of the next nominal hop to determine the next actual hop. Route policy can take into account the state of the PSAPs, congestion, media server, source of the call and “suspicion level” provided by the border control function and more. Route decisions can include the next ESRP, a nominal PSAP, diversion PSAP, IMR Interactive Media Response System (IMR) or Busy.

PRF – the Policy Routing Function evaluates the PSAP (Agency) controlled rules about how calls are routed in the ESRP. Inputs include the PSAP (System) state, congestion state, security posture, call suspicion, call state (SIP headers and added data) and more. The output is a routing decision. The ESRP queries the ECRF with location for the “nominal next hop”. That entity’s policy is obtained from a policy store and interpreted. For example, rules are in the form of IF “this is true”, THEN do “that.” “This” is the input conditions expressed with “and/or” statements. “That” is the route, the actual PSAP, diversion PSAP, IMR, or Busy. Policy is dynamic which means the capability to change it at any time to new calls route with new rules. Policy rules have a standardized format.

BCF – the Border Control Function provides the access security border for the ESInet and the internal isolation border for the PSAP. It has both firewall and Session Border Controller (SBC) (SIP specific) parts. It marks calls with suspicion levels and has functions to block specific call sources. The ESInet BCF will withstand the largest feasible attack, currently known to be in the range of 10 Gigabits.

NG PSAP - the Next Generation PSAP gets all calls from the ESInet via SIP protocols with Location routed by the ECRFs. The PSAP will use the ECRF/ESRP function to route to queues of call takers.

LNG and LPG – Legacy Network Gateways and Legacy PSAP Gateways

There are entry and exit points to and from the ESInet which will exist as long as there are non-IP communications devices in the network. They are called Legacy Network Gateways (LNG) and Legacy PSAP Gateways (LPG). Inside the ESInet the architecture uses IP protocol based communications.

LNG - the Legacy Network Gateway serves as the bridge between the existing originating networks and the ESInet. One means of interface to the LNG for transition purposes is the existing Selective Router interface to the LNGs. This is an initial step to bring the CAMA/MF, SS7 and ISDN PRI (Legacy Signaling protocols) interfaces to the ESInet. The LNG is always outside the ESInet. It will reside in each of the dual Data Centers housing the redundant ESInet NGCS in DeKalb and Rockford. The LNG routes via the ECRF, always coming through the BCFs. Specifically, the LNG uses the ESRP to route the calls. The LNG interworks location protocols and formats between the legacy network and the ESInet. The e2 interfaces (wireless and VoIP) or internal LIS (replaces ALI Data for wireline) faces toward the legacy network. The LNG either supplies location-by-value in the SIP signaling, or may supply a location reference that resolves to itself using SIP or HELD protocol towards the ESInet. This will be part of the architecture as long as legacy networks are deployed. The LNG is on the Access side of the network architecture.


Page 11 of 41

LPG – the Legacy PSAP Gateway allows existing non-upgraded PSAPs to connect to the ESInet. There are no LPG requirements in the NINGA architecture for DeKalb.

LSRG - the Legacy Selective Router Gateway facilitates the handling of Split Exchange Code Routing. The LSRG allows calls entering the ESInet, once identified by the GIS Database as belonging to a location outside the ESInet, to be routed dynamically to the correct Legacy PSAP that serves that customer base. The LSRG is a temporary solution. When Carrier Switches with Split Exchange customers are served by an inter-connected ESInets, Split exchanges are resolved without an LSRG. The LSRGs are typically co-located with the LNGs on the egress side of the NG9-1-1 network returning calls to the Legacy Selective Router. Refer to the Network Diagrams Document and Split Routing section of this document.

LVF – the Location Validation Function (LVF) is used by the LIS Operator to validate location before loading it into the LIS. Similar to MSAG validation, the LVF verifies that the location matches a known address within the 9-1-1 Authority’s service area. It is like the ECRF, using the same protocols and same data. The LVF can validate to the street address, not just address range. It can also validate to the building, floor, and unit (apartment, suite, etc.) and room. The LVF introduces a few new address elements, for example, the prefix for a street type. Addresses inside the NG9-1-1 standard systems are conformant to the new Federal Geographic Data Committee (FGDC) standards.

Additional Data

Call data is supplied by service providers in the path and in the future possibly the device itself, signaled with the call, by value or by reference. Call data contains Access Carrier Contact data, Subscriber data, Service data (Class of Service equivalent), and device-specific data such as sensors, telematics, etc.

Caller data is specific to the caller (home, work or cell provide the same data) and in the future can be signaled with the call or queried from a database. It can contain Contact Data, Emergency Contact Data, Medical Data, etc.

Location data is specific to the location of the call; two calls from the same location will have the same location data. An ECRF query with a special service URN yields a URI to the data. Location data contains Building Owner/Tenant Contact information, Floor Plans, Alarm and Sensor data, Control Panel data and more.


Page 12 of 41

NG9-1-1 ESInet Infrastructure for NINGA – Refer to Exhibit B (For readability purposes this diagram will be submitted separately on large paper)

The focus of this ESInet Diagram (Exhibit B) is the Diverse Fiber, Fiber Electronics and the Power Supply for DeKalb County’s two (2) PSAPs. In addition, the two (2) Data Centers can be seen on the Fiber Ring in DeKalb and in Rockford. For this initial DeKalb filing, the two (2) Data Centers will be fully active and the DeKalb PSAPs in Sycamore and in DeKalb will be fully tested and operational on the ESInet. The delivery of the Fiber to each PSAP is 100meg, much more than the 20 Meg which was considered minimally required, with full 100 Meg access across the ESInet. As other Counties are added to the ESInet, the connectivity to additional PSAPs is added according to the planned implementation schedule and with bandwidth to match the Access Carrier’s P.01 Grade of Service requirements.

The iFiber network is an evolving network since its inception, always implementing continuous improvement for security and reliability. Just since July 2016 the following items have been implemented.

FY2017 - iFiber is scheduling to perform full on-site battery and rectifier inspections at all distribution and core locations and to perform preventative maintenance and address any issues noticed.

iFiber field technicians will all attend a week-long training session on maintenance of telco-quality battery systems and UPS systems.

All iFiber distribution and core locations are within acceptable operating specifications. iFiber has replaced weak battery cells and rectifiers to keep those affected systems in specifications. iFiber maintains the configuration of all battery and rectifier system monitoring within the iFiber network. As such, iFiber has full visibility of all UPS functions including power outages, battery health, and total power drops.

iFiber maintains spare batteries (new) and rectifier(s) (new) in stock in anticipation of power failure at any distribution location. Stock batteries are fully charged at all times and available for emergency replacement in case of long-term power outages.

Refer to the Network Test Plan for the full set of requirements for Power and Environment. In addition to the Data Center NOC Monitoring, NG-911, Inc. as the 911 SSP is installing a solution for real time NOC monitoring into the Data Centers and PSAPs to alert and create tickets should a service threshold be crossed. NG-911, Inc. will report any “reportable” incidents to the ISP, ICC and/or FCC.

iFiber received Federal BTOP Grants which included money to build a broadband fiber network covering underserved areas of Northern Illinois; part of the finding mandate included building to support Public Safety.

Database


Page 13 of 41

The DeKalb County ETSB has designed and purchased a comprehensive NENA i3 standards based system that is highly sophisticated. The system will provide automatic location identification (ALI), automatic number identification (ANI), and selective routing to the PSAP using dynamic routing. In addition, the system will feature geo-spatial, policy based functionality that will deliver superior service and response to the emergency needs of the citizens of DeKalb County. Every structure in DeKalb County has been identified and every residence has a street number with a street or road name. Additionally, geo-spatial number has been designed with address points to identify the residence where the 9-1-1 request is made. All database elements comply with NENA Data Formats for ALI, MSAG and GIS.

Database flow starts with a Location Information Services function (LIS). A LIS or its equivalent is required to support interactive validation functions, and is especially crucial to support “over the top” IP based originating services. The LIS is the equivalent of the ALI Database in the new NENA i3 environment only it is much more.

When a call comes from a Carrier as shown below, it goes to the ESRP - Emergency Services Routing Proxy via the Session Border Controller (SBC). The ESRP queries the pre-populated LIS Database and, if needed, goes to the Mobile Positioning Center (MPC)/ Gateway Mobile Location Center System, or the VoIP Positioning Center System (VPC) to rebid and see if there is better location information. The ESRP queries the Server going into the ECRF the Emergency Services routing Proxy to determine which PSAP should handle the call. The ESInet gathers all relevant information sending the call with the data to the PSAP for answering. In the NG9-1-1 Network architecture, the PSAP equipment no longer is required to do the dip into the database.

Figure 3 - Database Flow

NG-911, Inc. is responsible for all functional aspects of database operations and will coordinate with the Access Providers to receive updates and maintain the database(s).

Text to 9-1-1 Flow

Session Border Controller


Page 14 of 41

Text to 9-1-1 will be implemented in DeKalb County and eventually across the NINGA footprint. Some technical capabilities for implementing Text to 9-1-1 are described at a high level in this document and referenced in the NENA Standards section and in the Network and Carrier Test Plan Documents.

NINGA and NG-911, Inc. the 911 SSP, have chosen Comtech TCS as their Text Control Company (TCC). The NENA Interim Standard which is being implemented best complements a full NENA NG9-1-1 Network, using an IP i3 SIP/MSRP interface to the ESInet and the NG9-1-1 NGCS equipment being deployed at NINGA. NENA provides instructions for the PSAPs and Carriers to complete the technical aspects of the project and register the PSAPs with the FCC.

The Design diagram in Figure 4 (below) represents the Carrier connectivity. The Diagrams, Network Test Plan and the Carrier Access Test Plan will reflect the requirements for Text testing with Wireless Carriers who are capable and participating in the Text Project.


Page 15 of 41

Figure 4 – NENA Interim Text to 9-1-1 Flow

Refer to NENA Interim SMS Text-to-9-1-1 Information and Planning Guide version 2 dated May 2014 available at www.NENA.org.

Access

Access traffic will be delivered for DeKalb County from all Carriers via the ESInet to reach the diverse duplicated Data Centers. Connectivity may be made through physical facilities terminating on the ESInet by connecting to the ESInet with a fiber connection at any suitable location where electronics are available along the Fiber Ring to a POI or into each Data Center to a POI, then integrated into the NGCS equipment. The iFiber equipment at that point of entry will allow the incoming 9-1-1 calls and/or tests to flow around the ring into the East or West Data Centers to be terminated in the same manner.

The NG9-1-1 SS7 STPs deliver the SS7 A Links into the Legacy Network Gateways (LNGs) to be converted to SIP Signaling before proceeding to the i3 NG9-1-1 PSAPs. The Legacy Trunks for SS7, ISDN-PRI, and MF terminate into the Legacy Network Gateways (LNGs) to be converted to SIP. Carriers with SIP Signaling send all calls and/or tests directly through the Session Border Controllers (SBCs) to the ESRPs for routing to the i3 PSAPs.

The size of the Access Carrier facilities and trunking are dependent on the volume of lines each Carrier must serve for 9-1-1. Roughly, for every 10,000 customers there are two (2) dedicated 9-1-1 trunks. As required by the ICC/Department of the Illinois State Police (ISP) there will be a minimum of two (2) trunks per legacy trunk group to achieve the Carrier Grade of Service (GOS) P.01 as prescribed by the ICC. Carriers may deliver their calls using copper or fiber facilities. If copper facilities, a minimum termination into the ESInet for each Data Center will be at a DS1 level.

Carrier Diagrams reflect the difference in call path if the calls are delivered by SS7 or Legacy Signaling than if delivered by SIP Signaling because the call flow is different from an access or trouble shooting perspective. At the time of filing almost all carriers will be using SS7, ISDN-PRI. A number of Carriers have identified themselves as ready for SIP signaling and those carriers access arrangements have been documented on the SIP Diagram. The telecommunication industry is constantly changing, especially in transport and signaling. Access Carriers operate on their own timetables and may change transport or signaling with minimum notice. The Carrier Diagrams are provided at a fixed point in time.

Carriers today have several trunk groups into the various NINGA footprint Selective Routers. All the Carrier traffic can be consolidated to two (2) facility routes with as many trunk groups as needed to reach the NINGA PSAPs for all eleven (11) Counties. This will create a more efficient Carrier Access Network while providing access diversity that is not in effect today. This design eliminates SPOF from end-to-end.

The exceptions are Carriers who share access through VPCs, MPCs and/or Resellers. Those Carriers share routing; they will have diverse paths if the Aggregators or Carriers provision them into


Page 16 of 41

the network. The VPCs/MPCs in the NINGA footprint include Bandwidth, Comtech TCS and West. Several Carriers choose to have Level 3 transport their traffic. Network Diagrams show the call flow for each type of carrier and their signaling.

Carriers have choices on how they provision and maintain diversity across their Access Network and size their facilities and trunking according to the engineering rules. Engineering rules include the request for Carriers to provide Load Balance. To accomplish this, all Carriers with Names starting with A through L (plus those Carriers whose names start with numbers) are asked to route first to DeKalb and then to Rockford. All Carriers with names M through Z are asked to route first through Rockford and then to DeKalb. The Access Test Plan will validate that the routing and load balance are in place.

Provisioning can take anywhere from 60 to 90 days from order to completion; the 911 SSP (NG-911, Inc.) is allowing up to 120 days on the timeline. Testing with Carriers can begin immediately following the completion of the provisioning process. Refer to the Access Test Plan.

Transfer Calls Out of the Network

In this document, NG9-1-1 PSAPS are called on-net PSAPs and Legacy PSAPs are called off-net PSAPs. For example, during a 9-1-1 call, the PSAP discovers the responsibility for call handling belongs to an adjacent PSAP. For DeKalb County, the call is transferred by the DeKalb County PSAP to an off-net Legacy PSAP using a Transfer solution documented in the Participating and Adjacent Agency form using the methodology described. The choices are varied from Radio to Call Relay to 10 Digit Administrative numbers to dedicated Trunking. When a County adjacent to DeKalb County becomes a part of a NG9-1-1 ESInet, any ESInet, transfers out of the PSAP’s jurisdiction will be done using the ESInet protocols and NGCS. Refer to the DeKalb Participating Agencies and Adjacent Agency documents for all details as prescribed by the ISP format. Initially Frontier, the existing 911 SSP for DeKalb County requested all transfers to be set up using 10 Digit numbers. Trunk Transfers may be implemented when Legacy Carriers are prepared to test and implement them. A one button transfer capability is built into the NGCS PSAP consoles.

Transfer Originates from County/ETSB

Transfer to County/ETSB

Transfer Process – Primary Today

Transfer Process at Adjacent County cutover – see forms for all other options

Effective Date

DeKalb Boone

10 Digit Number

One Button Transfer via ESInet with full ANI/ALI

When Boone joins the NINGA NG9-1-1 Network 2017

Kane 10 Digit Number One Button Transfer to 10

No change until Kane County joins an ESInet and ESInet to ESInet


Page 17 of 41

Digit Number connections are made.

Kendall

10 Digit Number

One Button Transfer to 10 Digit Number

No change until Kendall County joins an ESInet and ESInet to ESInet connections are made.

LaSalle

10 Digit Number

One Button Transfer to 10 Digit Number

No change until LaSalle County joins an ESInet and ESInet to ESInet connections are made.

Lee 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When Lee joins the NINGA NG9-1-1 Network

McHenry 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When McHenry joins the NINGA NG9-1-1 Network

Ogle 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When Ogle joins the NINGA NG9-1-1 Network

Winnebago 10 Digit Number/ One Button Transfer via ESInet with full ANI/ALI

When Winnebago joins the NINGA NG9-1-1 Network

*Note: Ogle and DeKalb ISP NG9-1-1 filings are scheduled for approximately the same time. The final sequence for ISP approval is not known as of this filing. Once the cutover is complete the ETSBs/Counties on the ESInet will be transferred On-Net to and from each other using the iFiber ESInet Network. The actual status will be shared with the ISP/ICC Staff prior to using an On-net transfer. Testing will be done to validate those transfers are working properly.

Transfer Calls into the ESInet

There are some cases where calls may be required to be transferred into the NG9-1-1 ESInet from a neighboring Legacy PSAP. Transfers to DeKalb County:

Transfer Originates from County/ETSB

Transfer to County/ETSB

Transfer Process Primary Today

Transfer Process – at Adjacent County at DeKalb Cutover – see forms for all

Effective Date


Page 18 of 41

other options

Boone DeKalb 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When Boone joins the NINGA NG9-1-1 Network

Kane 10 Digit Number One Button Transfer from 10 Digit Number

No change until Kane County joins an ESInet and ESInet to ESInet connections are made.

Kendall 10 Digit Number One Button Transfer from 10 Digit Number

No change until Kendall County joins an ESInet and ESInet to ESInet connections are made.

LaSalle 10 Digit Number One Button Transfer from 10 Digit Number

No change until LaSalle County joins an ESInet and ESInet to ESInet connections are made.

Lee 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When Lee joins the NINGA NG9-1-1 Network

McHenry 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When McHenry joins the NINGA NG9-1-1 Network

Ogle 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When Ogle joins the NINGA NG9-1-1 Network

Winnebago 10 Digit Number One Button Transfer via ESInet with full ANI/ALI

When Winnebago joins the NINGA NG9-1-1 Network

*Note: Ogle and DeKalb ISP/ NG9-1-1 filings are scheduled for approximately the same time. The sequence for ISP/ approval is not finalized as of this filing. Once the cutover is complete the ETSBs/Counties on the ESInet will be transferred On-Net to and from each other using the iFiber ESInet Fiber Network. The actual status will be shared with the ISP/ICC Staff prior to using an On-net transfer. Testing will be done to validate those transfers are working properly.


Page 19 of 41

2.0 Part 1325, Section 1325.205 (f) 2.1 Identify the 9-1-1 system providers. If multiple providers are being used, provide a detailed

description of each provider's role;

NG-911, Inc. is the sole 9-1-1 System Provider.

2.2 Explain what national standards, protocols, and/or operating measures will be followed;

National Emergency Number Association (NENA) standards will be followed. NG-911, Inc. has assembled the best NGCSs available from the vendors who comply with the NENA NG9-1-1 i3 standards. NG9-1-1 is an integrated standards based IP NENA solution. The DeKalb County NG9-1-1 network Design Plan conforms to the NENA Standards.

For a complete list of standards, please see the i3 standards references on the http://www.nena.org website.

The internal ESInet operates on SIP protocols. Access Carriers may retain their legacy access protocols they have in place today. The LNG will convert older existing protocols to SIP. The LSRG will handle Split Exchanges. The TCC will handle Texting and be fully integrated.

2.3 Explain what measures have been taken to create a robust, reliable and diverse/redundant network; and whether other 9-1-1 Authorities will be sharing the equipment.

The Design is based on building redundant systems to avoid any SPOF in the ESInet and across the entire NG9-1-1 Architecture. The NG9-1-1 system will provide flexibility in the routing of calls. The ESInet being deployed has all PSAPs connected and can route calls based on not only location, but also by availability. Currently, if a PSAP has only three (3) trunks from a legacy Selective Router, the (4) fourth caller gets a busy signal. In a Next Generation solution, that caller will be answered through intelligent routing. Additionally, there will be more available positions to answer calls because all connected PSAPs will be technically able to answer the call and will be able to dispatch or transfer the call to another PSAP. Refer to General Information 911. Routing methodology is documented in each Application. Based on the number of fixed and portable workstations per PSAP, not all PSAPs will back up each other in NINGA. The size disparity between PSAPs is one reason, and the ability to properly dispatch for one another is the second reason.

The hardware and software is expandable by installing additional components, such as servers, gateways and workstations as needed. The hardware is comprised of off the shelf servers and NENA compliant software. The Workstations used by the Call Takers are Dell computers, so there is not a barrier to replacing equipment if hardware fails.

If 9-1-1 calls are unable to be answered by the primary PSAP (for whatever reason), calls will be routed to the Backup PSAP designated in the 9-1-1 Plan. DeKalb County will utilize existing backup plans for the 1st layer of backup. The IP network allows flexibility to deliver overflow or re-routed calls to pre-determined Backup PSAPs. Calls can be routed to the Backup location through the software.

The key to network reliability is redundancy.

http://www.nena.org/


Page 20 of 41

The system will have automatic failover capability between the two Data Centers. Having two Data Centers to serve the PSAPs using the Emergency Services Internet Protocol Network (ESInet) will increase reliability 100%. The new NG9-1-1 system by design has redundancy built in at every point practical to eliminate all SPOF.

The NG9-1-1 ESInet is by design a reliable network. The factors that make it a good network during national security and emergency preparedness situations include:

• The dual Data Centers are more than 40 miles apart. • Duplicated capabilities of the NGCS within each Data Center. • Having a balanced load on the Data Centers with dual access requested of the Access

Carriers makes this a good plan in Disaster Recovery scenarios. Each PSAPs is backed up by one (1) or more PSAPs on separate call routes using separate power sources.

Security - Session Border Control

The SBC will act as a sophisticated firewall to protect the NG9-1-1 system from Denial of Service Attacks, malicious or accidental attempts that could cause ESInet network overload, and other intrusive security breach attempts. The SBC satisfies critical security, service assurance, and regulatory requirements and supports multiple protocols including SIP, H.323, MGCP/NCS, H.248 and RTSP and multiple border points.

A Session Border Controller (SBC) firewall is being installed in each of the Data Centers. The same system has been installed and tested extensively at the Illinois Institute of Technology Real Time Communications Laboratory (IIT RTCL) simulating loads well beyond what can be developed in the field.

Database Management Software

The software will enable NG-911, Inc. to manage the ALI database. The software fully integrates with the other NGCS of the NG9-1-1 system and performs data validation, request/response software, managing data quality and provides real-time communication tools. See 2.6 for more details

Map

The IP-based mapping system fully integrates with all the other components of the NG9-1-1 system.

IP Selective Router / Switch

The IP Selective Router equipment and software being deployed meets the redundancy and resiliency that is required by the NG-911, Inc. Additionally, the system has data integration and reporting tools

Monitoring


Page 21 of 41

The NG9-1-1, Inc. Monitoring solution captures call completion and other data in real time from relevant general-purpose and NG9-1-1 platforms from a wide variety of vendors and telecommunications equipment manufacturers. Algorithms sort through the data to capture and rapidly analyze only the information that applies to situations in which emergency calls are at risk of not being delivered. The rigorous analysis identifies emergency services call trouble areas, and rapidly identifies network failures and congestion points that may be interfering with these calls.

There are NG9-1-1 Network Operations Centers (NOCs) in three strategic places: NG9-1-1 has a main NOC with escalation policies and systems and processes. The NIU Data Center in DeKalb has a NOC which has personnel on duty 24 by 7 by 365 monitoring the health of the ESInet and the DeKalb Data Center. Tri Rivers has a 24 by 7 by 365 NOC in Rockford which monitors the health of the Rockford Data Center. The NG-911, Inc. monitoring system is connected to both Data Center NOCs to alert the NG9-1-1 24 by 7 by 365 NOC personnel to any problem with the Data Centers, the ESInet including Temperature and Power alarms and to alert on any NGCS in the secure collocation space. (Refer to Service Level Agreements in contracts with iFiber, NIU and TriRivers) Monitoring the systems and centers and network will be done during all phases of testing and ongoing after network cutover. Part of the monitoring is the alerting in near real time, the ability to ticket and/or display to systems centers and hand held devices.

Carriers have their own NOCs. NOC to NOC communications, alerting and cooperation on Critical, Major and Minor alarms is part of each Carrier’s connection agreement. The Carriers remain responsible for their own Access Reporting. NG-911, Inc. as the 911 SSP is accountable for the monitoring alerting problem resolution and reporting of all other aspects of the NG9-1-1 network.

2.4 Explain how the existing 9-1-1 traditional legacy wireline, wireless and VoIP network, along with the databases, will interface and/or be transitioned into the NG9-1-1 system.

Refer to the Network Diagram Exhibit B and associated spreadsheets for network information.

The NG9-1-1 system will handle 9-1-1 calls from all Carriers that are answered today plus Text to 9-1-1. The NG9-1-1 ESInet will enable a wide spectrum of users to utilize emergency support services, such as hearing impaired, deaf, speech impaired, and non-English speaking callers. The new system will incorporate the TTY technology that serves hearing and speech impaired end users.

The NG9-1-1 system fully integrates with a local ALI database management system as well as an integrated Mapped-ALI display. The ALI database management system (ALI DBMS) is Internet Protocol (IP)-based system, and for traditional wireline it calls operates exactly as the existing ALI.

DeKalb County is currently handling 9-1-1 Phase II wireless calls and this system will be as accurate in locating wireless callers as the current system. This NG9-1-1 solution will be in compliance with future standards and federal regulations for improved location capability as soon as those standards are in place commercially.

Dispatch to Participating and Adjacent Agencies Details of the elaborate dispatch system utilized by the PSAP is detailed in the Call Handling Intergovernmental Agreements. Details in said Agreements also cover all counties adjacent to DeKalb County:


Page 22 of 41

Access traffic will be delivered for DeKalb County through NG-911, Inc. NG-911, Inc. will aggregate Access Carrier traffic from Access Carrier offices and deliver it to the NG-911, Inc. Legacy Network Gateways (LNGs) in Rockford and DeKalb.

Calls will be routed by the NG-911, Inc. NGCS in the two (2) Data Centers onto the Fiber Network and routed to the proper PSAPs.

NG-911, Inc. converts the legacy protocols to SIP in the two (2) Data Centers. The Carriers know their 9-1-1 demand which in turn determines the size of each route from the Carrier trunk groups to the Data Centers. Each Carrier should comply with the required P.01 Grade of Service. which includes a minimum of two (2) trunks (or SIP equivalent) per group into each Data Center. This dual trunking will carry the full load should one Data Center or transport route completely fail.

ILECs will use their Legacy Selective Router(s) to access the NG9-1-1 Network for Split Exchange traffic where they are responsible to route the split calls. Where NG-911 is responsible to Split calls, they will send the calls outside the NINGA network to the adjacent Legacy Carrier Selective Router for completion until an ESInet to ESInet connection can be made. For DeKalb, this initially is to Frontier, AT&T and CenturyLink. Any changes in the connection of Carriers in the future will be documented by the 911 SSP when Diagrams are updated at the end of the year. Network Diagram Pages to address the Incumbent Local Exchange Carrier (ILEC), Regional Local Exchange Carriers (RLECs) and there are pages for the ILEC SR interfaces for return of traffic for split exchanges and a page for PS/ALI that are connected. Diagrams also include CLEC, Wireless, and VoIP Carriers, e2 Data links and PS/ALI Direct Customers; this includes signaling and routing.

NG-911, Inc. will ensure the Database records are received from the Access Carriers reviewed as they are today for location accuracy, accepted, validated and integrated into the active working records.

Most Wireline customer records come from the Service Order Process of the Carriers. The Carriers will transmit the database updates to NG-911, Inc. NG-911, Inc. will work closely with each Carrier directly on Database updates.

Split Exchange call handling records will be handled in the same manner. Service Order updates to the NG9-1-1 ALI records will be accomplished using database management software to process updates from all Carriers. See Figure 3.


Page 23 of 41

Figure 3 Database Management for Carrier Records

Carriers will provide ALI updates to NG-911, Inc. via a FTP site.

Directly connected PS/ALI will work in the same manner as the standard service order updates. The Next Generation System will accept ISDN-PRI and SIP trunking directly from the PS/ALI customer’s switch. NIU plans to initially connect via ISDN-PRI in Phase I Updates for directly connected PS/ALI will be sent via the same FTP site as the Carriers.

The ALI Database is hosted onsite in the two (2) Data Centers in the Database NGCS. The NGCS are duplicated and they reflect information that has been accepted, validated and aggregated and is ready to use in the 9-1-1 actual call flow. GIS coding will be added to all Service Order records that update the ALI. NG-911, Inc. will maintain the database in a manner that ensures that customer personnel cannot alter the data. All aspects of the ALI database process will meet NENA database standards. The Service Order updates that will be managed by NG-911, Inc. daily, will utilize multiple logic checks that guard against invalid ALI updates and increase the reliability of data. These invalid updates would include, but are not limited to, ensuring that the address conforms to public record including GIS ECRF data (MSAG) and that the ALI record telephone number is in a valid format. The database system supports direct service order entry, manual update as well as the import and export of NENA format.


Page 24 of 41

Steps to Test Database:

1. The 9-1-1 SSP obtains the DeKalb County ETSB ALI image copy from each Legacy 9-1-1 Access Carrier and/or directly connected PS/ALI Customer two weeks prior to live traffic being delivered to the NG9-1-1 System. This image copy is taken after the workweek’s updates have been processed to make the database as current as possible.

2. Updates will be sent daily (work day) from each Access Carrier directly to NG-911, Inc., as prescribed by the Commission, to update the database with the information sent from the Access Carriers.

3. Records that fail the database edits for syntax or formatting errors will be returned to the submitting Access Carrier for correction. Error records sent to Access Carriers and PS/ALI Customers will be tracked for resolution and completion.

4. After 10 days of running concurrent updates of the Legacy 9-1-1 Carriers’ and PS/ALI Customers databases with the identical updates processed into the DeKalb County database, the Legacy 9-1-1 provider will provide a current (updated) version of the ALI database that will be compared against the DeKalb County database that has been updated in parallel.

5. Discrepancies will be researched and resolved, depending on the situation, with the Legacy 9-1-1 SSP or the individual Carrier PS/ALI Customer that controls the records with the discrepancies.

6. Test results will be determined by reviewing the differences in the database on a record by record basis, based on update activity

7. When these tests are successful, NG-911, Inc. will continue to process the DeKalb County updates sent from the 9-1-1 Access Carrier until live traffic is successfully cut, beginning within days of successful database testing.

8. Once live traffic is cut the respective Access Carriers’ and PS/ALI Customers’ updates will be processed by to NG-911, Inc. daily.

2.5 Explain how split exchanges will be handled.

Local Exchange Telephone Companies send traffic from Split Exchanges to the primary 911 SSP per commercial agreements. Split exchanges in Telephone Company Central Offices are supported in the NG9-1-1 network architecture.

Split Exchanges agreements have a mutual responsibility clause. The 911 SSP who serves the most 9-1-1 lines from that Split Switch NPA NXX is generally responsible to accept all the calls and return the calls that are outside that 911 SSP’s PSAP boundaries. There are noted exceptions. In the NG9-1-1 Architecture the NGCS that performs the return routing function is the LSRG.


Page 25 of 41

The DeKalb County included Split exchanges:

DeKalb County Access Carrier

Split Exchanges in this application NPA NXXs

Split w ETSBs

Frontier Most lines Kane County

Frontier Splits and sends NG-911 portion from DKLBILXA4ED SR to the 2 Data Centers DKLBILAF0ED IPSR (Primary route) and RCFRILHX0ED IPSR (Alternate route); remaining to AT&T GENVILGNDS0 SR to complete to AT&T Kane County PSAP

2 Way Split

Maple Park MAPLILXARS0 Host: DeKalb

(815) 827 Kane County

AT&T PSAP

Frontier Most lines DeKalb County

(1)NG-911 Splits and sends AT&T Legacy portion from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to AT&T GENVILGNDS0 SR to complete LSRG to AT&T Kendall County PSAP

(2)NG-911 Splits and sends LaSalle County Legacy portion from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to DKLBILXA4ED SR to complete to the Frontier LaSalle PSAP

3 Way Split

Sandwich SNDWILXADS0 Host: Sandwich

(815) 786

(1) Kendall County

AT&T PSAP

(2)LaSalle County

Frontier PSAP


NG-911 Splits and sends Legacy portion from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to Frontier DKLBILXA4ED SR to complete to Frontier LaSalle County PSAP

Earlville ERVILIXARS0

Host: Sandwich

(815) 246 LaSalle County

Frontier PSAP


Page 26 of 41

2 Way Split. 1 Opted In

Frontier Most lines LaSalle County

Frontier Splits and sends NG-911 portion from DKLBILXA4ED SR to the 2 Data Centers DKLBILAF0ED IPSR (Primary route) and RCFRILHX0ED IPSR (Alternate route) to complete to Frontier LaSalle County PSAP

2 Way Split

Leland

LELDILXBRS0

Host: Sandwich


Frontier PSAP

Frontier Most lines Lee County; next Ogle County; next LaSalle County (Exception to Split Rule)

(1) NG-911 Splits and sends Lee County Legacy portion from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to CenturyLink DIXNILXADS0/9ED Lee County PSAP

When Lee joins the ESInet, calls route directly to Lee County from the NG-911 Data Centers either through the DKLBILAF0ED IPSR or RCFRILHX0ED IPSR

(2) NG-911 Splits and sends LaSalle County Legacy portion from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to DKLBILXA4ED SR to complete to the Frontier LaSalle PSAP

3 Way Split

Paw Paw PWPWILXARS0

Host: Sandwich

(815) 627 (1) Lee County

Splits resolved by ECRF/GIS on NG-911 ESInet 2017)

Starts as CenturyLink PSAP and becomes NG-911 NINGA PSAP

(2) LaSalle County

Frontier PSAP


NG-911 Splits and sends Legacy portion from Data Centers DKLBILAF0ED IPSR

Somonauk SMNKILXARS0

Host: Sandwich


Frontier PSAP


Page 27 of 41

or RCFRILHX0ED IPSR LSRG to Frontier DKLBILXA4ED SR to complete to LaSalle County PSAP

2 Way Split


NG-911 Splits and sends Lee County Legacy portion from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to CenturyLink DIXNILXADS0/9ED Lee County PSAP

When Lee joins the ESInet, calls route directly to Lee County from the NG-911 Data Centers either through the DKLBILAF0ED IPSR or RCFRILHX0ED IPSR

2 way Split

Shabbona SHBNILXARS0

Host: DeKalb

(815) 824 Lee County


Starts as CenturyLink PSAP and becomes NG-911 NINGA PSAP

Frontier Most lines DeKalb County - 3 lines in Ogle; Boone opted to DeKalb

NG-911 Splits and sends Ogle County from Data Centers DKLBILAF0ED IPSR or RCFRILHX0ED IPSR LSRG to complete through the Frontier DKLBILXA4ED to the Frontier Ogle County PSAP

When Ogle joins the ESInet, calls route directly to Ogle County from the NG-911 Data Centers either through the DKLBILAF0ED IPSR or RCFRILHX0ED IPSR

2 Way Split; 1 Opted In

Kirkland KRLDILXARS0

Host: Sycamore

(815) 522 Ogle County


Starts as Frontier PSAP and becomes NG-911 NINGA PSAP


Page 28 of 41

1. DeKalb County Split Exchanges that are Opted Out:

DeKalb County Access Carrier Split Exchanges Opted Out 815 NPA NXXs

Frontier Belvidere (815) 544, 547 to Boone – Future ESInet ECRF/GIS Routing

Frontier Creston (815) 384 to Ogle – Future ESInet ECRF/GIS Routing

Frontier Monroe Center (815) 393 to Ogle – Future ESInet ECRF/GIS Routing

AT&T Hampshire (847) 683 to Kane – Off net with no ESInet interface Planned as of Filing

Note: Where Opted Out to future NINGA NG-911 Counties, GIS Boundaries remains intact; Testing is Required to assure the NG-911 Dispatch and Routing are intact after Boone and Ogle cut to the network.

b. DeKalb County Split Exchanges that are Opted In:

DeKalb County Access Carrier Split Exchanges Opted In 815 NPA NXXs

Frontier Genoa (815) 784 from Boone County – Future ESInet ECRF/GIS Routing

Frontier Kirkland (see split with Ogle which remains)

(815) 522 from Boone County - – Future ESInet ECRF/GIS Routing

Frontier Earlville (See Split with LaSalle which remains)

(815) 246 from Lee County - – Future ESInet ECRF/GIS Routing except LaSalle

Note: Where Opted In from future NINGA NG-911 Counties. GIS Boundaries remain intact; Testing is Required to assure the NG-911 Dispatch and Routing are intact after Lee and Boone cut to the network.

2.6 Explain how these databases will be maintained and how address errors will be corrected and updated on a continuing basis;

A new 9-1-1 ALI database will be created by collecting records from all wireline, wireless and VoIP providers who offer service that allows customers to reach 9-1-1. There is no intention to transition existing 9-1-1 ALI databases to the new Next Generation 9-1-1 database(s). Instead, Carriers will be expected to provide a fresh/scrubbed load of ALI records for each of their customers per Title 83: Public Utilities Chapter I: Illinois Commerce Commission Subchapter f: Telephone Utilities Part 725 Standards of Service Applicable to 9-1-1 Emergency Systems Section 725.410 Telecommunications Carriers (J) (1) through (3).

The NINGA Members will transition the existing MSAG(s) into a new MSAG for the NINGA Members and that MSAG will be provided on request.


Page 29 of 41

Database Management software will enable NG-911, Inc. to manage the ALI database. The software fully integrates with the other NGCS of the NG9-1-1 system and performs data validation, request/response software, managing data quality and providing real-time communication tools.

NG-911, Inc. will ensure the Database records are received from the Access Carriers reviewed as they are today for location accuracy, accepted, validated and integrated into the active working records.

Carriers and PS/ALI Customers will provide ALI updates to NG-911, Inc. via a FTP site.

PS/ALI will work in the same manner as the standard service order updates. If the PS/ALI customer is connected to another Carrier, updates to PS/ALI records will be included with other service order updates from that Carrier. There is one (1) direct connected PS/ALI customer(s) identified by Frontier at the time of filing, but if there are directly connected PS/ALI customers, updates will be sent via the same FTP site as direct connect carriers. NIU has (815) 752 and 753 with ~5500 lines in their DMS100/CS2100 Switch. They will connect to the Network using ISDN PRI and the ESInet and provide Database updates via FTP server ongoing to the NG9-1-1 Database site.

The ALI Database is hosted onsite in the two (2) Data Centers in the Database FEs. They are duplicated and they reflect information that has been accepted, validated and aggregated and is ready to use in the 9-1-1 actual call flow.

GIS coding will be added to all Service Order records that update the ALI.

NG-911, Inc. will maintain the database in a manner that ensures that customer personnel cannot alter the data. All aspects of the ALI database process will meet NENA database standards.

The Service Order updates that will be managed by NG-911, Inc. daily, will utilize multiple logic checks that guard against invalid ALI updates and increase the reliability of data. These invalid updates would include, but are not limited to, ensuring that the address conforms to public record including GIS ECRF data (MSAG) and that the ALI record telephone number is in a valid format. The database system supports direct service order entry, manual update as well as the import and export of NENA format.

The system will provide automatic location identification (ALI), automatic number identification (ANI), and selective routing to the PSAP. In addition, the system will feature geo-spatial, policy based functionality that will deliver superior service and response to the emergency needs of the citizens of DeKalb County. Every structure in DeKalb County has been identified and every residence has a street number with a street and road name. Additionally, geo-spatial number has been designed with address points to identify the residence or business where the 9-1-1 request is made. All database elements comply with NENA Data Formats for ALI, MSAG and GIS.


Page 30 of 41

2.7 Explain who will be responsible for updating and maintaining the data, at a minimum on a daily basis Monday through Friday.

The Service Order updates that will be managed by NG-911, Inc. daily, will utilize multiple logic checks that guard against invalid ALI updates and increase the reliability of data. These invalid updates would include, but are not limited to, ensuring that the address conforms to public record including GIS ECRF data (MSAG) and that the ALI record telephone number is in a valid format. The database system supports direct service order entry, manual update as well as the import and export of NENA format.

All ALI delivery/updates and corrections will be accomplished via electronic transmittal. NG-911 Inc will accept all updates from the carriers, and after review by the system, will update and maintain the NG9-1-1 databases for all of NINGA. The ETSB Managers and their GIS Coordinators are responsible to maintain the County Boundaries, format of the records and the addition or changes in Street Addresses or other major features of the physical geography over time. Housing additions and road additions for example will be updated by the ETSBs into the system.

2.8 Explain what security measures will be placed on the IP 9-1-1 network and equipment to safeguard it from malicious attacks or threats to the system operation and what level of confidentiality will be placed on the system in order to keep unauthorized individuals from accessing it.

Security for IP based NG 9-1-1 is comprised of physical and logical layers. The locations of each data center have physical security layers, which include but not limited to: secure entry, limited access entry and video/audio recordings.

All calls and network users are authenticated for security reasons by a set of protocol parameters in the SBC(s). Calls are routed based on location. Being IP-based, the system is very flexible and can route calls based on network and/or PSAP access conditions, using database rules that can be set and are controllable.

The software components of the system have logical security i.e., Login and Password. Passwords will be controlled by the Data Center administrators and limited to IT staff. All employees that work with the equipment will have their own passwords and the log-ins will be recorded at time of log-in and log-off.

The Session Border Control (SBC) or sometimes called the Border Control Function (BCF) will act as a sophisticated firewall to protect the NG9-1-1 system from Denial of Service Attacks, malicious or accidental attempts that could cause ESInet network overload, and other intrusive security breach attempts. The SBC satisfies critical security, service assurance, and regulatory requirements and supports multiple protocols including SIP, H.323, MGCP/NCS, H.248 and RTSP and multiple border points.

All 9-1-1 calls will pass through the SBCs located in both Data Centers to avoid overload and malicious attacks.


Page 31 of 41

All calls and network users are authenticated for security reasons. Calls are routed based on location. Being IP-based, the system can route calls based on network and/or PSAP access conditions, under database rules set and controllable.

The software components of the system have logical security i.e., Login and Password. Passwords will be controlled by the Data Center administrators and limited to IT staff. All employees that work with the equipment will have their own passwords and the log-ins will be recorded at time of log-in and log-off.

All employees, including IT staff, employees and custodial employees, are required to carry departmental identification.

See below Figure 4 for Direct Connect and Indirect Security Configuration. DeKalb has no indirectly connected Carriers.

Figure 5 Security for Carriers.


Page 32 of 41

Additional Information:

Quality of Service Standards

NG-911, Inc. and DeKalb County will utilize the Commission’s service standards for call blocking and will provide the required P.01 level of service at a minimum. Call set up will remain the same or improve with the use of SIP signaling. Since the NG9-1-1 Architecture doesn’t rely on copper lines, inbound traffic is not limited by physical trunks. The NG9-1-1 Architecture will allow more calls to be answered once they are sent from the Access Carriers’ offices. SS7 is the dominant Access signaling into the ESInet by carriers. TNS is the SS7 provider for NG-911, Inc. Over time SS7 is replaced by SIP as Access Carriers upgrade their networks.

SLAs will be in place with Carriers and vendors.

The ESInet provider including Data Center providers have Service Level Agreements (SLAs) in place with NG9-1-1, Inc. Bandwidth and availability are part of the SLAs over the ESInet and to each PSAP. Refer to the Legal Agreements between NG9-1-1 Inc and iFiber for transport and NIU and TriRivers for colocation. Refer to the TNS Agreement for SS7 Signaling where required.

Test Plans.

Extensive written test plans are part of this modified plan filing. The test plan thoroughly explains how the operation of the network, routing and database accuracy will be verified. NG-911, Inc. and DeKalb County will oversee all aspects of testing the NG9-1-1 System and will be directly involved with The Network Test Plan. Testing with Carriers and directly connected PS/ALI Customers is described in detail in the Carrier Test Plans. DeKalb County will coordinate call through testing for each wireline end office. NG-911, Inc. will obtain from the Access Carriers, test numbers per wire center, per rate exchange, per class of service as appropriate. Phase I and II PS/ALI Customer testing is described in the Test Plans. The Network Diagrams show which carriers will route through the DKLBILXA4ED DeKalb Selective Router in Phase I and the carrier that will route directly.

DeKalb County will work with NG-911, Inc. to conduct coordinated testing with the telecommunications carriers when any of the following occur:

• New central office switching installations that affect the directly connected carrier(s) • Network router, Selective Router or functional equivalent installations, upgrades or rehomes; • NPA (Numbering Plan Area) additions • Any other event that affects 9-1-1

DeKalb County will perform coordinated testing with private residential or business switch operators who request/require such testing.

Initial Cutover Strategy

Initial Cutover Strategy will be cooperative with Carriers.


Page 33 of 41

The Cutover Plan will validate the translations in the network are operational for primary, alternate and disaster situations to ensure the proper response gets to the PSAP even if the network is overloaded.

Cutover will occur Carrier-by-Carrier in the mutually agreeable Carrier and PSAP maintenance window for 9-1-1 services. The process includes:

• Optimization of physical and logical routes • Circuit ordering process outlined and confirmed • Field Testing resulting in Cutover Ready Transition • Agreement on Primary and Alternate Routing Rules • Agreement on Split Exchange Routing and Interfaces • Translations for Load Balance and Routing in the Carrier Network • Sharing of Carrier Test Numbers • Addition of Carrier Test Numbers into the NG9-1-1 Database Records • Selective Router trunking to Data Centers • Originating Rate Center (NPA-NXX) to PSAP • Verify PSAP before and after Dispatch • Make Access Trunks Busy and Verify Load Balance • Log off workstations and verify Primary / Alternate PSAP

Traffic will be live after all steps are complete.

See Exhibit C for Cutover Methods and Procedures.

The legacy network will be available for seven days after successful cutover of the NINGA end to end network. DeKalb County’s ETSB plans to cut to live service after successful network and field testing.

When all tests are successful, the first access traffic load will be delivered to the appropriate PSAP/PSAPs in accordance with the deployment schedule. Include the deployment schedule. Subsequent migration will occur as specified in the deployment schedule.

Disaster Recovery

The NG9-1-1 ESInet is by Design a reliable network. The factors that make it a good network during national security and emergency preparedness situations include:

1. The dual Data Centers in DeKalb and Rockford are more than 40 miles apart. 2. Duplicated capabilities of the NGCS within each Data Center. 3. Having a balanced load on the Data Centers with dual access requested of the Access

Carriers makes this a good plan in Disaster Recovery scenarios. Manual switchover to a Disaster Recovery PSAP often requires staffing and physical switching over to a configuration that is only tested occasionally.

Access Carriers will connect in a way that supports Disaster Recovery principles.

1. Dual Trunking


Page 34 of 41

2. Alternate Facilities Routes 3. Commercial Agreements for service quality, problem identification and resolution. 4. Monitoring tools to see problems that are simplex in nature and get them rapidly corrected

before they become service affecting for customers trying to reach 9-1-1.

Business Processes are Critical to Disaster Recovery Principles.

1. Planning for Disasters in the ongoing design, engineering and during growth of the network. 2. The need for good records exchange with Carriers, Methods of Procedures for work activities

signed off and communicated ahead of a planned event. 3. Use of Maintenance Windows that are strict before any change is made to the network. 4. Proper staffing and coverage and a call out plan for emergencies. 5. Training on the NGCS and on processes and procedures. 6. Communications capabilities using the IP PBX. 7. Use of Conference Bridges and other means of communications during cutovers, planned

major activities and during major outages or emergencies. Radios etc. 8. Documented Disaster Plans in case of natural disasters such as earthquakes, floods,

tornadoes, electrical grid problems, prison breaks, plane crashes, bomb threats and physical and cyber-attacks on the Data Centers and more.

9. Testing of Scenarios planned and unplanned, exercises involving staged incidents. 10. Offers to participate with Access Carriers, during their annual Disaster Recovery exercises. 11. Use of Best Practices in password protection and physical and logical security

protection. Note: FCC provides industry Best Practices. FCC CSRIC includes NG9-1-1. www.fcc.gov.

12. Session Border Controllers (SBCs) to prevent, thwart and alert for unwarranted attacks on the network.

13. Facility diversity where possible and uninterrupted power supply (UPS) and generators to ensure the system can run indefinitely. In event of commercial power failure, UPS systems and generators will be utilized until electrical service is restored.

14. Grounding of the Data Centers to industry requirements. 15. DeKalb County will comply with NENA standards and sound Information Technology policy. 16. Standard procedures to maintain telephony and computer equipment will be utilized, including

HVAC and other environmental controls to ensure optimum conditions for the ongoing function of the hardware.

If PSAPs must abandon a physical site, the calls can be rerouted to other PSAPs in real time through changes in software and tables.

DeKalb County’s system is resilient and fault tolerant. The failure of individual components, such as Local Exchange End Offices, will not bring the NG9-1-1 system down because the components utilized in the NG9-1-1 system are geographically diverse and the network is designed for redundancy and resiliency.

http://www.fcc.gov/

Page 35 of 41

Exhibit A

Figure 1 – NENA Call Flow Diagram


Page 36 of 41

Exhibit B

Figure 2 – NINGA ESInet with Connectivity and Power;


Page 37 of 41

Exhibit C Cut Over Method and Procedure

GENERAL MOP DESCRIPTION: DeKalb County PSAP cut over 1. Set – Up and Preparation Carrier Trunks have all been installed and tested. NG-911, Inc. PSAP equipment and Data Center hardware has been installed and

tested. This is the procedure to cut live traffic to the Next Generation 9-1-1 system installed by NG-911, Inc. 2. PSAP Cut Over The plan is to cut one PSAP at a time. Start at 10:00 AM on MM/DD/YY

1. Monitoring apps (Wireshark and other apps) in place to assist with trouble shooting

2. Position personnel as required

3. Set up the bridge and bring in each tester

4. Test existing network to existing PSAP to verify that works

5. Change translations at the carrier switch

6. Use Maintenance Bridge to bring in necessary parties and trouble shoot

7. Make Test Calls

8. Verify Primary and Alternate Load Balance at ESRP is working

9. Verify TTY on the LEC lines

10. Verify voice quality is clear, no echo noise or quality issues. Test and resolve before closing.

11. Document details

12. Repeat steps 2 through 13 each Carrier Cutover.

Wireline Carrier Cut (ILEC)

The legacy SR routes and SR interfaces will be tested first then the rest can follow. Wireline ESNs for DeKalb County Sheriff Office

ESN PSAP Wireless / Notes


Page 38 of 41

VoIP xxx DeKalb County Sheriff VoIP xxx DeKalb County Sheriff Wireless xxx DeKalb County Sheriff Wireline

Once the ESN’s are all cut over, NG-911, Inc. and DeKalb County personnel will make test calls from pre-designated test numbers listed in Attachment 1 to ensure correct call routing. The split exchanges will need to be tested to ensure proper routing of calls to DeKalb County. NG-911, Inc. will monitor calls and ensure proper call routing and delivery. The DeKalb PD will be cut the same day as the Sheriff’s Office xx/xx17 Wireline ESNs for DeKalb PD

ESN PSAP Wireless / VoIP

Notes

xxx DeKalb PD VoIP xxx DeKalb PD Wireless xxx DeKalb PD Wireline

Once the ESN’s are all cut live, NG-911, Inc. and DeKalb County personnel will make test calls from pre-designated test numbers to ensure correct call routing from both wireline and wireless calls. NG-911, Inc. will monitor calls and ensure proper call routing and delivery. Wireless Carriers:

Once the wireline carrier(s) are cut over, Wireless Carriers will be cut next. Wireless carriers will be cut one at a time in alphabetical order. The first carrier will be asked to cut their traffic to the new system. Test calls will be generated to ensure a successful cut. Once that is successful the remaining carriers will be cut live to the new system. VoIP MPC/VPC Carriers:

After all the wireless carriers are cut live, the VoIP carriers will be cut next. VoIP and MPC/VPC carriers will be cut in a predetermined order that will be published before the cut. The first VoIP/ MPC/VPC carrier will be asked to cut their traffic to the new system. Test calls will be generated to ensure a successful cut. Once that is successful the remaining carriers will be cut live to the new system DeKalb County personnel will make test calls from pre-designated test numbers to ensure correct call routing from both wireline and wireless calls. NG-911, Inc. will monitor calls and ensure proper call routing and delivery.


Page 39 of 41

3. Database SOI Updates – Ongoing

The database has been loaded and tested. The daily SOI files have been processed for several weeks. MSAG changes are being delivered to carriers via the predetermined methods established. Once each PSAP is cut live and test calls are made, NG-911, Inc. and DeKalb County will ensure that ALI information is displayed on the PSAP workstations and that wireless calls are handled correctly (i.e. sent to a third-party West/ComTech/Bandwidth) and display correctly on the workstations. All calls where “No Record Found” occurs will be investigated.

4. Work schedules, a. PSAPs will be cut during the week day from 10:00 AM CT – 3:30 PM CT. This will accommodate the PSAP with traffic being

historically the lowest during these times. This increases the probability that sufficient experienced personnel being available. b. Special schedule arrangements or work conditions: In the event of severe weather or another event that would cause large volumes of

9-1-1 traffic, the cut over team will evaluate the practicality of cutting the PSAP that particular day. The 9-1-1 Director will have the final call to proceed with the cut on any particular day.

5. Technical documents, IP Addresses: a. IP Addresses have been provided. SIP trunks have been tested and accepted.

6. Delivery, storage and staging of equipment a. All Equipment is installed and tested: b. Access to buildings must be arranged in advance with the 9-1-1 Director and each Access Carrier as required.

7. Other pertinent items: Vendors have been notified of the cutover and are on call as needed.


Page 40 of 41

Contact Information (Illustrative Contact List)

Contact Name Company Function Number

Technical Bridge TBD Dial-in (605) 475-3220 Code: 1096980#.

Admin Bridge If necessary

. Conference ID: 5xxxxxxx

303-928-xxxx

Travis Stender NG-911, Inc. Technical 319-350-8430 Randy Rampersad NG-911, Inc. Technical 319-430-0611 Michael Ramsey NG-911, Inc. Technical 319-430-1670 Bart Lovett NG-911, Inc. PM 314 602 3399 Frontier

Communications PM

Frontier Communications

Technical

Limited requirement DeKalb

AT&T PM

AT&T Technical Limited Requirement DeKalb

CenturyLink PM

CenturyLink Technical as needed TNS SS7 Technical as needed Comtech

TCSTCC Technical

NIU and Tri-Rivers

Technical

Glenna Johnson DeKalb County E PSAP – D/B (815) 899-4559 iFiber Direct Carrier

Translations (618) 294-8034

Carriers 1-n


Page 41 of 41

Cutover at the PSAP

Change out half of the work stations

• Verify New Trunk Groups are Active

• Reroute originating translations to the new ESInet trunk groups

• Place 9-1-1 test calls over new route configuration

• Verify appropriate PSAP answers and verify location information

• Execute complete 9-1-1 test plan following.

• Determine the performance of the Split exchange routing if applicable, test them before and validate them during cutover.

• Verify Transfers In and Out are Operational.

If a service interruption occurs:

1. Cease all work operations immediately.

2. Local NG-911, Inc. and carriers as required shall be notified of outage details immediately.

4. Provide a written report/call to ICC as needed.

Back Out Plan

1. The existing E9-1-1 Trunks will be in place. 2. Carriers change switch translations back, 3. Reinstall the old work stations. 4. Retest E-911

Existing 9-1-1 Trunks

1. The existing E9-1-1 Trunks need to be left in place for 7 days after the PSAP is cut.

2. The E9-1-1 Trunks should be disconnected eight (8) calendar days after the cut date with the exception of the Legacy SR interfaces for Split Exchange Routing.

FINANCIAL INFORMATION

Annual recurring 9-1-1 network costs prior to modification $ _________________________

Projected annualrecurring 9-1-1 network costs aftermodification $ _________________________

Installation cost of the project $ _________________________

Anticipated annual revenues $ _________________________

Five Year Strategic Plan DeKalb County ETSB

The DeKalb County ETSB is a leader and participant in the eleven-county Northern Illinois Next

Generation Alliance (NINGA), an ongoing effort to provide consolidated Next Generation 911 to

all existing PSAPs in our eleven-county region. The DeKalb County ETSB has had the foresight

and ability to save money for this project over the past several years, and is in appropriate fiscal

condition to be able to completely fund the DeKalb County portion of this project, including

installation of Next Generation 911 to both DeKalb County PSAPs.

The Five year plan for DeKalb ETSB is to utilize the existing contract with NG-911, Inc. for the

hosted Next Generation 9-1-1 solution proposed in this plan. This system is compliant with the

legislative mandate of being Next Generation 911 by 2020. DeKalb County anticipates going

live in the 3rd Qtr. 2017.

The DeKalb County ETSB will implement Interim Text to 9-1-1 along with voice to 9-1-1 with the

other 11 NINGA counties, and may incorporate video and static images in the system in the

next five years if NENA standards are finalized and the benefits are tangible.

The DeKalb ETSB will continue to look for efficiencies in operations over the next five (5) years

and ways to improve service to the citizens and maintain or reduce expenditures. With Next

Generation 9-1-1, DeKalb County will have increased reliability with the fully diverse solution

from a network perspective. DeKalb has purchased the capability to activate remote 9-1-1

workstations in the event of area wide or localized situations causing greater than normal

demand for 9-1-1 service thus improving safety for citizens of DeKalb County.

Financial projections indicate a further decline in wireline revenue and flat to moderate growth in

wireless and VoIP surcharge. The DeKalb ETSB expects operating cost to remain flat over the

next five years.

DeKalb has budgeted for capital expenditures for peaks and valleys as equipment became

manufacture discontinued or broke down for the current 911 System. This will be smoothed out

and predictable since the hosting party will be responsible for all upgrades and maintenance of

the shared core system. Upgrades are shared by all NINGA members.

The system is robust and other Counties may choose to join NINGA, such as Carroll did after

the original contracts were signed. Revenue from added members will accrue to all members

from a onetime membership fee and any contributions to common maintenance and ongoing

costs will be shared through NINGA membership.

Five Year Strategic Plan DeKalb County ETSB

During this change to NG 9-1-1 DeKalb County ETSB will also be consolidating to two PSAPs.

Sandwich Police Department and Northern Illinois Police Department will no longer receive 9-1-

1 calls direct. With the reduction in PSAPs DeKalb Police Department will increase their

positions to six from four. At an expense to DeKalb County ETSB they have purchased two

remote 9-1-1 positions that could be used in their Command Post for large incidents or if a

PSAP is disabled for a long period of time.

Communities Served DeKalb

August 2017 Final

1

County: DeKalb COMMUNITIES SERVED

Provide a list of all communities to be served by the proposed 9-1-1 System. Please include the name of the community and the official mailing address including street address, city and zip code.

City, Town, or Village Street Address, City, Zip Code Belvidere 123 S. State St, Belvidere, IL 61008 DeKalb 700 N.7th St,, DeKalb, IL 60115 Earlville 99 East St, Earlville, IL 60518 Genoa 317 E. Railroad Ave, Genoa, IL 60135 Hinckley 911 N. Sycamore St., IL 60520 Kirkland 3891 IL-72, Kirkland, IL 60146 Lee 103 Lee Rd, Lee, IL 60530 Leland 145 E, Railroad Dr., Leland, IL 60531 Malta 308 Jefferson St., Malta, IL 60150 Maple Park 305 S. County Line Rd., Maple Park, IL 60151 Monroe Center 104 West St., Monroe Center, IL 61052 Paw Paw 244 Elizabeth St., Paw Paw, IL 61353 Sandwich 310 E. Railroad St., Sandwich, IL 60548 Shabbona 105 E, Navaho Ave, Shabbona, IL 60550 Sycamore 112 W, Elm St, Sycamore, IL 60178 Waterman 160 N. Cedar St., Waterman, IL 60556 Hampshire 202 Washington Ave, Hampshire, IL 60140 Note: DeKalb Community Addresses are from the Fire Departments

Participating Agencies August 2017 Final

1

County: DeKalb PSAPs: DeKalb County Sheriff Department; DeKalb Police Department; Sandwich Police Department; NIU Police Department

PARTICIPATING AGENCIES Provide a list of public safety agencies (Police, Fire, EMS etc.) that are to be dispatched by the 9-1-1 System. Each Agencies land area(s) in square miles and estimated population which will have access to the proposed 9-1-1 System. Do not forget to include County Sheriff’s jurisdiction and Illinois State Police Districts. Each agency that appears on this list should also have signed a call handling agreement. 9-1-1 Participant Agencies

Street Address, City, Zip Code

Administrative Telephone No./Contact

Direct Dispatch

Transfer Call Relay

Agency Land area(s) in square miles

Estimated population

Cortland Fire Department, DeKalb County, IL

30 West North Ave, Cortland IL 60112

(815) 756-2545 Chief Moser

153.485 36 4270

Cortland Police Department, DeKalb County, IL

250 S. Halwood St., Cortland IL 60112

(815) 756-2558 Chief Dargis

154.86 36 4270

DeKalb County Sheriff's Police, DeKalb County, IL

150 N. Main St. , DeKalb IL 60178

(815) 895-2155 Sheriff Scott

154.86 638 105,160

DeKalb Fire Department, DeKalb County, IL

700 N. 7th St, DeKalb IL 60115

(815) 748-8460 Chief Hicks

154.070 55 45,000

DeKalb Police Department, DeKalb County, IL

700 W. Lincoln, DeKalb, IL 60115

(815) 748-8400 Chief Lowery

155.250 55 45,000

Earlville Ambulance, DeKalb and LaSalle County, IL

125 East St., Earlville, IL 60518

(815) 246-2448 Chief Todd

815-246-8341 6 24

Earlville Fire Department, DeKalb and LaSalle County, IL

99 East St, Earlville, IL 60518

(815) 246-7095 Chief Todd

815-246-8341 6 24

Genoa/Kingston Fire/Rescue Department, DeKalb County, IL

391 Railroad St, Genoa, IL 60135

(815) 784-5131 Chief Kozlowski

154.070 72 8500

Genoa Police Department, DeKalb County, IL

333 E. First St., Genoa, IL 60135

(815) 784-2526 Chief Smith

154.800 2.6 5000

Hampshire Fire Department, DeKalb and McHenry County, IL

202 Washington Av, Hampshire, IL 60140

(847) 683-2629 Chief Robinson

(708) 232- 8400

6 34

Hinckley Fire 105, N. (815) 286-7711 153.485 64 2500


2

9-1-1 Participant Agencies



Direct Dispatch

Transfer Call Relay



Department, DeKalb County, IL

Main ST, Hinckley, IL 60520

Chief VanLanduyt

Hinckley Police Department, DeKalb County, IL

700 James St, Hinckley, IL 60520

(815) 286-7282 Chief Everhart

154.86 64 2500

Kingston Police Department, DeKalb County, IL

101 N. Main St, Kingston, IL 60145

(815) 784-5572 Chief Ayala

154.86 1.02 1164

Kirkland Fire Department, DeKalb County, IL

3891 State Route 72, Kirkland, IL 60146

(815) 522-4414 Chief Stott

153.485 77 2800

Kirkland Police Department, DeKalb County, IL

511 W. Main St, Kirkland, IL 60146

(815) 522-3315 Chief Lindstrom

154.86 77 2800

Lee Fire Department, DeKalb County and Lee County, IL

103 Lee Rd., Lee, IL 60530

(815) 824-2120 Chief Galbreath

153.485 10 225

Leland Fire Department, DeKalb and LaSalle County

145 E. Railroad, Leland, IL 60531

(815) 495-3342 Chief Hecathorn

153.485 36 200

Maple Park Fire Department, DeKalb County and Kane County, IL

305 E. County Line Rd, Maple, IL 60151

(815) 827-3500 Chief Peterson

(708) 232- 8400

22 500

Maple Park Police Department DeKalb County and Kane County, IL

302 Willow St., Maple Park, IL 60151

815 827 3286 Chief Walker

(708) 232- 8400

22 500

Malta Fire Department DeKalb County, IL

308 Jefferson St. Malta, IL 60150

(815) 825-2165 Chief Beyhof

153.485 22 2000 3500 Students

Malta Police Department, DeKalb County, IL

115 S. 3rd St., Malta, IL

(815) 825-2200 Chief Walker

154.86 22 2000 3500 Students

NIU Police Department, home based DeKalb County, IL – All calls outside DeKalb go to the specific county, DuPage or Naperville etc.

375 Wirtz Dr., DeKalb, IL 60115

(815) 753-1212 Chief Phillips

155.250 756 acres ~ 22,000 Students ~ 5500 lines

Sandwich Fire Department, DeKalb County, LaSalle,

310 E. Railroad St., Sandwich,

(815) 786-9241 Chief Pruski

154.190 27 10,000


3




Direct Dispatch

Transfer Call Relay



Kendall, IL IL 60548 Sandwich Police Department, DeKalb County, LaSalle, Kendall, IL

308 E. College St., Sandwich, IL 60548

(815) 786-7261 Chief Bianchi

460.550 27 7509

Sandwich Ambulance, DeKalb County, IL

101 W Center St, Sandwich, IL 60548

(815) 786-9241 Chief Pruski

155.805 27 10,000

Shabbona Fire Department, DeKalb County, IL

103 E. Navaho. Shabbona, IL 60550

(815) 824-2888 Chief Ottenheigme

154.86 42 700

Somonauk Fire Department, DeKalb County and LaSalle County, IL

145 W. DeKalb St, Somonauk, IL 60552

(815) 498-2218 Chief Colford

153.485 24 1800

Somonauk Police Department DeKalb County and LaSalle County, IL

131 Depot St, Somonauk, IL 60552

(815) 498-2351 Chief Smith

154.86 2.42 1893

Sycamore Fire Department DeKalb County, IL

535 W. DeKalb Av, Sycamore, IL 60178

(815) 895-4514 Chief Polarek

153.485 63 17,800

Sycamore Police Department, DeKalb County, IL

535 DeKalb Av. Sycamore, IL 60178

(815) 895-3435 Chief Theriault

154.86 10 17,800

Waterman Fire Department, DeKalb County, IL

160 N. Cedar, Waterman, IL 60556

(815) 264-3284 Chief Lave

153.485 58 1800

Waterman Police Department, DeKalb County, IL

150 N. Cedar , Waterman, IL

(815) 264-3574 Chief Breese

154.86 58 1100

Burlington Fire Department, Kane County, IL

154 South St, Burlington, IL 60109,

(847) 683-2199 Chief Whyte

(708) 232- 8400

4 6

Elburn Countryside Ambulance, Kane County, IL

200 E Route 38, Elburn, IL 60119

(708)-365-9226 Chief Hall

(708) 232-8400

22 500

No State Police inside county


4




Direct Dispatch

Transfer Call Relay



37 agencies. 3 Counties

.

Adjacent Agencies August 2017 Final

1

County: DeKalb

PSAP(s): DeKalb County Sheriff Office and DeKalb Police Department

ADJACENT AGENCIES LIST Provide a list of public safety agencies and existing 9-1-1Systems that are adjacent to the proposed system’s boundaries. Each agency that appears on this list should also have signed a call handling agreement and/or aid outside jurisdictional boundaries. Agency/County/State Street Address,

City, Zip Code Telephone Number/Contact Transfer/Process

Boone Co Sheriff, Boone County, IL

615 Main St, Belvidere, IL61008

(815) 544-9322 PSAP Center/ Sheriff Dave Ernest

10 Digit Transfer (815) 544-2144 via ESInet Date TBD

Boone Co Rural Fire, Boone County, IL

1777 Henry Luckow Lane, Belvidere, IL 61008

(815) 544-3336 Mel Johnson 10 Digit Transfer (815) 544-2144 via ESInet Date TBD

Lee Co Sheriff, Lee County, IL

316 S. Hennepin Dixon, IL 61021

(815) 284-6631 PSAP Center/Sheriff John Simonton


McHenry Co Sheriff, McHenry County, IL

2200 N. Seminary Ave. Woodstock, IL 60698

(815) 338-2144 PSAP Center/Sheriff Bill Prim


Marengo Fire, McHenry County, IL

121 E. Prairie St, Marengo, IL 60152

(815) 568-8912 Robert Bradbury 10 Digit Transfer (630) 232-8400 via ESInet Date TBD

Ogle Co Sheriff, Ogle County, IL

103 Jefferson St. Oregon, IL 61061

(815) 732-2136 PSAP Center/ Sheriff Brian E. VanVickle


Lynn-Scott-Rock Fire, Ogle County, IL

106 West 1st St Lindenwood, IL 61049

(815) 393-4422 Todd Seaworth 10 Digit Transfer (815) 393-4422 via ESInet Date TBD

Monroe Center Fire, Ogle County, IL

104 West St, Monroe Center, IL 61052

(815) 393-4222 Chief Scott Jaeger 10 Digit Transfer (815) 393-4466 via ESInet Date TBD

Ogle/Lee Fire, Ogle County, IL

401 5th Ave, Rochelle, IL 61068

(815) 562-2122 Chief Dave Sawlsville 10 Digit Transfer (815) 562-2121 via ESInet Date TBD

Winnebago Co Sheriff, Winnebago County, IL

400 W. State St. Rockford, IL 61101

(815) 937-5912 PSAP Center/ Sheriff Gary Caruana


Cherry Valley Fire, Winnebago County, IL

100 E. State St, Cherry Valley , IL 61016

(815) 332-5382 Interim Chief Doug Hayes


Kane Co Sheriff, Kane County , IL

37W755 Illinois Route 38 St. Charles, IL 60175

(630) 232-6840 PSAP Center/ Sheriff Donald E. Kramer

10 Digit Transfer (630) 232-8400 Trunk Transfer Post Cutover

Big Rock Fire, Kane County, IL

47w863 E Second St, Big Rock, IL 60511

(630) 556-3214 John Ruh 10 Digit Transfer (630) 232-8400 Trunk Transfer Post Cutover

Kaneville Fire, Kane County, IL

46w536 Lovell St., Kaneville, IL 60144

630-557-2443 Chief Sigmund 10 Digit Transfer (630) 232-8400 Trunk Transfer Post Cutover

Kendall Co Sheriff, Kendall County IL

1102 Cornell Ln, Yorkville, IL 60560

(630) 553-7500 PSAP Center/ Sheriff Dwight A. Baird


LaSalle Co Sheriff, LaSalle County, IL

707 Etna Rd. Ottawa, IL 61350

(815) 433-2161 PSAP Center/ Sheriff Thomas J. Templeton


Illinois State Police, #2 and #15; Sangamon County, IL

801 South 7th Street Suite 201N & Suite 300-A Springfield, IL 62703

(217) 524-6569 / ISP 911 Coordinator 10 Digit Transfer (630) 271-7535

17 Agencies in 9 Counties Counting State Police

Boone Lee McHenry Ogle 10 D Interim until ESInet Cutovers Trunking via Legacy SR Post Cutover for Kane, Kendall LaSalle

CONFIDENTIAL AND PROPRIETARY DOCUMENT

9-1-1 SERVICES AGREEMENT

This 9-1-1 Services Agreement ("Agreement") is made by and between NG-911, Inc.,

an Iowa corporation with its principal offices located at 815 South Highland, Williamsburg,

Iowa 52361 ("NG-911"), and the DeKalb County, Illinois, Emergency Telephone System

Board (“County” or “ETSB”), with its offices at 150 N. Main Street, Sycamore, IL 60178

(NG-911 and ETSB each a “Party” and collectively, the “Parties”).

RECITALS

WHEREAS, ETSB is part of a group of ten (10) Emergency Telephone System Boards

(“ETSBs”) known as the Northern Illinois Next Generation Alliance (“NINGA”); and

WHEREAS, during August of 2015, NINGA issued a Request for Proposals for a

System Integrator for a Next Generation 9-1-1 Host/Remote System (the “RFP”), a copy of

which, with the responses of NG-911, is attached hereto as Exhibit A and incorporated herein

by reference as though fully set forth; and

WHEREAS, NG-911 responded to the RFP and was selected by the members of

NINGA as the System Integrator; and

WHEREAS, the members of NINGA have each agreed to contract with NG-911

individually, but with contracts with substantially identical terms (except for pricing), to

provide the services contemplated by the RFP; and

WHEREAS, NG-911, Inc. is certificated as a 9-1-1 System Provider (“SSP”) in Illinois

pursuant to the order issued by the Illinois Commerce Commission (“ICC”) in Docket No. 12-

0093, and desires to provide the services contemplated by the RFP; and

WHEREAS, the Parties desire to set forth their agreements with respect to the provision

of a Next Generation 9-1-1 Host/Remote System for ETSB by NG-911,

NOW THEREFORE, in consideration of the premises and payments and mutual

covenants set forth herein, the receipt and sufficiency of such consideration being hereby

acknowledged, the Parties agree as follows:

1. The Project. NG-911 is the System Integrator as defined in the RFP and will design, purchase

and implement a complete turn-key hosted Next Generation 9-1-1 system for ETSB, including

customer premise equipment (CPE), emergency services Internet protocol network (ESInet)

and geographic information system (GIS) as described in the RFP.

2. Scope of Work. NG-911 agrees to perform the work described in the RFP.

a. NG-911 will furnish all tools, equipment, materials, supplies, labor, supervision,


2

transportation, and other accessories, and services required for the performance of its

duties and obligations specified in this Agreement and will execute and complete all

specified work with due diligence, in accordance with good technical practice and

industry standards.

b. As the System Integrator, NG-911 will be responsible for all aspects of Database

Management, GIS Data and Maintenance, and provisioning the Network, as described

in the RFP. ETSB acknowledges that NG-911 utilizes subcontractors for some or all

of those functions, including Solacom, 911 Datamaster, Assure 911, I-Fiber/NIU

Fiber, Cisco, Oracle and others.

c. Initial ALI Database Load. ETSB will provide (or shall direct its affected telecos to

provide) the initial ALI database load at no cost to NG-911. Thereafter, the telcos will

submit to NG-911 and NG-911 shall directly administer and have responsibility for,

Service Order Updates and Error Resolutions. ETSB will cooperate with NG-911 to

correct errors by working with NG-911 to update the MSAG or work with the Telcos

to resolve errors and successfully load ALI records into the ALI database.

d. GIS Data and Maintenance. NG-911 will utilize a format for GIS data consistent with

NENA standards, as required by the RFP. If format changes based on updated

technology, NENA standards or system requirements require an alternate format, the

ETSB agrees to accept the format and make changes to the ETSB’s GIS system and

data to make the system operational. ETSB will provide the initial GIS data load at

no cost to NG-911, which NG-911 will edit, validate and correct. (For clarity, ETSB

is paying $1,000.00 to NG-911 (collectively, the NINGA Members are paying

$10,000.00) for the initial data load as a component of the Start Up Cost. If ETSB

requests subsequent data loads, the cost is $1,000.00 per data load.) Thereafter, ETSB

will provide incremental changes to the GIS data as often as ETSB determines by

entering the data into the 911 Datamaster Ecosystem with Spatial Scene Map. If the

system accepts the changes, the ECRF, LVF and Spatial Scene Map will be updated

within no more than 24 hours. If the system doesn’t accept the changes, it will produce

a report of the noncompliant data. The ETSB will correct and re-submit the

noncompliant data.

e. Network. As the 9-1-1 Service Provider which is subject to State and Federal

regulatory compliance, NG-911 will have the sole responsibility and authority for the

design and deployment of the network, including but not limited to IP assignment,

hardware selection and deployment, monitoring, access to the network, remote access

to the network, connections to the network, bandwidth requirements, system

diagrams, methods and procedures, testing requirements. NG-911 will work

cooperatively with NG-911’s network sub-contractors and NINGA to produce the

network design, seeking input from all parties. NG-911 will make the final decision

on design issues considering all parties. The ETSB agrees to cooperate with NG-911

and make such connections as NG-911 shall direct for the network.

f. Project Management and Regulatory Support. Project Management will be provided


3

by NG-911 in accordance with the RFP. NG-911 will provide regulatory support for

the ETSB’s State’s Attorney or other counsel of ETSB’s choice, to navigate the

Illinois regulatory process for plan modification approvals, including approval of the

change to NG-911 as the System Service Provider. Before any application is filed,

NG-911 will engage in discussions with ICC and ISP Staff to ensure that all regulatory

concerns have been addressed. ETSB will be required to file an application for

approval of an amended plan, either before the ICC or the ISP, or both. The

application will be docketed as a separate proceeding (and may be consolidated with

other applications). The application will include the proposed amended plan and

narrative, network diagrams, test plans and numerous other documents required by

Illinois Administrative Regulations. ETSB will file prefiled direct testimony in

support of the application, respond to Data Requests from Staff and Intervenors, and

file rebuttal testimony and surrebuttal testimony. The ISP and/or the ICC may (and

probably will) hold hearings and require submission of proposed findings of fact and

conclusions of law and/or legal briefs. It is likely that Access Carriers and other third

Parties will intervene, which will require additional attention.

NG-911’s counsel cannot represent ETSB, but due to the common interests of the

Parties, will assist the ETSB’s State’s Attorney or other counsel of the ETSB’s choice

in preparing all filings. NG-911 will assist by providing suggested forms of all

pleadings, including applications, schedules and exhibits, suggested testimony,

rebuttal testimony, surrebuttal testimony; by providing suggested responses to Data

Requests and any other questions from ISP or ICC Staff; by conducting telephone

conferences with ETSB’s attorney or State’s Attorney, and by providing such other

assistance as ETSB, its attorney or State’s Attorney may reasonably request. In

addition, NG-911 will intervene and file testimony in support of the application for

approval of the amended plans and file rebuttal testimony, as needed.

g. Training. NG-911 will provide training as set forth in its RFP response within the

ETSB’s facility or in a location acceptable to the ETSB.

3. Service Level Agreement.

a. NG-911 shall provide support 24 hours, 7 days a week, 365 days per year. Twenty-

four hour technical and maintenance support shall be available with a response time

as set forth below. The Parties acknowledge that a “response” to a Critical or Major

service unavailability shall include the remote response of an NG-911 technician.

Critical: System failures that render the system completely unusable or

significantly reduce system operability, and are considered to be operationally

unacceptable by the ETSB.

Major – System failures that indicate a severe, service affecting condition has

occurred and that immediate corrective action is imperative, regardless of the time

of day or day of the week. Escalation to top level personnel is immediate, and

required.


4

Minor – Non Service affecting issues – noise-static – single position issues

b. NG-911 agrees to have two properly trained and certified technicians, one employed

by NG-911 and one employed by Solacom, located within the footprint of the NINGA

group, with at least one of said technicians available to respond to service

unavailability issues within the time limitations set forth below. Each technician will

have a back-up technician available at all times. The technicians will be on-site for

the installation and cut-over of the ETSB’s system.

c. If the ETSB experiences a Major or Critical service unavailability and NG-911 fails

to respond in the time specified, ETSB will be compensated by a service rebate credit

as follows:

Service Issue Response Time Monetary Credit

Critical 1 Hour $200.00 per hour until response

Major 2 Hours $100.00 per hour until response

Minor 2 Days $0.00

d. Any Credit due to the ETSB will be credited against the next monthly bill. The

maximum credit per month shall not exceed 20% of the monthly recurring charge.

e. The Service Unavailability Credit shall not apply to Service Unavailability caused by

failures or interruptions due to Force Majeure, unauthorized alterations by ETSB or

third parties, or planned work and outages, for which NG-911 will give the ETSB

advance notice.

f. The ETSB agrees to promptly report Service Unavailability to NG-911 via the toll-

free hotline number provided by NG-911.

4. Term. This Agreement shall be effective upon the execution by NG-911 and ETSB and shall

continue for a term that expires sixty (60) months after the date the last of the ten (10) NINGA

members (individually a “Member” and collectively the “Members”) is cut-over live on the

system (“Initial Term”). After the last of the Members is cut over live, the Parties will

confirm in writing the date of expiration of the Initial Term.

This Agreement will be automatically renewed for an additional term of sixty (60) months

(“Renewal Term”) unless either party gives notice, at least 6 months prior to the expiration

of the Initial Term, of intent to not renew.

5. Termination. This Agreement is not terminable by either party except that either party may,

subject to any applicable breach, notice and cure provision, terminate this Agreement for

cause. In the event of termination of this Agreement, the ETSB agrees to timely request

regulatory approval of an amended 9-1-1 Plan to delete reference to NG-911 as the SSP and

to hold NG-911 harmless from any costs associated therewith.


5

6. Payments. The ETSB shall pay to NG-911, the sums set forth and on the dates set forth in

the Payment Schedule attached hereto as Exhibit B and incorporated herein by reference as

though fully set forth.

a. Start Up Cost. The Parties agree that upon payment of the Start Up Cost of

$108,400.00, NG-911 will commence work. In the event less than all ten (10) of the

NINGA Members have executed a substantially identical agreement (except for

pricing provisions) and paid the required Start Up Costs by September 1, 2016, this

Agreement will continue in force and effect, except that

i. the Start Up Cost of $108,400.00 shall be adjusted to an amount equal to

$1,084,000.000 divided by the number of NINGA Members who have signed

agreements by that date. Any amount in excess of the $108,400.00 initially

paid by the ETSB shall be due and payable as of September 1, 2016; and

ii. the Parties covenant and agree to negotiate in good faith an adjustment of the

recurring monthly charges, if any. A reduction in the number of NINGA

Members shall not create any presumption that such monthly charges will be

reduced.

b. Recurring Monthly Charges. The Parties acknowledge that pursuant to 50 ILCS

750/10, the Illinois Department of State Police (“ISP”) is administering the payment

of certain 9-1-1 costs described in the statute, and as further developed by the Illinois

Administrative Code. NG-911 agrees to submit for payment by the ISP, those sums

denominated as such on Exhibit B and to make a good faith effort to obtain payment

of those costs from the ISP. However, the ETSB acknowledges that in the event for

any reason the ISP cannot or will not pay the amounts submitted to it by NG-911 for

payment, upon notice by NG-911, the ETSB will pay the costs. In the event NG-911

subsequently receives payment from the ISP for expenses paid by the ETSB, NG-911

will refund or credit the payment to the ETSB.

7. Participant Fee. Should any ETSB within the State of Illinois elect to not issue an RFP and

instead, contract with NG-911 upon terms and pricing acceptable to NG-911, utilizing the

same contract with the same terms as the contract between NG-911 and the ten (10) original

NINGA members (except for Exhibit B, Pricing, which will vary by customer), NG-911

agrees to collect a one-time fee of $50,000 as a Participant Fee to compensate the original ten

(10) ETSBs for their labor and expenses. After the Participant remits the Participant Fee,

NG-911 will provide a one-time credit of $5,000 to each of the original ten (10) NINGA

members’ monthly bills. The foregoing shall not apply to any ETSBs that are current

customers of NG-911 or that have been identified by NG-911 as its potential customers before

September 1, 2016.

8. Disclosure of Information. The terms of this Agreement, as well as information designated

as proprietary by NG-911, will be held in confidence by the ETSB to the fullest extent allowed

by law and will not be disclosed to or discussed with third parties, including without

limitation, NG-911's competitors. If the ETSB receives a request from a third party for


6

disclosure of all or any part of the Agreement, the ETSB will immediately inform NG-911 so

as to allow NG-911 the opportunity to contest the disclosure or take other measures to protect

its interests, as NG-911 deems appropriate. In all cases, the ETSB will limit disclosure of

information to those with a "need to know" such information; and will not disclose

information clearly designated as proprietary by NG-911 to third parties without the consent

of NG-911.

9. Representations, Warranties and Covenants of NG-911. NG-911 represents, warrants and

covenants:

a. That NG-911 is entering into this Agreement on its own behalf and not on behalf of

any undisclosed person, firm or corporation.

b. That the officer signing this Agreement on behalf of NG-911 has corporate authority

to execute this Agreement.

c. That NG-911 is a duly organized corporation, validly existing and in good standing

under the laws of the state of Iowa and is duly qualified to conduct business in the

state of Illinois and has the power to own or lease its properties and to carry on the

business described in the NINGA Project.

d. That NG-911 has duly approved the execution of this Agreement by all necessary

actions; that this Agreement has been duly and validly executed and delivered by

NG911; and that this Agreement constitutes a valid and binding obligation of NG-

911, enforceable against it according to its terms, subject to bankruptcy, insolvency,

fraudulent conveyance, reorganization, moratorium and similar laws affecting the

enforceability of contractual obligations and creditor's rights generally and by the

application of equitable principles by courts of competent jurisdiction, sitting at law

or in equity.

e. That the execution and delivery of this Agreement by NG-911 and its performance of

the obligations hereunder, do not a) conflict with or result in any breach of any

provision of the formation or charter documents of NG-911; b) except for any required

approvals of the Illinois Commerce Commission (“ICC”) or the Illinois Department

of State Police (“ISP”), require any consent, approval, authorization or permit of, or

filing with or notification to, any governmental authority, except where the failure to

obtain such consent, approval, authorization or permit, or to make such filing or

notification, would not have a material adverse effect on NG-911 or materially

adversely affect the ability of NG-911 to consummate the transactions contemplated

by this Agreement; c) except as would not, individually or in the aggregate, have a

material effect on NG-911, conflict with or result in a breach or violation of, or

constitute a default under, or result in (or create in any party the right to cause) the

acceleration of any performance of NG-911 under, (i) any judgment or law to which

it is subject or bound (subject to any consents, approvals, authorizations, permits,

filings or notifications required under b) above), or (ii) any mortgage, bond, indenture,

agreement, contract, license or other instrument or obligations to which NG-911 is


7

subject or bound.

f. Non-Discrimination/Equal Employment Opportunity. NG-911 shall comply with

Illinois laws regarding non-discrimination and equal employment opportunity and in

accordance with the provisions of 775 ILCS 5/2-105, NG-911 shall:

i. Refrain from unlawful discrimination and discrimination based on citizenship

status in employment and undertake affirmative action to assure equality of

employment opportunity and eliminate the effects of past discrimination;

ii. Comply with the procedures and requirements of the Department's regulations

concerning equal employment opportunities and affirmative action;

iii. Provide such information, with respect to its employees and applicants for

employment, and assistance as the Department may reasonably request;

iv. Have written sexual harassment policies that shall include, at a minimum, the

following information: (i) the illegality of sexual harassment; (ii) the definition

of sexual harassment under State law; (iii) a description of sexual harassment,

utilizing examples; (iv) the vendor's internal complaint process including

penalties; (v) the legal recourse, investigative and complaint process available

through the Department and the Commission; (vi) directions on how to contact

the Department and Commission; and (vii) protection against retaliation as

provided by Section 6-101 of this Act. A copy of the policies shall be provided

to the Department upon request.

g. All people representing/contracting that will be present in the communications centers

with LEADS/NCIC will have to meet the security guidelines as required by the

agency, LEADS, and NCIC. This will involve fingerprinting and receipt of a State

Identification Number (SID) from the State of Illinois.

10. Representations, Warranties and Covenants of the ETSB. The ETSB represents, warrants and

covenants:

a. That the ETSB has the requisite power and authority to approve, authorize, execute

and deliver this Agreement.

b. That the ETSB is a duly appointed and approved county governmental entity, duly

organized, validly existing and in good standing under the laws of the state of Illinois

and is duly qualified to conduct its business and purchase the services contemplated

by this Agreement.

c. That the ETSB has duly approved the execution of this Agreement by all necessary

actions; that this Agreement has been duly and validly executed and delivered by the

ETSB; and that this Agreement constitutes a valid and binding obligation of the ETSB,

enforceable against it according to its terms, subject to bankruptcy, insolvency,

fraudulent conveyance, reorganization, moratorium and similar laws affecting the


8

enforceability of contractual obligations and creditor's rights generally and by the

application of equitable principles by courts of competent jurisdiction, sitting at law

or in equity.

d. That there is no action, suit, claim, governmental investigation, arbitration or other

proceeding pending, or, to the actual knowledge of the ETSB's officers, threatened

against the ETSB or any of its officers or directors which, if adversely determined,

would have a material effect upon the ETSB’s ability to perform its obligations under

this Agreement.

11. Regulatory Approval. The Parties acknowledge that this Agreement and NG-911’s

authority to act as SSP for the ETSB, are subject to the approval and continuing jurisdiction

of the ICC and/or the ISP. NG-911 will request approval to act as the SSP as part of the

application for approval of the modified 9-1-1 Plan. In the event approval is not granted, the

Parties will negotiate in good faith for a resolution.

12. Breach, Notice and Cure. The Parties acknowledge that neither has previously contracted for

hosted 9-1-1 services and that there may be issues which arise that were not anticipated by

either party. Therefore, the Parties covenant and agree to attempt to resolve by good faith

negotiation, any issues which may arise during the term of this agreement.

Following good faith negotiations, in the event of a breach, the non-breaching party shall

notify the breaching party of the specific acts or omissions constituting the breach. The

breaching party shall have thirty (30) days from the receipt of this notice to cure the breach

(except that payment breaches shall be cured within ten (10) days) and if the breach is cured

within said thirty (30) day period (or ten (10) days for a payment breach), the breach will be

deemed to have not occurred; provided, that if the breach is of a type which cannot be cured

within thirty (30) days, the breaching party shall be allowed the opportunity to commence and

pursue to completion, good-faith efforts to cure the breach within a reasonable time. If the

breaching party fails to cure the breach within thirty (30) days or, if the breach is of a type

which cannot be cured within thirty (30) days and the breaching party has not commenced or

is not pursuing good-faith efforts to cure the breach within a reasonable time, this Agreement

may be terminated by the non-breaching party.

13. Limitation of Liability and Indemnity.

a. All provisions of NG-911’s Non-Competitive 9-1-1 System Provider Tariff presently

in effect and hereafter filed with the Chief Clerk of the Illinois Commerce

Commission releasing or limiting NG-911 from liability of any type to any person or

party, are incorporated herein by reference as though fully set forth.

b. Nothing in this Agreement shall limit or restrict either party from pursuing, through

civil litigation or other appropriate means, any actual damages arising out of this

Agreement.

c. NG-911 shall indemnify, defend and hold harmless the ETSB and its officers and

directors from and against any and all loss and expense incurred by the ETSB to third


9

parties arising from or in connection with (or alleged to arise from or in connection

with): (a) any failure by NG-911 to perform its obligations under this Agreement; or

(b) the negligence or willful misconduct of NG-911 or any of its officers, directors,

employees, agents or representatives in connection with this Agreement. The ETSB

shall promptly notify NG-911 of the assertion of any claim against it for which it is

entitled to be indemnified hereunder, and NG-911 shall have the right to assume the

defense of the claim in any legal proceeding and to approve any settlement of the

claim, which approval shall not be unreasonably withheld. These indemnification

provisions are for the protection of the ETSB only and shall not establish any liability

to third parties. The provisions of this Section shall survive termination of this

Agreement.

d. The ETSB shall indemnify, defend and hold harmless NG-911, and its officers and

directors, from and against any and all losses and expenses incurred by NG-911 to

third parties arising from or in connection with (or alleged to arise from or in

connection with): (a) any failure by the ETSB to perform its obligations under this

Agreement; or (b) the negligence or willful misconduct of the ETSB or any of its

officers, directors, employees, agents or representatives in connection with this

Agreement. NG-911 shall promptly notify the ETSB of the assertion of any claim

against it for which it is entitled to be indemnified hereunder, and the ETSB shall have

the right to assume the defense of the claim in any legal proceeding and to approve

any settlement of the claim, which approval shall not be unreasonably withheld. These

indemnification provisions are for the protection of NG-911 only and shall not

establish any liability to third parties. The provisions of this Section shall survive

termination of this Agreement.

14. Relationship of Parties. The relationship of the parties hereunder shall be that of independent

contractors. Neither party is intended to have, and neither of them shall represent to any other

person that it has, any power, right or authority to bind the other or to assume or create any

obligation or responsibility, expressed or implied, on behalf of the other, except as expressly

required by this Agreement or as otherwise permitted in writing. Nothing in this Agreement

shall be construed to create between the Parties any partnership, joint venture, employment

relationship, franchise or agency.

15. Governing Law. This Agreement shall be governed by and construed and interpreted in

accordance with the laws of the State of Illinois applicable to agreements made and to be

performed entirely within such state, including all matters of enforcement, validity and

performance.

16. Recitals. The Recitals set forth on the first page of this Agreement are incorporated herein

by reference as though fully set forth.

17. Severability. If any provision of this Agreement shall be held invalid, illegal or unenforceable,

the validity, legality or enforceability of the other provisions of this Agreement shall not be

affected thereby, and there shall be deemed substituted for the provision at issue a valid, legal and

enforceable provision as similar as possible to the provision at issue.


10

18. Construction of Agreement. The Parties hereto have participated jointly in the negotiation and

drafting of this Agreement. In the event an ambiguity or question of intent or interpretation arises,

this Agreement shall be construed as if drafted jointly by the Parties hereto, and no presumption

or burden of proof shall arise favoring or disfavoring any Party by virtue of the authorship of any

of the provisions of this Agreement. Whenever required by the context, any pronoun used in this

Agreement shall include the corresponding masculine, feminine, or neuter forms, and the singular

form of nouns, pronouns, and verbs shall include the plural and vice versa. The use of the word

"including" in this Agreement shall be by way of example rather than by limitation. The use of

the words "or," "either," and "any" shall not be exclusive. Any specific provisions of this

Agreement shall be deemed to supersede any provisions in the RFP on the same subject and

this Agreement and the RFP shall be construed harmoniously, if possible, to give effect to the

intent of the Parties.

19. Notices. Any notice required or permitted to be given hereunder shall be in writing shall be:

(i) personally delivered; and/or (ii) transmitted by postage pre-paid first class certified United

States mail return receipt requested; and/or (iii) transmitted by pre-paid, overnight courier

(e.g. FedEx, DHL, UPS, etc.); and/or (iv) transmitted by facsimile (fax); and/or (v)

transmitted by e-mail. All notices and other communications shall be deemed to have been

duly given, received and effective on the date of actual receipt. Either Party may unilaterally

change its address for purposes hereof by notice given to the other Party. Notices hereunder

shall be directed to the Parties and their designated agents at the following addresses:

NG-911: NG-911, Inc.

Attn: Michael Ramsey, CEO

815 S. Highland

Williamsburg, IA 52361

Fax: (319) 668-9369

Email: [email protected]

With a copy to :

Richard W. Hird

Petefish, Immel, Heeb & Hird, LLP

P.O. Box 485 842 Louisiana Street

Lawrence, KS 66044

Fax: 785-843-0407


ETSB: DeKalb County Emergency Telephone System Board

Attn: Glenna Johnson, 911 Coordinator

150 N. Main Street

Sycamore, IL 60178

Fax: _____________


20. Further Assurances. The Parties hereby agree to execute, acknowledge and deliver to each other

mailto:[email protected]

mailto:Email:%[email protected]

mailto:Email:


11

any further writings, documents, transfers, acknowledgements, instruments, powers of attorney,

authorizations, filings, applications, reports, etc. that may be reasonably required to give full force

and effect to the provisions of this Agreement, and to take such further actions reasonably required

in fulfillment of obligations set forth herein or in furtherance of the intent hereof.

21. Amendment. This Agreement may not be modified or amended, except by an instrument in

writing signed by the party against whom enforcement of any such modification or amendment is

sought. Either party hereto may waive compliance by the other party with any term or provision

of this Agreement on the part of the other party to be performed or complied with. The waiver by

a party hereto of a breach of any term or provision of this Agreement shall not be construed as a

waiver of any subsequent breach.

22. Force Majeure. No delay in, or failure of, performance by either party under this Agreement,

except and excluding payments hereunder, will constitute default hereunder or give rise to any

claim for damages if and to the extent caused by Force Majeure. Force Majeure shall mean acts

of God, strikes, lock-outs or other such industrial disturbances, acts of the public enemy, wars,

blockades, insurrections, riots, epidemics, landslides, lightning, earthquakes, fires, tornadoes,

storms, floods, high water, washouts, civil disturbances, explosions, breakage or accidents in

and to equipment and machinery, and all other causes, whether of the kind herein enumerated

or otherwise, not reasonably within the control of the party claiming suspension due to Force

Majeure.

23. Binding Agreement. The provisions of this Agreement shall be binding upon, and inure to the

benefit of, the Parties hereto and their respective successors and assigns.

24. Counterparts. This Agreement may be executed in counterparts, all of which together shall

constitute one Agreement binding on the Parties hereto, notwithstanding that both of the Parties

have not signed the same counterpart. Counterpart signatures may be exchanged by pdf file, fax

or other electronic communication and shall be considered to be binding originals.

25. Entire Agreement. This Agreement, including agreements incorporated herein, and the schedules

and exhibits hereto, contain the entire agreement between the Parties with respect to the subject

matter hereof and there are no agreements, understandings, representations or warranties between

the Parties other than those set forth or referred to herein.

(The remainder of this page intentionally left blank; signature pages follow.)


12

IN WITNESS WHEREOF, the Parties have executed this Agreement as of the date(s) set

forth below.

NG-911, INC.

__________________________________ _________________________

By: Michael Ramsey, President and CEO Date Signed

DEKALB COUNTY

EMERGENCY TELEPHONE SYSTEM BOARD

__________________________________ __________________________

By: _______________________________ Date Signed

Title: ______________________________


13

EXHIBIT A

REQUEST FOR PROPOSAL

WITH NG-911, INC. RESPONSES

The Request for Proposal issued by the NINGA group, together with the responses of NG-911,

Inc. are incorporated herein by reference as though fully set forth. The parties acknowledge that

the number of pages makes it impractical to attach to this Exhibit A.


14

EXHIBIT B

PAYMENT SCHEDULE

(Redacted in full)

Network Diagrams DeKalb County

August 2017

1

• DeKalb Network Diagrams (8 pages) August 2017

• iFiber ESInet Diagram (1 page) Connectivity, Data Centers, PSAPs, Power; August 10, 2017

• NG9-1-1 Call Flow Diagram (1 Page)

• NENA INF-003.1-2013 March 21, 2013


August 2017

2


August 2017

3


August 2017

4


August 2017

5


August 2017

6


August 2017

7


August 2017

8


August 2017

9


August 2017

10


August 2017

11

Carrier Listing Billing

List of Carriers w Surcharge 2015 August 2017

1

County: DeKalb

CARRIER LISTING (Wireline, Wireless, VoIP)

Billing Page

CARRIERS STREET ADDRESS, CITY, ZIP CODE

TELEPHONE NUMBER

ILEC/RLEC ILEC MSAG Frontier Rose Soto, 401 Merritt 7, Norwalk,

CT 06851 Barclay Hall, [email protected]

(203) 614-5190 (260) 461-2445

CLEC CLEC MSAG AT&T Local (TCG

and Teleport) (Fixed VoIP Business)

3100 Cumberland Blvd, Suite 700. Atlanta, GA 30339

(770) 240-8773

Fixed VoIP/CLEC VPC or MSAG UI

AT&T U-Verse Gary Johnson, 3100 Cumberland Blvd, Suite 700, Atlanta, GA 30339

(770) 240-8849

CLEC Bandwidth VPC

Birch Telecom (includes Sage)


(770) 240-8815

CLEC VPC UI

Call One (United Communications System dba Call One)

Katie Wilson, 225 W. Wacker Drive, 8th Floor, Chicago, IL 60606

(312) 681-8300

CLEC MSAG Charter FiberLink Andrew Ward, 12405 Powerscourt Dr, St. Louis, MO 63131

(314) 543-5820

CLEC Comtech TCS and West VPC

Comcast Corporate using Level 3 Transport

One Comcast Center, Philadelphia PA 19103

(215) 286-7347

CLEC Comtech TCS and West VPC

Comcast IP (Affiliates) using Level 3 Transport

One Comcast Center, Philadelphia PA 19103

(215) 286-7347

CLEC West VPC (Same owner as Syndeo)

D.N.A. Communications

Amit Patel 601 1st Ave. Rochelle, IL 61068

(815) 562-4290

CLEC Bandwidth VPC

Essex Telcom 1942 Gateway Center Dr, Belvidere, IL 61008

(815) 544-1173

CLEC Bandwidth VPC

First Communications, LLC

Daniel Tarrillion, Sales Tax Associates, Inc., W. William Cannon , Ste. B-150, Austin, TX 78749

(512) 301-1808

CLEC, VoIP and Wireless Transport

Level 3 Communications, LLC

Ernst & Young, 18006 Skypark Circle, Suite 106, Irvine CA 92615

(949) 838-3300

CLEC Fixed ALI VoIP West VPC West Prof Svcs

MCI Metro dba Verizon Business VoIP

3100 Cumberland Blvd, Suite 700. Atlanta GA 30339 John Raynor [email protected]

(770) 240-8773

CLEC West VPC Mediacom Communications

Megan L. Strom, One Mediacom Way, Mediacom Park NY 10918

Virginia Gannon Mediacom Project Manager (845) 443-2432

CLEC West VPC MSAG w NG9-1-1 Cutover

Syndeo Networks Amit Patel, Syndeo Networks, Inc., 300 Cardinal Dr., Ste: 110, Saint Charles, IL. 60175 Former 601 1st Ave. Rochelle, IL 61068

(815) 579-8232, [email protected]



2


TELEPHONE NUMBER

VoIP VoIP VPC UI 8x8 Inc. 3100 Cumberland Blvd Suite 700,

Atlanta GA 30339 (770) 240-8773 VoIP Bandwidth VPC

Access One Mark Lammert, Compliance Solutions, Inc, Longwood, Florida 32750 (407) 260-1011

VoIP Bandwidth VPC

BullsEye 8675 W. 96th St., Ste 220, Longwood, FL 32750 (913) 859-9674

VoIP Comtech TCS and West VPC

CenturyLink dba QCC Eva Morris-Parker, P.O. Box 4065, Monroe IA 71211

(318) 340-5317

VoIP Bandwidth VPC Cincinnati Bell 221E. Fourth St., Room 103-1170, Cincinnati, OH 45202 also Dept Cincinnati Bell Telephone Team - Accounts Payable| Email: [email protected]

(630) 203-0290 X 50039

VoIP West VPC

Clear Rate Communications, Inc

Mark Lammert, Compliance Solutions, Inc, Longwood, Florida 32750

(407) 260-1011

VoIP Bandwidth VPC Interface Security dba Star2Star

3100 Cumberland Blvd, Suite 700. Atlanta, GA 30339; added contact: Jeff Schaaf, Manager | Interface Digital Voice, Interface Security Systems, LLC, 3773 Corporate Center Drive

(310) 792-8272 (Fax)

VoIP Bandwidth VPC

Jive Communications Mark Lammert, 740 Florida Central Parkway, Longwood, Florida 32750 (407) 260-1011

VoIP West VPC West Prof Svcs.

Nextiva, Inc


(407) 260-1011

VoIP Bandwidth VPC

nexVortex Inc Mark Lammert, Compliance Solutions, Inc, Longwood, Florida 32750

(407) 260-1011

VoIP West VPC

Vonage EZTax , 8675 W. 96th St., Suite 220, Overland Park KS, 66212

(913) 859-9674

VoIP West VPC

Vonage Business Solutions, Inc

EZTax, 8675 W. 96th St., Suite 220, Overland Park KS, 66212

(913) 859-9674

Wireless Wireless Comtech TCS MPC

AT&T Mobility w Text

Lawson Dripps; 8089 South Ave., Boardman, Ohio 44512

(513) 657-6270

Wireless Comtech TCS MPC

Intelliquent (Onvoy Spectrum) w Text using Level 3; Live 3-4Q ’17 or early ‘18

1725 Walnut Street, Suite B, Boulder, CO, 80302

(303) 997-2308

Wireless West MPC Ericsson Prof Svcs

Sprint PCS w Text- (SIP using Level 3 SS7 Transport ) UI

6200 Sprint Pkwy. Overland Park, KS 66251

(913) 624-6000

Wireless Comtech TCS MPC

T-Mobile w Text (SIP using Level 3 Transport – Level 3 SS7 Transport ) UI

Document Processor, Illinois Corp Service Co 801 Adlai Stevenson Dr, Springfield, IL 62703-4261

(217) 544-5900

Wireless West MPC

US Cellular w Text

8410 W. Bryn Mawr, Suite 700, Chicago, IL 60631-3486

(773) 399-8900

Wireless West MPC

Verizon w Text (using ICN Transport)

Kip Skeels (TCS) 2401 Elliott Ave, Suite 200, Seattle, WA 98121 Patrick McHale;1120 Sanctuary Parkway, Suite 150 GASA5E911 Alpharetta, GA

(206) 792-2842 (770) 797-1226



3


TELEPHONE NUMBER

30004 MPC/VPC e2 Links into each Data Center

VPC

Bandwidth 3100 Cumberland Blvd, Suite 700. Atlanta, GA 30339

(770) 240-8773

MPC/VPC Comtech TCS

2401 Elliott Avenue, 2nd Floor, Seattle, Washington 98121

(206) 792-2473

MPC/VPC West Sean Smith, Technical Project Manager [email protected]

(720) 494-5814

Reseller Reseller A.C.N.

Communications 8675 W. 96th St., Ste 220, Longwood, FL 32750 (913) 859-9674

Reseller Access Point Mark Lammert, Compliance Solutions, Inc, Longwood, Florida 32750 (407) 260-1011

Reseller Granite Telecommunications, LLC

3100 Cumberland Blvd, Suite 700, Atlanta, GA 30339

(770) 240-8773

Reseller Quantum Shift EZTax , 8675 W. 96th St., Suite 220, Overland Park KS, 66212

(913) 859-9674

Text Control Center TCC Comtech TCS Eddie Lemaire; 2401 Elliott

Avenue, 2nd Floor, Seattle, Washington 98121

(206) 792-2031

Carriers not on Diagrams because: Out of Business, No Customers, Not on 2017 active Illinois ICC List , Not in DeKalb Wireless

365 Wireless (In LERG; no customers )

Carrier says no customers in DeKalb County; Donny McKinnies [email protected]

(678) 916) 0624

VoIP 5LINX (no customers) No longer in business

Mark Lammert, 740 Florida Central Parkway, Longwood, Florida 32750 (407) 260-1011

VoIP Bandwidth VPC AllVoi, Inc. (no customers) (Same as World Discount)

P.O. Box 720128, Oklahoma City, OK

(877) 425-5864 Out of business in Illinois

AMI Communications, Inc. (no customers)

300 Cardinal, Ste. 280, St. Charles, IL 60175 (630) 389-9000

CLEC Bandwidth VPC

Big River Telecom (no customers)

24 S. Minnesota, Cape Girardeau, MO 63703

(573) 651-373 or (855) 244-7483

Unclassified Carrier Chicago Business (no customers) (not on Diagram)

Mark Lammert, 740 Florida Central Parkway, Longwood, Florida 32750 [email protected] (407) 260-1011

Wireless Cricket/LEAP Absorbed by AT&T Mobility. (Not on Diagrams)

Document Processor; C T Corporation System 208 S. LaSalle Street, Chicago, IL 60604

(312) 263-1414

CLEC – not operating in this area

Gallatin River Communications (see CenturyLink; (Not on Diagrams)

Eva Morris-Parker, P.O. Box 4065, Monroe LA 71211

(318) 340-5317

Unable to find Carrier – not handled by West Public Safety

IBFA Acquisitions, LLC (no customers) (Not on Diagrams)

Mark Lammert, 740 Florida Central Parkway, Longwood, Florida 32750

(407) 260-1011

No customers by this name in NINGA Footprint

IP Networked Services dba Elite Telecom (Not on Diagrams)


(770) 240-8773

Removed from State of Illinois by ICC

Lingo Inc. dba PRIMUS Telecom

3838 Carson St, Suite 200, Torrence CA 90503

(310) 792-8272 (Fax)



4


TELEPHONE NUMBER

(Not on Diagrams)

CLEC/VoIP Refer to Comcast CLEC)

New Global Telecom dba Comcast Ventures (Not on Diagrams)

Tom Donnelly, 3100 Cumberland Blvd, Suite 700, Atlanta, GA 30339

(877) 829-4141

VoIP Bandwidth VPC M5 Acquisition Corp. (no customers)

3838 Carson St., Suite 200, Torrance, CA 90503

(310) 792-8272 (Fax)

Reseller NOS Communications, Inc. (No customers) (Not on Diagram)


(407) 260-1011

CLEC VPC unknown Peerless (In LERG for DeKalb) (No Customers) (Not on Diagrams)

Carrier says no presence in DeKalb County. J. Barnicle

[email protected]

Not on ICC List – suspect Reseller

Phone.com, LLC (Not on Diagrams)


(407) 260-1011

CLEC – Refer to CenturyLink VoIP -QCC

Qwest Communications (dba CenturyLink – Not on Diagrams)

Eva Morris-Parker, P.O Box 4065, Monroe, LA 71211

(318) 340-5317

CLEC – Refer to Birch Bandwidth VPC

Sage Telecom Communications, LLC dba Birch – see Birch – (Not on Diagrams)


CLEC Bandwidth VPC Customer – see Essex Telecom above

T6 Broadband dba Rise Broadband (related to Essex Telephone CLEC)

Richard Abels, [email protected]

(303) 779-6292

3/3/17 9:55 AM. Number on ICC goes to dead air.

TNCI Operating Co. (no customers) phone to dead air - Not on Diagrams)


Removed from State of Illinois by ICC

Trans National Communications (no customers) (Not on Diagrams)

Pamela Hesse, 3100 Cumberland Blvd, Suite 700, Atlanta, GA 30339

(877) 829-4141

Not on ICC List – cannot locate carrier

VOIP Street (Not on Diagrams)


Not on ICC List WANetics (no customers) (Not on Diagrams)

EZTax, 8675 W. 96th St, Overland Park KS 66212

(913) 859-9674

CLEC MSAG - self proclaimed West Prof Svcs – research for McHenry

XO Communications Services, LLC (No customers except McHenry) (Not on Diagrams)


(770) 240-8773

CLEC West VPC West Professional Services

Ymax Communications Corp (no customers) dba Magic Jack (Not on Diagrams)

LLC, 3838 Carson, Suite 200, Torrence, CA 90503

(310) 792-8272 (Fax)

Carrier Listing NPA-NXX

Source: LERG August 2017

1

County: DeKalb

CARRIER LISTING (Wireline, Wireless, VoIP)

Wireline NPA-NXX provided Wireless uses pseudo ALI - NPA-555-XXXX VoIP and selected CLECs use pseudo ALI NPA-222-XXXX

Refer to associated excel for added details for DeKalb Provide a list of each carrier that will be involved in the proposed system with NPAs and NXXs Same as Diagrams. ILEC only Split exchange information is detailed in the Plan Narrative and on Diagrams.

Type Carrier Name CLLI NPA NXX XXXX to XXXX ILEC Frontier CETNILXARS0 815 384 0000 9999 ILEC Frontier ERVLILXARS0*# 815 246 0000 9999 ILEC PS/ALI Frontier DKLBILXADS0^ 815 752 0000 9999 ILEC PS/ALI Frontier DKLBILXADS0^ 815 753 0000 9999 ILEC Frontier DKLBILXADS0 815 748 0000 9999 ILEC Frontier DKLBILXADS0 815 754 0000 9999 ILEC Frontier DKLBILXADS0 815 756 0000 9999 ILEC Frontier DKLBILXADS0 815 758 0000 9999 ILEC Frontier DKLBILXADS0 815 787 0000 9999 ILEC Frontier GENOILXARS1 815 784 0000 9999 ILEC Frontier HNCKILXARS0 815 286 0000 9999 ILEC Frontier KRLDILXARS0* 815 522 0000 9999 ILEC Frontier LELDILXBRS0* 815 495 0000 9999 ILEC Frontier MALTILXARS0 815 825 0000 9999 ILEC Frontier MAPKILXARS0* 815 827 0000 9999 ILEC Frontier PWPWILXARS0* 815 627 0000 9999 ILEC Frontier SNDWILXADS0* 815 786 0000 9999 ILEC Frontier SHBNILXARS0* 815 824 0000 9999 ILEC Frontier SMNKILXARS0* 815 498 0000 9999 ILEC Frontier SYCMILXADS0 815 855 0000 9999 ILEC Frontier SYCMILXADS0 815 899 0000 9999 ILEC Frontier WTMNILXARS0 815 264 0000 9999 Notes: 08-04-17 * Frontier Split Exchanges- See Network Diagrams and Plan Narrative for Split County Routing

^ PS/ALI with 9-1-1 Direct to NG9-1-1 NIUnet; Lines on Campus handed by DMS100/CS2100 Campus – see Diagram PS/ALI Page and Test Documents #Opted In

DeKalb County Access Test Plan Final v1.5

Final DeKalb County Access Test Plan

9-1-1 Northern Illinois Next Generation Alliance (9-1-1 NINGA)

August 2017

DeKalb County Carrier Test Plan Final 1.5

Page 2

This page intentionally left blank


Page 3

Table of Contents

1.0 Test Objectives and Guidelines 1.1 Scope of Document .............................................................................................................................................................................................................. 5 1.2 Prior to Testing ...................................................................................................................................................................................................................... 6 1.3 Carrier Types .......................................................................................................................................................................................................................... 7 1.4 Additional System Test Configuration ............................................................................................................................................................................ 15 1.5 Method of Procedure (MOP) ............................................................................................................................................................................................ 19

2.0 Equipment and Software .............................................................................................................................................................................. 23

3.0 Test Cases ........................................................................................................................................................................................................... 24 3.1 Transport Test Cases .......................................................................................................................................................................................................... 25 See the tables in earlier section 1.3 for information on the physical location of connection point. Upon complete of pending ASRs, additional information will be available as well. All Access Transport tests will include a colocation carrier where appropriate. ............ 25 3.2 Signaling Test Cases ............................................................................................................................................................................................................ 26 Each Carrier’s SS7 Point codes for each Switch, wireless or wireline, location and their STP Pair and Locations will be provided to NG-911 Inc and TNS prior to Network Testing and used during the Access Testing. Those records will be maintained by the 9-1-1 SSP..... 26 3.3 Routing and Failover Test Cases ...................................................................................................................................................................................... 28 3.4 Split Exchange Test Cases .................................................................................................................................................................................................. 29 3.5 Texting Test Cases............................................................................................................................................................................................................... 32 3.6 ANI/ALI Test Cases .............................................................................................................................................................................................................. 33 3.7 PS/ALI Test Cases ................................................................................................................................................................................................................ 34

4.0 Site Acceptance ................................................................................................................................................................................................. 35

Appendix A – Service Level Agreements ............................................................................................................................................................. 36

NOC Information will be exchanged for use after Cutover. The SLAs are specified in the Legal Agreements between NG-911, Inc and each Carrier. .............................................................................................................................................................................................. 36


Page 4

This page intentionally left blank.


Page 5

1.0 Test Objectives and Guidelines This NG-911, Inc., Access Test Plan has been developed to test the functionality of the Next Generation 9-1-1 (NG9-1-1) calling system being deployed by NG-911, Inc., the 9-1-1 System Service Provider (911 SSP) for DeKalb County, a member of the Northern Illinois Next Generation Alliance (NINGA). The intent is to deploy an IP-Based NG9-1-1 communication system that meets NENA NG9-1-1 standards, including the emerging NENA IP-Capable PSAP standards. The desired results will be increased functionality, redundancy, diversity, and scalability. The objectives of this testing is to insure that all Access Carriers and directly connected PS/ALI Switch Providers have successfully transitioned their 9-1-1 traffic to the new system, including turning up all appropriate physical and logical connections, and provisioning equipment in their networks to point to the NG9-1-1 NINGA system. The testing is intended to include all Access Carriers in the footprint, including landline, wireless, VoIP and directly connected PS/ALI Customers. In the remainder of the document, reference to Access Carriers includes those PS/ALI Customers unless designated otherwise.

1.1 Scope of Document The intent of this document is to define the test procedures for Acceptance Testing between the Access Carriers 9-1-1 networks, and the NG9-1-1 Next Generation Core Services (NGCS). All testing shall be coordinated by NG-911, Inc., the selected 9-1-1 SSP), in cooperation with each participating Access Carrier. The purpose of this effort is to verify that the Access Carrier networks will deliver 9-1-1 calls via SS7, ISDN PRI, MF or SIP protocol to the NG9-1-1 Data Centers and the NG9-1-1 NCGS. Test calls will then be placed by the Access Carriers and confirmed by NG9-1-1, Inc. that the correct ANI and ALI are received. NG 9-1-1, Inc. and the Access Carriers will work together to resolve any integration issues that arise during testing. This testing will include Transfers and the routing and/or return of Split Exchange traffic in areas where Split Exchanges exist. This Test Plan will be used in conjunction with other test plans developed for this project.


Page 6

There are several related Diagrams and Tables in the Network Diagram portion of the DeKalb filing. The diagrams and tables will assist with planning and executing the test cases described in this document. Those diagrams and tables are included here by reference only:

• SS7 ILEC Diagram • SS7 ILEC Legacy Selective Router for Split Exchange Transfers Diagram • SS7 CLEC Diagram • SS7 Wireless Diagram • SS7 VoIP Diagram • PS/ALI Diagram • e2 Data Link for MPCs and VPCs Diagram • SIP Diagram- includes CLEC and Wireless for DeKalb • Carrier Listing Documents including Name and Type of Carrier- Excel Spreadsheet

This test plan uses acronyms for certain Next Generation Core Services (NGCS) of the Next Generation 9-1-1 Architecture. These elements are described in detail in the Plan Narrative portion of the filing.

1.2 Prior to Testing The access carriers in the DeKalb County service area and NG-911, Inc. will terminate facilities from their networks at the POI in each of the two NINGA Data Centers or to POIs on the ESInet. Locations of the Data Centers and Points of Interconection (POIs) are part of the Narrative. The Carrier Legacy Selective Router Groups will be established to the ESInet. In this filing that includes the Frontier, CenturyLink and AT&T Selective Routers noted in this test plan and on the DeKalb Network Diagrams. Providers of MPC, VPC, PS/ALI, and other MSAG users will establish Database links or FTP interface connectivity to the POIs into the appropriate NGCS equipment in each Data Center, or into the ESInet. NG-911 Inc will extend the e2Links from the POI into the LIS in each Data Center.


Page 7

The provider of inbound texting (TCC) services, Comtech TCS, will establish connectivity from the TCC locations to a managed POI provided by the TCC provider in each Data Center. NG-911 will establish the connections from the POI into the ESRPs in each Data Center. The provider of SS7 services, TNS, will establish connectivity with the STPs from each Carrier’s networks to each other and to the POIs into each Data Center. NG-911, Inc. will extend those links into the Legacy Network Gateway (LNG) in each Data Center. PS/ALI Direct Customers will establish interfaces to a POI on the ESInet. Initially, only Northern Illinois University will use such a connection, while all others PS/ALI Direct Customers will route through the Legacy Selective Router. NG9-1-1, Inc. will configure the NGCS, in particular the Emergency Call Routing Function (ECRF) and the Emergency Service Routing Proxies (ESRPs) to establish IP Connectivity from the carrier network. In addition where SS7, ISDN PRI, MF or any Legacy Signaling besides SIP is required the Legacy Network Gateways (LNGs), Legacy Selective Router Gateways (LSRGs), Border Control Functions (BCFs), Assure911 Monitoring and Loggers and Recorders will be set up.

1.3 Carrier Types Each connection from the Access Carriers, and PS/ALI Direct Customers, the MPC, VPC providers, TCC, and SS7 providers to the NINGA system will be verified by the carriers or providers, and NG-911, Inc. Both primary and secondary connections will be tested. The ability of the carriers to communicate through to the properly designated POIs and onto the appropriate NGCS equipment will be tested. The scope of testing to be performed during testing with a particular carrier depends on the type of carrier, the type of signaling used, and if there are any split exchanges in the footprint. Carriers and Providers could fall under more than one type depending on the services being provided.


Page 8

There are five carrier types: ILEC Wireline CLEC Wireline VoIP Aggregation Wireline Wireless PS/ALI Direct Customer

Test cases common to all types: Transport Signaling Routing and Failover Trunking Database ANI/ALI Monitoring

Test Cases that may apply: Split Exchanges Text Messaging

There are some test cases that are common for all carrier types and will be executed for all carriers, and some test cases are specific to the services being provided. For example, testing with a wireless carrier requires the execution of all of the common test case types as well as the Text Messaging test cases. The test cases are listed in section 3.0. Information that is relevant to the configuration is captured in the following subsections. More specific detail used in executing test cases will be captured in section 1.4. The Carrier and their Types are found in the Carrier Listing table included in the filing.


Page 9

1.3.1 ILEC Testing The Incumbent Local Exchange Carriers (ILECs) have legacy selective routers and end offices serving the ETSB. Test cases will be executed for each selective router and for each end office in the ETSB footprint as listed in tables 1.3.1.1 and 1.3.1.2 below. Configuration information will be recorded at the outset of the testing in the tables below. The ILECs operating in the DeKalb footprint are Frontier Communications, CenturyLink, and AT&T. Their representatives have confirmed that no MF signaling is used. Neither is there any use of Carrier ISDN PRI in the DeKalb footprint. For Frontier and AT&T, the physical point of interconnection (POI) will be located along the ESInet at the locations indicated in the table1.3.1.1. 1.3.1.1 Points of Interconnection along the ESInet

Location Building (as labeled on

diagrams) Entity using

Colocations at this address

Traffic Type Inbound Access

Outbound Split

PS/ALI

3100 Sycamore Road DeKalb IL

DeKalb NIU Data Center DKLBILAF0ED

All Access Carriers and PS/ALI

Yes Yes Yes

903 3rd Avenue Rockford, IL

Rockford TriRivers Data Center RCFRILHX0ED

All Access Carriers and PS/ALI

Yes Yes Yes

225 E Locust St DeKalb IL

DKLBILXA AT&T, Frontier Yes Yes

110 W Locust St Belvidere IL

BLDVILXA Frontier Yes Yes

200 E Railroad St Sandwich IL

SNDWILXA AT&T Yes

375 Wirtz Drive Belvidere IL

DKLBIL NIU Yes

The ILECs may use their own facilities to reach to the POI, or use an underlying transport provider. This information will be available to the test team once the ASRs are received. At each POI, a cross-connection will be in place from the


Page 10

Carrier colocation point in the building to the ESInet interface using Ciena brand Routers or equivalent, capable of directing traffic to either Data Center by design or in an outage or other blocking situation, sending traffic to the alternate Data Center via the iFiber network. See table 1.3.1.2 below. The end customer address records and NPA NXXs will be provided by the ILEC into the NG-911 FTP server, in NENA format. 1.3.1.2 Legacy Selective Routers (Signaling is SS7)

For the end offices that connect with multiple redundant trunks, calls from the ILEC network will be routed using a Lower-Alpha-First routing plan, such that all traffic will initially be sent to the DeKalb Data Center, with overflow and busy attempts going to Rockford Data Center. Routing rules will be discussed with each Carrier at the completion of the pending ASRs. The ILECs in DeKalb’s footprint has been advised they will be routing to the NIU DeKalb Data Center, alternate route via the Rockford Data Center. Future interfaces are planned to the Frontier BLTNILXN1ED when Frontier is prepared to rehome designated split exchanges off of the DKLBILXA4ED SR. Advanced planning with new ASRs may be needed to make these changes. The BLTNILXN1ED SR interface will likely be in place because of Bureau County ahead of this transition. Capacity will be the primary consideration. A Method of Procedure (MOP) will be provided to make those changes.

Carrier Name

Selective Routers

Connectivity Locations (In Data Centers, On ESInet)

Transport Provider

Database

CenturyLink DIXNILXA9ED Direct facility to the NINGA Data Center POIs Pending ASR MSAG Frontier DKLBILXA4ED Via these POIs on the ESInet to reach the Data Center POI:

DKLBILXA BLVDILXA 225 E Locust St 110 W Locust St DeKalb IL Belvidere IL

Syndeo Cross-Connections to ESInet

Pending ASR MSAG

AT&T GENVILGNDS0 Via these POIs on the ESInet to reach the Data Center POI: SNDWILXA DKLBILXA 200 E Railroad St 225 E Locust St Sandwich IL DeKalb IL


Pending ASR MSAG


Page 11

1.3.1.3 End Offices (ILEC) (Signaling is SS7)

End Offices Host Connectivity Location (On ESInet)

Transport Provider

Database

SYCMILXADS0

On ESInet: DKLBILXA 225 E Locust St DeKalb IL BLVDILXA 110 W Locust St Belvidere IL


Frontier, using Frontier POIs to Data Center POIs MSAG GENOILXARS1 SYCMILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG KRLDILXARS0 SYCMILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG DKLBILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG HNCKILXARS0 DKLBILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG MALTILXARS0 DKLBILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG MAPKILXARS0 DKLBILXADS0 Frontier, using Frontier POIs to Data Center POIs SHBNILXARS0 DKLBILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG WTMNILXARS0 DKLBILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG SNDWILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG ERVLILXARS0 SNDWILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG PWPWILXARS0 SNDWILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG SMNKILXARS0 SNDWILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG LEDLILXBRS0 SNDWILXADS0 Frontier, using Frontier POIs to Data Center POIs MSAG

1.3.2 CLEC Testing The facilities based Competitive Local Exchange Carriers (CLECs) serving the DeKalb footprint will use SS7 as the signaling protocol when connecting to the physical point of interconnection (POI). The CLEC may use their own facilities to reach the POI to get into the NCGS, or use an underlying aggregator. The database lookup functionality may be provided by the CLEC or by a 3rd party database provider. The locations of the POIs will be available at the completion of the pending ASRs. The information that is known about facilities and database is available from the Carrier Listings included in this filing. The CLECs serving DeKalb have at least one switch. Test cases will be executed for each switch serving the ETSB footprint. Configuration information will be recorded at the outset of the testing in the table below. Testing for CLECs that


Page 12

serve the area through a 3rd party will be accomplished by testing with the 3rd Party. Testing of network connectivity and routing between these CLECs and their 3rd Party supplier is outside the scope of this section. Calls from the CLEC network will be routed using utilize a Class-Of-Service mechanism, such that all DeKalb traffic will be sent to the DeKalb or Rockford Data Centers. Calls that belong to agencies outside of the DeKalb system should not appear at either Data Center. Carriers will use the scheme of alpha A-L Carrier Names will route first to NIU DeKalb Data Center, alternate to Tri Rivers and the reverse for M-Z Carrier Names.

CLEC Sig Type (SS7, MF, SIP,

ISDN PRI)

Connectivity Location (In Data Centers, On

ESInet)

Aggregator (may be none)

Database

AT&T Local SS7 Pending ASR Pending ASR Pending ASR AT&T Uverse SS7 Pending ASR Pending ASR Pending ASR Bandwidth (transport) SS7 Pending ASR Pending ASR Bandwidth VPC Birch Telecom (same as Sage) SS7 Pending ASR Pending ASR Pending ASR Call One SS7 Pending ASR Pending ASR Pending ASR Comcast Corporate SIP Pending ASR Pending ASR Pending ASR Comcast IP SIP Pending ASR Pending ASR Pending ASR Charter FiberLink SS7 Pending ASR Pending ASR Pending ASR D. N. A. Comm. SS7 Pending ASR Pending ASR Pending ASR Essex SS7 Pending ASR Pending ASR Pending ASR First Communications SS7 Pending ASR Pending ASR Pending ASR Level 3 (transport) SS7 Pending ASR Pending ASR Pending ASR MCI dba Verizon (Fixed Business VoIP) SS7 Pending ASR Pending ASR Pending ASR Mediacom SS7 Pending ASR Pending ASR Pending ASR Syndeo SIP Pending ASR Pending ASR Pending ASR


Page 13

1.3.3 VoIP Testing The VoIP Carrier that will be sending VoIP traffic into the DeKalb footprint will have their traffic carried by an aggregator. The physical point of interconnection (POI) may be located along the ESInet, or at the NINGA Data Center locations. The VoIP Carriers serving the ETSB will likely use Level 3 as an underlying transport provider. The carriers will use the scheme of alpha A-L Carrier Names will route first to DeKalb Data Center, alternate to Rockford Data Center and the reverse for M-Z Carrier Names. Note: Carriers using Level 3 will, for example, be routing to the NIU Data Center first. The carriers may use one or more VoIP Positioning Centers (VPCs) or utilize fixed VoIP locations (Fixed VoIP). Test cases will be executed for each VPC. Configuration information will be recorded at the outset of the testing in the table below. This information as well as the physical locations that Level 3 will connect will become available at the completion of the pending ASRs.

Aggregator Sig Type (SS7, MF, SIP, ISDN PRI)

VPC or “Fixed VoIP”

Facility Provider


ESInet)

Dedicated or Aggregated

Trunking Bandwidth VoIP Carriers SIP/SS7 – Pending ASR Pending ASR Level 3 Pending ASR Pending ASR Comtech VoIP SIP/SS7 – Pending ASR Pending ASR Level 3 Pending ASR Pending ASR West VoIP Carriers SIP/SS7 – Pending ASR Pending ASR Level 3 Pending ASR Pending ASR 1.3.4 Wireless Testing The Wireless carriers serving the ETSB have at least one Mobile Telephone Switching Office (MTSO) and send traffic by way of one or more Mobile Positioning Centers (MPCs). Test cases will be executed for each MTSO in the ETSB footprint. Configuration information will be recorded at the outset of the testing. ESRK information will be verified before testing begins.

Wireless Carrier MPC

Sig Type (SS7, SIP)


ESInet)

Transport Provider

Texting (y/n)

AT&T Mobility Pending ASR SS7 Pending ASR Pending ASR Y


Page 14

Sprint Spectrum Wireless Pending ASR SS7 * Pending ASR Level 3 Y T-Mobile Wireless Pending ASR SS7 * Pending ASR Level 3 Y US Cellular Wireless Pending ASR SS7 Pending ASR Pending ASR Y Verizon Wireless Pending ASR SS7 Pending ASR ICN Transport Y Intelliquent Spectrum Pending ASR SIP Pending ASR Pending ASR Y

* Signaling is SIP to Level3, which re-originates as SS7 into the NCGS, pending SIP UI as of this filing. The wireless carrier may use SS7 or SIP as the signaling protocol when connecting to the system. The physical point of interconnection (POI) may be located along the ESInet, or at the NINGA Data Center locations, which will become available at the completion of the pending ASRs. The carrier may use their own facilities to reach to the system, or use an underlying transport provider. The wireless carriers in DeKalb support texting to 9-1-1. Calls from the MTSO network will be routed based on Location of the Caller. DeKalb traffic will be sent to the DeKalb or Rockford Data Centers. Calls that belong to agencies outside of the DeKalb system should not appear at either Data Center. Carriers will use the scheme of alpha A-L Carrier Names will route first to NIU DeKalb Data Center, alternate to Tri Rivers and the reverse for M-Z Carrier Names. Note: Carriers using Level 3 will, for example, be routing to the NIU Data Center first. 1.3.4 PS/ALI Testing PS/ALI deployment has two types of traffic, directly connected PS/ALI customers routing through the Frontier DeKalb Legacy Selective Router, and PS/ALI customers routing through the NIU Campus Switch. NIU will initially use ISDN PRI as the signaling protocol to reach the NGCS. For all other individual PS/ALI customers routing through the DeKalb Legacy SR, the signaling information is out of the scope of this test plan as it occurs behind the DeKalb Legacy SR. The signaling from the SR into the NGCS is SS7. Since DeKalb is a Frontier Legacy SR, the calls will route through the Frontier SR POIs to the two Data Center POIs.

PS/ALI Customer Switch

Sig Type (SS7,

SIP,ISDN)

Connectivity Location (In Data Centers, On ESInet)

3M DKLBILXA4ED SS7 Via these POIs on the ESInet to reach the Data Center POI: DKLBILXA BLVDILXA 225 E Locust St 110 W Locust St

AGCOM DKLBILXA4ED SS7 Castle Bank DKLBILXA4ED SS7


Page 15

Com Ed DKLBILXA4ED SS7 DeKalb IL Belvidere IL Greenlee Tool DKLBILXA4ED SS7 Ideal DKLBILXA4ED SS7 Kish College DKLBILXA4ED SS7 Nestle DKLBILXA4ED SS7 Northwestern Hospital DKLBILXA4ED SS7 NIU NIU Campus Switch ISDN PRI On ESInet:


Note: Per Frontier, the existing 911 SSP, prior to testing, PS/ALI Direct Customers will be added or deleted from this table as the NINGA network is deployed.

1.4 Additional System Test Configuration Each participant in the testing will provide configuration additional information to NG-911, Inc., which will be maintained throughout the testing period, and saved for future use. 1.4.1 Access Carrier Configuration Information

Connection Type Comments Transport Type Facility Type (Fiber or Copper) Termination Capacity (DS1, DS3) Termination Location Database Provider or FTP Server Legacy SR Interface to Data Center (Split Exchange Carriers only) Signaling Type Numbers of Trunks per End Office, Host or MTSO


Page 16

1.4.2 Database MPC, VPC Configuration Information Carriers use one of the following 3 choices per County

Bandwidth.com Information Comments Type (VPC or MPC) Locations of the Bandwidth Databases IP Addresses (primary E2, secondary E2) Terminating IP Addresses come from NG-911 Inc. Order Number, Completion Date NOC Information Contact Information

Comtech TCS Information Comments Type (VPC or MPC) Locations of the Comtech TCS Databases addresses (primary E2, secondary E2) Terminating IP Addresses come from NG-911 Inc. Order Number, Completion Date NOC Information Contact Information

West Information Comments Type (VPC or MPC) Locations of the West Databases IP Addresses (primary E2, secondary E2) Terminating IP Addresses come from NG-911 Inc. Order Number, Completion Date NOC Information


Page 17

Contact Information 1.4.3 SS7 Configuration Information In general, capacity will be driven by the aggregate of Counties and carriers using SS7, and their associated call volumes.

NINGA Configuration Information Quantity Comments NINGA CLLI Codes 2 DKLBILAF0ED, RCFRILHX0ED NINGA Point Codes 2 005-019-012 (DeKalb, IL), 005-019-013 (Rockford, IL) STP Pair CLLI Codes (TNS) 2 MRCRVA38GS0 (Ashburn, VA),CHCGIL98GS0 (Chicago, IL) STP Pair Point Codes (TNS) 2 238-001-000 (Ashburn, VA), 238-002-000 (Chicago, IL) TOTAL A Links 2 To each Data Center TOTAL Links per Linkset Up to 16 Starting with 2. Traffic volumes dictate growth Contact: Randy Rampersad (319) 430-0611

Carrier Configuration Information Quantity Comments Carrier Originating End Office Common Language Codes

Pending ASR Refer to CLLI Listings at testing

Common Language Codes of the Carrier STP Pairs 1 Per Switch Pending ASR; remotes carry same as host

Point Codes of the Carrier STP Pairs Pending ASR Refer to CLLI Listings at testing A-links to Carrier STP Pairs 2 Per Switch List link and which pair Links to system STP Pair Pending ASR List Link and which STP/Data Center Trunk Groups Pending ASR Trunks per group Pending ASR TOTAL LINKS Pending ASR Carrier Contact: for NG-911, Inc. Bart Lovett Per Carrier


Page 18

1.4.4 PS/ALI Configuration Information

Northern Illinois University Information Comments Connectivity Type (Direct or indirect) Directly Connected to ESInet via Ethernet at 10 meg; routed via NIU

Cienna equipment to each Data Center Switch Type SL100/CS2100 Signaling Type ISDN PRI (from NIU) Database Type FTP Server to NG-911 SSP Datamaster Interface Trunking 2 trunks to each of the Data Centers (2 – determined by NIU) Primary Route DeKalb Alternate Route Rockford NPA – NXXs (815) 752, 753 NAL ~5500 Contact: Kathy Minick; project leader (815) 763-4345 Other PS/ALI Non Direct or Indirect Comments: Connectivity Type (Direct to DKLBILXA4ED)

DeKalb has approximately 18 other Frontier Trunk Groups connected to DKLBILXA4ED. They will be identified and Tested

Switch Type Phase II Signaling Type Phase 1 all SS7 via DKLBILX4ED Database Type MSAG Trunking Per ASR Primary Route DeKalb Data Center Alternate Route Rockford Data Center NPA – NXXs Per ASR NAL Per Frontier Contact: Frontier, Barclay E. Hall


Page 19

1.4.5 TCC Configuration Information

Comtech TCS Information Comments Signaling on delivery interface into system IP3 SIP/MRSP Signaling Physical Connectivity to the system To managed POI at each Data Center Locations Comtech TCS location 1, Comtech TCS location 2 IP addresses of POI devices DeKalb IP address, Rockford IP address Addresses of originating devices Address of location 1, Address of location 2 TCC Contact: NG-911, Inc Randy Rampersad Comtech TCS Eddie Lemaire, Greg Lathrop

1.5 Method of Procedure (MOP) The testing MOP describes the schedule of events including agreed-upon dates as well as other important information to ensure the testing is performed smoothly. 1.5.1 Readiness Checklist

Key Items Notes Ready (y/n)

General Plan May include Diagrams and/or Specific work to be performed

Agreed Day of Week Agreed Maintenance Window Agreed Test Tools Agreed Communications Bridges NOCs Ready Signatures or Electronic Agreement Needed from each party


Page 20

Name and Reach Number Needed of Authorized person from each party 1.5.2 Schedule of Events

Event Date Access Service Request (ASR) received by Bart Lovett (Format of the ASR to be agreed upon industry standard)

Install Begin Testing Begin Testing Complete Grade of Service Observed: 2 Week Service Goal Reached Remove old equipment where appropriate

1.5.3 Contact Information

Testing Contacts Name Telephone Email Address Carrier Test Team Carrier Authorized Lead Person NG-911, Inc Test Team Travis Stender

Randy Rampersad Michael Ramsey Cindy Kruz

(319) 350-8430 (319) 430-0611 (319) 430-1670 (319) 668-8911

[email protected] [email protected] [email protected] [email protected]

NG-911, Inc Authorized Lead Person Bart Lovett (314) 602-3399 [email protected]

DeKalb County Representatives DeKalb County Authorized Lead Person Glenna Johnson (815) 761-6798 [email protected]








Page 21

NINGA Data Centers West East

TriRivers (CLLI: RCFRILHX0ED) 903 3rd Avenue Rockford, Illinois 61104

NIU Wellness and Literary Center (CLLI: DKLBILAFE0D) 3100 Sycamore Road DeKalb, Illinois 60115

Project Management: Project Management Kevin Finley (815) 753-7272 Terry Bainter (815) 980-4128 Henry Kuryliw (815) 753-7220 NOC: (779) 696-0101 24x7x365 NOC: NIU and iFiber Installation: See Below Installation: See Below Contact: Crystal Zimmerman (779) 696-6843 Contact: Kevin Finley (815) 753-7272

Joseph Trickey (815) 753-5798 CLLI: RCFRILHX0ED CLLI: DKLBILAFE0D

1.5.4 Operations and Escalation Procedure The NG-911, NOC is a 24 by 7 by 365 Operation, with the ability to monitor all the NG9-1-1 Core Services, the ESInet, and the health of the 2 Data Centers. The Data Centers have NOC personnel working for each one 24 by 7 by 365. NG-911, Inc., as the 9-1-1 SSP, has the responsibility to Restore Service; also to Report to the ICC Staff and the FCC via NORs when outages exceed the State and/or Federal Requirements for the Data Centers, the NGCS, and the PSAPs and associated transport from the Data Centers to the PSAPs. The 911 SSP also has the responsibility to advise the PSAPs of any problems affecting them per FCC rules promulgated in 2013. The ISP has requested courtesy information notification. There is only one 911 SSP, NG9-1-1, Inc. The various Test team members will escalate issues to their respective authorized persons. The NG-911, Inc Authorized person will keep DeKalb, the ISP and ICC informed. DeKalb County may escalate to the ISP and/or ICC. Amit Patel of Syndeo Networks may become a participant in various elements of the ESInet and Access Testing.


Page 22

Contact Name Telephone Email Address NG-911, Inc Authorized Person Bart Lovett (314) 602-3399 [email protected] DeKalb County Authorized Person Glenna Johnson (815) 761-6798 [email protected] Illinois State Police Authorized Person Cindy Barbera-Brelle (217) 782-3200 Cindy_Barbera-

[email protected] Illinois Commerce Commission Authorized Person

Russell Murray (217) 524-5072 [email protected]


Page 23

2.0 Equipment and Software Any equipment or software, above and beyond the typical testing and NOC tools in the carrier environment, or any that are not available in the new NINGA Next Gen 9-1-1 deployment that are required for this testing will be shown below.

Wireshark - Version 1.12.2 or later Assure911 Monitoring Mobile App v2.0 Vendor Network Element Management Tools


Page 24

3.0 Test Cases The functional test checklist is included in this section. Each item will be tested based on the availability of test circuits and interfaces. Requirements Codes The following codes will be used to indicate pass, fail, or not applicable for each application module feature. The designated code for each requested feature is listed in the “Test Code” column.

TP Test Passed

TF Test Failed

RTP Retest Passed

RTF Retest Failed

NA This feature is not applicable in Customer Systems

When the TF or RTF codes shown above are used, the Tester must also insert an explanation of the planned correction action in the Comments column. The following test cases support various Network and Access Carrier Configurations. The test cases that are relevant to a particular type of Access Carrier facility can be tested as those particular facilities are activated. If feasible, the Test Cases that represents a facility type for which there is multiple Access Carriers and will be repeated for each Carrier. The Templates will be used to track the results that are required to be tested end to end and by Carrier.


Page 25

3.1 Transport Test Cases

See the tables in earlier section 1.3 for information on the physical location of connection point. Upon complete of pending ASRs, additional information will be available as well. All Access Transport tests will include a colocation carrier where appropriate.

Test Case # Test Description Expected Test Outcome Notes

Results/Date

NG-TRN-001 Demonstrate the ability to connect from the carrier network to the POI

Carrier can connect to the ESInet or to a POI in the data center; bandwidth matches the plan.

NG-TRN-002 Demonstrate the ability to connect from the carrier network to the data centers

Carrier can connect to both data centers; bandwidth matches the plan.

NG-TRN-003 Demonstrate the ability to connect from the carrier network to NG Core equipment at the data centers

Sessions can be established to the LNG LSRG, BCF, or ESRP, or LIS

NG-TRN-004 Carriers using access point not on the ESInet – Demonstrate the ability to connect to and through the colocation point on the network through to the NIU DeKalb Data Center.

Carrier can connect and with stated bandwidth to the colocation point.

NG-TRN-005 Carriers using access point not on the ESInet – Demonstrate the ability to connect to and through the colocation point on the network through to the Tri Rivers Data Center.

Carrier can connect and with stated bandwidth to the colocation point.

NG-TRN-00 -006

Demonstrate calls going to intermediate ESInet POIs through Colocation interfaces through the Ciena Routers can reach both Data Center POIs

NG-TRN-00 -007 NG-TRN-010


Page 26

3.2 Signaling Test Cases This section shows signaling related test cases. Depending on the type of signaling used by the carrier some of these test cases may be out of scope. Test cases that are not applicable will have “NA” in the results column. Note: where test cases NG-SIG-006 through 009 show “system STP pair”, that refers to the STP pair of the SS7 service provider that is a partner to the 9-1-1 SSP.

Each Carrier’s SS7 Point codes for each Switch, wireless or wireline, location and their STP Pair and Locations will be provided to NG-911 Inc and TNS prior to Network Testing and used during the Access Testing. Those records will be maintained by the 9-1-1 SSP. The Legacy Selective Routers in the DeKalb footprint are shown in section 1.3.


Results/Date

NG-SIG-001 Demonstrate the ability to support multiple types of inbound and outbound analog or digital Central Office or End Office provisioning, such as SIP, SS7, ISDN PRI, and MF.

Based on collected results of individual tests with carriers using different signaling types. The individual test results appear in this table in the following test cases a - d.

NG-SIG-001a Demonstrate the ability to support SIP calls SIP call received by the SBC forwarded and received at the ESRP

NG-SIG-001b Demonstrate the ability to support SS7 calls Link set up across SS7 facilities and SS7 call received at LNG, converted to SIP, sent to the SBC, forwarded and received at the ESRP

NG-SIG-001c Demonstrate the ability to support MF calls MF call received at LNG, converted to SIP, sent to the SBC, forwarded and received at the ESRP

No MF for DeKalb

NG-SIG-001d Demonstrate the ability to support ISDN PRI calls ISDN PRI call received at LNG, converted to SIP, sent to the SBC, forwarded and received at the ESRP

NG-SIG-002 Demonstrate the ability to terminate call from the Call drops cleanly


Page 27

origination using non-emergency treatment NG-SIG-003 Demonstrate the ability to terminate call from the

data center using non-emergency treatment Call drops cleanly

NG-SIG-004 Demonstrate the ability to terminate call from the origination using emergency treatment

Call stays up on the data center end

NG-SIG-005 Demonstrate the ability to terminate call from the data center using emergency treatment

Call drops cleanly

NG-SIG-006

If SS7, demonstrate that the Carrier STP pairs send signaling messages to the system STP Pair

See section 1.4.4 for SS7 configuration information such as point codes

NG-SIG-007

If SS7, demonstrate that the system STP Pair sends messages to the appropriate Carrier STP Pair


NG-SIG-008 If SS7, demonstrate that the system STP Pair sends the correct network management signals to the appropriate Carrier STP Pair when the first route is unavailable


NG-SIG-009 If SS7, demonstrate that the system STP Pair sends the correct network management signals to the appropriate Carrier STP Pair when the first route is restored


NG-SIG-010 Reserved for future versions NG-SIG-011 Generate traffic to the Legacy Selective Router and

verify that the LSRG converts SIP to SS7 See section 1.4.4 for SS7

configuration information such as point codes


Page 28

3.3 Routing and Failover Test Cases


Results/Date

NG-RTE-001 Demonstrate the ability to establish a call from the carrier to the first route

Lower Alpha or Class of Service used properly

NG-RTE-002a Demonstrate the ability to establish a call from the carrier to the alternate route (make first route busy)

Failover performed properly

NG-RTE-002b Demonstrate the ability to establish a call from the carrier to the alternate route (take NG Core Service element offline)


NG-RTE-002c Demonstrate the ability to establish a call from the carrier to the alternate route (take first data center offline)


NG-RTE-003 Demonstrate that the system returns the appropriate response when the first route is unavailable

Overflow performed properly

NG-RTE-004 Demonstrate that the system returns the appropriate response when the second route is also unavailable

Network Busy Returned properly

NG-RTE-005 Demonstrate that the system returns the appropriate response when the disaster recovery route is also unavailable - This test cannot be performed until after Ogle is online for DeKalb- Note: as of the DeKalb Filing all tests between the DeKalb and Ogle PSAPs are void until an Intergovernmental Agreement can be reached.


NG-RTE-006 -NG-RTE-010

Reserved for future versions


Page 29

3.4 Split Exchange Test Cases

To perform these tests, refer to the following tables, the ILEC/SS7 and ILEC/SR diagrams in the diagram and narrative documents included with the filing. All line number ranges are 0000 – 9999. If the CLLI is split across 2 Legacy SRs, then an additional test number is required to verify proper handling of split traffic by each Legacy SR. Table 3.4.1 DeKalb Directory Numbers Use this table for split exchange testing, to be provided by each Carrier prior to testing. (Each Carrier also will verify NPA NXX or Alternate numbers and add to the list before tests begin)


Results/Date

NG-SPL-001 Demonstrate the ability to route calls that belong to DeKalb ETSB to the NG Core services in the system Data Centers

See Table 3.4.1 for a list of numbers that belong to DeKalb

NG-SPL-002 Demonstrate the ability to route calls that DO NOT belong to DeKalb ETSB to the appropriate County using NG9-1-1 technology. (LSRG)

ANI/ALI will be intact for these calls. See Table 3.4.1 for a list of numbers that belong to DeKalb.

NG-SPL-003

Demonstrate the ability for the 911 SSP that is responsible for Splitting the calls to route to NG-911 Inc those calls that DO belong to NINGA PSAPs. These calls are routed using E911 Legacy SR technology.

Refer to the Narrative Split Exchange section for the calls that are the responsibility of other Carriers to split. Calls terminate in the correct PSAPs.

NG-SPL-004 - NG-SPL-010

Reserved for future use


Page 30

CLLI Code NPA (815)-NXX Host Rate

Center Legacy Selective

Router(s) Test

Numbers Carrier Type LATA Name

LATA Num

PWPWILXARS0

627

SNDWILXADS0

PAW PAW

DIXNILXA9ED, DKLBILXA4ED

3 Needed

Frontier

ILEC

Chicago

358

SHBNILXARS0 824 DKLBILXADS0 SHABBONA DIXNILXA9ED 2 Needed Frontier ILEC Sterling 364 SMNKILXARS0 498 SNDWILXADS0 SOMONAK DKLBILXA4ED 2 Needed Frontier ILEC Chicago 358 SNDWILXADS0 786 SANDWICH DKLBILXA4ED,

GENVILGNDS0 3 Needed Frontier ILEC Chicago 358

For traffic split by the NG 911 System, the following table applies:

NG 911 LSGR TNS STP Legacy Selective Router Carrier PSAP

DLKBILAF0ED CHCGIL98GS0 DIXNILXA9ED CenturyLink Lee County DLKBILAF0ED MRCRVA38GS0 DIXNILXA9ED CenturyLink Lee County DLKBILAF0ED CHCGIL98GS0 DKLBILXA4ED Frontier LaSalle DLKBILAF0ED MRCRVA38GS0 DKLBILXA4ED Frontier LaSalle DLKBILAF0ED CHCGIL98GS0 BLTNILXN1ED Future Frontier LaSalle DLKBILAF0ED MRCRVA38GS0 BLTNILXN1ED Future Frontier LaSalle DLKBILAF0ED CHCGIL98GS0 GENVILGNDS0 AT&T Kendall DLKBILAF0ED MRCRVA38GS0 GENVILGNDS0 AT&T Kendall RCFRILHX0ED CHCGIL98GS0 DIXNILXA9ED CenturyLink Lee County RCFRILHX0ED MRCRVA38GS0 DIXNILXA9ED CenturyLink Lee County RCFRILHX0ED CHCGIL98GS0 DKLBILXA4ED Frontier LaSalle RCFRILHX0ED MRCRVA38GS0 DKLBILXA4ED Frontier LaSalle RCFRILHX0ED CHCGIL98GS0 BLTNILXN1ED - Future Frontier LaSalle RCFRILHX0ED MRCRVA38GS0 BLTNILXN1ED - Future Frontier LaSalle RCFRILHX0ED CHCGIL98GS0 GENVILGNDS0 Frontier Kendall RCFRILHX0ED MRCRVA38GS0 GENVILGNDS0 Frontier Kendall


Page 31

For traffic split by the Frontier Bloomington Legacy Selective Router, the following table applies:

Legacy Selective Router TNS STP NG 911 LSGR PSAP

BLTNILXN1ED - Future CHCGIL98GS0 DLKBILAF0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff BLTNILXN1ED - Future MRCRVA38GS0 DLKBILAF0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff BLTNILXN1ED - Future CHCGIL98GS0 RCFRILHX0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff BLTNILXN1ED - Future MRCRVA38GS0 RCFRILHX0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff

For traffic split by the Frontier DeKalb Legacy Selective Router, the following table applies:

Legacy Selective Router TNS STP NG 911 LSGR PSAP

DKLBILXA4ED CHCGIL98GS0 DLKBILAF0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff DKLBILXA4ED MRCRVA38GS0 DLKBILAF0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff DKLBILXA4ED CHCGIL98GS0 RCFRILHX0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff DKLBILXA4ED MRCRVA38GS0 RCFRILHX0ED DeKalb Sheriff, DeKalb PD, Ogle County Sheriff


Page 32

3.5 Texting Test Cases Testing text to 911 involves the use of cell phones with text capability using the wireless carriers’ services. More test cases will be added as contracts and other agreements are completed between the 9-1-1 SSP and various carriers and partners. Comtech TCS many have additional Access Tests which will be added below as required and duplicated as each County is added.


Results/Date

NG-TXT-001 Demonstrate the ability to deliver a text message. Text is received by NG Core NG-TXT-002 Demonstrate the ability to reply to a text message. A reply can be returned to the texter NG-TXT-003

Demonstrate the ability to deliver a text message to the alternate data center when the primary is unavailable.

NG-TXT-004 Demonstrate the ability to reply to a text message from the alternate data center when the primary is unavailable.

NG-TXT-005

Demonstrate the text messages are recorded properly Texts are recorded, retrieved, and with proper timestamps

NG-TXT-006 - NG-TXT-010

Reserved for future versions – Comtech Test Cases will augment the tests listed here.


Page 33

3.6 ANI/ALI Test Cases


Results/Date

NG-ALI-001 Demonstrate the ability of the Switch or MTSO to deliver Automatic Number Identification (ANI) and Automatic Location from the NG9-1-1 Database in the Datacenters or via the VPC/MPC Databases in the Network for Mobile and VoIP plus some CLECs who choose that solution for Location. Identification (ALI) data display to the ECRF.

Receive ANI/ALI

NG-ALI-002 Validate that NG Core Services equipment can retrieve ALI equivalent information from database system.

Can retrieve ALI information

NG-ALi-003 Validate that NG Core Services equipment can provide for ALI retrieval from Caller ID or manually entered telephone number.

Can retrieve ALI information

NG-ALI-004 Verify connectivity to LIS NG-ALI-005 –

NG-ALI-010 Reserved for future versions


Page 34

3.7 PS/ALI Test Cases


Results/Date

NG-PSA-001 Demonstrate the ability to establish a call from the PS/ALI customer to the first route into the NGCS

Lower Alpha or Class of Service used properly

NG- PSA -002a Demonstrate the ability to establish a call from the PS/ALI customer to the alternate route (make first route busy)


NG- PSA -002b Demonstrate the ability to establish a call from the PS/ALI customer to the alternate route (take NG Core Service element offline)


NG- PSA -002c Demonstrate the ability to establish a call from the PS/ALI customer to the alternate route (take first data center offline)


NG- PSA -003 Demonstrate that the system returns the appropriate response when the first route is unavailable

Overflow performed properly

NG- PSA -004 Demonstrate that the system returns the appropriate response when the second route is also unavailable


NG- PSA -005 Demonstrate that the floor and building number of the caller match the location received.

NG- PSA -006 Demonstrate that the caller’s location appears correctly on the Map.

NG- PSA -007 Demonstrate that all PS/ALI customers can complete 911 calls

NG- PSA -008 Demonstrate that all PS/ALI customer’s 911 calls route to the appropriate PSAP


Page 35

4.0 Site Acceptance We hereby certify that the present document is complete (no missing page) and that all test procedures have been executed and passed as per associated expected results or that all tests have been executed and some deviations were observed All test were executed and passed – including those in Appendix A All test were executed, with the following deviations:

Test Case Number Deviation and acceptability Future Resolution Plan

NG9-1-1, Inc. Test Representative/Witness

Name:

Title:

Signature:

Date:

Carrier Test Representative/Witness (includes acceptance of third party results where applicable)

Name:

Title:

Signature:

Date:


Page 36

Appendix A – Service Level Agreements

NOC Information will be exchanged for use after Cutover. The SLAs are specified in the Legal Agreements between NG-911, Inc and each Carrier. This section will identify specific testable aspects of the Service Level Agreement (SLA) or Carrier Connectivity Agreement between the carrier and the 9-1-1 SSP, NG-911, Inc. This section will be updated as contracts and other agreements are completed. The reference for this section is the NENA Standard Document for Design 08 506. Packet Loss “Packets can be dropped by various devices in the network (e.g. routers, ATM and MPLS switches), or the packet may have been corrupted during transport and dropped at the destination. An overall (end to end) packet loss budget for maintaining intelligible voice transmission is about 5 %. Out of that 5% budget approximately ½ of the packet loss should be allocated for the ESInets with the remaining allocated for the origination network. It is a best practice to engineer ESInets to keep the packet loss budget under 2.5%. Audio media streams are the most sensitive to packet loss. ESInets should be designed without oversubscription. Packet loss of less than 1% should be achievable on such ESInets.” Jitter “A packet's delay varies with its position in the queues of the routers along the path between source and destination and this position can vary unpredictably. Arrival time of packets is ideally equal to the packetization period (i.e. sample rate times samples per packet). Because of the effects of queuing and because 2 sequential packets sent from the same source may not arrive via the same paths, variation in the actual arrival time of packets may occur. It is this variability in the delay that causes jitter. Jitter buffers are utilized to smooth out the variation. It is a best practice to design ESInets to maintain less than 20mS variation in the end point jitter buffers.”


Page 37

Latency “Latency is the amount of time it takes for a packet to reach its destination. The one-way transit delay (i.e. end to end, mouth to ear) for real-time media packets should not exceed 150mS. (ITU-TG.114). When latency exceeds 150 mS, turn taking is significantly impaired. Because the access network is outside the scope of the ESInet, and considerable latency may be incurred, the maximum acceptable delay for packets traversing the ESInet should be less than or equal to 35 mS. It is a best practice to design ESInets to operate with less than 15 to 20 mS of latency. This allows the original encode and decode and a conference bridge in the middle of the path and still achieve the maximum 35mS or less packet delay.” Metro Ethernet “There are ESInets in operation today which have been built on Metro Ethernet services. Metro Ethernet provides a scalable, high performance broadband platform that supports next-generation voice, data, and video. Metro Ethernet is a technology that uses several classes of layer 2 technologies to provide a service that behaves much like an Ethernet (CSMA/CD) over a wide area. Unlike Frame Relay and ATM, where the standards largely defined the service offering and the terms used in describing the technology, Metro Ethernet services vary widely depending on the objectives of the service provider. Metro Ethernet services are sometimes marketed under something like Business Class Ethernet or Business Ethernet. Metro Ethernet services are typically provisioned over private networks managed and sometimes monitored by service providers. Symmetrical rates are available anywhere from 1Mbps to 1Gbps. Different classes of service may be supported, or it could be best effort. It is a best practice to utilize a delay sensitive Class of Service for emergency 9-1-1 calls. Priority classes of service may be used for various data within ESInets. Advantages

• High Bandwidth • Low Cost • Dedicated • Private • Low Latency • Scalable


Page 38

• Regional Availability Disadvantages

• Wide variation in services and SLAs • Complex Traffic Engineering • Reliability (varies with service provider)”

Design Parameters for the ESInet and NGCS per Michael Ramsey CEO and CTO NG-911, Inc.

• Delay – 50ms maximum • Packet Loss – 1% maximum • Jitter – 5 ms maximum • Bandwidth – 100 kbps for each remote position, analog trunk and analog admin line.

Quality of Service – Alerts to Assure911 if Design Parameters are exceeded, assuming the Network Element Managers are able to deliver the exception data from the ESInet and the NGCS.

• Packet Loss – Budget for ESInet – Data Center Core Equipment to the PSAP – 2.5% with no ESInet over-subscription. ESInet transport – 1%

• Jitter – less than 20mS in the end point jitter buffers • Latency –end to end - </= 150mS (ITU-TG.114) – ESInet portion </= 35mS packet delay • QoS measurements that will be monitored in the Data Center NOCs and exceptions send to NG-911, Inc via

Assure911 for alerting, ticketing and reporting. • Other information about the overall network will be discussed with the NOC Manager, NG-911 Technical lead and

Assure911 to refine the Assure system details.


Page 39

Minimum Bandwidth

• 1.544 megabits/second on Ingress from any interconnected Carrier and Egress to any PSAP. (.5 meg per position to handle voice data text and video; smallest number of positions per PSAP is 3; Largest is 10. Each PSAP has 100 meg of bandwidth allocated from the ESInet to the PSAP, far exceeding the Design Requirements at that flat rate. The NENA Standards for the ESInet are 99.999% Reliability; the NENA Standards from the ESInet to each PSAP are 99.9% Reliability. Each PSAP has a backup PSAP and in the future most NINGA PSAPs will have Disaster Recovery backup PSAPs.

• .5 megabits/second per position to any PSAP (number of positions can grow – refer to Design Planning Guidance in the NENA documents is a general rule.

• Each Data Center shall be engineered to carry no more than 40% of the total demand of the NG9-1-1 network. This assumes if there is a failure of one or more of the Data Center Core or of the total Data Center, that the load to be carried by the remaining Data Center is at 80% of the normal demand. If the major event is caused by an extraordinary event, a single focused overload or a general demand overload, or a planned downtime of a part of the network, the remaining 20% could carry the full load until the network is restored. The ESInet was designed with these limits in mind. The NINGA ESInet bandwidth allocation exceeds these parameters.

The testing will validate the measurements as set forth by NENA and NG-911 Inc. are within Design Limits between the Access Carriers through the ESInet to the PSAPs.

Test Status: Completed on to be Done

Type of Testing and Results

Pass or Fail Notes Date

To Be Done Packet Loss


Page 40

To Be Done Jitter

To Be Done Latency

To Be Done Other

End of Document

DeKalb County Network Test Plan

Page 1


9-1-1 Northern Illinois Next Generation Alliance (9-1-1 NINGA)

August 2017


Page 2

This page intentionally left blank


Page 3

Table of Contents 1.0 Overview ............................................................................................................................................................................................................................... 5 2.0 Next Generation 9-1-1 System Requirements Test Cases ................................................................................................................................... 7 2.1 Network Configuration Test Scenarios .........................................................................................................................................8 2.2 PSAP Configuration Test Scenarios ...............................................................................................................................................9 2.3 SS7 Test Scenarios ........................................................................................................................................................................ 14 2.4 TDD/TTY Configuration Test Scenarios ...................................................................................................................................... 16 2.5 Portable PSAP Workstation Test Cases ....................................................................................................................................... 16 2.6 Logging and Instant Recall Recorders Test Scenarios ................................................................................................................ 17 2.7 Management Information Systems Test Scenarios..................................................................................................................... 17 2.8 System Administration Test Scenarios........................................................................................................................................ 20 2.9 System Performance Test Scenarios ........................................................................................................................................... 21 2.10 Reserved ...................................................................................................................................................................................... 21 2.11 System Monitoring Test Scenarios ............................................................................................................................................. 22 2.12 Master Clock Test Scenarios ....................................................................................................................................................... 24 Table 2.12.1 Master Clock Test Devices ............................................................................................................................................... 25 2.13 Administrative Reports Test Scenarios ..................................................................................................................................... 26 2.14 Text Test Scenarios ..................................................................................................................................................................... 27 2.15 Split Exchange Test Cases ........................................................................................................................................................... 30 2.16 VoIP Equipment Scenarios ......................................................................................................................................................... 32 2.17 Map Scenarios ............................................................................................................................................................................. 33 2.18 Data Center Scenarios ................................................................................................................................................................. 34 2.19 Switch and Router Equipment Scenarios (At the Data Centers and at each PSAP)................................................................. 35 Table 2.19.1 Switch and Router Equipment ........................................................................................................................................ 35 2.20 Power and Environment Scenarios ........................................................................................................................................... 36

Table 2.20.1 State Regulations Section 785.55 Technical Requirements .......................................................................................................... 38 Table 2.20.2 Alarm Capable Component Integration Testing - PSAP ................................................................................................................... 39 Table 2.20.3 Alarm Capable Component Integration Testing – Data Center ..................................................................................................... 40


Page 4

Table 2.20.4 Alarm Capable Component Integration Testing – Point of Interface (POI) Locations .......................................................... 40 3.0 Next Generation 9-1-1 Core Services Field Test Cases ....................................................................................................................................... 42 3.1 Resiliency Test Plan ........................................................................................................................................................................ 45 3.2 Security Test Plan .......................................................................................................................................................................... 46 3.3 Performance Test Plan .................................................................................................................................................................... 47

Table 3.3.1 QoS Recommendations from NENA ........................................................................................................................................................... 49 4.0 Additional Testing ........................................................................................................................................................................................................... 50 5.0 Glossary ............................................................................................................................................................................................................................... 51

Appendix A - Standards Report Resolution Template ............................................................................................................................................... 52 Appendix B - General Trouble Report Resolution Template .................................................................................................................................. 53 Appendix C - End to End Test Requirements ................................................................................................................................................................. 54


Page 5

1.0 Overview This NG-911, Inc., Integrated Test Plan has been developed to test the functionality of the Next Generation 9-1-1 network architecture being deployed by NG-911, Inc., the System Service Provider (SSP) for DeKalb County, a member of the 9-1-1 Northern Illinois Next Generation Alliance (NINGA). The intent is to deploy an IP-Based Next Generation 9-1-1 communication system that meets NENA NG 9-1-1 standards, including the emerging NENA IP-Capable PSAP standards. The results will be increased functionality, redundancy, diversity, and scalability. As this document has undergone revisions test cases that were removed are marked as “Reserved”, preserving previous numbering for convenience to the reader. Many Network Tests are common across the NINGA footprint and once completed will not be required again; once completed those sections will be indicated as complete in versions submitted for other NINGA Counties. Each test case has been identified with a specific Test Case number, Test Case Description, the Expected successful outcome of the Test Case and the Actual outcome of the Test Case. Please note that there are many test cases for which the explanation of the expected outcome is captured in the text of the test case description, and no additional notes are included. These will be shown as a blank “Expected Outcome” field. There are some tests that do not require any traffic or call attempt results, and those can be performed any time. There is a distinction between Access Testing and Network testing of the NG9-1-1 Architecture. For Access Testing please refer to the Access Test Plan. Network Test calls will be made prior to live activation of the 9-1-1 service and Access Test calls will be made to validate end-to-end performance during the End to End Testing process. Some Tests are designed to demonstrate performance of the Network. Access Testing will be made to validate Connectivity to the Data Center to and through the Next Generation Core Services (NGCS.) End-to-end testing is to be completed after State Approval and before Cutover. Section 2 describes the tests that validate Next Generation 9-1-1 network connectivity, logging, monitoring, and administrative capabilities. Section 3 describes the tests performed to determine that key components of the network design functioned in a resilient and secure fashion, and performed well under a simulated load. Section 3 describes the tests to be performed and documented. Section 4 describes the testing performed with various NGCS elements, using vendor tools and procedures used during installation validation. This test plan uses acronyms for certain core services of the Next Generation 9-1-1 Architecture. These core services are described in detail in the Narrative in the DeKalb filing, and are included here by reference only. A glossary of additional acronyms appears in section 5.0. Appendix A provides a Standards Trouble Reporting and Resolution Template Appendix B provides a General Trouble Reporting and Resolution Template Appendix C provides an End-to-End Test Requirements. The following page has the overall NENA Standard based connectivity and flow diagram. Not all NGCS are in use in the NINGA NG9-1-1 Architecture.


Page 6

Figure 1.0 Network Connectivity and Flow Diagram


Page 7

2.0 Next Generation 9-1-1 System Requirements Test Cases The following sections provide a brief description of the various functions related to the Emergency Services Internet Protocol Network (ESInet) and i3 specifications as well as test cases and expected responses for each function. The test cases have also been ordered such that they build on data that is produced by a previous test case. The test areas are listed below.

• Network Configuration Test Scenarios • PSAP Configuration Test Scenarios • TDD/TTY Configuration Test Scenarios • Logging and Instant Recall Recorders Test Scenarios • Management Information Systems Test Scenarios • System Administration Test Scenarios • System Performance Test Scenarios • System Monitoring Test Scenarios • Administrative Reports Test Scenarios • Master Clock Test Scenarios • Test scenarios for other aspects of the network, such as:

Texting VoIP Map Data Center Switch and Router Power – Data Center and PSAP Next Generation 9-1-1 specific tests

It should be noted that the test cases performed below serve also as test cases for the NENA standards that comprise the Next Generation 9-1-1 system functional elements and protocols. In particular, this test plan will validate the following list of NENA standards as they apply to this project. For terminology definitions refer to the NENA Standards.

• Flexible Call routing via Emergency Services Routing Protocol (ESRP) • Database queries • Origination using legacy signaling through the Legacy Network Gateway (LNG) • Originating and return of calls through the Legacy Selective Router Gateway (LSRG) • SIP Origination using SIP Protocol, through the Border Control Function (BCF) • Originating from the Text Control Center (TCC) to NG9-1-1 Text Standards for Wireless Carriers specific to Comtech TCS as the TCC • Originating from and to the SS7 STP and SS7 A Link Provider TNS.


Page 8

2.1 Network Configuration Test Scenarios The following test cases support various Network Configurations.

Test Case #

Test Description Results/Date

NG-NC-001 Connectivity East NIU Data Center to DeKalb Sheriff Office NG-NC-002 Connectivity West TriRivers Data Center to DeKalb Sheriff Office NG-NC-003 East NIU Data Center to DeKalb Sheriff Office with Failure in iFiber network NG-NC-004 East NIU Data Center to DeKalb Sheriff Office with Failure in DATA Fiber network NG-NC-005 Reserved NG-NC-006 West TriRivers Data Center to DeKalb Sheriff Office with Failure in iFiber network NG-NC-007 West TriRivers Data Center to DeKalb Sheriff Office with Failure in DATA Fiber network NG-NC-008 Reserved NG-NC-009 Connectivity East Data Center to DeKalb Police Dept NG-NC-010 Connectivity West Data Center to DeKalb Police Dept NG-NC-011 East NIU Data Center to DeKalb Police Dept with Failure in iFiber network NG-NC-012 East NIU Data Center to DeKalb Police Dept with Failure in DATA Fiber network NG-NC-013 Reserved NG-NC-014 West TriRivers Data Center to DeKalb Police Dept with Failure in iFiber network NG-NC-015 West TriRivers Data Center to DeKalb Police Dept with Failure in DATA Fiber network NG-NC-016 Reserved NG-NC-017 Validate that the Configuration of network components, such as software versions are current and

performance parameters are set appropriately

NG-NC-018 Reserved NG-NC-019 Reserved NG-NC-020 Reserved NG-NC-021 Reserved NG-NC-022 Reserved NG-NC-023 Reserved NG-NC-024 Reserved NG-NC-025 Reserved NG-NC-026 Reserved NG-NC-027 Reserved NG-NC-028 Reserved NG-NC-029 Reserved


Page 9

2.2 PSAP Configuration Test Scenarios The following test cases align with the requirements to support network connectivity to various PSAP Equipment, including failover. The test cases will be repeated to confirm connectivity through both data centers.


Results/Dates

NG-PSAP-001 Validate that all new PSAP Equipment complies in all material respects with the current NENA recommendations for PSAP Equipment.

A statement detailing this requirement is available.

NG-PSAP-001-1 Validate that all new PSAP Equipment complies with NENA 04-001, Standards for PSAP Equipment.

NG-PSAP-001-2 Validate new workstations comply with NENA 04-004, Standards for PSAP Intelligent Workstations

NG-PSAP-001-3 Validate system complies with NENA 08-003, Functional and interface Standards NG9-1-1 (i3)

NG-PSAP-001-4 Validate system complies NENA 08-501, Network Interface to IP capable PSAP

Connectivity can be verified from the PSAP devices to each data center, such as switches, routers, and servers. IP addresses are needed at the time of testing. Refer to Tables 2.2.4.1 and 2.2.4.2

See Tables 2.2.4.1 and 2.2.4.2

NG-PSAP-002a Validate that calls are completed when the primary PSAP is unavailable.

This test will be executed including DeKalb County Sheriff and DeKalb PD

NG-PSAP-002b Validate that a fast busy (120 IPM, Network busy) is returned from the NGCS when all DeKalb PSAPs are unavailable.

This test will be executed including DeKalb County Sheriff and DeKalb PD

NG-PSAP-003a Reserved NG-PSAP-003b Reserved

NG-PSAP-004-1 Test for the delivery of Automatic Number Identification (ANI) and Automatic Location Identification (ALI) data display in a consistent format regardless of the originating carrier or

Receive ANI/ALI See Table 2.2.4.3


Page 10

Table 2.2.4.1 – Network Interface to IP Capable PSAP - NIU Data Center East

DeKalb County PSAPSs (From)

IP Address

NIU Data Center East (To)

Result Solacom Servers BCF

Comm APP Proxy Primary Backup 10.110.60.100 10.110.60.103 10.110.60.105 10.110.10.150 10.110.10.151

DeKalb Sheriff Office Router 10.110.60.29 Call Taker Position 1 10.110.60.30

Call Taker Position 2 10.110.60.31






Portable Call Taker 1 n/a


DeKalb Police Department Router 10.110.64.29 Call Taker Position 1 10.110.64.30 Call Taker Position 2 10.110.64.31 Call Taker Position 3 10.110.64.32 Call Taker Position 4 10.110.64.33 Call Taker Position 5 10.110.64.34 Call Taker Position 6 10.110.64.35 Call Taker Position 7 10.110.64.36

routing of the call. NG-PSAP-004-2 Validate that PSAP equipment can retrieve ALI

equivalent information from database system. Eq. Can retrieve ALI information See Table 2.2.4.3

NG-PSAP-005 Confirm that the pre-installation of all new CPE has been completed according to instructions or checklists from the CPE vendor.


Page 11

DeKalb County PSAPSs (From)

IP Address

NIU Data Center East (To)



Call Taker Position 8 10.110.64.37 Portable Call Taker 1 n/a Portable Call Taker 2 n/a


Page 12

Table 2.2.4.2 – Network Interface to IP Capable PSAP - TriRivers Data Center West

DeKalb County PSAPs (From)

IP Address

TriRivers Data Center West (To)



DeKalb Sheriff Office Router 10.110.60.29 Call Taker Position 1 10.110.60.30









DeKalb Police Department Router 10.110.64.29 Call Taker Position 1 10.110.64.30 Call Taker Position 2 10.110.64.31 Call Taker Position 3 10.110.64.32 Call Taker Position 4 10.110.64.33 Call Taker Position 5 10.110.64.34 Call Taker Position 6 10.110.64.35 Call Taker Position 7 10.110.64.36 Call Taker Position 8 10.110.64.37 Portable Call Taker 1 n/a Portable Call Taker 2 n/a


Page 13

Table 2.2.4.3 – Network connectivity to/from ALI providers The information needed to complete this table will become available as pending ASR contracts are finalized and completion of the installation of the links from the ALI providers, West, Comtech, and Bandwidth is accomplished.

NINGA ALI Device IP Address DEKALB CO. SHERIFF Result

DEKALB POLICE DEPT Result

NIU East Data Center ALI 10.110.60.161

NIU East Data Center ALI provided by West Pending ASR

NIU East Data Center ALI provided by Bandwidth Pending ASR

NIU East Data Center ALI provided by Comtech Pending ASR

TriRivers West Data Center ALI 10.110.61.161

TriRivers West Data Center ALI interface with West Pending ASR

TriRivers West Data Center ALI interface with Bandwidth Pending ASR

TriRivers West Data Center ALI interface with Comtech Pending ASR


Page 14

2.3 SS7 Test Scenarios The following test cases support the networking connection required by the SS7 configurations. Test cases in support of signaling are out of scope of this Network Test Plan, and appear in the Access Carrier Test Plan included in the filing. See Figure 2.3.1 for point code information. The Table has Network SS7 Point Codes for the TNS STPs and the Solacom LNGs. Most SS7 Access point codes come with the Pending ASR or upon request from each carrier who has self identified as being an SS7 Provider. The Access work will be completed before testing.

The figure on the next page shows the SS7 configuration that supports DeKalb County, as well as the rest of the NINGA system.

Test Case # Test Description Expected Test Outcome

Notes

Results/Dates/Initials

NG-SS7-001 Demonstrate that the system STP Pair sends signaling messages to the ESRP NG-SS7-002 Demonstrate that the ESRP pairs sends signaling messages to the system STP Pair NG-SS7-003 Demonstrate a Chicago Il STP Failure causes SS7 to route to Ashburn, VA via C-links

and an Alert to go to the Monitoring System

NG-SS7-004 Demonstrate an Ashburn VA STP Failure causes SS7 to route to Chicago IL via C-links and an Alert to go to the Monitoring System

NG-SS7-005 Demonstrate the LSRG can send SS7 back to the STP in Chicago IL through the LNG NG-SS7-006 Demonstrate the LSRG can send SS7 back to the STP in Ashburn, VA through the LNG NG-SS7-007 Follow all recommended Network Tests from TNS the SS7 subcontractor – Document

each for future test purposes.

NG-SS7-008 Verify the ANI and ALI for the SS7 are available at each PSAP NG-SS7-009 Verify the MAP interface has the ANI/ALI and location information from the SS7

interface through v Tri Rivers

NG-SS7-010 Verify the MAP interface has the ANI/ALI and location info from the SS7 i/f through NIU NG-SS7-010 Verify Links in each Linkset are adequate for traffic and that alerts will show if Links are

causing blocked Call Set up queries.

NG-SS7-010 Verify all SS7 Trunks are operating when the SS7 Links are in use and trunking per Data Center is aligned.

NG-SS7-011 Verify Direct Interfaces work for SS7 Links to each Data Center from each STP NG-SS7-012 Reserved. NG-SS7-013 Generate SS7 IAMs in a quantity that exceeds the number of available A-links and

verify that no harm is caused to the LNGs and that an Alert to goes to the Monitoring System

NG-SS7-014 Generate SS7 IAMs in a quantity that exceeds the design capacity of the LNGs and verify that no harm is caused to the LNGs and that an Alert to goes to the Monitoring System

Requires an MGTS or similar equipment


Page 15

Figure 2.3.1 SS7 Connectivity for DeKalb County and NINGA


Page 16

2.4 TDD/TTY Configuration Test Scenarios The following test cases support various TDD/TTY configurations.

2.5 Portable PSAP Workstation Test Cases The following test cases support portable workstations.



NG-TDD-001 Validate the ability to support Baudot–format TDD/TTY dialogue from callers at every position.

NG-TDD-002 Validate the ability to provide TDD/TTY detection and alerting at each call taker position



NG-PRT-001 Demonstrate that each portable workstation can be placed into the system at a PSAP, and perform call taker functions.

NG-PRT-002 Demonstrate that each portable workstation can be placed into the system at an offsite location, and perform call taker functions.

NG-PRT-003 Verify that each Portable Workstation can cause an alert to let the Assure system know it came online

NG-PRT-004 Verify all other Workstation functions the same as a fixed Workstation – use of transfer dispatch and all ANI ALI integration per user.


Page 17

2.6 Logging and Instant Recall Recorders Test Scenarios The following test cases support Logging and Instant Recall Recorders. NG-911, Inc. will work with DeKalb County and the logging and recorder vendors of existing recorders, to integrate and test on the new system to ensure local recordings can be retrieved by the PSAP.

2.7 Management Information Systems Test Scenarios The following test cases support Management Information Systems.



NG-LOGIR-001 Test the Instant Recall Recording and playback application software at each workstation position with the ability to integrate with existing analog voice logging recorder at each PSAP.

Workstation will have IRR functionality

NG-LOGIR-002 Test the Instant Recall Recording and playback application software at each workstation position with the ability to integrate with IP based SIP call logging recorder at each PSAP.

Workstation will have IRR functionality



NG-MIS-001 Validate the System Management Information System (MIS) reporting of transaction volumes and system performance for overall system as well as significant components.

NG-MIS-001-a Test that the MIS and reporting application can allow access to all captured database elements.

NG-MIS-001-b Test the Detail of MIS reporting to provide for both individual PSAP and system-wide transaction volumes and call handling performance.


Page 18

NG-MIS-001-c Test that the MIS reporting can provide for time and day of week in tabular and graphical formats.

NG-MIS-001-d Test that the Reporting application can provide for selection of indexing and sorting keys by any formatted field.

NG-MIS-001-g Test that the MIS is be capable of capturing data from all circuits within the system, including inbound 9-1-1trunks, administrative lines as well as outbound calling.

NG-MIS-002 Test that access to information shall be acquired remotely by permissions.

NG-MIS-002-a Test that the MIS can collect data on the Number of total calls received

NG-MIS-002-b Test that the MIS can collect data on the Number of abandoned calls

NG-MIS-002-c Test that the MIS can collect data on the Number of calls on a per trunk/per circuit basis

NG-MIS-002-d Test that the MIS can collect data on the Number of calls on a call type (wire line, wireless, VOIP, etc.) basis

NG-MIS-002-e Test that the MIS can collect data on the Number of calls conference/transferred

NG-MIS-002-f Test that the MIS can collect data on the Calls conference/transferred by destination

NG-MIS-002-g Test that the MIS can collect data on the Number of calls on a log-on or per position basis

NG-MIS-002-h Test that the MIS can collect data on the Average time to answer

NG-MIS-002-i Test that the MIS can collect data on the Average length of call and average hold time

NG-MIS-003 Test that each data center is equipped with a Call Detail Record (CDR) function that provides for capture, search and retrieval, display, and printing of information regarding each 9-1-1 call. The MIS be able to process data with the following configurations.

NG-MIS-003-a Test that the MIS can collect data on the Date received


Page 19

NG-MIS-003-b Test that the MIS can collect data on appearance time

NG-MIS-003-c Test that the MIS can collect data on the Caller’s telephone number

NG-MIS-003-d Test that the MIS can collect data on the ANI, ESRK or other routing identification

NG-MIS-003-e Test that the MIS can collect data on the Answer time

NG-MIS-003-f Test that the MIS can collect data on the Answering position identification

NG-MIS-003-g Test that the MIS can collect data on the Trunk/circuit identification

NG-MIS-003-h Test that the MIS can collect data on the Time call was released

NG-MIS-003-i Test that the MIS can collect data on the Time call was transferred

NG-MIS-003-j Test that the MIS can collect data on the Transfer destination

NG-MIS-003-k Test that the MIS can collect data on the Abandoned call indicator

NG-MIS-003-l Test that the MIS can collect data on the Ringing start time

NG-MIS-003-m Test that the MIS can collect data on the Time call was placed on hold and taken off hold and by what position

NG-MIS-003-n Test that the MIS can collect data on the All ALI data, including name, address, Community, ESN, Class of Service, etc. Test data may be accessed remotely from the PSAPs with permissions.

NG-MIS-004 Test the ability to direct MIS reports or Workstation printouts to any Local Area Network-attached printer.

NG-MIS-005 Test the ability to export formatted detailed records or summary report tables for analysis with third-party applications (e.g., Microsoft Office)

NG-MIS-006 Test the ability of the MIS reporting to be fully initialized prior to operational use of system; this


Page 20

2.8 System Administration Test Scenarios The following test cases support System Administration.

includes any procedures, routines and scripts for daily, monthly and annual periodic reporting.

NG-MIS-007a Test the ability of the MIS to allow text messages to be retrieved

(See also Section 2.14 Test Case NG-TXT-003a)

NG-MIS-007b Test the ability of the MIS to allow display proper timestamps on text messages

(See also Section 2.14 Test Case NG-TXT-003b)



NG-SA-001 Test the ability to administer call queuing and call routing parameters.

NG-SA-002 Test the ability to support centralized and administered backup and recovery policies.

NG-SA-003 Test the ability to support on-line centralized backup

NG-SA-004 Test that the system can provide real-time call volume and call status information at remote locations

NG-SA-005-a Test that the system can provide Positions Logged On/Ready/Available

Solacom – Guardian Workstation Software

NG-SA-005-b Test that the system can provide Positions Busy/Off Hook


NG-SA-005-c Test that the system can provide Positions Not Ready/Out of Queue


NG-SA-005-d Test that the system can provide Calls in Queue/Calls Pending


NG-SA-005-e Test that the system can provide Calls Holding/Calls Parked


NG-SA-005-f Test that the system can provide PSAP Status (e.g., system OK, connectivity good)


NG-SA-006 Test that the system can provide the Ability to provide a real-time display of system availability, call taker availability & calls in progress.



Page 21

2.9 System Performance Test Scenarios The following test cases support System Performance.

2.10 Reserved This section heading is held pending additional scenario development.



NG-SP-001 Test the ability of the system to support automated, unassisted restoration from stoppages or outages, including significant network components and application software.

NG-SP-002 Test the ability of the system to provide positive/affirmative alert to each call taker position of off-line status, error conditions or conditional events.

NG-SP-003 Test the ability of the system to support localized supervision and reporting of ANI and ALI failures, network outages, etc.

NG-SP-004 Test the ability of the system to provide in each PSAP readily visible and (selectable) audible indicators of emergency and non-emergency calls pending.

Call will ring differently for each type of call – 911 or Admin.

NG-SP-005 Validate that the vendor has described their recommended approach to node and link redundancy to meet Availability Performance Requirements.

Node and Links are redundant

NG-SP-006 Validate that the vendor(s) described their system architecture as it relates to failover and fault tolerance, including the gateway into the 9-1-1 IP network, traffic paths to the network endpoints, and any crucial devices within the scope of the relevant network fabric.

A statement will be available with the system architecture described as it relates to this requirement.


Page 22

2.11 System Monitoring Test Scenarios

Figure 2.11 Monitoring for Testing DeKalb County The following test cases provide System Monitoring validation.



NG-MON-001 Test that the system can provide error logs and diagnostic


Page 23

information sufficient to support vendor troubleshooting. NG-MON-002 Test that the system collects sufficient information to give the

NG-911, Inc. and IT staff an end-to-end view of the ability of incoming calls to be completed

Includes the use of the Monitoring Application to see the exceptions.

NG-MON-003 Test that the system collects SNMP traps from devices capable of sending

SNMP V3 supported

NG-MON-004 Test that the system can provide status in the event of a failure of one of the data centers

Redundant remote server provides status

NG-MON-005a Test that the system can provide status and alerts for Power failure at the data centers

NG-MON-005b Test that the system can provide status and alerts for Power failure at the PSAP, if applicable

NG-MON-005c Test that the system can provide status and alerts Power failure at the POI Locations, if applicable

NG-MON-005d Test that the system can provide status and alerts for Environmental Issues at the data centers

NG-MON-005e Test that the system can provide status and alerts for Environmental Issues at the PSAP, if applicable

NG-MON-005f Test that the system can provide status and alerts for Environmental Issues at the POI Locations, if applicable

NG-MON-006 Reserved NG-MON-007 Test that the system can detect and provide ticketing

information, email and app alerts to both Android and IOS Platform phones

NG-MON-008 Test that the system can discretely alert for NINGA as opposed to other applications to the correct team members.

Alarms will map to the correct part of the architecture.

NG-MON-009 Test that the system can detect and alert on SS7 troubles NG-MON-010 Reserved NG-MON-011 Reserved NG-MON-012 Reserved NG-MON-013 Reserved for SS7 tests pending contract with SS7 service

provider


Page 24

2.12 Master Clock Test Scenarios The following test cases support Master Clock Testing.



NG-MC-001

Test to ensure that the master clock subsystem can provide NTP (Network Time Protocol) and SNTP (Simple Network Time Protocol) time synchronization outputs for additional information systems.

Ensure all end-to-end Master Clock Synchronization Issues are clearly being managed without conflict. Develop a Master Clock diagram for future trouble

NG-MC-001-a Test to ensure that the master clock subsystem can provide timing to 3rd party applications.

Third Party applications will show the appropriate synchronized time.

See Table 2.12.1

NG-MC-001-b

Test to ensure that the master clock subsystem can provide timing to the Database and Communications Servers

Database and Communications Servers will show the appropriate synchronized time.

See Table 2.12.1

NG-MC-001-c Test to ensure that the master clock subsystem can provide timing to the Logging Recorders

Logging Recorders will show the appropriate synchronized time.

See Table 2.12.1

NG-MC-002 Test to ensure that the master clock subsystem can provide a time synchronization source to all PSAPs

PSAP equipment will show the appropriate synchronized time.

See Table 2.12.1


Page 25

Table 2.12.1 Master Clock Test Devices The information needed to complete this table will become available as pending ASR contracts are finalized and completion of the installation of the links from the ALI providers, West and Comtech, and the Service provider Bandwidth is accomplished.

Devices that sync from the Master Clock IP Address (Preliminary)

Master Clock Source (Primary)

Result

Master Clock Source (Secondary – if present)

Result NIU East Data Center Database 10.110.60.160

NIU East Data Center Comm Server 10.110.60.100

NIU East Data Center ALI 10.110.60.161

NIU East Data Center ALI provided by West Pending ASR

NIU East Data Center ALI provided by Bandwidth Pending ASR

NIU East Data Center ALI provided by Comtech Pending ASR

NIU East Data Center Logging Recorder 10.110.60.164

TriRivers West Data Center Database 10.110.61.160

TriRivers West Data Center Comm Server 10.110.61.100

TriRivers West Data Center ALI 10.110.61.161

TriRivers West Data Center ALI interface with West Pending ASR

TriRivers West Data Center ALI interface with Bandwidth Pending ASR

TriRivers West Data Center ALI interface with Comtech Pending ASR

TriRivers West Data Center Logging Recorder 10.110.61.164

DeKalb County. Sheriff PSAP Router 10.110.60.29

DeKalb Police Dept. PSAP Router 10.110.64.29


Page 26

2.13 Administrative Reports Test Scenarios The following test cases support Administrative Report testing.

Table 2.13.1 Report Testing

RFP Section 3.6 Requirements (NINGA Specific) Results A ANI/ALI/Location Information B Seizure time C Position answered D Answer time E Disconnect time F Incoming trunk number

G Total count of call type(s) such as but not limited to wireline, wireless, VoIP call types.

H Average call waiting I Average call duration J Duration of transferred calls K Number of calls transferred to each PSAP

L Total number of times a caller is transferred and to which PSAP(s)

M Total abandoned calls N Calls by incoming trunk O Call by hour of day P Calls answered by position Q Calls answered by all positions

Test Case # Test Description Expected Test Outcome Results/Dates/Initials

NG-ADM-001 Test to ensure that the system provides the reports called for in the requirements in the 9-1-1 NINGA RFP, section 3.6.

Requirements are shown in Table 2.13.1

See Table 2.13.1


Page 27

R Calls answered by each PSAP S Call answered by user ID T Make busy time

2.14 Text Test Scenarios The following test cases support Text Message testing. These test cases are concerned with network connectivity from the Texting service provider to the new system, including accessing location databases. The new system supports NENA Compliant Text Standards, and test cases to validate that or reveal any issues with compliance on the part of the system, or the incoming text message formats and/or protocol, are contained in the Access Carrier Test Plan, and will be performed on a per-carrier basis.

The figure on the next page shows the Text Message flow through the system.



NG-TXT-001

The system is capable of delivering a text message.

The appropriate call-taker position based on the location of the “texter” receives the incoming msg. All Texts will be delivered by Comtech so testing includes connectivity to both data centers as shown in table 2.14.2

See 2.14.1

NG-TXT-002 The system is capable of replying to a text message.

The call-taker can engage in a text session.

NG-TXT-003a The text message is properly logged and recorded

History of texts show proper logging (See also Section 2.7 Test Case NG-MIS-007a)

NG-TXT-003b The text message is properly time stamped

History of texts show proper timestamp (See also Section 2.7 Test Case NG-MIS-007b)

NG-TXT-004 Reserved for TCC tests per Contract with TCC provider


Page 28

Figure 2.14 Text Message Connectivity and Flow


Page 29

Table 2.14.1 – Text Testing Comtech Connectivity TCC to ESRP through the BCF w Database Location

Comtech Location NINGA Data Center East (To)

Result

NINGA Data Center West (To)

Result To the POI To the NGCS To the POI To the NGCS Comtech Location 1 IP Address

Comtech Location 2 IP Address


Page 30

2.15 Split Exchange Test Cases

In these test the flow of the call must track the path from the LNG, to the LIS/ECRF, then onto the ESRP. From there, if the call belongs to the DeKalb ETSB it will proceed through the Data Center Router, and on to the DeKalb PSAP site. If the call does not belong to the DeKalb ETSB, it will be “hair-pinned”, or “tromboned” per Solacom, out to the Legacy PSAP through the Legacy Selective Router Gateway (LSRG). Additional test cases appear in the Access Carrier Test Plan.


Results/Date

NG-SPL-001 Demonstrate the ability to route calls that belong to DeKalb ETSB through the LNG and the NG Core services in the Data Centers

ANI/ALI will be intact for these calls.

NG-SPL-002 Demonstrate the ability to route calls that DO NOT belong to DeKalb ETSB to the LSRG and through to the appropriate County.

ANI/ALI will be intact for these calls.

NG-SPL-003 Reserved for NG Core vendor and Database vendor tests per Contract with each provider


Page 31

Figure 2.15 Split Exchange Connectivity and Flow.


Page 32

2.16 VoIP Equipment Scenarios The following test cases support connectivity to and from VoIP handsets.

Table 2.16.1 – Handset Connectivity

NINGA NIU Data Center East NINGA TriRivers Data Center West

PSAP Handset IP Address

Result Handset IP Address

Result

DeKalb County Sheriff 10.110.60.10 10.110.60.10 DeKalb Police Dept 10.110.64.10 10.110.64.10



NG-VOIP-001 The system is capable of routing a call from a VoIP Trunk Group located outside of the ESInet

NG-VOIP-002 Validate the telephone instruments are configured to operate on the network

Show at least one of the existing m5420e systems can operate on the network.

See Table 2.16.1


Page 33

2.17 Map Scenarios The following test cases support MAP function testing. Tests for the integrated map system will be augmented based on NINGA requirements and vendor specs when the Vendor’s contract is completed.



NG-MAP-001 The system is capable of populating the Map at a call-taker position

NG-MAP-002 The call-taker can access call information from the Map

NG-MAP-003 The call-taker can answer a call from the Map Display


Page 34

2.18 Data Center Scenarios The following test cases support various Data Center functions and failure modes.



NG-DC-001 The East Data Center can perform all relevant functions

The East Data Center processes calls, accesses the Database, maintains connectivity with incoming trunks, etc.

NG-DC-002 The West Data Center can perform all relevant functions

The West Data Center processes calls, accesses the Database, maintains connectivity with incoming trunks, etc.

NG-DC-003 The system can deliver calls to the appropriate PSAP with an entire Data Center offline

The redundant Data Center picks up the load

NG-DC-004 The system can deliver calls to the appropriate PSAP with a partial Data Center failure

The data center recovers readily or the redundant Data Center picks up the load

NG-DC-005 Load Balance – This test case was moved to NGCS testing in section 3.0


Page 35

2.19 Switch and Router Equipment Scenarios (At the Data Centers and at each PSAP) The following test cases support testing various modes of operations including failures related to the routers and switches.

Table 2.19.1 Switch and Router Equipment

Devices that sync from the Master Clock IP Address Device is Functional

Results Admin Access

Results Failures are detectable results

East Data Center Router 10.110.60.29

West Data Center Router 10.110.61.29

DeKalb County Sheriff Router 10.110.60.29

DeKalb Police Dept Router 10.110.64.29



NG-RTR-001 The Router at each site is functional

Communication to each site is up See Table 2.19.1

NG-RTR-002 The Router at each site can be accessed by the administrator

Admin logins are configured See Table 2.19.1

NG-RTR-003

A failure of a Router is detectable.

Monitoring system picks up the event and maps to the Appropriate Router Address and Icon on the Handheld Device; the Alert is received and is fully visible and actionable by the right party.

See Table 2.19.1


Page 36

2.20 Power and Environment Scenarios

Figure 2.20 Power system-wide including DeKalb County


Page 37

The following test cases support various power related scenarios. (Failover from Primary to UPS to Generator or Battery will be unique for each Data Center and at each PSAP. (Additional Power information – refer to the Narrative). Note: For every ESInet field location with direct Carrier connectivity or PSAP connectivity, it is desirable to verify the Power and critical environmental alarms, where they exist, come to the Data Centers and are ported to the Assure911 System for alerting. Augment Tests accordingly. These results will be required once and not be repeated per County unless additional sites are added to the ESInet or different equipment.



NG-PWR-001 Each site recovers from partial power outage

No functionality lost after outage

NG-PWR-002 Each site recovers from complete power outage

No functionality lost after outage

NG-PWR-003 Backup power facility at each site is operational

Site remains in operation during initial outage

NG-PWR-004 At each Data Center, State Power Regulations are adhered to.

Statement from the Data Center operator will show compliance with Section 785.55 technical requirements as excerpted in table 2.20.1

NG-PWR-005 Alarm-capable features of Data Center power plant are integrated with the Assure911 system

Narrative Input Requirements Power and Environmental Requirements (July 14, 2016) for TriRivers and NIU Data Centers See Table 20.20.3

NG-PWR-006 Alarm-capable features of PSAP power plant are integrated with the Assure911 system

Per NINGA Requirements Power and Environmental Survey (November 16, 2016) for DeKalb Sheriff Office and DeKalb Police Dept. See Table 20.20.2

NG-PWR-007 Alarm-capable features of POI Sites power plants are integrated with the Assure911

Per NINGA Requirements Power and Environmental


Page 38

Table 2.20.1 State Regulations Section 785.55 Technical Requirements a) Power and Communications Systems

1) All direct current (DC) power supply service feeds shall be fused at a level not to exceed the rated capacity of the smallest conductor used in the feed, or 200% of the maximal operational consumption of the feed, whichever is smaller.

2) The use of equalizing center design, the practice of tapping smaller power cables to larger power cables, is only permitted when fused at the tap, or fused in accordance with subsection 785.55(a)(1) above.

3) Main power supply systems, both AC and DC, shall be designed to enable a practical, safe disconnection of all interior feed circuits using a master or zoned master switches or fuses. Multiple locations for zoned master switches or fuses may be utilized, but no more than three locations per floor shall be permitted except that existing telecommunications switch facilities with multiple power supply systems exceeding three locations per floor shall develop and utilize a coded layout plan for effective zoned disconnections subject to individual approval by the Office of the State Fire Marshal. Details of such disconnect plan shall be made a part of the pre-emergency plan.

4) Carriers should consider the incorporation of surge protective devices for use on AC service to mitigate the potential impact of equipment damage due to transient or overvoltage surges.

5) Armored cable, rigid or flexible metal conduit, or any other cable with an exterior metallic or conductive external surface shall not be placed in cable trays containing AC, DC or communications cables.

6) Wherever possible, existing AC and DC power cables should be physically separated from communications cables. New construction shall have AC and DC power cables physically separated from communications cables.

7) Use of cables employing polyvinyl chloride (PVC) insulation for any new or expansion of facilities shall be allowed only if the cable has an oxygen index rating of 28 or higher, unless monitored by a system designed to sense chloride emissions.

8) Removal of old cable shall be monitored by each telephone company or telecommunications carrier to guard against damage to remaining cable. b) Detection Systems

1) Design and installation shall comply with fire protection standards as published in the NFPA's Code 72 and 72E. 2) Types of fire detectors include heat, smoke, flame, laser, photoelectric, aspiration, ionization and fire-gas types. Detection systems shall utilize a minimum of two (2)

types of devices monitoring each alarm zone within a facility for buildings exceeding 1,600 square feet. Buildings of less than 1,600 square feet will require one (1) single detector-type capability. Single detector-type systems shall not utilize heat only sensors.

3) Each facility with multiple alarm zones within a building exceeding 1,600 square feet shall have a local interior zone annunciator panel immediately inside of an entrance door as designated in the pre-plan. The facility may also have remote monitoring by a company operated central station. Upon receipt of fire signal at such remote station, the station operator shall immediately notify the appropriate Fire Department.

system Survey (November 16, 2016) See Table 20.20.4

NG-PWR-008 PSAP Power testing performed as planned

The date of the most recent testing per NINGA Requirements Power and Environmental Survey (November 16, 2016), will be provided as results


Page 39

4) Each carrier should develop a facility inspection program utilizing thermographic infrared scanning technology or equivalent as an aid to identify abnormal heat buildup. c) Ventilation

1) All facilities shall provide ventilation access for removal of smoke and toxic gases from the facility as follows: A) Single level telephone facilities consisting of no more than 1,600 square feet shall provide no less than two separate physical openings of sixteen (16) square feet each

or greater on separate sides of the facility unless the local fire agency agrees to accept a single opening. B) All facilities exceeding 1,600 square feet (including multi-story buildings) shall provide at least two (2) vent access openings per floor. The minimum size of each

opening shall be sixteen (16) square feet for each 10,000 square feet of floor area, except that multiple vent openings per floor shall not be required where mechanical smoke evacuation systems are present and are acceptable to the local fire agency.

Table 2.20.2 Alarm Capable Component Integration Testing - PSAP The dates of integration with Assure911 and testing complete will be shown in the results for each location that undergoes alarm integration testing. Refer to documents included by reference with the filing for PSAP locations.

Alarm Capable Component DeKalb Sheriff Office Results DeKalb Police Dept Results Commercial Power UPS Generator Battery Heating Plant Air Conditioning Plant Security Physical Security Logical Timing Source


Page 40

Table 2.20.3 Alarm Capable Component Integration Testing – Data Center The dates of applicable integration with Assure911 and testing complete will be shown in the results for each location that undergoes alarm integration testing. Refer to table 2.20.5 below for locations of the Data Centers.

Alarm Capable Component NIU Data Center East Results TriRivers Data Center West Results Commercial Power UPS Generator Battery Heating Plant Air Conditioning Plant Security Physical Security Logical Timing Source

Table 2.20.4 Alarm Capable Component Integration Testing – Point of Interface (POI) Locations The applicable integration tests, and completion of this table (2.20.4) will be repeated for each of the locations in table 2.20.5 below. The dates of integration with Assure911 and testing complete will be shown in the results for each location .

Alarm Capable Component ESInet Location Results Commercial Power UPS Generator Battery Heating Plant Air Conditioning Plant Security Physical Security Logical Timing Source


Page 41

Table 2.20.5 Point of Interface (POI) Locations

Location Building (as labeled on diagrams)

3100 Sycamore Road DeKalb IL

DKLBILAF0ED (DeKalb NIU Data Center)

903 3rd Avenue Rockford, IL

RCFRILHX0ED (Rockford TriRivers Data Center)

225 E Locust St DeKalb IL

DKLBILXA

110 W Locust St Belvidere IL

BLDVILXA

200 E Railroad St Sandwich IL

SNDWILXA


DKLBIL


Page 42

3.0 Next Generation 9-1-1 Core Services Field Test Cases NG9-1-1 Network Testing takes place on the deployed network and functional elements in the field. Access Carriers are not involved in the Network testing. NG-911, Inc. will perform these same tests before any Access Carrier enters the Network. Many of these tests can be done once, such as the SIP related tests with an Access Carrier after the basic tests are performed in a simulated fashion and not repeated with each Access Carrier The Diagram for the Test Configuration is labeled 3.0.1. with associated Tables 3.0.1.1 and 3.0.1.2 respectively. The functions of the NG9-1-1 Network Design that will be tested are:

1. Resiliency to component failures 2. Performance of the design under heavy load conditions. 3. Security of information and security from attacks that affect performance.

Section 3.1 describes the results of network tests to be performed to validate that key NGCS components in the network design function in a resilient and secure fashion, and perform well under a simulated load. Section 3.2 describes the Security Testing. Section 3.3 also describes the network tests to be performed to validate that the NG9-1-1 NGCS configuration based on the overall engineering design can perform under a load. The following page has the overall system network diagram. Where items are marked with an asterisk (*), please refer to tables 2.2.4.1, 2.2.4.2, 2.2.4.3, 2.12.1, and 2.19.1 for additional IP Address Information. Items marked with a double asterisk (**) are in pending until contracts and agreements are finalized, and will become available after approval of the filing.

DeKalb County Network Test Plan Version 1.0

Figure 3.0.1 - Network Testing Configuration Diagram


Page 44

Table 3.0.1.1 - Data Center - see Figure 3.0.1

Data Center NGCS Functions IP Address** TriRivers

West Legacy Network Gateway (LNG) 10.110.61.106 SIPc 10.110.61.100 ESRP 10.110.61.105 Media Server 10.110.61.101 Legacy Selective Router Gateway (LSRG) 10.110.61.107

Data Center NGCS Functions IP Address NIU East Legacy Network Gateway (LNG) 10.110.60.106

SIPc 10.110.60.100 ESRP 10.110.60.105 Media Server 10.110.60.101 Legacy Selective Router Gateway (LSRG) 10.110.60.107

** - The IP addresses for these devices will be verified again prior to testing

Table 3.0.1.2 - PSAP Info - see Figure 3.0.1

PSAP Number County

Work Stations

Work Station IP Addresses

Router /PSAP

IP Address /Router

1 DeKalb County Sheriff 2 10.110.60.30 10.110.60.31

1 10.110.60.29

2. DeKalb Police Dept 2 10.110.64.30 10.110.64.31

1 10.110.64.29


Page 45

3.1 Resiliency Test Plan This set of tables reflects the tests and the documented results from Resiliency Testing.

Test Case # Test Description Expected Test Outcome Results/Dates/Initials NG-001 Place 911 test call from SIP UA and remove

power from the ESRP IP address Place 2nd test call and record both results

911 call is routed to the alternate ESRP IP address via Virtual IP address

NG-002 Place 911 test call from SIP UA and remove the RJ45 connection from ESRP to Switch IP address Place 2nd test call and record both results

911 call is routed to the alternate ESRP IP address via IP address

NG-003 Place 911 test call from SIP UA and remove power from the PSAP IP address Place 2nd test call and record both results

911 call is routed to alternate PSAP IP address via Virtual IP address

NG-004 Place 911 test call from SIP UA and remove the RJ45 connection from PSAP to Switch IP address and record both results

911 call is routed to alternate PSAP IP address via Virtual IP address

NG-005 Place 911 test call from SIP UA and remove power from Call taker 1 Place 2nd test call and record both results

The 911 call is routed to the 2nd Call Taker

NG-006 Place 911 Test call from SIP UA and remove RJ 45 connection from Call taker position to Switch Place 2nd test call and record both results

911 call is routed to alternate Call Taker


Page 46

3.2 Security Test Plan

Test Case # Test Description Expected Test Outcome Results/Dates/Initials

NG-017 Restrict Access to the BCF and ESInet from outside the network by denying access to other than authorized IP addresses.

Access to the BCF from outside the network using Non-Authorized IP Address is denied.

NG-018 Login to BCF Management port using non-authorized logins and passwords

Access is denied for non-authorized users

NG-019 Allow Authorized Access to management port of the BCF

Users with non-Authorized Logins and passwords are denied access to the BCF Management port

NG-020 Restrict user privileges in the BCF on a per user login and password basis

Authorized users are restricted to their allowed access privileges

NG-021 Call Taker/PSAP initiates outbound SIP call Call completes from PSAP NG-022 PSAP/ Call Takers attempt to access Internet Call takers cannot complete to

the Internet

NG-023

Allow normal inbound SIP call traffic and block unauthorized SIP sessions

SIP traffic allowed for trusted IP addresses only


Page 47

3.3 Performance Test Plan In the case of the Performance Testing, if assistance is needed to generate the call volume, locate DDoS attack software. Another major objective is to recognize when a DDoS or TDoS attack is taking place and to escalate, and advise others per Policy or Regulatory Requirements. Note: The monitoring system will be set to alert where data is available when QoS parameters exceed established thresholds.

Test Case # Test Description Expected Test Outcome Results/Dates/Initials NG-024 Generate multiple SIP test calls to the ESInet and

observe performance. SBC should forward all SIP Calls to the PSAP Call Takers

NG-025 Generate Multiple SIP calls to the Session Boarder Controller (SBC)

SBC should forward all SIP Calls to the PSAP Call Takers

NG-026 Generate Multiple test Calls to the Call taker positions until all are busy

Calls should Queue and release as positions become available

NG-027a Verify the ability of the Call Taker to transfer a call to another PSAP on the ESInet

Call Taker successfully transfers the call

NG-027b Verify the ability of the Call Taker to transfer a call to another PSAP off the ESInet via 10 digit dialing

Call Taker successfully transfers the call

NG-027c Verify the ability of the Call Taker to conference a call with another PSAP on the ESInet

Call Taker successfully conferences the call

NG-027d Verify the ability of the Call Taker to conference a call with another PSAP off the ESInet via 10 digit dialing

Call Taker successfully conferences the call

NG-028 Generate Multiple invite messages to the ESRP and observe performance.

The ESRP should accept all invites until limits are reached.

NG-029a Generate Multiple Invite messages to the SBC and ESInet to simulate a DDoS attack and then observe performance.

The SBC should accept all invite messages until failure. The SBC is not configured to prevent a DDoS attack during this test

NG-029b Generate Multiple Invite messages to the SBC and ESInet to simulate a DDoS attack and then observe performance.

The SBC should accept all invite messages until failure. The SBC is configured to prevent a DDoS attack during this test

NG-030 Generate registrations without authorization to Call takers

The Call takers should register to PSAP.

NG-031 Generate Multiple Invite messages to the SBC and ESInet to simulate a DDoS attack with the SBC configured to throttle requests

The SBC should allow multiple invite request based on the programmed parameters of the SBC


Page 48

NG-032

Load Balance – Calls Volumes are relatively balanced at the Data Centers – Monitor load and display capacity and exceptions if one Data Center is not receiving or handling calls.*

NG-033

Selective transfer – system has capacity for a minimum of six (6) emergency service providers for each emergency service number (ESN).

A call-taker will be able transfer a call to more than 6 agencies. Based on collected results of individual tests with other counties The individual test results appear test cases NG-027a - d.

NG-034a Validate that all system complies in all material respects with the current NENA recommendations for network QoS, for Packet Loss

NENA recommends a target of under 2.5 percent. See table 3.3.1a for more information.

NG-034b Validate that all system complies in all material respects with the current NENA recommendations for network QoS, for Jitter

NENA recommends a target of less than 20mS variation. See table 3.3.1b for more information.

NG-034c Validate that all system complies in all material respects with the current NENA recommendations for network QoS, for Latency

NENA recommends a target of 35mS or less packet delay. See table 3.3.1c for more information.

NG-035a Generate Multiple Invite messages to the SBC and ESInet to simulate a TDoS attack and then observe performance.

The LNG should accept all IAM messages until failure. The SBC is not configured to prevent a TDoS attack during this test.

NG-035b Generate Multiple Invite messages to the SBC and ESInet to simulate a TDoS attack and then observe performance.

The LNG should accept all SS7 IAM messages until failure. If possible, the system is configured to prevent a TDoS attack during this test.

NG-036


Page 49

* - Carriers are planned to first route A-l plus numbers to Data Center East and M through Z to Data Center West, with the alternate routes operating properly.

Table 3.3.1 QoS Recommendations from NENA The following network performance requirements are taken directly from NENA 08-506, Version 1, December 14, 2011:

a. Packet Loss An overall (end-to-end) packet loss budget for maintaining intelligible voice transmission is about 5 Percent. Out of that 5 percent budget approximately one half of the packet loss should be allocated for the ESInets with the remaining allocated for the origination network. It is a best practice to engineer ESInets to keep the packet loss budget under 2.5 percent. The ESInets should be designed without oversubscription. Packet loss of less than 1 percent should be achievable on such ESInets.

b. Jitter It is a best practice to design ESInets to maintain less than 20mS variation in the end point jitter buffers.

c. Latency The one-way transit delay (e.g. end-to-end, mouth to ear) for real-time media packets should not exceed 150mS. (ITU-TG.114). The maximum acceptable delay for packets traversing the ESInet should be less than or equal to 35 mS. It is a best practice to design ESInets to operate with less than 15 to 20 mS of latency. This allows the original encode and decode and a conference bridge in the middle of the path and still achieves the maximum 35mS or less packet delay.


Page 50

4.0 Additional Testing The test cases ensure that, call through and field-testing has been performed.

Test Case # Test Description Expected Test Outcome Notes Results/Dates/Initials

V-000 Perform Call Through Testing for NXXs, Carrier, and PSAP combinations shown on the table below. Ensure each Class of Service is Tested in each Rate Center in each Originating Location. (See Templates in appendices)

V-001 Exchange Testing Direct This section was moved to 2.15 in this document

The Narrative and the ETSB Network Diagrams include 1 Exchanges to be and tested for call completion to the correct PSAPs each time using SIP Connectivity Insert as needed.

V-002 Split Exchange Testing Indirect Legacy Network Interfaces. This section was moved to 2.15 in this document

The Narrative Plan has a table and reference to the ETSB Diagram to reflect the Split Exchanges to be tested for call completion to the correct PSAPs each time using Legacy Gateways to be further documented.


Page 51

5.0 Glossary Glossaries appear in other documents included in the filing, and are hereby included by reference. Additional are terms are defined below.

APP Application Server ARO After Receipt of Order ASR Access Service Request IAM SS7 Initial Address Message MIS Management Information System NIU Northern Illinois University NTP Network Time Protocol SNMP Simple Network Monitoring Protocol SNTP Simple Network Time Protocol TBD To Be Determined


Page 52

Appendix A - Standards Report Resolution Template

Standards Clarification/Resolution Request - NG-911, Inc. Item Date Trouble

Ticket(s) Vendor(s) Compliance Clarification Request Standard

Name/ Section

Resolution Y/N

1 2 3 4 5 6 7 8 9 10 n


Page 53

Appendix B - General Trouble Report Resolution Template

Trouble Resolution Request - NG-911, Inc. Commission Item Date

Time Open

Trouble Ticket(s)

Vendor(s) Brief Description of Trouble Severity Level

Resolution Y/N

Date Closed

Commission Report Y/N/NA and

Which Commission 1 Y 2 Y 3 4 5 6 7 8 9 n

1. During Pre-Cutover Testing, the Trouble Resolution timeframe will be agreed upon by all parties before the start of the testing

process. 2. After Cutover to live service, the Trouble Resolution timeframe will be agreed upon based on Severity Level, Service Level

Agreements (SLAs) including an Escalation Policy. 3. Trouble Report filing to the Commissions will be governed by the Commission requirements. NG 9-1-1, Inc. will follow

ISP/ICC and FCC guidelines as they pertain to the 911 SSP for Trouble Reports.


Page 54

Appendix C - End to End Test Requirements End-to-End Test Plans are only developed after Approval to proceed with the ICC. The following types of testing will be added to End-to-End Test Plan.

Origination Locations will be tested using test numbers provided by the Access Carrier from the Central Offices and/or MTSO. This includes a call from each NPA NXX and in some cases line numbers. This includes Split Exchange Testing. This includes Class of Service Testing to the extent that routing is unique. This includes TTY Testing. This includes SS7 End to end testing with Point Codes as required. This includes testing for failovers by blocking the Initial routes and verifying the alternate routes are used. This includes testing to each PSAP in the architecture. This includes testing the TCC texts end to end. This includes verification the Mapping is operational. This includes transfer in and out testing to neighboring PSAPs. This includes one button and all forms of Dispatch to all Agencies Participating and Adjacent. This includes testing of Conference Capabilities This includes Testing from all ILECs, RLECs, CLECs, Wireless Carriers and VoIP Aggregation Providers in the footprint. This includes verification the Database is mapping properly for the numbers in the test cases. In many cases the tests will be from [pseudo numbers and then redone using live friendly customers. The tests will be laid out on an excel spreadsheet by carrier type. Testing will be scheduled so that the adjacent agencies can participate transferring in and out of the PSAP(s) being converted. Test results will be shared as required with all appropriate ISP/ICC Staff. The ICC and ISP agree all tests that are required are completed before proceeding to cutover. Default routing will be tested and the [properly identified PSAP will get the default routed calls per the plans. The Cutover plan will run through each location and exchange to cutover and test for full operation,


Page 55

End of Document

August 2017 - Carrier Listing Issues DEKALB COUNTY 364

CLLI NPA NXX RATE CENTER LINE NUMBERS TEST* CARRIER PS/ALI -Other TYPE COUNTY LATA

DKLBILXAXMD 779 212 DE KALB 1000 1999 365 Wireless No lines Wireless DeKalb Sterling 364Not on Diagram

DKLBILRSDMD 815 756 DE KALB 0000 9999 T-Mobile Level 3 Transport Wireless Dekalb Sterling 364DKLBILRSDMD 815 517 DE KALB 2000 2999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 517 DE KALB 4000 4999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 517 DE KALB 5000 5999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 517 DE KALB 6000 6999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 764 DE KALB 8000 8999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 0000 9999 9999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 0000 0999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 1000 1999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 2000 2999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 3000 3999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 4000 4999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 5000 5999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 6000 6999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 7000 7999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 8000 8999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 793 DE KALB 9000 9999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 909 DE KALB 0000 9999 9988 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 995 DE KALB 0000 0999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 995 DE KALB 1000 1999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 995 DE KALB 2000 2999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 995 DE KALB 3000 3999 T-Mobile Wireless Dekalb Sterling 364DKLBILRSDMD 815 995 DE KALB 4000 4999 T-Mobile Wireless Dekalb Sterling 364

DKLBILXA1MD 815 751 DE KALB 0000 9999 0273 Verizon Wireless ICN Transport Wireless DeKalb Sterling 364DKLBILXA1MD 815 761 DE KALB 0000 9999 0293 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 762 DE KALB 0000 9999 0774 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 764 DE KALB 9000 9999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 1000 1999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 2000 2999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 3000 3999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 4000 4999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 5000 5999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 6000 6999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 7000 7999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 815 901 DE KALB 8000 8999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 779 212 DE KALB 0000 0999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 779 212 DE KALB 2000 2999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 779 212 DE KALB 8000 8999 Verizon Wireless Wireless DeKalb Sterling 364DKLBILXA1MD 779 212 DE KALB 9000 9999 Verizon Wireless Wireless DeKalb Sterling 364

DKLBILRSNMD 779 212 DE KALB 3000 3999 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 779 222 SYCAMORE 6000 6999 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 779 400 DE KALB 5000 5999 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 779 777 DE KALB 0000 9999 2960 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 779 777 DE KALB 0000 0999 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 779 777 DE KALB 2000 2999 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 779 777 DE KALB 6000 6999 AT&T Mobility Wireless Dekalb Sterling 364DKLBILRSNMD 815 XXX DE KALB 4000 4999 AT&T Mobility Wireless Dekalb Sterling 364

DKLBILRS3MD 815 757 DE KALB 0000 9999 0686 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 375 DE KALB 0000 9999 0412 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 375 DE KALB 0000 0999 0412 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 375 DE KALB 1000 1999 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 375 DE KALB 2000 2999 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 375 DE KALB 3000 3999 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 375 DE KALB 9000 9999 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 766 DE KALB 0000 9999 0331 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 766 DE KALB 0000 0999 0331 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 766 DE KALB 1000 1999 US Cellular Wireless DeKalb Sterling 364DKLBILRS3MD 815 766 DE KALB 2000 2999 US Cellular Wireless DeKalb Sterling 364

DKLBILXC3MD 815 501 DE KALB 0000 9999 9603 Sprint Spectrum Level 3 Transport PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 0000 0999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 1000 1999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 2000 2999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 3000 3999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 4000 4999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 5000 5999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 6000 6999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 7000 7999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 8000 8999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 501 DE KALB 9000 9999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 508 DE KALB 6000 6999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 508 DE KALB 7000 7999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 508 DE KALB 9000 9999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 517 DE KALB 3000 3999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 517 DE KALB 7000 7999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 517 DE KALB 8000 8999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 593 DE KALB 0000 0999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 739 SYCAMORE 0000 9999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 824 SHABBONA 6000 6999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 0000 9999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 0000 0999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 1000 1999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 2000 2999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 3000 3999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 4000 4999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 5000 5999 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 6000 6999 6245 Sprint Spectrum PCS Dekalb Sterling 364DKLBILXC3MD 815 970 SYCAMORE 7000 7999 Sprint Spectrum PCS Dekalb Sterling 364

WTMNILXARS0 815 264 WATERMAN 0000 9999 Frontier Uses ESInet POIs ILEC Dekalb Sterling 364WTMNILXARS0 815 264 WATERMAN 0000 0999 Frontier ILEC Dekalb Sterling 364WTMNILXARS0 815 264 WATERMAN 3000 3999 Frontier ILEC Dekalb Sterling 364WTMNILXARS0 815 264 WATERMAN 7000 7999 Frontier ILEC Dekalb Sterling 364WTMNILXARS0 815 264 WATERMAN 8000 8999 Frontier ILEC Dekalb Sterling 364WTMNILXARS0 815 264 WATERMAN 9000 9999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 0000 9999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 2000 2999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 3000 3999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 4000 4999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 5000 5999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 6000 6999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 7000 7999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 8000 8999 Frontier ILEC Dekalb Sterling 364GENOILXARS1 815 784 GENOA 9000 9999 Frontier ILEC Dekalb Sterling 364KRLDILXARS0 815 522 KIRKLAND** 0000 9999 Frontier ILEC Dekalb Sterling 364KRLDILXARS0 815 522 KIRKLAND 2000 2999 Frontier ILEC Dekalb Sterling 364

KRLDILXARS0 815 522 KIRKLAND 3000 3999 Frontier ILEC Dekalb Sterling 364KRLDILXARS0 815 522 KIRKLAND 6000 6999 Frontier ILEC Dekalb Sterling 364KRLDILXARS0 815 522 KIRKLAND 9000 9999 Frontier ILEC Dekalb Sterling 364MAPKILXARS0 815 827 MAPLE PARK** 0000 9999 Frontier ILEC Dekalb Sterling 364MAPKILXARS0 815 827 MAPLE PARK** 3000 3999 Frontier ILEC Dekalb Sterling 364MAPKILXARS0 815 827 MAPLE PARK** 4000 4999 Frontier ILEC Dekalb Sterling 364MAPKILXARS0 815 827 MAPLE PARK** 5000 5999 Frontier ILEC Dekalb Sterling 364MAPKILXARS0 815 827 MAPLE PARK** 9000 9999 Frontier ILEC Dekalb Sterling 364CETNILXARS0 815 384 CRESTON # 0000 9999 Frontier ILEC DeKalb Sterling 364CETNILXARS0 815 384 CRESTON # 3000 3999 Frontier ILEC DeKalb Sterling 364CETNILXARS0 815 384 CRESTON # 5000 5999 Frontier ILEC DeKalb Sterling 364DKLBILXADS0 815 748 DE KALB 0000 9999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 752 DE KALB 0000 9999 Frontier NIU/PS/ALI ILEC Dekalb Sterling 364DKLBILXADS0 815 753 DE KALB 0000 9999 Frontier Uses ESInet POIs ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 0000 0999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 1000 1999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 2000 2999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 3000 3999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 4000 4999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 5000 5999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 6000 6999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 7000 7999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 754 DE KALB 8000 8999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 2000 2999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 3000 3999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 4000 4999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 5000 5999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 6000 6999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 7000 7999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 8000 8999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 756 DE KALB 9000 9999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 758 DE KALB 0000 9999 Frontier ILEC Dekalb Sterling 364DKLBILXADS0 815 787 DE KALB 0000 9999 Frontier ILEC Dekalb Sterling 364MALTILXARS0 815 825 MALTA 2000 2999 Frontier ILEC Dekalb Sterling 364MALTILXARS0 815 825 MALTA 9000 9999 Frontier ILEC Dekalb Sterling 364SYCMILXADS0 815 895 SYCAMORE 0000 9999 Frontier ILEC Dekalb Sterling 364SYCMILXADS0 815 899 SYCAMORE 0000 9999 Frontier ILEC Dekalb Sterling 364SHBNILXARS0 815 824 SHABBONA** 0000 9999 Frontier ILEC Dekalb Sterling 364SHBNILXARS0 815 824 SHABBONA** 2000 2999 Frontier ILEC Dekalb Sterling 364SHBNILXARS0 815 824 SHABBONA** 8000 8999 Frontier ILEC Dekalb Sterling 364SHBNILXARS0 815 824 SHABBONA** 9000 9999 Frontier ILEC Dekalb Sterling 364HNCKILXARS0 815 286 HINCKLEY 0000 9999 Frontier ILEC Dekalb Sterling

DKLBILRS8MD 815 593 DE KALB 0000 9999 9988 AT&T Local TCG/Teleport CLEC DeKalb Sterling 364DKLBILRS8MD 815 593 DE KALB 9000 9999 AT&T Local Fixed VoIP CLEC DeKalb Sterling 364

DKLBILXAJMD 779 382 GENOA 0000 9999 0102 Charter Fiberlink CLEC Dekalb Sterling 364DKLBILXAJMD 779 382 GENOA 0000 0999 Charter Fiberlink CLEC Dekalb Sterling 364

DIXNILXAEMD 779 382 GENOA 7000 7999 Centurylink dba QCC VoIP Dekalb Sterling 364DIXNILXAEMD 815 283 WATERMAN 7000 7999 Centurylink VoIP Dekalb Sterling 364DIXNILXAEMD 815 286 HINCKLEY 5000 5999 Centurylink VoIP Dekalb Sterling 364

DKLBILXAX0X 779 777 DE KALB 7000 7999 Comcast IP CLEC Dekalb Sterling 364DKLBILXAX0X 779 222 SYCAMORE 4000 4999 Comcast IP CLEC Dekalb Sterling 364DKLBILXAX0X 815 375 DE KALB 5000 5999 Comcast IP CLEC Dekalb Sterling 364

DKLBILXAX0X 815 517 DE KALB 0000 0999 Comcast Corporate CLEC Dekalb Sterling 364

DKLBILXAX0X 815 517 DE KALB 1000 1999 Comcast Corporate CLEC Dekalb Sterling 364

DKLBILRS0MD 815 766 DE KALB 3000 3999 Level 3 Comm Transport CLEC DeKalb Sterling 364

DKLBILXAQMD 815 283 WATERMAN 0000 9999 1998 Mediacom CLEC Dekalb Sterling 364DKLBILXAQMD 815 283 WATERMAN 1000 1999 1998 Mediacom CLEC Dekalb Sterling 364DKLBILXAQMD 815 522 KIRKLAND 0000 0999 0998 Mediacom CLEC Dekalb Sterling 364DKLBILXAQMD 815 824 SHABBONA 3000 3999 3998 Mediacom CLEC Dekalb Sterling 364DKLBILXAQMD 815 825 MALTA 3000 3999 3998 Mediacom CLEC Dekalb Sterling 364DKLBILXAQMD 815 827 MAPLE PARK 0000 0999 0998 Mediacom CLEC Dekalb Sterling 364

DKLBILRSMMD 779 400 DE KALB 0000 9999 0629 YMAX Magic Jack CLEC Dekalb Sterling 364DKLBILRSMMD 779 400 DE KALB 0000 0999 0629 YMAX no DeKalb lines CLEC Dekalb Sterling 364DKLBILRSMMD 779 400 DE KALB 1000 1999 1629 YMAX CLEC Dekalb Sterling 364DKLBILRSMMD 779 400 DE KALB 2000 2999 2629 YMAX CLEC Dekalb Sterling 364DKLBILRSMMD 779 400 DE KALB 3000 3999 3629 YMAX CLEC Dekalb Sterling 364DKLBILRSMMD 779 400 DE KALB 4000 4999 4629 YMAX CLEC Dekalb Sterling 364

DKLBILXAH60 815 NXX DEKALB XXXX XXXX XXXX Syndeo Networks Added CLEC DeKalb Sterling 364

DKLBILXAYMD 815 517 DE KALB 0000 9999 9921 MCI Verizon Business Fixed VoIP CLEC Dekalb Sterling 364

DKLBILXAYMD 815 517 DE KALB 9000 9999 9921 MCI CLEC Dekalb Sterling 364

DEKALB COUNTY 360

CLLI NPA NXX RATE CENTER LINE NUMBERS TEST* CARRIER TYPE COUNTY LATA

RCFRILRTDS2 815 420 ROCKFORD 0000 9999 Essex CLEC Rockford Rockford 360

DEKALB COUNTY 358

CLLI NPA NXX RATE CENTER LINE NUMBERS TEST* CARRIER TYPE COUNTY LATA

CHCGILWUDS4 779 209 SANDWICH 0000 9999 9999 Peerless No Lines CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 0000 0999 Peerless Not on diagram CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 1000 1999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 2000 2999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 3000 3999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 4000 4999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 5000 5999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 6000 6999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 7000 7999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 8000 8999 Peerless CLEC Dekalb Chicago 358CHCGILWUDS4 779 209 SANDWICH 9000 9999 9999 Peerless CLEC Dekalb Chicago 358

SNDWILAH2MD 779 706 SANDWICH 0000 9999 0999 Verizon ICN Transport Wireless Dekalb Chicago 358

SNDWILAH2MD 779 706 SANDWICH 0000 0999 Verizon Wireless Dekalb Chicago 358SNDWILAH2MD 815 570 SANDWICH 1000 1999 Verizon Wireless Dekalb Chicago 358SNDWILAH2MD 815 570 SANDWICH 7000 7999 Verizon Wireless Dekalb Chicago 358

CHCGILWBXJZ 779 978 SANDWICH 0000 9999 0999 US Cellular Wireless Dekalb Chicago 358CHCGILWBXJZ 779 978 SANDWICH 0000 0999 US Cellular Wireless Dekalb Chicago 358

CHCGILDT8MD 779 706 SANDWICH 7000 7999 Centurylink dba QCC VoIP Dekalb Chicago 358CHCGILDT8MD 815 495 LELAND 7000 7999 CenturyLink VoIP Dekalb Chicago 358CHCGILDT8MD 815 498 SOMONAUK 7000 7999 Centurylink VoIP Dekalb Chicago 358

CHCGIL24DS3 815 570 SANDWICH 8000 8999 8999 First Comm Added CLEC Dekalb Chicago 358CHCGIL24DS3 815 495 LELAND 8000 8999 8999 First Com CLEC Dekalb Chicago 358CHCGIL24DS3 815 498 SOMONAUK 8000 8999 8999 First Com CLEC Dekalb Chicago 358

CHCGILGMDS7 815 570 SANDWICH 0000 9999 4996 Level 3 Transport CLEC Dekalb Chicago 358CHCGILGMDS7 815 570 SANDWICH 4000 4999 Level 3 CLEC Dekalb Chicago 358CHCGILGMDS7 815 570 SANDWICH 5000 5999 Level 3 CLEC Dekalb Chicago 358CHCGILGMDS7 815 570 SANDWICH 6000 6999 Level 3 CLEC Dekalb Chicago 358

CHCGILWBXDZ 815 570 SANDWICH 3000 3999 Bandwidth VoIP Aggregator CLEC Dekalb Chicago 358CHCGILWBXDZ 815 570 SANDWICH 9000 9999 Bandwidth CLEC Dekalb Chicago 358CHCGILWBXDZ 779 706 SANDWICH 1000 1999 Bandwidth CLEC Dekalb Chicago 358CHCGILWBXDZ 815 246 EARLVILLE 2000 2999 Bandwidth CLEC Dekalb Chicago 358

SNDWILXADS0 815 786 SANDWICH** 3 way 0000 9999 Frontier Uses ESInet POIs ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 1000 1999 Frontier ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 2000 2999 Frontier ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 3000 3999 Frontier ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 6000 6999 Frontier ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 7000 7999 Frontier ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 8000 8999 Frontier ILEC Dekalb Chicago 358SNDWILXADS0 815 786 SANDWICH** 9000 9999 Frontier ILEC Dekalb Chicago 358ERVLILXARS0 815 246 EARLVILLE **# 0000 9999 Frontier ILEC Dekalb Chicago 358ERVLILXARS0 815 246 EARLVILLE ** 4000 4999 Frontier ILEC Dekalb Chicago 358ERVLILXARS0 815 246 EARLVILLE ** 6000 6999 Frontier ILEC Dekalb Chicago 358ERVLILXARS0 815 246 EARLVILLE ** 7000 7999 Frontier ILEC Dekalb Chicago 358ERVLILXARS0 815 246 EARLVILLE ** 8000 8999 Frontier ILEC Dekalb Chicago 358ERVLILXARS0 815 246 EARLVILLE ** 9000 9999 Frontier ILEC Dekalb Chicago 358SMNKILXARS0 815 498 SOMONAK** 0000 9999 Frontier ILEC Dekalb Chicago 358SMNKILXARS0 815 498 SOMONAK** 1000 1999 Frontier ILEC Dekalb Chicago 358SMNKILXARS0 815 498 SOMONAK** 2000 2999 Frontier ILEC Dekalb Chicago 358SMNKILXARS0 815 498 SOMONAK** 3000 3999 Frontier ILEC Dekalb Chicago 358SMNKILXARS0 815 498 SOMONAK** 4000 4999 Frontier ILEC Dekalb Chicago 358SMNKILXARS0 815 498 SOMONAK** 9000 9999 Frontier ILEC Dekalb Chicago 358PWPWILXARS0 815 627 PAW PAW** 3 way 0000 9999 Frontier ILEC Dekalb Chicago 358PWPWILXARS0 815 627 PAW PAW** 0000 9999 Frontier ILEC Dekalb Chicago 358PWPWILXARS0 815 627 PAW PAW** 2000 2999 Frontier ILEC Dekalb Chicago 358PWPWILXARS0 815 627 PAW PAW** 3000 3999 Frontier ILEC Dekalb Chicago 358PWPWILXARS0 815 627 PAW PAW** 8000 8999 Frontier ILEC Dekalb Chicago 358PWPWILXARS0 815 627 PAW PAW** 9000 9999 Frontier ILEC Dekalb Chicago 358LELDILXBRS0 815 495 LELAND** 0000 9999 Frontier ILEC Dekalb Chicago 358

CHCIILNQPS3 815 498 SOMONAK 6000 6999 Comcast Corporate CLEC Dekalb Chicago 358CHCIILNQPS3 815 570 SANDWICH 2000 2999 Comcast Corporate CLEC Dekalb Chicago 358

XXXXXXXXXXX 815 XXX TOWN(s) XXXX XXXX Birch Telecom Added CLEC DeKalb Locate Locate

XXXXXXXXXXX 815 TOWN(s) XXXX XXXX D.N.A.Comm Added CLEC DeKalb Locate Locate

XXXXXXXXXXX 815 XXX TOWN(s) XXXX XXXX Intelliquent Added PCS DeKalb Locate Locatewas Onvoy

SELECTIVE ROUTERS

DIXNILXA9ED SR DIXON CenturylLink ILEC Dekalb Sterling 364DKLBILXA4ED SR DEKALB Frontier ILEC Dekalb Sterling 364GENVILGNDS0 SR GENEVA AT&T ILEC Dekalb Chicago 358BLTNINXN1ED SR Bloomington Future rehome replace DKLBILXA4ED Frontier ILEC Dekalb Bloomington 366

* Test Numbers from LERG must be replaced with validated field test numbers. All Test numbers must be in the GIS Databsae with full addressing.** Split Exchanges; Counties for Splits shown on Diagrams# Creston was opted to Ogle. Rochelle is therefore deleted from DeKalb and so is Creston.$ Amit Patel indicated Syndeo has a DKLBIL Switch, then Chicago based Switch then a Denver based Switch which all send calls to NINGA 11 Counties he serves. None in JoDaviess, Lee and McHenry. All SIPNIU PS/ALI added to notation for DeKalb 815 762, 763, uses on Campus POIsPaw Paw - Subtending the CenturyLink Legacy SR. Sandwich 5RU - Add the CLLI as needed. UI - Under InvestigationPeerless says they are not active in Illinois - yet, they are in LERG and now we find them with actual calls in JoDaviess. InvestigateNo Lines - did not show on DiagramFrontier chose to use DeKalb and Belevidere Wire Center ESInet POIs to reach the Data CentersBoone DeKalb Opted In per Boone Legacy Diagram; First SR Geneva AT&T; Then to DKLBILXA4EDPaul Stoffels requested change from DKLBILXA3ED to 4ED on all Frontier references. Next image shows why Harvard and South Beloit cannot be in DeKalb

This image helps to see the splits and opted Central Offices. Narrative describes handling supported by the DeKalb Diagrams